# Pay by Bank: How A2A Payments Work for SaaS

> How pay by bank and account-to-account payments work, what they cost compared with cards, and where they fit in a global SaaS checkout.
- **Author**: Deepak Jangir
- **Published**: 2026-08-06
- **Category**: Payments, SaaS
- **URL**: https://dodopayments.com/blogs/pay-by-bank

---

A Dutch customer reaches your checkout, sees a card form, and leaves. Not because the price was wrong, but because paying a foreign software company by card is not what they do. They pay with iDEAL, and iDEAL is a pay by bank method.

Pay by bank, also called account-to-account or A2A payment, moves money directly from the customer's bank account to the merchant's without a card network in the middle. The customer authenticates in their own banking app, approves a specific amount, and the funds move over domestic payment rails.

For a SaaS business selling internationally, this is less an optimisation than a coverage question. In several large markets, bank-based methods are the default consumer payment behaviour and card-only checkout quietly caps conversion.

## How the Flow Actually Works

The mechanics differ by market, but the shape is consistent.

```mermaid
sequenceDiagram
    participant C as Customer
    participant M as Merchant checkout
    participant P as Payment provider
    participant B as Customer bank
    C->>M: Selects pay by bank at checkout
    M->>P: Creates payment intent
    P->>C: Redirects to bank selection
    C->>B: Authenticates in banking app
    B->>C: Confirms amount and payee
    B->>P: Sends authorisation result
    P->>M: Confirms payment status
    M->>C: Grants access to product
```

Three properties follow from that flow and they explain most of the trade-offs.

