Skip to main content

Card Vault

API data

API Gateway
This API is used for payment gateway operations:

Introduction

The Vault operation lets you store a consumer’s card data in the vault for future payments and recurrence. This functionality is essential to implement recurring payments and improve the user experience by avoiding the need to enter card data on every transaction.


Store card in the vault

To create a vault record from a consumer’s card data, send a POST request to /v1/vaults/cards with the required data. The example below shows a typical request.

POST /v1/vaults/cards

Via REST request with the following body:

Request
{
"numberToken": "88f466c4-d17a-4430-952f-2a44bdb98525",
"brand": "visa",
"cardholderName": "JOSE SILVA",
"expirationMonth": "01",
"expirationYear": "19",
"verifyCard": false,
"securityCode": "123"
}

Data dictionary - Parameters

PROPERTYDESCRIPTIONTYPELOCATIONREQUIREDMAX SIZE
NumberTokenTokenized card number.stringbodyyes36
BrandCard brand (visa, mastercard, elo, amex, hipercard).stringbodyyesFixed
CardholderNameCardholder name printed on the card.stringbodyyesMust match the name on the card
ExpirationMonthCard expiration month (two digits).stringbodyyes2
ExpirationYearCard expiration year (two digits).stringbodyyes2
VerifyCardPerforms a verification transaction to check whether the provided card is valid.booleanbodyyesFixed
SecurityCodeSecurity code (CVV).stringbodyno04
Note

When verifyCard is set to true, the system performs a verification transaction to validate the card. This operation may generate a small charge depending on the card brand.

Domains

PROPERTYVALUES
Brandvisa, mastercard, elo, amex, hipercard
Card stored successfully
{
"vaultId": "90fa2d95-3430-4e32-b86b-5b3b3a8393cb"
}

Data dictionary - Response

PROPERTYDESCRIPTIONTYPE
VaultIdIdentifier of the card stored in the vault.string