Get Card Payment Token Details - Field Descriptions
The following page details each of the fields received in the response when using the Get Card Payment Token Details endpoint.
Response Fields
A successful response for the Get Card Payment Token Details endpoint will return a 200 response.
| Field | Description |
|---|---|
| id | The unique payment token identifier. |
| walletId | Name of the wallet provider this payment token uses (e.g., APPLE, ANDROID, SAMSUNG). |
| walletProvider | The name of the wallet provider. For example Apple or Google. |
| tokenPAN | PAN token for the card linked to the MDES or VTS card. |
| statuses | Object that contains different statuses for the payment token. |
| tokenisedStatus | Tokenised status of this payment token: U = unknown; 0 = not tokenised; 1=tokenised. |
| authorisationStatus | Status of the authorisation to digitise this payment token: U = unknown 0 = approve digitisation request A = approve digitisation request (with additional authentication) 1 = decline digitisation request
|
| authorisationDecision | Final tokenisation decision: U = unknown 0 = approve digitisation request A = approve digitisation request (with additional authentication). |
| transactionStatus | Status of the payment token as received from the payment token creator (normally Visa or Mastercard). After tokenisation, this is not changed by Thredd. A = Active D = Deleted (once in this status, it is normally never changed) I = Inactive N = Not Tokenised P = Pending S = Suspended U = Unknown X = Deactivated |
| gpsStatusInfo | Device status on the Thredd system. Options include: A = Active D = Deleted (once in this status, it is normally never changed) I = Inactive N = Not Tokenised P = Pending S = Suspended U = Unknown X = Deactivated |
| statuses | End of the statuses object.. |
| tokenisedDate | Date and time when tokenised, in the format: yyyy-mm-ddhhmmss. |
| expiryDate | Expiry date of the payment token. |
| tokenType | Payment token type. |
| deviceType | The type of device enabled for tokenised payments for this token. |
| deviceName | Name of the cardholder assigned to the device in the wallet. |
| merchantName | The name of the merchant that created the token. |
| creatorTokenReference | The token creator's unique reference for this payment token. (Mastercard Token Unique Reference (TUR) and Visa Token reference ID.) |
| cardUsageGroup | The card usage group the token is associated with. |
| paymentTokenUsageGroup | The payment token usage group the token is associated with. |
| walletAccountScore | Risk score for the account, received from the wallet provider during digitisation: 1 = highest risk; 2 = higher risk; 3 = neutral; 4 = lower risk; 5 = least risk |
| walletDeviceScore | Risk score for the device received from the wallet provider during digitisation: 1 = highest risk; 2 = higher risk; 3 = neutral; 4 = lower risk; 5 = least risk |
| walletReasons | Wallet service provider tokenization recommendation reason codes. For details, see Wallet Tokenisation Reason Codes |
| transactionID | The unique identifier for the transaction. |
| responseCode | The action code for the response. |
| transactionDate | The date and time of the transaction. |
| cardAcceptorNameLocation | The location of the card acceptor, which can be a merchant or an ATM where the transaction occurred. |
| bnReference | The network reference. |
| mtid | The Message Type Identifier (MTID) for the transaction. |
| ehiRequestTime | The date and time the EHI received the request. |
| ehiResponseTime | The date and time the EHI responded to the request. |
| activationCode | Activation code to be sent directly to the cardholder to activate this payment token. |
| activationMethod | Which activation method was used: 0 = none; 1 = SMS to mobile phone; 2 = email; 3 = cardholder called an automated call centre; 4 = cardholder called a human call centre; 5 = website; 6 = mobile application; 7 = voice phone call |
| activationStatus | The payment token's activation status: Status is 'R' when Reason code = 00 |