Skip to main content

EBANX

This page provides an overview of the payments methods provided by the EBANX adapter in the IXOPAY platform. It also includes a full list of all configuration options available to you when integrating EBANX within your payments landscape, as well as an overview of the parameters required when submitting a transaction via IXOPAY's API.

Payment Methods

Payment MethodTransaction FlowsTransaction Types
BalotoFull-Page RedirectDebit & Refund
BancoDoBrasilFull-Page RedirectDebit & Refund
BankTransferFull-Page RedirectDebit, Refund & Payout
BanrisulFull-Page RedirectDebit & Refund
BoletoFull-Page RedirectDebit & Refund
BradescoFull-Page RedirectDebit & Refund
EbanxAccountFull-Page RedirectDebit & Refund
EftFull-Page RedirectDebit & Refund
ItauFull-Page RedirectDebit & Refund
MulticajaFull-Page RedirectDebit & Refund
OxxoFull-Page RedirectDebit & Refund
PagoEfectivoFull-Page RedirectDebit & Refund
PagosNetFull-Page RedirectDebit & Refund
SafetyPayFull-Page RedirectDebit & Refund
SafetyPayCashFull-Page RedirectDebit & Refund
SafetyPayOnlineFull-Page RedirectDebit & Refund
SencillitoFull-Page RedirectDebit & Refund
ServipagFull-Page RedirectDebit & Refund
SpeiFull-Page RedirectDebit & Refund
WebpayFull-Page RedirectDebit & Refund
PixFull-Page RedirectDebit
PixAutomaticoFull-Page RedirectRegister, Debit (Initial Charge + Enrollment), Recurring Debit, Deregister
UPIFull-Page RedirectDebit
UPIAutopayFull-Page RedirectDebit (Enrollment), Recurring Debit, Deregister

Refund is available for any completed debit on Pix, PixAutomatico, UPI & UPIAutopay — it targets the original EBANX payment hash directly and is not payment-method-specific.

Configuration

The EBANX (non-PCI) adapter is configured with a single credential field, labeled Integration Key. No password, API secret, or certificate is required.

Two additional configuration options are mandatory:

OptionValuesPurpose
Default UPI FlowUPI QR Code (upi-qrcode), UPI Intent (upi-intent)Used for UPI Debit when the transaction doesn't specify extraData.psp:payment.payment_type_code
Default UPI Autopay FlowUPI Autopay QR Code (upi-qrcode-autopay), UPI Autopay Intent (upi-intent-autopay)Used for UPI Autopay flows when the transaction doesn't specify extraData.psp:payment.payment_type_code

Additional Parameters

Debit: APM & BankTransfer

FieldRequired
customer.firstNametrue
customer.lastNametrue
customer.emailtrue
customer.billingPhonefalse
customer.billingAddress1false
customer.billingCityfalse
customer.billingPostcodefalse
customer.billingStatefalse
customer.billingCountrytrue

Refund: APM & BankTransfer

FieldRequired
descriptiontrue

Payout: BankTransfer

FieldRequired
customer.firstNametrue
customer.lastNametrue
customer.emailtrue
customer.birthDatetrue
customer.ibantrue
customer.bictrue for Brazil (=bank branch)
customer.billingCountrytrue
customer.nationalIdtrue
customer.extraData.documentTypetrue
customer.extraData.bankDetailstrue
customer.extraData.bankNametrue
customer.extraData.termsAcceptedAt (format: YYYY-MM-DD HH:MM:SS)Depending on EBANX business account

Debit: Pix

The adapter does not validate these fields itself — it simply omits whatever is missing from the request. Refer to EBANX's own requirements for which of these are mandatory to process a payment.

FieldDescription
customer.firstName, customer.lastNameCombined into the payer's full name
customer.emailPayer email
customer.nationalIdPayer document/tax ID
customer.billingCountryPayer country; used only if extraData.psp:subscription.country is not set
extraData.psp:subscription.countryOverrides customer.billingCountry for country resolution when set

Register (Enrollment): PixAutomatico

