Do merchants have to change their checkout when a platform embeds payments?

Usually only once. The merchant moves from an external page or plugin to a checkout built into the platform, with its customers' saved cards migrated where possible. After that switch, the platform can add providers or payment methods behind the same checkout without asking the merchant to integrate anything new.

One switch, then stability

Merchants using an external payment page or a plugin have to move once: to the checkout built into the platform. That move is the moment to migrate saved cards where the outgoing provider allows it, and to set up the methods the merchant's market expects. After that, the platform handles changes behind the same checkout.

What changes behind the scenes without the merchant

• New acquirers added for a country or a better rate.
• New payment methods enabled per market.
• Routing and fallback rules adjusted.
• Wallet certificates renewed, 3-D Secure rules updated.

Making the one switch painless

A hosted checkout that matches the merchant's site removes the visual change. Universal tokens keep returning customers from re-entering cards where migration is possible. A migration plan that lets new customers go to the new setup while old subscriptions finish on the old one avoids a cutover date. The platform's promise to merchants is simple: integrate once, and never again for payments. Keeping that promise is what makes embedded payments stick.