Payment processor vs payment gateway: what UK businesses need to know

Key takeaways

• A payment gateway handles the customer-facing side of checkout — capturing, encrypting, and authenticating card data — while a payment processor works in the back end to route that data through card networks and settle funds into your merchant account.

• UK card transactions account for billions of pounds in daily commerce, yet fragmented payment infrastructure quietly erodes margins — particularly for businesses managing cross-border payments.

• Traditional standalone gateway and processor setups typically add separate fee layers and force settlement into GBP, applying FX markups on every international transaction — whereas Airwallex combines gateway, processing, and multi-currency accounts into a single platform with interbank FX rates and local payment rails across 150+ countries, helping UK businesses reduce cross-border payment costs by up to 90%.

Running a business that accepts online payments means depending on infrastructure most customers never see. Behind every transaction sits a chain of systems — and two of them, the payment gateway and the payment processor, are regularly confused with each other despite doing very different jobs.

Getting the distinction right isn't just a technical exercise. For businesses handling international payments, the wrong setup can mean slower settlement, hidden FX costs, and far more operational complexity than you need.

This guide explains what each component does, how they interact in a live transaction, and what to look for when choosing the right payment setup for your business.

What's the difference between a payment gateway and a payment processor?

A payment gateway is the software layer at your checkout. When a customer enters their card details, the gateway captures that data, encrypts it using secure protocols, and replaces the card number with a secure token. This tokenisation protects sensitive information from being exposed as it travels through the payments chain.

A payment processor works behind the scenes. Once the gateway has secured the transaction data, the processor routes it through the relevant card network — Visa or Mastercard — to the customer's issuing bank. It requests authorisation, manages the clearing process, and coordinates the movement of funds into your merchant account.

The distinction matters for compliance as well as cost. Gateways carry responsibility for PCI DSS compliance, PSD2 requirements, and Strong Customer Authentication through 3D Secure. Processors handle card scheme rules, AML controls, and settlement operations.

Here's how they compare:

Most businesses that accept online card payments need both functions. The real choice is whether you source them separately or through a single provider — and that decision has a direct bearing on cost, complexity, and how well your setup scales internationally.

How a payment works from click to confirmation

In practice, the gateway and processor work in sequence — completing the entire authorisation cycle in a matter of seconds. Understanding each step helps you spot where delays, failures, or avoidable costs can enter the process.

1. Payment initiation. The customer selects their payment method at checkout and submits their card details or wallet credentials.

2. Encryption and tokenisation. The gateway captures the data, encrypts it, and replaces the card number with a secure token. Raw card data is never transmitted across the network.

3. Handoff and routing. The gateway sends the encrypted payload to the processor, which reformats the data and routes it through the appropriate card network to the issuing bank.

4. Authorisation. The issuing bank checks available funds and fraud signals, then returns an approval or decline code.

5. Settlement. If approved, the processor coordinates the transfer of funds to your merchant account — typically within one to three business days for card payments.

Each step introduces a potential point of latency or failure. For domestic transactions, the cycle usually runs smoothly. But, for international payments, step five is where many businesses encounter costs they didn't account for — particularly when a processor forces settlement into GBP rather than holding funds in the original transaction currency.

It's worth understanding this lifecycle in detail before choosing a provider, because not all gateways and processors handle each step with the same degree of transparency.

Standalone providers versus a unified payment service provider

In a traditional or fragmented setup, a business manages three separate relationships: a gateway provider, a payment processor, and a merchant acquirer. Each requires its own contract, its own integration, and its own reconciliation process. Each sends a separate invoice.

This structure can work for large enterprises with the resources to negotiate bespoke terms across multiple vendors. But, for most growing businesses, it adds overhead without adding value.

A payment service provider (PSP) consolidates those functions into a single platform. That typically means:

• A single API integration

• Unified reporting across all payment types and markets

• One support relationship and invoice

• Lower operational overhead for lean finance and engineering teams

Modern unified platforms such as Stripe, Adyen, and Airwallex go further — acting as both gateway and processor while also supporting global card acquiring and alternative payment methods.

Here's how the two approaches compare in practice:

The unified approach doesn't suit every business. Large enterprise setups with existing bank relationships and dedicated treasury teams often have valid reasons for maintaining a fragmented model. But, for businesses scaling internationally and trying to keep overhead down, a unified PSP tends to reduce both cost and complexity from the outset.

Why your payment setup matters for cross-border transactions

Many finance teams focus on headline transaction fees when evaluating payment infrastructure. The more significant cost for international businesses, however, is usually the FX layer.

Traditional payment processors commonly force settlement into the merchant's home currency. When a UK business receives a €5,000 payment from a European customer, the processor converts it to GBP at a rate that can embed a 2–3% FX markup. On a single €5,000 transaction, that's roughly €100–€150 in hidden costs. For businesses processing regular international volumes, that figure compounds quickly.

