On this page · 12 sections
- What Visa announced on 17 November
- Who joined, by role
- What agentic ready means: Visa's four stages
- The two technical pieces: agentic tokens and Trusted Agent Protocol
- What merchants should do now
- How Agentic Ready relates to ChatGPT Wallet and Google UCP
- Klarna in Adyen Agentic checkout (20 November)
- Worked example: what a false decline on agent orders costs
- US and UK notes
- What Visa has not said
- How eCorpIT can help
- References
Summary. Visa extended its Agentic Ready programme to the acceptance side on 17 November 2026, opening it to merchants, payment service providers (PSPs), acquirers, B2B suppliers and commerce platforms. It launched with more than 140 participants, 19 of them named, including Adyen, Antom, Billtrust, Checkout.com, Fiserv, Global Payments, PayPal and Stripe; a corrected version of the release adds J.P. Morgan Payments. They join the 175+ issuers already testing across 45 markets, a phase that began in Europe, including the UK, on 17 March 2026. Agentic Ready is a readiness and testing programme inside Visa Intelligent Commerce, not a priced product: Visa publishes no fees and tells interested firms to contact their Visa representative. Its two technical anchors are the network tokens issuers provision for AI agents and Trusted Agent Protocol, Visa's signed-request scheme built on RFC 9421 HTTP Message Signatures. Visa calls the programme protocol-agnostic across ACP, UCP, AP2 and MCP, so it sits beneath ChatGPT Wallet and Google's Universal Commerce Protocol rather than competing with them. Our verdict for US and UK merchants: you do not need to join yourself. Before Black Friday on 27 November, six days away, ask your PSP how it handles agentic tokens, check that your CDN is not blocking signed agents, and brief your fraud team.
About this article. For ecommerce, payments and fraud leads at US and UK online merchants, and the engineers who run their checkout and edge. On 21 November 2026 we checked the announcement against the copies of the release on Visa's own newsrooms, Visa's programme and Intelligent Commerce pages, its UK and US newsroom releases, the Trusted Agent Protocol documentation on Visa's developer site, OpenAI's and Google's announcements and developer pages, the Klarna and Adyen release as distributed by Business Wire, and Stripe's US and UK pricing pages (the US page through an Internet Archive copy of 20 November 2026, because Stripe redirected us to a regional page). Visa's investor relations site refused our automated requests, and Visa's programme guide sits behind a partner sign-in, so neither was reviewed. This is general information, not payment, legal or fraud advice; vendors change terms, and no vendor paid for inclusion. Researched with AI assistance and checked against the primary sources listed in the references.
What Visa announced on 17 November
Visa published the release through Business Wire on 17 November 2026. Its US newsroom carries that version, listed under 18 November, without J.P. Morgan Payments. Visa then issued a correction, and the version on its corporate newsroom names J.P. Morgan Payments in the subhead and the acquirer section. Earlier phases come from Visa's March and April releases. The table sums up what the release and Visa's programme page say.
| Item | Detail | Status |
|---|---|---|
| Programme | Visa Agentic Ready, expanded to the acceptance ecosystem within Visa Intelligent Commerce | Confirmed |
| Launch participants | More than 140, with 19 named in the corrected release | Confirmed |
| Issuer side | 175+ issuers across 45 markets, testing with cards they issue | Confirmed |
| Earlier phases | Europe and the UK from 17 March 2026; Asia Pacific and Latin America from 29 April 2026 | Confirmed |
| What participants test | How agent-initiated transactions are recognised, authenticated and processed on existing infrastructure | Confirmed |
| Growth | More institutions, merchants and enablers expected to join during 2027 | Forward-looking |
| How to join | Contact your Visa representative; the programme page has a readiness assessment form | Confirmed |
| Fees | None published | Not published |
| Protocols | Protocol-agnostic across ACP, UCP, AP2 and MCP | Confirmed, programme FAQ |
Visa's FAQ explains the timing. It says agentic transactions are already live with major AI platforms and that payment-processing reliability is now the main barrier to scale; the aim is that the tokens issuers create for agents are processed reliably wherever people shop. Put plainly, issuers can already create agent credentials. The weak link is whether every acquirer, gateway and fraud stack handles them correctly.
Who joined, by role
Visa names 19 of the 140-plus launch participants, grouped by role, and does not publish the full list.
| Role | Named participants | What Visa says they are testing |
|---|---|---|
| Acquirers and financial institutions | Antom (Ant International), dLocal, Getnet, J.P. Morgan Payments, Moneris, Spreedly | Agentic network token transactions through authorisation and processing; J.P. Morgan is testing how tokens and Trusted Agent Protocol signals move across merchant, acquiring and network systems |
| Payment service providers | Adyen, Airwallex, Basis Theory, Checkout.com, Fiserv, Global Payments, PayPal, Stripe, VGS, Worldline | Recognising agent-initiated transactions, accepting network tokens and feeding agent signals into risk; PayPal is enabling its merchants to accept Visa agentic tokens through their existing PayPal integration |
| B2B commerce platforms | Billtrust, HighRadius, Versapay | Agent and business identity, payment instructions, controls and reconciliation for invoice payments |
Some partner statements in the release are specific enough to act on:
- Stripe says it is testing ways to recognise agent-initiated payments, tighten merchant controls and raise approval rates.
- Adyen names three tasks: recognising agent-initiated transactions, accepting network tokens reliably, and feeding agentic signals into its risk and fraud tools.
- Checkout.com describes extending existing checkout flows to agent payments, including identifying trusted agents.
- Fiserv lists agent discovery and checkout, tokenised payments, agent authentication, fraud management and post-purchase services.
- Billtrust builds on its October 2026 pilot with Visa and BILL, covered below.
The release also points merchants to the Visa Acceptance Platform for fraud protection, credential management and dispute management alongside the programme. Visa's FAQ sets expectations: PSPs and acquirers are the primary participants and the main route to merchants, merchants can take part through their provider or use the framework directly, and the first announcement includes only merchants already building connections into agent platforms. If you run an ordinary online store, your PSP is your way in.
What agentic ready means: Visa's four stages
Visa's programme page describes four stages in any agentic purchase: access, discovery and cart, payment, and post-purchase. Participants must meet requirements at each stage according to their business and role. The detailed programme guide sits on Visa's documentation site behind a partner sign-in, so the right-hand column below is our reading of Visa's public wording and the Trusted Agent Protocol specification.
| Stage | Visa's public description | What it likely means for a merchant (our reading) |
|---|---|---|
| Access | Enabling trusted agent access | Your CDN or bot manager recognises signed agents instead of blocking them |
| Discovery and cart | Product discovery and cart management | Agents can read product pages, stock, sizes and shipping costs |
| Payment | Token and cryptogram handling for agent-initiated transactions | Your PSP accepts agentic network tokens and passes agent signals to risk scoring |
| Post-purchase | Post-purchase servicing | Order status, returns and disputes work when an agent placed the order |
The two technical pieces: agentic tokens and Trusted Agent Protocol
Agentic network tokens
A network token stands in for the card number. In agentic commerce, issuers provision tokens for an AI agent acting for a cardholder. Visa's FAQ says the programme checks that existing payment stacks work reliably for agentic transactions, especially token and cryptogram handling. For most merchants that is a PSP job. Your questions are whether your PSP accepts these tokens today, whether it marks them as agent-initiated in dashboards and reports, and whether your stored-credential logic treats them correctly.
ChatGPT Wallet shows what arrives at checkout. OpenAI says that once the user approves a purchase, the payment network issues a token with its own card number, security code and expiry date, so neither the business nor the agent sees the real card details. That is a network token arriving through an ordinary card form.
Trusted Agent Protocol
Trusted Agent Protocol is how a merchant tells a Visa-approved agent from a scraper. Visa describes it as a cryptographic standard for separating legitimate agents from malicious bots and crawlers, and links sample code from its getting-started page. The merchant specification sets out:
- Standard. Agent recognition uses HTTP Message Signatures (RFC 9421), aligned with web-bot-auth, carried in
Signature-InputandSignatureheaders.
- Two interaction types. Signatures carry the tag
agent-browser-authwhen the agent views a product page andagent-payer-authat checkout.
- Freshness. The
createdandexpirestimestamps must sit no more than 8 minutes apart, and merchants can keep recent nonces to reject replays. A message that fails any check should be blocked.
- Keys. Public keys come from a well-known URL that Visa hosts.
- Three signatures. The agent recognition signature in the headers, an optional signed consumer recognition object (
agenticConsumer) for spotting a returning customer, and a signed payment container (agenticPaymentContainer) at checkout.
- Who verifies. The merchant, or a site protection provider such as a CDN or bot-management service acting for it.
- Optional. Merchants are not required to adopt it, and those that have not can ignore the signatures.
A browsing request from a trusted agent carries headers shaped like this. The values are our placeholders, with the expiry set 480 seconds after creation to stay inside the 8-minute rule:
Signature-Input: sig2=("@authority" "@path");created=1795219200;expires=1795219680;keyid="<key id from Visa's key directory>";alg="Ed25519";nonce="<random nonce>";tag="agent-browser-auth"
Signature: sig2=:<base64 signature>:
One caution for test suites: the browsing example in Visa's own specification uses created and expires values 3,600 seconds apart, which its 8-minute (480-second) rule would reject, so do not copy those values into a test that expects a pass.
The practical point: bot rules that rely on user-agent strings or IP reputation can mistake a legitimate agent for a bot. Signature verification at the edge is the cleaner fix. OpenAI also asks merchants to verify its agents' Web Bot Auth signatures at the CDN or firewall, and because both schemes build on RFC 9421, one verification path can serve both, although each operator publishes its own keys. Visa said in July 2026 that Cloudflare and Akamai support Trusted Agent Protocol implementation.
B2B: agents paying invoices
Visa, BILL and Billtrust announced on 20 October 2026 what they called the first live pilot of AI agents completing approved invoice payments through supplier portals. BILL's payment agent is registered through Visa's Trusted Agent Protocol and Agentic Directory and pays with tokenised credentials bound to the buyer's approved payment instruction. Billtrust uses the protocol to recognise and admit the agent, which Visa says can stand in for the CAPTCHA and other bot checks such portals have relied on. The pilot FAQ says the agent makes no payment decisions and only executes payments the buyer has already approved. HighRadius and Versapay are building similar flows within Agentic Ready.
What merchants should do now
There is no single Agentic Ready integration. What you do depends on your stack.
| Your setup | Do this now | You can skip |
|---|---|---|
| Online store on Stripe, Adyen, Checkout.com or PayPal | Ask your PSP whether it accepts Visa agentic tokens today, how it flags them and whether its fraud model scores them differently | Contacting Visa directly; new SDKs (none announced) |
| Enterprise with a direct acquirer such as J.P. Morgan Payments, Fiserv, Global Payments or Worldline | Ask about token and cryptogram handling for agent-initiated transactions and whether you can join testing | Waiting for a general availability date Visa has not set |
| Any store behind a CDN or bot manager | Ask your vendor about verifying Trusted Agent Protocol and Web Bot Auth signatures; log, then allow, verified agents | Allow-listing agent IP ranges by hand |
| B2B supplier with a card payment portal | Ask Billtrust, Versapay or HighRadius about agent access to your portal | Sharing portal logins with buyers' automation tools |
| PSP, acquirer or commerce platform | Join through your Visa representative; you are the primary audience | Nothing |
| Building agent-facing checkout on UCP or ACP | Choose the protocol by surface and confirm your PSP handles the tokens those surfaces send | A Visa-specific protocol layer |
A short checklist for the next two weeks:
- Ask your PSP five questions. Do you accept Visa agentic network tokens? Are they labelled as agent-initiated in reports and webhooks? Does your risk engine use agent signals? Are you in Agentic Ready? What changes for disputes on agent orders?
- Review edge rules. Find the rules that challenge or block automated traffic on product, cart and checkout pages. Agents visit both, which is why Visa defines separate browsing and checkout tags.
- Brief your fraud team. Agent orders can look unusual: cloud-browser IP addresses, fast form completion, no mouse movement. Agree a review path rather than an automatic decline.
- Tag agent orders. Where your PSP exposes it, add an order attribute for agent-initiated payments so finance and support can track approval, refund and dispute rates separately.
- Keep stored-credential logic tight. ChatGPT Wallet asks the shopper to approve each purchase. Do not save an agent token for later charges unless the flow explicitly supports it.
- Plan, do not build, for January. Writing signature verification into your own code and building native agent checkout are post-peak projects.
How Agentic Ready relates to ChatGPT Wallet and Google UCP
These are not competing choices; they sit at different layers of the same purchase. The table draws on Visa's programme page, OpenAI's Wallet announcement, Google's UCP guide and Google's Universal Cart launch post.
| Aspect | Visa Agentic Ready | ChatGPT Wallet | Google Universal Commerce Protocol (UCP) |
|---|---|---|---|
| What it is | Network readiness and testing programme | Consumer wallet used by OpenAI's dots agents | Open protocol for checkout in AI Mode in Search and Gemini |
| Run by | Visa, within Visa Intelligent Commerce | OpenAI, built with American Express, Chase, Mastercard and Visa | Google with industry partners; open source |
| Layer | Payment network and acceptance | Credential and consent | Agent-to-merchant communication |
| Merchant build | None mandated; work goes through PSP and edge | No plugin or product feed needed for browser access | Native checkout, or embedded checkout for approved merchants |
| What you receive | Agentic network tokens plus Trusted Agent Protocol signals | A network payment token per approved purchase | Tokenised payment through payment handlers on existing integrations |
| Availability | Issuers: 175+ in 45 markets; acceptance from 17 November 2026 | US ChatGPT Pro subscribers aged 18+ with eligible US-issued cards | AI Mode and Gemini; Universal Cart in the US since 15 October 2026 |
In plain terms: UCP and OpenAI's Agentic Commerce Protocol decide how an agent talks to your store. ChatGPT Wallet or Google Pay hold the shopper's credential and approval. Visa Intelligent Commerce supplies the agent token and the agent's signed identity. Agentic Ready tests that your acquirer, gateway and fraud stack process all of that correctly. Visa says merchants can offer agent checkout through whichever path they choose, and Google says UCP handles tokenised payments through payment handlers on existing integrations while you remain the merchant of record.
Our Universal Cart and UCP guide covers the endpoints, our ChatGPT Wallet guide covers CDN rules and fraud briefings, and our ACP vs UCP comparison covers the protocol choice. This article covers the network layer underneath all three.
Klarna in Adyen Agentic checkout (20 November)
Klarna and Adyen announced on 20 November 2026 that shoppers can now pay with Klarna when an AI agent checks out for them through Adyen Agentic, Adyen's agentic commerce suite. We read the release as distributed by Business Wire. It says:
- Klarna is the first non-card payment option in Adyen Agentic.
- Merchants already offering Klarna through Adyen can switch it on without new integration work.
- The agent shows the Klarna options the merchant already offers, such as paying in full, interest-free instalments or financing, and shoppers review and confirm each purchase.
- Adyen built it on Klarna's open payment handler, a published specification that any payment provider can use to add Klarna to agent checkout.
This sits outside Agentic Ready, which covers Visa card credentials, but it matters to the same merchants: agent checkout is no longer card-only. If buy now, pay later is a large share of your sales, ask your PSP when non-card methods reach its agent checkout. On Stripe's published prices, Klarna costs 5.99% + 30¢ per successful US transaction and from 4.99% + 35p in the UK, against 2.9% + 30¢ for US domestic cards and 1.5% + 20p for standard UK cards. Adyen's Klarna pricing was not on the pages we checked; our Stripe, Adyen and Checkout.com fee comparison covers card rates.
Worked example: what a false decline on agent orders costs
Volumes are illustrative. Fees are Stripe's standard online list prices, checked on 21 November 2026. Gross margin is assumed at 40%.
US store. 40,000 online orders a month at a $75 average order value, so $3,000,000 a month. Assume 1% of orders are agent-initiated: 400 orders. If risk rules wrongly decline 10% of them, that is 40 lost orders.
- Lost revenue: 40 × $75 = $3,000 a month.
- Stripe fee you would have paid per order: 2.9% × $75 + $0.30 = $2.175 + $0.30 = $2.475.
- Lost gross profit: 40 × ($75 × 0.40 − $2.475) = 40 × ($30.00 − $2.475) = 40 × $27.525 = $1,101 a month.
UK store. 12,000 orders a month at a £60 average order value, so £720,000 a month. A 1% agent share is 120 orders; 10% wrongly declined is 12 orders.
- Lost revenue: 12 × £60 = £720 a month.
- Stripe fee per order on a standard UK card: 1.5% × £60 + £0.20 = £0.90 + £0.20 = £1.10.
- Lost gross profit: 12 × (£60 × 0.40 − £1.10) = 12 × (£24.00 − £1.10) = 12 × £22.90 = £274.80 a month.
Disputes. Stripe charges $15.00 for each dispute received in the US and £20.00 in the UK. Five extra disputes a month from poorly handled agent orders add 5 × $15 = $75 or 5 × £20 = £100, before any lost goods.
Payment mix. The same $75 US order paid with Klarna on Stripe costs 5.99% × $75 + $0.30 = $4.4925 + $0.30 = $4.79 (rounded), almost double the $2.475 card fee.
The sums are small today, which is the point. The fixes are configuration and briefing work, cheap next to an agent channel that declines by default once volumes rise in 2027.
US and UK notes
- United States. J.P. Morgan Payments, which describes itself as one of the largest US merchant acquirers, appears in the corrected release alongside Fiserv and Global Payments. ChatGPT Wallet and Google Universal Cart both launched in the US, so US merchants will see agent orders first. Thanksgiving is 26 November and Black Friday 27 November.
- United Kingdom. The issuer phase launched first in Europe, including the UK, on 17 March 2026, and early issuers named then included Barclays, HSBC UK, Nationwide Building Society, Revolut and Banco Santander. Visa cited Europe's high use of tokenisation, passkeys and advanced authentication as the reason to start there. On 2 July 2026 Visa said agents were completing live purchases at European merchants including Frasers and lastminute.com, with every programme transaction authenticated by Visa Payment Passkeys to support Strong Customer Authentication compliance; the issuers named included Barclays, HSBC UK, Lloyds Banking Group, NatWest, Nationwide and Revolut. UK merchants should ask their PSP how agent-initiated payments are authenticated and flagged, and how that fits their existing authentication set-up.
- Both. Visa has not listed the 45 markets. Check with your PSP that your country is in scope.
What Visa has not said
- No pricing for joining or for agentic transactions.
- No full partner list. 19 of the 140-plus participants are named.
- No timeline beyond more participants joining during 2027.
- No rule changes on disputes, liability or chargebacks for agent-initiated transactions in the public material.
- Gated detail. The programme guide needs a Visa partner sign-in.
How eCorpIT can help
eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Through our application development services we build and harden checkout, payment and edge configurations for agent traffic, from Trusted Agent Protocol and Web Bot Auth verification at the CDN to tagging agent-initiated orders across PSP webhooks and order systems. Talk to us at /contact-us/.
Last updated: 21 November 2026.