Explainer · agentic payments
Ant International's Agentic Mobile Protocol is a wallet-first attempt to make AI agents trusted payment actors.
Agentic Mobile Protocol, or AMP, was launched by Ant International in April 2026 as an open-sourced framework for AI agents using digital wallets, super apps and mobile devices. On 11 September, Ant announced a much broader rollout across Alipay+ wallet and acquiring partners. The important point is that AMP is more than a checkout message: it combines delegated task authority, agent identity, payment execution, protection and very small agent-to-agent settlement.
Published 11 September 2026 · current rollout announced 11 September 2026 · primary sources below
10 wallets
Phase I Alipay+ wallet partners
7 acquirers
Adyen, Allinpay, Checkout.com, Fiserv, Global Payments, Nuvei and Worldline
1.5B accounts
User accounts served by the Phase I wallet partners, according to Ant International
What AMP is trying to solve
The agent needs permission to complete a task, not permanent control of the user's money
Traditional wallet binding asks whether a payment credential can be used. An autonomous purchase adds a different question: what was the agent authorised to achieve, under which budget and conditions, and can that authority be changed or revoked before execution?
Ant International describes AMP as extending payment authorisation into task authorisation. A user can constrain the goal, budget, merchant or other conditions while retaining visibility and the ability to modify or revoke the task. That makes delegated intent part of the payment architecture rather than a prompt the model is trusted to remember.
AMP is aimed particularly at mobile commerce, where users already have wallets and payment accounts. The intended path is for the agent to use that existing payment relationship instead of forcing the user to create a new merchant account or manually return to checkout.
The AMP stack
Five jobs inside one agent-payment framework
Delegated task authority
The user authorises a task and its boundaries instead of handing over an unrestricted account.
Agent identity / KYA
AMP describes agent identity, certified capabilities and trust/risk controls for deciding how much autonomy to grant.
Payment execution
The agent can invoke payment through existing wallet and mobile-payment infrastructure once the task is authorised.
Transaction protection
Ant International describes AgentSafePay protections for agentic-payment risks.
A2A settlement
AMP includes a high-frequency settlement mechanism for very small agent-to-agent payments, with Ant stating support down to $0.000001.
September rollout
AMP moved from an April protocol launch into a named wallet-and-acquirer deployment programme
Ant International said on 11 September that Phase I includes Alipay, AlipayHK, DANA, GCash, KakaoPay, MPay, TNG eWallet, TrueMoney, Toss and Starryblu. Those ten wallet partners together serve about 1.5 billion user accounts, according to the announcement.
The seven named acquiring partners are Adyen, Allinpay, Checkout.com, Fiserv, Global Payments, Nuvei and Worldline. The wider Alipay+ network is described as connecting more than 50 wallet and banking partners, more than 10 national QR schemes, around 150 million merchants and roughly 2 billion consumer accounts.
At the same time, Ant International, Mastercard and Visa are working on interoperable Know-Your-Agent principles. That matters because AMP's own KYA and Agent Trust Rating concepts now sit beside an explicit cross-network effort to make agent identity and accountability portable across cards and wallets.
AMP vs x402 vs MCP
These protocols solve different jobs and can appear in the same workflow
| Dimension | Ant AMP | x402 | MCP |
|---|---|---|---|
| Primary job | Mobile-wallet agentic commerce | Machine-readable payment for an HTTP resource | Tool discovery and invocation |
| Typical surface | Wallets, super apps, smart devices, mobile interfaces | APIs and web resources | Model runtime ↔ tool server |
| Identity / intent | Built into the broader framework | Usually supplied by wallet/policy layers around the payment | Outside the core payment question |
| Settlement | Wallet rails plus AMP A2A mechanism | Commonly exact stablecoin settlement through an x402 facilitator | None in core MCP |
| What it does not replace | HTTP service contracts and tool schemas | KYA, delegated intent and full wallet policy | A payment rail or spending policy |
A practical agent could discover a tool through MCP, use a wallet policy that understands delegated authority, and then settle a particular API call over x402. A mobile shopping agent could instead use AMP to act through an existing consumer wallet. The rail and trust model should follow the job rather than be collapsed into one generic "agent payments" category.
What builders should watch
Interoperable KYA
Whether agent identity and certification signals can actually travel across wallets, card networks, marketplaces and agent platforms without duplicate onboarding.
Delegated-intent portability
Whether task limits remain understandable and enforceable when an agent crosses from its home app into another merchant or payment network.
Nano-settlement economics
Whether the advertised A2A settlement mechanism becomes a broadly available developer rail and how fees, dispute handling and reconciliation work at sub-cent values.
Developer adoption
AMP is open-sourced, but deployment breadth, stable tooling and independent production integrations are stronger evidence than protocol availability alone.