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

API reference

Authentication

Wallet sign-in for people, API keys for code.

Base URL (sandbox, local): https://dapp.railpay.app. All bodies are JSON.

Wallet sign-in

  1. POST /v1/auth/nonce with { address } returns { message }, which contains a one-time nonce valid for 10 minutes.
  2. Sign message with the wallet (EIP-191 personal_sign).
  3. POST /v1/auth/verify with { address, signature } sets the rp_session cookie (HttpOnly, 7 days) and returns { account }.
POST/v1/auth/nonceNone

Get a sign-in message for an address.

Body
{ "address": "0x…" }
Response
{ "message": "…" }
curl
curl -X POST https://dapp.railpay.app/v1/auth/nonce \
  -H "Content-Type: application/json" \
  -d '{ "address": "0x…" }'
POST/v1/auth/verifyNone

Verify the signature and start a session.

Body
{ "address": "0x…", "signature": "0x…" }
Response
{ "account": { … } }
curl
curl -X POST https://dapp.railpay.app/v1/auth/verify \
  -H "Content-Type: application/json" \
  -d '{ "address": "0x…", "signature": "0x…" }'
POST/v1/auth/logoutSession

End the session.

curl
curl -X POST https://dapp.railpay.app/v1/auth/logout -b "rp_session=…"

API keys

Send keys as Authorization: Bearer rp_sk_…. Keys are shown once; only a SHA-256 hash is stored.

KeyCreated inCan call
Account keyDevelopers page in the app, or POST /v1/keysEverything for the owning account
Agent keyReturned when you create an agentOnly /v1/agent/*, bound by the agent's policy

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.