Documentation Index
Fetch the complete documentation index at: https://docs.algovoi.co.uk/llms.txt
Use this file to discover all available pages before exploring further.
The Agent Payment Module (APM) is AlgoVoi’s production agentic-payment platform. It runs the substrate work that AlgoVoi authors in IETF Internet-Drafts and ships as open-source reference implementations on PyPI and npm.
Substrate work is the canonicalisation discipline, the receipt-format suite, the conformance vectors, and the cross-implementation attestations. Five IETF Internet-Drafts, five reference implementations on PyPI and npm, byte-deterministic across eight language runtimes. Open standards.
APM is the production deployment of that substrate. A facilitator + gateway + control plane at api.algovoi.co.uk that handles real money (USDC across 8 chains, PayPal Orders v2 GBP top-up under EMR 2011 safeguarding), runs the receipt-format emission live, and offers a managed integration surface for downstream parties who want the substrate in production rather than self-hosted.
One platform, one acquirer story. Not two separate engineering tracks.
Production capabilities
| Capability | Detail |
|---|
| Multi-chain settlement | 8 chain families: Algorand, VOI, Solana, Stellar, Hedera, Base (L2), Tempo, Ethereum mainnet. USDC-native where supported. |
| Multi-protocol | x402 (HTTP 402 facilitator), Agent Payment Protocol 2 (AP2 mandate verifier), Merchant Payment Protocol (MPP subscription), Agent-to-Agent (A2A). |
| Fiat rail | PayPal Orders v2 in production for agent-mandate balance top-up. Customers fund prepaid GBP balances under EMR 2011 reg 20-21 safeguarding (£100/mandate cap, £300/account cap, max 3 mandates). |
| Receipt-format emission | Compliance receipts (ALLOW / REFER / DENY), settlement attestations (SETTLED / PENDING_FINALITY / REVERSED), cancellation receipts (USER_REQUESTED / MERCHANT_REQUESTED / COMPLIANCE_TERMINATED / EXPIRED), refund receipts (FULL / PARTIAL / REJECTED), composite-trust-query responses (TRUSTED / PROVISIONAL / INSUFFICIENT_EVIDENCE / UNTRUSTED). All emitted under the JCS RFC 8785 canonicalisation pin. |
| Audit chain | Hash-chained audit-row records, year-N retention-property preserved by construction. B2 Object Lock COMPLIANCE 7-year retention for safeguarded data. |
| Sanctions + KYC + KYB | Pre-payment compliance gate, MaxMind GeoIP, 7 threat-intel feeds, KYC OCR Tier 1, KYB Fernet-encrypted (AVK1). |
| Post-quantum | Tier 2A (HMAC v1=SHA-256 + v2=SHA-384 dual-emit), Tier 2B (AVK2 AES-256-GCM dispatcher). Tier 1 JWT multi-alg. |
| Failover | Active-passive: VM1 primary + VM4 facilitator-2 (10.8.96.5:8001). Alchemy key IP-allowlisted both VMs. |
| Production endpoints | 399 routes, 88/88 e2e PASS at last regression. Health: https://api.algovoi.co.uk/health. |
Substrate ↔ APM mapping
| Substrate work (open standards) | APM implementation (production) |
|---|
draft-hopley-x402-canonicalisation-jcs-v1 | Every receipt APM emits is canonicalised under urn:x402:canonicalisation:jcs-rfc8785-v1 |
draft-hopley-x402-compliance-receipt | /compliance/screen + /compliance/attestation endpoints emit compliance receipts at every admission decision |
draft-hopley-x402-settlement-attestation | Settlement attestations emitted per on-chain or PayPal settlement, with settled_payment_ref content-addressed |
draft-hopley-x402-cancellation-receipt | Mandate cancellation flows emit categorical receipts with cancellation_reason enum |
draft-hopley-x402-refund-receipt | Refund flows emit categorical receipts under the same audit chain |
draft-hopley-x402-composite-trust-query | /compliance/attestation returns CTQ-shape responses for verifier consumers |
Open-source reference implementations
All Apache 2.0, all byte-for-byte cross-validated against published conformance vectors:
| Package | npm | PyPI |
|---|
algovoi-substrate / @algovoi/substrate | npm | PyPI |
algovoi-settlement-attestation / @algovoi/settlement-attestation | npm | PyPI |
algovoi-cancellation-receipt / @algovoi/cancellation-receipt | npm | PyPI |
algovoi-refund-receipt / @algovoi/refund-receipt | npm | PyPI |
algovoi-composite-trust-query / @algovoi/composite-trust-query | npm | PyPI |
Cross-validation evidence
Two attestation runs published at _attestations/ in the conformance corpus:
- 2026-05-24 eight-implementation attestation: 192/192 across Python, TypeScript, Go, Rust, Java, PHP, .NET, Ruby
- 2026-05-25 script-language 5-format attestation: 200/200 across Python, Node.js, Ruby, PHP inline-stdlib, Go for the five receipt/response formats
Cumulative: 392/392 byte-for-byte agreements. Every receipt APM emits is byte-reproducible in any of eight independent JCS implementations.
Adopters Registry
Production parties anchoring to the same canonicalisation discipline as APM are recorded at the Substrate Adopters Registry. Three current entries:
- AlgoVoi (substrate-author): production gateway emitting all five receipt formats, eight chain families, PayPal Orders v2 fiat rail
- Supership (downstream-adopter):
service_trust_v0 conformance vector set
- PEAC Protocol (downstream-adopter):
ap2-open-mandate-hash interop fixture set
A JSON-LD mirror is maintained at docs.algovoi.co.uk/adopters.json for automated consumption by composite-trust-query verifiers and downstream tooling.
Integration surfaces
APM exposes integration surfaces matching the substrate layers:
- x402 facilitator: HTTP 402 challenge /
/verify / /settle cycle, with categorical receipt emission per settlement
- AP2 mandate verifier:
open_mandate_hash computation under the JCS canonicalisation, IntentMandate / CartMandate / PaymentMandate verification
- MPP subscription engine: recurring-payment authority lifecycle with cancellation-receipt emission
- PayPal Orders v2: agent-mandate balance top-up flow (
/mandate/portal/{id}/topup/initiate and /.../topup/capture)
- Composite trust query: verifier endpoint emitting categorical responses over audit-chain references
A downstream integrator (translation layer, agent framework, e-commerce platform, regulated PSP) can route a single API integration to APM and gain access to every substrate layer plus the multi-chain settlement plus the fiat rail without re-implementing any of it.
Regulatory posture
- EMR 2011 reg 20-21 safeguarding for prepaid GBP balances on agent mandates
- PSD2 Articles 64 / 72 / 89 discipline reflected in cancellation receipt 4-state enum (USER_REQUESTED revocation, MERCHANT_REQUESTED termination, COMPLIANCE_TERMINATED, EXPIRED) and refund-window timing on settlement attestations
- MiCA Article 80 record-keeping for settled crypto-asset transactions, retained under the JCS canonicalisation pin for byte-deterministic year-N re-verification
- AMLR Article 56 retention obligations satisfied via the audit chain
- POCA s.330 / AML 5+6 evidence chain anchored by compliance-terminated cancellation receipts
- DORA Article 14 operational resilience receipt-chain emission
The receipt formats are not retro-fitted compliance theatre. They are the byte-deterministic substrate that the regulatory frameworks expect, designed around the operational distinctions the frameworks make (settled vs settled-then-reversed, payer-revocation vs merchant-termination, etc.).
Production status
Operational since 2026-04. Production health, route inventory, and cross-validation evidence in Substrate Authorship and Provenance.
For an acquirer evaluating the platform: APM is the productized side of the substrate work that anchors AlgoVoi’s IETF Internet-Drafts and conformance corpus. Both sides are AlgoVoi-authored, both are independently citable, both are operational. The substrate authorship case and the production-platform case are the same case.
See also
