Use case summary
Connect an acquirer in each market you sell into, then route that market's traffic to it by customer country, card country, or currency. Regions stay separated, so adding a market changes nothing for the ones already running. Result: transactions arrive at issuers as domestic, and each new market gets its own route instead of inheriting one.
- Payment Manager
Why a new market inherits the wrong acquirer
Expansion usually begins by pointing new traffic at the providers you already have. It works on the first day, and nothing in the integration objects. What changes is invisible from your side: for an acquirer in one country, every card issued in another is a foreign transaction.
Issuers treat those differently. The same cardholder, the same card, and the same basket carry more risk signals when the acquirer sits outside their country, and a share of clean payments is refused on that basis alone.
The effect hides inside your overall approval rate. One number across all markets averages a strong home market together with a new one performing badly, so the stack looks healthy while the market you just invested in quietly underperforms.
How to structure routing market by market
Regional routing means each market has an acquirer of its own and a route that sends only that market's traffic to it. The work is configuration, done once per market.
- 1
Find which markets are underperforming
Analytics breaks results down by country and currency, which is what separates a market with a routing problem from your overall average. This is also the baseline you compare against later.
- 2
Connect an acquirer in that market
Filter the connectors directory by the currency, methods, and flow types the market needs, and connect the provider with your own merchant account. Some markets also require a local legal entity before an acquirer will onboard you, which is handled by your commercial team rather than the platform.
- 3
Route that market's traffic to it
Routing rules send transactions by customer country, card BIN country, or currency, so payments from that market reach the local acquirer while everything else follows the routes it already followed.
- 4
Keep each region in its own branch
Separate branches per region mean adding a market, or changing its provider, leaves the routes serving other regions untouched. That is what makes expansion repeatable instead of a rework of the whole scheme.
- 5
Keep a route back out
Cascading sends a payment on to the next provider when the local acquirer declines it for a recoverable reason or has an incident, so a new regional route does not become a single point of failure for that market.
- 6
Compare the market against its own baseline
Approval rates per country show whether the local route did what you added it for. If it did not, the rule is a configuration change, not a migration.
What you get
Each market is served by an acquirer inside it, and the routing for one market has no bearing on the rest.
Approvals judged on local terms
Transactions arrive at the issuer as domestic ones, which removes the cross-border risk signals that push otherwise legitimate payments into declines.
Markets you can actually see
Approval rates per country tell you which markets are working and which are not, so expansion decisions rest on the performance of each market rather than on a blended average.
A repeatable way to open a market
Connect the acquirer, add a routing branch, compare against the baseline. The same short sequence applies to the second market and the tenth.
Changes that stay inside one region
Because regional branches are separate, swapping a provider in one market or testing a new one carries no risk to the markets already running.
Grand Cru Concepts keeps its providers separated by geography
Grand Cru Concepts, a software publisher running high-volume consumer products across the US and Canada, started with a single active integration and now runs several providers from one interface, with routing deliberately separated by geography. Adding a provider for one market does not affect the routes serving the other, which is how Canada was brought on after the US launch, bringing Interac e-Transfer alongside the existing methods. As of May 2026, more than a year after go-live, the stack ran at a 79% approval rate with all active providers stable.