pragma.vision Your technology observatory

Verification register Agentic Commerce & Payments

Readiness verdict

Stripe Shared Payment Tokens (SPT)

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

As of
2026-06-28
Revision
1
Method
v1.0.0

Current reading

The readiness gap, in one scan

AI-assisted assembly · derived results

Claimed
75

Public ambition and stated capability

Reported
73

Observed practitioner reporting

Verified
67

Independently supported evidence

Gap
+8

Claimed minus verified

Evidence strength Strong

Decision

What the current evidence supports

Human editorial judgment · 2026-06-28

Proceed with caution

Why
Cleanest security model of the three (server-enforced seller/amount/expiry scoping, no raw card exposure, real merchant adoption) but preview-stage, US-only, and structurally dependent on Stripe + Link, so it warrants a guarded pilot, not broad adoption.
Next
Prototype SPT issuance + the single deactivation webhook (shared_payment.granted_token.deactivated) against the preview API in a US-scoped sandbox; evaluate fit alongside our existing AP2/ACP mandate model before any production checkout integration, with server-side amount recompute (Rule #1).

Constraints

Blockers

No named blocker is present in the current public projection.

Evidence summary

Derived counts

AI-assisted assembly

Total
6
Tier 1
0
Tier 2
2
Tier 3
4
Supports
4
Contradicts
1
Context
1
Latest observed
2026-05-06

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

Publication record

Revisions

Initial public reading

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

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.