Compliance receipts for agentic payments
Every protocol answers how an AI agent pays. AlgoVoi answers how you prove the payment was screened, authorised and settled: an offline-verifiable compliance receipt for x402, AP2, A2A and MPP, on one open JCS (RFC 8785) substrate, with zero customer PII.
The gap every agentic payment protocol leaves
x402 charges per request, AP2 per signed mandate, A2A per agent-to-agent task, MPP per method call. None of them, on their own, leave a portable, verifiable record of the compliance and settlement decision that a supervisor can re-check years later, offline, without trusting the operator. That record is the receipt layer, and it is where AlgoVoi sits across the whole ecosystem.
One receipt layer for every protocol
- x402: x402 compliance receipt at admission, settlement attestation on-chain.
- AP2: mandate-bound AP2 verifiable receipts tied to the exercised mandate.
- A2A: payment-gated task receipts and A2A settlement attestations on the same substrate.
- MPP: per-method MPP compliance receipts for MCP tools and JSON-RPC calls.
All four resolve to the same grammar over the same canonical bytes, bound by the action_ref primitive (SHA-256(JCS({agent_id, action_type, scope, timestamp_ms}))), regardless of which protocol carried the payment.
What is in the receipt
- Categorical ALLOW / REFER / DENY: the outcome of an admission-time sanctions / PEP / AML screen, as an enumeration, not raw customer data.
- Deterministic and recomputable: canonicalised under JCS (RFC 8785); anyone can re-derive the hash from the disclosed fields.
- Offline-verifiable: cryptographically signed; verification needs no live call back to AlgoVoi.
- Zero customer PII: audit-grade evidence that the check ran, without exposing the customer.
Bring your own screening provider
AlgoVoi is the receipt and canonicalisation layer, not the screening vendor. Bring your own provider (Chainalysis, TRM, Elliptic or an internal list) and AlgoVoi turns each decision into a signed, offline-verifiable receipt. Built for agentic commerce, regulated PSPs, VASPs and exchanges that have to evidence the check, not just run it.
Open, and verifiable yourself
The substrate is open (Apache 2.0), specified in dated AlgoVoi-authored IETF Internet-Drafts (draft-hopley-x402-canonicalisation-jcs-v1, draft-hopley-x402-compliance-receipt), and cross-validated byte for byte across eight independent implementations in eight languages. Full reference: docs.algovoi.co.uk/agentic-payment-receipts.