Verification register Agentic Commerce & Payments
Current reading
Readiness band and full integer triple
AI-assisted assembly · derived results
Readiness band
Ready
Primary summary from verified readiness
- Confidence
- 71% · stale
- Computed at
- 2026-08-20T10:53:03.609144+00:00
- Claimed
- 68
- Reported
- 63
- Verified
- 55
- Gap
- +13
Public ambition and stated capability
Observed practitioner reporting
Independently supported evidence
Claimed leads verified
Evidence strength Critical
Decision
What the current evidence supports
Human editorial judgment · 2026-08-20
Adopt with guardrails
- Why
- TAP is built on a real IETF standard (RFC 9421), is openly specified under MIT, has 100+ enrolled partners and a multi-PSP Oct 2025 launch, and is already part of our protocol stack — making it the most adoptable of the three. Guardrails needed because the reference impl is demo-grade (6 commits, no releases) and trust is rooted in a Visa-operated key directory.
- Next
- Since TAP is already a named layer in our protocol architecture, validate our TAP identity layer against the published RFC 9421 spec (Ed25519/PS256 signatures, 8-minute validity window, nonce replay protection, agent-browser-auth vs agent-payer-auth tags) and align our header/JWT schema to Visa's; keep our implementation directory-agnostic so we are not hard-bound to Visa's JWKS.
Constraints
Blockers
No named blocker is present in the current public projection.
Evidence summary
Derived counts
AI-assisted assembly
- Total
- 12
- Tier 1
- 0
- Tier 2
- 6
- Tier 3
- 6
- Supports
- 6
- Contradicts
- 4
- Context
- 2
- Latest observed
- 2026-06-25
Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.
Publication record
Revisions
Initial public reading
- 2026-07-19 Reading moved from ready to ready.