Get Card Payment Tokens - Field Descriptions
The following page details each of the fields received in the response when using the Get Card Payment Tokens endpoint, sometimes referred to as the Get List of Card Payment Tokens endpoint.
Response Fields
The following section describes the fields returned by the endpoint.
A successful request returns an HTTP 200 response.
| Field | Description |
|---|---|
| id | Unique payment token identifier for the Mastercard Digital Enablement Services (MDES) or Visa Digital Enablement Program (VDEP) card. |
| walletId | Unique identifier of the wallet provider linked to the payment token. For example: APPLE, ANDROID, or SAMSUNG. |
| walletProvider | Name of the wallet provider linked to the payment token. For example: Apple, Android, or Samsung. |
| tokenPAN | Funding PAN (card PAN), with only the last four digits shown. |
| statuses | Object containing the statuses associated with the payment token. |
| statuses.tokenisedStatus | Tokenisation status of the payment token. The object contains a Example codes include: U = Unknown 0 = Not tokenised 1 = Tokenised |
| statuses.authorisationStatus | Status of the authorisation to digitise the payment token. The object contains a Example codes include: U = Unknown 0 = Approve digitisation request A = Approve digitisation request with additional authentication 1 = Decline digitisation request Note: This is not the same as a transaction authorisation. |
| statuses.authorisationDecision | Final tokenisation decision. The object contains a Example codes include: U = Unknown 0 = Approve digitisation request A = Approve digitisation request with additional authentication |
| statuses.transactionStatus | Status of the payment token as received from the payment token creator, normally Visa or Mastercard. After tokenisation, this status is not changed by Thredd. The object contains a Example codes include: A = Active D = Deleted I = Inactive N = Not Tokenised P = Pending S = Suspended U = Unknown X = Deactivated |
| statuses.gpsStatusInfo | Status of the payment token on the Thredd system. The object contains a Example codes include: A = Active D = Deleted I = Inactive N = Not Tokenised P = Pending S = Suspended U = Unknown X = Deactivated |
| tokenisedDate | Date on which the payment token was tokenised. Format: YYYY-MM-DD. |
| expiryDate | Expiry date of the payment token. Format: YYYY-MM-DD. |
| tokenType | Type of payment token. For example: C (Contactless Device PAN) or CF (Card on File PAN). |
| deviceType | Type of device or technology linked to the token. For example: F (Fob or key-fob), M (Mobile phone), or P (Personal computer). |
| deviceName | Name assigned to the device by the cardholder in the wallet. |
| activationCode | Activation code associated with the payment token. |
| threddDecisionAt | Date and time at which Thredd made the decision associated with the payment token. |
| threddDecision | Thredd decision associated with the payment token. |
Updated 15 days ago