← All insights

Payment basics

Payment gateway vs payment processor:
what's the difference?

20 Nov 20263 min readPayment basics

"Gateway" and "processor" get used interchangeably, but they are different jobs in the same chain. Confuse them and you'll sign up for the wrong thing — or pay for the wrong problem.

The gateway: the front door

A payment gateway is the software layer that captures a cardholder's details at checkout, encrypts them, and forwards them for authorisation. It is the "front door" that sits between your website or app and the payment networks. It handles the customer-facing moment: tokenising card numbers, handling 3-D Secure challenges, and returning an approved or declined response.

The processor: the money mover

A payment processor is the entity that actually communicates with the card schemes and the banks to move money — debiting the customer, crediting the merchant, and settling the difference. Where the gateway handles data, the processor handles the transaction lifecycle: authorisation, capture, settlement, refunds and chargebacks.

How they work together — and where they blur

In practice, one checkout uses both: the gateway takes the data, the processor moves the money, and an acquirer (a bank) provides the merchant account that receives the funds. Most modern providers bundle all three under one API, which is convenient but makes it easy to stop noticing which layer you're actually paying for.

Why the distinction matters

  • If checkout is slow or clunky, you have a gateway problem.
  • If funds arrive late or reconciliations don't match, you have a processor problem.
  • If your application is declined at underwriting, you have an acquiring problem.

Naming the layer correctly is the first step to fixing it — and to knowing exactly what you're being charged for.