07 — Wallets & Platform Players

Sibling sections: card networks are covered in 06-card-networks.md; pure‑crypto rails (x402, ERC‑8004, Crossmint, Catena, Skyfire) are covered in 05-protocol-deep-dive-x402-and-crypto.md; merchant‑side moves (Walmart, Etsy, Shopify UCP) are covered in 08-merchant-and-retail.md; regulation is deferred to 10-regulation-and-compliance.md. This section focuses on wallet and platform players — the consumer‑facing (PayPal, Apple Pay, Google Pay, Cash App, Samsung Pay, Shop Pay, Alipay/Antom, Klarna, Affirm, Revolut, Wise) and the developer‑facing platforms (Stripe, Block) that are either repackaging existing wallet rails for agents, or trying to invent new primitives for agent‑held value.

1. Three architectures: wallet‑centric, network‑centric, protocol‑centric

Before cataloguing players, it helps to name the three competing architectures because the same company often plays in more than one.

Network‑centric. The card network sits between issuer and acquirer and mints a new token for the agent. Agentic tokens, dynamic cryptograms, Visa Intelligent Commerce and Mastercard Agent Pay are canonical examples. The wallet is, in this view, a front‑end for a network‑issued credential that happens to be authorised for an agent. Analysed in 06-card-networks.md.
Wallet‑centric. A wallet — PayPal, Google Pay, Alipay, Cash App, Shop Pay — exposes the agent a scoped checkout capability from the user's existing funding sources (balance, bank account, linked cards). The wallet remains the consent surface, the SCA surface, the dispute surface, and (usually) the Merchant‑of‑Record (MoR) or the payment facilitator. Agents never see a PAN or an IBAN; they see a wallet handle and a one‑time intent token.[^1]
Protocol‑centric. An open protocol — AP2, ACP, x402, UCP — defines the message format for intent, cart and payment mandates but is formally neutral about who clears. The wallet is a pluggable role (a "Credential Provider" in AP2 terms). Stripe's ACP and Google's AP2 both explicitly architect this way.[^2][^3]

Wallet incumbents have a clear incentive to prefer the wallet‑centric framing, because it preserves their consent monopoly, their take rate, and their position as dispute of record. Agent builders and LLM platforms lean toward protocol‑centric, because they want to avoid lock‑in to any one wallet. Card networks split the difference: they promote their network‑centric tokens but publicly endorse AP2 and ACP to avoid looking like an enclosure.

The practical result, through Q1 2026, is that nearly every major wallet has announced an agent posture but very few have shipped a consumer‑facing, agent‑initiated payment at scale. This section is careful to distinguish announced, developer‑preview, and in production with real GMV.

2. PayPal — Agent Toolkit and MCP server

PayPal was the first major consumer wallet with a public, installable agent SDK. On 29 April 2025, at its "PayPal Dev Days" event in San Jose, PayPal announced the PayPal Agent Toolkit and what the press release described as "the industry's first remote MCP server" for a payment wallet.[^4]

2.1 What shipped

The Agent Toolkit is an npm package (@paypal/agent-toolkit) with a parallel Python release. It wraps the existing PayPal REST APIs as tool calls that an LLM can invoke natively in any of the supported frameworks. The documented framework bindings are:[^5]

OpenAI Agents SDK (Python and TypeScript)
Anthropic (via MCP and direct tool‑call format)
Vercel AI SDK
LangChain
CrewAI
A remote MCP server at the wallet boundary, callable from any MCP‑aware client

The domain of action is everything PayPal's REST API already exposes: create/capture/refund orders, list/send/cancel invoices, manage subscriptions, read transaction reports and disputes, look up shipment tracking, and manage a merchant catalog.[^5][^6] In other words, the Agent Toolkit is a merchant‑side SDK first — it empowers a merchant's agent to run its PayPal operation conversationally — and a consumer‑side SDK second, in the sense that a consumer agent can initiate a PayPal checkout by constructing an order and handing the approval URL back to the user.

2.2 What did not ship on 29 April 2025

