Can an ISO keep its merchants when it changes acquirer?

Short answer

Yes, when the merchant relationship, the console and the reporting belong to the ISO rather than to the acquirer. With its own infrastructure, an ISO connects several acquirers, places each merchant with the one that fits its risk profile and market, and moves merchants between them without asking them to change tools.

In detail

Yes, when the merchant relationship, the console and the reporting belong to the ISO rather than to the acquirer. With its own infrastructure, an ISO connects several acquirers, places each merchant with the one that fits its risk profile and market, and moves merchants between them without asking them to change tools.

It depends on who owns the relationship

In the classic ISO model, each merchant signs with the acquirer, uses the acquirer's portal and sees the acquirer's brand. If the ISO changes acquirer, every merchant has to sign a new contract, learn a new tool and often re-enter stored cards. Many stay with the old acquirer, and the ISO loses them.

With its own infrastructure

  • Merchants sign with the ISO and use the ISO's console and reporting.
  • The ISO connects several acquirers and places each merchant with the one that fits its category and market.
  • Moving a merchant between acquirers is an onboarding with the new acquirer plus a routing change; the merchant's tools do not change.
  • Stored cards follow through universal and network tokens.

What this changes

The ISO stops being a sales channel for one acquirer and becomes a payment business with its own merchant base. Acquirers compete for its volume. A change of acquirer, for pricing, risk appetite or performance, becomes a commercial decision rather than a loss of merchants. This is the main reason ISOs move to white-label infrastructure: the merchant relationship, once held by the acquirer, becomes theirs.

Still have a question?

Our team walks you through the platform with your use case on the table.

Book a demo