Pay-by-bank, the modern way.
Account-to-account payments through Paytone — PSD2-compliant, consent-aware, and routed instantly where the bank supports it. Lower fees than cards, fewer chargebacks, and settlement that lands fast.
Three reasons to put pay-by-bank in your checkout.
Open banking isn't a niche method anymore. For high-ticket, high-trust flows, it routinely beats cards on cost, speed, and dispute exposure.
Lower fees
Account-to-account flows bypass card scheme fees. Effective cost per transaction is typically a fraction of a card charge at the same volume.
Instant settlement
Where the originating bank supports instant rails — SEPA Instant, FPS, Pix — funds arrive in seconds, not days. No waiting for batch windows.
Fewer chargebacks
The customer authenticates with their bank, not just a card number — friendly fraud and dispute exposure drop materially compared with card-on-file flows.
A complete open banking toolkit.
Initiation, consent, account information, returns, and recovery — the full PSD2 surface, exposed through Paytone's payment object.
PSD2-compliant flows
SCA, redirect, and decoupled authentication patterns implemented to the standards mandated by PSD2 and the relevant national competent authorities.
Consent management
Consents stored, scoped, expiring, and revocable. Re-consent flows triggered automatically when scope or expiry conditions change.
AIS & PIS endpoints
Account information and payment initiation against participating banks in supported markets, with consistent response shapes across providers.
Supported regions
UK and EU coverage live; selected non-EU markets through partner aggregators as those markets formalize open-finance frameworks.
Refund flows
Refunds initiated as outbound transfers to the same account that paid in — surfaced through the standard refund object and lifecycle.
Dispute & recovery
Patterns for handling failed initiation, abandoned consent, and post-payment recovery — built into the routing engine, not your application code.
Four steps, end to end.
Open banking has more steps than a card charge, but each is well-defined. Paytone manages the moving parts and exposes a clean status timeline.
Initiate
Your application calls payments.create with the open banking method. Paytone returns a redirect URL or QR code for the customer to authenticate against their bank.
Consent
The customer authenticates and consents at their bank using strong customer authentication. The consent token is stored against the customer's record in Paytone.
Bank confirms
The bank confirms the payment instruction back to Paytone. A webhook fires with the confirmation status and, where supported, an end-to-end reference for reconciliation.
Settled
Funds arrive at the beneficiary account — typically in seconds on instant rails. Paytone fires the settlement event and the payment moves to the captured state.
Add pay-by-bank to your checkout.
Talk to the team about the markets, ticket sizes, and trust profile of your flows. We'll show you whether open banking belongs in your checkout and how to add it.