The x402 Payment Gateway with compliance built in
Self-hosted, multi-chain, and fully compliance-screened. AlgoVoi accepts stablecoin payments via x402, MPP, AP2 and A2A across seven blockchains — with sanctions screening, KYB gating and a write-once audit chain on every transaction.
Seven chains, one gateway
Every payment settles on the chain your counterparty prefers. The same compliance receipt and audit-chain entry is written regardless of which chain executes the transaction.
Four agentic payment protocols
The gateway speaks every major agent payment protocol natively. Drop it behind any AI agent, API, or storefront.
- x402: HTTP 402 stablecoin payments — the agent hits a 402, pays in USDC, retries. Gateway verifies on-chain and returns the resource.
- MPP: per-method billing for MCP tools and JSON-RPC calls.
- AP2: signed-mandate payments where the agent pre-authorises a spend budget.
- A2A: agent-to-agent task payments with full settlement attestation.
Compliance built in, not bolted on
Sanctions and PEP screening
Every payment is screened at admission time against your provider (Chainalysis, TRM, Elliptic, or internal list). Bring your own vendor — AlgoVoi produces the signed receipt.
KYB and KYC gating
Counterparty verification before settlement. MLRO-grade audit pipeline for regulated environments.
Write-once audit chain
Every payment writes a SHA-256-chained, tamper-evident entry. No entry can be inserted or deleted without breaking the chain.
Offline-verifiable receipts
Every compliance decision becomes a signed, categorical ALLOW / REFER / DENY receipt with zero customer PII — recomputable from disclosed fields without calling back to AlgoVoi.
How x402 works through the gateway
- Agent calls a paid endpoint. Server returns
402 Payment Requiredwith payment instructions. - Agent pays the stated USDC amount on-chain and retries the request with an
X-PAYMENTheader. - AlgoVoi gateway runs the sanctions screen, verifies the on-chain transaction, and writes a compliance receipt.
- Server returns the resource plus a signed
settlement_attestation. Both parties hold verifiable proof.
Drop-in for merchants and AI platforms
- WooCommerce, OpenCart, PrestaShop, Shopware, BigCommerce, Magento
- AI agent frameworks: OpenAI, Claude, Gemini adapters
- No-code: Zapier, Make, n8n
- Native SDK: Python, TypeScript, Go, Rust, PHP
Open substrate, commercial gateway
The receipt format and canonicalisation layer are open-source (Apache 2.0), specified in dated IETF Internet-Drafts (draft-hopley-x402-canonicalisation-jcs-v1), and cross-validated byte-for-byte across eight languages. The gateway that runs on top is the commercial product.
Full technical reference: docs.algovoi.co.uk/payment-gateway
Frequently asked questions
A self-hosted x402, MPP, AP2 and A2A payment facilitator you run on your own infrastructure across seven chains, with operator custody. Every settlement produces a post-quantum signed receipt an auditor verifies offline. It ships as Payment Rails, a one-time perpetual licence at $15,000.
No. You hold the keys and the funds. The gateway runs in your own environment with operator custody and payouts; AlgoVoi is never in the payment trust path and never touches your funds.
x402, MPP, AP2 and A2A across seven chains: Algorand, VOI, Hedera, Stellar, Base, Solana and Tempo, plus Bitcoin settlement verification.
Sanctions screening, KYB and signed no-PII compliance receipts are built into the gateway, not bolted on. Every payment can carry a verifiable ALLOW or DENY decision, and settlements produce audit-chain evidence.
Payment Rails is a one-time perpetual licence at $15,000, self-serve from the store, paid in stablecoin. It includes the Security Suite and Mesh federation, with no per-transaction fee.