pragma.vision Technology observatory & strategic foresight

Verification register Agentic Commerce & Payments

Readiness verdict

OpenAI/Stripe ACP Delegated Payment Spec

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

As of
2026-10-02
Revision
4
Method
v1.4.0

Current reading

Readiness band and full integer triple

AI-assisted assembly · derived results

Readiness band

Emerging

Primary summary from verified readiness

Confidence
83% · stale
Computed at
2026-10-02T05:43:28.921341+00:00
Claimed
55

Public ambition and stated capability

Reported
25

Observed practitioner reporting

Verified
15

Independently supported evidence

Gap
+40

Claimed leads verified

Evidence strength Growing

Decision

What the current evidence supports

Agent-assisted assessment · independently reviewed · 2026-10-02

Consider a limited pilot with a compatible PSP, conditional on transaction-level security testing.

Why
Implementations exist, but allowance binding and replay behavior need deployment-level confirmation. Original checkout field results also showed commercial limitations.
Next
Pin the API version and test merchant/session binding, amount and currency limits, expiry, single use, request integrity, retries and payment-to-order recovery before expanding.

Constraints

Blockers

  • Direct integration requires a PSP or a PCI DSS Level 1 merchant with its own vault.
  • The released delegation endpoint supports only card credentials.
  • Checkout-session binding at payment time needs explicit PSP enforcement.
  • Optional signatures and timestamps require deployment-specific integrity and freshness controls.
  • Public validation of current-version token limits and replay handling remains limited.
  • Checkout flexibility and conversion need testing in the intended buying journey.

Evidence summary

Derived counts

AI-assisted assembly

Total
12
Tier 1
10
Tier 2
2
Tier 3
0
Supports
4
Contradicts
5
Context
3
Latest observed
2026-08-30

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

Publication record

Revisions

Revision 4

  1. 2026-07-19 Reading moved from watch to watch.
  2. 2026-09-22 Reading moved from watch to watch.
  3. 2026-09-30 Reading moved from watch to emerging.
  4. 2026-10-02 Reading moved from emerging to emerging.

Your opinion

Tell us anything.

What works, what doesn't, what's missing — especially about our watches, lenses, and the register itself. Anonymous is fine; leave an email if you'd like a reply.