OpenAI/Stripe ACP Delegated Payment Spec

A dated reading of what is claimed, reported, and independently verified in the current evidence.

Current reading

The readiness gap, in one scan

AI-assisted assembly · derived results

Evidence strength Strong

Decision

Human editorial judgment · 2026-06-28

Adopt with guardrails

Why: It is the agentic-commerce payment path with the most mature multi-vendor spec (Stripe+OpenAI+Meta, versioned 2026-04-17) and a production PSP implementation, but PCI-scope constraints, US-only/single-use limits, and the 2026 pivot away from a unified Instant Checkout mean it must be wrapped in our own server-side validation and watched for surface changes rather than trusted directly.
Next: Prototype against the 2026-04-17 ACP OpenAPI spec via a Stripe Shared Payment Token sandbox; keep all amount/commission recalculation server-side (Rule #1/#13) and treat the delegated token's max_amount/merchant_id/expiry as untrusted-until-verified inputs. Track the retailer-app vs. embedded-checkout direction before committing to a single surface.

Constraints

No named blocker is present in the current public projection.

Evidence summary

AI-assisted assembly

Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.

Publication record

Initial public reading

This is the initial public reading. No earlier readiness change is recorded.