Token Management
Technical identifier pre-defined at on-boarding that identifies the API
consumer.
Format shall be the string 'APIKEY' followed by a space and the
api key value.
Example: APIKEY c03f88fe-01ba-11e8-ba89-0ed5f89f718b
Technical identifier used for troubleshooting.
It helps on customer support when needed.
Each API request must be identified with a unique correlation Id.
It correlates the response and the request and eventually a notification if any.
Identifier of the merchant provided by Thales at on-boarding.
The user and card information encrypted in a JWE structure (see security section in the documentation).
Once decrypted, the JWE plaintext contains the following JSON object:
| JSON field parameter name | description | MOC | Length |
|---|---|---|---|
| fpan | The funding pan to tokenize. Value expected when 'source' parameter is 'MANUAL' or 'ON_FILE'. | C | Up to 19 |
| exp | The expiry date in format MMYY. Value expected when 'source' parameter is 'MANUAL' or 'ON_FILE'. Optional when VCES feature is activated for VISA | C | 4 |
| token | Token number. Value expected when 'source' parameter is 'TOKEN'. | C | Up to 19 |
| name | The card holder name in the format FIRSTNAME LASTNAME or as written on the card. MDES limits the length to 27 characters so ETP may truncate the provided value. This parameter is mandatory for Discover card tokenization. | O | 256 |
| cvv | The security code. It can help the issuer in the decision of approving the payment. | O | 3 or 4 |
| accountId | The card holder account identifier defined by the Merchant. It can help the issuer in the decision of approving the payment. | O | 24 |
| The card holder email. This parameter is mandatory for AMEX card tokenization. | O | 128 |
Example: {"fpan":"5123456789012345", "exp":"0822", "name":"JOHN DOE", "cvv":"123", "accountId":"johndoe", "email":"[email protected]"}
The card info entry mode.
'MANUAL' It can help the issuer in the decision of approving the payment.
'TOKEN' is allowed just for Visa, used by token per token feature
Card holder language in ISO-639-1 two-letter language code.
enExample: enCard holder country in ISO-3166-1 alpha-2 two-letter country code.
USCreated
Bad request - Not Retryable
Unauthorized - Not Retryable
Too Many Requests - Retryable
Internal Server Error - Not Retryable
Service Unavailable - Retryable
Technical identifier pre-defined at on-boarding that identifies the API
consumer.
Format shall be the string 'APIKEY' followed by a space and the
api key value.
Example: APIKEY c03f88fe-01ba-11e8-ba89-0ed5f89f718b
Technical identifier used for troubleshooting.
It helps on customer support when needed.
Each API request must be identified with a unique correlation Id.
It correlates the response and the request and eventually a notification if any.
Identifier of the merchant provided by Thales at on-boarding.
The user and card information encrypted in a JWE structure (see security section in the documentation).
Once decrypted, the JWE plaintext contains the following JSON object:
| JSON field parameter name | description | MOC | Length |
|---|---|---|---|
| fpan | The funding pan to tokenize. | M | Up to 19 |
| exp | The expiry date in the format MMYY. Optional when VCES feature is activated for VISA | C | 4 |
| name | The card holder name in the format FIRSTNAME LASTNAME or as written on the card. MDES limits the length to 27 characters so ETP may truncate the provided value. This parameter is mandatory for Discover card tokenization. | O | 256 |
| cvv | The security code. It can help the issuer in the decision of approving the payment. | O | 3 or 4 |
| accountId | The card holder account identifier defined by the Merchant. It can help the issuer in the decision of approving the payment. | O | 24 |
| The card holder email. This parameter is mandatory for AMEX card tokenization. | O | 128 |
Example: {"fpan":"5123456789012345", "exp":"0822", "name":"JOHN DOE", "cvv":"123", "accountId":"johndoe", "email":"[email protected]"}
The card info entry mode.
'MANUAL' It can help the issuer in the decision of approving the payment.
Card holder language in ISO-639-1 two-letter language code.
enExample: enCard holder country in ISO-3166-1 alpha-2 two-letter country code.
USAccepted
Bad request - Not Retryable
Unauthorized - Not Retryable
Too Many Requests - Retryable
Internal Server Error - Not Retryable
Service Unavailable - Retryable
Sin contenido
Technical identifier pre-defined at on-boarding that identifies the API
consumer.
Format shall be the string 'APIKEY' followed by a space and the
api key value.
Example: APIKEY c03f88fe-01ba-11e8-ba89-0ed5f89f718b
Technical identifier used for troubleshooting.
It helps on customer support when needed.
Each API request must be identified with a unique correlation Id.
It correlates the response and the request and eventually a notification if any.
Identifier of the merchant provided by Thales at on-boarding.
The user and card information encrypted in a JWE structure (see security section in the documentation).
Once decrypted, the JWE plaintext contains the following JSON object:
| JSON field parameter name | description | MOC | Length |
|---|---|---|---|
| fpan | The funding pan to tokenize. | M | Up to 19 |
| exp | The expiry date in the format MMYY. | M | 4 |
Example: {"fpan":"5123456789012345", "exp":"0822"}
Created
Bad request - Not Retryable
Unauthorized - Not Retryable
Too Many Requests - Retryable
Internal Server Error - Not Retryable
Service Unavailable - Retryable
Technical identifier pre-defined at on-boarding that identifies the API
consumer.
Format shall be the string 'APIKEY' followed by a space and the
api key value.
Example: APIKEY c03f88fe-01ba-11e8-ba89-0ed5f89f718b
Technical identifier used for troubleshooting.
It helps on customer support when needed.
Each API request must be identified with a unique correlation Id.
It correlates the response and the request and eventually a notification if any.
Identifier of the merchant provided by Thales at on-boarding.
The push provisioning payload provided by the Issuer to the merchant application.
For Mastercard, it corresponds to the 'pushAccountReceipt'.
For Visa, it corresponds to the 'encPaymentInstrument'.
The card primary scheme.
MASTERCARDValores posibles: The user information encrypted in a JWE structure (see security section in the documentation).
Once decrypted, the JWE plaintext contains the following JSON object:
| JSON field parameter name | description | MOC | Length |
|---|---|---|---|
| accountId | The card holder account identifier defined by the Merchant. | O | 24 |
| The card holder email. | O | 128 |
Example: {"accountId:"johndoe", "email":"[email protected]"}
Card holder language in ISO-639-1 two-letter language code.
enExample: enCard holder country in ISO-3166-1 alpha-2 two-letter country code.
USCreated
Bad request - Not Retryable
Unauthorized - Not Retryable
Too Many Requests - Retryable
Internal Server Error - Not Retryable
Service Unavailable - Retryable
The token identifier.
Technical identifier pre-defined at on-boarding that identifies the API
consumer.
Format shall be the string 'APIKEY' followed by a space and the
api key value.
Example: APIKEY c03f88fe-01ba-11e8-ba89-0ed5f89f718b
Technical identifier used for troubleshooting.
It helps on customer support when needed.
Each API request must be identified with a unique correlation Id.
It correlates the response and the request and eventually a notification if any.
OK
Identifier of the merchant provided by Thales at on-boarding.
The card bin returned by the scheme, just available for VISA and Mastercard SCOF.
453421The card last digits.
2366The card expiry date in format MMYY.
0420Token state.
PCI token state can only be 'ACTIVE' or 'DELETED'.
ACTIVEValores posibles: The token last digits.
5589The token expiry date in format MMYY. This information can be missing. It is intended for display only at this step.
Rely on token expiry date in create transaction response for storage.
1022Payment Account Reference returned by the Scheme TSP.
5001a9f027e5629d11e3949a0800aSpecific to Visa. Another token identifier that shall be used only with Visa Cloud Token Framework.
The list of device identifiers bound to the token.
Token creation timestamp compliant with ISO 8601.
2025-11-10T09:08:24.479ZToken last update timestamp compliant with ISO 8601. Provided only in case the token was updated after its creation.
2025-11-13T11:012:41.165ZBad request - Not Retryable
Unauthorized - Not Retryable
Not Found - Not Retryable
Too Many Requests - Retryable
Internal Server Error - Not Retryable
Service Unavailable - Retryable
The token identifier.
Technical identifier pre-defined at on-boarding that identifies the API
consumer.
Format shall be the string 'APIKEY' followed by a space and the
api key value.
Example: APIKEY c03f88fe-01ba-11e8-ba89-0ed5f89f718b
Technical identifier used for troubleshooting.
It helps on customer support when needed.
Each API request must be identified with a unique correlation Id.
It correlates the response and the request and eventually a notification if any.
No Content
Bad request - Not Retryable
Unauthorized - Not Retryable
Not Found - Not Retryable
Too Many Requests - Retryable
Internal Server Error - Not Retryable
Service Unavailable - Retryable
Sin contenido
The unique asset identifier.
Technical identifier pre-defined at on-boarding that identifies the API
consumer.
Format shall be the string 'APIKEY' followed by a space and the
api key value.
Example: APIKEY c03f88fe-01ba-11e8-ba89-0ed5f89f718b
OK
The media type of the asset.
The asset encoded in base64.
The asset height specified in pixels.
The asset width specified in pixels.
Bad request - Not Retryable
Unauthorized - Not Retryable
Not Found - Not Retryable
Too Many Requests - Retryable
Internal Server Error - Not Retryable
Service Unavailable - Retryable
Última actualización
¿Te fue útil?