Skip to content

What issuer processor handles digital wallet provisioning during migration?

During a migration, responsibility for digital wallet provisioning shifts to the new issuer processor. Providers such as Enfuce are designed to take on this role.

In simple terms, the issuer processor is the technical layer that connects your card programme to digital wallets like Apple Pay, Google Pay, and Samsung Pay. It manages tokenisation, wallet eligibility, and the APIs that allow cards to be added to mobile devices.

When switching issuer processors, this role becomes more complex. You are not only moving card data, you are also transitioning the token infrastructure that supports every wallet transaction.

What is digital wallet provisioning?

Digital wallet provisioning is the process of adding a card to a mobile wallet and enabling it for payments using tokenisation.

Instead of storing the actual card number, wallets store a token issued by card schemes such as Visa and Mastercard.

Key components include:

  • Tokenisation via Visa Token Service (VTS) and Mastercard Digital Enablement Service (MDES)
  • Wallet integrations with Apple, Google and Samsung
  • Authentication flows for adding cards securely
  • Token lifecycle management

Why wallet provisioning is critical during migration

Wallet provisioning matters because if token relationships are disrupted during migration, customers may lose access to their saved cards in wallets and experience failed payments.

From a technical perspective:

  • Wallets store tokens, not card numbers
  • Migration success depends on preserving token-to-card relationships

From a business perspective:

  • Wallet disruption leads to immediate customer friction
  • Failed payments can damage trust and increase support costs

Digital wallet provisioning therefore enables issuers to preserve a seamless customer payment experience while transitioning the underlying token infrastructure.

Who manages provisioning during a card migration?

Responsibility for digital wallet provisioning shifts throughout the migration lifecycle.

Before cutover

  • The legacy processor manages existing tokens and wallet activity
  • All provisioning and token lifecycle events remain unchanged

During the transition or dual run

  • Both processors may operate in parallel
  • Each processor handles provisioning for the BINs it controls

After cutover

The new issuer processor becomes the system of record and takes full ownership of:

  • Token provisioning
  • Wallet integrations
  • Token lifecycle management
  • Transaction routing
  • Maintaining wallet and scheme metadata configurations

This includes managing push provisioning APIs, keeping scheme profile updates up to date, and ensuring cards meet wallet eligibility criteria.

How does digital wallet provisioning work during migration?

There are two main approaches to handling wallet provisioning during a migration.

1. Token migration (preferred approach)

This method preserves the existing customer experience.

  • Existing tokens, along with their corresponding statuses, are mapped and migrated to the new processor
  • The link between token and underlying card is maintained
  • Customers continue using their wallets without interruption

This requires coordination between:

  • Outgoing and incoming issuer processors
  • Card schemes such as Visa and Mastercard
  • Token service providers (VTS and MDES)
  • Wallet providers such as Apple, Google, and Samsung

When done correctly, the migration should have no visible impact on the end user.

2. Re-provisioning (fallback approach)

If token migration is not possible:

  • Existing tokens are deactivated
  • Customers must re-add their cards to wallets

To reduce friction, advanced issuer processors support:

  • In-app push provisioning
  • Streamlined authentication flows
  • Faster card re-enrolment across digital wallets
  • Multiple wallet provisioning entry points across apps, wallets, and devices

While effective, this approach can still introduce additional customer friction and potential drop-off compared to token migration.

How Enfuce handles digital wallet provisioning during migration

Enfuce is an advanced issuer processor that approaches wallet provisioning as a key part of the overall migration process. We deliver this through a dedicated migration team working closely with the issuer’s product, engineering, and operations teams.

1. Discovery and token mapping

  • Identify all relationships between cards, tokens, devices, and wallets
  • Support accurate mapping between legacy and new systems

2. Token migration strategy

  • Prioritise token migration where supported
  • Fall back to re-provisioning only when necessary
  • Enable push provisioning to minimise disruption

3. Sandbox testing

  • Full API access for testing provisioning flows
  • Simulated environments for:
    • Tokenisation
    • Authentication
    • Transaction authorisation
  • Ensures real-world readiness before go-live

4. Go-live and routing

  • Update token routing to the new processor
  • Ensure wallet transactions are authorised correctly
  • Maintain a consistent experience for end users

5. Post-migration monitoring

  • Track provisioning success rates
  • Monitor wallet transaction performance
  • Ensure compliance with scheme and wallet requirements

The bottom line

During a migration, the new issuer processor ultimately becomes responsible for digital wallet provisioning.

Providers like Enfuce are designed to take on this role through:

  • Proven token migration strategies
  • Robust testing environments
  • Close coordination with Visa, Mastercard, and wallet providers
  • Dedicated migration teams that work alongside your internal stakeholders

When executed correctly, the migration can take place with minimal visible impact to the customer while giving issuers full control, operational confidence, and a future-ready platform.

Frequently asked questions

What happens to Apple Pay or Google Pay during a card migration?

If token migration is used, cards remain active in the wallet and continue to work as normal. If not, customers may need to re-add their cards.

Can customers keep using their wallets during migration?

In most cases, yes, if the token to card relationship is preserved. This is why token migration is the preferred approach.

Who is responsible for wallet integrations after migration?

The new issuer processor becomes fully responsible for wallet integrations, token lifecycle management, and provisioning APIs after cutover.

Why do some migrations require re-provisioning?

Re-provisioning is required when token migration is not supported due to technical or scheme limitations. In these cases, customers must re-authenticate and add their cards again.