Implement Payment Pages 2.0 to support one-time payment flows
Learn how to implement Zuora's Payment Pages 2.0 for one-time payments, including configuring hosted payment pages, handling user authentication, and managing invoice payment methods.
You can use Zuora's Payment Pages 2.0 solution to configure and integrate a hosted payment page for processing one-time payments. You can also take advantage of the flow to create a payment method, process a one-time payment, and store the payment method for processing subsequent recurring payments. Additional fields need to be included in the request of the payment page to support processing either authorization amounts or posted invoices.
Best practices
Handle off-session payment attempts requiring user authentication
For the off-session payment attempts that require your users to come back on-session to authenticate the payment, you can also implement a one-time payment flow and configure a payment notification to bring your users on-session.
Follow the procedure to implement a one-time Payment Page. When rendering the Payment Page form, in addition to the additional parameters for authorization amount or invoice processing, pass in the pmId client parameter as well. Use this parameter to allow your users to view and edit their existing credit card payment method information, and re-authenticate the credit card upon submission. For more information about the pmId parameter, see Client parameters for Payment Pages 2.0.
Avoid applying payments to the same invoice through different methods at the same time
To avoid payment processing failure due to applying payments to the same invoice through payment runs and one-time payment flow at the same time, plan your payment collection approach to decide which invoices will be collected through which method, and separate your invoices into different groups. When an invoice is being processed by a payment, it is locked and any further payment against the invoice will fail. If you encounter this problem, wait till the current payment is properly finished and process another payment against the invoice.
One-time payment support matrix
This table is scoped to the current Payment Pages 2.0 one-time payment flow articles and the India-specific overview page. It is a documentation-first matrix of combinations explicitly covered by those pages, not a claim that it includes every payment integration in Zuora Payments.
Core gateway and payment method combinations
Payment Gateway Integration | Payment Method | One-time payment support | Can also save or create a payment method for later recurring use? | Notes |
| Stripe v2 | Credit Card | Yes | Yes | Supports authorization-amount and invoice-processing variants of the flow. |
| Stripe v2 | Credit Card Reference Transaction | Yes | Yes | For India-local flows, see the India-specific section below because the implementation differs. |
| CyberSource 2.0 | Credit Card | Yes | Yes | Covers authorization-amount and invoice-processing use cases. |
| EBANX | PIX | Yes | Not stated in this one-time-flow article | Specifically framed as processing one-time payments using PIX on EBANX. |
| Fat Zebra | Card or account-number based method as described in the article | Yes | Yes | |
| Adyen v2.0 | iDEAL | Yes | Yes | |
| GoCardless | SEPA Direct Debit | Yes | Yes | The flow references GoCardless Instant Bank Pay and Verified Mandates for authorization-amount or invoice-processing scenarios. |
| Braintree | Credit Card | Yes | Yes |
India-specific local flow combinations
| Stripe v2 | Credit Card Reference Transaction | Yes | Yes | Mandates must be established for local recurring payments in India; recurring payments without mandate ID data fail. |
| CyberSource 2.0 | Credit Card | Yes | No | The gateway instance must use the CyberSource India endpoint. |