All Tools
Tools/AP2 Mandate Decoder
🤝
BlockchainAvailable

AP2 Mandate Decoder

Decode Agent Payments Protocol (AP2 v0.2) Checkout and Payment Mandates — open and closed, as SD-JWT VCs — plus receipts. Resolves selective disclosures, checks the chain binding, checkout hash and the agent’s signature in the browser, and evaluates constraints.

Follows Agent Payments Protocol (AP2)v0.2 — Checkout & Payment Mandates (SD-JWT VC), receipts·verified Oct 2026· double-checked Oct 2026— tested against the spec’s published example tokens; receipts decoded as signed JWTs whose reference is the hash of the closed mandate; v0.1 Intent/Cart/Payment mandates shown as legacy

Mandate tokens are the examples published in the AP2 v0.2 specification; they were minted in April 2026, so their exp shows as expired. The Payment Receipt is an illustrative PSP-signed JWT whose reference is the hash of the spec’s closed Payment Mandate.

Where AP2 sits in the agentic stack

AP2 (Google; v0.2 published 28 April 2026 at github.com/google-agentic-commerce/AP2) is the authorization layer: a Checkout Mandate proves the agent may complete this checkout, a Payment Mandate proves it may pay for it. It is designed to run inside a commerce protocol such as UCP; ACP (OpenAI/Stripe) is a competing checkout layer. x402 is a settlement rail — decode its headers with the x402 Header Decoder. The agent’s own HTTP identity (Web Bot Auth / Visa TAP) is checked with the HTTP Message Signature decoder; SD-JWT basics are in the SD-JWT VC decoder. Background: Agentic Payments guide.

Something wrong or missing? Report a problem— we check reports against the specs and fix them.