Agent-Initiated Payments · Chargeback Evidence

Agent Payment Dispute Evidence Hub

Browser-based verify-only tools plus chain for assembling the evidence a chargeback or dispute review needs when an AI agent initiated the payment: was the underlying mandate's signature chain intact, was the disputed action inside the token's declared scope, and does the mandate/receipt, payment-protocol, and session/delivery evidence hold together in one hash-chained bundle.

Tools · Chain Verify-Only, Never Executes Zero PII
Last Reviewed: 2026-07-25
Agent Payment Dispute Evidence Hub chain and tool matrixMatrix for Agent Payment Dispute Evidence Hub: columns are the tools this guide covers, each row is one chain, and a filled cell marks a chain that runs through the tool. AP2 Mandate-Chain ValidatorAP2 Mandate-Chain… Chargeback Evidence Bundle ComposerChargeback Evidence… Agent Token Scope CheckerAgent Token Scope… Agent Commerce… Agent Commerce Cross-Protocol Conformance run through AP2 Mandate-Chain Validator Human-Not-Present… Human-Not-Present Autonomous-Payment Guardrail run through AP2 Mandate-Chain Validator AP2 PaymentReceipt… AP2 PaymentReceipt Verification & HNP Guardrail run through AP2 Mandate-Chain Validator Agent Payment Dispute EvidenceAgent Payment Dispute… Agent Payment Dispute Evidence run through AP2 Mandate-Chain Validator Agent Payment Dispute Evidence run through Chargeback Evidence Bundle Composer Agent Payment Dispute Evidence run through Agent Token Scope Checker Agentic Commerce… Agentic Commerce Convergence run through AP2 Mandate-Chain Validator Assemble Agent Dispute… Assemble Agent Dispute Evidence run through AP2 Mandate-Chain Validator Tempo MPP Agent Mandate Tempo MPP Agent Mandate run through AP2 Mandate-Chain Validator Chains using the tool 7 1 1
Chain and tool matrix for Agent Payment Dispute Evidence Hub: each column is a tool this guide covers, most used first, each row is one chain, and a brighter cell means more of that row's chains run through the tool. Hover a cell to list them.
What we verify vs. what we never do

Every tool on this page reads structures you supply: an AP2 mandate chain, an agent token or delegation record, or dispute-evidence artifacts already collected elsewhere. They check signature-chain integrity, scope and expiry bounds, and evidence completeness, and they say when a field can't be verified rather than guessing. None of these tools initiate, route, settle, or transmit a payment, query a live payment network, or move value in any way. They do not adjudicate a dispute outcome either — the adjudication bundle they produce is evidence for a human or downstream system to review, not a verdict.

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Agent Payment Dispute Evidence
Mandate-chain validation and token scope checking feed the evidence bundle composer, which folds in payment-protocol and session/delivery evidence and produces one hash-anchored adjudication bundle.
Open chain →
AP2 (Google)Intent→Cart→Payment mandate chain the agent acted under — validated by ART-01, scope-checked by ART-385.
x402Payment-protocol evidence group inside the bundle composer — payload decode/lint, not execution.
A2A x402 extensionAgent-to-agent settlement-record lint feeding the same evidence group.
Mastercard SPTNot covered — the spec is partner-gated with no published field or signature schema as of 2026-07-18.