Connect Railbed to your store and tools
Set up Shopify or WooCommerce, connect Slack, Telegram, Zapier, n8n or an AI assistant, and give your developer what they need for a custom checkout.
On this page
Choose a supported connection
Open Integrations. It groups everything you can connect:
| Section on the page | What's there |
|---|---|
| Ways to take payments | Invoices, Checkouts and buy buttons, Checkout API, WooCommerce and Shopify. The way you chose while setting up is marked Your main way |
| Your team’s tools | Slack: alerts, a daily report and invoices in your team's Slack |
| Automation | Zapier and n8n |
| Card providers | Which card providers your buyers are offered, and in what order. See Choose which card providers buyers see |
Telegram isn't on this page: each person connects their own Telegram in Settings → Telegram (below).
| Your setup | Start here |
|---|---|
| No website, or you bill customers one at a time | Invoices |
| A website with an HTML or custom-code block | Widgets and buy buttons |
| A Shopify store | Set up Shopify |
| A WordPress store using WooCommerce | Install WooCommerce |
| A custom store, app or game | Give your developer the API quickstart |
For a different store platform, use a website embed or ask your developer to use the API.
Set up Shopify
Railbed Checkout for Shopify keeps buyers in your store's cart, then takes them to Railbed's checkout to pay by card. Shopify prices the order, including shipping, tax and discounts, and each paid checkout becomes a real Shopify order with the customer attached.
Before you start:
- You're the store owner, or staff with Shopify's App developer role. In Railbed, you're an Owner or Developer.
- Your store sells in USD, EUR, GBP, CAD, AUD, INR or SEK and has at least one product.
- Your store uses a theme. Headless storefronts (Hydrogen) aren't supported.
- You can stop and come back at any step; Railbed keeps your progress.
Open Integrations → Shopify and follow its four steps. Railbed checks each one on your store and opens the next when it passes.
- Connect your store. Type your store's .myshopify.com address, your own domain or any link to the store, then choose Connect store.
- Create the Railbed app in Shopify. Choose Open the Dev Dashboard, then: under Apps, choose Create app and Create app manually (some accounts read Start from Dev Dashboard); on the form that opens, type the App name the setup page shows, paste the App URL and Scopes from the setup page (each has a copy button) and choose Create app, then Release if Shopify asks (where Shopify asks for the name alone first, the two fields are on the app's Versions page); in the app's Settings, under Access requests, choose Manage beside Protected customer data, select Customer data, give a reason (App functionality) and choose Apply reasons, do the same for First and last name, Email, Phone number and Address, then Save; choose Install app, in the ⋮ menu on the app's row in the Apps list or at the top of the app's Installs card, and pick your store (again, if you installed it before allowing the data); and paste the Client ID and Client secret from the app's Settings into Railbed. The setup page draws each Shopify screen. Shopify renames these screens from time to time: if yours reads differently, look for the same fields.
- Add Railbed to your theme. In Online Store → Themes → Customize, add a Custom Liquid section to the footer, paste the code from the setup page, set Top and Bottom padding to 0 and save. If your theme has no Custom Liquid section in the footer, the setup page shows where to paste it instead. The step reads Connected once Railbed sees the code on your store.
- Try it, then go live. Choose Open store preview, place a test order and check it in Shopify, then choose Go live.
Going live needs the app checks passed and a payout wallet that can take Live payments. If the saved wallet can't (a token's address, say, or an address with a typo), the step says why and links to Settings. Until a checkout from your store has reached Railbed, the step notes You haven’t placed a test order yet. Try the whole checkout first through the store preview, where nothing is charged. It doesn't stop you going live.
Until you go live, only browsers that opened the preview link see Railbed's checkout, and test orders arrive in Shopify tagged railbed-test. Your buyers keep Shopify's checkout. Going live affects only this store; the dashboard's Test and Live switch only changes which payments you're viewing.
Checkout settings and ad tracking
Two cards under the steps hold the store's options. Checkout settings:
| Setting | What it does |
|---|---|
| Thank-you page | Where buyers land after paying; empty means your store's home page. Use a page on your store, so the cart empties after payment |
| Provider choice | As on checkout pages. New stores start on Smart Routing, which sends buyers straight to the best provider. Choose Save provider choice after changing it |
| Railbed only | Off by default: when Railbed's checkout can't open, Shopify's takes over so the sale isn't lost. On, buyers see "Checkout is unavailable right now" and can try again |
| Express checkout buttons | Switch off "Show accelerated checkout buttons" in the theme editor: Shop Pay, PayPal and other express buttons skip Railbed's checkout |
The card also says the smallest card payment in your store's currency; smaller carts stay in Shopify's checkout.
Ad tracking takes your Meta, Google, TikTok or affiliate tracker details, so Railbed reports purchases made on its checkout to your ad platforms. Test mode never loads ad tags.
Recent checkouts
Once the store has checkouts, Recent checkouts lists the latest, Test and Live. Each row links to the payment's details (the dashboard switches to that checkout's mode on the way):
| You see | What happened |
|---|---|
| Couldn’t start, with the reason | The buyer pressed Pay and no payment started. Nothing was charged |
| Expired · Didn’t pay at a provider | The buyer went to the provider and no payment came back in time (Didn’t finish paying when they chose crypto) |
| Expired · Left before choosing how to pay | The payment started, but the buyer never reached a provider |
| Expired · Left before paying | The buyer reached Railbed's checkout but didn't press Pay |
When a checkout expired, the list adds An expired checkout means the buyer didn’t finish paying in time. Your checkout still works. Money that arrives after a payment expired still settles it, and the row then reads Paid. If a paid order couldn't be created in Shopify, its row offers to send it again.
What stays with Shopify
Some carts go to Shopify's own checkout instead: subscriptions, gift cards, bundles, a currency other than your store's, and totals under the card minimum. Checkout apps such as upsells don't run on Railbed's checkout. The setup page's Good to know lists the rest.
The draft order holds the stock while the buyer pays. If an item still sells out before the payment settles, the paid order is created in Shopify as usual and the Railbed order is marked Needs your decision with the reason "sold out before payment settled". If Shopify doesn't confirm the stock, the reason is "stock could not be confirmed in Shopify". Either way you get an email (and a Telegram or Slack notice if you connected one), so check stock before fulfilling it. Fulfilling or canceling the order in Shopify clears the mark.
After you go live, Railbed keeps checking the store. If it stops taking checkouts, loses the code, or a paid order can't reach Shopify, you get a notice and the setup page says what to fix.
If something gets in the way
| You see | What to do |
|---|---|
| The app check says Shopify refused the app’s request (HTTP 403) | The app's IP allowlist is turned on, and Railbed's servers aren't on it. In the Dev Dashboard, open the app's Settings, choose Manage under IP allowlist, turn off Enforce IP allowlist and save. Then choose Check again on the setup page. A store's own app doesn't need an allowlist |
| Buyers see Shopify's Are you sure you want to leave page before Railbed's checkout | Shopify's link protection asks before some moves to another website. It doesn't ask for Railbed's checkout today. If your buyers ever see it, open Online Store → Preferences in Shopify, and under Trusted domains add railbed.io |
| Order updates stopped after you changed the app's client secret | Shopify keeps signing with the old secret until you revoke it. Revoke the old secret in the app's Settings, then choose Check again |
Install WooCommerce
The plugin needs WordPress 6.9 or later, WooCommerce 10.9 or later and PHP 8.1 or later. It supports classic checkout and Checkout Blocks. The store must use HTTPS for Live checkout.
Open Integrations → WooCommerce and follow its four steps. Railbed checks each one as you go. The page follows the dashboard's mode: set up in Live to take real payments straight away, or switch to Test mode in the sidebar's business menu to try it first.
- Add the plugin. Download the ZIP from the setup page. In WordPress, open Plugins → Add new plugin → Upload plugin, choose the ZIP, then Install now and Activate. The same plugin runs Test and Live.
- Connect Railbed. Create an API key on the setup page and copy it (Railbed shows it once), then add your store's webhook by typing your store's address. In WooCommerce → Settings → Payments → Railbed, set Payment mode to match, paste the key and the webhook secret into that mode's fields and choose Save changes. Keep both values private.
- Send a test webhook. Choose Send a test webhook on the setup page. Reload the plugin settings and confirm they say Connection verified.
- Place an order. In the plugin settings, tick Enable and save. In Test mode, open the preview link shown under Who sees Test mode, check out with Pay by card and choose Simulate successful payment. In Live mode, try one small order yourself before telling customers.
The WooCommerce order waits as Pending payment while the buyer pays, and becomes Processing (or Completed for an order of only virtual, downloadable items) when Railbed confirms the payment. In Test mode shoppers don't see Railbed: only signed-in store managers and browsers that opened the preview link do.
The setup page's Checkout settings card holds the Provider choice for all your WooCommerce orders, in Test and Live. Your first WooCommerce key starts it on Smart Routing, so buyers go straight to the best provider. The plugin needs no change.
The WooCommerce guide has the connection details, requirements and recovery notes.
Move the store to Live
If you set up in Test first, check your payout wallet, switch the dashboard to Live and repeat steps 2 and 3 there: Live has its own key and webhook. Then set the plugin's Payment mode to Live and save. Keep Enable on only once the connection is verified and you're ready for customers.
Test orders keep their Test mode when you change the plugin's mode. A mode switch never turns an old Test order into a real payment.
What connects the payment to the order
The plugin creates a payment for the order, sends the customer to checkout, and verifies the result before marking the order paid. A signed webhook starts the check; the plugin then reads the payment through the API.
The customer's return to the store is not proof of payment. If the store and Railbed disagree, compare the payment ID, mode and status, then check webhook delivery and WordPress cron. See Troubleshooting.
Follow store orders and customers
New WooCommerce checkouts send the purchase details to Orders and the buyer to Customers: items, quantities and variants, coupon discounts, shipping, tax, addresses and a link back to WooCommerce.
- Fulfil in WooCommerce. Completed marks the Railbed order fulfilled; moving it back to Processing or On hold marks it not fulfilled. Updates retry in the background. If one still fails, read the order's private note and use Order actions → Send fulfilment status to Railbed.
- Sold out while paying. The order still completes and gets a private note asking you to check stock before fulfilling it.
- Cancellations and refunds recorded in WooCommerce show on the Railbed order's timeline. They never move money: arrange any refund with the buyer yourself.
- A payment that needs your decision puts the WooCommerce order On hold until you decide in Railbed.
- Updates. WordPress offers new plugin versions like any other plugin.
If a store extension makes the line totals inconsistent, the plugin sends the order as a single total instead; its private note and the WooCommerce order keep the breakdown. The WooCommerce guide covers upgrades and sync details.
Connect Telegram
Railbed in Telegram sends you alerts and lets you check sales and create invoices from your phone. Each person connects their own Telegram, and what it lets them do follows their role.
- Open Settings → Telegram and choose Connect Telegram.
- In Telegram, tap Start in the chat with Railbed, then Connect. The link works once and lasts 10 minutes.
- Back in Settings, choose your alerts and choose Send test alert to check it works.
| Setting | What it does |
|---|---|
| Alerts | Paid and Needs your decision are on to start; Checkout started, Declined and Expired unpaid are optional |
| Test payment alerts | Alerts for Test payments, labelled Test |
| Daily summary | Yesterday's Live sales, what reached your wallet and anything waiting on you, at the hour you choose in your time zone, or off |
Railbed also messages you about account changes, such as a changed payout wallet, a failing webhook endpoint, a Shopify store problem or two-factor sign-in turned on or off.
In the chat, type /stats, /recent (the latest paid payments), /review (payments that need your decision), /link 49 Logo design (an invoice for one amount, if your role can create invoices), /balance or /help. /app opens the Railbed app inside Telegram for sales, payments and invoices. Accepting a payment that needs your decision stays in the dashboard.
If you're on more than one business, Telegram works with the first one your login joined. Disconnect from Settings, with /disconnect, or in the app inside Telegram.
Connect Slack
Railbed for Slack posts payment alerts and a daily report in the channels you choose, and lets your team check sales, create invoices and accept payments from Slack. An Owner or Developer connects it from Integrations → Slack. See Railbed for Slack.
Connect automation tools
The Automation section lists the tools that work with Railbed. They connect with a secret key and signed webhooks, so there's nothing to switch on in Railbed. On each setup page, an Owner or Developer chooses Create a secret key; choose Full access, because a Read only key can't start a workflow when a payment is paid.
- Zapier (Integrations → Zapier): choose Open Railbed in Zapier to accept the invite, connect your key, then pick a trigger such as New Paid Payment. Railbed offers triggers for paid payments, payments that need your decision, expired or failed payments, orders and customers, searches, and Update Order Fulfilment. Zapier guide.
- n8n (Integrations → n8n): install the Railbed node from Settings → Community nodes, connect your key, then add Railbed Trigger or import one of the example workflows. n8n guide.
Fulfil orders only from a paid payment. Each payment trigger adds a webhook endpoint you'll see under Developers; it's removed when you turn the Zap or workflow off.
Connect an AI assistant
The official MCP server connects Claude, ChatGPT, Codex, Cursor and other assistants to one Railbed business, in Test or Live, with Read only or Full access. Your assistant can read your records and prepare changes; you confirm each change in Railbed. To start, open Developers → AI assistants and pick your assistant; the same card lists what's connected and lets you disconnect it. Set up your assistant.
Give your developer the right resources
You don't need the API to send invoices. For automatic order delivery, a custom purchase screen or account metadata, share these guides with the person connecting your system:
- Developer quickstartCreate and check a payment from a server.
- Fulfil orders safelyConfirm the right order and prevent duplicate delivery.
- WebhooksReceive signed payment events and recover missed deliveries.
- Your own checkoutBuild a custom purchase screen while card entry stays with a provider.
Create keys and endpoints in the matching mode. Secret keys and signing secrets belong in your server or store settings, never in a public web page, widget snippet or customer message. A key that only looks things up, such as one for a reporting tool, can be Read only.
Let an AI agent connect
An AI coding assistant can ask for its own access instead of being given a key: it reads railbed.com/auth.md, gives you a link, and you approve it on a Railbed page, choosing Test or Live and Full access or Read only. Owners and Developers can approve agents. Connected agents appear under Developers → AI assistants, where you can disconnect them. How agent sign-in works.