CREATE ACCOUNT

capture operation

This page's content:

Endpoints

https://api.ebanxpay.com/ws/capture

https://sandbox.ebanxpay.com/ws/capture

HTTP Method

POST

Response

JSON

This is a server-to-server HTTP POST used by the merchant to capture credit card payments when the auto_capture flag is false in the Direct Operation.

Method parameters

integration_key string, length 100, required

Your unique and secret integration key.

hash string, length 48, required if merchant_payment_code not provided

The payment hash (EBANX unique identifier).

merchant_payment_code string, length 1-40, required if hash not provided

The payment hash Merchant Payment Code (unique merchant ID).

merchant_capture_code string, length 1-200, optional

Optional identifier for the payment capture.

amount float, optional

The amount of the partial capture. You can make only one partial capture per authorized payment and this feature is only available in Brazil. If you want to enable this feature, please contact our Integration Team.

This method call will return a JSON object with the payment data:

Response parameters

status string

The status of the the request (SUCCESS or ERROR).

payment JSON

A JSON object that represents the payment.

payment.hash string, 48 length, unique

The payment hash (EBANX unique identifier).

payment.pin string, 41 length, unique

The payment PIN (EBANX and Customer unique identifier).

payment.country string, 2 length, unique

The country of the payment.

payment.merchant_payment_code string, 1-40 length

The payment hash Merchant Payment Code (unique merchant ID).

payment.order_number string, 1-40 length

The order number, optional identifier set by the merchant. You can have multiple payments with the same order number.

payment.status string, 2 length

The payment status. The following statuses are available:

  • OP: the customer has not yet filled the payment details on the EBANX Checkout. It can change either to CA (time out) or PE.
  • PE: the payment is pending confirmation. It can change either to CA or CO.
  • CO: the payment is confirmed (paid).
  • CA: the payment is cancelled.
payment.status_date string, 19 length, UTC Date

The date and hour of the last status change.

payment.open_date string, 19 length, UTC Date

The date and hour of when the payment was created.

payment.confirm_date string, 19 length, UTC Date

The date and hour of when the payment was confirmed.

payment.transfer_date string, 19 length, UTC Date

The date and hour of when the payment was settled.

payment.amount_br float

The amount in local currency.

payment.amount_iof float

The tax amount in local currency (varies between countries).

payment.amount_ext float

The amount in the original currency.

payment.currency_rate float

The exchange rate used in the payment.

payment.currency_ext string, 3 length, ISO 4217 three letter code

Three-letter code of the original currency.

payment.due_date string, 10 length, dd/mm/yyyy

Expiry date of the payment (not applicable to all payment methods).

payment.instalments integer, ranges from 1 to 12

Number of instalments for the payment, default value is 1.

payment.payment_type_code string, 32 length

The code of the payment method. The supported codes are:

  • amex: American Express credit card (Brazil, Mexico, Colombia).
  • baloto: Baloto (Colombia).
  • bancodobrasil: Banco do Brasil bank transfer (Brazil).
  • banrisul: Banrisul bank transfer (Brazil).
  • boleto: Boleto bancário (Brazil).
  • bradesco: Bradesco bank transfer (Brazil).
  • carnet: CARNET credit card (Mexico).
  • diners: Diners credit card (Brazil, Colombia).
  • discover: Discover credit card (Brazil).
  • ebanxaccount: EBANX Account (Brazil).
  • eft: Bank Transfer (Colombia).
  • elo: Elo credit card (Brazil).
  • hipercard: Hipercard credit card (Brazil).
  • itau: Itaú bank transfer (Brazil).
  • mastercard: MasterCard credit card (Brazil, Mexico, Colombia).
  • multicaja: Multicaja (Chile).
  • oxxo: OXXO (Mexico).
  • pagoefectivo: PagoEfectivo (Peru).
  • pagosnet: PagosNet (Bolivia).
  • safetypay: SafetyPay (Peru, Ecuador, Checkout only).
  • safetypay-cash: SafetyPay Cash (Peru, Ecuador).
  • safetypay-online: SafetyPay Online (Peru, Ecuador).
  • sencillito: Sencillito (Chile).
  • servipag: Servipag (Chile).
  • spei: SPEI bank transfer method (Mexico).
  • visa: Visa credit card (Brazil, Mexico, Colombia).
  • webpay: Webpay (Chile).
