Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getopenrails.com/llms.txt

Use this file to discover all available pages before exploring further.

Open Rails separates the merchant integration from the payment data plane. Your app asks for a checkout session; Open Rails chooses the best available route based on method, geography, asset, network, fee model, provider health, and merchant policy.

​
Route kinds

KindTypical buyer actionExample providers
cardPay with card, Apple Pay, or Google PayMoonPay, Transak, Ramp, Onramper
walletSend USDC or USDT from a walletDirect stablecoin checkout
localUse regional bank or local payment methodOnramp or local rail provider

​
Route metadata

Every route includes:
  • integrationId and integrationLabel
  • kind
  • network
  • asset
  • payerLabel
  • kycPolicy
  • buyer fee, gateway fee, provider cost, and estimated margin

​
List available routes

curl https://dash.getopenrails.com/api/agent/routes
Use preferredRoute when creating a checkout session. If you need a specific provider, inspect routes first and pass the route or provider through your own orchestration policy.

​
Fail-closed default

If no live route exists for the requested method, the API returns a structured error instead of silently routing to an unknown provider.