Detokenization and Tokenization

If you are sending sensitive data to a 3rd-party API and receive sensitive data in the response from that API, then you might need to use transparent detokenization and transparent tokenization in the same request and response pair. As with any Transparent Gateway API request, you will construct the HTTPS payload to match the specification of the 3rd-party API. In addition to this, you will need to make a few minor modifications to the request. You will then POST the request to the TokenEx transparent detokenization endpoint. TokenEx will replace the token in the request with the cleartext data before forwarding the request to the 3rd party. The response will be returned to the transparent gateway endpoint by the 3rd-party API. Data elements that match the regular expression will be tokenized before the response is returned to your application. To accomplish this functionality, first, follow the same documentation that is outlined for transparent detokenization.


If one or more headers are expected from the endpoint, you can request they be included in the response by providing the header names as a comma-separated list within the optional TX_Headers header.

This feature supports the following HTTP verbs: POST. It also supports any data format (JSON, XML, Form URL, etc.)