Payment Gateway vs Payment Processor: What UK Businesses Need to Know

The terms "payment gateway" and "payment processor" get thrown around as if they were interchangeable. They are not. A gateway and a processor do two fundamentally different jobs in a card transaction, and understanding the distinction matters — it affects your pricing, your checkout experience, and whether you need one provider or two. Here is how each one works, how they fit together, and what the difference means for a UK business taking card payments.

What Is a Payment Gateway?

A payment gateway is the front-end of a card transaction. It is the digital equivalent of the card terminal in a shop — its job is to capture payment details securely and pass them to the next step in the chain.

When a customer enters their card number, expiry date, and CVV on your checkout page, the gateway encrypts that data and routes it onward. The gateway never stores the full card number (or it should not — PCI DSS compliance requires tokenisation or encryption). It also handles the customer-facing side of authentication, including 3D Secure 2 (3DS2) challenges — the "verify this payment in your banking app" step mandated under UK Strong Customer Authentication (SCA) rules.

What a gateway does:

Encrypts and transmits card data from your checkout to the payment network
Triggers 3D Secure authentication for SCA compliance
Returns the transaction result (approved or declined) to your checkout
May provide a hosted payment page if you do not want to handle card data on your own site

Examples of standalone gateways: Braintree (owned by PayPal), Opayo (formerly Sage Pay), Worldpay's gateway product. Many modern providers bundle the gateway with processing — Stripe, Adyen, and Checkout.com all include both in a single integration.

What Is a Payment Processor?

A payment processor is the back-end. Once the gateway has captured the card details, the processor takes over: it communicates with the card schemes (Visa, Mastercard), routes the transaction to the issuing bank for authorisation, and — if approved — facilitates the settlement of funds from the customer's bank to your merchant account.

The processor is also the entity that manages your merchant account and handles the operational side: chargebacks, settlement reports, and compliance with card scheme rules. In the UK, a processor typically needs to be authorised by the FCA as a payment institution or operate through an acquiring bank relationship.

What a processor does:

Routes authorisation requests to the card schemes and issuing banks
Manages settlement — moving funds from the cardholder's bank to your business account
Handles chargebacks and disputes on your behalf
Provides reporting on transaction volumes, fees, and settlement batches

Examples of processors (acquirers): Worldpay, Barclaycard, Elavon, and Global Payments are traditional UK acquirers. Stripe, Adyen, and Checkout.com are modern full-stack providers that combine processing with their own gateway.

How They Work Together

A card transaction in the UK moves through four entities in sequence:

Payment gateway — captures and encrypts card details; triggers 3DS2 if required
Payment processor / acquirer — receives the encrypted data, forwards it to the card scheme
Card scheme (Visa, Mastercard) — routes the authorisation request to the issuing bank
Issuing bank — approves or declines the transaction; holds the funds for settlement

All of this happens in under two seconds. The gateway and processor each handle distinct stages, and neither can complete a transaction without the other.

Payment Gateway vs Payment Processor: Key Differences

The easiest way to think about it: the gateway is what your customer sees; the processor is what your bank sees.

Role

Gateway: Captures and secures card data at checkout
Processor: Authorises, settles, and manages the transaction financially

Customer-facing

Gateway: Yes — it is the checkout form or hosted payment page
Processor: No — operates entirely behind the scenes

Handles funds

Gateway: No — it never touches the money
Processor: Yes — it settles funds to your merchant account

SCA responsibility

Gateway: Triggers the 3DS2 challenge and manages the customer authentication flow
Processor: Relies on the gateway's authentication result; may decline a transaction if SCA is missing

Pricing model

Gateway: Per-transaction fee (e.g. 10–20p per transaction for standalone gateways) or monthly subscription
Processor: Percentage of transaction value + fixed per-transaction fee (e.g. 1.5% + 20p)

PCI DSS scope

Gateway: High — it handles raw card data
Processor: High — but uses tokenised data from the gateway in modern setups

Examples (UK)

Gateway: Braintree, Opayo, Worldpay Gateway
Processor: Worldpay, Barclaycard, Elavon, Stripe (combined), Adyen (combined)

