W3C Workshop Spotlights Agent Payments: Huawei Pay and openJiuwen Unveil A4P Protocol
The new framework targets machine-to-machine payment compliance, introducing pre-settlement interception and Know-Your-Agent checks to tackle authorization challenges in AI-driven transactions.

At a recent W3C workshop, Huawei Pay and openJiuwen jointly introduced the A4P protocol, aiming to establish an industry compliance foundation for AI agent payment scenarios. The protocol focuses on critical elements in machine-to-machine (M2M) payments—such as authorization intent, per-transaction limits, and daily cumulative caps—seeking to provide a standardized framework for real fund flows initiated by agents. According to attendees, A4P emphasizes pre-settlement interception and Know-Your-Agent (KYA) mechanisms to address the compliance challenges of "who is paying, who is being paid, and whether the payment should occur" in agent-driven transactions. Several major technology and payment firms participated in the discussions, covering topics like the integration of open protocols such as x402 and MCP with stablecoin settlement. Currently, A4P remains in the standard proposal stage, and its adoption by mainstream ecosystems is still uncertain. Industry observers note that agent payments are transitioning from concept to reality, and the race to establish technical standards around authorization, attribution, and non-repudiation could become the next critical battleground in payment infrastructure.
Provenance & status
- Byline
- OceanAlt Editorial
- First published
- 2026-09-09
- Last updated
- 2026-09-09
- Content type
- Newsflash
- Source material
- View original ↗
Related reading

Consumers Use AI Assistants but Won't Hand Over Their Wallets: Visa Data Reveals the Agent Payment Trust Gap

a16z's Five Charts Break Down Argentina's Stablecoin Reality: Dollarized Payments in an Inflationary Economy Pave the Way for Agent Payments

BIS Chief Douses Stablecoin Hype: Not a Scalable Payment Tool, Reigniting Regulatory vs. Market Tensions
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.

