Token Provisioning and Management API
Unique identifier used to trace function calls across systems
Unique Identifier of Issuer
ISSUER1234A unique identifier of the issuer that aims to identify the funding card.
This parameter is provided by the TSH unless it's not connected to Issuer.
This identifier might be updated by Issuer on card replacement/renewal flows.
A unique identifier of the wallet provider that aims to identify the funding card.
This parameter is provided by the TSH.
For ApplePay, it corresponds to the FPANID.
This identifier remains constant even on card replacement/renewal flows.
TSH sends card information as JSON encrypted using the PKCS#7 encryption scheme defined in RFC 2315/5652 using following encryption parameters:
- The content encryption algorithm used is AES256/CBC/PKCS7Padding using a randomly generated AES key.
- The key encryption algorithm is either RSAES-PKCS1-v1_5 (RSA/NONE/PKCS1Padding) or RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256), using the certificate provided during onboarding.
The key encryption algorithm is defined during onboarding and is by default (if ommitted) the RSA/NONE/PKCS1Padding for legacy purpose.
It is recommended to configure RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256) for new TSPs. - The encryption result is then encoded using base64.
- The public key length in the certificate can be 2048-bit or 4096-bit.
Once deciphered, the card info contains the following information:
| JSON field parameter name | description | MOC | Length |
|---|---|---|---|
| fpan | The funding pan to digitize | M | Up to 19 |
| exp | The expiry date in the format MMYY | O | 4 |
| cvv | Depending of the OEM, this value is provided or not | O | 3 or 4 |
| additionalCardInfos | Optional JSON Open format, in order to add additional card info - project dependent | O | Up to 8177 |
Note: If not provided, the TSP must rely on the walletCardRefId provided to find the funding card to digitize from its token vault.
Identifier of the key used to encrypt cipheredCardInfo.
Provided by TSP to Thales during onboarding.
ID of the token product (Identify token domain).
As the token products are mapped to Issuer card products, the values shall be defined at the begining of the project with the TSP.
ID of the token requestor in the format expected by the TSP
Token storage unique identifier (also known as deviceId or applicationId).
Indicates the storage in which the token has been digitized.
For ApplePay, it corresponds to the device SEID.
The tokenId provided in case the Wallet Provider wants to re-use an existing token.
This is applicable for Apple Pay only and needs to have an agreement on this process at the beginning of a project.
Initial state of the token when created.
Default value is SUSPENDED
SUSPENDEDPossible values: createToken response payload
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter.
Possible error codes are 111, 112, 113, 115, 163, 164, 166, 167, 911, 921
Internal Server Error Retry possible
Service Unavailable Retry possible
Identifier of the token to update
Unique identifier used to trace function calls across systems
Unique Identifier of Issuer
ISSUER1234TSH sends new card information as JSON encrypted using the PKCS#7 encryption scheme defined in RFC 2315/5652 using following encryption parameters:
- The content encryption algorithm used is AES256/CBC/PKCS7Padding using a randomly generated AES key.
- The key encryption algorithm is either RSAES-PKCS1-v1_5 (RSA/NONE/PKCS1Padding) or RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256), using the certificate provided during onboarding.
The key encryption algorithm is defined during onboarding and is by default (if ommitted) the RSA/NONE/PKCS1Padding for legacy purpose.
It is recommended to configure RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256) for new TSPs. - The encryption result is then encoded using base64.
- The public key length in the certificate can be 2048-bit or 4096-bit.
Once deciphered, the card info contains the following information:
| JSON field parameter name | description | MOC | Length |
|---|---|---|---|
| newFpan | The new funding pan value to update | O | Up to 19 |
| newExp | The new expiry date in the format MMYY | O | 4 |
| newAdditionalCardInfos | Optional JSON Open format, in order add/update/delete additional card info - project dependent | O | Up to 8177 |
Note: At least one of the three JSON fields needs to be provided.
Identifier of the key used to encrypt newCipheredCardInfo.
Provided by TSP to Thales during onboarding.
New unique identifier of the issuer that aims to identify the funding card.
successful
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter.
Possible error codes are 111, 112, 113, 119, 163, 166, 432, 911, 921
Internal Server Error Retry possible
Service Unavailable Retry possible
No content
Identifier of the token to update
Unique identifier used to trace function calls across systems
Unique Identifier of Issuer
ISSUER1234state of the token
The reason of the state update
Possible values are:
| reason code | description |
|---|---|
| 11001 | Activation from user interaction |
| 21001 | Activation initiated by the issuer |
| 21002 | Deletion initiated by the issuer |
| 11002 | Deletion initiated by the user |
| 21003 | Suspension initiated by the issuer |
| 11003 | Suspension initiated by the user |
| 21004 | Resumption initiated by the issuer |
| 11004 | Resumption initiated by the user |
successful
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter.
Possible error codes are 111, 112, 113, 119, 432, 911, 921
Internal Server Error Retry possible
Service Unavailable Retry possible
No content
Identifier of the token to update
Unique identifier used to trace function calls across systems
Unique Identifier of Issuer
ISSUER1234Value of the application transaction counter that will be used in the next payment transaction. The ATC is encoded as an hexa string on 4 digits.
Value of the replenishment counter for the last replenishment.
Transaction records for the last transactions as specified by the payment scheme. The transaction records data is encoded in base 64.
Signature of the transaction records computed according to the scheme specifications and encoded in hexa.
requestReplenishment response payload
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter.
Possible error codes are 111, 112, 119, 432, 911, 921
Internal Server Error Retry possible
Service Unavailable Retry possible
Identifier of the token to update
Unique identifier used to trace function calls across systems
Unique Identifier of Issuer
ISSUER1234Value of the replenishment counter for the last replenishment.
Payment credential diversifier:
- For an SUK, this is an ATC which is a string of 4 hexa digits.
- For an LUK, this is an "YHHHHCC" Visa CBP diversifier which is a string of 7 digits.
successful
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter.
Possible error codes are 111, 112, 119, 432, 911, 921
Internal Server Error Retry possible
Service Unavailable Retry possible
No content
Identifier of the token to update
Unique identifier used to trace function calls across systems
Unique Identifier of Issuer
ISSUER1234successful
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter.
Possible error codes are 111, 112, 113, 119, 911, 921
Internal Server Error Retry possible
Service Unavailable Retry possible
No content
Unique identifier of the request
successful
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter.
Possible error codes are 111, 112, 911, 921
Internal Server Error Retry possible
Service Unavailable Retry possible
No content
Identifier of the token to update
Unique identifier used to trace function calls across systems
Unique Identifier of Issuer
ISSUER1234successful
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter.
Possible error codes are 111, 112, 113, 119, 321, 432, 911, 921
Internal Server Error Retry possible
Service Unavailable Retry possible
No content
Identifier of the token to update
Unique identifier used to trace function calls across systems
Unique Identifier of Issuer
ISSUER1234Only for ApplePay. Applet version as provided by the Wallet Provider.
1.22successful
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter.
Possible error codes are 111, 112, 119, 911, 921
Internal Server Error Retry possible
Service Unavailable Retry possible
No content
Unique identifier used to trace function calls across systems
Unique Identifier of Issuer
ISSUER1234TSH sends card information as JSON encrypted using the PKCS#7 encryption scheme defined in RFC 2315/5652 using following encryption parameters:
- The content encryption algorithm used is AES256/CBC/PKCS7Padding using a randomly generated AES key.
- The key encryption algorithm is either RSAES-PKCS1-v1_5 (RSA/NONE/PKCS1Padding) or RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256), using the certificate provided during onboarding.
The key encryption algorithm is defined during onboarding and is by default (if ommitted) the RSA/NONE/PKCS1Padding for legacy purpose.
It is recommended to configure RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256) for new TSPs. - The encryption result is then encoded using base64.
- The public key length in the certificate can be 2048-bit or 4096-bit.
Once deciphered, the card info contains the following information:
| JSON field parameter name | description | MOC | Length |
|---|---|---|---|
| fpan | The funding pan | M | Up to 19 |
TSH sends token information as JSON encrypted using the PKCS#7 encryption scheme defined in RFC 2315/5652 using following encryption parameters:
- The content encryption algorithm used is AES256/CBC/PKCS7Padding using a randomly generated AES key.
- The key encryption algorithm is either RSAES-PKCS1-v1_5 (RSA/NONE/PKCS1Padding) or RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256), using the certificate provided during onboarding.
The key encryption algorithm is defined during onboarding and is by default (if ommitted) the RSA/NONE/PKCS1Padding for legacy purpose.
It is recommended to configure RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256) for new TSPs. - The encryption result is then encoded using base64.
- The public key length in the certificate can be 2048-bit or 4096-bit.
Once deciphered, the card info contains the following information:
| JSON field parameter name | description | MOC | Length |
|---|---|---|---|
| dpan | The token PAN | M | Up to 19 |
A unique identifier of the issuer that aims to identify the funding card.
This parameter is provided by the TSH unless it's not connected to Issuer.
This identifier might be updated by Issuer on card replacement/renewal flows.
Identifier of the key used to encrypt cipheredCardInfo.
Provided by TSP to Thales during onboarding.
listTokens response payload
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter.
Possible error codes are 111, 112, 113, 166, 911, 921
Identifier of the token to update
Unique identifier used to trace function calls across systems
Unique Identifier of Issuer
ISSUER1234replenishToken response payload
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter.
Possible error codes are 111, 112, 113, 119, 321, 432, 911, 921
Internal Server Error Retry possible
Service Unavailable Retry possible
Identifier of the token to update
Unique identifier used to trace function calls across systems
Unique Identifier of Issuer
ISSUER1234successful
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter.
Possible error codes are 111, 112, 113, 119, 911, 921
Internal Server Error Retry possible
Service Unavailable Retry possible
No content
Last updated
Was this helpful?