RailPayDocs
Sandbox. No real funds move and nothing settles on a chain yet. What this means

Get started

Concepts

The five things everything else is built from.

Accounts

One account per wallet. An account has a kind (business or customer), a name and a unique handle (a-z0-9-, 3–24 characters) that others can send to.

Ledger

Every movement of money is one ledger entry { id, from_id, to_id, amount, kind, ref, memo, created_at }. Balances are derived from entries and returned precomputed. Entry kinds: faucet, transfer, invoice, x402, a2a, rule, pocket.

Pockets

Named sub-balances of an account, such as Treasury or Tax. You move money in and out manually, or let a rule do it.

Agents

An agent is a wallet owned by your account, with its own balance, its own API keys and a policy: per-request max, daily cap, allowed hosts, agent-to-agent and pause. Every payment attempt is logged as paid or blocked.

x402

x402 uses HTTP status 402 Payment Required so a client can pay for a resource inline: request, receive the price, pay, retry with proof. RailPay serves real 402 responses and accepts sandbox payments for them.

The RailPay app runs in Sandbox mode. Balances are in Sandbox USD (SUSD). No real funds move and nothing settles on a chain. Chains, stablecoins, card issuing, ramps, fees and yield are TBD.

© 2026 RailPay. Built as practical payment infrastructure, not a token or fundraising project.