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

Guides

Agent-to-agent

Let one agent pay another.

Turn on allow_a2a in the sending agent's policy. Then the agent can call POST /v1/agent/send with { to: "agt_…", amount, memo? }. The same per-request max and daily cap apply, and the payment is an a2a ledger entry.

bash
curl -X POST https://dapp.railpay.app/v1/agent/send \
  -H "Authorization: Bearer $RAILPAY_AGENT_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "to": "agt_xxx", "amount": "0.01", "memo": "summary job" }'

Without allow_a2a the attempt is blocked with a2a_not_allowed.

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.