Tokenization and Vault
PCI Tokenization
For the purpose of carrying out transactions securely, card data should be tokenized through GetNet PSP internal solution, which is available for all four countries: Argentina, Brazil, Chile, Mexico and Uruguay.
Card tokenization
Tokenization process can be accomplished by sending a request body to the GetNet Api with the following details:
- card_number
- customer_id: Buyer identifier. And receiving the token number in return to be used in following actions.
For more details, see the API reference
Create payment with token
In order to allow a payment with a tokenized card, the GetNet Api expects to receive the following details in the payment request body:
- data: First level object.
- payment: Second level object (inside data).
- card: Third level object (inside payment).
- number_token: Property (inside card object) that should have the value of the previously received token number. When including number_token inside the body, you should exclude the card_number property.
Vault
This feature enables the secure storage of sensitive card information, meeting the strict requirements of PCI-DSS, which are essential for payment providers and companies that process card transactions as it helps protect their customers. It offers several actions:
Store card data
The storage process can be achieved by a single request that also supports idempotency, meaning that it produces the same result (avoiding duplicates), regardless of how many times it is made.
For more details, see the API reference
List cards
In order to return a list of saved cards, the GetNet Api expects to receive the
customer_id (buyer identifier) in the query parameter.For more details, see the API reference
Retrieve a card
In order to return a specific saved card information, the GetNet Api expects to receive the
card_id in the final path parameter.For more details, see the API reference
On this page