Payment Factory
Multi-protocol payment infrastructure for any Solana-anchored service. Charge per call, per attestation, per inference — x402, AP2, MPP, or Bearer, all on one SDK.
Overview
Axiom Payment Factory is the open-source consolidation point for autonomous-agent payments on Solana. It speaks x402 (Coinbase), AP2 (Google), MPP (Stripe), and Bearer auth from a single SDK, so a service can accept the four major agent-payment shapes without picking a winner. Receipts, mandates, idempotency, and wallet rotation come built-in.
The product is service-agnostic: any Solana-settling API can publish a .well-known/x402 manifest and start charging agents. Themra is the first service we built on it — we use Payment Factory to run it, and the same surface ships to customers.
Independent. Composable.
Payment Factory is service-agnostic: it charges any service that publishes a .well-known/x402 manifest — oracles, LLM APIs, data feeds, compute rentals, agent-to-agent task delegation. Themra is the first service we built on it, and the same factory-pattern infrastructure ships to customers: you wire your own services to the same rails. The two products are independently useful, and the dogfood is the proof the surface holds.
Status
Production-grade · devnet. Four payment modes live and verified end-to-end on Solana devnet: Bearer (quota), x402 (agent-autonomous), AP2 (mandate passthrough), MPP (charge voucher). Real on-chain settlements verified against the Coinbase facilitator — all four advertised at api.axiomstack.dev/v1/.well-known/x402. Mainnet follows formal third-party security audit (Q3 2026).
Ecosystem compatibility
How we fit alongside Coinbase x402 and Stripe Agent Toolkit
Coinbase's x402-sdk is the canonical x402 implementation, Apache-2.0, multi-chain, with hundreds of millions of transactions settled on Base and Solana and Linux Foundation governance behind it. We don't compete with that. Axiom Payment Factory sits one layer up: it is the open-source consolidation point that speaks x402, AP2, Stripe MPP, and Bearer auth from a single SDK, with a hosted dashboard for receipts, mandates, and wallet rotation that customers would otherwise build themselves.
Use @coinbase/x402 if you are an x402-only API on Base. Use Stripe's Agent Toolkit if your settlement is Stripe-native. Use Axiom Payment Factory when you are a Solana-settling service that needs to accept the four major agent-payment shapes without picking a winner — and want the receipts UI, idempotency, and institutional audit trail ready on day one. It complements the foundation work; it does not replace it.
Security posture
Designed to audit-grade standards, pending formal audit Q3 2026
Axiom Stack is built by a founder with deep institutional grounding in IT audit, security-controls assessment, and risk frameworks, and the payment + attestation infrastructure is engineered to that posture from the start. Operational gates we ship today:
- Multi-role custody: the program upgrade authority is held on a hardware wallet (Ledger Nano X secure element, migrated 2026-05-19). The program ID keypair, treasury hot wallet, provider signer, and registry authority are separate keys with distinct roles — no single hot key controls upgrade, settlement, and attestation simultaneously.
- Receipts & idempotency: every paid request emits a verifiable receipt (DDB-backed for MPP-charge and AP2 mandates; on-chain TX signature for x402). Replay protection on every primary settlement path.
- Threat model published: trust boundaries, attack surface, and known limitations are documented in the Themra threat model alongside the program code.
Designed to audit-grade standards — formal third-party security audit scheduled Q3 2026, gating mainnet rollout. See /developers/docs/architecture for the hardware-anchored upgrade authority detail and /developers/docs/roadmap for the audit timeline.
What can you charge for
Six customer shapes: Oracle data (our dogfood), API access, content licensing, compute & LLM inference, model inference, and agent-to-agent commerce.
For developers
Four payment modes — x402, AP2, MPP-charge, Bearer — on a single endpoint. Composition patterns, precedence rules, signed-payload recipes.