95% of tokens migrated in one week, acquirer switch with zero customer impact
When its acquirer went offline, a high-risk PSP moved 95% of stored card tokens to a new partner in about a week. Recurring payments never stopped and customers never re-entered a card.
Card tokens / Migration to new acquirer
Token migration
Previous acquirer → new acquirerHow a High-Risk PSP Switched Acquirers in One Week, Without Losing a Single Recurring Customer
- Client
- A high-risk PSP working with recurring payments and a large base of stored card data
- Challenge
- Acquirer went offline overnight: stored cards at risk, recurring payments could stop
- Solution
- Payment data migration: token extraction, conversion, re-tokenisation
- Result
- 95% of available tokens migrated in about one week, zero customer action required
The acquirer left. The stored cards were at risk.
The client’s acquiring partner became unavailable, creating an immediate threat to the business.
The problem was not just finding a new acquirer. It was the risk of losing all stored card data, and with it the ability to keep charging returning customers.
Card tokens / Recurring payments
| Card | Next charge | Status |
|---|---|---|
| Visa •••• 1246 | Monthly plan | Cannot charge |
| Mastercard •••• 4410 | Monthly plan | Cannot charge |
| Visa •••• 0387 | Annual plan | Cannot charge |
The challenge was not finding a new acquirer. It was keeping the payment base intact during the switch.
Case study 02- Loss of recurring revenue
- Payment flows coming to a stop
- Customers asked to re-enter cards, many never doing so
Full migration in about a week.
The eComCharge team moved the payment data at the infrastructure level, so customers never had to re-enter their card details.
Card tokens / Migration to new acquirer
Acquirer becomes unavailable
Risk to stored cards and recurring flows.
Data extraction
Tokenised card data retrieved from the previous acquirer.
Token conversion
New tokens generated, compatible with the new acquirer.
Payments resume
Recurring transactions continue, zero customer action.
Not all tokens from the previous acquirer were available for transfer; this depends on what the outgoing provider is able and willing to share. The 95% figure reflects the tokens that were technically accessible.
The PSP kept control of its payment data.
Instead of asking users to re-enter payment details, the PSP retained control over its payment data and moved it across providers. It switched its entire acquiring infrastructure without rebuilding its payment base. Customers never noticed a thing.
Stored cards kept working
The payment base survived the acquirer switch intact.
No gap in recurring
Subscription charges continued without interruption.
Infrastructure level
Migration handled by the platform, not by customers.
Plan for it before you need it.
Payment data migration becomes essential when an acquirer suddenly becomes unavailable or exits the market, when a PSP needs to switch partners for risk, compliance or performance reasons, or when a business relies heavily on stored cards and recurring transactions. It applies both to PSPs already on the platform and to new PSPs migrating from another provider.
- Whether the previous provider and its acquiring partners are able and willing to share tokenised payment data
- Whether the new acquiring partner can accept and process migrated tokens
- The format and compatibility of tokenisation across providers
Each migration is unique and needs coordination between all parties. When these conditions are met, migration significantly reduces switching risk and protects ongoing revenue.
Case study 02High-risk PSP · Recurring payments · Acquirer migration
Migration was handled at the infrastructure level: customers never re-entered their card details, and the PSP retained full control over its payment data.
More case studies
Want a similar setup on your platform?
Tell us about your traffic, acquirers and merchants. We will show you how the same approach would work for you.