UK businesses can now integrate four main payment rails: Faster Payments (instant, up to £1m per transaction, near-zero cost), Bacs Direct Debit (3 working days, pennies per collection), CHAPS (same-day high value) and open banking pay-by-bank, which initiates a Faster Payment directly from a customer's bank for roughly £0.20 to £0.50 flat versus 1.5% to 3%+ on cards. On a £500 invoice that is about 10p instead of £7.50. Faster Payments processed 5.09 billion transactions worth £4.2 trillion in 2024, and open banking now serves over 15 million UK users. Integration runs either through a regulated PISP or aggregator (fastest, no PCI burden) or a direct bank API build. Since 7 October 2024, APP fraud reimbursement is mandatory up to £85,000. Choosing the right rail per use case, not one rail for everything, is what cuts cost and fraud at once.
Last updated: June 2026
The UK runs on four core payment rails plus the card schemes, and each is built for a different job. Faster Payments (FPS) moves money between bank accounts in seconds, with an individual transaction limit now raised to as much as £1 million depending on your bank. Bacs Direct Debit pulls scheduled or recurring amounts on a three working day cycle at a cost of pennies. CHAPS is the same-day rail for high-value or time-critical transfers like property completions. The card schemes (Visa, Mastercard) sit on top of all of this and charge a percentage on every transaction. Understanding which rail does what is the single most important decision in any payment integration project.
Faster Payments is the backbone of modern UK commerce. In 2024 it processed 5.09 billion transactions worth £4.2 trillion, and open banking pay-by-bank rides on these same rails to settle instantly. Bacs, by contrast, is the slow and steady workhorse for subscriptions, salaries and utility bills. CHAPS is rarely used by small businesses directly but matters for conveyancing, large supplier settlements and treasury movements. Cards remain dominant at the checkout because of habit, chargeback protection and consumer trust, but they are the most expensive rail to run by a wide margin.
Our honest view: most UK businesses default to cards for everything because their first payment provider sold them a card terminal, then never revisit it. That is a mistake. A plumber taking a £2,000 boiler payment, a B2B supplier invoicing £15,000, and a SaaS firm billing £29 a month should not all be on the same rail. Matching the rail to the transaction is where real savings live.
| Rail | Speed | Typical cost | Limit | Best for |
|---|---|---|---|---|
| Faster Payments | Seconds | Near zero (bank fee) | Up to £1m | Instant transfers, payouts |
| Open banking (pay-by-bank) | Seconds | £0.20-£0.50 flat or 0.1-1.0% | Up to £1m | Invoices, checkout, top-ups |
| Bacs Direct Debit | 3 working days | Pennies per collection | No fixed cap | Subscriptions, recurring bills |
| CHAPS | Same day | £15-£30 per transfer | No upper limit | High-value, property completions |
| Card schemes | 1-3 days to settle | 1.5%-3%+ plus fees | Acquirer dependent | Consumer checkout, low-trust |
The practical takeaway is that no single rail wins on every dimension. Faster Payments and open banking win on speed and cost. Direct Debit wins on recurring collection where you need to pull rather than be pushed. Cards win on consumer familiarity and dispute cover. A well-architected payment system uses several rails and routes each transaction to the cheapest rail that satisfies the customer experience and risk needs.
Open banking pay-by-bank lets a customer pay directly from their bank account without entering card details, by authorising a single payment through their own banking app. Technically, a regulated Payment Initiation Service Provider (PISP) initiates a Faster Payment on the customer's behalf after they approve it with biometric or passcode authentication. The money lands in your account in seconds, and there is no card number, no stored credential and no chargeback. Open banking is roughly eight years old in the UK, now serves over 15 million active users and handles more than two billion API calls a month.
The flow at checkout is straightforward. The customer selects pay-by-bank, chooses their bank from a list, gets redirected (or app-switched) into their banking app, sees the exact amount and payee pre-filled, and confirms. Because the customer authenticates inside their own bank, Strong Customer Authentication is handled natively and the payment is pushed by the payer rather than pulled by the merchant. That single architectural difference removes most of the fraud surface that cards carry.
Where pay-by-bank shines is high-value, account-funding and invoice scenarios: paying a £4,000 builder, topping up a trading account, settling a B2B invoice, or paying rent. It is gaining ground in consumer retail too, with pay-by-bank now appearing on major platforms including Amazon and eBay. For UK businesses building modern checkouts, an open banking option built alongside cards is increasingly standard, and we frequently deliver it as part of a wider business process automation project so that reconciliation, invoicing and accounting all update automatically when a payment clears.
Our stance: open banking is not a card replacement for every shopper, and pretending it is sets the wrong expectation. It is a powerful additional rail that wins decisively on cost, speed and fraud for the right transactions. Offer it as a prominent option, default to it for invoices and high-value payments, and keep cards for impulse and low-trust purchases.
Open banking is dramatically cheaper than cards, typically costing a flat £0.20 to £0.50 per transaction (or 0.1% to 1.0%) versus 1.5% to over 3% on cards once interchange, scheme and acquirer fees are stacked. The headline example: on a £500 repair invoice you pay around 10p with open banking instead of about £7.50 on a card. That gap widens as transaction values rise, because card fees are percentage-based while open banking is often flat. For a business processing tens of thousands of pounds a month, the annual difference runs into thousands of pounds saved.
Card fees are not a single number, which is part of why they are so expensive. They are an interchange fee (paid to the cardholder's bank), a scheme fee (paid to Visa or Mastercard) and an acquirer margin (paid to your payment processor), all bundled into the rate you see. Premium and commercial cards push the rate higher still. Refund handling adds friction too: card refunds take three to five business days, while open banking refunds are near-instant because they are simply another Faster Payment in reverse.
| Transaction value | Card cost (~1.5%) | Open banking (~£0.30 flat) | Saving per transaction |
|---|---|---|---|
| £50 | £0.75 | £0.30 | £0.45 |
| £500 | £7.50 | £0.30 | £7.20 |
| £2,000 | £30.00 | £0.30 | £29.70 |
| £10,000 | £150.00 | £0.30 | £149.70 |
Now scale that across volume. A trades business taking 60 payments a month averaging £800 pays roughly £720 a month in card fees at 1.5%, or about £8,640 a year. The same volume on open banking at a flat £0.30 costs about £216 a year. That is over £8,400 saved annually on a single channel, and the saving grows for businesses with higher average transaction values or premium card mixes.
The honest caveat: open banking conversion can be lower than cards for first-time users who are unfamiliar with the flow, and not every shopper has a supported bank for every PISP. So the saving is real but you must measure conversion alongside cost. The right answer for most businesses is to offer both and steer high-value or invoice payments toward pay-by-bank, where the saving is largest and conversion is naturally higher.
Choose the rail by matching transaction type to the rail that is cheapest while still meeting the customer experience and risk needs. Use open banking or Faster Payments for one-off invoices and high-value payments, Bacs Direct Debit for recurring subscriptions, cards for low-trust consumer checkout where chargeback protection matters, and CHAPS only for time-critical high-value transfers. There is no single best rail. The cost and fraud savings come from routing each transaction to the right one rather than forcing everything through cards because that is what you already have.
Here is the decision matrix we apply when designing a multi-rail payment architecture for a UK business. It is deliberately vendor-neutral, because the right rail depends on your transaction profile, not on which provider is paying for the most marketing.
| Use case | Recommended rail | Why | Fallback |
|---|---|---|---|
| One-off invoice (B2B) | Open banking | Flat fee, instant settlement, no chargeback | Faster Payments (manual) |
| High-value payment (£2k+) | Open banking / CHAPS | Percentage card fees become punitive | Bank transfer |
| Monthly subscription | Bacs Direct Debit | Pull-based, cheap, automated retries | Card on file / VRP |
| Consumer impulse checkout | Cards | Familiarity, speed, dispute cover | Open banking option |
| Account top-up / wallet funding | Open banking | Instant, low cost, no stored card | Cards |
| Property completion | CHAPS | Same-day, high-value, audited | Faster Payments (under limit) |
A few practical rules follow from this. First, the higher the transaction value, the more punishing card fees become, so push high-value payments to open banking or bank transfer. Second, anything recurring with a predictable amount belongs on Direct Debit, while recurring with a variable amount is the natural home of Variable Recurring Payments, which we cover below. Third, never remove cards entirely from a consumer-facing checkout: some shoppers will simply abandon if their preferred method is missing.
This is exactly the kind of logic we build into custom CRM and billing systems so that the routing decision is invisible to staff and the cheapest viable rail is selected automatically on every transaction.
You integrate UK payments one of two ways: through a regulated provider (a PISP or aggregator that gives you a single API across many banks) or by building directly against individual bank APIs. For almost every UK business, the provider route is the correct choice because it removes the PCI burden, gives instant multi-bank coverage, and lets you go live in weeks rather than months. The direct route only makes sense at very large scale or where you have specific regulatory or commercial reasons to hold the bank relationships yourself. Most integration projects therefore become a question of which provider, not whether to build from scratch.
The provider route works because aggregators have already done the hard part: they hold the regulatory permissions, maintain connections to every major UK bank, handle Strong Customer Authentication flows, and absorb the constant maintenance as bank APIs change. You integrate against one clean API and inherit coverage of the whole market. Crucially, because the customer pays from their bank and you never touch card data, the heavy PCI DSS compliance scope that comes with handling card numbers largely disappears for the open banking flow.
| Factor | Provider / PISP route | Direct bank API build |
|---|---|---|
| Time to live | 2-8 weeks | 6-18 months |
| Regulatory permissions | Inherited from provider | You must be FCA authorised or use an agent model |
| Bank coverage | Whole market, day one | One bank at a time |
| Maintenance burden | Provider handles it | You handle every API change |
| PCI scope (open banking) | Minimal | Minimal but everything else is on you |
| Best for | Almost all UK businesses | Large platforms, specific regulatory needs |
Whichever route you take, a real integration is more than calling a payment API. It is the surrounding plumbing that makes payments trustworthy and auditable. Below is the integration checklist we work through on every project, and it is the part thin vendor guides tend to skip.
Our honest rule: do not build direct bank integrations unless you have a board-level reason and the engineering depth to maintain them. We have seen businesses sink six figures into a direct build that an aggregator would have delivered in a month. The smart money goes on a provider integration plus excellent reconciliation and reporting around it, which is where we focus our software development and web application work.
Variable Recurring Payments (VRP) let a customer give a one-time consent for a business to take payments of varying amounts within agreed limits, executed as instant Faster Payments rather than the three-day Bacs cycle. Commercial VRP (cVRP) extends this beyond moving money between your own accounts to paying merchants and billers, and it is positioned as the modern successor to Direct Debit for many recurring use cases. The first cVRP transactions were made in November 2025, and a UK Payments Initiative of 31 firms is being set up to run the cVRP scheme. VRP will not kill Direct Debit overnight, but it will steadily take the recurring-payment use cases where instant settlement and finer control matter.
The difference from Direct Debit is meaningful. With Direct Debit, the customer signs a mandate and the business pulls amounts on a multi-day cycle, with limited real-time visibility and a guarantee scheme to handle disputes. With VRP, the customer authorises a recurring permission inside their banking app, sets parameters such as maximum amount and frequency, and each payment executes instantly with full transparency. It combines the convenience of card-on-file with the cost and speed of Faster Payments.
| Feature | Bacs Direct Debit | Variable Recurring Payments |
|---|---|---|
| Settlement speed | 3 working days | Instant (Faster Payments) |
| Amount | Variable, pulled by business | Variable, within customer-set limits |
| Consent model | Mandate | In-app permission with parameters |
| Customer control | Cancel via bank | Granular limits, instant cancel |
| Cost | Pennies per collection | Low, Faster Payments based |
| Maturity (2026) | Decades, ubiquitous | Early, scaling fast |
Real-world momentum is building. The first cVRP went live in November 2025 involving Tink, Visa, Kroo and Utilita, and pay-by-bank flows are now appearing on large consumer platforms. For now, the pragmatic position is to keep stable, established recurring billing on Direct Debit while piloting VRP for use cases that benefit from instant settlement and customer-set limits, such as topping up accounts, variable utility bills, or flexible subscription tiers.
Our view: VRP is the most important development in UK recurring payments in a decade, but be sceptical of anyone telling you to rip out Direct Debit today. Migrate where the use case clearly benefits, run both in parallel, and let the conversion and settlement data guide the pace.
UK payment integration is governed by PSD2 (which underpins open banking and Strong Customer Authentication), the FCA (which authorises payment firms) and the Payment Systems Regulator (PSR), with the headline 2024 change being mandatory APP fraud reimbursement. Since 7 October 2024, victims of Authorised Push Payment fraud over Faster Payments and CHAPS must be reimbursed up to a cap of £85,000, within five business days, with liability split 50/50 between the sending and receiving payment service providers. If you use a regulated provider you inherit most of these permissions, but you still carry obligations around fraud prevention, Confirmation of Payee and customer protection.
The regulatory picture matters because it shapes both your liability and your integration design. Strong Customer Authentication, required under PSD2, is the reason open banking payments are approved inside the customer's banking app. Confirmation of Payee, which checks that the account name matches before money moves, is now a frontline defence against misdirected and fraudulent payments and should be part of any pay flow you build. The APP reimbursement regime has reshaped incentives across the industry by making both the sending and receiving firms financially responsible for fraud, which has driven heavier investment in real-time fraud detection.
| Rule / body | What it requires | Who it applies to |
|---|---|---|
| PSD2 / SCA | Strong Customer Authentication on payments | All payment flows |
| FCA authorisation | Permission to provide payment services | PISPs, providers (you inherit via them) |
| PSR APP reimbursement | Reimburse APP fraud up to £85,000 in 5 days, 50/50 PSP liability | FPS and CHAPS payments |
| Confirmation of Payee | Verify payee name matches account | Push payment flows |
| PCI DSS | Secure handling of card data | Card flows only (open banking avoids most) |
For a business integrating payments, the compliance work breaks down into a manageable checklist. You do not need to become an authorised payment institution to accept open banking payments if you use a regulated provider, but you do need to design fraud controls, name verification and clear customer communication into your flows.
The honest summary: regulation has made UK payments safer and pushed liability onto firms, which means fraud prevention is no longer optional engineering. Build it in from day one. We treat fraud controls, Confirmation of Payee and audit logging as core requirements on every payment project, not bolt-ons, and increasingly use AI-driven automation to flag anomalous payment patterns in real time.
Softomate Solutions delivers UK payment integration as a fixed-scope, five-stage project that typically runs four to ten weeks depending on complexity, with a fixed quote agreed up front and no hourly surprises. We are a London-based software and automation agency in Stanmore (HA7), and we integrate open banking, Faster Payments, Bacs Direct Debit and card rails into checkouts, invoicing systems, CRMs and bespoke applications, with reconciliation and reporting built in. A typical multi-rail integration with reconciliation starts from £6,500, with simpler single-rail provider integrations starting from around £3,500.
Our process is deliberately structured so you know exactly what happens, when, and what it costs before we write a line of code. We are vendor-neutral on providers: we recommend the rail and provider that fit your transaction profile and savings target, not the one that pays the biggest referral.
| Stage | What happens | Typical timeline |
|---|---|---|
| 1. Discovery and mapping | Audit your transactions, map rails, model the savings | Week 1 |
| 2. Provider and architecture | Select provider, design multi-rail routing and reconciliation | Week 1-2 |
| 3. Build and integrate | Sandbox build, CoP, webhooks, idempotency, reporting | Week 2-6 |
| 4. Testing and compliance | End-to-end testing, fraud controls, audit trail, sign-off | Week 5-8 |
| 5. Go live and support | Phased launch, monitoring, reconciliation tuning, handover | Week 7-10 |
Every engagement comes with a fixed quote agreed after discovery, so the price does not move once scope is set. If you want a chatbot or voice layer to handle payment queries and reminders, we can add an AI chatbot or AI voice agent that ties into the same payment system. For businesses already running GoHighLevel, we connect payment rails directly into your funnels and pipelines through our GoHighLevel automation services.
Yes. Open banking payments are approved inside the customer's own banking app using Strong Customer Authentication, so you never store card details. Because payments are pushed by the payer rather than pulled, there are no chargebacks, and Confirmation of Payee reduces misdirected payments. It is generally considered as safe or safer than card payments for most use cases.
Settlement is near-instant. Open banking initiates a Faster Payment, so funds typically land in your account within seconds, well ahead of the one to three days card settlement usually takes. Refunds are also near-instant because they are simply a Faster Payment in reverse, compared with three to five business days for card refunds.
No, not if you use a regulated provider. A licensed Payment Initiation Service Provider or aggregator holds the FCA permissions and scheme membership, and you integrate against their API. You inherit their authorisation for the payment flow, though you remain responsible for fraud prevention, customer communication and data protection within your own systems.
The individual Faster Payments transaction limit has been raised to as much as £1 million, though the exact ceiling depends on your bank, which may set lower internal limits. This higher limit makes Faster Payments and open banking viable for substantial B2B invoices and high-value payments that previously had to use CHAPS.
Substantially. Cards typically cost 1.5% to over 3% per transaction, while open banking is often a flat £0.20 to £0.50. On a £500 payment that is around 10p versus £7.50. For a business taking 60 payments a month averaging £800, that can mean over £8,000 saved annually on a single channel.
Not immediately. VRP offers instant settlement and customer-set limits, making it ideal for variable or usage-based billing, and the first commercial VRP went live in November 2025. But Direct Debit remains cheap, ubiquitous and backed by a guarantee scheme. Expect VRP to take specific use cases first while Direct Debit continues for stable recurring billing.
Since 7 October 2024, UK payment firms must reimburse victims of Authorised Push Payment fraud over Faster Payments and CHAPS up to £85,000, within five business days, with liability split 50/50 between the sending and receiving firms. It has driven heavier investment in real-time fraud detection across the industry.
For almost every UK business, use a provider. A PISP or aggregator gives whole-market bank coverage, inherited FCA permissions and a single API, with go-live in weeks. Direct bank builds take six to eighteen months and only make sense at large scale or where you have specific regulatory or commercial reasons to hold bank relationships yourself.
Increasingly, yes, through Variable Recurring Payments, which let customers authorise recurring payments within set limits. For now, Bacs Direct Debit remains the standard for fixed recurring billing because it is cheap, automated and well established. Many businesses run Direct Debit for stable subscriptions while piloting VRP for variable or usage-based charges.
Yes, and we recommend it. Offering both lets you steer high-value and invoice payments toward low-cost open banking while keeping cards for shoppers who prefer them, protecting conversion. Routing logic can automatically present the cheapest viable option, and you measure conversion and cost per rail to refine the mix over time.
UK payment integration in 2026 is no longer a single decision about which card terminal to buy. The smart approach routes each transaction to the cheapest viable rail: open banking and Faster Payments for invoices and high-value payments at roughly 10p instead of £7.50 on a £500 sale, Bacs Direct Debit for stable subscriptions at pennies, and cards retained for consumer checkout where familiarity and dispute cover matter. With Faster Payments now reaching up to £1 million per transaction, open banking serving over 15 million users, Variable Recurring Payments emerging since November 2025, and mandatory APP fraud reimbursement up to £85,000 since October 2024, the rails and rules have shifted decisively in favour of bank-based payments. Use a regulated provider, build Confirmation of Payee and reconciliation in from day one, and measure cost and conversion per rail. Get the architecture right and the savings compound month after month.
If you want a payment system that routes every transaction to the cheapest rail and reconciles automatically, our team can scope it with a fixed quote: see our London business process automation services or get in touch for a payment integration consultation.
Written by Deen Dayal Yadav, Founder of Softomate Solutions, a London-based software development and AI automation agency in Stanmore (HA7). With over 12 years building software, payment and automation systems for UK businesses, he has delivered open banking, Faster Payments and Direct Debit integrations across trades, B2B services and SaaS. Softomate Solutions is registered at Companies House and specialises in multi-rail payment architecture, custom CRM and process automation. Learn more about Softomate Solutions.
We protect the real names of all clients featured in examples and case studies. Every testimonial is from a real client.
More from the blog
Work with us
Every project we take on has a measurable outcome. Talk to our London team and we will show you exactly how we would approach your challenge.
Softomate Solutions Limited
Deen Dayal Yadav
Online
