Create a store
Add your name, logo, colors, and payout preferences in sandbox mode.
Backup checkout for serious merchants
Accept payments when cards, Stripe, or PayPal stop working.
Open Rails gives merchants a branded hosted checkout that can route buyers to cards, wallets, local rails, and stablecoins without making the merchant stitch providers together.
Share a checkout
Sell with hosted payment links first. Embed checkout later when ready.
Send events
Give your developer one webhook and one API contract for fulfillment.
Merchant setup
No-code link
Developer handoff
Typed API
Payment rails
Cards + crypto
Funds
Provider direct
Live checkout performance
Seven-day revenue, route health, and provider status from sandbox data
Gross revenue
$422,980
Before gateway fees
Net revenue
$400,862
After provider cost
Payments
1,049
54 failed attempts
Route mix
Primary rails selected by health, region, and method.
Card checkout
Wallet transfer
Local methods
Merchant receives
$111
Provider estimateTransak
Gateway take4.0%
Webhooktyped
Private model workspaceTimed Out
Prompt automation packSucceeded
Creator AI Pro - annualSucceeded
Routes across the payment methods merchants already need
USDC
USDT
Base
Polygon
Solana
Tron
MoonPay
Transak
Onramper
Ramp
Easy onboarding
Start as a merchant. Hand off to a developer only when needed.
A merchant can configure a branded hosted checkout without writing code. When they are ready for automation, Open Rails gives their team one API, one webhook payload, and an agent-readable capabilities file.
Merchant
Create a sandbox workspace
Store name, payout wallet, supported tokens, checkout color, redirect URL, and webhook URL live in settings.
Checkout
Preview hosted checkout before engineering starts
Test the provider route, preview the buyer handoff, and see fake settlement data in the dashboard.
Developer or agent
Integrate with typed contracts
Use docs, API schemas, planned CLI commands, and /api/agent/capabilities to wire fulfillment.
The problem
The painful part is not crypto. It is keeping checkout alive.
Merchants lose revenue when a single processor goes down. Integrating multiple providers means multiple dashboards, multiple webhook schemas, and no unified view of what happened. Open Rails gives them a control plane for payment continuity.
Processor fragility
One provider outage kills conversion. Merchants need automatic fallback across cards, onramps, and wallets.
Provider sprawl
MoonPay, Transak, Ramp, Onramper each expose different APIs, callbacks, and settlement flows.
Data fragmentation
Payment IDs, customer records, fees, and status live in five dashboards instead of one.
Control plane
One integration. Hosted checkout, routing, and webhook delivery.
The buyer gets routed to the best provider. The merchant keeps one dashboard, one checkout session model, one event schema, and one fee policy. No custody -- providers handle the regulated work.
Route policy
Best available
Failover
Automatic + rules
Settlement
Provider direct
Card-to-stablecoin
Show one checkout amount. Track provider quote, spread, gateway take, and merchant receive behind the scenes.
Hosted and embedded
Offer hosted checkout pages or an embedded widget. Provider selection stays behind a merchant-controlled UX.
Unified ledger
Customer metadata, order IDs, payment attempts, provider references, and reconciliation exports in one place.
Non-custodial
Open Rails is software and routing infrastructure. Providers handle KYC, risk, acceptance, and settlement.
How it works
The merchant sees Open Rails. The provider does the regulated work.
Merchants configure checkout and webhooks in the dashboard. Buyers complete a provider-backed payment flow. Open Rails records state and delivers a normalized event.
Step 1
Merchant creates checkout
Product, amount, customer metadata, redirect URL, webhook URL, route policy, and fee take.
Step 2
Buyer sees a branded payment page
Hosted checkout or embedded widget routes the buyer into the best available payment rail.
Step 3
Provider confirms payment
The onramp, wallet, or stablecoin provider runs compliance and calls back with state.
Step 4
Open Rails delivers one event
One typed webhook payload for success, failure, refund, abandoned checkout, and replay.
For developers
Typed webhooks, not provider callbacks.
Every checkout event follows one schema. No parsing five different provider callback formats. Build against a single contract and let Open Rails normalize the rest.
payment.paid
{
"id": "evt_chk_nimbus_1056_paid",
"type": "payment.paid",
"livemode": false,
"created": "2026-05-26T14:32:00Z",
"data": {
"session_id": "chk_nimbus_1056",
"customer_id": "cus_nimbus_42",
"status": "paid",
"amount": 116,
"currency": "USD",
"asset": "USDC",
"network": "Base",
"route": {
"id": "card-bridge-a",
"kind": "card",
"label": "Credit card",
"provider": "MoonPay"
},
"fees": {
"buyer_fee": 3.71,
"gateway_fee": 3.48,
"merchant_net": 112.52,
"total": 119.71
},
"tx_hash": "0xabc123",
"metadata": {
"order_id": "ord_284"
}
}
}One event schema
Success, failure, refund, and abandoned -- all the same shape. No provider-specific parsing.
Route metadata
Every event includes which provider handled the payment, which rail was used, and why it was selected.
Webhook replay
Missed an event? Replay any webhook from the dashboard or API. Full delivery log with timestamps and response codes.
Pricing
Fees inside the transaction, not surprise invoices.
The gateway fee is embedded in the checkout calculation so merchants always know the take before the buyer pays. Platform plans unlock higher limits, priority routing, production credentials, and dedicated support.
Launch pricing
- Starter
- $199/mo + 1.5%
- Growth
- $499/mo + 1.0%
- High-risk routing
- $1k+/mo + 3-5%
- Provider cost
- Passed through
All plans include hosted checkout, typed webhooks, merchant dashboard, and multi-provider routing. Provider fees are always passed through at cost.
Give merchants a payment backup plan before they need one.
Non-custodial stablecoin checkout with provider routing, failover, and typed webhooks. Get started in minutes.