# Visa Intelligent Commerce vs Mastercard Agent Pay for merchants

The two card networks’ programmes for AI agents side by side: how each recognises an agent, pays with a token, records what the shopper approved, and what changes at your checkout.

By Valerii Checha, 10 Nov 2026

Picture the order: a shopper tells an AI agent to buy a pair of running shoes under £120, and an hour later your store gets a card payment. Nobody typed a card number. The agent looked at your product page, filled in your checkout, and paid with a credential its card network issued for exactly this. Visa calls its version of that system Visa Intelligent Commerce. Mastercard calls its version Agent Pay.

For a merchant, the two do the same three jobs. Each lets your site recognise a registered agent by a signature on its requests, each pays you with a token in place of the shopper's card number, and each records what the shopper approved so there is evidence if the purchase is disputed. They differ in how much they have published: Visa's developer documentation is public and detailed, while Mastercard's merchant specification sits behind a developer portal we could not read.

Neither network has anything to do with Storewalk, the scanner we make, and both are quoted in their own words. If agent payments in general are new to you, [how an agent pays](https://storewalk.ai/blog/how-agents-pay) is the gentler starting point.

## What are Visa Intelligent Commerce and Mastercard Agent Pay?

Both are card-network programmes, so neither is a checkout you install. Visa describes Visa Intelligent Commerce (VIC) as "our strategic portfolio for the age of AI agents". Its developer page says VIC "enables Agent Providers, Wallet Providers, and Agent Enablers to securely conduct commerce on behalf of consumers using Visa credentials". The page lists it as available for use by "Merchants" and "Independent developers", yet the audience it describes is agent providers, wallets, agent enablers and "commerce platforms connecting directly to VIC".

Mastercard announced "its Agentic Payments Program, Mastercard Agent Pay" on 29 April 2025. Its product page calls Agent Pay "Mastercard's new infrastructure for enabling secure, scalable and trusted payments in agentic commerce", and says "Only registered agents can transact".

So the heavy lifting falls on the agent's side. On Visa's, the agent company onboards, enrols the shopper's card and asks Visa for a credential per purchase; Mastercard says agents are registered and verified "before they are permitted to transact on the Mastercard network". What reaches you is a signed request and a token. Here are the two, aspect by aspect:

Visa Intelligent Commerce and Mastercard Agent Pay, side by side in their own words.

What it is. Visa: Visa calls VIC “our strategic portfolio for the age of AI agents”. Its developer page: VIC “enables Agent Providers, Wallet Providers, and Agent Enablers to securely conduct commerce on behalf of consumers using Visa credentials.” Mastercard: Mastercard announced “its Agentic Payments Program, Mastercard Agent Pay” on 29 April 2025. Its product page: “Mastercard’s new infrastructure for enabling secure, scalable and trusted payments in agentic commerce.” Our reading: Both are card-network programmes for agents that pay with a shopper’s card. Neither is a checkout you install.

Sources: [Visa: Intelligent Commerce](https://www.visa.com/en-us/solutions/intelligent-commerce.html), [Visa Developer: Visa Intelligent Commerce, getting started](https://developer.visa.com/docs/visa-intelligent-commerce), [Mastercard: Mastercard unveils Agent Pay (29 Apr 2025)](https://newsroom.mastercard.com/news/press/2025/april/mastercard-unveils-agent-pay-pioneering-agentic-payments-technology-to-power-commerce-in-the-age-of-ai) and [Mastercard: Mastercard Agent Pay](https://www.mastercard.com/global/en/business/artificial-intelligence/mastercard-agent-pay.html).

Recognising the agent. Visa: The Trusted Agent Protocol: the agent signs its requests, tagged agent-browser-auth or agent-payer-auth, on a base of “HTTP Message Signatures defined by RCF 9421” (Visa’s typo) and “aligned with web-bot-auth”. Mastercard: “By implementing the emerging Web Bot Auth standard (as outlined in the framework) at the Content Delivery Network (CDN) layer, merchants can verify agent authenticity without deploying new code”. Our reading: Both lean on signed HTTP requests from the same IETF family, so one verifier at your CDN or bot manager may serve both.

Sources: [Visa Developer: Trusted Agent Protocol specifications](https://developer.visa.com/docs/trusted-agent-protocol/trusted-agent-protocol-specifications), [Visa: Visa Introduces Trusted Agent Protocol (14 Oct 2025)](https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21716.html) and [Mastercard: Agent Pay Acceptance Framework (14 Oct 2025)](https://www.mastercard.com/global/en/news-and-trends/stories/2025/agentic-commerce-framework.html).

The payment credential. Visa: VIC returns “The signed or encrypted network token, cryptogram, and ECI” for a purchase. “Cryptograms are one-time use with a 72-hour lifespan”. Mastercard: Agents transact “using agentic tokens - dynamic, cryptographically secure credentials that ensure every transaction is both traceable and authenticated.” Our reading: In our reading, either way your store is paid with a token in place of the card number, much as with a phone wallet.

Sources: [Visa Developer: Visa Intelligent Commerce concepts](https://developer.visa.com/docs/visa-intelligent-commerce/concepts) and [Mastercard: Agent Pay Acceptance Framework (14 Oct 2025)](https://www.mastercard.com/global/en/news-and-trends/stories/2025/agentic-commerce-framework.html).

What the shopper approved. Visa: A Purchase Instruction is “The agreed upon purchase intent between consumer and agent”, and a mandate holds “Consumer-defined spend parameters (declineThreshold, effectiveUntilTime)”. Visa “checks that the transaction’s merchant name matches any preferred merchant name set on that mandate”. Mastercard: Purchase intent data “Provides detailed visibility into the consumer’s intent”, “including cart contents, transaction limits and validity windows.” The product page lists “Verifiable intent”. Our reading: Both record limits the shopper set. Visa’s documents say the network checks them; Mastercard’s describe them as data a merchant can be given.

Sources: [Visa Developer: Visa Intelligent Commerce concepts](https://developer.visa.com/docs/visa-intelligent-commerce/concepts), [Mastercard: Agent Pay Acceptance Framework (14 Oct 2025)](https://www.mastercard.com/global/en/news-and-trends/stories/2025/agentic-commerce-framework.html) and [Mastercard: Mastercard Agent Pay](https://www.mastercard.com/global/en/business/artificial-intelligence/mastercard-agent-pay.html).

Your checkout. Visa: Visa says the protocol needs “minimal user experience (UX) changes required on merchant websites or checkout pages”, and its product chief speaks of “no-code functionality for merchants”. Mastercard: “trusted agents can then use existing checkout forms on merchant websites to submit a Dynamic Token Verification Code”, which Mastercard calls “an agentic token formatted for standard card payment fields”. Our reading: Both aim at the checkout you already have. Mastercard is the more specific: the agent types a token into your card fields.

Sources: [Visa: Visa Introduces Trusted Agent Protocol (14 Oct 2025)](https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21716.html) and [Mastercard: Agent Pay Acceptance Framework (14 Oct 2025)](https://www.mastercard.com/global/en/news-and-trends/stories/2025/agentic-commerce-framework.html).

Disputes. Visa: For every purchase type, Purchase Instructions are “Required to evidence the specific authorized transaction for disputes” (or instruction), and Signals are “Required to evidence agent execution context”. Mastercard: Purchase intent data “also provides the merchant with an audit trail that may be used to help avoid and/or resolve potential cardholder disputes.” Our reading: Both promise evidence. Neither page we read says how a chargeback over an agent purchase is decided.

Sources: [Visa Developer: Visa Intelligent Commerce concepts](https://developer.visa.com/docs/visa-intelligent-commerce/concepts) and [Mastercard: Agent Pay Acceptance Framework (14 Oct 2025)](https://www.mastercard.com/global/en/news-and-trends/stories/2025/agentic-commerce-framework.html).

A product for merchants. Visa: Intelligent Commerce Connect (8 Apr 2026), “Currently in pilot with select partners”, works “Through a single integration via the Visa Acceptance Platform” and accepts payments via “Trusted Agent Protocol, Machine Payments Protocol (MPP), Agentic Commerce Protocol (ACP), and Universal Commerce Protocol (UCP).” Mastercard: Agent Connect (9 Sep 2026): “a new solution that will help merchants, AI agents, digital platforms and payment providers easily connect and transact through a single integration”, “Beginning in the United States”. Our reading: Each has announced one integration for merchants that reaches several agents. Both are newer than the programmes they sit on.

Sources: [Visa: Visa Opens the Door to AI-Driven Shopping for Businesses Worldwide (8 Apr 2026)](https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.22276.html) and [Mastercard: Mastercard Agent Connect (9 Sep 2026)](https://www.mastercard.com/us/en/news-and-trends/press/2026/september/mastercard-gives-merchants-a-simpler-way-to-build--connect-and-s.html).

What is published. Visa: Developer documentation with “a three-environment progression: Sandbox, then Certification, then Production”. Its December 2025 release put US pilots “in closed beta”. The TAP specification carries no version label. Mastercard: Newsroom posts and product pages. Mastercard says it shares the framework “on Mastercard Developers”; that page served us only a script shell on 4 November 2026, so we have not read the merchant specification itself. Our reading: You can read Visa’s rules today. For Mastercard’s, ask your acquirer for the merchant specification.

Sources: [Visa Developer: Visa Intelligent Commerce, getting started](https://developer.visa.com/docs/visa-intelligent-commerce), [Visa: Visa and Partners Complete Secure AI Transactions (18 Dec 2025)](https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21961.html) and [Mastercard: Agent Pay Acceptance Framework (14 Oct 2025)](https://www.mastercard.com/global/en/news-and-trends/stories/2025/agentic-commerce-framework.html).

Visa launched its [Trusted Agent Protocol](https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21716.html) and Mastercard published its Agent Pay Acceptance Framework on the same day, 14 October 2025. Payments people agree on very little, so two networks reaching for signatures on one Tuesday is worth noticing.

## How does each network let a store recognise the agent?

Both use a signature on the agent's HTTP requests, from the same family of IETF work.

Visa's part is the Trusted Agent Protocol. The agent signs its request with a key Visa knows, and the signature carries a tag saying what the agent is doing: `agent-browser-auth` on a product page, `agent-payer-auth` at checkout. Visa bases it on "HTTP Message Signatures defined by RCF 9421" (the typo is Visa's) and says it is "aligned with web-bot-auth". The checks "can be performed independently by the Merchant or by a Site Protection Provider on behalf of the Merchant", which means your CDN or bot manager can do them for you.

Mastercard's framework uses Web Bot Auth directly: "By implementing the emerging Web Bot Auth standard (as outlined in the framework) at the Content Delivery Network (CDN) layer, merchants can verify agent authenticity without deploying new code". Mastercard says it "partnered with Cloudflare to support Web Bot Auth in Mastercard Agent Pay". Visa, for its part, says its protocol was "developed in collaboration with Cloudflare". Cloudflare is having a good year.

If you want the mechanics of signed agent requests, [Bots, crawlers and agents](https://storewalk.ai/blog/bots-crawlers-agents) walks through Web Bot Auth. For a store owner it comes down to where the check happens: the verification lives at the edge of your site, so the question is whether your CDN does it, and whether it is switched on.

## What changes at your checkout?

Visa says its protocol needs "minimal user experience (UX) changes required on merchant websites or checkout pages", and its chief product officer spoke of "no-code functionality for merchants".

Mastercard is more concrete. Once verified, "trusted agents can then use existing checkout forms on merchant websites to submit a Dynamic Token Verification Code", which Mastercard calls "an agentic token formatted for standard card payment fields". In other words, the agent types a token into the same card fields a person would use.

Visa's documents describe the agent's side of the same moment. Its purchase types table says checkout runs "Agent via browser automation" when the shopper approves each purchase, and "Agent via API or browser automation" when the agent acts within limits set in advance. What the agent gets back from Visa is "The signed or encrypted network token, cryptogram, and ECI returned for a purchase".

As we read the two programmes, an agent paying under either one still needs a checkout it can get through: a guest checkout, a card form it can fill, and a bot wall that lets a signed agent past. Step through what reaches you at each stage:

What reaches a merchant at each stage of an agent’s card payment.

Visa:

- 1\. Product page. What reaches you: A request whose Signature-Input carries tag="agent-browser-auth", signed over @authority and @path with the agent’s key. Who checks what: Visa: the checks “can be performed independently by the Merchant or by a Site Protection Provider on behalf of the Merchant.” What you can do (our reading): Ask your CDN or bot manager whether it verifies Trusted Agent Protocol signatures.
- 2\. Checkout. What reaches you: The same signature tagged agent-payer-auth. Visa says agents “have the option to carry payment data to support a merchant’s preferred checkout or payment method.” Who checks what: Visa’s spec: without either tag, “the message has not been signed by a trusted agent”, and the merchant “may decide to block the message or use some other mechanism”. What you can do (our reading): Keep guest checkout open to a signed agent rather than walling every automated visit.
- 3\. Payment. What reaches you: A network token, cryptogram and ECI that the agent fetched from VIC. Checkout runs “via browser automation” when the shopper approves each purchase, and “via API or browser automation” when the agent acts within limits. Who checks what: Visa checks the amount against the mandate’s declineThreshold and “that the transaction’s merchant name matches any preferred merchant name set on that mandate”. What you can do (our reading): Our reading: it reaches you through your acquirer like any token payment, so your payment provider decides whether you accept it.
- 4\. Afterwards. What reaches you: “Cryptograms are one-time use with a 72-hour lifespan”. “If the original transaction fails, a fresh credential can be requested once Visa is notified via the confirmation API.” Who checks what: Purchase Instructions are “Required to evidence the specific authorized transaction for disputes”. What you can do (our reading): Our reading: a declined agent payment can be retried, so a clear decline reason helps the agent more than a generic error page.

Mastercard:

- 1\. Product page. What reaches you: A request signed under Web Bot Auth. Mastercard says it “partnered with Cloudflare to support Web Bot Auth in Mastercard Agent Pay”. Who checks what: Verification sits “at the Content Delivery Network (CDN) layer”, so “merchants can verify agent authenticity without deploying new code”. What you can do (our reading): Ask your CDN whether it verifies Web Bot Auth for Agent Pay agents, and whether that is switched on for you.
- 2\. Checkout. What reaches you: The agent fills your existing checkout form with “a Dynamic Token Verification Code”, “an agentic token formatted for standard card payment fields”. Who checks what: Agents are registered first: “Only registered agents can transact”, by the product page. What you can do (our reading): Nothing new to build, if an agent can already fill in your card form. Worth testing once.
- 3\. Payment. What reaches you: An agentic token, “dynamic, cryptographically secure credentials that ensure every transaction is both traceable and authenticated.” Who checks what: The 2025 launch: “Every player in the value chain, from consumers to issuers and merchants, will be able to recognize the transactions that are facilitated by intelligent agents”. What you can do (our reading): Ask your acquirer whether it supports Agent Pay. At launch Mastercard said it “will work with acquirers and checkout players like Braintree and Checkout.com”.
- 4\. Afterwards. What reaches you: Purchase intent data, “including cart contents, transaction limits and validity windows.” Who checks what: It gives “an audit trail that may be used to help avoid and/or resolve potential cardholder disputes”, and the launch promised “a process to help clarify agentic transactions that may be unfamiliar or unrecognized.” What you can do (our reading): Ask how that data reaches you: in the authorisation, in your provider’s dashboard, or not yet.

The first two lines in each step are the network’s own words. “What you can do” is our reading of them.

Sources: [Visa Developer: Trusted Agent Protocol specifications](https://developer.visa.com/docs/trusted-agent-protocol/trusted-agent-protocol-specifications), [Visa: Visa Introduces Trusted Agent Protocol (14 Oct 2025)](https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21716.html), [Visa Developer: Visa Intelligent Commerce concepts](https://developer.visa.com/docs/visa-intelligent-commerce/concepts), [Mastercard: Agent Pay Acceptance Framework (14 Oct 2025)](https://www.mastercard.com/global/en/news-and-trends/stories/2025/agentic-commerce-framework.html), [Mastercard: Mastercard unveils Agent Pay (29 Apr 2025)](https://newsroom.mastercard.com/news/press/2025/april/mastercard-unveils-agent-pay-pioneering-agentic-payments-technology-to-power-commerce-in-the-age-of-ai) and [Mastercard: Mastercard Agent Pay](https://www.mastercard.com/global/en/business/artificial-intelligence/mastercard-agent-pay.html).

## What did the shopper approve, and who checks it?

Both networks keep a record of the shopper's limits, and they describe its use differently.

On Visa's side, a Purchase Instruction is "The agreed upon purchase intent between consumer and agent", and each one holds mandates with "Consumer-defined spend parameters (declineThreshold, effectiveUntilTime)". Visa checks those itself. It confirms the amount stays under the threshold and "checks that the transaction's merchant name matches any preferred merchant name set on that mandate". So a mandate can name the shop, and the network compares the payment with it. Instructions "default to a 30-day (US) intent expiration".

Mastercard frames it as data for the merchant. Its purchase intent data "Provides detailed visibility into the consumer's intent", "including cart contents, transaction limits and validity windows." Its product page lists "Verifiable intent", and Mastercard's September 2026 announcement says Agent Pay "uses Verifiable Intent", the AP2-compatible standard covered in [AP2 explained](https://storewalk.ai/blog/ap2-explained).

## How does a store check a Visa agent's signature?

Your CDN or bot manager should do this, but it helps to know what it is checking. Visa's specification gives the merchant a list of steps, and several need no key at all: the tag, the minimum fields, and the timestamps. Paste a `Signature-Input` value below, or load one of Visa's samples:

Check a Trusted Agent Protocol Signature-Input header against Visa’s merchant rules.

On the page, you paste a Signature-Input value (or load one of Visa’s samples) and the steps of Visa’s merchant verification that need no key run on it. Visa’s product-page sample, checked:

```http
Signature-Input: sig2=("@authority" "@path"); created=1735689600; keyid="poqkLGiymh_W0uP6PZFw-dvez3QJT5SolqXBCW38r0U"; alg="Ed25519"; expires=1735693200; nonce="e8N7S2MFd/qrd6T2R3tdfAuuANngKI7LFtKYI/vowzk4lAZYadIX6wW25MwG7DCT9RUKAJ0qVkU0mEeLElW1qg=="; tag="agent-browser-auth"
```

1. Tag is agent-browser-auth or agent-payer-auth: passes (tag="agent-browser-auth").
2. Minimum fields present: passes (All eight are there).
3. created and expires at most 8 minutes apart: fails (3600 seconds apart).
4. created in the past, expires in the future: not run (Needs a clock: the page runs this step against yours).

Visa: “the message should be blocked.”

What this page cannot check: a nonce seen in the last 8 minutes, the agent’s public key, and the signature over the request. Visa’s spec blocks the message on any of those too. Nothing you paste leaves the page.

Source: [Visa Developer: Trusted Agent Protocol specifications](https://developer.visa.com/docs/trusted-agent-protocol/trusted-agent-protocol-specifications).

Load Visa's own sample and it fails. Its `created` and `expires` are an hour apart, and Visa's rule says "if the interval between the created and expired timestamps is greater than 8 minutes … the message should be blocked." Sample data has never been good at following rules. The button that moves the times to now shows a header that passes the checks a page can run. The signature itself still needs the agent's public key, and that check belongs on a server.

## What happens when a purchase is disputed?

Both networks promise evidence.

Visa's concepts page says that for every purchase type, Purchase Instructions are "Required to evidence the specific authorized transaction for disputes", and Signals (the agent's order data) are "Required to evidence agent execution context". Its credentials are short-lived, too: "Cryptograms are one-time use with a 72-hour lifespan", and "If the original transaction fails, a fresh credential can be requested once Visa is notified via the confirmation API."

Mastercard says its purchase intent data "also provides the merchant with an audit trail that may be used to help avoid and/or resolve potential cardholder disputes." Its 2025 launch release also promised "a process to help clarify agentic transactions that may be unfamiliar or unrecognized."

Mastercard's sentence says "may", and neither network describes a dispute rule for agent purchases on the pages we read. The evidence is promised; how much it counts in a chargeback is not yet written down.

## Is either one live, and can a merchant sign up?

As of November 2026, neither network gives a merchant a sign-up form. What each has announced reaches stores through payment providers and pilots.

In December 2025 Visa said "hundreds of secure, agent-initiated transactions have now been successfully completed", with US pilots "executing end-to-end consumer and B2B purchases in closed beta" and pilots in Asia Pacific and Europe "anticipated to kick off in early 2026". In April 2026 it launched Intelligent Commerce Connect for businesses, "Currently in pilot with select partners", which works "Through a single integration via the Visa Acceptance Platform" and accepts payments made via "Trusted Agent Protocol, Machine Payments Protocol (MPP), Agentic Commerce Protocol (ACP), and Universal Commerce Protocol (UCP)."

At its 2025 launch, Mastercard said it "will work with acquirers and checkout players like Braintree and Checkout.com". In September 2026 it introduced Agent Connect, "a new solution that will help merchants, AI agents, digital platforms and payment providers easily connect and transact through a single integration", rolling out "Beginning in the United States" and "expected to evolve over time with additional capabilities, subject to market needs and product availability."

As of November 2026, Visa's VIC documentation carries no version or status label, and neither does Mastercard's product page. Mastercard says it shares its framework "on Mastercard Developers"; on 4 November 2026 that page served us only a script shell, so we have not read Mastercard's merchant specification. If you need its exact rules, your acquirer should have them.

## Who do you ask about what?

Most of this is in your providers' hands, so the useful work is a few questions to the right people:

| Question                                                                                | Ask                               | Why                                                                                                                               |
| --------------------------------------------------------------------------------------- | --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Do you verify Trusted Agent Protocol signatures, and Web Bot Auth for Agent Pay agents? | Your CDN or bot manager           | Visa lets a "Site Protection Provider" verify for you; Mastercard puts verification "at the Content Delivery Network (CDN) layer" |
| Will a verified agent get past our bot rules at checkout?                               | Your CDN or bot manager           | A signature that is checked and then challenged anyway helps nobody                                                               |
| Do you accept Visa Intelligent Commerce and Agent Pay tokens?                           | Your payment provider or acquirer | The token reaches you through your acquirer, as we understand it                                                                  |
| Can we see the shopper's purchase intent data, and where?                               | Your payment provider             | Mastercard calls it an audit trail for disputes                                                                                   |
| Is guest checkout open, and can an automated browser fill in our card form?             | Your own team                     | Both networks build on the checkout you already have                                                                              |

Our scan does not verify Visa or Mastercard signatures; nothing in it reads them. It checks the parts of your store both programmes rely on. [VER-001](https://storewalk.ai/checks/VER-001) asks whether bot management is present at all, [VER-003](https://storewalk.ai/checks/VER-003) whether checkout carries stricter controls than the product page, [TRX-001](https://storewalk.ai/checks/TRX-001) whether guest checkout is available, and [TRX-003](https://storewalk.ai/checks/TRX-003) whether your payment provider documents a way to accept a token an agent holds for the shopper. A token is no help to an agent that never reaches the card form, and [the reasons agents get stuck before payment](https://storewalk.ai/blog/why-agents-cant-buy) have an article of their own. [Scan your store](https://storewalk.ai/) before you write to your acquirer, and the email can be shorter.

## Frequently asked questions

### What is the difference between Visa Intelligent Commerce and Mastercard Agent Pay?

Very little, in what they do for a merchant: both recognise registered agents by a signature, pay with a token and keep a record of what the shopper approved. Visa checks the shopper's limits at the network; Mastercard describes them as data a merchant can be given. Visa's developer documentation is public; Mastercard's merchant specification sits on its developer portal.

### Do I need to integrate with Visa or Mastercard directly?

Not as a typical store. Both programmes are aimed at agent companies and payment providers. Visa's merchant product, Intelligent Commerce Connect (in pilot, as of November 2026), comes through the Visa Acceptance Platform, and Mastercard's Agent Connect is "a single integration" for merchants and their providers. Ask your payment provider which it supports.

### What is a Dynamic Token Verification Code?

Mastercard's name for "an agentic token formatted for standard card payment fields". A verified agent can enter it into your existing checkout form instead of a card number.

### What is Visa's Trusted Agent Protocol?

The part of Visa's programme a merchant sees: a signature on the agent's requests, tagged `agent-browser-auth` or `agent-payer-auth`, based on HTTP Message Signatures. Visa says the merchant or a site protection provider can verify it.

### Does Storewalk check for Visa or Mastercard support?

No check reads these signatures or tokens. What our scan does check is whether bot management, guest checkout and your payment provider leave room for an agent to pay.

The sources below were last checked on the date shown.

## Sources

- [Visa Developer: Visa Intelligent Commerce](https://developer.visa.com/docs/visa-intelligent-commerce)
- [Visa Developer: Visa Intelligent Commerce concepts](https://developer.visa.com/docs/visa-intelligent-commerce/concepts)
- [Visa Developer: Trusted Agent Protocol specifications](https://developer.visa.com/docs/trusted-agent-protocol/trusted-agent-protocol-specifications)
- [Visa: Visa Introduces Trusted Agent Protocol (14 Oct 2025)](https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21716.html)
- [Visa: Visa and Partners Complete Secure AI Transactions (18 Dec 2025)](https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21961.html)
- [Visa: Intelligent Commerce Connect (8 Apr 2026)](https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.22276.html)
- [Mastercard: Mastercard unveils Agent Pay (29 Apr 2025)](https://newsroom.mastercard.com/news/press/2025/april/mastercard-unveils-agent-pay-pioneering-agentic-payments-technology-to-power-commerce-in-the-age-of-ai)
- [Mastercard: Agent Pay Acceptance Framework (14 Oct 2025)](https://www.mastercard.com/global/en/news-and-trends/stories/2025/agentic-commerce-framework.html)
- [Mastercard: Mastercard Agent Pay](https://www.mastercard.com/global/en/business/artificial-intelligence/mastercard-agent-pay.html)
- [Mastercard: Mastercard Agent Connect (9 Sep 2026)](https://www.mastercard.com/us/en/news-and-trends/press/2026/september/mastercard-gives-merchants-a-simpler-way-to-build--connect-and-s.html)

Last checked 4 Nov 2026
