The Agentic Commerce Protocol (OpenAI + Stripe) lets a purchase complete inside an assistant via a narrowly-scoped Shared Payment Token. This tool checks an ACP checkout-session object's shape and — more importantly — lints a delegated payment token for the four properties that keep it safe: single-use, merchant-bound, amount-capped, and short-lived.
⚠ ACP is in beta (spec dated 2026-04-17) and versions monthly. The checkout field names below are illustrative — confirm against the published ACP JSON schema. The token scope checks are security properties that hold regardless of exact field names.
ACP 2026-04-17Shared Payment TokenZero PIIClient-Side · No Network
Scope & reliance —🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only. Paste synthetic objects only — never a real payment token. Structure/scope checks only; no charge is made and nothing is transmitted. Deterministic · zero PII · CC BY 4.0.
▸ Validate an ACP checkout-session object
Paste the checkout-session JSON. Top-level shape is checked; unfamiliar field names are flagged as illustrative. An example is pre-loaded.
▸ Lint a Shared / delegated payment token's scope
Paste the token descriptor (synthetic). Checks single-use, merchant binding, amount cap, currency, and expiry. Field aliases are accepted.
▸ ACP version notes
ACP uses date-based versioning (Apache-2.0, OpenAI + Stripe). Milestones from the public repo:
The Shared Payment Token is Stripe-issued, single-use, and scoped to merchant + cart total. Delegate Authentication uses OAuth 2.0. Verify the exact schema in the ACP repo before building.