Pay-by-Bank

Pay-by-Bank lets your users send money directly from their bank account inside your application. No card numbers, no redirects to a third-party checkout - just a bank transfer authorised by the user with their existing online banking credentials.

nrich uses SEPA Instant wherever the bank supports it, with automatic fallback to standard SEPA Credit Transfer where Instant is not available. No configuration required — the payment rail is selected automatically based on bank capability.

📘

Get credentials

Sign in to console.qwist.cloud to generate sandbox credentials. Use the sandbox demo bank to test payment flows end-to-end.

Why bank transfer?

Card payments are ubiquitous, but they carry structural costs that become significant at scale or for high-value transactions. Bank transfers via PSD2 eliminate most of them.

The three costs cards impose that bank transfers don't:

• Interchange fees - card transactions typically cost 1.5–2.5% of the transaction value, paid to the card network and issuing bank. Bank transfers use a flat fee regardless of amount.
• Chargeback risk - card disputes can reverse a payment weeks or months after it was made, with the merchant bearing the burden of proof. SEPA payments initiated via SCA are push payments: once the user authorises, the transaction is irrevocable.
• Infrastructure overhead - accepting cards requires PCI-DSS compliance and contracts with card network acquirers. Bank transfer via nrich uses your existing API credentials.

Bank transfer is the better fit when card fees are material (high-value purchases, B2B invoices), when chargeback exposure is a real concern (digital goods, lending repayments), or when you're running a platform with repeat collections or payouts and the percentage cost compounds over time.

How it Works

You can find a Step-by-Step guide depending on your use case in the following sections: Onetime Payment & Ongoing Payments.

One-time vs ongoing payments

Coverage

View full bank catalog - 3,381 banks across 33 countries →