Payment Gateway vs Payment Processor: What UK Merchants Actually Need to Know
If you are setting up online payments, the terms payment gateway and payment processor can sound like the same thing. They are not. Understanding the difference between payment gateway and processor helps UK merchants choose a checkout setup that is secure, practical, and ready to grow.
In plain English, a gateway securely captures the payment instruction at checkout; a processor carries that instruction through the banking and card-network systems so the payment can be authorised and settled. Most businesses use both, often through one provider. This guide explains the difference, how the pieces work together, and what you actually need to accept payments online.
The short answer: gateway handles the checkout message; processor handles the payment movement
| Payment gateway | Payment processor | |
|---|---|---|
| Primary role | Captures, protects, and sends payment data from checkout | Obtains authorisation and coordinates settlement between financial parties |
| Visible to the shopper | Usually yes: it powers the payment form or hosted checkout | No: it works in the background |
| Simple analogy | The digital card terminal | The secure network that asks the bank and moves the funds |
| What it does not do alone | It does not itself approve a card or settle money | It does not usually provide the customer-facing checkout experience |
Key takeaway: the gateway moves securely formatted information. The processor turns that information into an approved, declined, and eventually settled payment.
What is a payment gateway?
An ecommerce payment gateway is the online equivalent of a card machine at a counter. It is the technology that receives the details a shopper enters at checkout, protects them, and passes the payment request into the processing flow. It can be a payment form embedded on your site, a redirect to a hosted page, or a wallet button presented at checkout.
A gateway normally supports three important jobs:
- Secure capture and tokenisation. It helps prevent sensitive card details from being exposed in your own systems by encrypting data and, where supported, replacing it with a token that can be used safely for later actions such as refunds or recurring payments.
- Checkout controls. It presents the payment experience, returns a clear success or failure response, and can support authentication flows such as 3D Secure when they are required.
- Routing payment data. Once the payment request is ready, the gateway sends it to the processor or acquiring path selected by your payment setup. It moves data, not money.
For a UK merchant, gateway security is central to reducing your exposure to cardholder data. Your exact responsibilities depend on how checkout is implemented, but choosing a provider and integration model that supports PCI DSS obligations is an important early decision.
What is a payment processor?
A payment processor is the behind-the-scenes service that communicates with the acquiring side of the transaction, the card scheme, and the shopper’s issuing bank. It asks whether the payment can be approved, returns the answer to checkout, and helps manage the later transfer of funds.
After receiving a payment request, the processor sends an authorisation message through the relevant card network, such as Visa or Mastercard, to the issuing bank. That bank evaluates available funds, account status, and its own risk checks, then responds with an approval or decline. If the payment is approved and captured, the processor also supports settlement: the process by which funds are made available to the merchant according to the agreed settlement schedule.
This is why the difference between a payment gateway and a payment processor matters: a smooth payment form alone is not enough. It must connect to a processing arrangement capable of approving and settling the transactions you want to accept.
How an online card payment works in practice
- The shopper pays. They enter card details or choose a wallet at your checkout and confirm the purchase.
- The gateway protects the request. It encrypts or tokenises the data, applies the relevant checkout and authentication steps, and sends the request onwards.
- The processor seeks authorisation. It passes the request through the acquiring path and card network to the customer’s issuing bank.
- The issuing bank decides. The bank approves or declines based on factors including funds, account status, and fraud controls.
- Checkout receives the result. The processor returns the response via the gateway, and the shopper sees a confirmation or a prompt to try another method.
Authorisation happens in seconds. Settlement is separate: the payment is captured, cleared, and paid out to your nominated account according to your provider’s terms. Refunds, chargebacks, and reconciliation continue after the checkout response has been shown.
Do UK merchants need both?
Operationally, yes. An online card payment needs a secure way to collect payment information and a processing path to obtain approval and settle funds. Practically, however, most UK merchants do not need to find, contract with, and integrate a gateway and processor separately.
Payment service providers, payment aggregators, and merchant accounts
A modern payment service provider (PSP) commonly bundles gateway capability, processing, fraud tools, and settlement into one service. A payment aggregator is a PSP model in which merchants operate under the provider’s broader acquiring arrangement, rather than each opening and managing a separate direct merchant account UK relationship. This can make onboarding and integration simpler, especially for new or lower-volume businesses.
| Setup model | How it works | Often suitable for |
|---|---|---|
| All-in-one PSP or aggregator | One provider supplies gateway, processing, settlement, and usually a managed merchant arrangement | Merchants seeking a faster, simpler route to online payment processing UK |
| Separate gateway and direct acquiring | The gateway connects to a processor or acquirer under a direct merchant account arrangement | Businesses needing more tailored commercial or operational control |
| Multiple providers with orchestration | An orchestration layer manages several gateways, acquirers, and payment methods through one integration | Merchants expanding across markets or optimising resilience and routing |
Neither model is automatically better. The right choice depends on your markets, volume, payment methods, risk profile, technical resources, and the level of control your business needs.
What you actually need to accept payments online
- A checkout experience. This may be a hosted payment page, an embedded payment form, or an ecommerce platform integration.
- A PSP, processor, or acquiring arrangement. It must support your business type, currencies, countries, and the card or local payment methods you plan to offer.
- A settlement destination. Confirm where funds will be paid, in which currencies, on what timetable, and how fees appear in reports.
- A clear operating process. Your team needs a way to handle refunds, customer support, disputes, reconciliation, and suspicious-payment reviews.
- A scalable integration. Consider the next market as well as the first one. Adding a wallet, local method, or new provider should not force a full checkout rebuild.
How to choose the right payment setup
Start with your customer and operating model rather than with a technology label. The following questions make the choice more concrete:
- Where are your customers? UK-only card acceptance has different needs from selling across the EU, US, or Asia-Pacific markets.
- Which payment methods do they expect? Cards may be enough for one audience, while another expects wallets, bank payments, or local schemes.
- How much control do you need? A bundled PSP is efficient for many merchants; larger or international businesses may need local acquiring, tailored fraud rules, or more detailed routing control.
- What happens when a payment fails? Look beyond headline pricing. Assess approval performance, support, reporting, retry rules, and contingency options.
- Can your team maintain it? An API integration should fit your ecommerce platform and engineering capacity, with clear test environments and documentation.
When payment orchestration becomes relevant
A PSP can give a merchant a complete first payment stack. Payment orchestration becomes relevant when one provider is no longer enough: perhaps you need several acquirers, different local payment methods, country-specific routing, or a fallback route when a provider degrades. It sits above gateways and processors to coordinate the options without turning checkout into a collection of separate integrations.
Read our guide to payment orchestration for UK scale-ups to see how this model supports international expansion.
Frequently asked questions
Is PayPal a gateway or a processor?
PayPal is best understood as a payment service provider. It combines customer-facing checkout capability with payment processing and settlement under one commercial arrangement. Merchants typically do not need to connect a separate traditional gateway and merchant account just to accept PayPal payments.
Do I need a merchant account to use a payment gateway?
Not always. A traditional gateway may connect to a direct merchant account with an acquirer. With an all-in-one PSP or payment aggregator, the provider may offer a managed or aggregated merchant arrangement instead. Ask how your funds are settled, what underwriting applies, and whether the model fits your expected volume and risk profile.
Can a payment gateway accept wallets and local payment methods?
A gateway can present and route many payment methods when they are enabled by the provider and supported by the underlying processing arrangement. Availability varies by country, currency, merchant category, and provider, so confirm the specific methods your customers need before integrating.
Build the payment stack your business needs now—and next
The difference between payment gateway and processor is simple once you see the transaction flow: the gateway securely captures the request at checkout, while the processor obtains authorisation and supports the movement of funds. For many UK merchants, one PSP supplies both. As your business grows internationally, you can add the local coverage and routing control that your next stage requires.
