Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.

View: get token list

With the Push Provisioning SDK, the issuer application can retrieve the token list for a specific card and the locations where those tokens were requested. The end user can then browse the token list and view:

  • The state of the token (enabled or disabled).

  • Token requestor identifier.

  • Device information, such as device ID, name, and type (when provided by the TSP).

  • Expiry date of the token.

  • Last four digits of the token.

  • Whether the token is on the current device (isOnCurrentDevice) when the issuer application is configured for Google Pay, Samsung Pay, or Apple Pay.

The following figure shows an example user experience that the issuer application can implement:

Example token list user experience.

The Push Provisioning SDK requires card information (PAN and expiry date) to retrieve the token list. The following figure shows an overview of the flow the issuer application must implement:

Get token list flow.

Note

  • Due to payment network limitations, you cannot retrieve the token requestor name and logo in real time.

  • We recommend that the issuer application identifies the top 5–10 token requestor identifiers and hardcodes a merchant- or wallet-facing name and logo.

SDK integration

Step 1: Getting the encrypted card details

To retrieve the token list, the issuer application must provide the encrypted card details to the Push Provisioning SDK.

The issuer backend provides the encrypted card details to the issuer application. The card details use the PKCS#7 format.

Step 2: Getting the token list

After the issuer application retrieves the encrypted card details from the issuer backend, it can request the token list.

The following code snippet shows an example of how to retrieve the token list via the Push Provisioning SDK:

Last updated

Was this helpful?