Create a reusable checkout
Sell one product at one price with a page you can share again and again. Every buyer gets a separate payment.
On this page
One page, many customers
A checkout page is a reusable product page hosted by Railbed. Unlike an invoice, which bills one customer, it keeps accepting new buyers until you turn it off or delete it, and every buyer gets their own payment. Share it on your website, social profile or in messages, or put it behind a buy button.
Build your checkout
- Check the dashboard mode, then choose Create → Checkout page.
- In the Product card, enter the Name, an optional Description, the Price and the Currency. The preview shows how they appear to buyers; until you type a name, it shows a muted Product name in its place. The name is required.
- In the Appearance card, choose Light or dark and an Accent, or turn on Match my site to use the brand saved in Settings → Brand. Fonts, logo and header image holds the rest (Set an individual checkout's appearance).
- In the Checkout card, optionally change the Button text (it defaults to Continue to pay and the price). This is the button inside the checkout; a buy button on your website has its own label.
- In the same card, choose the Provider choice: Smart Routing (the default), Buyers choose or One provider. How buyers reach a provider explains each.
- If you turned on crypto payments in Settings, Accept crypto payments lets buyers at this checkout pay in USDC or USDT from their own wallet instead of by card. Turn it off to keep this checkout card only.
- Under More options, add a success URL if you have a thank-you page (below).
- In the Ask buyers for card, choose what buyers fill in besides their email (Ask buyers for their details).
- Choose Create checkout page. The saved checkout opens on its Share tab.
In Live mode, a checkout needs a payout wallet that can receive Live payments. Until the business has one, the editor says why and offers the fix, or Test mode to try it out.
Names can be up to 80 characters; descriptions up to 280. Prices go up to 100,000.00 in USD, EUR, GBP, CAD, AUD, INR or SEK, and start at the smallest card payment (about 2.00 USD, shown under the price field): a lower price is refused, and a small one gets a note saying which providers can take it and where buyers may have only one. Smart Routing then checks the providers available to each buyer.
Choose how buyers reach a provider
Provider choice in the Checkout card decides what happens after the buyer enters their email. It applies to this checkout, including any widget or buy button that uses it.
- Smart Routing sends each buyer straight to the best card provider for their country, amount and currency. Their one click on Continue to pay opens the provider. New checkouts start here.
- Buyers choose shows Smart Routing's ranked list, with the best match selected, and the buyer picks. Checkouts made before this setting existed use it until you change them.
- One provider sends every buyer to the provider you pick. The editor shows the provider's minimum and warns when your price is below it (or asks you to check, when the minimum is in another currency), when the provider isn't taking payments, or when it serves only some countries.
With One provider, If it can't take a buyer, use Smart Routing instead is on by default: a buyer the provider can't serve (another country, below its minimum, or while it's down) goes to the best provider for them, and the payment's timeline says why, such as “Stripe doesn’t take buyers in South Korea, so Smart Routing chose Banxa” (reasons). For a provider that serves only some countries, the editor says so with the switch on too: “Only buyers in … can pay with Stripe. Other buyers go to Smart Routing’s pick.” Turn it off only if every buyer must use that provider. Buyers it can't serve then see a message and can't pay at this checkout, and no payment is created. Apple Pay and Rampnow, which pay on Ethereum, need the switch on, because the smallest order they take changes from day to day (the editor shows their minimum as “about”).
In every mode, a buyer can choose Choose another way to pay to see the full list, including after a declined card. A buyer who comes back without paying sees the providers they already tried last, and Smart Routing sends them to one they haven't tried (details). The payment's timeline shows who chose each provider: Smart Routing, your checkout's setting, or the buyer. Shopify stores and WooCommerce have the same setting on their setup pages (Integrations). Invoices have their own Card providers setting, which starts on Buyers choose (details), and custom API checkouts always show the list.
Ask buyers for their details
Every buyer gives their email. The Ask buyers for card decides what else the checkout asks, and the preview shows the fields as buyers will see them. Each detail is Don't ask, Optional or Required. Invoices have the same card, titled Ask the customer for.
| Detail | Use it for | Where it goes |
|---|---|---|
| Name | Knowing who paid | The order, the customer and webhooks |
| Phone | Delivery questions or a call back | The order and the customer |
| Date of birth | Age-restricted products. With Required, you can set a Minimum age (13, 16, 18, 21 or 25 or older): a younger buyer is told they can't buy this before anything is charged. It records what the buyer says; it is not an ID check | The customer |
| Delivery address | Something to ship. A paid order with one waits in Orders → Not fulfilled | The order and the customer |
| Billing address | Invoices and receipts | The order and the customer |
Under More to ask, Email list box (turn on Show it) adds an unticked "Email me news and offers" box. Buyers who tick it show under Customers → Subscribed; an unticked box never removes someone who joined before. Railbed keeps the choice and shows it to your systems; it doesn't send the emails.
Your own questions (up to five, with Add a question) ask for one line of text each, such as a player ID or a Discord username. Mark a question required when you can't deliver without the answer. Answers appear on the order, in its CSV export and in your webhooks and API under the key shown beside the question (player_id for "Player ID"). Questions can be in any language: one with no Latin letters gets a key like question_1, and a key never changes once the question is saved.
Buyers who leave a required field out are told which one before anything is sent. A buyer who tries again after a declined or expired attempt fills the form in again (the page never shows what an earlier attempt gave, since anyone who knows their email could open it), and the new attempt replaces the earlier details on the same order. Changing the settings affects buyers from then on; orders already placed keep what they have.
Share the saved page
The Share tab holds the hosted URL and QR code. Open the actual checkout to check the buyer view, then copy the URL wherever customers will find it.
The status beside the checkout's name is what a buyer opening the link would find: Active when they can pay, or why they can't, such as Turned off, Needs a payout wallet or Turned off by Railbed. A Test checkout is marked Test mode, and only your team can pay it. When you're ready to sell, Recreate in Live makes a Live copy with the same name, price, questions and settings and its own link; share that one. While buyers can pay a Live checkout, its Share card says Buyers pay real money here. To try the buyer’s steps without paying, switch to Test mode.
A checkout address looks like this:
https://pay.railbed.io/c/your-checkout-slugThe slug is the final part of the saved address. It is also what the embed code uses. Use the URL Railbed gives you instead of typing a slug from the product name.
To take payments on your own website, use Add it to your site in the Share tab. Widgets and buy buttons covers the formats and copyable HTML.
See how it's doing
The Last 30 days card at the top of the Share tab counts Views, Started, Paid and Drop-off for this checkout, split by where buyers started: Public widget (its page or code pasted on your site) or Your site (API) (sessions your server made). Views count only while the checkout was on screen.
Edit an existing checkout
Open Checkouts, choose the checkout, then select the Edit tab. Change what you need and choose Save changes. The Share and Edit tabs keep sharing controls separate from your product settings.
The hosted URL stays the same when you edit the product. Future payment creation uses the updated checkout details. A buyer who already has the page open when you change the price or currency is shown the new price and asked to check it before paying, so nobody is charged an amount they didn't see; the editor says so when you change it. Payments already created retain their saved amount and description, so do not expect an edit to rewrite an existing customer's order.
Currency becomes fixed once a payment reaches a card provider, or a payment is paid or needs your decision. If the field is locked, create a new checkout to sell in a different currency. For a different checkout kind, create that kind separately.
Use a success URL
Set After payment, send buyers to under More options:
https://example.com/thanks?payment={PAYMENT_ID}In Live mode it must be a public https:// page on your own site: an http:// address, localhost, a private network address, an address with a username and password, or a Railbed link (a checkout's own link, say) is refused, because a buyer who has just paid couldn't open it, or would be shown a fresh checkout and pay again. Test mode also accepts http:// and localhost for trying things out.
Railbed fills in the payment ID after confirmation. Reusable checkout payments do not have your own order reference, so {REFERENCE} would be empty. Use an API integration if every order needs a reference or customer-account metadata supplied by your server.
A redirect is a convenience for the buyer. For manual delivery, check the payment in the dashboard. For automatic delivery, use verified webhooks or authenticated payment retrieval.
Stop accepting new buyers
To stop sales for a while (sold out, a holiday, a price review), open Edit → Turn off checkout page. Buyers who open the link or a button using it see that it isn't available right now, and nothing can be paid. Turn on in the Share tab, or in Edit, brings it back with the same link, QR code and embeds. Payments buyers already started still finish.
To stop for good, open Edit → Delete checkout page and choose Delete. This can't be undone: the link, its QR codes and any embedded button or widget using it stop working, and a new checkout gets a new link. Past payments remain in Payments. Deleting the checkout is not a refund or a cancellation of payments that already exist.