Visa Mastercard PayPal Agentic AI Commerce: What UK Shops Can Use
No7 Engineering Team
Growth Architecture Unit

Agentic AI commerce is shopping in which an AI agent helps a customer discover products, decide and complete part or all of the purchase. That is close to how Visa describes agentic commerce, and the card networks and PayPal now publish merchant-facing pieces for it. Between them they cover recognising a trusted agent, accepting a credential made for agents and taking payment from an assistant.
In practice, most of the payment work sits with your acquirer or payment provider. The merchant's own job is narrower: let verified agents reach a checkout they can call.
What do Visa, Mastercard and PayPal each offer for agentic AI commerce?
The table maps each offer to the credential it uses, how the agent is checked and where a merchant starts. The sections below take each in turn.
| Provider | Agent credential | How the agent is checked | Where the merchant starts | UK status (October 2026) |
|---|---|---|---|---|
| Mastercard Agent Pay | Agentic Token, a tokenised credential for agent-initiated payments | Web Bot Auth headers; intent validation at Level 3 | Payment provider or Merchant Cloud | No regions listed; ask your acquirer |
| Visa Intelligent Commerce | Agent-specific token enrolled with Visa | Trusted Agent Protocol signatures, time bound and tied to merchant and purpose | Edge and bot rules, then the payment provider | May not be available in all markets; ask your acquirer |
| PayPal Agent Ready | Delegated token (ChatGPT) or single-use Google Wallet token (Google AI Mode, Gemini) | Not exposed to the merchant; PayPal handles security | Braintree | No regions listed; confirm with PayPal |
| PayPal Store Sync | None exposed; orders arrive in your existing order system | Not described in the Store Sync overview | Access request | Not available: US buyers in USD only |
Mastercard Agent Pay: agentic tokens and intent binding
Mastercard Agent Pay is Mastercard's framework for certified AI agents to conduct secure commerce transactions on behalf of consumers. Its credential is the Agentic Token, a tokenised payment credential provisioned specifically for transactions that AI agents initiate. That lets issuers identify and authorise agentic commerce flows.
Tokens come from the Mastercard Digital Enablement Service (MDES), a platform for issuers, wallet providers, merchants and other token requestors. For the checkout itself, Mastercard's agentic commerce guide tells merchants to validate agent identity through Web Bot Auth headers. At Level 3 of that guide, agents submit tokens in API request bodies and the payment object is validated directly. At that level, intent validation is required before checkout proceeds, and the payment token is bound to a verified intent ID.
Merchants on Mastercard Merchant Cloud can let Agent Pay handle the full payment process, including transactions, pages and payment details. For everyone else, in practice it is the acquirer or payment provider that decides which agent credentials reach the store. Mastercard's guide lists no regions, so ask your acquirer whether Agentic Tokens are live for UK cards.
Visa Intelligent Commerce and the Trusted Agent Protocol
Visa Intelligent Commerce is Visa's portfolio for agent payments. Its developer APIs come in two sets. Tokenization and authentication covers token provisioning and lifecycle, step-up verification of the cardholder and passkey management. Payment instructions and signals covers two stages. First an agent-specific token is enrolled and the user's instruction submitted. Then credentials are retrieved to fulfil it, and the purchase outcome is reported.
For a merchant, the nearer piece is the Trusted Agent Protocol. Visa notes that merchants, CDNs and bot-mitigation services have usually treated automated traffic as bots and blocked it. As agent use grows, merchants need to tell trusted shopping agents from malicious bots.
The protocol uses signatures that are specific to the merchant and purpose, time bound, and cannot be replayed or relayed. A signed request can state the agent's intent and carry consumer details, such as a loyalty account or a country and postal code. It can also shape payment details to the merchant's processing method. Visa says the protocol is still in development and deployment and may not be available in all markets, so confirm UK coverage with your acquirer.
The risk to plan for is your own edge. Bot rules that block every non-browser client will block a signed agent too; our guide to agentic commerce risks covers the controls to keep. Fix that before you chase any one programme.
PayPal Agent Ready and Store Sync
PayPal's agentic commerce services have two parts. Agent Ready lets merchants accept payments through AI assistants with minimal changes to their current payment setup, while PayPal handles security and compatibility across platforms.
The Agent Ready overview lists two integrations, both through Braintree. The Agentic Commerce Protocol integration serves ChatGPT: the customer authorises PayPal and your app receives a delegated token. The Universal Commerce Protocol integration serves Google AI Mode and Gemini: the customer pays with Google Wallet and Google returns a single-use payment token.
Store Sync makes products discoverable to AI shopping assistants and places orders into your existing order management system. Its eligibility rules matter for UK sellers. Per the Store Sync overview, only merchants selling physical goods to US customers in USD are eligible as of October 2026. You also need an existing PayPal merchant account, Orders v2 or a compatible Braintree setup, a shareable product catalogue and approved access from PayPal's AI team.
Where Stripe and OpenAI fit alongside the networks
Stripe's shared payment tokens (SPTs) give sellers scoped access to a customer's payment method for agent-initiated purchases. The token carries seller details and usage limits. SPTs are available in the US, Canada and select European countries, and Stripe links the full country list from that page.
The Agentic Commerce Protocol used by ChatGPT defines how a delegated payment reaches the merchant. OpenAI prepares a one-time delegated payment request. It sets a maximum chargeable amount and an expiry based on what the buyer selected in ChatGPT. OpenAI calls the provider's payment delegation endpoint, and the provider returns a token that OpenAI passes to the merchant to complete the checkout. OpenAI is not the merchant of record, and eligible cards are upgraded using network tokenisation. Our explainer on how ACP, MCP and UCP fit together covers the protocol side.
A worked example: a UK homeware store choosing its first route
Take a homeware store selling physical goods to UK customers in GBP, with cards on Stripe and PayPal running through Braintree. Walk it through the options in order.
- Store Sync: not available today, because the store sells in GBP outside the US.
- Agent Ready: the closest fit, since Braintree already carries its PayPal payments. The overview lists no regions, so confirm with PayPal that a UK store selling in GBP qualifies, and that the assistant's checkout is open to UK shoppers.
- Stripe SPTs: look the UK up on Stripe's linked country list before planning around them.
- Card network tokens: leave Agentic Tokens and Visa agent credentials to the acquirer, rather than integrating MDES or Visa's APIs directly.
- Edge rules: make sure the bot layer can let a signed agent reach the checkout API.
If the payment provider itself is up for review, our Adyen and Stripe comparison for UK stores covers the gateway decision. The checkout side is in our agentic checkout architecture guide.
What should you do first?
Start with the payment provider you already use, not with a network integration.
A first-pass checklist
- Ask your providers which agent programmes and credentials they support in your markets, and how agent payments handle strong customer authentication and disputes.
- Check regional rules for each programme against where your customers are.
- Fix the edge so verified agents can reach your checkout API while generic bots stay blocked.
- Decide where agent orders land in your order system, and how they are tagged.
- Ship one assistant surface end to end, once it is confirmed open to your customers' region, before adding the next.
If you want that scoped against your own stack, our ecommerce development team can map it.
Frequently Asked Questions
The questions buyers and engineers ask us most about this topic.
Do merchants need to integrate Mastercard Agent Pay or MDES directly?
Not necessarily. MDES serves issuers, wallet providers, merchants and other token requestors, so a direct integration is possible, but most stores take card payments through an acquirer or payment provider, which in practice decides which agent credentials reach the store. Merchants on Mastercard Merchant Cloud can let Agent Pay handle the payment process.
Can a UK merchant use PayPal Store Sync?
Not currently. PayPal's Store Sync overview says only merchants selling physical goods to US customers in USD are eligible, and access is by request through PayPal's AI team. Agent Ready, which takes payments from AI assistants through Braintree, is the separate service to check first.
What is Visa's Trusted Agent Protocol?
A Visa Intelligent Commerce specification that lets merchants tell trusted shopping agents from malicious bots. Agents send signatures that are specific to the merchant and purpose, time bound, and cannot be replayed or relayed. Visa says it is still in development and deployment and may not be available in all markets.