Your cardholders can add cards to digital wallets such as Apple Pay and Google Pay using standard text entry or automated push provisioning.
All cards issued through an Instant Issuance card program have support for digital wallets enabled immediately.
If you have an Enterprise card program, your card program must be configured to support digital wallets. During the configuration process Apto works with the issuing bank, the card networks, and the relevant app store to run checks and gain approval for cards to work with each kind of digital wallet.
The approval process includes administrative and operational checks. An example of an administrative check is confirming that the cardholder agreement shown in the app, and card design displayed in the wallet’s UI, adhere to standards. An example of an operation check is verifying that information is correctly transmitted between the digital wallet and the card networks.
Apto takes care of the entire process, but it takes some time to exchange paperwork and receive the necessary approvals. We recommend beginning this process as soon as possible during your implementation.
If your card program is approved to use digital wallets, your cardholders can enter their card details into any mobile wallet. Instant Issuance programs have digital wallet support by default, so cardholders within these programs can enter their payment card details without additional configuration.
This table explains how each feature relates to the main card program types.
|Instant Issuance card program||Enterprise card program|
|Digital wallets||Enabled immediately||Require configuration|
|Text entry||Allowed immediately||Allowed after configuration is complete|
Thorough testing ensures that cards can be added to a cardholder’s digital wallet, the Terms and Conditions are displayed correctly, and the necessary One-Time Passcode (OTP) SMS messages are delivered to the cardholder.
Out of the box, digital wallets use the default card design shown in the images above. To ensure that cardholders see your custom card art in their digital wallets, we highly recommend that you finalize digital wallet card art prior to program launch.
Because digital wallets involve many parties—such as a merchant, Mastercard, and Apple, Google, or Samsung—controlled testing must be performed in a production environment.
Apto completes rigorous testing, but we recommend that you also perform your own thorough testing prior to launch.
When a cardholder adds a card to (or removes a card from) a digital wallet, Mastercard sends Apto a series of transactions. The transactions do the following:
- Exchange the token information
- Inform Apto an OTP verification is made
- Inform Apto a card was approved to be added to a digital wallet
In turn, we send you webhook
These transactions do not come in the same order each time. You must account for the various orders in which the transactions may arrive. Additionally, not all three transactions are always performed.
Digital wallet provisioning webhooks contain
"type": "NON_FINANCIAL". A common identifier is sent in the
transaction_update webhook for all related digital wallet transactions.
Below are examples of the webhooks that are generated:
Card was approved to be added
Token exchange and removal (At this time, we do not offer the ability to distinguish between an add and a removal)
Digital wallet transactions appear the same as any other transaction performed with the card. At this time, Apto does not offer the ability to identify whether the transaction was performed using a digital wallet. This feature is currently in our roadmap.