The practical answer to stripe vs gocardless
For stripe vs gocardless in 2026, most UK service businesses should start with Stripe if their website needs cards, wallets and Bacs Direct Debit. Stripe is not limited to cards: one provider can cover immediate card authorisation, deposits and recurring bank collections.
Choose GoCardless when Direct Debit is the core payment rail and its specialist mandate, recovery and accounting workflows earn their place. GoCardless does not process credit or debit cards, so businesses needing both must either choose Stripe or operate two providers.
This corrects two common misconceptions. Stripe supports UK Bacs Direct Debit, whilst the old GoCardless prices repeated by some comparison pages no longer match its current tiers.
For most smaller businesses, one provider is the better starting point. A second adds another onboarding process, customer record, webhook system, refund route, reconciliation workflow and set of failure messages for staff to understand.
Current UK fees as at 18 October 2026
A useful stripe vs gocardless comparison now has three columns: Stripe cards, Stripe Bacs Direct Debit and GoCardless Direct Debit.
Stripe’s current UK schedule lists standard cards, premium cards, Bacs and optional Billing fees. GoCardless publishes three domestic transaction tiers, excluding VAT, with an additional 0.3% for Direct Debits over £2,000.
| Payment method or plan | Current UK fee | Cap |
|---|---|---|
| Stripe standard UK card | 1.5% + 20p | None stated |
| Stripe premium UK card | 2.8% + 20p | None stated |
| Stripe Bacs Direct Debit | 1%, with a 20p minimum | £4 |
| GoCardless Standard | 1% + 20p, excluding VAT | £4 |
| GoCardless Advanced | 1.25% + 20p, excluding VAT | £5 |
| GoCardless Pro | 1.4% + 20p, excluding VAT | £5.60 |
Stripe Billing is separate from payment processing. Its pay-as-you-go plan costs 0.7% of Billing volume, but businesses do not automatically need Billing merely because they collect recurring Bacs payments. A custom portal might already own the invoice schedule and subscription rules.
The GoCardless VAT treatment matters. GoCardless says VAT applies to transaction fees invoiced to UK merchants, and displaying the merchant’s name rather than “GoCardless Ltd” costs £50 per month.
There is another easily missed cost: GoCardless charges for every submitted payment, not only successful collections. Failure, refund or chargeback fees may also apply.
Do not budget from the old “GoCardless Plus £50 and Pro £250 monthly” comparison still circulating online. It does not represent the current GoCardless pricing structure, and live pricing should always be checked before implementation.
Worked costs at £25, £100 and £500
The table below applies the published domestic rates and rounds to the nearest penny. The GoCardless VAT-inclusive row shows the cost for a business unable to recover that VAT.
| Collection method | £25 payment | £100 payment | £500 payment |
|---|---|---|---|
| Stripe standard UK card | £0.58 | £1.70 | £7.70 |
| Stripe Bacs Direct Debit | £0.25 | £1.00 | £4.00 |
| GoCardless Standard, before VAT | £0.45 | £1.20 | £4.00 |
| GoCardless Standard, including 20% VAT | £0.54 | £1.44 | £4.80 |
| Stripe Bacs plus pay-as-you-go Billing | approximately £0.43 | £1.70 | £7.50 |
The Stripe Billing percentage is calculated separately from the Bacs collection charge. It is not covered by the £4 Bacs transaction cap, which is why the illustrative £500 total reaches £7.50.
VAT-registered businesses may be able to reclaim GoCardless VAT and should model their own position rather than treating the VAT-inclusive figures as universal. Confirm the treatment with the person responsible for the company’s tax affairs.
Stripe Bacs has the lowest baseline collection fee at these payment values. That does not settle the decision: optional Billing can change Stripe’s total, whilst GoCardless’s collection and recovery workflows may reduce manual work elsewhere.
Mandates, payment timing and the Direct Debit Guarantee
Direct Debit is not an instant payment method. Stripe says Bacs confirmation normally takes four business days with an existing mandate or seven with a new mandate.
With an existing GoCardless authorisation, collection normally takes three business days to charge the customer and another two business days to reach the merchant. These timings affect when an invoice can safely be treated as paid.
The Direct Debit Guarantee normally requires ten working days’ notice of changes. It also lets customers cancel through their bank at any time and provides a full and immediate refund when a collection error is made.
We therefore prefer cards or wallets for deposits, urgent bookings and other payments needing an immediate authorisation result. Customer choice also matters: UK Finance reports that cards represented 64% of UK payments in 2025 and 65% of UK adults were registered for a mobile payment service.
The implementation consequence is simple but critical. Fulfilment, account activation and invoice status must follow verified provider events, not the browser page a customer reaches after submitting a form.
Failed payments, retries and the real collection cost
Stripe can retry an insufficient-funds Bacs failure twice within 30 days. GoCardless has a more specialist recurring-payment proposition, including Success+, mandate management, fraud controls and accounting workflows that may justify a dedicated provider.
Because GoCardless charges on submission, unsuccessful attempts can still cost money. Its support documentation also confirms that additional failure, refund or chargeback fees may apply.
A card dispute and a Direct Debit Guarantee claim are not the same event. They need distinct internal statuses, evidence processes, accounting entries and customer communications rather than one generic “reversed” flag.
Transaction price is only part of collection cost. We would model failure frequency, staff time, retry success and involuntary churn alongside the headline fee. A dearer provider can be cheaper overall if it recovers more valid recurring revenue or removes enough administration.
How we would integrate either provider into a website or portal
A robust build keeps customer, mandate and provider identifiers server-side. Webhooks are processed idempotently, meaning a repeated event cannot mark the same invoice paid twice or trigger duplicate fulfilment.
We also use a payment-status state machine rather than a single paid checkbox. Typical states include pending, submitted, confirmed, failed, refunded and claimed, backed by an internal invoice ledger recording every transition.
The simplest architecture is Stripe for cards, compatible wallets and Bacs. A booking system can request a card deposit immediately, whilst a customer portal offers Bacs for a retainer or membership collected later. This is usually the cleanest route for custom booking systems and customer portals.
The legitimate dual-provider design uses Stripe for cards and wallets and GoCardless for Direct Debit. Both feed a normalised customer, invoice and reconciliation layer so staff do not have to assemble the truth from two dashboards.
That normalisation is real development work. Two providers mean two sets of payment IDs, mandate references, webhook events, permissions, failure states, refunds and reconciliation rules. We add both only when customer payment choice or specialist Direct Debit operations provide enough value to cover that complexity.
Any proposed Xero or QuickBooks workflow should be tested alongside the custom build, including tax handling, credit notes and failed collections. An accounting sync is useful downstream, but it should not become the website’s source of truth for live payment status.
Decision checklist: Stripe, GoCardless or both
Choose Stripe when:
- customers need cards or wallets as well as Direct Debit;
- one API, account and reconciliation flow are preferable;
- deposits or bookings need immediate payment confirmation;
- Stripe Billing is either unnecessary or worth its additional cost.
Choose GoCardless when:
- most revenue is collected through Direct Debit;
- mandate management and Success+ recovery are operational priorities;
- its accounting workflows reduce enough work to justify a dedicated provider;
- card payments are not needed, or another provider is already justified.
Use both only when card choice and specialist Direct Debit operations each provide enough value to offset the additional build and administration. It should be an explicit operating decision, not the default architecture.
Before choosing Stripe or GoCardless for subscriptions, record your typical payment values, monthly volume, failed-payment rate, VAT position, settlement requirements, statement-name needs and accounting workflow. Decide separately whether Stripe Billing is genuinely required.
Stripe is included in our technology stack because we build with it; that is a technical choice, not a claim of partner status. Our Stripe integration work focuses on verified events, failure handling and reconciliation rather than stopping at a checkout form.
Before any code is written, map one invoice from creation through submission, confirmation, failure, retry, refund and reconciliation. That process usually exposes the right provider choice faster than comparing headline percentages.
Talk to us about your payment or customer-portal build, and we will help you choose the simplest architecture that meets the operational requirement.