Case study · AI agent payments
AI agents are starting to pay. Is your bank ready to say yes, safely?
Visa and Mastercard now run live payments made by AI agents. This case study shows what an issuing bank must decide and build (consent, limits, agent identity, disputes and testing) with a 120-day pilot plan.
The situation
An AI agent that books travel or reorders supplies has to pay for them. The card networks are building the rails for that now.
- April 2025. Visa launched Visa Intelligent Commerce, giving developers tools to connect AI agents to its network.
- United States. Mastercard told investors that AI shopping agents had already completed purchases on its network and that its Agent Pay platform was rolling out in the US.
- July 2, 2026. Visa announced live agent payments across Europe, working with more than 30 European issuers. Each payment is authorised by the cardholder, with the agent acting inside set limits.
- 2026. Mastercard said Agent Pay would launch across Latin America and the Caribbean, with issuers enabled by February.
- Protocols. Google’s Agent Payments Protocol and OpenAI’s Agentic Commerce Protocol give agents shared ways to show what the user wants and who the agent is.
Milestones: from launch to live payments
Public announcements by the card networks
Visa launches Visa Intelligent Commerce, tools that connect AI agents to its network.
Mastercard says Agent Pay will launch across Latin America and the Caribbean in 2026.
Mastercard announces Agent Suite to help banks and merchants adopt agentic AI, available from the second quarter.
Target date for Latin American and Caribbean issuers to be enabled for Agent Pay.
Visa announces live agent payments across Europe with more than 30 issuers.
Most programs are pilots. Banks that set their rules now will be ready when volumes grow.
Most programs are still pilots. That is the right moment for a bank to set its rules, before the volumes arrive.
What it means for an issuing bank
Consent
Customers set and can see what an agent may buy, how much, where and until when, and can cancel it at any time.
Agent tokens
Agents pay with network tokens tied to that agent and that permission, never the real card number.
Identity
Know which agent is acting, and step up with passkeys when the request falls outside the permission.
Fraud
New patterns: bots posing as trusted agents, or an agent tricked by a malicious website into buying.
Disputes
Who is liable when an agent buys the wrong thing? Terms, dispute reasons and evidence must cover it.
Servicing
Apps and statements show which purchases an agent made, so customers and agents can check them.
How an agent payment works, and where the bank decides
The issuing bank’s checks sit in steps 1 and 4
The approach: a 120-day pilot
Days 1 to 20
Choose one use case and a small cohort
A low-risk case, such as repeat purchases from known merchants, for a small group of card holders who opt in. Choose the network program to join and agree the success measures.
Days 15 to 45
Design the permission and controls
Amount per purchase and per month, allowed merchant categories, an end date, an alert for every agent purchase, and a one-tap way to cancel.
Days 40 to 80
Build
Token set-up for agents through the network program, consent screens in the app, an agent label on every transaction, and a log of every agent action.
Days 60 to 100
Test like an attacker
Purchases just over the limit; an expired or cancelled permission; an unknown or fake agent; test web pages that try to trick the agent into buying; duplicate orders; refunds and disputes end to end; and accessible consent screens.
Days 100 to 120
Pilot and decide
Go live with the cohort, review approvals, declines, fraud and complaints every day, then hold a go/no-go on scaling.
Decisions the bank must own
| Decision | Owner | Evidence |
|---|---|---|
| Which agents, programs and protocols we accept | Agentic commerce product lead | Partner list, signed design |
| Default limits and merchant categories | Fraud and identity lead | Limit policy |
| Consent wording and liability | Legal and compliance lead | Terms, consent records |
| How agent purchases are disputed | Disputes operations lead | Dispute playbook |
| Pilot go-live | Head of digital | Go/no-go minutes |
Numbers to watch
Where I would start: write the dispute rules before the first agent purchase. Consent, limits and tokens are well covered by the networks; who pays when an agent gets it wrong is the question most pilots leave open.
Sources
- Digital Commerce 360: Visa Intelligent Commerce launch and Visa with OpenAI
- Digital Commerce 360: Mastercard Agent Suite, Jan 2026
- Digital Commerce 360: Mastercard on agent purchases and Agent Pay in the US
- Visa: live agent payments across Europe, Jul 2, 2026
- Mastercard: Agent Pay in Latin America and the Caribbean
- AI and Agent Payments Tracker
Get the case studies as a PDF, free
Take this case study and the other two with you, to share with your team.
- All three case studies with charts, plans, risks and controls (14 pages)
- Plus the Cloud vs On-Prem study of 29 US banks (10 slides)
Enter your email and confirm it. The download links arrive straight away.
I use your email to send the case studies and, now and then, payments insights. Nothing is sold or shared. Every email has a one-click unsubscribe link, and you can ask me to delete your details at any time at sp@paymentconsultant.top. Didn’t receive it? Check your spam folder, or email me and I’ll send it personally.
Want this plan for your bank or fintech?
I help banks and fintechs launch and change payment products safely: discovery, delivery plans, testing, release and go-live.
Book a 15-minute callOpen the AI agent payments trackerIndustry case study built from public sources and my payments delivery experience. It does not describe any client engagement. Figures are as published by the sources listed; general guidance, not legal advice.