Skip to main content
Open Rails is a non-custodial payment control plane for merchants who need a backup checkout when cards, Stripe, or PayPal stop working. The product gives merchants one hosted checkout and one integration surface while the actual payment, KYC, card processing, wallet transfer, or stablecoin settlement happens through approved data-plane providers.

​
What you can build

  • Create hosted checkout sessions for cards, wallets, local rails, and stablecoins.
  • Route buyers to the best available provider without exposing every provider decision in your merchant app.
  • Pass a per-order redirectUrl so each checkout can return to the right success or failure page.
  • Receive one normalized webhook payload for provider-pending, paid, and failed payments.
  • Inspect machine-readable schemas before sending requests, which makes Open Rails easier for agents and CI scripts to integrate.

​
Base URLs

​
Integration rule

Do not build against provider-specific callbacks in your app. Build against Open Rails checkout sessions, route metadata, and merchant webhooks. Provider details should remain an operational routing decision.

​
Next steps

Start with the quickstart, then hand the agent integration guide to your coding agent or developer.