Links

Vault

Server to Server API to detokonize data
Use the reverse Vault API to convert sensitive data from a PCI Proxy token back to the clear text value. The API supports single as well as bulk detokenization for credit card number-, cvv- and custom value aliases.
Please consider the following constraints when using the reverse Vault API:
  • For bulk detokenizations the maximum number of requests per batch is 100
  • For custom values we do not apply any form of validation
  • Please also consider the PCI DSS requirements below
Only PCI DSS compliant merchants are allowed to use the reverse Vault API as it returns sensitive plain text data which extends your PCI DSS scope. Exemptions can be granted for a limited period of time if there is a valid business reason such as for instance PSP migrations or in case of non-sensitive data. For any sensitive data to be revealed in client apps, please use the Show API integration.
Learn below how to build the request. You can find as well an example request and response.

Endpoints

1. Request access

Due to increased security risk, the reverse Vault API needs to be activated for your merchantId and IP whitelisting is required. Please get in touch with our team to configure it for you.

2. Detokenization Request

post
https://api.sandbox.datatrans.com
/v1/aliases/detokenize
Vault API

Example

Request
Response
curl -L -X POST 'https://api.sandbox.datatrans.com/v1/aliases/detokenize' \
-H 'Authorization: {merchantId}:{password}' \
-H 'Content-Type: application/json' \
--data-raw '{
"requests": [
{
"type": "CARD",
"alias": "7LHXscqwAAEAAAGELW8yPYx7lOreANmg"
},
{
"type": "CVV",
"alias": "LqFr-TLBQRC6lIkfogaSDbz3"
},
{
"type": "CUSTOM",
"alias": "DHoVO57dSKKK5EDH-ysnSw=="
}
]
}'
{
"overview": {
"total": 3,
"successful": 3,
"failed": 0
},
"responses": [
{
"type": "CARD",
"pan": "5186151650011006"
},
{
"type": "CVV",
"cvv": "123"
},
{
"type": "CUSTOM",
"custom": "John Doe"
}
]
}
CVV aliases have a limited lifespan of 30 minutes and can't be detokenized anymore when expired.