EBANX payment gateway integration
Integrate Zuora with EBANX to process Credit Card and PIX transactions, supporting features like 3D Secure 2.0 and Delayed Capture, with certain limitations.
Zuora integrates with the EBANX payment services to provide a gateway integration called EBANX for processing Credit Card and PIX transactions.
Credit Card
Credit Card payment methods on the EBANX integration can be created through any of the following methods, with the exception of Elo and Hipercard card brands, which cannot be created through hosted payment pages.
-
Zuora UI
-
Hosted payment pages
-
REST APIs for creating payment methods
For credit card transactions, the validation and authorization amount can be 0 or a non-zero value, depending on the supported currencies and country-specific authorization rules. The recommended value is 0. If the 0 amount is not supported, $1 might be used in authorization even if the default value is set to 0. For 3DS2 payment method validation, 0 amount is not supported.
PIX
To enable the PIX payment method type on your tenant, submit a request at Zuora Global Support.
When your customers select PIX to pay, the hosted payment page that you created will be loaded. After your customers enter the customer information on the payment page and submit the page, a barcode will be displayed. Your customers can then use the bank application to scan the barcode and pay. The payment method data will not be stored in Zuora.
PIX payment methods on EBANX can be created through the Payment Pages 2.0 and Payment Forms.
Support for stored credential profiles
The EBANX payment gateway integration includes support for the Stored Credential Transaction framework for Credit Card payment methods. For details, see Support for stored credential transactions overview .
Note that the EBANX payment gateway integration does not support the sharing NTI feature, so existing payment methods that were previously created through other payment gateway integrations cannot be used to process payments through EBANX. To process payments through Ebanx, you must create a payment method through the Ebanx payment gateway integration.
Support for network tokenization
EBANX supports Zuora-provisioned network tokens (via Worldpay NPT) for credit card Customer-Initiated Transactions (CIT) and Merchant-Initiated Transactions (MIT). When network tokenization is enabled and a token exists for a payment method, EBANX uses the network token as the primary credential, falling back to the EBANX gateway token and then the raw PAN in alignment with the global token priority model. Network tokens are gateway-agnostic and can be provisioned on any supported gateway and reused on EBANX once EBANX is configured as network token–capable. For customer-initiated unscheduled payments, Zuora includes a fresh cryptogram and ECI (if available) in the request. Digital wallets, such as Apple Pay and Google Pay, are not supported for Zuora-provisioned network tokenization on EBANX.
For more detailed information, see Network Tokenization.
Support for 3D Secure 2.0
3D Secure 2.0 (3DS2) is a solution for Strong Customer Authentication (SCA) under PSD2 to reduce fraud and increase authorization approvals. The EBANX payment gateway integration supports 3DS2 for Credit Card payment methods. See the following articles for more information:
Support for Delayed Capture
The Delayed Capture feature allows you to authorize the availability of funds for a transaction but delay the capture of funds until a later time. The EBANX payment gateway integration supports Delayed Capture for Credit Card payment methods. For how to use the Delayed Capture feature, see Payment Authorization in Zuora API Reference.
Limitations
Non-referenced refunds are not supported.