What Is a Merchant Payment?

A merchant payment is any electronic payment made by a customer to a business in exchange for goods or services. The simple direction — customer to business — is what separates it from a peer-to-peer transfer, and that direction sets off a whole machinery of accreditation, fees and consumer-protection rules that wouldn't apply if your friend was sending you a tenner. To accept merchant payments at all, the business has to be registered as a merchant with a bank or processor, has to identify what it sells via a Merchant Category Code, and has to accept that every transaction will pass through a layered settlement chain that takes a few percentage points along the way.

The phrase "merchant payment" sounds straightforward, but it covers everything from a £3 contactless tap at a coffee shop to a six-figure invoice paid by ACH between two manufacturers. The underlying machinery is the same — the merchant accepts the payment instruction, an acquirer routes it through a network, the issuer or the customer's bank authorises it, and a few days later the money settles into the merchant's account. What changes between use cases is the rail, the fee structure and the consumer-protection rules.

The Players in the Merchant Payment Ecosystem

Five distinct parties get involved in every card-based merchant payment, plus the customer makes six. They each take a cut.

The customer initiates the payment, using a card, a wallet, a bank app or an Open Banking authorisation. The issuer is the bank that gave the customer the card or holds the customer's account; they authorise the payment and bear fraud risk on it (or shift that risk to the merchant under defined rules). The card network — Visa, Mastercard, Amex, Discover — owns the rails the message travels along and sets the interchange rates. The acquirer (also called the acquiring bank) is the merchant's bank; they hold the merchant's account, accept liability for the merchant to the network, and settle funds into the merchant's account a few days later. The processor handles the technical message-routing between the merchant and the network. The gateway is the API layer the merchant's website or terminal actually talks to. In smaller merchants, the acquirer, the processor and the gateway are often the same company — Stripe, for example, plays all three roles at once for most customers.

For an account-to-account payment over Open Banking or FedNow or Faster Payments, the chain is shorter: customer's bank initiates, scheme clears, merchant's bank credits. No interchange, fewer parties, no scheme fees in the card sense — but also no chargeback infrastructure.

What Distinguishes a Merchant Payment from a P2P Transfer

This is the line that matters legally and commercially. A merchant payment is regulated as a commercial transaction. The merchant has registered with an acquirer, signed scheme rules, declared a category, and accepted the chargeback and refund rules. The customer has consumer-protection rights — Section 75 in the UK for purchases over £100 on a credit card, chargeback rights on a debit card, the right to dispute the transaction with their bank if the goods don't turn up.

A peer-to-peer transfer is the same technical money movement without those protections. If you send a friend £200 via Faster Payments, you don't get to dispute it later because you fell out. If a merchant accepts a P2P transfer instead of a proper merchant payment to dodge the fees, both parties lose the consumer-protection layer, and the merchant arguably also loses their right to operate under their scheme rules.

Card networks actively police this. Misclassifying merchant payments as P2P transfers — sometimes called transaction laundering or factoring — is a serious scheme-rule breach and can get a merchant terminated from accepting cards entirely.

The Settlement Flow

When a customer pays a merchant by card, the transaction goes through two distinct phases: authorisation and settlement.

Authorisation happens in real time. The gateway sends the transaction to the processor, the processor sends it to the network, the network sends it to the issuer, the issuer checks the customer has the funds and the transaction isn't suspicious, and the issuer sends back an approve or decline code. The whole chain typically completes in 200–500 milliseconds. At this point, the funds are reserved against the customer's account but not yet moved.

Settlement happens later, usually overnight or on a scheduled batch. The merchant submits the day's approved transactions to the acquirer; the acquirer claims the funds from each issuer through the network; the network nets the totals between banks; and the acquirer credits the merchant's account, minus fees, on the agreed schedule — typically T+1, T+2 or T+3 in most markets. For high-risk industries the acquirer may hold a rolling reserve as well.

This split is why "my customer paid yesterday but I haven't got the money yet" is normal and not a problem. The payment is committed at authorisation; the cash moves at settlement.

The Merchant Category Code (MCC)

Every merchant is assigned a four-digit Merchant Category Code (MCC) when they're set up with an acquirer. The MCC describes what the merchant sells — 5411 is grocery stores, 7372 is software companies, 5812 is restaurants, 4900 is utilities. Some MCCs are gambling, adult content or political donations, and those get a different fee and risk profile.

The MCC drives a surprising amount. It sets the interchange tier the merchant pays. It determines whether the issuer is allowed to authorise the transaction at all (some cards block adult-content MCCs by default). It influences fraud-monitoring thresholds, points-and-rewards eligibility, and even consumer cashback rates. Merchants who think their interchange is too high should check what MCC they've been classified under before changing processor — sometimes a misclassified MCC is the entire problem.

What the Merchant Pays

The total cost of accepting a card-based merchant payment splits into three layers. Interchange is the largest chunk — typically 0.2-0.3% on UK consumer debit cards, 0.3% on UK consumer credit cards (both capped by regulation), and significantly more on commercial cards and cards issued outside Europe. The interchange goes from the acquirer to the issuer. Scheme fees are a smaller layer paid to Visa or Mastercard for using the network — usually 0.05–0.15% plus per-transaction fees. Processor markup is what the acquirer and gateway add on top. This is the one merchants can actually negotiate; the first two are set elsewhere.

Total all-in cost for a typical UK e-commerce merchant runs 1.4–2.5% of transaction value. For Amex it's higher. For an Open Banking pay-by-bank transaction, the merchant pays a flat fee — pence per transaction rather than a percentage — and no interchange at all, which is why merchants who can route customers to bank payments often do.

The Channels a Merchant Payment Can Use

Merchant payments aren't limited to card transactions. The full set of channels in 2026 includes card-not-present e-commerce, card-present in-store payments, telephone payments (a subset of CNP), digital wallet payments, Open Banking bank transfers, ACH payments in the US, direct debit in the UK and Europe, and instant rails like FedNow and Faster Payments. The merchant decides which channels to enable, and the trade-off in each case is fees against risk against settlement speed.