UK alternative to Stripe
Every collection method, one ledger
Stripe is a card platform. UK operators still bolt on a bureau and an open-banking provider. Omni-payments keeps Apple Pay, Google Pay, cards, open banking and BACS in one place — and runs the retry path for you.
Cards from 10p · Open banking at 0.5% · BACS from 2.0p
Why look past Stripe
A card gateway is not a UK collections stack
Stripe is good at taking a card. Memberships, invoices and regulated collections in the UK usually also need Direct Debit, BACS reports and bank-to-bank. That is three suppliers and three reconciliations unless you run them together.
| Need | Stripe-led setup | ePayment omni |
|---|---|---|
| Cards, Apple Pay, Google Pay | Native | Native on the card scheme |
| Open banking | A second product, or not used | Same customer, same report |
| BACS Direct Debit bureau | Not a bureau — AUDDIS, ADDACS, ARUDD sit elsewhere | Bureau on the same stack, from 2.0p |
| Failed card → cheaper method | You build the retry | Workflow: wallet or card, then open banking or Direct Debit |
| Support | Global ticket queue | UK team, ISO 27001 and ISO 9001 |
| Indicative card rate | Typically 1.5% + 20p online | From 10p plus acquiring, or from 1% + 4p all-in |
Stripe remains a strong card processor. The gap is running UK schemes as one operation, not as add-ons.
One place
Every payment against the same customer
Wallets, cards, open banking and BACS write to one ledger. The payer is not a Stripe customer plus a bureau mandate plus an open-banking consent.
-
One customer record
Name, account, card token and bank consent live together. Confirmation of Payee and modulus checks sit on the same file before a BACS collection leaves.
-
One reconciliation
Settlements, fails, chargebacks and ARUDD land in one report. Finance is not matching three CSVs at month end.
-
One retry path
If Apple Pay or a card does not go through, the workflow can offer open banking the same session, or lodge a Direct Debit for the next cycle.
Methods
Offer the method the payer already uses
Checkout, invoice and membership collection on the schemes UK payers actually complete.
-
Apple Pay
Wallet on the card scheme. Biometric confirm, then the same acquiring path as a Visa or Mastercard sale.
-
Google Pay
Same card scheme, same fraud controls, same settlement. Useful on Android checkout and in-app.
-
Cards
Visa, Mastercard and Amex. PCI DSS, 3-D Secure and AVS. Gateway from 10p plus the acquirer rate.
-
Open banking
Bank-to-bank, confirmed immediately. 0.5% plus 10–15p. No card scheme fee, no chargeback.
-
Direct Debit
Recurring collections on BACS. Mandates, AUDDIS, ADDACS and ARUDD without you running the cycle.
-
Direct Credit
Payouts, refunds and supplier payments on the same bureau as the collections.
Automated workflows
More than one way to get paid, in the right order
You set the path. The platform tries the methods in sequence and writes one outcome.
-
Start with the wallet or card
Apple Pay, Google Pay or a keyed card for payers who want to finish in the browser. Fraud checks and 3-D Secure run on that attempt.
-
Offer open banking on a fail or a preference
If the card is declined, or the payer chooses bank-to-bank, they pick their bank and authorise the amount. Settlement is confirmed immediately.
-
Lodge Direct Debit for the next cycle
Memberships and invoices that will repeat do not need a card on file. The bureau lodges the mandate and collects on BACS.
-
Report once
Success, fail and fallback sit on the same payment. Support sees one timeline, not three portals.
Indicative rates
Price the scheme, not a blended Stripe tariff
Run the schemes as one operation.
Tell us the mix of wallets, cards, open banking and BACS. We will size the gateway, the bureau and the workflow.
Contact sales