On-Us Transaction

An on-us transaction is a payment where the same bank sits on both sides. It issued the card the shopper used. It also serves the shop that took the payment. So the request does not have to travel between two separate banks. It goes out from the till, reaches the bank, and comes back approved or declined. All of it happens inside one set of systems. The card network may not need to sit in the middle at all, and in some setups it does not.

The term is banking shorthand for a payment that stays in house. Under the usual four party model, a card issuer holds the cardholder's account. An acquiring bank holds the shop's account. The two then square up through a scheme. The UK version of the interchange fee rules defines those roles, and Article 2 of that regulation sets them out in full. When one bank plays both parts, the middle of that picture folds in. The money side changes with it.

Why The Route Is Shorter

A normal card payment makes several hops. The terminal talks to the acquirer. The acquirer hands the request to the network. The network routes it to the issuer. The answer comes back the same way. On-us cuts most of that out. Fewer hops usually means a quicker answer, and fewer places for a message to go missing. It also means the bank has the full picture in one place. It can see both the account being debited and the shop being paid.

The Fee Picture

The interchange fee is a payment from the acquirer to the issuer. So it makes little sense when both are the same firm. That fee is capped for consumer cards in several markets. The UK rules cap credit card payments at 0.3 percent of the value of the payment at the time of writing. A separate figure applies to debit. Caps, scope and carve-outs differ by market and are revised from time to time. So the version in force locally is the one to check. What is left on an on-us payment is a scheme fee, which may be cut or waived, plus the bank's own cost to process.

Where It Shows Up In Practice

Home markets with a few large banks see it often. So many cards and so many shops sit with the same handful of names. It is common in closed markets, and in countries with a national card scheme. It also turns up in banks that serve both shoppers and small firms. Group structures matter too, where the issuing and acquiring arms sit under one parent. In such cases the routing choice may be made inside the group, so a merchant sees the effect without being told about it. Firms that use local acquiring tend to hit on-us routing more often, because a local acquirer holds more of the local cards.

Effect On Approval Rates

This is the part that interests merchants. A bank looking at its own cardholder has more context than a bank looking at a stranger. It can see the balance, the account history and the recent pattern of spend. That tends to support a better approval rate on marginal payments. It can also mean fewer requests for a step-up check. The effect varies by bank and by market, and it is not a rule to bank on. It is one reason local acquiring is worth testing rather than assumed.

Clearing And Settlement Differences

An on-us payment does not need the same clearing run as a two bank payment. There is no other bank to square up with. The bank simply moves value between two accounts on its own books. That looks much like an internal transfer. It changes the timing of what a merchant sees. Funds can land sooner, and the settlement file may split on-us volume from the rest. Finance teams that expect one figure and receive two often assume a fault when the split is normal.

What It Means For Reporting

Because the route differs, the data can differ too. Some fields that a scheme would normally stamp on a payment may be absent. The bank may fill them in instead. Decline codes can be more precise on on-us traffic, since they come straight from the issuer's own system. That is helpful for diagnosis and awkward for comparing routes. One route speaks a slightly different dialect from the other. Mapping both to a single internal set of reasons is worth the effort. It also makes trend reports honest, since a rise in one code may simply reflect a shift in routing.

Practical Guidance For Merchants

Ask an acquirer what share of volume it expects to run on-us in each market. Treat that as part of the pricing talk rather than a technical detail. Compare approval rates by route where the data allows. Expect settlement and reporting to differ, and set the books up for both from the start. And keep more than one route open, since a single bank on both sides is also a single point of failure. A global acquirer network exists partly for that reason. This piece on local acquiring and smart routing weighs up the trade-offs.

‍