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.
Overall, complete the following steps to implement a one-time payment flow:
- Review prerequisites for the implementation of one-time payment flows.
- Set up a Payment Page 2.0.
- Request a signature for the payment page from Zuora.
- Set up your client code to integrate the payment page to your web page.
- Implement the callback response.
You can find detailed instructions in the following section.
Payment gateway integrations that support the implementation
The following tables list Zuora's gateway integrations that support the implementation of one-time payment flows.
|Payment gateway integration
|Detailed instructions for implementation
|Adyen Integration v2.0
|Implement one-time payment flows on Adyen v2.0
|Implement one-time payment flows on Braintree
|Implement one-time payment flows on CyberSource 2.0
Only one-time processing is supported.
|Implement one-time payment flows on Ebanx
|SEPA Direct Debit
|Implement one-time payment flows on GoCardless
|Implement one-time payment flows on Stripe v2
Credit Card Reference Transaction
|Implement one-time payment flows for processing payments in India
Only one-time processing (INR and non-INR) is supported.
Only Non-INR one-time processing is supported.
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.
- Implement one-time payment flows on Adyen v2.0
- Implement one-time payment flows on Braintree
- Implement one-time payment flows on CyberSource 2.0
- Implement one-time payment flows on Ebanx
- Implement one-time payment flows on GoCardless
- Implement one-time payment flows on Stripe v2
- Implement one-time payment flows for processing payments in India