The token operation is used to create a token for a given credit card to be used for recurrent payments.
For this method, you will need to wrap the request parameters in a JSON object and send them as the value of a parameter called request_body.
It’s important to know that the tokens expire after 14 months of its last use.
Your unique and secret integration key.
Your unique and public integration key. You can do a token operation using this key instead of the integration key when the request is from the client of your customer (browser, app, etc…). By doing this, you don’t have to deal directly with the credit card information of your customer.
The credit card scheme: amex, aura, diners, discover, elo, hipercard, mastercard, visa.
This must be set if you want to inform the token instead of letting EBANX create one.
The two-letter country code for the customer country. The available codes are:
- br: Brazil.
- co: Colombia.
- mx: Mexico.
The credit card number (14-19 digits, must pass the Luhn algorithm).
The cardholder name, as written in the credit card.
The credit card valid thru date (formatted as mm/yyyy).
The Card Verification Value (CVV) (3-4 digits).
The status of the request (SUCCESS or ERROR).
The credit card scheme.
The generated token or the same one that was informed in the request.
The masked credit card number. This can be stored and shown to the customer.