Payments for the agentic era
Let agents pay.
Let the bank hold the limits.
Bank on File keeps a bank account, not a card, on file with a merchant. The customer sets the limits once, in their own banking app. Their bank enforces those limits on every payment an agent makes.
- Payee
- Talweg Outdoor GmbH
- Initiated by
- Shopping agent
- Max per payment
- €250.00
- Max per month
- €600.00
- Valid until
- 31 Dec 2027
- Revoke
- Any time, in bank app
The tent exceeds the €250 per-payment limit. The bank declines it before any money moves, so there is nothing to dispute.
See it in 30 seconds
Dinner, groceries and a declined sushi order
An AI agent orders food, buys the weekly groceries on its own budget and gets stopped by the bank when it overspends. The customer never types a card number.
- The agent shops. It compares restaurants and picks one inside the brief.
- The bank asks once. A push notification: approve your agent's purchase. One tap.
- The agent pays alone. Groceries bought within the weekly budget, with the balance shown.
- The bank says no. An order over the per-payment limit is declined before money moves.
The shift
Checkout was built for a human pressing “Pay”
AI agents now search, compare and buy on people's behalf. That removes the one moment every payment method was designed around: a person, present, approving a single purchase. The question for merchants is no longer how to make checkout faster. It is how a customer can delegate spending safely, and who enforces the boundaries when they do.
of transactions involve AI agents today, according to merchants surveyed.
Checkout.com, Agentic Commerce 2026of merchants say they are actively preparing for agentic commerce.
Checkout.com, Agentic Commerce 2026projected agentic commerce value in 2031, up from about $8bn in 2026.
Juniper Research, via American Bankerof UK open banking payments are already variable recurring payments.
FCA, 2025 open banking progressAlready happening
The agent is a new storefront, not a new payment
Agentic commerce does not have to wait for new payment rails. In Sweden it is already running on the bank payments people use every day.
A USB-C cable, bought by an agent, paid from a bank account
In October 2026 a shopper asked his AI assistant for the cheapest USB-C cable at Inet, a Swedish electronics retailer. Connected to Inet's store through its MCP server, the agent searched the range, offered a longer alternative, arranged free delivery to a parcel locker and asked before placing the order.
Inet's system then sent an ordinary Swish payment request. The shopper approved it with BankID, and the agent confirmed the order was paid. Swish changed nothing on its side. On 12 November Inet opened the service to all its customers.
What it shows: the agent did the searching, comparing and form-filling. The money moved only after an approval in the bank app, on a screen the agent cannot touch. That is Level 1. Bank on File is what lets the same trusted approval cover the next purchases, within limits, without a tap each time.
Get the cheapest USB-C to USB-C cable you can find.
Found a 25 cm cable for SEK 119, or 1 m for SEK 30 more. Free delivery to your nearest parcel locker. Place the order?
Yes, the 25 cm one.
Order placed. Approve the payment request in your Swish app.
Payment approved with BankID · order confirmed paid
Three levels of autonomy
The more an agent does alone, the more the limits matter
Agentic payments are not one use case. They range from an agent that only does the research to one that spends a budget on its own. Each step up moves trust away from the person at checkout and onto the rules set in advance.
The agent finds it. The person pays.
The agent compares options and hands over a ready basket. The customer picks their bank and approves the payment there, as they would today.
Works now with a standard pay-by-bank payment.
The agent proposes. The person taps once.
The agent builds the purchase and asks for a single approval. Because a mandate already exists with that merchant, there is no redirect and no re-authentication.
Bank on File turns a full bank journey into one tap, within a pre-agreed amount.
The person sets a budget. The agent spends it.
The customer defines caps by payment, period or category. The agent buys without asking and reports back afterwards.
Needs mandates that can span several merchants, which current frameworks do not yet support.
How it works
One consent, many payments, every one checked by the bank
Consent once
The customer approves a mandate in their own banking app, with the bank's strong authentication. The agent never sees a password or card number.
Set the limits
Maximum per payment, maximum per period and an end date. The limits live at the bank, not in the agent or the merchant's system.
Pay in the background
The merchant, acting on the agent's instruction, takes payments inside those limits without asking the customer to authenticate again.
Stay in control
The bank rejects anything outside the limits. The customer sees every mandate in their banking app and can cancel one without touching the others.
Cards vs bank
Card on file asks for trust. Bank on File sets the terms.
Cards are adapting to agents, and the card networks deserve credit for moving fast. But the underlying model still assumes the merchant charges reasonably and the customer disputes afterwards if not.
| Card on file | Bank on File | |
|---|---|---|
| Who enforces the limit | Mainly the merchant, under merchant-initiated transaction rules. Networks are adding agent tokens with spending controls. | The customer's bank, on every payment, against limits the customer set. |
| A payment outside the limits | Goes through, then gets disputed through a chargeback. | Rejected at execution, before money moves. |
| What the agent holds | A card number or a network token. | No payment credential. Consent sits with the bank. |
| Confirmation and settlement | Authorisation now, settlement in days, disputes open for months. | Confirmed in real time over instant payment rails. |
| Stopping one agent | Contact the merchant or replace the card. | Cancel that mandate in the banking app. Others keep working. |
| Cost to the merchant | Interchange and scheme fees on every payment. | No interchange. Typically flat or lower account-to-account pricing. |
The trade-off: card buyers are used to chargeback protection, and that habit is real. Bank on File answers it by preventing unwanted payments up front rather than refunding them later. Agentic commerce protocols such as Google's AP2 already list real-time bank transfers alongside cards as supported payment types.
The rails are ready
Bank on File already exists in Europe, under local names
Europe's national account-to-account schemes are adding the same building block: the customer approves once in their banking app, and the merchant collects later payments without asking again. The names differ by country. The model is the same.
Swish recurring payments
The customer signs a consent once with BankID, then payments run automatically and show up in the Swish app. Now offered by most of Sweden's large banks.
BLIK Recurring Payments
Consent is approved in the banking app, and later charges need no new BLIK code. Already used for subscriptions such as Netflix and ChatGPT.
Bizum recurring payments
Some Spanish banks already support recurring and merchant-initiated Bizum payments, with wider rollout expected during 2027.
Commercial VRP
The UK Payments Initiative launched its commercial variable recurring payments scheme in June 2026, backed by the largest UK banks. It lets customers authorise businesses to take payments within set limits.
Instant payments by law
Under the EU Instant Payments Regulation, euro-area banks must send instant credit transfers at the same price as standard ones, with a free payee name check.
Non-euro countries follow
Banks in Sweden and other non-euro member states must send instant euro payments and verify payees by 9 July 2027.
Still to solve
The open questions, stated plainly
Bank on File fits agents well in principle. These are the problems the industry still has to work through before it scales.
One merchant per mandate
Today a mandate names a single payee. A fully autonomous agent shops across many merchants, and no framework yet covers that.
Seeing agent payments
Payment data does not yet mark whether an agent started a transaction. That makes agent-specific risk models and clear bank statements harder.
Timing
Bank on File for everyday ecommerce is not yet broadly live. Agent adoption may move faster than the rails.
Network effects
Every major merchant accepts cards, and card networks are shaping agent standards. Bank payments need regulatory backing and merchant demand to keep pace.
For merchants
Three things to do this quarter
Add pay by bank now
Every customer who pays from their bank today is one who can approve an agent mandate tomorrow.
Ask your provider about Bank on File
Or its local equivalent: commercial VRP in the UK, Swish recurring in Sweden, BLIK Recurring in Poland, Bizum recurring in Spain. Ask which markets they cover and when.
Open your store to agents
Give agents what your website gives people: account sign-in, product search, an order summary with a short expiry, order placement that triggers your existing payment, and order status. Check prices and limits on your side, as you would for any browser.
Get in touch
Building agentic payments? Let's compare notes.
Ideas, questions, a use case you are testing or a story we should tell: write to us. Merchants, payment providers, banks and agent builders all welcome.
If the button does not open your email app, copy the address above.