Field mappings for Payment in EBANX Payment Gateway Integration
This reference details the mapping of EBANX API fields to Zuora fields, including their usage in requests and responses for payment processing.
|
EBANX API Field |
Zuora Field |
Request/Response |
Description |
|---|---|---|---|
|
integration_key |
The Integration Key field in the UI |
Request |
Your unique and secret integration key. |
|
payment.name |
CreditCardHolderName |
Request |
Cardholder name. |
|
payment.document |
IdentityNumber |
Request |
Customer’s document. In Brazil, a valid CPF (natural person taxpayer ID) or CNPJ (business taxpayer ID) is required. |
|
payment.merchant_payment_code |
TenantId_PaymentNumber |
Request |
The payment hash Merchant Payment Code (unique merchant ID) |
|
payment.merchant_payment_code |
TenantId_PaymentNumber |
Request |
The payment hash Merchant Payment Code (unique merchant ID) |
|
device_id |
gwOptions_deviceId |
Request |
Unique ID to identify the customer’s device. Used for anti-fraud checking purposes. |
|
payment.card.token |
MITSubmittedParam_Token |
Request |
If a previously created token is informed, no credit card information is needed. EBANX will identify the credit card associated with the token and perform the transaction.Only available for recurring billing. |
|
payment.hash |
GatewayReferenceId |
Response | |
|
payment.merchant_payment_code |
GatewaySecondReference |
Response | |
|
payment.token |
MITReceivedParam_Token |
Response |