This page's content:

Payment Page API

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:

integration_key string

Your unique and secret integration key.

name string

Customer name.

email string

Customer email address.

country string

Two-letter country code ar for Argentina.

instalments string

The number of instalments for this payment(Range of 1 to 6). Example: 1-6.

payment_type_code string

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_code string

Unique identifier for this payment (usually the order number from your system).

currency_code string

The currency code of your transaction. Supported values: ARS and USD

amount float

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:

integration_key string

Your unique and secret integration key.

payment.name string

Customer name.

payment.email string

Customer email address.

payment.phone_number string

Customer phone number with area code.

payment.country string

Two-letter country code ar for Argentina.

payment.document string

Customer CUIT / CUIL / CDI (taxpayer identification number). It must be a valid one. You can check our documentation about validation here

payment.city string

Customer city.

payment.state string

Customer state name.

payment.address string

Customer address.

payment.street_number string

Customer street number.

payment.zipcode string

Customer zipcode.

payment.merchant_payment_code string

Unique identifier for this payment (usually the order number from your system).

payment.currency_code string

The currency code of your transaction. Supported values: ARS and USD

payment.amount_total float

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_code string

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:

payment.payment_type_code string

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:

payment.payment_type_code string

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:

payment.payment_type_code string

The value of this field always will be creditcard for credit card transactions.

payment.instalments integer

The number of instalments of the payment (accepts 2x, 3x, 6x, 9x and 12x).

payment.creditcard JSON

An object containing the customer’s credit card information.

payment.creditcard.card_number string

Credit card number.

payment.creditcard.card_name string

Credit card cardholder name.

payment.creditcard.card_due_date string

Credit card due date (“valid thru”) in the format mm/yyyy.

payment.creditcard.card_cvv string

Credit card security code.

payment.creditcard.auto_capture boolean

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).