Payment Gateway vs. Payment Processor: What’s the Difference?

The two terms get used interchangeably and they aren’t the same thing — here is what each one actually does, and why confusing them costs sellers money.

A payment gateway captures and transmits card details from your checkout. A payment processor moves the money between the banks. Most sellers today buy both from one provider, which is why the terms blur — but they are separate functions, and knowing which one is failing tells you who to call.

The Short Version

Think of a card payment as a message and a transfer.

The gateway handles the message. It sits at your checkout, captures the card details, encrypts them, and passes an authorisation request onward.

The processor handles the transfer. It routes that request through the card network to the customer’s bank, gets an approve or decline, and later moves the actual funds into your account.

One is the front door. The other is the plumbing.

What Happens in the Two Seconds After Someone Clicks Pay

The clearest way to see the division of labour is to follow a single transaction.

1. The customer submits the card on your checkout. The gateway captures it and immediately tokenises it, so the raw number doesn’t linger anywhere it shouldn’t.
2. The gateway sends an authorisation request to the processor, usually with fraud signals and 3-D Secure results attached.
3. The processor routes it to the card network — Visa, Mastercard, Amex — which passes it to the bank that issued the card.
4. The issuing bank decides. It checks funds, risk, and velocity, and returns an approve or a decline with a response code.
5. The answer travels back through the network, processor, and gateway to your checkout, and the customer sees success or failure.
6. Settlement happens later. Approved transactions are batched, usually at the end of the day, and funds move over the following days into a merchant account and then to you.

Authorisation Is Not Payment

An approval means the issuing bank has agreed to the charge and reserved the funds. It does not mean money has moved.

Between authorisation and settlement, the transaction can still be voided, reversed, or later disputed. Which is why an approved order is a strong signal rather than a finished sale, and why platforms hold payouts rather than paying out instantly.

What a Payment Gateway Does

The gateway is the only part of the stack your customer touches.

• Captures card data at the checkout, in a form or hosted field.
• Encrypts and tokenises it, so the raw card number never sits on your server.
• Passes the authorisation request to the processor.
• Returns the result — approved, declined, or an error your checkout has to handle gracefully.
• Often adds fraud screening, address verification, and 3-D Secure.

Because it owns the checkout experience, the gateway is also where conversion is won or lost. A gateway that forces a redirect, mangles mobile layout, or handles declines with a dead end costs you more in abandoned carts than any fee difference. Which is why the checkout page deserves as much attention as the payment terms behind it.

What a Payment Processor Does

The processor never appears to your customer and does the harder half of the work.

• Routes the authorisation through Visa, Mastercard or another network to the issuing bank.
• Returns the approve or decline to the gateway.
• Settles the funds — the money moves later, in a batch, not at the moment of approval.
• Handles the money side of disputes, pulling funds back when a chargeback lands.
• Calculates and deducts fees, including interchange set by the networks and the processor’s own margin.

Where Merchant Accounts Fit In

There’s a third component the comparison usually leaves out, and it’s the one with the most consequences.

A merchant account is a specific type of bank account that holds card funds before they’re paid out to you. Traditionally you applied for one, got underwritten on your business model, and accepted the risk exposure that came with it.

Modern platforms often aggregate — you sit under the platform’s merchant account rather than holding your own. That’s why you can start selling in an afternoon instead of waiting three weeks for underwriting. It also means the platform’s risk rules apply to you, and that a free merchant account usually means aggregated rather than genuinely free.

Which Layer Charges You What

Payment pricing feels opaque partly because three different parties are taking a cut and only one of them sends you an invoice.

• Interchange — set by the card networks and paid to the issuing bank. Non-negotiable, varies by card type, and is the largest component. Rewards and corporate cards cost more.
• Scheme fees — the networks’ own charge for running the rails. Small, fixed, and also non-negotiable.
• Processor margin — what your processor adds on top. This is the negotiable part, and at volume it is worth negotiating.
• Gateway fees — often a monthly fee plus a per-transaction charge of a few cents, sometimes bundled to zero when the same provider does both.

Two pricing models sit on top of that.

1. Interchange-plus shows you the true cost and the margin separately, which is transparent and worth having at volume.
2. Blended or flat-rate pricing gives you a single percentage regardless of card type, which is simpler and slightly more expensive on average — a fair trade for most smaller sellers.

Aggregated platforms almost always price blended, because they are absorbing the variance across everyone on the platform.

Why Sellers Confuse Them, and Why It Costs Money

Declines: Who Owns the Problem

Declines are the clearest illustration of why the distinction matters, because the fix lives in a different layer depending on the cause.

The response code tells you which you’re dealing with, and most gateways surface it if you look. Sellers who treat every failed payment as one category either retry things that will never work or abandon things that would have succeeded on Tuesday.

Do You Need Both?

Functionally, yes — a card payment cannot complete without both a gateway and a processor. Commercially, almost certainly not as separate purchases.

Buying them separately makes sense if you need a specific gateway for a specific checkout experience, want to route transactions across multiple processors for redundancy or better rates, or operate at a volume where interchange optimisation is worth engineering effort.

For nearly everyone else, one provider covering both is fewer integrations, fewer contracts and one number to call. The genuine decision isn’t gateway versus processor — it’s whether you assemble the payment stack yourself or use a platform that carries it, which also determines who owes the tax and who handles disputes. Selling internationally is where that choice bites hardest, and where the global payment mistakes sellers make tend to surface.