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.

Response Fields

A successful response for the Get Card Payment Tokens endpoint will return a 200 response.

FieldDescription
idUnique payment token identifier for the Mastercard Digital Enablement Services (MDES) or Visa Digital Enablement Program (VDEP) card.
walletIdUnique identifier of the wallet provider this payment token is linked to (e.g., APPLE, ANDROID, SAMSUNG).
walletProviderName of the wallet provider this payment token is linked to (e.g., Apple, Android, Samsung).
tokenPANPThe funding PAN (card PAN), with only the last four digits shown.
statusesObject that contains different statuses for the payment token.
tokenisedStatusTokenised status of this payment token: U = unknown; 0 = not tokenised; 1=tokenised.
authorisationStatusStatus 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

Note: this is not the same as a transaction authorisation.
authorisationDecisionFinal tokenisation decision:

U = unknown

0 = approve digitisation request

A = approve digitisation request (with additional authentication).
transactionStatusStatus 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
gpsStatusInfoDevice 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
tokenisedDateTokenised date. Format YYYY-MM-DD.
expiryDateToken expiry date. Format YYYY-MM-DD.
tokenTypeThe payment token type. For example: C (Contactless Device PAN), CF (Card on File PAN).
deviceTypeThe type of technology linked to the token. For example: F (Fob or key-fob), M (Mobile phone), P (Personal computer).
deviceNameName of the cardholder assigned to the device in the wallet.
merchantNameThe merchant name (name of the token requester). For example: Amazon, Apple Pay, Google Pay.