Documentation
Build on GenesisPay
GenesisPay is the account layer for agentic payments, with two sides. Sellers publish one link that is a human checkout and an x402 API at the same time. Agent users give their AI a funded USDC account with spending limits and human approvals instead of a private key.
GenesisPay was formerly PeerDirect — technical identifiers (PEERPAY_* variables, pp_ key prefixes, PEERPAY-* headers) intentionally keep the legacy prefix for stability.
Getting started
Integrations
Guides
Reference
Control plane, data plane
Everything a human decides — login, funding, spending limits, approvals, key management — happens on the website. Everything a machine does — x402 payments, programmatic link creation, discovery, webhooks — happens behind API keys under /api/v1. Secrets are shown once at creation; GenesisPay stores only SHA-256 hashes.
# Seller key — create links, settle payments
Authorization: Bearer pp_sk_<32 base62 chars>
# Agent key — pay x402 endpoints
Authorization: Bearer pp_ag_<32 base62 chars>GenesisPay is in free public beta on Base Sepolia (testnet). All money is USDC or EURC: decimal strings like "5.00" in requests, integer minor-unit strings (6 decimals) in stored data and responses.
Pricing and fees
One price at launch: 1% per payment. No fixed costs, no monthly fees, no rolling reserve, no chargebacks. The beta is free — the fee rate is controlled by PEERPAY_FEE_BPS (basis points; 100 = 1%, 0 during beta).
The fee is currently recorded as a billing line item on each payment (fee_usdc_minor) and shown in the dashboard activity. It is not deducted from the settlement amount: the on-chain transfer moves the full amount to the merchant, and the 1% is tracked separately for later invoicing. Amounts are shown to people in € / $ (EURC settles in euros, USDC in dollars); the token symbol appears only in receipts and activity detail.