**Authentication happens inside the bank.** The customer approves the payment with the credentials and biometrics they already use. There is no card number to steal and no separate [3D Secure](https://dodopayments.com/blogs/3d-secure-3ds-payment-authentication) step bolted on afterwards.

**The payment is pushed, not pulled.** The customer instructs their bank to send money. With cards, the merchant pulls funds using stored credentials. That difference is why chargebacks work very differently here.

**Settlement is often near real time.** Many domestic rails clear within seconds, which is materially faster than card settlement cycles.

## Pay by Bank vs Cards: The Honest Comparison

| Dimension | Cards | Pay by bank |
| --- | --- | --- |
| Cost | Interchange plus scheme and processor fees | Typically lower, often a flat or near-flat fee |
| Settlement speed | Days, depending on the acquirer | Often seconds to same day on domestic rails |
| Chargeback exposure | High, with a formal dispute process | Low, because the customer authorised the push |
| Recurring billing | Native, using stored credentials | Requires a mandate scheme, not universally available |
| Failed payment recovery | Retries and account updater services work well | Weaker, since there is no credential to retry against |
| Geographic coverage | Near universal | Strong in specific markets, absent in others |
| Refunds | Standard and well understood | Supported but mechanics vary by scheme |

The trade is straightforward: lower cost and far lower dispute exposure, in exchange for weaker recurring billing support and coverage that is regional rather than global.

That last point is the one that determines strategy. Cards are the only method that works everywhere. Pay by bank works extremely well in particular markets, which makes it an addition to a checkout rather than a replacement for it. Our guide to [why localised payment methods increase conversion](https://dodopayments.com/blogs/why-localized-payment-methods-are-important-for-higher-conversions) covers the measurement side, and [payment localization and ARR](https://dodopayments.com/blogs/payment-localization-increases-arr) covers the revenue impact.

## The Major Schemes by Market

Pay by bank is not one system. It is a family of domestic schemes with different names and different capabilities.

| Market | Scheme | Notes |
| --- | --- | --- |
| Netherlands | iDEAL | Dominant consumer method, bank redirect flow |
| Belgium | Bancontact | Card and bank hybrid, app-based confirmation |
| Poland | Przelewy24 | Aggregates a large set of Polish banks |
| Austria | EPS | Bank transfer redirect |
| Portugal | Multibanco | Reference-based, customer pays after checkout |
| India | UPI | Real-time rails with a mandate scheme for recurring |
| Brazil | Pix | Instant transfers, extremely broad adoption |
| Eurozone | SEPA Direct Debit | Mandate-based pull, suited to recurring |
| US | ACH | Batch based, slower, used for higher-value B2B |

The European set is covered in depth in our [European payment methods guide](https://dodopayments.com/blogs/european-payment-methods-saas). For the two largest real-time markets, [UPI for global business](https://dodopayments.com/blogs/upi-payments-global-business) and [Pix for Brazilian SaaS](https://dodopayments.com/blogs/pix-payments-brazilian-saas) go into the specifics, including how each handles recurring mandates.

Multibanco deserves a specific warning because it breaks a common assumption. The customer receives a reference and pays it later, at an ATM or in online banking. The payment can arrive hours after checkout, so any flow that provisions access synchronously will appear broken. Handle it with [webhook-driven fulfilment](https://dodopayments.com/blogs/webhooks-payment-notifications) rather than a redirect-and-grant pattern.

## The Recurring Billing Problem

This is where pay by bank gets genuinely hard, and where most write-ups skip the detail.

A card gives you a reusable credential. You store a token and charge it again. A one-off bank push gives you nothing reusable. The customer authorised one payment, and there is no instrument to charge next month.

Three workarounds exist, with different coverage:

- **Mandate schemes.** [SEPA Direct Debit](https://dodopayments.com/blogs/what-is-direct-debit) in the eurozone and UPI AutoPay in India let a customer authorise future pulls. These are real recurring solutions, but they are regional and each has its own mandate rules and failure modes. [UPI AutoPay](https://dodopayments.com/blogs/upi-autopay) covers the Indian scheme in detail.
- **Invoice and re-authorise.** Send an invoice each cycle and have the customer approve a fresh payment. Reliable, but it converts a passive renewal into an active decision every period, which increases voluntary churn.
- **Bank method for acquisition, card for renewal.** Take the first payment through the local method to win the conversion, then collect a card during onboarding for renewals.

The third pattern is the pragmatic one for most SaaS businesses. It captures the conversion benefit where local methods dominate without giving up the retention benefit of stored credentials. It does require thinking about [involuntary churn](https://dodopayments.com/blogs/involuntary-churn-failed-payments) on the card leg, because a card added later is often a secondary card with a higher decline rate.

## Where the Chargeback Advantage Ends

Lower dispute exposure is real, and it is the strongest commercial argument for pay by bank in categories with elevated fraud. Because the customer authenticated in their own banking app and pushed the funds, the "I did not authorise this" claim that drives card disputes largely disappears.

It does not eliminate every risk:

- **Fraud still exists.** Authorised push payment fraud, where a customer is tricked into paying a criminal, is a growing problem and regulators in several markets have shifted liability toward banks.
- **Refunds are still your obligation.** A customer unhappy with the product is entitled to a refund under your policy and consumer law, whatever rail they used.
- **Mandate-based schemes reintroduce disputes.** SEPA Direct Debit allows customers to reclaim an authorised transaction within a defined window, and an unauthorised one for considerably longer. That is closer to a card chargeback than to an irrevocable push.

So the accurate statement is that one-off pushes carry very low dispute risk, and mandate-based pulls carry moderate risk. Treating all pay by bank as dispute-free leads to unpleasant surprises on the direct debit side. [What is a chargeback](https://dodopayments.com/blogs/what-is-a-chargeback-explained) covers the card baseline for comparison.

## Refunds and Reconciliation

Two operational realities catch teams that have only ever run cards.

**Refunds do not reverse the original transaction.** With a card, a refund follows the authorisation back along the same path. With most bank methods, the original payment was a push from the customer, so a refund is a fresh transfer from you to them. That has three consequences: it needs the customer's bank details, which you may not hold; it can take longer than a card refund; and it may carry its own transfer cost. Reference-based methods like Multibanco are the most affected, since there was never a stored instrument to credit.

**Reconciliation works on different identifiers.** Card settlements arrive in batches with a processor reference. Bank payments often arrive individually with a scheme reference that has to be matched back to an order. If your reconciliation logic assumes batched settlement with a single identifier, individual real-time credits will not match cleanly. Our [payment reconciliation guide](https://dodopayments.com/blogs/payment-reconciliation-saas) and [payment ledger design](https://dodopayments.com/blogs/payment-ledger-design) cover building a ledger that handles both shapes.

The practical implication is that fulfilment, refunds, and accounting should all key off the provider's payment identifier rather than off a card-shaped assumption. Where a provider settles all methods into one stream, this problem mostly disappears, because you reconcile against one settlement report rather than against each scheme individually.

## Adding It Without Rebuilding Checkout

The practical implementation question is whether you integrate each scheme individually or take them through a single provider.

Integrating directly means separate agreements, separate settlement, separate reconciliation, and in several markets a local entity or local bank account. That is a real engineering and legal programme, not a sprint.

Taking them through a provider that already holds those relationships means one integration and one settlement stream. Under a [merchant of record](https://dodopayments.com/blogs/what-is-a-merchant-of-record) model, the provider is the legal seller, which is also what makes it possible to offer methods that would otherwise require you to be locally established.

Dodo Payments supports 40+ payment methods across 220+ countries and territories with 80+ currencies at checkout, and methods surface based on customer location without per-market configuration. On the bank-rail side that covers the redirect and real-time methods discussed above, including iDEAL, Bancontact, EPS, Multibanco, Przelewy24, BLIK, UPI, and Pix. On the direct debit side, ACH Debit in the US and SEPA Direct Debit in the Eurozone are supported for one-time payments, while BACS Direct Debit is not available, and because neither rail is offered for subscriptions the mandate-based recurring path described earlier is not one you can run on Dodo Payments today. The [payment methods documentation](https://docs.dodopayments.com/features/payment-methods) lists current coverage, with dedicated pages for [European methods](https://docs.dodopayments.com/features/payment-methods/europe), [Indian methods including UPI](https://docs.dodopayments.com/features/payment-methods/india), and [Pix in Brazil](https://docs.dodopayments.com/features/payment-methods/pix). The [integration guide](https://docs.dodopayments.com/developer-resources/integration-guide) and [webhooks documentation](https://docs.dodopayments.com/developer-resources/webhooks) cover the redirect and asynchronous confirmation handling these flows require.

Two implementation notes that save time:

- **Test the redirect return path properly.** Bank redirects leave your site. A missing or wrong return URL is the most common reason a working integration looks broken. [Testing payment integrations in sandbox](https://dodopayments.com/blogs/test-payment-integration-sandbox) covers the setup.
- **Do not block on synchronous confirmation.** Treat the webhook as the source of truth for fulfilment, particularly for reference-based methods.

## FAQ

### Is pay by bank cheaper than card payments?

Usually yes. Bank rails avoid interchange and scheme fees, so the cost is typically lower and often closer to a flat fee than a percentage. The saving is largest on high-value transactions, where a percentage-based card fee scales but a flat bank fee does not.

### Can I run subscriptions on pay by bank?

Only with a mandate scheme such as SEPA Direct Debit or UPI AutoPay, and those are regional. A single bank push authorises one payment and leaves nothing reusable, so many SaaS businesses take the first payment via a local bank method and collect a card for renewals.

### Do pay by bank payments have chargebacks?

One-off push payments carry very low dispute risk because the customer authenticated with their own bank and initiated the transfer. Mandate-based schemes such as SEPA Direct Debit do allow customers to reclaim payments within defined windows, so those behave more like card disputes.

### Which markets should I enable first?

Start where a bank method is the default rather than an alternative: iDEAL in the Netherlands, Pix in Brazil, UPI in India, Przelewy24 in Poland, and Bancontact in Belgium. Check where your traffic already comes from before adding methods for markets you do not sell into.

### How long do funds take to settle?

Most domestic real-time rails such as UPI and Pix confirm within seconds. European bank redirects typically confirm quickly, though reference-based methods like Multibanco can take hours because the customer pays after leaving checkout. ACH in the US remains batch-based and slower.

## The Takeaway

Pay by bank is not a card replacement. It is the default consumer behaviour in a set of large markets, and card-only checkout loses those customers before the price is ever considered. Add the methods that match where your customers actually are, use webhooks rather than redirects to drive fulfilment, and plan the recurring path deliberately: a mandate scheme where one exists, and a card collected during onboarding where one does not.
---
- [More Payments articles](https://dodopayments.com/blogs/category/payments)
- [All articles](https://dodopayments.com/blogs)