Can new customers use the new processor before the migration ends?

With a universal token, yes. New customers and new subscriptions go to the new processor from the first day, while existing subscriptions keep being billed with the old processor's tokens. NORBr maps those tokens behind the scenes until the migrated card data arrives, so neither the operator nor its merchants change their integration during the transition.

Two populations, one platform

During a migration, existing subscribers are billed with tokens held by the old processor, while new customers can be onboarded anywhere. Separating the two is the key to a migration without a cutover date. New customers and new subscriptions go to the new processor from day one. Existing subscriptions keep running on the old tokens until the migrated card data arrives.

How the universal token works

• The platform holds its own token for each stored card, independent of any processor.
• That token maps to the old processor's token today, and to the new processor's token once the data is migrated.
• Routing rules decide which processor handles each payment, based on where the card is available.

What stays unchanged

The operator's integration and its merchants' integrations. They reference the universal token; the mapping underneath changes without them knowing. Reporting shows volume moving from one processor to the other as the migration progresses. If the export from the old processor is delayed, nothing breaks: old subscriptions keep billing where they are, and the share of new business on the new processor keeps growing.