Protocol evidence
The strict API accepts compact JWS, AP2 SD-JWT and Visa TAP-style HTTP message signatures with public verification keys.
CRYPTOGRAPHIC AUTHORITY LAB
Prove the agent was allowed—not merely instructed.
Verify signed purchase evidence, bind it to the final transaction and issue an independently verifiable decision receipt before money moves.
LIVE CRYPTOGRAPHIC PROOF
Generate → sign → verify → attest
Your browser creates an ephemeral P-256 key, signs a synthetic purchase and sends only the public key and signature. No payment or private key leaves this device.
STRICT PROFILE
Nothing is trusted until the signature and bindings pass.
The v2 endpoint fails closed on missing, expired, modified or wrongly addressed evidence.
OFFLINE-VERIFIABLE EVIDENCE
Verify any MandateShield receipt.
Receipts are ES256-signed JWTs. Anyone can verify them with the public JWKS without trusting a screenshot or database export.
Fail-closed binding
Signatures must be current and bound to the evaluated merchant, amount, audience, nonce or canonical purchase digest.
Portable receipts
Each decision receives a signed receipt containing input and decision digests, evidence assurance and the verifier engine version.