Inbound (from issuer)
Unique identifier of a give session (enrolment session or Life Cycle Management session), used to link inbound and outbound requests of the same session together
Unique identifier used to identify the issuer
The unique identifier of the funding card.
This value is generated and manage by the issuer.
This value can be updated in case of funding PAN replacement by the issuer.
getCardInfo response payload
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
Unique identifier of a give session (enrolment session or Life Cycle Management session), used to link inbound and outbound requests of the same session together
Unique identifier used to identify the issuer
The unique identifier of the funding card.
This value is generated and manage by the issuer.
This value can be updated in case of funding PAN replacement by the issuer.
Identifier of the virtual card to update
getTokenInfo response payload
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
Unique identifier of a give session (enrolment session or Life Cycle Management session), used to link inbound and outbound requests of the same session together
Unique identifier used to identify the issuer
The unique identifier of the funding card.
This value is generated and manage by the issuer.
This value can be updated in case of funding PAN replacement by the issuer.
New issuerCardRefId to be updated, provided only if the issuerCardRefId change after a PAN,exp or productId replacement.
Note, the newIssuerCardRefId is not mandatory and it is preferable to keep the same issuerCardRefId after updateCard
This field has been added to the API for issuers that are not able to manage the same identifier following a PAN/exp date update.
Old and new FPAN details (for example in case of card renewal)
This value is 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
- The key encryption algorithm is RSA/NONE/OAEPWithSHA256AndMGF1Padding (with MGF1 using SHA-256) using the TSH certificate provided during onboarding.
- The encryption result shall be provided as hexadecimal string.
The format of the data is:
{
"oldFPAN": "[0-9]{16,19}",
"oldExpDate": "MMYY",
"oldPSN": "[a-fA-F0-9]{2}",
"newFPAN": "[0-9]{16,19}",
"newExpDate": "MMYY",
"newPSN": "[a-fA-F0-9]{2}"
}
NOTE1: all fields are MANDATORY...
NOTE2: oldPSN and newPSN apply ONLY to AMEX
^[a-fA-F0-9]+Identifier of the key used to encrypt fpanDetails.
Provided by Thales to Issuer during onboarding.
New ProductId to be used for digital card (for example: product upgrade).
This field is mutually exclusive to "fpanDetails" AND "metadata".
NOTE:
- UPI: not applicable.
- Mastercard: the supported range is 0-10
Successful (no response body)
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
No content
Unique identifier of a give session (enrolment session or Life Cycle Management session), used to link inbound and outbound requests of the same session together
Unique identifier used to identify the issuer
The unique identifier of the funding card state to update.
If provided, it update the state of all active or suspended tokens that belongs to the funding card identified by issuerCardRefId
mandatory if virtualCardId is not provided
The unique identifier of the virtual card state to update.
mandatory if issuerCardRefId is not provided
reference of the device binding process/link to the Virtual Card.The deviceBindingReference is used only with action UNBIND_DEVICE and APPROVE_DEVICE_BINDING (VTS only. Note that this field corresponds to the deviceIndex)
action to update the state Note: ERASE aims to be use in the context of GDPR compliancy, TSH will take care of erasing everything related to the given card/tokens when receiving this action.
Reason of the token(s) state update
Here is the possible values:
- 11 : User decision
- 21 : Issuer decision
- 31 : Device lost
- 32 : Device stolen
Successful (no response body)
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
No content
Unique identifier of a give session (enrolment session or Life Cycle Management session), used to link inbound and outbound requests of the same session together
Unique identifier used to identify the issuer
Identifier of the virtual card to update
The unique identifier of the funding card.
This value is generated and manage by the issuer.
This value can be updated in case of funding PAN replacement by the issuer.
The value for this language localization code is an IETF Language (https://en.wikipedia.org/wiki/IETF_language_tag) Tag, such as “en-us”. Region Designator should be one of the valid ISO 3166-1 alpha-2 codes, which can be found in this link: http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 Language Designator should use the two-letter ISO 639-1 standard (preferred) or the three-letter ISO 639-2 standard, which can be found in this link : https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
Textual message that must be sent to end user
An optional value provided in case the issuer mobile application support deep link If messageToken is provided, the wallet application will enable the deep link feature for this particular message
Expiration date of the message RFC3339 format.
sendMessage response payload
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
No content
Unique identifier of a give session (enrolment session or Life Cycle Management session), used to link inbound and outbound requests of the same session together
Unique identifier used to identify the issuer
succesfull
No content
Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
Internal Server Error
No content
Last updated
Was this helpful?