Digital wallets allow cardholders to store payment credentials securely and make contactless, in-app, and online payments without using a physical card.

Passport-issued debit cards can be added to supported wallets, enabling:

Faster checkout experiences
Secure, tokenized transactions
Improved user engagement and activation

Wallet provisioning is supported via API-based integrations, ensuring that sensitive card data is never exposed during the process.

Supported Wallets

Apple Pay
Google Pay
Samsung Pay

Provisioning Methods

Cards can be added to digital wallets using two approaches:

Method	Experience	Integration Effort
Manual Provisioning	Cardholder enters card details in wallet app	No integration required
Push Provisioning	Add card directly from your app (one-tap experience)	Requires API + wallet integration

Push provisioning is recommended for a frictionless user experience and higher activation rates.

How Push Provisioning Works

The push provisioning flow enables secure, tokenized card addition directly from your application.

Push provisioning follows a standard, network-defined flow used across digital wallet providers (such as Apple Pay, Google Pay, and Samsung Pay).

The steps below represent the typical industry process for securely provisioning a card to a digital wallet.

Cardholder taps “Add to Wallet” in your app
Create card using card issuance API
Receive card identifier
Call provisioning API
Receive encrypted card payload
Forward payload to wallet provider (SDK/API)
Wallet requests token from card network
Network generates device-specific token
Wallet stores token → card is ready for use

Provision a Card

Use the POST /v1/customer/id/{id}/issuance/card/id/{id}/provision API to provision a card to a digital wallet.

Key Parameters:

Field	Description
`walletProvider`	Target wallet (`APPLE_PAY`, `GOOGLE_PAY`, `SAMSUNG_PAY`)
`cert1`, `cert2`	Apple Pay certificates (required for Apple Pay)
`nonce`, `nonceSignature`	Apple-provided security parameters
`walletAccountId`	Wallet account ID (Google / Samsung)
`deviceId`	Device identifier from wallet provider

When a card is provisioned:

A device-specific network token is generated
The original card number is never exposed
Each wallet-device combination gets a unique token

This ensures:

Reduced fraud risk
Secure transactions across all channels

Operational Considerations

Card Replacement & Wallet Sync: When a card is replaced:

Wallets do not automatically update card details
Existing tokens may become invalid
Transactions may be declined

To restore functionality:

Re-provision the card using push provisioning, or
Manually re-add the card in the wallet