Can an ISV keep its current processor when it embeds payments?

Yes. On a white-label infrastructure with a connected provider network, an existing processor can stay as one route among several. The ISV can add acquirers for new countries or methods, move volume between providers with routing rules, and keep stored cards usable across providers through tokenization, without asking merchants to change their integration.

One route among several

An ISV that already sends payments to a processor does not have to drop it. On a white-label infrastructure with a connected provider network, that processor becomes one route. Existing merchants keep processing there on day one; the ISV adds acquirers for new countries, methods or better pricing, and moves volume with routing rules when it chooses.

What makes this work

• Universal tokens that keep stored cards usable across providers.
• Routing rules per merchant, market and method.
• Fallback to another provider when the first fails.
• Reconciliation across all providers in one view.

What merchants experience

No new integration. The checkout, the saved cards and the reporting stay the same while the ISV changes what happens behind them. This is the practical answer to a common fear: embedding payments does not mean a migration weekend. It means adding infrastructure above the current processor, then deciding, merchant by merchant, where each payment should go. The current processor's contract and notice period remain a commercial question, handled separately from the technical path.