Mastercard, AP2 and x402: Three Paths to AI Agent Payments
Card network infrastructure, verifiable authorization credentials, and on-chain per-use settlement—three paths with different roles, yet facing the same compliance question: when an agent initiates a payment, who authorized it, what is the limit, and is the payee trustworthy?
Payments giant Mastercard is advancing its Agent Pay system, allowing AI agents to initiate transactions on behalf of cardholders with their authorization; meanwhile, Google-led AP2 (Agent Payments Protocol) and the HTTP 402-based x402 protocol are approaching the same scenario from two directions: authorization intent and machine-native settlement. According to The Defiant, the three are positioned differently: Agent Pay relies on existing card network and merchant acceptance infrastructure, AP2 focuses on providing verifiable authorization credentials for agent transactions, and x402 enables agents to complete per-use payments on-chain using stablecoins.
This division of labor also brings up a shared compliance issue. Once an agent initiates payments on behalf of a person, who authorized it, what is the limit, and whether the payee is on a whitelist all need to be determined before settlement; for card networks, this means KYA (Know Your Agent) and per-transaction limit controls, while for on-chain protocols, it means payee whitelists and on-chain taint screening.
All three paths are currently in early stages, and actual transaction volumes and merchant coverage have not yet been disclosed.
Source: https://news.google.com/rss/articles/CBMiqwFBVV95cUxPeXBqS2tieDVHWmtlVHBSc1lNcl9kd2N3UmtVazRBbk5SZmU3YlBsQVdMZi1HUFc0NzRoclpjTVEzRWFBazJZUVVMSXhhb24yakhNMFV1QzBDR295alpNUWthTE1LUGcydk5pTW5taUgxdnNVOUpKYnd2V1FyRExHVm9fekZJeU1xQnk5Qk8yelNwY0ZFSFVPU2hqc2JlZTlsZUE3SVltbzVxU3M?oc=5
Provenance & status
- Byline
- OceanAlt Editorial
- First published
- 2026-10-24
- Last updated
- 2026-10-24
- Content type
- Newsflash
- Source material
- View original ↗
Related reading
Paste a payee address before you pay and see whether it's on a sanctions list, through a mixer, or tagged for fraud.
This judgement can sit inside your own product
One line of code; it touches neither your CSS nor your JS. The same pre-settlement judgement can appear in your articles, on your wallet's confirmation screen, or as an endpoint your agent calls before it pays.