Bank on File vs Card on File: What Changes for Recurring Billing

Recurring revenue depends on a stored funding method you can charge again without asking the customer to re-enter details every cycle. Card on file is the default: you tokenise the PAN and bill through card networks. Bank on file means you hold a bank-account relationship — verified IBAN, consent token, or mandate — and collect on account-to-account rails. The choice changes fees, churn, disputes, and which ops playbooks you run. This comparison is neutral: many businesses keep both and route each customer segment to the rail that fits.

Bank on file: Storing a customer’s bank account as the funding source for future charges — after verification or a first pay by bank payment — and collecting repeat amounts via mandates, variable recurring payments, or scheme pulls, depending on country.

What card on file gives you

Card on file is familiar: checkout captures a card, your PSP tokenises it, renewals run until expiry, chargeback, or cancellation.

Strengths

• Global habit — customers know how subscriptions work
• Variable amounts are straightforward on most PSPs
• Broad acceptance for international B2C

Trade-offs

• Interchange and scheme fees on each success
• Expiry and replacement cards drive involuntary churn
• Chargeback processes your support team already knows — but cost remains

Cards stay the fallback while you pilot bank rails in markets where open banking coverage is strong.

What bank on file gives you

Bank on file is not one global product. It is an outcome: you can charge again from the customer’s account without a full checkout redirect every time. Implementation depends on region:

Region	Typical bank-on-file mechanism
UK	Variable recurring payments or Bacs Direct Debit after setup
Euro area	SEPA Direct Debit mandate after verification or first pay by bank
Nordics	National schemes plus SEPA where relevant

Strengths

• Lower variable cost per success on many eligible flows
• No card expiry — different churn profile
• Payer authenticates at bank during setup — strong for eligible use cases
• Clearer IBAN-level reconciliation for B2B

Trade-offs

• Bank and country coverage gates who you can enroll
• Setup UX is often a bank redirect, not a 16-digit field
• Variable amounts need VRP (UK) or mandate rules (SEPA) — not “type any amount anytime” everywhere
• Dispute and refund playbooks differ from cards

Side-by-side comparison

Dimension	Card on file	Bank on file
Customer setup	Card number / wallet	Bank app consent or mandate
Variable amounts	Widely supported	UK VRP or SEPA amendment rules
Typical fees	Interchange + scheme	Often lower per success on eligible A2A
Churn drivers	Expiry, insufficient funds	Mandate failure, consent revocation
Disputes	Chargebacks	Scheme/bank rules — not identical to cards
Coverage	Global cards	Per bank and country
PCI scope	Token via PSP	No PAN; still secure tokens and webhooks

Neither wins every segment. B2B invoices in Germany may favour bank rails; global B2C with small tickets may stay card-first.

When teams add bank on file

Common triggers:

1. Margin — subscription or usage revenue where interchange hurts unit economics
2. B2B trust — customers prefer paying from operating accounts
3. Verification bundled with billing — same provider confirms account then stores for debit
4. UK variable billing — VRP where banks support commercial collection
5. EU recurring stack — verify, first pay by bank, SEPA DD for renewals

Vertical playbooks overlap: e-commerce for repeat buyers, SaaS for annual contracts, utilities and insurance for variable premiums. Read recurring transactions via open banking for provider criteria by rail.

Operational differences your billing system must handle

Token lifecycle — Cards expire; bank consents revoke or hit limits. Your subscription engine needs webhooks for revocation and failure codes that map to dunning.

Retry logic — Insufficient funds behave differently; retry policies should not copy card rules blindly.

Reconciliation — Bank pulls often arrive with references and payer IBAN useful for finance; ensure billing IDs survive the flow.

Customer communications — “Update payment method” for bank on file may mean a new bank consent journey, not a card form.

Compliance copy — Mandate and consent wording is market-specific; legal review per country.

Hybrid strategy most teams ship

A practical default:

• Offer both at signup where coverage allows
• Default by segment — e.g. B2B EU → bank, global consumer → card
• Measure involuntary churn and cost per successful renewal per rail
• Pilot one plan tier before migrating enterprise contracts

Do not force bank on file without card fallback until conversion and pull success rates are proven.

Choosing infrastructure

Bank on file requires a licensed partner for verification, mandates, or VRP — you rarely wire every bank yourself. Shortlist on:

• Countries and banks your customers use
• Fixed vs variable recurring product
• Webhook quality and mandate lifecycle APIs

Use how to shortlist open banking providers and compare options via providers when you have a defined corridor.

Frequently Asked Questions

What is bank on file?

Bank on file means storing a customer’s bank account relationship so you can charge it again for renewals or invoices — via mandates, VRP, or other account-to-account mechanisms, depending on country.

What is the difference between bank on file and card on file?

Card on file tokenises a card for network billing. Bank on file collects from a bank account using consent or direct debit-style rails — different fees, churn drivers, and dispute paths.

Is bank on file cheaper than card on file?

Often lower variable cost per successful payment on eligible account-to-account flows, but setup coverage and ops matter. Model total cost including failed pulls and engineering.

Can bank on file handle variable subscription amounts?

In the UK, variable recurring payments can support variable amounts within consent limits. In the euro area, SEPA Direct Debit has amendment and notification rules — not identical to UK VRP.

Do customers still use cards if we add bank on file?

Yes — most businesses keep cards for segments or countries where bank coverage or UX is weaker. Hybrid is normal.

Is bank on file the same as open banking?

Open banking is often how you verify the account and obtain consent; bank on file is the business outcome of storing that funding method for repeat collection.

How do we migrate subscribers from card to bank?

Offer an incentive or clearer B2B UX, run a pilot tier, and measure churn. Never hard-migrate without fallback until pull rates are stable.

What providers support bank on file for recurring?

Depends on country: SEPA mandate, UK VRP, Nordic schemes. See recurring open banking providers and match on your banks.

Conclusion

Bank on file and card on file are two ways to power repeat billing — not a moral upgrade of one over the other. Cards win on global habit and variable simplicity; bank rails win on economics and reconciliation for many EU and UK segments when coverage fits. Store the right funding method per customer, align billing ops to webhooks and mandates, and pilot before you migrate revenue. When you are ready to compare who can deliver bank on file for your countries, start from recurring-focused criteria and a short provider list — not a one-size headline.