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 to the digital wallet

Push to the digital wallet

Use this guide to push a card from the issuer application to a digital wallet application using the D1 SDK. Supported wallet applications are Google Pay, Samsung Pay, and Apple Pay.

Call this API when the end user taps Add to wallet and the card digitization state is NOT_DIGITIZED. To retrieve the state, see Get the card digitization state.

Overview

The issuer application calls the D1 SDK addDigitalCardToOEM() API to start the push provisioning flow. The D1 SDK and D1 backend:

  • Validate the end user and card data stored in D1.

  • Prepare the payload required by the wallet application and TSP.

  • Call the wallet application to start Tokenization.

  • Return the result so the issuer application can update the UI.

  • Only call addDigitalCardToOEM() after the D1 SDK returns NOT_DIGITIZED from getCardDigitizationState().

  • For Google Pay on Android, you must implement onActivityResult so that the wallet result is forwarded back to the D1 SDK.

  • Starting June 10, 2024, Google Wallet requires Android 9 or higher.

Flow

Sequence diagram

Prerequisites

  • The end user account and card are registered in D1.

  • The D1 SDK is initialized.

  • The issuer application has called the D1 SDK login API.

High-level sequence for pushing a card to a digital wallet
High-level sequence for pushing a card from the issuer application to a digital wallet using the D1 SDK.

Platform integration

For Android 2.4.0 and later, use D1PushWallet.addDigitalCardToOEM().

For complete D1 SDK details, see the API reference.

Last updated

Was this helpful?