Multi-currency settlement lets you hold funds in the original transaction currency and convert — or pay out — at a time that works for your business. This avoids the forced conversion cycle entirely and keeps more money where it belongs.

There's also a newer alternative worth understanding. Open Banking account-to-account (A2A) payments allow customers to authorise a bank transfer directly from their banking app, bypassing card processors, card schemes, and conventional gateway layers entirely. For B2B transactions or high-value payments, this approach can offer faster settlement and lower processing costs.

For UK businesses expanding into Europe or further afield, these options aren't peripheral features — they're core infrastructure decisions that can determine whether international expansion is profitable.

What to look for when evaluating payment infrastructure

Choosing a payment setup goes well beyond comparing advertised processing rates. Here are the factors that tend to matter most for UK businesses evaluating their options:

• Settlement speed. How quickly do funds move from authorisation to your account? Card payments typically take one to three business days. Some PSPs offer faster or same-day settlement options.

• FX handling. Does your provider support multi-currency settlement, or do they force conversion into GBP? This is often the single largest cost driver for businesses with international customers.

• Security and compliance. Your gateway should support PCI DSS compliance, 3D Secure, and Strong Customer Authentication. Your processor should handle AML requirements and card scheme rules.

• Integration complexity. A fragmented setup can take weeks to integrate and maintain. Unified PSPs can typically go live within days and require fewer ongoing engineering resources.

• Reporting visibility. Can you see all payment activity — authorisation rates, chargebacks, FX costs — in one place? Consolidated reporting significantly reduces month-end closing friction for finance teams.

• International reach. If you're selling across multiple markets, check whether your provider supports local payment methods and local acquiring in those regions. Relying solely on international card rails can increase decline rates and add unnecessary costs.

The right setup depends on your transaction volumes, the markets you sell into, and how much operational complexity your team can absorb. But, for most scaling businesses, a unified approach offers a more sensible starting point — with the option to negotiate more bespoke arrangements as volumes warrant it.

Consolidate your payment infrastructure with Airwallex

The choice between a standalone gateway and processor or a unified platform is one of the most consequential infrastructure decisions you'll make as you scale. For businesses operating purely in domestic markets with stable volumes, a fragmented setup can work. But, the moment you add international customers, the case for consolidation becomes hard to ignore.

Airwallex brings together gateway and processing capabilities with multi-currency accounts — helping businesses simplify their payments infrastructure and reduce unnecessary operational complexity. With local payment rails across 150+ countries and interbank FX rates, it removes the forced-conversion problem and gives you clearer visibility over exactly what you're paying to move money.

Create a free Airwallex account to streamline your payment gateway and processing infrastructure under a single multi-currency platform.

Frequently asked questions

Is a payment processor the same as a payment gateway?

No. A payment gateway is the secure, customer-facing interface that captures and encrypts payment data at checkout. A payment processor is the back-end company that routes authorisation requests across card networks and handles fund settlement. They serve different functions in the transaction chain, though many modern providers offer both under one platform.

Do I need both a payment gateway and a payment processor in the UK?

If you accept online card payments, you generally need both functions — whether you access them through separate providers or a unified PSP. The gateway captures and secures the payment data; the processor routes and settles it. You can't complete an online card transaction without both elements working together.

What is a payment gateway example?

Common payment gateway examples in the UK include Worldpay, Opayo (formerly Sage Pay), and Stripe. Some modern platforms — including Airwallex — act as both gateway and processor, providing a single integration for the full payment stack.

What's the difference between a payment service provider and a payment processor?

A payment service provider (PSP) typically bundles multiple components — gateway, processing, and merchant account — into a single platform. A payment processor is one specific function within that stack: it routes and settles transactions through card networks. Most PSPs include processing as part of their core offering, making them a more streamlined choice for businesses that want to avoid managing multiple vendors.

Sources and references

1. PCI Security Standards Council, PCI DSS Tokenization Guidelines Information Supplement: https://listings.pcisecuritystandards.org/documents/Tokenization_Guidelines_Info_Supplement.pdf

2. 2 PCI Security Standards Council, PCI DSS overview: https://www.pcisecuritystandards.org/standards/pci-dss/ and Maintaining payment security: https://listings.pcisecuritystandards.org/pci_security/maintaining_payment_security

3. UK Finance, Strong Customer Authentication: https://www.ukfinance.org.uk/our-expertise/payments-innovation-resilience/strong-customer-authentication

4. UK Finance, £1 trillion worth of UK card transactions in 2024: https://www.ukfinance.org.uk/news-and-insight/press-release/ps1-trillion-worth-uk-card-transactions-in-2024

5. UK Finance, Industry guidance on Strong Customer Authentication under PSD2: https://www.ukfinance.org.uk/policy-and-guidance/guidance/uk-finance-industry-guidance-strong-customer-authentication-under-psd2