- Push provisioning starts from the customer’s application or digital channel.
- Manual provisioning starts from the wallet application.
Push Provisioning
Push Provisioning
Push provisioning, also known as in-app provisioning, is initiated from your application. In this flow, a cardholder selects a card in the customer’s application and chooses to add it to a digital wallet.
1
First Step
The cardholder opens your application and selects the card they want to add to a digital wallet.
2
Second Step
Your system sends a request to the Enfuce Wallet API to retrieve wallet provisioning data.
3
Third Step
Enfuce generates and returns the provisioning data that the wallet provider requires.
4
Fourth Step
You transmit the provisioning data to the wallet provider using the wallet provider’s Software Development Kit (SDK).
5
Fifth Step
The wallet provider forwards the request to the Scheme’s tokenisation service, such as Mastercard Digital Enablement Service (MDES) or Visa Token Service (VTS).
6
Sixth Step
Depending on Scheme requirements, the wallet provider requirements, and your authentication implementation, the cardholder may need to complete additional authentication before the token is activated.
7
Seventh Step
The Scheme creates a payment token and links it to the underlying card.
8
Eighth Step
The wallet provider provisions the token to the device, allowing the cardholder to make payments using the digital wallet.
Manual Provisioning
Manual Provisioning
Manual provisioning initiates from a specific wallet application, rather than your application. In this flow, the cardholder adds the card directly in the wallet application — enters the card details manually or scans the physical card.
1
First Step
The cardholder opens the digital wallet application.
2
Second Step
The cardholder enters the card details manually or scans the physical card.
3
Third Step
The wallet provider sends a provisioning request to the Scheme’s tokenisation service, such as MDES or VTS.
4
Fourth Step
The Scheme exchanges the information required for token provisioning with Enfuce, including card and token-related validation data.
5
Fifth Step
Depending on the Scheme requirements, the wallet provider requirements, and your authentication implementation, the cardholder may need to complete additional authentication before the token is activated.
6
Sixth Step
Once all requirements are met, the Scheme creates a payment token and links it to the underlying card.
7
Seventh Step
The wallet provider provisions the token to the device, allowing the cardholder to make payments using the digital wallet.