The April 2025 launch did not ship an autonomous consumer agent. A human is still the consent gate: the Toolkit's orders.create tool returns an approval URL, and the end user must click through and satisfy PayPal's OTP step‑up. PayPal's own release emphasises this: "When consumers securely check out, they must perform a one‑time password (OTP) identity check to verify their purchase."[^4] In AP2 vocabulary (see 03-protocol-deep-dive-ap2.md), PayPal's Dev Days product is a Human‑Present (HP) flow with an agent building the cart, not a Human‑Not‑Present (HNP) mandate flow.

2.3 Mastercard Agent Pay × PayPal (27 October 2025)

Six months later, on 27 October 2025, PayPal and Mastercard announced an expansion of their long‑standing card‑issuing partnership into agentic commerce. Mastercard Agent Pay will be integrated into the PayPal wallet so that a consumer asking an AI agent to "buy running shoes" can check out with PayPal wherever PayPal is accepted on an "agent platform or agentic chat experience."[^7] The press release includes a worked example ("Tom wants to buy new running shoes…") where the agent detects that the merchant accepts PayPal and that Tom's PayPal has a Mastercard on file; Tom then does a single SCA step and the agent completes the order.[^7]

Structurally, this is the wallet‑centric architecture: PayPal stays the consent surface and the MoR‑style dispute owner, but Mastercard's Agent Pay tokenisation (see 06-card-networks.md) replaces the old card‑on‑file credential with an agent‑scoped dynamic token. As part of the deal, PayPal agreed to pilot the Mastercard Agent Pay Acceptance Framework, i.e. the verification/data‑exchange format Mastercard wants merchants to accept as proof of legitimate agent traffic.[^7]

2.4 Business model: still MoR, still fees

Importantly, PayPal's agent posture does not alter its unit economics. PayPal Agent Toolkit calls the standard Orders API, which settles at PayPal's standard merchant discount rate (approximately 2.99% + fixed fee for domestic US card‑funded PayPal transactions as of 2025). The Toolkit itself is free; revenue accrues on the underlying transaction. PayPal remains the payment facilitator in the Visa/Mastercard sense and retains buyer‑protection and dispute responsibility. There is no agent‑specific price point, no per‑agent subscription, and no new MID tier for agents — at least nothing PayPal has disclosed by April 2026.

3. Stripe — two hats at once

Stripe's agentic strategy is bifurcated and worth separating.

3.1 Hat #1 — Merchant‑of‑record facilitation via ACP

Stripe is the cryptographic core of the Agentic Commerce Protocol (ACP) that OpenAI announced on 29 September 2025 for "Instant Checkout in ChatGPT." The key primitive is the Shared Payment Token (SPT) — a delegated, single‑use payment credential minted by Stripe and scoped to a particular cart, merchant, buyer and agent session. ACP is dissected in 04-protocol-deep-dive-acp.md; here we note only Stripe's wallet/platform posture: when a ChatGPT user checks out at Etsy, Shopify sellers, or (from 14 October 2025) Walmart, Stripe is the payments platform that materialises a usable card credential from the user's saved Stripe Link wallet or a newly entered card, and the merchant remains the Merchant‑of‑Record.[^8][^9]

Stripe's Agent Toolkit (repo: github.com/stripe/agent-toolkit) is the dev‑side twin of PayPal's: a Python and TypeScript SDK, a hosted remote MCP server at mcp.stripe.com (OAuth‑authenticated), and integrations with OpenAI Agents SDK, LangChain, CrewAI and Vercel AI SDK.[^10] Tool permissions are explicitly controlled by a Restricted API Key (RAK), letting a developer scope the agent to only those Stripe operations (e.g. charges.create but not payouts.create) the agent is authorised for.[^10] Stripe recommends RAK over the root secret key for any agentic deployment.

3.2 Hat #2 — Stripe Issuing for agents ("Agent‑issued cards")

Stripe's second hat is fundamentally different: instead of facilitating merchant acceptance of agent‑initiated transactions, Stripe Issuing lets developers mint virtual cards that the agent itself holds and spends. This pattern — "give the agent its own card with a cap" — first surfaced in Stripe customer blog posts in late 2024 and early 2025 and was formalised in the "adding financial capabilities to AI agents" narrative Stripe pushed at Sessions 2025.[^11][^12]