FieldRequired
transactionIdtrue
customer.firstNametrue
customer.lastNametrue
customer.emailtrue
customer.nationalIdtrue
customer.billingCountryfalse, unless extraData.psp:subscription.country is set
extraData.psp:subscription.countryfalse — overrides customer.billingCountry when set
extraData.psp:subscription.subscription_nametrue (also accepts extraData.subscription.subscription_name)
extraData.psp:subscription.frequencytrue (also accepts extraData.subscription.frequency)
extraData.psp:subscription.retrytrue (also accepts extraData.subscription.retry)
extraData.psp:subscription.start_datetrue (also accepts extraData.subscription.start_date)
extraData.psp:subscription.fixed_amountone of fixed_amount or max_amount_floor is required
extraData.psp:subscription.max_amount_floorone of fixed_amount or max_amount_floor is required
extraData.psp:subscription.expiration_datefalse
extraData.psp:subscription.expiration_time_in_secondsfalse — defaults to 3600 seconds

Debit (Initial Charge + Enrollment): PixAutomatico

Triggered by sending the debit as "with register". Combines an initial charge with a Pix Automatico enrollment in a single request; accepts the same customer and subscription fields as Register (Enrollment): PixAutomatico above.

Recurring Debit: PixAutomatico

Charges an existing Pix Automatico enrollment.

FieldRequired
referencedTransactiontrue — must reference the original enrollment transaction, whose transactionId is used as the merchant enrollment code
extraData.psp:payment.due_datefalse

Debit: UPI

Only extraData.psp:payment.payment_type_code is validated by the adapter (it must resolve, directly or via the config fallback, to a supported value — otherwise the transaction is rejected before calling EBANX). The customer fields below are not validated by the adapter itself; refer to EBANX's own requirements for your target flow.

FieldRequired
extraData.psp:payment.payment_type_codetrue, effectively — one of upi-qrcode / upi-intent; falls back to the "Default UPI Flow" configuration option if omitted, but the resolved value must be one of these two or the transaction is rejected
customer.firstName, customer.lastNamenot adapter-validated — combined into the payer's full name
customer.emailnot adapter-validated
customer.billingPhonenot adapter-validated
customer.billingAddress1not adapter-validated
customer.billingCitynot adapter-validated
customer.billingStatenot adapter-validated
customer.billingPostcodenot adapter-validated
customer.billingCountrynot adapter-validated

Debit (Enrollment): UPIAutopay

Triggered by sending the debit as "with register". Like plain UPI Debit, only extraData.psp:payment.payment_type_code is validated by the adapter; the customer/subscription fields below are not.

FieldRequired
extraData.psp:payment.payment_type_codetrue, effectively — one of upi-qrcode-autopay / upi-intent-autopay; falls back to the "Default UPI Autopay Flow" configuration option if omitted, but the resolved value must be one of these two or the transaction is rejected
customer.firstName, customer.lastNamenot adapter-validated — combined into the payer's full name
customer.emailnot adapter-validated
customer.billingPhonenot adapter-validated
customer.billingAddress1not adapter-validated
customer.billingAddress2not adapter-validated — mapped to street_number
customer.billingCitynot adapter-validated
customer.billingStatenot adapter-validated
customer.billingPostcodenot adapter-validated
customer.billingCountrynot adapter-validated
extraData.psp:subscription.subscription_namenot adapter-validated (also accepts extraData.subscription.subscription_name)
extraData.psp:subscription.expiration_datenot adapter-validated
extraData.psp:subscription.recurrence_valuenot adapter-validated
extraData.psp:subscription.recurrence_rulenot adapter-validated
extraData.psp:subscription.min_amountnot adapter-validated
extraData.psp:subscription.max_amountnot adapter-validated

Recurring Debit: UPIAutopay

Charges an existing UPI Autopay enrollment.

FieldRequired
referencedTransactiontrue — must reference the original enrollment transaction, whose transactionId is used as the merchant enrollment code
extraData.psp:payment.payment_type_codefalse — taken from the referenced enrollment transaction if not set on the recurring debit itself, otherwise falls back to the "Default UPI Autopay Flow" configuration option
extraData.psp:subscription.countryfalse — taken from the referenced enrollment transaction if not set, otherwise falls back to customer.billingCountry

Deregister: PixAutomatico & UPIAutopay

Cancels an existing Pix Automatico or UPI Autopay enrollment.

FieldRequired
referencedTransactiontrue — must reference the original enrollment transaction, whose transactionId is used as the enrollment ID to cancel

Refund: Pix, PixAutomatico, UPI & UPIAutopay

Refunds an existing debit by its original EBANX payment hash. Available for any of these payment methods.

FieldRequired
descriptiontrue

Options Request

You can find more information about the options request here: Options Request

Retrieving a list of available banks

EBANX supports 2 endpoints for retrieving a list of available banks for all supported countries. The results may be used for providing the correct parameters for the payout request.

They're available with the options request identifier getAvailableBanks and getBankDetails.