payment.details JSON

A JSON object that represents the payment details.

payment.details.billing_descriptor string

The billing descriptor of the payment.

payment.transaction_status JSON

A JSON object that represents the payment credit card transaction.

payment.transaction_status.acquirer string, 16 length

The acquirer that processed the transaction.

payment.transaction_status.code string, 2-7 length

The transaction status code:

  • OK: The transaction amount was approved.
  • NOK: The acquirer did not approved the transaction. The customer must contact the issuer to check for any issue with his credit card.
  • RETRY: Something went wrong with the process. You can retry with the same data. We recommend you to try more 3 times on different periods of time (first try, then second try after 2 hours after the first, etc).

You can see more of these status HERE.

payment.transaction_status.description string, 500 length

The description for the status code, which is returned from the acquirer.

payment.transaction_status.authcode string, length 40

Transaction authentication code in the acquirer.

payment.pre_approved boolean

Flag that shows if a payment is pre-approved by the credit card acquirer.

payment.capture_available boolean

Flag that shows if a payment is ready to be captured. Applies only to credit cards when auto_capture is set to false. Some remarks on this attribute:

  • A payment can only be captured if pre_approved value is true, which means that the payment has been pre approved by the credit card acquirer. Before capture, an authorized payment has status as PE (pending). After the capture, the status changes to CO (confirmed). A payment can only be captured if the status is PE (pending). *Payments must be captured in 4 (four) days, otherwise they are automatically cancelled.

NOTE: It can be changed up to 5 (five) days.

payment.redirect_url string, variable

The URL the customer should be redirected to. Applies to certain payment methods using the Direct API.

payment.pay_with_balance_url string, variable

If the customer has an EBANX Account profile and it has balance enough to pay for the created boleto, the response will contain this parameter responsible for redirecting the customer to his EBANX Account page so he can pay the boleto with his available balance.

payment.boleto_url string, variable

The boleto URL.

payment.boleto_barcode string, length 47

The boleto barcode number. (Boleto)

payment.cip_url string, variable

The CIP URL. (PagoEfectivo)

payment.cip_code string, length 12

The CIP code. (PagoEfectivo)

payment.refunds JSON

An array of objects that represent a refund linked to this payment. This node will only be present if a refund was issued.

payment.refunds.id integer

The ID of the refund on EBANX.

payment.refunds.merchant_refund_code string, length 1-20

The ID of the refund on the merchant system (optional).

payment.refunds.status string, length 2

The status of the refund:

  • RE (Requested): The refund has been requested and is waiting to be processed. It can be cancelled while it has this status.
  • PE (Pending): The refund is being processed. It cannot be cancelled anymore.
  • CO (Confirmed): The refund was processed and the money was sent back to the customer.
  • CA (Cancelled): The refund was cancelled.
payment.refunds.request_date string, length 19, UTC Date

The date and hour when the refund was created.

payment.refunds.pending_date string, length 19, UTC Date

The date and hour when the customer data was received

payment.refunds.confirm_date string, length 19, UTC Date

The date and hour when the money was transferred to the customer.

payment.refunds.amount_ext float

The refunded amount in the original currency.

payment.refunds.description string, length 1-1500

Description of the refund reason.

payment.chargeback JSON

A JSON object that represents a chargeback linked to this payment. This node will only be present if a chargeback was issued.

payment.chargeback.create_date string, length 19, UTC Date

The date and hour when the chargeback was imported into the system.

payment.chargeback.chargeback_date string, length 19, UTC Date

The date and hour when the chargeback was created by the acquirer on behalf of the customer.

payment.chargeback.description string, length 1-1500

Description of the chargeback.

payment.chargeback_credit boolean

Flag that shows if a chargeback credit was issued.

payment.clabe_account string

(Only for SPEI payments) The customer’s CLABE account.

payment.clabe_reference string

(Only for SPEI payments) The reference for the current payment.

First Steps

Integration Methods

Sandbox Testing