Best Payment Processors for London Businesses (2026)

What actually matters when choosing a payment processor in London

The first split to make is in-person versus online. A London café processing 200 contactless taps a day needs a different tool than a Shoreditch agency billing clients monthly via invoice. In-person rates are almost always lower — processors can be more confident about fraud — so mixing up the two categories when you compare prices is a common mistake. SumUp's 1.69% in-person rate looks attractive; their 2.5% online rate is merely average. Stripe's 1.5% + 20p online rate is sharp; their Terminal hardware costs more than the competition. The headline number only matters if it is the rate that applies to how your business actually takes money.

Transaction fees beat monthly fees every time, past a certain volume. This is simple arithmetic that most processor comparison guides gloss over. A processor charging 1.5% with no monthly fee costs £1,500 per £100,000 of card turnover. A processor charging 1.2% with a £30 monthly fee costs £1,560 on the same volume — more expensive, despite the lower rate. The crossover point for most monthly-fee structures lands between £8,000 and £15,000 per month. Run the numbers for your actual volume before being seduced by low percentage rates attached to mandatory monthly commitments.

The hidden costs that processors bury in their terms are international cards, currency conversion, and chargebacks. London businesses face all three more acutely than the UK average. Central London retail and hospitality regularly sees 20–30% of card transactions from non-UK-issued cards — American visitors on Amex, European tourists on cards issued outside the EEA. Stripe adds 0.9% for non-EEA cards; non-EEA cards on Stripe Terminal jump to 2.9% + 10p per transaction. Square absorbs no chargeback fee at all, which is a genuine competitive advantage for businesses with any dispute exposure. Worldpay buries PCI compliance fees in small print. These are not edge cases — for a busy London business, they are monthly line items.

• Split your volume into in-person and online before comparing rates — in-person transactions cluster at 1.69–1.75%, while online card-not-present rates run higher (Stripe charges 1.5% + 25p for UK cards, Square Online 1.9%).
• Payout timing directly affects cash flow: Stripe and Square settle next business day, SumUp takes 1–3 business days, and Worldpay can take 3–5 days — a real problem for high-volume London hospitality and retail businesses.
• Factor chargeback fees into your decision before committing: Stripe charges £15 per dispute regardless of outcome, SumUp charges £10, and Square charges nothing — a meaningful difference if you operate in a sector prone to disputes.
• Confirm Apple Pay and Google Pay support before signing up — the majority of London customers under 40 tap to pay, and missing contactless wallet support costs you sales at the till.
• Check PCI DSS compliance obligations upfront — Stripe, Square, and SumUp handle PCI compliance on your behalf, but some older acquirers charge a separate annual PCI compliance fee that adds to your effective rate.
• For recurring B2B billing, compare direct debit via GoCardless (1% + 20p, capped at £4) against Stripe card-on-file — direct debit becomes the cheaper option on any payment above roughly £160.

Best payment processors for London businesses, ranked

The right processor depends on your business model, monthly volume, and whether most of your revenue is in-person or online. The ranking below is ordered by overall usefulness to the broadest range of London businesses — not by who has the most marketing budget.

At a glance: payment processors compared

All rates are for UK-issued cards unless stated. In-person rates assume a physical card reader; online rates assume a hosted checkout or payment link.

Ecommerce, service businesses, subscriptions: different businesses need different processors

A London ecommerce brand shipping across Europe has one set of problems. A Soho creative agency billing retainer clients has a completely different set. A Notting Hill gym with 300 monthly members has a third. Treating payment processing as a single category is where most businesses end up overpaying.

For ecommerce, Stripe is the default for good reason. The checkout conversion tooling, the Radar fraud detection, and the breadth of integrations with Shopify, WooCommerce, and custom stacks make it the path of least resistance. The 1.5% + 20p rate is competitive for domestic UK and EEA traffic, but if your customer base is international — particularly North American or Asian — the non-EEA surcharge of 0.9% on top creates real friction. Businesses with significant non-EEA traffic above £50K/month should model an Adyen switch, or at minimum negotiate a custom Stripe rate for international volume.

For service businesses — agencies, consultants, photographers, tradespeople — the calculus changes entirely. If you are raising invoices for £500–£5,000 and chasing payment, GoCardless beats every card processor on large transactions because of the £4 cap. A £2,000 invoice collected via GoCardless Standard costs £4. The same invoice via Stripe costs £30.20. That is a £26 difference per invoice, and service businesses that switch to direct debit for regular clients typically see that decision pay for itself inside the first month. For one-off payments where customers expect to pay by card, combine GoCardless for recurring clients with Stripe for new or occasional ones. For gyms, subscription boxes, and any business with a predictable monthly billing cycle, GoCardless is not a nice-to-have — it is the structurally correct choice. The failure rate on direct debit is materially lower than card subscriptions (no expired cards, no lost cards, no limit increases needed), which means less revenue leakage and less time spent on failed payment recovery.

Payment Processor FAQs for London Businesses

The questions London founders ask most often when choosing how to take payments — answered without the hedging.

Payment Processor FAQs for London Businesses

The questions London founders ask most often when choosing how to take payments — answered without the hedging.

How to choose, and what to sort out first

Run your last three months of revenue through the pricing models above before signing anything. Take your total card turnover, split it roughly between in-person and online, and estimate what percentage comes from non-UK cards. Plug those numbers into each processor's rate card. The right answer will become obvious — in most cases, one or two processors will be meaningfully cheaper than the rest for your specific mix, and the difference often runs to several hundred pounds a month at modest volumes.

The second thing to sort out is your PCI DSS compliance status. Stripe, Square, SumUp, and Zettle all handle PCI compliance for you when you use their hosted payment tools — you do not hold card data, so the compliance burden is minimal. Worldpay and Adyen involve more complex compliance scoping, and Worldpay in particular charges a separate PCI fee that can sit anywhere between £2.50 and £7.50 per month depending on your plan. It is not a dealbreaker, but it is an honest cost that does not appear in their headline rate.

Finally: whatever processor you choose, the checkout experience the customer sees matters as much as the rate you pay. A payment page hosted on a generic Stripe link or a payment widget bolted clumsily onto a template site communicates something to the customer — and what it communicates is that the business has not invested in how it presents itself online. London businesses competing for clients and customers at any meaningful price point need a website that makes the payment step feel like a natural conclusion to a professional journey, not an afterthought. A well-designed website with payments integrated cleanly — whether that is Stripe Checkout embedded in a custom flow, Square's online store, or a GoCardless mandate built into an onboarding sequence — converts better and builds the kind of trust that brings customers back. The processor handles the transaction. The website handles the relationship.