To create a payment using EBANX Payment Page, you must call the API method request.
The following parameters are mandatory for Argentina payment methods using EBANX Payment Page. Depending on your business model, more information can be required for a payment request, please talk to an implementation specialist for more details:
integration_keystring
Your unique and secret integration key.
namestring
Customer name.
emailstring
Customer email address.
countrystring
Two-letter country code ar for Argentina.
instalmentsstring
The number of instalments for this payment(Range of 1 to 6). Example: 1-6.
payment_type_codestring
The customer chooses the payment method. Supported values:
_all: all available payment methods for the merchant account in this country.
rapipago: Rapipago.
pagofacil: PagoFacil.
cupon: Cupon de Pagos.
_creditcard: Credit Card.
merchant_payment_codestring
Unique identifier for this payment (usually the order number from your system).
currency_codestring
The currency code of your transaction. Supported values: ARS and USD
amountfloat
Transaction amount, in the specified currency. E.g.,: 100.50
A successful request will return a JSON expression similar to the one below. You will need to redirect the customer to the EBANX Payment Page using the redirect_url.
Direct API
Here’s a guide of User Experience that may help you in your integration with Argentine payments. CLICK HERE.
To create a payment using EBANX Direct, you must call the API method direct.
The following parameters are mandatory for Argentine payment methods using EBANX Direct. Depending on your business model, more information can be required for a payment request, please talk to an implementation specialist for more details:
integration_keystring
Your unique and secret integration key.
payment.namestring
Customer name.
payment.emailstring
Customer email address.
payment.phone_numberstring
Customer phone number with area code.
payment.countrystring
Two-letter country code ar for Argentina.
payment.documentstring
Customer CUIT / CUIL / DNI (ID and taxpayer identification numbers). It must be a valid one. You can check our documentation about validation here
payment.citystring
Customer city.
payment.statestring
Customer state name.
payment.addressstring
Customer address.
payment.street_numberstring
Customer street number.
payment.zipcodestring
Customer zipcode.
payment.merchant_payment_codestring
Unique identifier for this payment (usually the order number from your system).
payment.currency_codestring
The currency code of your transaction. Supported values: ARS and USD
payment.amount_totalfloat
Transaction amount, in the specified currency. E.g.,: 100.50
RapiPago – Direct API
The following parameters are specific to the RapiPago payment method:
payment.payment_type_codestring
The value must be rapipago for RapiPago payments.
A successful request will return a JSON expression similar to the one below. You will need to redirect the customer to voucher_url.
PagoFacil – Direct API
The following parameters are specific to the PagoFacil payment method. Depending on your business model, more information can be required for a payment request, please talk to an implementation specialist for more details:
payment.payment_type_codestring
the value must be pagofacil for PagoFacil payments.
A successful request will return a JSON expression similar to the one below. You will need to redirect the customer to voucher_url.
Cupon de Pagos – Direct API
The following parameters are specific to the Cupon de Pagos payment method. Depending on your business model, more information can be required for a payment request, please talk to an implementation specialist for more details:
payment.payment_type_codestring
The value must be cupon for Cupon de Pagos payments.
A successful request will return a JSON expression similar to the one below. You will need to redirect the customer to voucher_url.
Credit card – Direct API
The following parameters are specific for the credit card payment method. Depending on your business model, more information can be required for a payment request, please talk to an implementation specialist for more details:
payment.payment_type_codestring
The value of this field always will be creditcard for credit card transactions.
payment.instalmentsinteger
The number of instalments of the payment (accepts 2x, 3x, 6x, 9x and 12x).
payment.creditcardJSON
An object containing the customer’s credit card information.
payment.creditcard.card_numberstring
Credit card number.
payment.creditcard.card_namestring
Credit card cardholder name.
payment.creditcard.card_due_datestring
Credit card due date (“valid thru”) in the format mm/yyyy.
payment.creditcard.card_cvvstring
Credit card security code.
payment.creditcard.auto_captureboolean
If true, the payment will be captured automatically by EBANX; if false, the payment will have to be captured by the merchant using the API method capture.
A successful request will return a JSON expression similar to the one below. Credit card payments for merchants with fraud checking enable will have status PE (pending), while for merchants that have fraud checking disabled and auto_capture set to true it will have status CO (confirmed).