Which Does Your UK Business Need?

The answer depends on your setup:

If you use a full-stack provider:

You do not need to think about the distinction. These platforms bundle gateway and processor into one integration — one contract, one set of fees, one dashboard. For most UK businesses, this is the simplest path. PhotonPay extends this model further by adding global payment and stablecoin-native settlement on top of its combined gateway-processor stack, meaning a single platform covers checkout, processing, and cross-border money movement.

If you use a standalone gateway with a separate acquirer:

You are maintaining two relationships. The gateway provides the checkout technology; the processor handles authorisation and settlement. This setup is more common among established UK businesses that chose their acquirer years ago and their gateway separately. It can offer more negotiating leverage — you can switch gateways without changing acquirers — but it also means two fee structures and two support channels.

If you are a marketplace or platform handling payments on behalf of others:

You likely need both, and your gateway-processor architecture must support sub-merchant onboarding, split payments, and regulatory compliance. Platforms like Stripe Connect and Adyen for Platforms are built for this use case.

Full-Stack Platforms: When One Provider Covers Both

If you would rather not manage two separate relationships, a full-stack platform bundles gateway and processor into a single integration. Several providers serve the UK market this way — and a few extend beyond card payments to cover international money movement.

PhotonPay is one such platform. It combines gateway and processing for UK card transactions with multi-currency wallets and global payout capabilities. For a UK business trading internationally, this means a single provider handles the entire payment lifecycle — from checkout to settlement to cross-border supplier payments.

Key advantages of choosing a full-stack platform like PhotonPay:

One integration for gateway and processor — no stitching together a checkout provider and a separate acquirer
UK card acquiring combined with global collection accounts, so you can accept payments from domestic and international customers through the same system
Stablecoin-native settlement infrastructure for global transactions, which can settle faster and at lower cost than traditional correspondent banking channels
Multi-currency wallets that let you hold, convert, and pay out in multiple currencies without forced conversion on every incoming payment
FCA-authorised operations, ensuring regulatory compliance and UK-based support
Direct integration with Faster Payments and BACS for domestic GBP settlement

FAQ

Can I use just a payment gateway without a processor?

No. A gateway alone cannot settle funds to your bank account. It can capture and encrypt card data, but you need a processor (acquirer) behind it to complete the transaction. If you use a full-stack provider like Stripe or Adyen, both are included in a single service — you are not "skipping" the processor; it is just bundled in.

Do I need both if I use PayPal?

No. PayPal operates as both gateway and processor for PayPal wallet transactions — it handles the entire flow from checkout to settlement. If PayPal is your only payment method, you do not need a separate gateway or processor. If you add card payments alongside PayPal, those card transactions will require a processor (which may be PayPal itself, depending on your setup).

What is an acquirer, and is it the same as a processor?

In the UK, "acquirer" and "processor" are often used interchangeably, but technically they are distinct. The acquirer is the financial institution that holds the merchant account and settles funds — it is the entity with the direct relationship with Visa and Mastercard. The processor is the technology layer that handles authorisation routing. In a modern full-stack provider, the distinction collapses — Stripe, for example, acts as both. In a traditional setup, your merchant account might be with Barclaycard (acquirer) while First Data (now Fiserv) provides the processing technology.

How does SCA affect my choice of gateway and processor?

Both the gateway and processor must support 3D Secure 2. If your gateway does not support 3DS2, the processor will see the transaction as lacking SCA and may decline it. When choosing a gateway or a full-stack provider, confirm they are 3DS2-compliant — it has been a regulatory requirement in the UK since March 2022.

Final Thoughts

The distinction between a payment gateway and a payment processor matters less than it used to for most UK businesses, because the industry has consolidated toward bundled solutions. Stripe, Adyen, Checkout.com, and PhotonPay all provide gateway and processor as a single package. The question is not "which gateway and which processor?" but "which full-stack provider matches my business?" — and whether their combined offering extends beyond card payments to cover the international payment needs that many British businesses now operate with daily.