Capabilities, as documented on the public Issuing and Agent Toolkit pages:[^11][^12]

Single‑use virtual card numbers minted per agent task, destroyed after use.
Per‑card spending controls: hard dollar caps, date windows, merchant category code (MCC) allow/deny lists, merchant‑ID‑level controls.
Real‑time authorisation webhooks so the developer's code — not just Stripe — can approve or decline a given agent‑initiated auth based on whatever policy (the user is offline, the cart exceeds an LLM‑summarised budget, the merchant is on an internal blocklist, etc.).
Instant freeze/cancel via a single API call or an MCP tool.
Stablecoin‑backed multi‑currency cards via Stripe's acquisition of Bridge (closed Q4 2024), letting a USDC balance back a Visa card the agent uses globally.[^12]

This is architecturally the inverse of the wallet‑centric model: there is no upstream wallet consent surface at spend time. The consent surface is the card‑issuance step, in which the user (or the developer on their behalf) sets the mandate — amount, time window, MCC list — and the agent then transacts freely within that envelope. In regulatory terms (see 10-regulation-and-compliance.md), it is closer to a corporate T&E card issued to an employee than to a consumer wallet checkout: the user has delegated authority and the agent is the cardholder‑of‑record for that single transaction.

Stripe's current competitive advantage on Hat #2 is that the Issuing API and the Agent Toolkit share the same authentication, the same RAK, and the same MCP endpoint — so a developer can mint a card and spend it from the same agent without a second KYC stack.

4. Block / Cash App — agentic infrastructure, not yet agentic checkout

Block's 2025–2026 agent story is different in kind from PayPal's or Stripe's. It is less about exposing Cash App to external agents and more about using agents inside Block.

Goose, Block's open‑source agent framework (released mid‑2024 and heavily developed through 2025), is the internal orchestrator. Block's CTO Dhanji Prasanna told Forbes in November 2025 that "automating all of Block" — including Cash App — is the company's top priority, and that agents had already absorbed substantial portions of customer service, refund, risk‑review and engineering workloads.[^13]
Workforce implications. In January/February 2026 Block cut roughly 40% of headcount (≈4,000 roles), citing agentic automation as the enabler; Jack Dorsey personally framed the shift as existential for the company.[^14]
Cash App "Moneybot" and adjacent features surfaced in the Q4 2025 earnings call as the consumer‑facing productisations: proactive, conversational financial guidance rather than open‑world shopping. Cash App had 59 million monthly actives at year‑end 2025, 9.3 million of whom used it as a primary bank account.[^15]

What Block has not publicly shipped as of April 2026 is a third‑party‑callable Cash App agent SDK, an MCP server, or an analogue to PayPal's or Stripe's Toolkit. Cash App's Bitcoin and USDC rails are technically amenable to x402‑style machine‑to‑machine payments, and Block has been a visible public advocate of Bitcoin Lightning for micropayments (TBD / Web5 efforts), but none of this has been packaged as an "agent wallet" product a ChatGPT or Gemini integration could call. Block's agentic push is, today, an internal efficiency story more than an agent‑commerce story.[^13]

5. Big‑tech wallets: Google Pay, Apple Pay, Samsung Pay

5.1 Google Pay / Google Wallet — the AP2 reference wallet

Google's Agent Payments Protocol (AP2) was announced on 16 September 2025 as an open protocol with >60 launch partners, including American Express, Mastercard, PayPal, Affirm, Coinbase, UnionPay, Adyen and Worldpay.[^16][^17] Google Pay (renamed Google Wallet on Android) is positioned as the reference Credential Provider for AP2: Google has published reference code showing how a wallet ingests Intent Mandates, surfaces them in the Wallet UI for user confirmation, emits a signed Cart Mandate, and participates in the Payment Mandate for authenticated agent presence signalling.[^16]

Concretely, by April 2026 Google had:

Shipped the AP2 protocol spec and reference code at github.com/google-agentic-commerce/AP2.[^16]
Integrated AP2 primitives into Android's Credential Manager so that any Android app can receive an AP2 mandate and display a native consent sheet.
Demonstrated, but not generally released, agent‑initiated Google Wallet transactions at Google I/O‑adjacent events.

What is not yet live is a consumer‑shipping surface: you cannot, as of April 2026, tell Gemini to "buy me running shoes" and have Google Wallet actually settle the transaction without a human‑in‑the‑loop Wallet sheet appearing on‑device. Google has been explicit that consumer roll‑out will track merchant AP2 adoption, and — tellingly — the Universal Commerce Protocol (UCP) that Google and Shopify announced at NRF January 2026 reuses AP2's mandate format as its consent layer (see 08-merchant-and-retail.md).

5.2 Apple Pay — conspicuously silent

Apple has made no public agentic‑payments announcement as of 21 April 2026. There is:

No Apple Pay developer SDK for agents.
No MCP server or Anthropic tool adapter from Apple.
No listing of Apple among the AP2, ACP, Agent Pay, Visa Intelligent Commerce, or UCP launch partners.

Apple's silence is consistent with its general stance — a private, on‑device AI (Apple Intelligence) with extremely tight scopes and a historical reluctance to expose Apple Pay credentials to third parties beyond the one‑tap merchant sheet. Passkeys and on‑device Secure Enclave signing give Apple a plausible long‑term AP2‑compatible primitive (a mandate signed by the Secure Enclave would be the natural Apple form), but until Apple chooses to ship something, wallet‑centric agentic commerce on iOS is effectively blocked at the OS level: third‑party agents cannot invoke Apple Pay programmatically, and Apple Pay cannot be a Credential Provider for an AP2 or ACP flow initiated by a non‑Apple agent. This is perhaps the single biggest unresolved question in the wallet landscape.

5.3 Samsung Pay / Samsung Wallet

Samsung's posture is intermediate. Samsung Wallet runs on both Samsung MST and NFC and has a long partnership history with Visa and Mastercard; in the Mastercard Agent Pay April 2025 launch, Samsung was not named as a launch partner, and Samsung has not issued a standalone agentic‑commerce announcement. However, because Samsung Wallet provisions Mastercard (and Visa) tokens via standard EMV tokenisation, any agentic token minted via Mastercard Agent Pay or Visa Intelligent Commerce will, in principle, be provisionable into Samsung Wallet without a new Samsung product being needed. Samsung's public 2025 AI narrative has centred on Galaxy AI features (Circle‑to‑Search, live translate) rather than on agent‑initiated commerce.

6. BNPL: Klarna and Affirm

6.1 Klarna — AI‑native rhetoric, limited agent shipping

Klarna CEO Sebastian Siemiatkowski has been the loudest BNPL voice on AI since 2023, and his public statements escalated through 2025. Klarna's public positioning includes: the company describes itself as an "AI‑native super app";[^18] Siemiatkowski told CNBC in June 2025 that AI would let Klarna "abstract and adapt the [commerce and payment] experience much more to the specific user you're dealing with";[^19] and Klarna's Q1 2025 release claimed its AI assistant had done the work of ≈700 agents, a figure that featured prominently in Sam Altman–led OpenAI case studies.[^20] Klarna later acknowledged in mid‑2025 that it had "overpivoted" on AI customer‑service automation and was rehiring humans for premium support tiers.[^21]

Concrete agent‑commerce shipping from Klarna is thinner than the rhetoric. By April 2026 Klarna is:

