Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Push provisioning to xPay Wallets

End users can add eligible cards to xPay Wallets from the issuer application. Supported wallets include Apple Pay, Google Pay, and Samsung Pay.

The issuer application verifies the end user’s identity before activating the card.

Step 1: Decide whether to show Add to Wallet

The issuer application uses the Push Provisioning SDK to check whether:

  • The target xPay Wallet is supported on the device.

  • A token already exists for the card on the device.

Based on the result, show or hide Add to Wallet.

Call getToken to decide whether to show Add to Wallet. Pass the last 4 digits of the PAN.

The SDK checks whether the card is already present in the wallet. Use the response to decide whether to display Add to Wallet.

Show or hide Add to Wallet based on card presence.

The Push Provisioning SDK requires encrypted card data to verify with the issuer backend. See Card data encryption (PKCS#7 format).

Step 2: Provision a card

After the end user taps Add to Wallet, start push provisioning. Call the SDK provision method.

Create an authorizationCode (JWT) for this flow. See Authorization code (JWT format).

Provisioning flow with the Push Provisioning SDK.

Last updated

Was this helpful?