Detokenization and Tokenization Integration
To begin using this service, you simply need to make a few modifications to the code that is constructing your HTTPS POST to the 3rd-party endpoint.
- Update the URL to POST to TokenEx
- Add HTTP Header for the intended URL
- TX_URL
- Add your Authentication Headers
- TX_TokenExID
- TX_APIKey
- Add an HTTP Header to locate the sensitive data within the response to be tokenized using a regular expression
- TX_ResponseField
- Add an HTTP header to apply a token scheme to the data located in the response to be tokenized
- TX_TokenScheme
- Wrap the field in the HTTP Body with three curly braces
- example:
{{{424242XXXXXX4242}}}
- example:
HTTP Request Headers
| Header | Description |
|---|---|
| TX_TokenExID | Your TokenExID |
| TX_APIKey | Your API key |
| TX_URL | The endpoint URL to which TokenEx should POST the detokenized request |
| TX_ResponseField | A regular expression to locate the data element in the response to be tokenized |
| TX_TokenScheme | see Token Schemes |
| TX_Headers | (Optional) Comma-separated list of desired headers received from the endpoint |
HTTP Response Headers
| Header | Description |
|---|---|
| tx_Message | Informational message about the request. Number of possible matches based on Regular Expression, etc. |
| tx_tokenize_error_xxxx | Reports any error in tokenization |
| tx_thirdpartystatuscode | The status code received from the third party defined in the tx-url request header |
| tx_tokenexstatuscode | The status code for the request to TokenEx |