Payment Routing

Payment routing is the choice of which path a payment takes on its way out. A business with more than one acquirer, or more than one processor, has that choice to make on every single transaction, and the right answer changes from one payment to the next. Card country, amount, product type and how a route has been performing lately can all point in different directions. Routing is the set of rules that settles it.

The choice matters because the outcome is not fixed. The same card, for the same amount, at the same shop, can be approved on one route and turned down on another. Banks do not read a local request the same way as a foreign one, and some acquirers handle certain card products better than others. Once a business can see that spread in its own numbers, routing stops being a technical detail. It becomes a thing worth real time. How much there is to gain varies by market and by card mix, so test it rather than assume.

What A Routing Rule Looks At

The card number carries more than people expect, and the first digits give the issuing bank and the country, which is the basis of BIN routing. Amount matters too, because thresholds change which checks apply. Product type matters as well, since debit, credit and prepaid cards behave in different ways. Then there is history: how a given route has done lately for that slice of traffic. Rules that mix all of this live in routing logic the business can edit itself.

Static Rules And Live Ones

A static rule is a table, and the table says cards from this country go to that acquirer. It is easy to reason about and just as easy to forget about. A live rule watches results and shifts traffic as they change, which is what dynamic routing does: quicker to react, harder to explain after the fact. Many teams run a static base with a live layer on top, so there is a known default sitting behind the clever part.

Local Acquiring And On-Us

Routing to a local acquirer in the shopper's own market tends to help, because the request reads as domestic to the bank that issued the card. In some cases it goes further than that. Where the same bank issued the card and serves the shop, the payment becomes an on-us transaction and does not leave that bank's systems. That means a quicker answer and a different fee shape. It also means the bank has more context to work with, and that can swing a marginal request.

Cost As Well As Approval

Approval is the headline and cost is the quieter half. Routes differ on interchange, scheme fees and the acquirer's own margin, and a switching fee can apply when traffic moves between networks. A route that approves a bit more while costing a good deal more is not the better one. The measure worth using is margin per attempt, not approval rate on its own, since that keeps both halves in the same view.

When A Route Fails

Rules need an answer for the bad case as well as the good one. Where a route times out or returns an error, the payment can be tried elsewhere, and that is what a fallback route is for. Care is needed at this point, because a retry after a timeout risks charging the customer twice unless the status is checked first. A hard decline should not be re-routed at all: the answer will be the same wherever it is asked.

What The Rules Say About Choice

Routing has limits set from outside. Where a card carries more than one brand, UK interchange rules stop anyone building in a mechanism that limits the payer's choice at the till. A payee may set a default, and Article 8 of those rules says the payer must be able to override it. Apart from that, the standards on authentication let some lower risk payments skip the full check. One route is based on risk analysis of each payment. Those figures sit in the rules, they get revised, and they differ by market.

Routing Beyond Cards

Cards get the attention, and the same thinking applies more widely. A bank based payment may have more than one provider able to reach the same network. A payout can go by card push, by instant transfer or by a batch file, each with its own cost and speed. The same logic holds. The choice is made per payment, not per business. Rules are simpler here because there are fewer options. The saving on a high volume payout run can still beat anything cards offer.

Measuring It Honestly

Comparing routes fairly is harder than it sounds. Approval rates differ by card country and by product, so a route that gets easier traffic will look better than it is. The cleaner method is to split a similar slice of traffic across both routes and compare the halves. Watch decline codes as well as totals, since a route can approve the same share while producing more soft declines and more friction along the way.

Getting The First Rule Right

Get the data into one place before writing any rules. Routing you cannot measure is guesswork. Start with one clear idea, such as local acquiring in a single market, and split traffic rather than switching it outright. Keep a static default behind any live rule. Watch cost and approval together. And review the rules on a schedule, since acquirer performance moves around over the course of a year. Smart routing covers the tooling, and this piece on routing best practice covers the habits worth building.

‍