The Short Answer
A payment gateway is the technology that captures and encrypts card data at checkout. A payment processor routes that data between the parties involved. An acquirer is the bank that settles the funds into your account and takes on the financial risk of the transaction.
In practice, these functions are often bundled — Stripe, for example, operates as all three. But understanding the separation matters when you need to troubleshoot a decline, negotiate pricing, or scale to a setup that gives you more control.
What a Payment Gateway Does
The payment gateway sits between your checkout and the rest of the payment chain. When a customer enters their card details, the gateway:
- Encrypts the card data and tokenises it (replacing raw card numbers with a secure token)
- Transmits the authorisation request to the processor
- Returns the authorisation response (approved/declined) to your checkout
- Handles 3D Secure authentication where required
Gateway providers include Stripe, Adyen, Braintree, NMI, and many others. Some are consumer-facing (Stripe's hosted payment page), some are API-only (NMI, Spreedly). The gateway doesn't hold funds — it's purely a data conduit.
What a Payment Processor Does
The processor is the infrastructure layer that routes transaction data from the gateway to the card schemes (Visa, Mastercard) and to the issuing bank. It handles:
- Routing authorisation requests to the correct card network
- Receiving authorisation responses from the issuing bank
- Batching and clearing transactions at end of day
- Facilitating settlement from the card scheme to the acquirer
Processing is largely invisible to merchants. Companies like Worldpay, Fiserv, and TSYS operate as processors on behalf of acquiring banks. Many acquirers process their own transactions in-house.
What an Acquirer Does
The acquirer (acquiring bank) is the financial institution that holds your merchant account and provides you with the ability to accept card payments. It's the acquirer that:
- Underwrites your business and assesses your risk profile
- Provides your Merchant ID (MID) — your unique identifier on the card networks
- Settles card revenue into your bank account, typically T+1 or T+2
- Takes on financial liability for chargebacks and fraud losses
- Charges your MDR (Merchant Discount Rate) for the service
Examples include Lloyds Cardnet, Barclaycard, Worldpay (banking arm), and many specialist acquirers for high-risk industries. The acquirer relationship is the most important of the three — it determines your pricing, your risk limits, and ultimately whether you can process cards at all.
Why it matters
When a transaction declines, the reason code comes from the issuing bank — but it's routed through the processor and presented by the gateway. Understanding which layer is causing a problem tells you who to call. A soft decline (insufficient funds) is an issuer issue. A technical decline (invalid gateway configuration) is a gateway issue. A risk-based decline (flagged as suspicious) might be acquirer-level rules. Same symptom, very different root causes.
How a Transaction Flows Through All Three
Here's what happens in the ~2 seconds between a customer clicking "Pay" and seeing "Payment confirmed":
- Step 1 — Gateway. Customer enters card details. Gateway encrypts and tokenises the data, sends an authorisation request to the processor.
- Step 2 — Processor. Routes the request through the relevant card scheme (Visa/Mastercard) to the issuing bank.
- Step 3 — Issuing bank. Checks available funds, fraud rules, and 3DS status. Returns approved or declined.
- Step 4 — Processor. Relays the response back through the scheme to the gateway.
- Step 5 — Gateway. Returns the result to your checkout. Customer sees the outcome.
- Step 6 — Settlement (end of day). Approved transactions are batched, cleared through the scheme, and settled to your merchant account by the acquirer. Funds hit your bank account T+1 or T+2.
All-in-One vs Unbundled: Which Is Right for You?
All-in-One (Stripe, Adyen, Checkout.com)
All-in-one providers combine the gateway, processor, and acquirer (or acquiring bank relationship) under a single contract, API, and dashboard. This is the right choice for most businesses getting started or scaling to mid-market volumes. Setup is fast, pricing is transparent, and there's one throat to choke when something goes wrong.
The trade-off: you have no acquirer redundancy. If your account is suspended or terminated, you stop processing entirely. You also have limited ability to negotiate components independently.
Unbundled (Independent Gateway + Direct Acquirer)
Larger merchants often separate the gateway from the acquiring relationship. An independent gateway (NMI, Spreedly, Primer) sits in front of one or more direct acquiring relationships. This gives you:
- Acquirer redundancy — route traffic to a backup acquirer if your primary has issues
- Negotiating leverage — switch acquirers without rebuilding your checkout integration
- Smart routing — send transactions to the acquirer with the highest acceptance rate for each card type or geography
- Better pricing — negotiate directly with acquirers at volume, rather than paying a platform markup
This setup is more complex to manage and typically only makes economic sense above £1–2M monthly processing volume, but the savings and resilience can be substantial at scale.
The practical question
If you're processing under £500k/month, an all-in-one provider is almost certainly the right call. Above that, it's worth modelling whether an unbundled setup would pay for the added operational overhead. At £2M+ monthly volume, the answer is usually yes — and having a payment consultant run that analysis costs you nothing.