A named participant in Google AP2's launch cohort of ≥60 partners.[^17]
A BNPL option offered inside some ChatGPT Instant Checkout merchants via Stripe's ACP; Klarna is integrated at the acceptance layer rather than being the agent wallet.
Running internal AI assistants (Klarna's shopping assistant, powered by OpenAI, launched 2023) that can search and surface product offers but still hand off to a human‑confirmed checkout.

6.2 Affirm

Affirm's agent commitments are more concrete than Klarna's. Affirm announced in October 2025 that it was extending its partnership with Google as a formal supporter of AP2, with BNPL terms expressible inside AP2 Payment Mandates.[^22] In parallel, Affirm extended its Stripe partnership to consume Shared Payment Tokens — meaning an ACP flow can originate an Affirm loan without the agent ever seeing the consumer's underlying card or banking credential.[^23] Affirm's CEO has framed this as getting BNPL "wherever the consumer chooses to shop — whether by bot, browser, or voice assistant."[^23]

For both Klarna and Affirm, the core technical question is how BNPL underwriting integrates with a mandate: a BNPL decision is a credit decision that has historically required a live consent event (Klarna's or Affirm's app showing you the instalment plan). The AP2 Cart Mandate lets a BNPL provider bake the instalment terms into the user‑signed cart, preserving consent symmetry. Both Klarna and Affirm therefore prefer the protocol‑centric architecture to the wallet‑centric one: it keeps them in the checkout without requiring them to be the sole wallet.

7. Alipay / Ant International — Antom

The most important Asian data point is Antom, Ant International's merchant payments brand (distinct from consumer Alipay). On 5 September 2025, Antom announced an Agentic Payment Solution, described as the first productised agentic commerce stack from a major Chinese wallet group.[^24] Key elements:

EasySafePay direct‑link checkout. Alternative‑payment‑method (APM) wallets — including Alipay, GCash, Kakao Pay, Touch 'n Go — can be invoked inline inside an agent conversation without the classic deep‑link redirect out of the chat surface.[^24]
Mastercard and Visa pilots. Antom is one of the first merchant payment partners piloting Mastercard Agent Pay Acceptance Framework and Visa Intelligent Commerce, positioning it as the primary bridge between Chinese/South‑East Asian APMs and the Western card‑network agentic schemes.[^24]
MCP‑based architecture. Antom has open‑sourced the integration as an MCP server so that any AI agent can discover the agentic payment tool set.[^24]
MPC‑based risk engine. Antom's fraud layer uses multi‑party computation so that user identity signals and device signals are evaluable without exposing raw data to the agent or to the LLM vendor.[^24]

Antom is the only major player that is simultaneously a wallet‑centric solution (because Alipay's APMs are ultimately wallet credentials) and a network‑centric solution (via its Mastercard and Visa pilot), and the only one with a production open‑source MCP wallet surface by Q1 2026. The geopolitical caveat is that Ant International's reach is global but Alipay proper is PRC‑centric; how Antom's agentic stack will interact with China's domestic regulatory environment for AI agents remains unclear.

Consumer Alipay itself (the 1‑billion‑user super‑app) has added AI assistants (Alipay's "Zhi Xiao Bao") that surface inside the app, but Alipay has not — as of April 2026 — released a third‑party agent SDK equivalent to PayPal's or Stripe's.

8. Revolut, Wise, and the European digital wallet fringe

Revolut. In late‑2025 / early‑2026 Revolut rolled out AIR ("AI Revolut"), an in‑app financial assistant that can provide spending insights, block/unblock cards, manage subscriptions, and trigger money moves. Revolut has publicly stated that AIR does not retain user data and is not used for external model training.[^25] Revolut is building additional agents for contact‑centre, sales, and voice interactions. Critically, Revolut's agent‑initiated payments — an agent autonomously moving money to third parties based on user delegation — remain gated behind UK/EU regulatory review; the CEO, Nik Storonsky, told the press that Revolut's agentic capabilities are "throttled by what regulators let us ship," an explicit nod to PSD2 Strong Customer Authentication (SCA) constraints.[^26]
Wise. By April 2026 Wise has made no comparable public agent announcement. Wise's product surface — batch international payouts, multi‑currency accounts — is a natural fit for agent automation (an agent that pays suppliers in 30 currencies), but Wise has not shipped a dedicated agent SDK, has not joined AP2 or ACP as a named launch partner, and has not announced any Mastercard Agent Pay integration for its card.
PSD3 / SEPA context. The broader European wallet story is shaped by the PSD3 proposals and the EPI "Wero" wallet roll‑out. PSD3's clarifications on delegated authority and SCA exemption categories are critical for any wallet‑centric agent flow in the EEA; this is developed in 10-regulation-and-compliance.md. The European Central Bank's digital euro, if it ships with a programmable consent primitive, could become a wallet‑neutral agent‑native rail; but as of April 2026 the digital euro is still in preparation phase and has no published agent API.

9. Comparison: wallet capabilities for agent‑initiated transactions (April 2026)

Wallet / Platform	Agent SDK released?	MCP server?	AP2 support?	ACP support?	Mastercard Agent Pay	Visa Trusted Agent	Agent‑held cards?	HNP flow (no live user)?
PayPal[^4][^7]	Yes (Apr 2025)	Yes, remote	Launch partner	Via merchants	Yes (Oct 2025 pilot)	—	No	No (OTP required)
Stripe[^10][^11]	Yes (2024)	Yes, `mcp.stripe.com`	Compatible	Co‑author	Partner	Partner	Yes (Issuing)	Yes (Issuing)
Cash App / Block[^13]	No (Goose is internal)	No public	—	—	—	—	No	No
Google Pay / Wallet[^16]	Reference impl	Yes	Reference wallet	Compatible	—	—	No	Yes (on‑device)
Apple Pay	No	No	—	—	—	—	No	No
Samsung Pay / Wallet	No	No	—	—	(token provisioning only)	(token provisioning only)	No	No
Klarna[^17]	No	No	Launch partner	BNPL option	—	—	No	Partial
Affirm[^22][^23]	No	No	Launch partner	SPT integrated	—	—	No	Partial
Alipay / Antom[^24]	Yes (Sep 2025)	Yes, open‑source	Compatible	Compatible	Pilot	Pilot	No	Yes
Shop Pay (Shopify)[^27]	Agentic Plan (2025)	Via ACP / UCP	UCP co‑author	Instant Checkout	—	—	No	No (one‑tap confirm)
Revolut (AIR)[^25]	In‑app only	No public	—	—	—	—	No	No (SCA‑gated)
Wise	No	No	—	—	—	—	No	No

Cells marked "—" mean the wallet has made no public announcement in that column as of 21 April 2026, not that the wallet is technically incompatible.

10. Where the wallet model breaks down

Wallets are the natural consent surface for agent payments — they already carry the user's identity, the funding source, the SCA device, and the dispute relationship. But the wallet‑centric model has four structural cracks.

10.1 Key custody. A wallet's historical contract is "we hold the credential; you show up to approve." An agent that must transact while the user is asleep, offline, or simply unwilling to be interrupted breaks that contract. The three answers on offer are:

A pre‑signed, bounded mandate (AP2, Stripe SPT): the wallet pre‑approves a scope, not a transaction.
A delegated sub‑credential (Stripe Issuing card, Crossmint virtual card): the agent holds its own credential with a hard cap.
A live synchronous handoff (PayPal OTP, Apple Pay sheet): the agent cannot, in fact, transact autonomously; it can only build the cart.

No consumer wallet except Stripe Issuing, Antom, and (in preview) Google Wallet can actually clear a payment with the user asleep. This is the gap between announced and shipped agentic commerce.

10.2 Consent UX. An LLM's natural interface is continuous, multi‑turn and low‑friction. A wallet's natural UX is discrete, one‑shot and explicitly high‑friction (you feel the approve button because it is a liability‑transfer event). These two aesthetics are at war. Wallets that collapse too many approvals into one (for lower friction) weaken their dispute defence; wallets that demand per‑transaction SCA re‑entry destroy the agent's value proposition. PayPal's current compromise — a single OTP per cart — is a sane mid‑point but does not scale to true HNP flows. AP2's Intent Mandate is the most technically serious attempt at scoped consent (e.g. "buy any pair of running shoes under $200, size 11, in the next 48 hours") but its consumer UX is still being worked out.

10.3 Re‑authentication and SCA exemption. EU PSD2 (and the pending PSD3) require SCA for remote electronic payments unless a specific exemption applies. None of the current exemptions (low‑value, trusted beneficiary, transaction risk analysis) map cleanly to "the payer is an AI agent." Until regulators either (a) expand TRA exemption to cover mandate‑backed agent flows, or (b) publish a new exemption category for agentic payments, European consumer wallets are effectively prevented from shipping HNP agent flows at scale. Antom, Google and Mastercard have all quietly lobbied for such a category; see 10-regulation-and-compliance.md.

10.4 Dispute asymmetry. Wallets historically own the dispute relationship with the consumer (PayPal Buyer Protection, Apple Pay's card‑issuer chain). An agent‑initiated mis‑purchase raises two new questions: is the issuing wallet liable for an LLM hallucination ("the agent bought the wrong size because it misread the product page")? And how does a wallet distinguish agent error from unauthorised transaction for the purposes of a Regulation E / PSD2 chargeback? PayPal's published October 2025 material with Mastercard promises "tokenization and authentication" as the dispute substrate but does not commit to a specific liability rule. Stripe Issuing sidesteps the problem by making the developer the liable party (they set the controls; they eat the losses). That is acceptable for B2B agents but does not solve consumer‑grade liability.

11. Where this leaves us

The wallet and platform layer, as of April 2026, is a patchwork of announced architectures around two genuinely shipping primitives:

Stripe's Shared Payment Token + Issuing virtual cards, which together are the only consumer‑scale, end‑to‑end agent‑to‑clearing path in production in the United States.
Antom's EasySafePay MCP server, which is the equivalent path in Asia for alternative payment methods, and the only open‑source wallet agent server of its class.

Everything else — PayPal's Mastercard integration, Google Wallet's AP2 reference, Apple's silence, Revolut's AIR, Klarna's rhetoric, Block's internal Goose, Shop Pay's Agentic Plan — is either a developer‑preview SDK, a protocol participation with no consumer UX yet, or a productivity‑side AI story that is not really about agent payments at all. The fault line that will matter most through 2026 is whether wallets can extend their consent UX from one transaction at a time to a scoped mandate at a time without breaking their dispute and SCA obligations. That is a regulatory and design question more than a technical one, and it is covered in 10-regulation-and-compliance.md and 11-pain-points-and-open-problems.md.

Sources

[^1]: Kearney, "Agentic payments: a new frontier in digital commerce." https://www.kearney.com/industry/financial-services/article/agentic-payments-a-new-frontier-in-digital-commerce [^2]: Stripe, "Agentic commerce: protocol overview." https://docs.stripe.com/agentic-commerce/protocol [^3]: Google Cloud, "Announcing Agent Payments Protocol (AP2)," 16 September 2025. https://cloud.google.com/blog/products/ai-machine-learning/announcing-agents-to-payments-ap2-protocol [^4]: PayPal Newsroom, "PayPal Brings Together Developers, AI Leaders to Power Agentic Commerce at Dev Days," 29 April 2025. https://newsroom.paypal-corp.com/2025-04-29-PayPal-Brings-Together-Developers,-AI-Leaders-to-Power-Agentic-Commerce-at-Dev-Days [^5]: PayPal, "Agent Toolkit — Quickstart." https://paypal.gitbook.com/agent-toolkit-and-mcp-server/agent-toolkit/quickstart [^6]: InfoQ, "PayPal Launches MCP Server and Agent Toolkit," 30 April 2025. https://www.infoq.com/news/2025/04/paypal-mcp-ai-toolkit/ [^7]: PayPal Newsroom, "Mastercard and PayPal Join Forces To Accelerate Secure Global Agentic Commerce," 27 October 2025. https://newsroom.paypal-corp.com/2025-10-27-Mastercard-and-PayPal-Join-Forces-To-Accelerate-Secure-Global-Agentic-Commerce [^8]: OpenAI, "Buy it in ChatGPT: Instant Checkout and the Agentic Commerce Protocol," 29 September 2025. https://openai.com/index/buy-it-in-chatgpt/ [^9]: Walmart Corporate, "Walmart partners with OpenAI to create AI‑first shopping experiences," 14 October 2025. https://corporate.walmart.com/news/2025/10/14/walmart-partners-with-openai-to-create-ai-first-shopping-experiences [^10]: Stripe, "Agent Toolkit (GitHub repository)." https://github.com/stripe/agent-toolkit [^11]: Stripe, "Stripe Issuing." https://stripe.com/issuing [^12]: Seb G, "Adding Financial Capabilities to AI Agents: A Pattern Emerges From Stripe," 15 January 2025. https://sebgnotes.com/blog/2025-01-15-adding-financial-capabilities-to-ai-agents-a-pattern-emerges-from-stripe/ [^13]: Forbes, "How Block's CTO Is Working To Reinvent Jack Dorsey's Payments Company," 18 November 2025. https://www.forbes.com/sites/richardnieva/2025/11/18/block-cto-dhanji-prasanna-cio-next/ [^14]: VentureBeat, "Jack Dorsey's Block cuts 40% of staff, 4,000+ people — and yes, it's because of AI," 2026. https://venturebeat.com/orchestration/jack-dorseys-block-cuts-40-of-staff-4-000-people-and-yes-its-because-of-ai [^15]: Block Inc., "Q4 2025 Earnings Call Transcript," February 2026. https://www.theglobeandmail.com/investing/markets/stocks/XYZ-N/pressreleases/472458/block-xyz-q4-2025-earnings-call-transcript/ [^16]: Google / google‑agentic‑commerce, "AP2 specification repository." https://github.com/google-agentic-commerce/AP2 [^17]: TechCrunch, "Google launches new protocol for agent‑driven purchases," 16 September 2025. https://techcrunch.com/2025/09/16/google-launches-new-protocol-for-agent-driven-purchases/ [^18]: Klarna Press, "Klarna accelerates global momentum in Q1 2025," May 2025. https://www.klarna.com/international/press/klarna-accelerates-global-momentum-in-q1-2025-and-unlocks-large-gains-from/ [^19]: CNBC, "Klarna CEO outlines plan to become super app with AI," 18 June 2025. https://www.cnbc.com/2025/06/18/klarna-ceo-outlines-plan-to-become-super-app-with-ai.html [^20]: Yahoo Finance, "Klarna says its AI agent is doing the work of 853 employees," 2024–25. https://finance.yahoo.com/news/klarna-says-ai-agent-doing-070000869.html [^21]: The Independent, "Klarna's AI replaced 700 workers. It's trying to bring them back," 2025. https://www.independent.co.uk/news/business/klarna-ceo-sebastian-siemiatkowski-ai-job-cuts-hiring-b2755580.html [^22]: Affirm Investor Relations, "Affirm extends collaboration with Google as a supporter of Agent Payments Protocol," October 2025. https://investors.affirm.com/news-releases/news-release-details/affirm-extends-collaboration-google-supporter-agent-payments [^23]: Credit and Collection News, "BNPL Fintech Affirm Extends Stripe Partnership to Enable Shared Payment Tokens for Agentic Commerce," 2025. https://www.creditandcollectionnews.com/bnpl-fintech-affirm-extends-stripe-partnership-to-enable-shared-payment-tokens-for-agentic-commerce/ [^24]: Disruption Banking, "Ant International's Antom Launches Agentic Payment Solution, Redefining AI Commerce," 5 September 2025. https://www.disruptionbanking.com/2025/09/05/ant-internationals-antom-launches-agentic-payment-solution-redefining-ai-commerce/ ; Fintech News Singapore, "Ant International's Antom Enables AI Agents to Pay Directly in Chat," September 2025. https://fintechnews.sg/117385/payments/antom-ai-agent-payment/ [^25]: FF News, "Revolut Enters New Era of Money Intelligence With Launch of AI Assistant," 2026. https://ffnews.com/newsarticle/revolut-enters-new-era-of-money-intelligence-with-launch-of-ai-assistant/ [^26]: Payment Expert, "Revolut teases AI that could do more — if only regulators let it," 18 June 2025. https://paymentexpert.com/2025/06/18/revolut-ai-tool-starling-bank-launch/ [^27]: Shopify, "Agentic Plan: Sell Directly in AI Channels," 2025. https://www.shopify.com/agentic-plan