0.1.0 historical release
Published 2025-09-16 · First observed 2026-09-28
Initial AP2 release.
Merchant impact: Review authority and mandate handling with your payment provider; this is not a live payment test.
Version source ↗Protocol intelligence / Identity & trust
Agent Payments Protocol
A protocol for expressing and verifying authority for agent-performed payments.
Specification state: public-previewPrimary evidence available
StewardAP2 contributors / FIDO standardization work
Stack layerIdentity & trust
Version0.2.0
Last evidence check28 September 2026
Merchant answer / Source-backed reference
A protocol for expressing and verifying authority for agent-performed payments. Uses linked checkout/payment mandates and receipts to bind authorization. Does not define the catalog API or replace a commerce protocol. Individual merchant eligibility and deployed configuration require confirmation. Map this role to your existing stack and confirm the exact version, access conditions and implementation scope before making a merchant decision.
What this establishes
The documented role and version scope in the source ledger.
What it cannot establish
Live merchant deployment, private account eligibility, purchase completion or guaranteed AI selection.
Claim-to-source mapping
- description: A protocol for expressing and verifying authority for agent-performed payments. · verified · Checked 2026-09-28 · Sources: ap2-spec, ap2-home
- role: Uses linked checkout/payment mandates and receipts to bind authorization. · verified · Checked 2026-09-28 · Sources: ap2-spec, ap2-home
- version: v0.2 · verified · Checked 2026-09-28 · Sources: ap2-spec, ap2-home
- version: 0.2.0 · verified · Checked 2026-09-28 · Sources: v11-ap2-releases
Version-aware protocol intelligence
Current version. Clear scope.
Current version0.2.0
Current statusreleased
Published date2026-04-28
First observed / last verified2026-09-28 / 2026-09-28
GitHub release published_at; distinct from the date encoded in a version tag.
Scope: Official repository release · Layer: Identity & trust · Steward: AP2 contributors / FIDO standardization work
Merchant impact
Human Not Present payment flows are the focus of this release.
Review authority and mandate handling with your payment provider; this is not a live payment test.
Public implementation evidence: Public specification; individual deployments Unknown
Merchant action today: Assign verification responsibility for each role.
Unknowns: Your enabled version, provider rollout, plan and region require merchant-side confirmation.
Source capture hashes
Previous versions
Documented role
What it helps with
Uses linked checkout/payment mandates and receipts to bind authorization.
Keep the scope clear
What it does not solve
Does not define the catalog API or replace a commerce protocol.
The merchant work
- Assign verification responsibility for each role.
- Keep deterministic mandate validation outside the model.
- Confirm provider support and dispute evidence handling.
Individual merchant eligibility and deployed configuration require confirmation.
| Version | 0.2.0 |
|---|---|
| Discovery | Outside scope |
| Checkout | Authorizes checkout; does not define commerce API |
| Payment | Mandates and receipts; not a settlement rail |
| Authorization | Core role |
| Transport | Integration with commerce protocols |
| Adoption | Public specification; individual deployments Unknown |
Append-only history
What we observed, and when.
First house observation: 28 September 2026. Earlier dates, where known, are effective dates researched retrospectively.
Evidence improved
0.2.0; 2 scoped version record(s) now linked.
V1 record: v0.2; no structured prior-version timeline.
0.2.0; 2 scoped version record(s) now linked.
Merchant impact: Review authority and mandate handling with your payment provider; this is not a live payment test.
Evidence ledger
Go to the source.
Primary documentation records what is publicly stated. It does not independently prove outcomes or your account’s eligibility.
Claim scope: Authorization mandates and receipts
Payment authorization within a commerce protocol; catalog API details are out of scope.
Claim scope: Stewardship and integrations
Site states continued standardization within FIDO working groups.
Claim scope: Version metadata and documented changes only; not merchant adoption.
SHA-256 of retrieved source response: 43572d4defa8d53e8ab8dbfe90cc2d6734892aa93fcce009015d73cf21336ad6