# Railbed user guide > How to use Railbed as a merchant: set up an account and payout wallet, take card payments with invoices, checkout pages, pricing tables and buy buttons, follow orders and customers, decide on payments that need a decision, move money from your wallet to your bank, and fix common problems. Every page below is also available as Markdown. Key facts: - Buyers pay by card on a Railbed-hosted checkout; card details are entered with a licensed on-ramp provider, never on Railbed's pages. - Card payments settle almost always as USDC on the Polygon network, directly to the merchant's own self-custody wallet; a few card routes (Apple Pay, Alipay, WeChat Pay, Rampnow and Venmo on Ethereum, Cash App as USDT on BNB Chain) settle on another network to the same wallet, and crypto payments, which the merchant turns on, settle to the same wallet or to the wallet the merchant saved for that network. Each is valued in dollars. Railbed is non-custodial and never holds, pools or controls funds. - Smart Routing ranks the available on-ramp providers for each buyer by country, amount and currency, sending each buyer to the providers least likely to ask for ID. The providers decide whether to run identity checks. - Railbed adds no underwriting, review or restrictions of its own. Signup is self-serve, with no credit check and no documents, and nothing is held back from a merchant's sales. A merchant needs a business name, an email address and a Polygon wallet address they control. - Fees come out of the USDC that arrives: the on-ramp provider's own fee and spread, a 1% network fee, and the Railbed fee, from 0.9%, shown in the dashboard when the payment starts. - Available today: invoices (shared by link or emailed, paid in full or in parts), reusable checkout pages, pricing tables and website buy buttons, a REST API for checkout sessions, payments, orders and invoices, signed webhooks (HMAC-SHA256), WooCommerce, Shopify, Zapier and n8n integrations, an official MCP server for AI assistants, and a test mode that simulates payments. - Railbed cannot reverse a settled payment, so a settled sale can't be pulled back from the merchant's wallet. Merchants handle refunds; card disputes are handled by the on-ramp provider that charged the card. - Built for businesses such as supplements, adult content and apps, AI companion apps, iGaming and gambling apps, CBD and hemp, dating, vape, online courses and coaching, and digital goods. Railbed doesn't underwrite, review or judge what a merchant sells. Each industry has its own page at https://railbed.com/industries/. ## Start here - [Your guide to getting paid](https://railbed.com/docs/user-guide.md): Set up your business, take your first card payment, and follow every sale to your wallet. Start here. - [Set up your account](https://railbed.com/docs/user-guide/getting-started.md): Go from a new account to a checkout you can share, with the right business details and payout wallet in place. - [Test and Live mode](https://railbed.com/docs/user-guide/test-and-live.md): Practice the buyer experience without moving money, then prepare a separate checkout for real customers. ## Take payments - [Send invoices and get paid](https://railbed.com/docs/user-guide/invoices.md): Bill a customer for one amount or line by line, with a discount, tax and a due date if you need them. Share its link or email it with its PDF, let them pay in full or in parts, and follow every payment. - [Invoices made in other apps](https://railbed.com/docs/user-guide/payment-links.md): Invoices made while setting up, in Telegram or Slack, through the API or by an AI assistant ask for one amount. Share their link or QR code, follow them, and edit, cancel or copy them. - [Create a reusable checkout](https://railbed.com/docs/user-guide/checkout-pages.md): Sell one product at one price with a page you can share again and again. Every buyer gets a separate payment. - [Offer plans with a pricing table](https://railbed.com/docs/user-guide/pricing-tables.md): Present up to four packages side by side, highlight one recommendation, and let buyers choose the right one. - [Add Railbed to your website](https://railbed.com/docs/user-guide/widgets-and-buttons.md): Keep customers on your site while they choose what to buy. Copy a small HTML snippet; Railbed handles the checkout. - [What your customer sees](https://railbed.com/docs/user-guide/buyer-experience.md): Understand the card checkout, provider choice and return journey so you can confidently guide a customer through payment. - [Accept crypto payments](https://railbed.com/docs/user-guide/crypto-payments.md): Let buyers pay from their own wallet in USDC, USDT, Bitcoin and other coins, beside card. It's off until you turn it on, and the money goes to your own wallets. ## Orders and customers - [Manage orders and fulfilment](https://railbed.com/docs/user-guide/orders.md): See what a customer bought, review their payment attempts, and keep track of what still needs to be delivered. - [Understand your customers](https://railbed.com/docs/user-guide/customers.md): See a customer's order history, contact details and spending. Keep a private note and manage the personal data saved in Railbed. - [Find records across Railbed](https://railbed.com/docs/user-guide/search.md): Jump to an order, customer, payment, invoice or setting from anywhere in your dashboard. Search by a name, amount, email or record ID. ## Manage your money - [Find and understand a payment](https://railbed.com/docs/user-guide/payments.md): Search across your invoices, checkouts, store and API payments. See what happened, what arrived and what to do next. - [Payments that need your decision](https://railbed.com/docs/user-guide/held-payments.md): Why a payment reads Needs your decision or Not received, and when you can choose to accept the amount that arrived. - [Understand your wallet and settlement](https://railbed.com/docs/user-guide/wallet-and-settlement.md): Know where the money goes, how received totals are calculated, and why your checkout price and wallet balance can differ. - [Move money from your wallet to your bank](https://railbed.com/docs/user-guide/move-money-to-your-bank.md): Your sales are already in your own wallet. Sell the USDC for dollars through an exchange or your wallet app, then withdraw it to your bank. ## Your business - [Make Railbed your own](https://railbed.com/docs/user-guide/branding-and-settings.md): Put your business name, logo and brand on checkout, choose how Railbed reaches you, secure your sign-in and manage your team. - [Work with your team](https://railbed.com/docs/user-guide/team.md): Invite the people you work with, give each one the role they need, and change or remove access at any time. - [Connect Railbed to your store and tools](https://railbed.com/docs/user-guide/integrations.md): 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. - [Railbed for Slack](https://railbed.com/docs/user-guide/slack.md): Connect your Slack workspace to get payment alerts and a daily report in the channels you choose, check your account, create invoices and accept payments without leaving Slack. - [Use Railbed on your phone](https://railbed.com/docs/user-guide/mobile.md): Manage payments from your phone's browser, move around with the tab bar, and add the dashboard to your Home Screen for quicker access. ## Help and reference - [Find your next step](https://railbed.com/docs/user-guide/troubleshooting.md): Start with the symptom, check the current payment state, and take the next action without losing track of the order. - [Railbed, in plain language](https://railbed.com/docs/user-guide/glossary.md): A short reference for the words you will see in checkout, the dashboard and your payment records. ## Optional - [The whole user guide in one file](https://railbed.com/docs/user-guide/llms-full.txt) - [Developer docs and API reference (llms.txt)](https://railbed.com/docs/llms.txt) - [Railbed company overview (llms.txt)](https://railbed.com/llms.txt) - [Sign up](https://app.railbed.io/signup) · [Log in](https://app.railbed.io/login) --- # Your guide to getting paid > Set up your business, take your first card payment, and follow every sale to your wallet. Start here. Source: https://railbed.com/docs/user-guide/ · Updated: 2026-11-18 · Railbed user guide New to Railbed? [Set up your account and try a Test payment](https://railbed.com/docs/user-guide/getting-started.md). **Visual example: How a payment works.** 1. Share your checkout: Send an invoice or publish a reusable checkout. You set the price. 2. Your buyer pays by card: They choose an eligible provider and pay on its page. Provider checks may apply. 3. Confirm the payment: Read the payment status and reported USDC settlement in Railbed. Your wallet · Polygon. Deliver only when the payment is Paid. A browser return does not confirm payment. *The Live payment journey. In Test mode, the provider and settlement are simulated.* ## Start with your first payment A customer pays by card. You receive USDC, usually on Polygon, in a wallet you control. Railbed gives you the checkout, a record of each payment, and a place to manage it all. Start in **Test mode** to try the full experience without charging a card. When you are ready to take real payments, create the invoices and checkouts you share in **Live mode**. - [Set up your account](https://railbed.com/docs/user-guide/getting-started.md): Add your business, choose a payout wallet, and find your way around the dashboard. - [Try a test payment](https://railbed.com/docs/user-guide/test-and-live.md): See a successful payment, an underpayment, and a decline before going live. - [Connect an AI assistant](https://railbed.com/docs/mcp.md): Let ChatGPT, Claude, Codex or your coding agent read your records and prepare checkouts, invoices and webhook changes you confirm. ## Choose how to get paid The right starting point depends on whether you are requesting one payment or selling the same thing repeatedly. | You want to… | Use | What you share | |---|---|---| | Bill one customer | [Invoice](https://railbed.com/docs/user-guide/invoices.md) | Line items or one amount, a link or QR code, and email with reminders if you like | | Sell one product to many buyers | [Checkout page](https://railbed.com/docs/user-guide/checkout-pages.md) | A reusable page; each buyer gets a separate payment | | Let buyers choose between packages | [Pricing table](https://railbed.com/docs/user-guide/pricing-tables.md) | A reusable page with up to four plans | | Take payments inside your website | [Widget or buy button](https://railbed.com/docs/user-guide/widgets-and-buttons.md) | A short HTML snippet copied from the dashboard | | Sell on Shopify or WooCommerce | [Store integrations](https://railbed.com/docs/user-guide/integrations.md) | Railbed's card checkout in your store, connected to your account | ## Make Railbed part of your day - [Manage your orders](https://railbed.com/docs/user-guide/orders.md): See items, payment attempts and what still needs to be fulfilled. - [Know your customers](https://railbed.com/docs/user-guide/customers.md): Read purchase histories, save private notes and manage customer data. - [Understand your payments](https://railbed.com/docs/user-guide/payments.md): Find an order, read its status, and open its timeline. - [Read your wallet](https://railbed.com/docs/user-guide/wallet-and-settlement.md): Understand the difference between a balance, a sale, and the amount received. - [Make it yours](https://railbed.com/docs/user-guide/branding-and-settings.md): Set your business name, logo, support email, and checkout appearance. - [Work with your team](https://railbed.com/docs/user-guide/team.md): Invite people and give each one the role they need, including Sales. - [Work from Slack](https://railbed.com/docs/user-guide/slack.md): Get payment alerts and a daily report in your channels, and create invoices without leaving Slack. - [Solve a problem](https://railbed.com/docs/user-guide/troubleshooting.md): Find the next step for a missing payment, an unavailable checkout, or a buyer who needs help. Use [account search](https://railbed.com/docs/user-guide/search.md) to jump between records. These docs follow your device's light or dark setting; choose **Light** or **Dark** from the theme selector to fix one. [Appearance settings](https://railbed.com/docs/user-guide/branding-and-settings.md#choose-light-dark-or-match-system) explains the separate dashboard and checkout preferences. ## A few things to know **You control the wallet.** Railbed does not hold a balance for you to withdraw. Settlement goes to your own wallet. **Your buyer pays with a card provider.** They enter card details on that provider's page. Available providers and identity checks vary by buyer, country, currency and amount. **Payment status is what matters.** Check that a payment is **Paid** before delivering the order. A buyer returning to a thank-you page is not proof of payment. [Read the statuses](https://railbed.com/docs/user-guide/payments.md#understand-each-status). **Pricing tables are one-time purchases.** A monthly or yearly label does not create automatic recurring billing. Building your own store, app or game? Switch to the [developer docs](https://railbed.com/docs/index.md) for API examples and signed webhooks. These user guides focus on the dashboard and everyday merchant tasks. --- # Set up your account > Go from a new account to a checkout you can share, with the right business details and payout wallet in place. Source: https://railbed.com/docs/user-guide/getting-started/ · Updated: 2026-11-19 · Railbed user guide ## Before you begin Have these ready. Setup takes a few minutes, and you can practise in Test mode before anything is real. | You need | Why | |---|---| | Your business name and website | Buyers see the name on your checkout. The website is where buyers see what you sell, and Railbed matches your checkout to its colours, fonts and logo | | A product or service to sell | Your first invoice or checkout needs a price and a description | | The public address of a self-custody wallet on Polygon | Your sales settle there. You can add it later and practise in Test mode first | Use a wallet you control, not an exchange deposit address or a token's own address (such as USDC's contract), which Railbed refuses because money sent there can't be recovered. Smart wallets such as a Safe or Base Account work. Railbed only needs the public address: never give anyone your seed phrase or private key. Your customers see prices in USD, EUR, GBP, CAD, AUD, INR or SEK. Almost every card payment settles to your wallet as USDC on Polygon, whatever the checkout currency. A few providers pay on another network to the same wallet address, and are offered only when your payout wallet is an ordinary wallet rather than a smart contract wallet: Apple Pay (as a provider of its own), Alipay, WeChat Pay and Rampnow on Ethereum for larger orders, Venmo on Ethereum, and Cash App on BNB Chain ([details](https://railbed.com/docs/user-guide/buyer-experience.md#apple-pay-and-google-pay)). > [!TIP] > **Prefer to have an AI assistant set things up with you?** Connect ChatGPT, Claude or your coding agent through the [Railbed MCP server](https://railbed.com/docs/mcp.md). It works on your business after you sign in, and you confirm every change it prepares. ## Create your account 1. Open [Railbed signup](https://app.railbed.io/signup) and choose **Continue with Google**, **Continue with GitHub** or **Continue with email**, then complete any verification prompts. **Sign up with Google** on railbed.com takes you straight to Google's account picker. 2. In **Set up your business**, enter the name buyers should see and **Your website**, and add your logo if you like, then choose **Continue**. Railbed suggests a fix for a likely typo, such as a missing `.com`. A social or marketplace page (an Instagram or Etsy shop, say) can't stand in for a website; if that's the only place you sell, or you have no website yet, email support and the team will help you set up. 3. In **Where should your money go?**, add your payout wallet. Choose **Connect a wallet** to pick it from MetaMask, Trust Wallet, Rabby, Rainbow or any wallet that scans a WalletConnect QR code. Railbed reads the wallet's public address and disconnects; it never asks you to sign anything or approve a transaction. Or choose **Paste an address**: Railbed checks a pasted address for typos. Either way the address is shown in groups of four so you can compare it with your wallet app; choose **Continue** to save it. **Back** returns to your name and website. No wallet yet? [The wallet step helps](#no-wallet-yet), or choose **Try Test mode first** to start without one. 4. In **How will you take payments?**, choose your main way to sell. You can add the others later from **Integrations**. | Choose | When | What happens next | |---|---|---| | **Send invoices** | You bill customers one at a time, or sell without a store | Make your first invoice and share it by link or QR code. You can try a test payment first. | | **Add it to your own app or website** | You have a site or app of your own | Without a developer: make a checkout and paste two lines of HTML. With one: connect your server with a Test key, then a Live key, through the [API](https://railbed.com/docs/api.md). | | **Sell on Shopify** | Your store runs on Shopify | Enter your store address, then follow the [Shopify setup](https://railbed.com/docs/user-guide/integrations.md#set-up-shopify) page's four steps. | | **Sell on WooCommerce** | Your store runs on WordPress | Download the plugin, then follow the [WooCommerce setup](https://railbed.com/docs/guides/woocommerce.md). | 5. Back on **Home**, the **Your first payment** card lists what's left for your way to sell and ticks each step as it happens. For invoices, the first step is **Ask for your first payment**, ticked once an invoice is sent. Hide the card when you don't need it; **Settings → Setup checklist** brings it back. 6. Check the mode before sharing anything: it shows under your business name at the top of the sidebar. To practise, open that block and turn on **Test mode**; turn it off for Live. An invoice or checkout belongs to the mode in which you created it. > [!IMPORTANT] > Test mode and Live mode have separate checkouts and payment records. Switching the dashboard to Live does not convert a Test checkout into a real one. Create a checkout in the intended mode and share its new link. ### No wallet yet The wallet step has two ways to start without a wallet of your own, and a short guide: - **Create one now** opens Base Account, Coinbase's free wallet that you set up with Face ID, your fingerprint or a passkey, with nothing to install. - **New to wallets?**, under the choices, opens the steps for a wallet app of your own: install one you control, such as MetaMask, Trust Wallet or Rabby; keep its recovery phrase offline and never share it; then connect it, or copy its address (it starts with 0x) and paste it. It links to [Move money to your bank](https://railbed.com/docs/user-guide/move-money-to-your-bank.md), so you can see how sales reach your bank before you choose. - If you close the wallet list without choosing a wallet, **New to wallets?** opens by itself. If Base Account can't open in your browser, the step switches to pasting an address. - After **Paste an address**, **Other ways to add a wallet** brings the choices back. **Continue** without a complete address says what's missing under **Payout wallet address**. - **Try Test mode first**, the last choice, saves your business without a wallet and opens Railbed in Test mode, where you can make invoices and checkouts and pay them with simulated money. Live payments need the wallet: Home's **Your first payment** card starts with **Add your payout wallet**, and every page reminds you until you add it in Settings ([Change the payout wallet](https://railbed.com/docs/user-guide/wallet-and-settlement.md#change-the-payout-wallet)). Until then, Live invoices and checkouts can't be created. ### If Railbed asks you to sign in again Saving your first payout wallet needs a sign-in from the last hour, so a new account saves it without signing in twice. If you signed in longer ago (you came back to setup later, say), Railbed says **Sign in again to save your payout wallet. What you entered stays here.** After you sign in, the step shows the wallet you added with **You’re signed in again. Check your wallet, then press Continue.** Nothing is saved until you press **Continue**. Changing a saved wallet later needs a sign-in from the last five minutes ([Change the payout wallet](https://railbed.com/docs/user-guide/wallet-and-settlement.md#change-the-payout-wallet)). ## Find your way around The sidebar holds every page. On a phone, the tab bar at the bottom has **Home**, **Payments**, **Create** and **Orders**, and **More** opens the rest. | Dashboard area | What you do there | |---|---| | Home | Follow the steps to your first payment, then see what you received, your wallet, recent payments and who is buying ([Read Home](#read-home)) | | Create | Make an invoice, checkout page, pricing table or payment widget | | Orders | Review items, customers, payment attempts and fulfilment for each purchase | | Customers | See purchase histories, contact details and your private customer notes | | Payments | Search every payment, filter by status and open a payment's details | | Invoices | Bill a customer, share its link or email it, and follow what's been paid | | Checkouts | Manage reusable checkout pages, pricing tables and payment widgets | | Integrations | Connect your store, Slack, Telegram or an automation tool, and choose your card providers | | Developers | Create API keys, connect webhooks, inspect event deliveries and manage connected AI assistants | | Team | Owners invite people, change their roles and see [what each role can do](https://railbed.com/docs/user-guide/team.md#team-roles) | | Settings | Business details, brand, payout wallets, crypto payments, notifications, two-factor sign-in and appearance. Open it from your name at the bottom of the sidebar | The bell at the top of every page collects what needs you: payments that need your decision, webhook endpoints that keep failing and invitations to other businesses. For owners, its panel also lists [the latest changes to the business](https://railbed.com/docs/user-guide/branding-and-settings.md#see-what-changed). ### Read Home Choose a period at the top of **Home**: **Today**, **7 days**, **30 days**, **90 days**, **12 months** or **All time**. It starts on 30 days (Today on a phone) and remembers your choice in this browser. Today is shown hour by hour, the day periods by the day, and 12 months and All time by the month. - **Received**, **Paid payments** and **New customers** sit above a chart of what you received. Received is in dollars, after fees, whatever coin or network the money arrived in; each card compares the period with the one before it. - **Success rate** (paid payments out of the ones buyers started), **Average sale** and **Pending** (payments from the period that can still be paid) sit under the chart. Amounts stay in their own currency. - The wallet card shows your payout wallet and, in Live, its balance, with **Move to your bank** for [turning it into money in your bank](https://railbed.com/docs/user-guide/move-money-to-your-bank.md). - **Recent payments** lists the latest payments, and the card beside it follows your main way to sell: your store's connection, your API key and webhooks, or your latest checkout. - **Breakdown** shows the period's **Top providers** and **Top buyers**, and **Who started paying**: their **Devices**, **Countries**, **Languages** and **Time zones**, from the buyers' own browsers. Your name at the bottom of the sidebar opens your account menu: **Settings**, **Accounts** (the businesses you belong to), **Affiliate earnings**, **Contact support** (shows the support address to copy, or opens your email app) and **Sign out**. Use **Search** in the sidebar (the magnifier at the top of the screen on a phone), or press Ctrl+K or ⌘K, to find a record or jump to another page. [Account search](https://railbed.com/docs/user-guide/search.md) supports keyboard shortcuts and queries such as an order number, email or payment ID. The dashboard follows your device's light or dark setting until you choose **Light** or **Dark** with the switch above your name, or in [Settings](https://railbed.com/docs/user-guide/branding-and-settings.md#choose-light-dark-or-match-system). ## Make your first practice checkout 1. Open the business block at the top of the sidebar and turn on **Test mode**. Confirm the **Test mode** label is visible. 2. Choose **Create → Checkout page**. Enter an example product such as Design consultation, a price such as `49.00`, and USD. 3. Create the page, then open its **Share** tab and choose **Open it to try a payment**. 4. Follow [Try a test payment](https://railbed.com/docs/user-guide/test-and-live.md#run-a-practice-payment) to experience the buyer's steps and confirm the result in Payments. **Visual example: A reusable checkout page.** A checkout shows Northstar Studio, Design consultation, $49.00 USD and an email field. Continue to pay leads to provider selection; card details are entered on the provider's page. *Illustrative example · your product on the left, buyer details on the right.* ## Finish your business settings In [Settings](https://app.railbed.io/settings), add your logo and support email. Buyers use those details to recognize your business and get help with their order. Choose a checkout brand color and **Save settings**. Logo and profile photo uploads save as soon as you finish cropping them. [Branding and settings](https://railbed.com/docs/user-guide/branding-and-settings.md) explains where each detail appears and which changes are shared across modes. ## When you are ready for customers Open [Test and Live mode](https://railbed.com/docs/user-guide/test-and-live.md#before-sharing-a-live-link) and work through the launch checklist. Confirm the payout address, the product price and currency, the buyer experience, and how you will deliver orders after payment. For a one-off bill or deposit, send an [invoice](https://railbed.com/docs/user-guide/invoices.md). For a product you sell repeatedly, keep using a [checkout page](https://railbed.com/docs/user-guide/checkout-pages.md). --- # Test and Live mode > Practice the buyer experience without moving money, then prepare a separate checkout for real customers. Source: https://railbed.com/docs/user-guide/test-and-live/ · Updated: 2026-11-18 · Railbed user guide ## Check the mode before you create Switch modes from the business block at the top of the dashboard's sidebar: open it, then use the **Test mode** switch. On means Test mode; off means Live. The block shows the current mode under your business name, and in Test mode the app shows a Test mode banner and labels so you can tell which records you are viewing. | What changes | Test mode | Live mode | |---|---|---| | Card payments | Simulated; no card is charged | Real payments through available card providers | | Wallet card on Home | Simulated money received in the period you choose, in dollars | USDC balance read from your wallet on Polygon | | Invoices, checkouts, orders, customers and payments | Separate Test records | Separate Live records | | Provider list | Fixed for practice | Depends on current availability and buyer eligibility | | Webhooks | Real signed HTTP deliveries for simulated events | Real signed HTTP deliveries for actual events | Business details, branding, team members and the payout wallet are shared across both modes. Changing them while viewing Test mode still changes them for Live. ## Run a practice payment 1. Turn on **Test mode** and create an invoice or checkout with a sample price, such as $49. 2. Choose **Open it to try a payment**: on a checkout's **Share** tab, or on the invoice's page. This opens the buyer link as your team, so this browser can simulate payments for seven days. Continue with an email address you use for testing and choose one of the available Test providers. 3. Railbed opens a simulated provider page. Choose **Simulate successful payment**. You do not enter card details. 4. Return to the original checkout tab. It updates to the paid result, or follows your success URL if you set one. 5. Open **Payments** in Test mode. Find the payment, confirm **Paid**, and inspect the timeline and simulated receipt. You can also open [Orders](https://railbed.com/docs/user-guide/orders.md) to inspect the purchase and its attempts, then open its [customer](https://railbed.com/docs/user-guide/customers.md). These are Test records. A simulated Paid status does not represent a real charge or settlement. ## Practice the exceptions too Create a **new** Test payment for each completed-payment scenario. A declined card can be retried on the same payment. - **Simulate an underpayment:** half the amount arrives, and the payment reads **Needs your decision**, with **Underpaid** beside it. Open its details to see why and try **Accept as paid**. - **Simulate declined card:** the payment stays open. Return to the checkout tab, choose **Choose another way to pay**, and try another provider. You can then simulate a successful payment on the same checkout. - **Leave a payment unfinished:** see how an open or in-progress payment differs from a paid one. A Live card decline happens on the provider's page and is not directly reported to Railbed. The payment may stay open or in progress until it is paid or expires. Test mode teaches the UI and integration behavior; it does not prove which providers will approve a real buyer. > [!NOTE] > A configured Test webhook still sends real requests to its endpoint. Use an endpoint intended for testing, especially if your connected system sends emails or fulfils orders automatically. ## A Test link never takes money A Test checkout or invoice is marked **Test mode** on its Share card, in the copy confirmation and in its QR code's file name, including the Share cards on the setup screens. Anyone outside your team who opens it is told it's a test page and can't start or simulate a payment. A Test checkout's Share tab, and a Test invoice's page, say when people opened it from outside Railbed in the last seven days. Don't share or print a Test link: choose **Recreate in Live** on the Test checkout's Share tab, or create the invoice in Live, and share that one. When a browser outside your team is refused, the message says how your team tries that page instead: | The Test page | What the message points to | |---|---| | A checkout | **Test on your site** on the checkout's Share tab | | An invoice | **Open it to try a payment** on the invoice's page in the dashboard | | A checkout session your server made | **Turn on Test payments in this browser** on **Developers** | To try a Test checkout embedded in your own site, use [Test on your site](https://railbed.com/docs/user-guide/widgets-and-buttons.md#test-on-your-site). Without it, the embed shows **This checkout isn’t live yet** to everyone, your team included: a frame on another site can't read the test access your browser keeps for Railbed's own pages. A Live checkout's or invoice's Share card says **Buyers pay real money here. To try the buyer’s steps without paying, switch to Test mode.** while buyers can pay it. ## Before sharing a Live link - [ ] Confirm the full Polygon payout address in **Settings** against the wallet you control. - [ ] Review your business name, logo, support email and displayed Railbed fee. - [ ] Turn off **Test mode** so the dashboard is in Live, and create the invoice or checkout there. - [ ] Open that exact buyer link and confirm its price, currency, description and appearance. - [ ] Copy the Live embed code again if you are using a button or widget. - [ ] Confirm how you will deliver the order after **Paid**, and what you will do with a payment that needs your decision. - [ ] If you use a store or API integration, connect the matching Live key and Live webhook endpoint. Opening a Live checkout is different from completing a card payment. A successful Test payment does not move funds or demonstrate real settlement. ## Where did my checkout go? Check the mode first. A Test link, payment or key is not listed in Live mode, and vice versa. Switching modes changes the records you see; it does not delete them. The buyer URL already identifies its checkout or payment. Your current dashboard mode does not change what a customer sees when they open a previously shared URL. --- # Send invoices and get paid > Bill a customer for one amount or line by line, with a discount, tax and a due date if you need them. Share its link or email it with its PDF, let them pay in full or in parts, and follow every payment. Source: https://railbed.com/docs/user-guide/invoices/ · Updated: 2026-11-18 · Railbed user guide ## When to use an invoice Use an invoice when you sell by quote, by phone or in person: a consultation, a custom order, a project with several parts, a retainer, a deposit and a balance, or a sale your team closed by hand. There is one kind of invoice. For a single amount, give it one line and leave out what you don't need. It can add a discount and tax, have a due date, and let the customer pay in parts and add a tip. Invoices made while setting up your account, in Railbed in Telegram, in [Railbed for Slack](https://railbed.com/docs/user-guide/slack.md), through the [API](https://railbed.com/docs/api/payment-links.md) or by an AI assistant are listed in **Invoices** too and open their own page: see [Invoices made in other apps](https://railbed.com/docs/user-guide/payment-links.md). To sell the same product to many buyers, use a [checkout page](https://railbed.com/docs/user-guide/checkout-pages.md) instead. An invoice never moves money itself. Each payment toward it is an ordinary payment: the customer chooses how to pay on Railbed's payment page, and the sale settles to your wallet like any other. ## Build an invoice **Visual example: Build an invoice.** New invoice for Alex Morgan (alex@example.com): Brand strategy $900.00 and Logo design $350.00, due in 14 days. Your customer sees invoice INV-0042 from Northstar Studio for $1,250.00 USD, its line items, the due date and a Pay button; they pay by card through a licensed provider. *Illustrative example · two line items, due in 14 days.* 1. Check Test or Live mode, then open **Create** and choose **Invoice**, or choose **New invoice** on the **Invoices** page. The preview beside the form shows what your customer will see as you type. On a phone, switch between **Edit** and **Preview**. 2. Under **Bill to**, enter the customer's **Name** and **Email**. Start typing either one to pick a saved customer. **Company** and **Phone** are optional, and **Add a billing address** adds one. The name and email are needed only for Railbed to email the invoice: shared by its link, it can go out without them, and the customer gives their email as they pay. 3. Under **Line items**, choose the currency at the top of the card and add a line for each thing you're billing: a description, a quantity (hours can be `2.5`) and a price. **Add line** adds another, up to 50; pressing Enter in a price starts the next line. 4. **Add discount** takes a percentage or a fixed amount off the subtotal. **Add tax** adds a rate, as a percentage of what's left after the discount, and a name such as `VAT`. The total updates as you type. 5. Under **When it's due**, choose **On receipt**, **7 days**, **14 days** (the default), **30 days** or **Pick a date**, up to two years ahead. The same card holds **Remind them by email** ([below](#how-your-customer-can-pay)). 6. Under **How they can pay**, choose part payments, tips and receipts ([below](#how-your-customer-can-pay)). 7. Under **Ask the customer for**, choose what the customer fills in themselves besides their email: name, phone, date of birth or addresses, each **Don't ask**, **Optional** or **Required**. **More to ask** adds an email list box or up to five questions of your own, such as a PO number. It works as on a checkout page: [Ask buyers for their details](https://railbed.com/docs/user-guide/checkout-pages.md#ask-buyers-for-their-details). 8. **Payment settings** is folded until you change something; its summary line says what is set now: - **Card providers**: how the customer reaches a card provider. **Buyers choose** (the default) shows them the list, **Smart Routing** sends them straight to the best provider for them, and **One provider** sends them to the one you pick. With Smart Routing or Buyers choose, turn off **Offer every card provider** to tick only the providers this invoice offers. The ones offered follow your [card provider order](https://railbed.com/docs/user-guide/buyer-experience.md#provider-order). - **Pays to**: which wallet it pays, once an owner has saved another one ([below](#pay-another-wallet)). - **After payment, send them to**: your own thank-you page ([below](#send-the-customer-to-your-thank-you-page)). 9. **More details** holds a **Reference or PO number**, a **Note to the customer**, your **Terms** and, if more than one person can own invoices, its **Owner**. 10. Choose **Create invoice**, or **Save draft** to finish it later. A draft is visible only to your team, and a new invoice's form is kept if your session runs out before you save. When the invoice is created, its page opens. If it has the customer's name and email, the email is ready to send ([Send it](#send-it)). In Live mode, an invoice needs a payout wallet that can receive Live payments. Until the business has one, the form says why and offers the fix, or Test mode to try it out. You can still save a draft. | Field | What to enter | Example | |---|---|---| | Name and email | Who the invoice is made out to. Needed to email it; optional when you share its link | Alex Morgan, `alex@example.com` | | Company | Optional, up to 120 characters | Northwind Studio | | Line description | What the line is for, up to 200 characters | Brand workshop, half day | | Quantity | Up to two decimals | `2.5` | | Price | The price of one unit | `1,200.00` | | Currency | USD, EUR, GBP, CAD, AUD, INR or SEK, one per invoice | `USD` | | Reference or PO number | Optional, up to 64 characters | `PO-7781` | | Note to the customer | Optional, up to 1,000 characters, shown on the invoice and its PDF | Thank you for the project. | | Terms | Optional, up to 2,000 characters, printed at the foot of the invoice | Payment due within 14 days of the invoice date. | The total can be up to 100,000.00. Railbed checks it against the card providers' minimums for its currency (the smallest is about 2.00 USD): a total no provider can take is refused, and a small one gets a note saying which providers can take it. Split a larger sale across invoices. ## How your customer can pay | Setting | What it does | |---|---| | **Let them pay in parts** | Off by default, so they pay the whole amount at once. On, they choose how much to pay each time until the total is paid. Set a **Smallest first payment** to ask for a deposit; later payments can be any amount. Each part must still be one a card provider can take, and never more than what's left | | **Let them add a tip** | Offers 10, 15 or 20 percent of what they're paying, or an amount of their own. A tip is shown apart everywhere and never counts toward what's owed | | **Email a receipt for each payment** | On for new invoices. Each time a payment arrives, the customer gets a receipt in your name with any tip shown apart and what's left to pay | | **Remind them by email** | In the **When it's due** card. Off until you turn it on, and only with a due date. Turned on, it picks 3 days before, the due date, and 3 and 7 days after; tick other days from 7 days before to 30 days after. The card says when the first reminder goes. Reminders go in the morning (UTC) of each day and stop once the invoice is paid or voided | ## Send it An invoice can reach your customer two ways: Railbed emails it, or you share its link. - **Send invoice** (on a draft) creates the invoice and emails it in one step. **Email invoice** emails one already created. Once it has been emailed, the button reads **Send reminder**. Each needs the customer's name and email, and lets you add a message of up to 1,000 characters above the invoice. - **Get link only** (on a draft) creates it without an email. A draft with no customer email shows **Create invoice** instead. Copy the link or QR code from the **Send it** card, or use **Copy link** on its row in the list. The email comes from your business's name ("Your Business via Railbed"), shows the amount, due date and lines, carries a button to the customer's page and attaches the invoice's PDF. Replies go to the person who sent it; for an automatic reminder or receipt, to the invoice's owner, else your support address. **View as your customer** on the **Send it** card opens the customer's page without marking it viewed. **In Test mode nothing reaches the customer.** The send dialog's **Send test copy** emails a copy marked `[Test]` to you instead, and Test invoices never send reminders or receipts. An invoice can be emailed at most once a minute and ten times a day, and a business can send 200 invoice emails a day. An address that bounced or marked an earlier email as spam isn't emailed again; the send says so. The **Emails** card lists each email, who sent it (or **Automatic**), and what happened to it: **Sending**, **Sent**, **Delivered**, **Delayed**, **Bounced**, **Marked as spam**, **Not delivered** or **Not sent**. ## What your customer sees The customer opens the invoice from the email or link. They see your name and logo, the lines and totals, the due date and anything already paid. If you allowed it, they choose **In full** or **Part of it**, add a tip, and choose **Pay**. Railbed's payment page then lets them pay by card, as on any Railbed checkout, and offers **Back to invoice** when it ends. They can download the PDF at any time. A paid invoice thanks them, lists what arrived and offers **Download receipt**. The page never shows your team, the reason you voided it, or anything about your account. A Test invoice can be paid only by your team, with simulated money. ## Statuses | Status | What it means | |---|---| | Draft | Saved, not created. No link yet; only your team sees it | | Sent | Created and shared or emailed, not yet opened | | Viewed | The customer opened it | | Partially paid | Some of it has been paid | | Overdue | Unpaid or part paid after its due date. The due date runs to the end of that day everywhere, so nobody is late early | | Paid | Paid in full | | Void | You stopped collecting it | | Needs your decision | A payment toward it arrived but didn't pass a check. Open it from the invoice's page ([held payments](https://railbed.com/docs/user-guide/held-payments.md)); it counts toward the invoice only once accepted | Invoices made in other apps read **Open**, **Canceled** or **Expired** instead of Sent, Viewed and Void ([details](https://railbed.com/docs/user-guide/payment-links.md#read-the-result)). The **Invoices** page shows what's **Unpaid**, **Overdue**, **Paid** in the last 30 days (per currency) and how many **Drafts** wait; choose a figure to filter by it. Use the status chips to see **Drafts**, **Unpaid**, **Overdue**, **Partially paid**, **Paid**, **Void** or **Expired**, and the search to find an invoice by number, customer, item or reference. A part-paid invoice shows what's still due and a bar of how much is paid. ## Change, copy or stop an invoice - **Edit** changes anything until the customer starts a payment. After that, the lines, discount, tax, currency, customer, part payments and tips are fixed; you can still change the due date, reminders, receipts, note, terms and owner. Changes show on the customer's page and PDF at once. - **Duplicate** starts a new draft with the same customer, lines, discount, tax and settings, without the reference. A due date already past is left empty. The copy pays the same wallet as the original, or your main payout wallet if that wallet has been removed since. - **Void invoice** stops collection: the customer's page says it was voided, and no more reminders go. Add a reason for your team if you like; the customer doesn't see it. Money already paid stays in your wallet, and a payment already under way still completes and counts. A paid invoice can't be voided. - **Delete draft** removes a draft for good; its number isn't used again. A created invoice can't be deleted; void it instead. ## Pay another wallet An invoice pays your payout wallet unless you choose otherwise. Once an owner has saved another wallet under [Settings → Payout wallet → Other wallets](https://railbed.com/docs/user-guide/wallet-and-settlement.md#other-payout-wallets), **Payment settings** shows **Pays to**: choose the wallet this invoice pays. You can only pick a saved wallet, never type an address, and in Live a wallet Railbed's checks refuse can't be chosen. The wallet is chosen before the invoice is created; after that, **Edit** can't change it. An invoice that pays another wallet is paid by card only, because crypto payments go to your payout wallet. Changing your main payout wallet doesn't affect it. While an unpaid invoice pays a wallet, that wallet can't be removed from Settings; void the invoice first, or wait until it's paid. ## Send the customer to your thank-you page Under **Payment settings**, fill **After payment, send them to**. You can include `{PAYMENT_ID}` and `{REFERENCE}`: Example: Example success URL ```text https://example.com/thanks?payment={PAYMENT_ID}&order={REFERENCE} ``` 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 is refused, because a customer 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`. Leaving it empty shows Railbed's on-screen receipt. [The buyer experience](https://railbed.com/docs/user-guide/buyer-experience.md) explains the two-tab flow. ## PDF and export **PDF** on an invoice's page downloads it as your customer sees it; a draft is marked Draft, and a paid invoice reads as a receipt. **Export CSV** on the Invoices page downloads the list you're looking at, up to 10,000 rows. ## Sales teams Give a salesperson the **Sales** role on the **Team** page ([roles](https://railbed.com/docs/user-guide/team.md#team-roles)). They can make, send and change their own invoices and see only those; **Create** offers them invoices only. An [invoice made in another app](https://railbed.com/docs/user-guide/payment-links.md) that they own shows in their list, but only owners and managers can change it. Every invoice records who created it and who owns it, and owners and managers can give an invoice to anyone who can own one with **Owner** under **More details**. Once more than one person can own invoices, owners and managers see **By owner** on the Invoices page: each person's sent invoices, what they total, what's been paid and what's still unpaid, per currency. Choose a person to see only their invoices. An invoice made with an API key that names no owner counts under "No owner". ## Build it into your own systems Developers can create, send, void and list invoices with the [Invoices API](https://railbed.com/docs/api/invoices.md) and follow them with [invoice webhook events](https://railbed.com/docs/webhooks/events.md#invoice-events). Payments toward an invoice carry its id. --- # Invoices made in other apps > Invoices made while setting up, in Telegram or Slack, through the API or by an AI assistant ask for one amount. Share their link or QR code, follow them, and edit, cancel or copy them. Source: https://railbed.com/docs/user-guide/payment-links/ · Updated: 2026-11-18 · Railbed user guide ## Where they come from In the dashboard, every invoice is made with the [invoice builder](https://railbed.com/docs/user-guide/invoices.md). An invoice made while setting up your account, in Railbed in Telegram, in [Railbed for Slack](https://railbed.com/docs/user-guide/slack.md), through the [API](https://railbed.com/docs/api/payment-links.md) (where it's called a payment link) or by an AI assistant is simpler: it asks for one amount, can be paid once, and lasts until a date. It's listed in **Invoices** with the rest and opens its own page, described here. | | Invoice from the builder | Invoice made in another app | |---|---|---| | Amount | Line items, discount and tax | One amount | | Paying | In full or in parts, with a tip if you allow it | Once, in full | | Ends | When it's paid or you void it; it can go overdue | On its expiry date, or when you cancel it | | Email | Railbed emails it, with reminders and receipts if you choose | You send the link yourself | | Changing it | [Send invoices and get paid](https://railbed.com/docs/user-guide/invoices.md) | This page | **Visual example: An invoice made in another app.** An invoice made in Telegram: Amount 49.00, Currency USD, What it is for Design consultation, Customer's name Alex Morgan, Can be paid for 7 days. The customer sees a payment request with the amount, description and their name. *Illustrative example · a $49 consultation, payable for 7 days.* ## What it holds | Field | What it holds | Example | |---|---|---| | Amount | From the smallest card payment (about 2.00 USD) to 100,000.00 | `49.00` | | Currency | USD, EUR, GBP, CAD, AUD, INR or SEK | `USD` | | What it’s for | Optional. A customer-facing description, up to 120 characters; without one it reads "Payment to" and your business name | Design consultation | | Invoice or reference number | Optional, up to 64 characters | `INV-0042` | | Name, email and phone | Optional. Filled in for the customer on the page, where they can correct them | Alex Morgan, `alex@example.com` | | Billing and delivery address | Optional; kept on the order and filled in for the customer | 418 Linden Avenue, Portland | | Note to the customer | Optional, shown on the payment page, up to 500 characters | Consultation on Friday at 2 pm | | Can be paid for | 7 days by default, from 1 day up to a year | 30 days | It can also ask the customer for details, offer only some card providers, pay another saved wallet and send the customer to your own page after paying, as a [built invoice](https://railbed.com/docs/user-guide/invoices.md#build-an-invoice) can. Its page shows each under **Details**. **Railbed doesn't email it.** A customer email only fills in the payment page; you still send the link yourself. To have Railbed email it with a PDF, reminders and receipts, choose **Duplicate** on its page and send the new invoice from the builder ([below](#cancel-duplicate-or-replace-a-request)). A customer's name or email doesn't restrict who can pay, so share the link only with people who should see the request. ## Pay another wallet It pays the wallet chosen when it was made: your payout wallet, or another one an owner saved under [Settings → Payout wallet → Other wallets](https://railbed.com/docs/user-guide/wallet-and-settlement.md#other-payout-wallets). Through the API, it names that wallet with `payout_wallet_id`. **Edit** can't change it; **Duplicate** copies it. When the customer starts paying, the payment keeps that wallet, so removing the wallet later doesn't change where their money goes. One that pays another wallet is paid by card only, because crypto payments go to your payout wallet. While an open one that nobody has started paying uses a wallet, that wallet can't be removed from Settings. If you change your main payout wallet while an unpaid one still pays the old wallet, its page says so and offers **Replace link**: the old link stops working, and a new one for the same amount and details pays your current wallet. Send the customer the new link. One that pays another saved wallet isn't affected by the change, so it never offers this. ## Share the link or QR code The **Invoice** card on its page holds its link. Copy the link into a message or email, or use **Copy link** on its row in the **Invoices** list. Use its QR code for a printed invoice or for a customer to scan from another screen. The QR code opens the same payment page; it is not a crypto transfer address. Here is a message you can adapt: Example: Example message to a customer ```text Hi Alex, Your design consultation is ready to book. The total is $49.00 USD (reference INV-0042). Pay using the Railbed link included in this message. The link is available for 7 days. Thank you, Northstar Studio ``` Paste your actual saved link into the message before sending it. Recheck the mode: a Test invoice cannot collect real money. While a Live one can be paid, its card says **Buyers pay real money here. To try the buyer’s steps without paying, switch to Test mode.** Until your business's first Live sale, its page in Live also offers **Try it without paying**. It opens a Test copy of the same request in a new tab, as your team, so you can follow the customer's steps to a simulated payment. The copy lasts a day, opening it again reuses it, and the Live invoice doesn't change. ## Share progress with someone else Use the separate **Tracking link** for an accountant or collaborator who needs to see whether the request has been paid. **Visual example: A status-only tracking page.** The tracking page shows a $49 Design consultation for Alex Morgan, reference INV-0042, In progress. It omits the email, note, wallet, transactions and a way to pay. *Illustrative example · share progress without sharing payment details.* The tracking page shows the amount, status, progress, reference and billed-to name. It omits the customer's email, your note, deposit and wallet details, transaction links and a way to pay. Anyone with the tracking link can see that limited information; treat it as a shareable link, not a login-protected report. ## Read the result In the **Invoices** list it reads **Open** with the date it's open until, then **Paid**, **Expired** or **Canceled**. Open it to see its status, details and timeline, including the addresses and answers the customer gave. Its page uses the payment statuses: | Status | What it means | |---|---| | Open | Waiting for the customer | | In progress | The customer went to a card provider. Until money arrives, the page says **No money has reached your wallet for this payment yet. If the payer finishes at Stripe, it updates here by itself.** | | Paid | Paid in full; the customer's link now shows their receipt | | Needs your decision | Money arrived but didn't pass a check, or less than the full amount arrived. The customer's link tells them their payment is being checked, or that less than the full amount arrived. See [held payments](https://railbed.com/docs/user-guide/held-payments.md) | | Declined | The card provider declined the payment | | Expired | Its time ran out before it was paid | | Canceled | You canceled it | In **Payments**, a card payment whose customer went to a provider half an hour ago with no money back says where and when, such as **Went to Stripe 3 hours ago · no payment yet**. Always read the status before delivering an order. [Payment statuses](https://railbed.com/docs/user-guide/payments.md#understand-each-status) explains the next action for each one. ## Cancel, duplicate or replace a request Owners and managers can edit, cancel, replace and duplicate it. **Cancel invoice** is on the **Invoice** card while it can still be paid and the customer hasn't gone to a card provider. After that hand-off, it stays open for the payment to arrive or expire. Canceling stops the link and shows the tracking link as canceled; it does not reverse a card payment or refund money. Until the customer starts paying, **Edit** changes the amount and currency, what it's for, the reference, the customer's details and addresses, the note, the expiry, the card providers and where the customer goes after paying; the same link keeps working. To bill again, or to bill line by line, choose **Duplicate**: the [invoice builder](https://railbed.com/docs/user-guide/invoices.md) opens with its amount as one line, its customer and its settings. Duplicate leaves out the reference, the phone and the delivery address, and once the original payment has started, the saved email and billing address too, so review the details before you create it. Cancel the old one if that action is still available. ## Send the buyer to your thank-you page Its page shows the address it sends the customer to under **After payment**, and **Edit** changes it until the customer starts paying. The rules are the same as for a [built invoice](https://railbed.com/docs/user-guide/invoices.md#send-the-customer-to-your-thank-you-page). The original Railbed tab follows this address after payment is confirmed; if the customer closes the tab, the redirect can't happen. Leaving it empty shows Railbed's on-screen receipt; it doesn't send a receipt email. --- # 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. Source: https://railbed.com/docs/user-guide/checkout-pages/ · Updated: 2026-11-18 · Railbed user guide ## One page, many customers A checkout page is a reusable product page hosted by Railbed. Unlike an [invoice](https://railbed.com/docs/user-guide/invoices.md), 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. **Visual example: A reusable checkout page.** A checkout shows Northstar Studio, Design consultation, $49.00 USD and an email field. Continue to pay leads to provider selection; card details are entered on the provider's page. *Illustrative example · your product on the left, buyer details on the right.* ## Build your checkout 1. Check the dashboard mode, then choose **Create → Checkout page**. 2. 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. 3. 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](https://railbed.com/docs/user-guide/branding-and-settings.md#checkout-appearance)). 4. 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. 5. In the same card, choose the **Provider choice**: **Smart Routing** (the default), **Buyers choose** or **One provider**. [How buyers reach a provider](#choose-how-buyers-reach-a-provider) explains each. 6. If you turned on [crypto payments](https://railbed.com/docs/user-guide/crypto-payments.md) 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. 7. Under **More options**, add a success URL if you have a thank-you page ([below](#use-a-success-url)). 8. In the **Ask buyers for** card, choose what buyers fill in besides their email ([Ask buyers for their details](#ask-buyers-for-their-details)). 9. 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](https://railbed.com/docs/user-guide/buyer-experience.md#how-smart-routing-chooses-providers) 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](https://railbed.com/docs/user-guide/payments.md#follow-the-timeline)). 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](https://railbed.com/docs/user-guide/buyer-experience.md#apple-pay-and-google-pay), 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](https://railbed.com/docs/user-guide/buyer-experience.md#coming-back)). 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](https://railbed.com/docs/user-guide/integrations.md)). Invoices have their own **Card providers** setting, which starts on Buyers choose ([details](https://railbed.com/docs/user-guide/invoices.md#build-an-invoice)), 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: Example: Example checkout address — use your saved URL ```text https://pay.railbed.io/c/your-checkout-slug ``` The 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](https://railbed.com/docs/user-guide/widgets-and-buttons.md) 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: Example: Send a confirmed buyer to your thank\-you page ```text 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](https://railbed.com/docs/guides/fulfilment.md). ## 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. --- # Offer plans with a pricing table > Present up to four packages side by side, highlight one recommendation, and let buyers choose the right one. Source: https://railbed.com/docs/user-guide/pricing-tables/ · Updated: 2026-11-18 · Railbed user guide ## What a pricing table does A pricing table is a reusable checkout with multiple plans. It works for service packages, access passes, resource bundles or other choices with a fixed price. A buyer chooses a plan, enters their details, and continues to a card provider. **Visual example: Compare three one-time plans.** Starter costs $19, Studio $49 and Team $99. Studio is highlighted as recommended. Each purchase is a one-time payment; nothing renews automatically. *Illustrative example · Studio is the recommended plan.* > [!IMPORTANT] > Every purchase is one payment. Pricing tables do not create subscriptions or automatic renewals. Labels such as / mo and / yr describe what you sell; they do not schedule another card charge. ## Create the table 1. Choose the correct mode, then **Create → Pricing table**. 2. In the **Table** card, set the **Title**, an optional **Description** and the **Currency**. All plans use that currency. 3. The **Plans** card starts with Starter, Pro and Team, with Pro recommended. Rename them and enter your own prices, or remove one; **Add a plan** adds another, up to four. 4. For each plan, fill **Name**, optional **Description**, **Price**, optional **Label** (such as `/ session`) and **Features**, one per line, up to eight. 5. Turn on **Recommended plan** for at most one plan. It appears as the highlighted card. 6. Arrange plans with their move up and move down controls, and check the preview. 7. Set the look in the **Appearance** card, as on a [checkout page](https://railbed.com/docs/user-guide/checkout-pages.md#build-your-checkout). 8. Optionally change the **Provider choice** in the **Checkout** card. It works as it does on [checkout pages](https://railbed.com/docs/user-guide/checkout-pages.md#choose-how-buyers-reach-a-provider); with One provider, the editor compares every plan price with the provider's minimum when both are in the same currency, and asks you to check them when they aren't. The same card holds **Accept crypto payments** (when crypto is on in Settings) and the success URL under **More options**. 9. Optionally choose what buyers fill in under **Ask buyers for** ([details](https://railbed.com/docs/user-guide/checkout-pages.md#ask-buyers-for-their-details)). 10. Choose **Create pricing table**. The saved table opens on its **Share** tab. A plan name can contain up to 40 characters, its description up to 140, and the price label up to 16. Each plan needs its own name: payments, orders and webhooks carry only the name, so two plans called Pro couldn't be told apart. Every price must be one a card provider can take (the smallest is about 2.00 USD), up to 100,000.00. Keep feature descriptions short enough for buyers to compare at a glance. ## Offer two price options Turn on **Price switch** in the **Plans** card to give every plan two prices that buyers flip between. Name the **First option** and **Second option** (up to 20 characters each), then fill in both prices for each plan. For example, a studio could sell a **Single session** or a **Three-session pack**. Switching the option changes the displayed prices across the table. Monthly and Yearly are also possible labels when the purchase buys that period of access, but Railbed will not charge again when it ends. Make both the price and what it includes explicit: | Plan | Single session | Three-session pack | |---|---|---| | Consultation | $49 | $129 | | Extended session | $99 | $269 | These are illustrative prices. You decide what you deliver and any access duration outside Railbed. ## Share or embed it Open the saved table's **Share** tab. Share its hosted URL or QR code, or add the table to your website from **Add it to your site**: choose **On your page** to place the plans in your page, or **In a pop-up** for a button that opens them. [On your page or in a pop-up](https://railbed.com/docs/user-guide/widgets-and-buttons.md#page-or-pop-up) compares the two. Example: Place your pricing table on a website ```html ``` Replace the example slug with the one copied from your saved table. No API key goes in this snippet. [Embed instructions](https://railbed.com/docs/user-guide/widgets-and-buttons.md) cover testing and site-builder behavior. ## See which plan was purchased Open **Payments** and choose the payment. Its title and its **Plan** detail name the plan and, when used, the price option, such as Pro · Yearly. The same detail reaches your orders, webhooks and connected integrations, so fulfil the package actually purchased. ## Change your plans later Open the table from **Checkouts**, choose the **Edit** tab, change descriptions, features, prices, order or the recommended plan, and choose **Save changes**. The currency locks once a payment reaches a card provider, or is paid or needs your decision. Create a new table for another currency if the field is locked. Edits affect future purchases. Existing payment records keep the details captured when they were created. **Turn off pricing table** stops sales for a while and **Turn on** brings it back with the same link and embeds. **Delete pricing table** stops its link and embeds for good while keeping past payments ([details](https://railbed.com/docs/user-guide/checkout-pages.md#stop-accepting-new-buyers)). --- # Add Railbed to your website > Keep customers on your site while they choose what to buy. Copy a small HTML snippet; Railbed handles the checkout. Source: https://railbed.com/docs/user-guide/widgets-and-buttons/ · Updated: 2026-11-18 · Railbed user guide ## Choose the right format A **buy button** opens a checkout over your website when clicked. A **payment widget** places a compact checkout directly inside your page. A **pricing table** can also sit inside your page with its plans visible. A widget or a table can open from a buy button instead; see [On your page or in a pop-up](#page-or-pop-up). These use checkouts created in the dashboard. Your website does not need an API key, a server integration or card fields. | Format | Start with | What buyers see on your site | |---|---|---| | Buy button | Any checkout | A button; clicking opens the checkout in a pop-up over your page | | Payment widget | A payment widget checkout | The compact checkout itself, inline | | Pricing table | A pricing table checkout | Plans and the price switch, if configured | ## Copy the code from Railbed 1. Open **Checkouts** and select your saved checkout. It opens on its **Share** tab. 2. Find **Add it to your site**. A checkout page gets a buy button. For a payment widget or pricing table, choose **On your page** or **In a pop-up** under **How it shows on your site**. 3. For a button, optionally set its **Button text** (Buy now by default, or See plans for a pricing table) and **Shape** (**Pill** or **Rounded**). The preview shows the button as your page will. 4. Copy the generated code and paste it into your site's HTML or custom-code block. You can paste a button as many times as you like. 5. Preview the published page. Some site builders do not run custom scripts inside their editing canvas. Start with a Test checkout and try it with [Test on your site](#test-on-your-site). When ready, copy code from a separate Live checkout and replace the Test snippet. Under the code, **For developers** has the extras a developer can add: linking each payment to a user of your site, filling in the buyer's email, and matching your site's accent color, fonts and light or dark mode. The [embedded checkout guide](https://railbed.com/docs/guides/embedded-checkout.md) has recipes for WordPress, Webflow, Next.js and Vue, including React and Vue components. ## On your page or in a pop-up A payment widget or pricing table sits on your page unless you choose a pop-up, since that's what they're made for. **Add it to your site** shows both, with the trade-offs: | | On your page (the default) | In a pop-up | |---|---|---| | What buyers see | The checkout or the plans, right in your page | A button that opens the checkout over your page | | Best for | A page that sells one thing, or a pricing page | Pages with other content, several buy buttons or little room | | Keep in mind | It takes room: a widget up to 440 pixels wide, a table the width it's given | Buyers click once before they see the price or the plans | Either way, card details go in on the provider's page in a new tab, and a confirmed payment sends the buyer to your success URL if you set one. Nothing about the choice is saved with the checkout, so to change it, paste the other code. ## Add a buy button Include the script once per page, then put the button where you want it: Example: A button that opens your checkout ```html Book a consultation ``` The link inside the element is what shows if your site strips or blocks the script, so buyers can still reach the checkout. The script draws the button over it once it runs. The code you copy from the Share tab includes it. | Attribute | What it does | |---|---| | checkout | Required. The slug from your saved checkout URL | | label | Optional. Your button text; defaults to Buy now, or See plans for a pricing table | | shape | Optional. Use pill or rounded; the default is pill | The button takes the checkout's accent color: the one set for the checkout's look, or else your business's brand color from [Settings](https://railbed.com/docs/user-guide/branding-and-settings.md). The button label is separate from the payment button text inside the checkout. ## Add an inline checkout For a payment widget or pricing table, use this element: Example: A checkout embedded in your page ```html Buy now ``` The embedded checkout adjusts its height to its content as the buyer moves through it, and takes the look you set for the checkout. Give it enough width for the checkout to be readable; test the surrounding layout on a phone too. ## Match your site's look The checkout uses the accent color and fonts set for it in the dashboard, inside Railbed's own design. A developer can also match it to your site with a few lines of CSS, which win over the dashboard's settings on that site: Example: Your site's accent color and font ```html ``` Text stays readable whatever accent is set. Every variable is listed in [Match your site](https://railbed.com/docs/guides/embedded-checkout.md#css-variables). ## What happens when a buyer pays The buyer starts in your embedded checkout. The card provider opens in a new tab because card entry happens on the provider's own page. If the browser blocks the new tab, the provider opens in the same tab instead. If your site doesn't let the checkout open the provider at all, the buyer is offered the checkout in a new tab, and the Share tab tells you ([troubleshooting](#troubleshoot-an-embed)). If the buyer comes back to your page before their payment arrives, the checkout asks whether they finished paying and offers **Choose another way to pay** first ([what the buyer sees](https://railbed.com/docs/user-guide/buyer-experience.md#coming-back)). After confirmation, the buyer sees a receipt in the checkout, and then your page goes to the success URL you configured, if there is one. If a buyer tries to close a pop-up while their payment is open in the other tab, it asks **Close checkout?** with **Keep paying** and **Close**. On phones, a pop-up fills the screen. Returning to your website alone does not confirm payment: check Payments or use your connected store's verified order status. ## Test on your site A Test checkout takes payments only from your team, on your website too: anyone else sees that it's a test and can't pay. To try it where you pasted the code: 1. In Test mode, open the checkout's **Share** tab. Owners, managers and developers see this section. 2. Under **Test on your site**, enter the address of your page, then choose **Get test link**. 3. Open the link. For one hour, the tab it opens in can try Test payments on your page. Anyone with the link can try Test payments there until it runs out, so share it only with your team. Test payments never take real money. Without the link, a Test checkout on your site shows **This checkout isn’t live yet** and “[your business] is still setting it up, so nothing can be paid here yet.”, to your team too. If the hour runs out while the checkout is open, the next Pay shows the same card; get a new test link to carry on. ## Troubleshoot an embed - **Nothing appears:** confirm your site builder allows custom HTML and JavaScript, includes the script, and keeps the custom element tags. Check the published page as well as the editor. - **Blocked by your site's security settings:** if your site sets a Content Security Policy, allow `https://pay.railbed.io` in its `script-src`, `frame-src` and `connect-src` rules. When a site's policy blocks an embed, the checkout's Share tab names the site and when it last happened. - **Buyers can't reach the card provider:** some sites stop embedded content from opening new tabs. Buyers then see **This site can’t open the card provider from here** with a link to open the checkout in a new tab, and the Share tab names the site. Link to the checkout's own page there instead, or ask whoever runs the site to let frames from `pay.railbed.io` open tabs. - **Checkout unavailable:** check that the slug matches an existing checkout and that it has not been deleted or become unavailable. - **Still in Test mode:** copy the code from the Live checkout. Flipping your dashboard mode does not change the slug in your website. A Test checkout shows your buyers **This checkout isn’t live yet** and can't be paid; to try it yourself, use [Test on your site](#test-on-your-site). - **Provider opens elsewhere:** that is expected. Provider card entry is not embedded inside your website. Only Railbed checkout and payment pages can be framed. Do not try to embed the dashboard or a tracking page. If a custom integration needs more control, use the [embedded checkout guide](https://railbed.com/docs/guides/embedded-checkout.md). --- # What your customer sees > Understand the card checkout, provider choice and return journey so you can confidently guide a customer through payment. Source: https://railbed.com/docs/user-guide/buyer-experience/ · Updated: 2026-11-21 · Railbed user guide ## From your link to payment **Visual example: Explore a payment from start to finish.** Send an invoice: set the amount, then share its link or QR code, or email it. Buyer pays: the buyer opens a licensed provider in a new tab and pays by card. Payment confirmed: check the payment status and the reported settlement in your dashboard. *Illustrative Test payment. Select a step to see what happens.* 1. Your customer opens the invoice, checkout page or embed. They see your business, product and price. A pricing table first asks them to choose a plan. 2. They give an email address, answer any [details you ask for](https://railbed.com/docs/user-guide/checkout-pages.md#ask-buyers-for-their-details), and choose **Continue to pay**. An invoice can prefill the email you entered for its customer. 3. What happens next follows the provider choice of the checkout, store or invoice. **Smart Routing** opens the best provider for that buyer straight away, and **One provider** opens the provider you picked. **Buyers choose** shows every card provider that can take them in one list, with a recommended **Best match**; under it the list may say why (**Picked for your country** or **Lowest minimum payment**). When Apple Pay or Google Pay is on the list and the buyer's browser can pay with it, it comes right after Best match: Apple Pay on an iPhone, iPad or Mac set up for it, Google Pay on Android and in Chrome. 4. The provider opens in a new tab, which shows **Opening secure payment** until the provider's page loads. If it takes more than a few seconds, the tab offers a **Continue to** link for that provider. The buyer enters card details and completes any checks on the provider's page. 5. The original checkout tab waits for confirmation. When the payment is marked paid, it shows the result or follows your success URL. When the browser can't open a tab (a blocked pop-up, or the built-in browser of an app such as Instagram), the provider opens in the same tab. Coming back to the checkout then asks whether they finished, as [below](#coming-back). **Visual example: From a card payment to your wallet.** Smart Routing checks country, currency, amount and availability to show eligible card providers. The buyer pays with a provider, and settlement goes to the merchant's wallet as USDC on Polygon. *Eligibility depends on the buyer. Identity checks are decided by the provider.* ## How Smart Routing chooses providers Smart Routing looks at the buyer's country, the checkout currency, the amount, each provider's minimum and whether the provider is working today. It keeps the card providers that can take the buyer and ranks them. You don't need a rule for each country, though you can [put the providers in your own order](#provider-order). [Provider choice](https://railbed.com/docs/user-guide/checkout-pages.md#choose-how-buyers-reach-a-provider) sets how each checkout uses the ranking. The list can differ between buyers and change over time. Test mode uses a fixed example list, so it is not a live availability check. A low amount may have no provider that can take it, even though Railbed accepted the price. ### Choose which card providers buyers see Under **Integrations** → **Card providers**, each provider has an **Offer to buyers** switch. Turn one off and your buyers are never offered it, in Test or Live, on checkout pages, invoices, your store and anything your developer builds; it reads **Turned off by you**. Smart Routing picks from the rest. Only an owner can change the switches, and each change appears in your account's activity. At least one card provider stays on. Interac e-Transfer (a bank payment) and Venmo don't count toward that, and nor do the providers that [pay on another network](#apple-pay-and-google-pay) unless your payout wallet can take them. If checkout pages, unpaid invoices, your Shopify store or WooCommerce are set to **One provider** with the provider you're turning off, a dialog lists them. Choose where they send buyers instead (Smart Routing or another provider you offer) and **Move and turn off**, or keep the provider on and nothing changes. Providers you turn off no longer count toward the smallest payment you can take. If the ones left all start at $5, a $3 price is refused with words saying so, and Card providers notes that card payments start at $5.00 while you have them turned off. A checkout set to **One provider** with a provider you turned off sends buyers to Smart Routing's pick when **If it can't take a buyer, use Smart Routing instead** is on, and stops them when it's off. Before a switch turns a provider off, Railbed runs your prices (your checkouts' prices and the amounts you were paid in the last 30 days) against the providers that would be left. If some buyers would have no card provider for one of them, it asks first, for example **Buyers outside the US would have no card provider for your 4.99 USD price.** Keep the provider on, or turn it off anyway; you can turn it back on at any time. Turning a provider on never asks. Under the list, **Buyers who couldn't pay** appears when a Live payment couldn't start in the last 7 days. Each line says why in a sentence, how many times it happened, when it last happened and the latest amount; when a provider you turned off could have taken those buyers, it names the provider. A buyer who tried more than once is counted each time, and nothing was charged. The page also shows each provider's status and minimum: | Status | What it means | |---|---| | **Available** | Offered to buyers it can take | | **Unstable** or **Unavailable** | The provider itself is having trouble; it comes back on its own | | **Turned off by you** | Your own switch; it stays off until you turn it on | | **Turned off by Railbed** | Railbed's team paused it for now | | **Not working, paused by Railbed** | Railbed's own checks found its payments aren't going through; it comes back once they pass | | **Not offered** | Listed but never offered, or not offered with your payout wallet; its line says why | ### Put card providers in your order 1. Under **Integrations** → **Card providers**, choose **Change order**. 2. Drag a provider by its handle, or use its arrows. With a keyboard, focus the handle and press the up and down arrow keys. 3. Choose **Save order**. Test and Live mode each keep their own order, so save it in each mode you sell in. Only an owner can change it, and each change appears in your account's activity. Each buyer still sees only the providers that can take them, now in your order, and **Best match** is the first of them, so a checkout on Smart Routing sends buyers straight to it. A buyer who comes back without paying still sees the providers they already tried last, and a checkout set to **One provider** still sends buyers to that provider first. **Reset to Smart Routing** goes back to ranking the providers for each buyer's country. > [!IMPORTANT] > Best match is a recommendation, not an approval guarantee. A card can still be declined on the provider's page, where the provider also shows its fees and conversion terms and decides which identity checks to require. Railbed can't promise that a buyer will never be asked for ID. ### Apple Pay, Google Pay and other networks Buyers can pay with Apple Pay or Google Pay through card providers such as Stripe and Topper, which pay on Polygon like any card. A few providers pay on another network instead, to the same wallet address: | Provider | Pays | Prices it takes | |---|---|---| | Apple Pay (as a provider of its own) | USDC on Ethereum | USD, EUR or GBP | | Alipay and WeChat Pay | USDT on Ethereum | USD, EUR or GBP; first for buyers in mainland China, Hong Kong and Macau | | Rampnow | ETH on Ethereum | USD or GBP | | [Venmo](#venmo) | PayPal USD on Ethereum | US buyers, at the order's dollar value | | Cash App | USDT on BNB Chain | US buyers | Railbed values what arrives in dollars, so a payment never needs your decision because of the coin or the network it came on. These providers are offered only where they work for you: - **An ordinary wallet.** In Live, they're offered only with an ordinary self-custody payout wallet, such as MetaMask, Coinbase Wallet or Rabby, where the same address receives on every network, so there's nothing to set up. A smart contract wallet such as a Safe can't take them, because it may not exist on those networks; Card providers then lists them as **Not offered** and says what turns them on. - **Larger orders on Ethereum.** Forwarding money from Ethereum costs more, and the cost comes out of your share, so the Ethereum providers take an order only where that cost stays at most 3% of it and the amount clears the network's minimum. That line moves with network costs (about $75 for Apple Pay when forwarding costs $2.25, a few dollars when it costs cents), so Card providers shows their minimum as "From about". With **One provider**, Apple Pay, Alipay, WeChat Pay, Rampnow or Venmo can be the provider only with **If it can't take a buyer, use Smart Routing instead** on, because their minimum changes from day to day. In Test mode, Apple Pay, Alipay and WeChat Pay are on the list from about $75 and Rampnow from $6, with any wallet. Google Pay as a provider of its own is paused for now. Buyers still pay with Google Pay through card providers such as Stripe. ### Interac e-Transfer Buyers in Canada paying in Canadian dollars can pay by Interac e-Transfer from their bank, through Paytrie, on orders of 100 CAD or more. Smart Routing lists it after Banxa, Topper and Coinbase, the card providers it prefers in Canada. ### Venmo Buyers in the US can pay from the Venmo app. No new tab opens: the checkout itself shows what to send and where. - The buyer sends PayPal USD (PYUSD), the dollar coin in Venmo's Crypto tab, where 1 PYUSD is worth $1. An order priced in another currency is shown at its US dollar value, fixed when the buyer starts paying. The checkout shows the amount, the address with a copy button and a QR code, and the steps in Venmo, whether the buyer already holds PYUSD or buys it first. - Since the buyer sends the money themselves, Venmo is offered only when Railbed can tell the buyer is in the US and while at least 15 minutes are left on the payment. A buyer already shown the Venmo details keeps them until the payment closes. - Venmo pays on Ethereum, to the same wallet address, from about $3. In Live it needs an ordinary self-custody payout wallet, as Apple Pay does. - The checkout shows the result as soon as the payment arrives, like any other provider. Venmo appears under **Integrations** → **Card providers** like the other providers, so you can turn it off or put it in your order. ## Why there are two tabs The Railbed tab stays open so it can report the verified result and send the customer back to your store. The provider's own final page may lead somewhere else that your success URL doesn't control. Tell customers to keep the original checkout tab open and return to it after paying. If their browser blocks new tabs, payment continues in the same tab, and they may need to go back to the Railbed page to see the result. ## If a card is declined A Live decline is shown by the card provider. Railbed doesn't receive a direct decline signal, so your dashboard may still show **Open** or **In progress**. The buyer can use **Choose another way to pay** to go back to the full provider list before the payment expires, including on checkouts that sent them straight to a provider. Don't assume an in-progress payment means the card was charged. If the buyer believes they were charged, open the payment and use **Check now** ([how](https://railbed.com/docs/user-guide/payments.md#check-now)) before asking them to pay again. ## If the buyer comes back without paying When the buyer comes back to the Railbed tab and Railbed hasn't seen their payment yet, the page asks **Did you finish paying with Stripe?** (naming their provider) and goes on: "If you did, stay here. This page updates by itself, usually within a few minutes. If Stripe's page didn't open, didn't take your card or asked for something you couldn't give, choose another way to pay." **Choose another way to pay** comes first; **Reopen Stripe** goes back to the provider. The provider list then shows the providers they already tried last, marked **You tried this**, and **Best match** goes to the first one they haven't tried. A checkout on Smart Routing sends them straight to a provider they haven't tried, when one can take them. Every attempt at the same order counts, so starting the checkout again doesn't send them back to the same provider. A checkout set to **One provider** shows the list once its buyer has tried that provider, with it last. A buyer who opens the page again later, after a reload or on another device, sees **Waiting for your payment**: "You started paying with Stripe. If you finished there, this page updates by itself, usually within a few minutes. If you didn't, choose a way to pay again." **Choose a way to pay** opens the list. If the payment expires after the buyer reached a provider, the page tells them not to pay twice: "If you finished paying at Stripe, don't pay again. A payment still on its way counts, and [your business] will see it." Your support email follows when you've set one. Money that still arrives settles the expired payment. Embedded checkouts and buy buttons ask the same questions inside their card. ## If the page says Being reviewed or Underpaid Money arrived but didn't pass every check needed to confirm it. The buyer's page reads **Your payment is being reviewed**, or **Your payment is underpaid** when less than the full amount arrived, and says you will contact them about what happens next. In your dashboard the payment reads **Needs your decision** (with **Underpaid** beside it), or **Not received** when its money may have gone elsewhere. Ask the buyer to wait while you [check it](https://railbed.com/docs/user-guide/held-payments.md). It is not an instruction to top up the original payment. ## Thank-you pages and receipts A success URL runs from the original checkout tab after the payment is confirmed. If that tab is closed, Railbed can't redirect it. Closing the page doesn't cancel money already sent. Without a success URL, Railbed shows an on-screen receipt. Railbed doesn't email buyers a receipt for checkout pages; an [invoice](https://railbed.com/docs/user-guide/invoices.md#how-your-customer-can-pay) can email its customer one for each payment. If your store sends order emails, those come from the store or your own integration. For manual delivery, check for **Paid** in your dashboard. For automatic delivery, connect [signed webhooks or authenticated payment checks](https://railbed.com/docs/guides/fulfilment.md). Never use the buyer's screenshot, browser redirect or thank-you page as the only payment proof. ## Next step - [Find and understand a payment](https://railbed.com/docs/user-guide/payments.md): Read statuses, the timeline and what arrived. - [Payments that need your decision](https://railbed.com/docs/user-guide/held-payments.md): What to do when money arrives but doesn't pass a check. --- # Accept crypto payments > Let buyers pay from their own wallet in USDC, USDT, Bitcoin and other coins, beside card. It's off until you turn it on, and the money goes to your own wallets. Source: https://railbed.com/docs/user-guide/crypto-payments/ · Updated: 2026-11-18 · Railbed user guide ## How it works Card stays the main way to pay. When you turn crypto payments on, your checkout pages, invoices and store checkouts show a **Card | Crypto wallet** switch, with Card selected. A buyer who picks **Crypto wallet**: 1. Enters their email and chooses a coin and network. 2. Sends the exact amount to a one-time address, shown with a QR code and a copy button, and a link to follow it on the network's block explorer. **Send by** shows when the checkout closes. 3. Waits on the page, which updates when the money arrives. The payment then settles to your wallet like a card payment. The QR code asks for the chosen coin, network and exact amount in wallets that support payment requests. On TRON, and for USDT on TON, it holds the address only, and the page asks the buyer to enter the amount. Buyers can send: | Coin | Networks | |---|---| | USDC | Polygon, Base, Arbitrum, Optimism, BNB Chain, Ethereum, Solana | | USDT | Polygon, Base, Arbitrum, Optimism, BNB Chain, Ethereum, Solana, TRON, TON | | BTC, LTC, DOGE, BCH, ZEC, XMR | Bitcoin, Litecoin, Dogecoin, Bitcoin Cash, Zcash, Monero | | SOL, TRX, TON | Solana, TRON, TON | USDC and USDT count as one US dollar each. Any other coin is asked for at its price in dollars: the page shows the exact amount of that coin for the order and holds it for 30 minutes. After that the buyer chooses **Get a new amount** before sending. When the coin arrives it's valued at the network's price then, and every figure in your dashboard is in dollars. An order only offers the coins and networks it can use. Each has a minimum, and those that cost more to forward (such as Ethereum, Base and USDT on TRON) only appear on larger orders, so the network cost never takes much of your payment. When Bitcoin, TRON, Solana or another network beyond the first six is on offer, buyers pick the network first, then its coin. ## Before you turn it on On Polygon, Base, Arbitrum, Optimism, BNB Chain and Ethereum, crypto payments arrive at your payout wallet on whichever network the buyer used. Your payout wallet must be a **self-custody wallet** (one where you hold the recovery phrase, such as MetaMask, Rabby, Trust Wallet or a hardware wallet). The same address then works on all six. A smart contract wallet, such as a Safe, can't take crypto payments, because it may not exist on the other networks. Bitcoin, Litecoin, Dogecoin, Bitcoin Cash, Zcash, Monero, TRON, Solana and TON each have their own kind of address. Save one wallet for each network you want under **Settings → Payout wallet → Wallets on other networks** ([how](https://railbed.com/docs/user-guide/wallet-and-settlement.md#other-payout-wallets)). Payments in that network's coins go straight to the wallet you saved for it, and a network without a saved wallet isn't offered to buyers. > [!NOTE] > Railbed is turning these networks on one at a time, and none is offered while your crypto fee is 0%. Settings lists only the networks your buyers can pay on today, plus any network where you already saved a wallet. Crypto payments on any network still need your main payout wallet, and an [invoice that pays one of your other wallets](https://railbed.com/docs/user-guide/invoices.md#pay-another-wallet) takes card payments only. > [!WARNING] > Don't turn crypto payments on if your payout wallet is an exchange deposit address. An exchange deposit address usually works on one network only, and money sent to it on a network the exchange doesn't support can be lost. ## Turn it on 1. Open **Settings** and find **Crypto payments**, under **Getting paid**. Only an owner sees it, and your payout wallet must be saved first. 2. Turn on **Accept crypto payments**. 3. In **Turn on crypto payments?**, check the address, tick the box confirming it's a self-custody wallet (not an exchange deposit address) that works on all six networks, and choose **Turn on crypto payments**. Turning crypto payments on or off needs a sign-in from the last five minutes; if yours is older, Railbed asks you to sign in again first. Settings then shows **On**, and your checkout pages, invoices and store checkouts offer **Crypto wallet**. If you change your payout wallet later, you confirm the new one the same way. The [card providers that pay on another network](https://railbed.com/docs/user-guide/buyer-experience.md#apple-pay-and-google-pay) (Apple Pay, Alipay, WeChat Pay, Rampnow and Venmo on Ethereum, Cash App on BNB Chain) don't need this confirmation: every ordinary payout wallet gets them. To keep one checkout card only, open it and turn off its own **Accept crypto payments**. ## Fees The **Crypto payments** card in Settings shows what comes out of each crypto payment: a 1% network fee, the cost of forwarding the money to your wallet, and Railbed's crypto fee when yours is above 0%. The crypto fee is set apart from the card fee and is usually lower. It's all taken from what arrives, as with card payments. ## Short and late payments The buyer must send the full amount. A payment counts as paid when what arrives is worth at least 85% of the order: USDC or USDT at face value, any other coin at the network's price. That leaves room for an exchange's withdrawal fee and for the price to move while the buyer sends. Less reads **Needs your decision** with **Underpaid** beside it, and you decide what to do, as for any [payment that needs your decision](https://railbed.com/docs/user-guide/held-payments.md). A second, separate transfer isn't added to the first. Money that arrives after the checkout closed still settles, as with card. A transfer counts once its network confirms it; on Bitcoin, Bitcoin Cash, Zcash and Monero that can take up to an hour, and the buyer's page says so. ## Test mode In Test mode the address is an example in the network's own form: never send real funds to it. Coins other than USDC and USDT are priced at fixed example prices. Use **Simulate payment** or **Simulate underpayment** on the page to see what your buyers and your dashboard show. They appear only on Test pages your team opened from the dashboard ([Test and Live mode](https://railbed.com/docs/user-guide/test-and-live.md)). ## In the dashboard and integrations A crypto payment reads like **Crypto · USDC on Base** or **Crypto · Bitcoin** in Payments, Orders and alerts, with links to that network's block explorer. The payment's drawer lists the **Crypto addresses shown** to the buyer. Webhooks and the API say `method: crypto` and name the `network` (`base`, `bitcoin`, `tron`, …) ([payment fields](https://railbed.com/docs/api/payments.md), [webhook fields](https://railbed.com/docs/webhooks/events.md)). Crypto addresses can't be created through the API yet: an API checkout session offers crypto on its hosted payment page. ## Next step - [Understand your wallet and settlement](https://railbed.com/docs/user-guide/wallet-and-settlement.md): Your payout wallet and the wallets on other networks. - [Move money to your bank](https://railbed.com/docs/user-guide/move-money-to-your-bank.md): Sell what arrived and withdraw it. --- # Manage orders and fulfilment > See what a customer bought, review their payment attempts, and keep track of what still needs to be delivered. Source: https://railbed.com/docs/user-guide/orders/ · Updated: 2026-11-18 · Railbed user guide ## An order brings the purchase together Open [Orders](https://app.railbed.io/orders) for the purchase itself: the items, customer, total, addresses, payment attempts and fulfilment. Use [Payments](https://railbed.com/docs/user-guide/payments.md) when you need the evidence for one particular attempt to pay. One order can have several payment attempts. A retry does not always mean a second purchase, and one customer can have many orders. Always match the order and payment before delivering. **Visual example: How customers, orders and payments relate.** Customer: Alex Morgan. Their history can include many orders. alex@example.com. Order #1001: Design consultation. One purchase, with its own total and fulfilment record. $49.00 USD. Payment attempts: One retry, one purchase. An order can be paid after an earlier attempt expires. Attempt 1: Expired · Attempt 2: Paid. Fulfil the order once; inspect individual attempts when reviewing payment evidence. *Illustrative records. A customer can have many orders, and an order can have several payment attempts.* Orders come from checkouts, [invoices](https://railbed.com/docs/user-guide/invoices.md), your connected store and the Checkout API. Stores and the API can send item details, shipping, tax, discounts and addresses. A checkout creates an order for its product or plan. A payment toward an invoice creates an order with the invoice's lines when it pays the whole invoice, or one line such as "Payment toward INV-0042" when it pays part of it. Missing details mean the source did not provide them; Railbed does not invent an address or a product. Everyone on your team can read orders. Owners and managers can mark them fulfilled and export them. ## Find the orders that need you 1. Check **Test** or **Live** mode. Orders, customers and payments are separate in each mode. 2. Choose a view at the top of **Orders**. To see one source only, choose it in **All sources**: **WooCommerce**, **Checkouts**, **Invoices** or **Checkout API**. 3. Search for an order number, a customer's name or email, a product or SKU, your reference, or an order or payment ID. **Clear filters** returns to the full list when nothing matches. 4. Open a row to review the order. **Show more** loads the next results. | View | What it includes | |---|---| | All | Every order that matches your source and search | | Not fulfilled | Paid orders waiting to be shipped or delivered | | Needs your decision | Orders whose payment arrived but didn't pass a check. Team members who can't accept payments see **Needs a decision** | | Awaiting payment | Orders whose payment is Open or In progress | | Ended unpaid | Orders that ended Declined, Expired or Canceled | The counts on **Not fulfilled** and **Needs your decision** stop at **100+**: a capped count, not exactly 100. The total beside the page title can read **10,000+** the same way. Filters stay in the page address, so refreshing or using Back keeps your view. Someone opening a link to an order still needs to sign in to the same business and mode. ## Read an order The order opens in a panel over the list, so you keep your place. Use **Previous order** and **Next order**, or **K** and **J** when the panel has focus and you aren't typing in a field. - **Customer:** their name, contact and what they have paid so far. Open it for their [customer page](https://railbed.com/docs/user-guide/customers.md). - **Items:** products, quantities, variants and SKUs, with the subtotal, discount, shipping and tax when the source sent them. The total is what the customer was charged, in the order's currency. - **Ship to** or **Bill to:** the address as supplied, with a button to copy it. Addresses are not checked against a postal service. - **Payment:** the card provider (or the coin and network for a crypto payment), **Received** and when it was paid. With more than one attempt, each is listed newest first with its own status. One failed or expired attempt does not undo another that is Paid. - **Timeline:** the order's and its payments' events in order. - **Answers:** what the buyer typed for the questions your checkout or invoice asked ([Ask buyers for their details](https://railbed.com/docs/user-guide/checkout-pages.md#ask-buyers-for-their-details)). - **Details:** the order ID to copy, the store's own order number and store name for a store order, and **Your reference** when one was sent. **Received** is the net amount that reached your wallet, in dollars, after fees. It is a different figure from the order total, and reads **Not reported yet** until it is reported. See [wallet and settlement](https://railbed.com/docs/user-guide/wallet-and-settlement.md). When Railbed support has corrected a detail of this order or its customer for you, the panel shows **Corrected by Railbed support** with **View original values**. A correction never changes the order's amounts or payment evidence; see [Customers](https://railbed.com/docs/user-guide/customers.md#corrections-made-by-railbed-support). ### Warnings at the top of an order | Warning | What to do | |---|---| | A payment didn't pass a check | Choose **Open payment** and follow [Payments that need your decision](https://railbed.com/docs/user-guide/held-payments.md). Don't fulfil until it is Paid | | Only part of the total was paid, or it was paid in another currency | Choose **Open payment**, then check with the buyer before you fulfil | | The buyer paid twice (or more) for this order | Check each payment under **Payment**. Deliver the order once, then agree any refund for the extra payment with the buyer | Marking an order fulfilled never refunds a payment. Railbed doesn't move money back to buyers. ## Payment and fulfilment are separate A payment status answers whether the order was paid. Fulfilment records whether you have delivered it. **Mark as fulfilled** cannot turn an unpaid order into a paid one and does not send money. | Fulfilment label | Meaning | |---|---| | No shipping | A paid order created without a shipping requirement, such as a service or digital product | | Not fulfilled | A paid order waiting to be shipped or delivered | | Fulfilled | You or the connected store recorded delivery or dispatch | An unpaid order shows no fulfilment label. **No shipping** is not proof that a digital item was delivered; your business or connected system still handles delivery. A fulfilment label alone is not proof of payment either. ## Mark an order fulfilled For an order managed in Railbed: 1. Open the order and confirm it reads **Paid**. Check the items, customer and delivery details. 2. Deliver the goods or service through your normal process. 3. Choose **Mark as fulfilled**. To correct the record later, choose **Mark as not fulfilled**. To mark several at once, tick their rows and choose **Mark as fulfilled** in the bar that appears. Shift-click ticks every row between two ticks, and **Escape** clears the selection. You can select up to 100 orders. Railbed checks each one: unpaid orders and orders whose fulfilment comes from a store are skipped, and the message says how many were marked and how many were left. > [!IMPORTANT] > A store order says **Fulfilment comes from the store**. Update it in that store; **Open in WooCommerce** (or your store's name) takes you to it. Railbed shows the state the store reports. If an order reads **Needs your decision** or **Not received**, choose **Open payment** and follow [Payments that need your decision](https://railbed.com/docs/user-guide/held-payments.md). Don't mark it fulfilled before its payment is Paid. ## Export orders Choose **Export CSV** to download the orders that match the current view, source and search. To export only some orders, tick them and choose **Export CSV** in the selection bar. The file has the order number, date, status, fulfilment, customer and contact, items and units, currency, subtotal, discount, shipping, tax and total, **Received (net, USD)**, source, store and store order, your reference, both addresses, the buyer's **Answers**, and the order and payment IDs. - An export holds up to 10,000 orders. When more match, the dashboard says **Export limited to 10,000 rows; narrow the filter** and the file ends with a row saying the same, so a cut-off file is never mistaken for a complete one. - Keep the currency with every amount; don't add USD, EUR and other currencies together. **Received (net, USD)** is a separate measure: what reached your wallet, in dollars, after fees, whatever coin it arrived in. - Exports contain customer details. Keep the file only where you mean to keep those details. Deleting a customer's data in Railbed does not reach a file you already downloaded. ## When something looks wrong | What you see | What to check | |---|---| | An order is missing | Confirm the mode, clear filters and search by its order or payment ID. An order from the other mode says to switch modes | | A customer tried again | Look under **Payment**; several attempts can belong to the same order | | An expired order later becomes Paid | A late payment can still settle and update the order. Read its current status before you send a new request | | Fulfilment can't be changed here | The order isn't paid yet, its fulfilment comes from a store, or your role can't change orders | | The timeline says **Canceled in** your store or **Refund recorded in** your store | The store reported it. The payment stays as it is, and Railbed didn't move any money; refund the buyer yourself if money arrived | | The store shows a different fulfilment state | Check the integration, then make the change in the store | | An address or item is missing | Check what the store, invoice or API sent when the order was created | - [Understand your customers](https://railbed.com/docs/user-guide/customers.md): See each customer's orders, contact details and private note. - [Find records across Railbed](https://railbed.com/docs/user-guide/search.md): Search by order number, email, payment ID or transaction. --- # Understand your customers > See a customer's order history, contact details and spending. Keep a private note and manage the personal data saved in Railbed. Source: https://railbed.com/docs/user-guide/customers/ · Updated: 2026-11-18 · Railbed user guide ## How customers appear [Customers](https://app.railbed.io/customers) brings together the purchases made with the same email address in the current mode. Railbed creates a customer when a checkout, invoice or store order provides an email, so you never enter customers by hand. Email matching ignores letter case, and **Test** and **Live** records are separate. Names, phone numbers, dates of birth and addresses appear when the checkout or connected store supplies them. A later order updates the details it brings; details it leaves out keep their earlier value. A customer first created when a buyer starts paying may hold only their email. Open the order to see any other details supplied with the purchase. Everyone on your team can read customers. Owners and managers can edit them, delete their data and export the list. > [!IMPORTANT] > A checkout email is typed by the buyer or sent by your store. A customer record is purchase history, not proof that the buyer owns an account in your own system. ## Find a customer 1. Open **Customers** and check the mode. 2. Search by name, email or phone, or paste the customer's full ID. 3. Choose a view to narrow the list, then open a customer to see their details. | View | What it means | |---|---| | All | Every customer that matches your search | | Returning | Two or more paid orders | | New | First seen in the last 30 days | | Never paid | No paid orders yet | | Subscribed | Ticked the email-list box at checkout, or marked by your team | To change the order, choose **Last order** or **Spent** in the sort menu beside the search. **Spent** ranks customers on a dollar basis; each amount still shows in its own currency, and it isn't a converted wallet balance. Choose **Show more** for the next results. If nothing matches, choose **Clear filters** and check whether the customer belongs to the other mode. ## Read the customer page Four figures sit at the top: - **Spent:** the amounts of their paid payments, grouped by currency. Unpaid attempts aren't counted. If the buyer paid twice for one order, both payments count here even though there is one order. - **Reached your wallet:** the net amount that reached your wallet from their payments, in dollars, whichever coin it arrived in. It can differ from Spent because of fees, conversion, payments not reported yet or more than one payment. - **Orders:** how many of their orders were paid, out of all of them, with one dot per order. - **Needs you:** an order that needs your decision or isn't fulfilled yet, if there is one, with a count of any others. Below them are their **Orders**. Open one to see its items, payments and timeline without leaving the page. The page shows the latest 50; **All their orders** opens the full list in Orders, filtered to this customer. The side of the page holds: - **Contact:** email, phone, date of birth (when a checkout asked for it), whether they're on your email list and since when, and any store customer IDs. - **Ships to** and **Bills to:** the latest saved addresses, with a button to copy them. - **Note:** your private note (below). - **Activity:** each edit to their details (which fields, and by whom, never the old values) and any data request their store sent. **Email** at the top opens your device's email app with their address; it doesn't send anything by itself. ## Edit a customer's details Choose **Edit** on the **Contact** card to change the name, email, phone, date of birth, either address, or **On your email list**, then choose **Save details**. The customer's **Activity** records which fields changed and who changed them. - A changed email is the address later orders join. Railbed refuses an email another customer already has; open that customer instead. - A later order still brings its own details, and the newest details win. - If someone else saved changes while you were editing, your save is refused. Reload the customer and try again. ## Corrections made by Railbed support If Railbed support corrects a customer's details for you (a name, phone number, address or email), the customer page shows **Corrected by Railbed support** with **View original values**, so what the buyer or store originally supplied stays readable. The corrected values are what the list, search, exports and the API show. A corrected email becomes the customer's identity: later orders with that email join this customer, and support cannot give a customer an email another customer already uses. Railbed keeps the reason for a correction; it isn't shown here. ## Keep a private note Use the **Note** card for context that helps you serve the customer, such as a delivery instruction. The customer never sees it, and it isn't included in API responses or webhooks. 1. Choose **Add note**, or **Edit note** to change one. 2. Write up to 2,000 characters. 3. Choose **Save note**. **Cancel** keeps the saved version. To remove a note, clear the text and save. The note belongs to this Railbed record: it doesn't update your store's customer profile, and changes in your store don't edit it. ## Export your customer list Choose **Export CSV** on Customers. The file follows the current search, view and sort, and holds up to 10,000 customers. It has each customer's name, email, phone, date of birth, email-list mark, location, both addresses, order and paid-order counts, spending by currency, **Received (net, USD)** (what reached your wallet, in dollars), first seen and last order dates, and customer ID. Export the **Subscribed** view to get your email list. When more than 10,000 match, the dashboard says **Export limited to 10,000 rows; narrow the filter** and the file ends with a row saying the same. Customers whose data was deleted are left out. Files you already downloaded stay wherever you saved them. ## Delete customer data 1. Open the customer and choose **Delete customer data**. 2. Read the confirmation. It can't be undone. 3. Choose **Delete customer data** again, or **Keep details** to stop. Railbed removes the customer's name, email, phone, date of birth, email-list mark, addresses, store customer IDs and private note. It also removes them from their orders, payments, invoices and stored webhook deliveries, along with the answers they gave to your checkout questions and what each payment recorded about where it was started (device, browser, operating system, language, time zone, country and IP address). An invoice email or reminder still waiting to go to them is stopped. Orders, payments, invoices and amounts stay for your records, with the person shown as **Deleted customer**. After deletion: - The customer leaves the customer list and its export. Their orders can still be opened and searched. - The same email in a future purchase creates a new customer. - Webhooks already delivered, emails already sent and files already exported can't be recalled. Handle those copies where they were saved. - Order descriptions, your references and integration metadata are separate fields. Don't assume they were cleared if you or an integration put personal details in them. Deleting customer data doesn't refund, cancel or fulfil an order. Review the order or payment separately if the buyer also needs help with a purchase. - [Manage orders and fulfilment](https://railbed.com/docs/user-guide/orders.md): Review what was bought and what still needs to be delivered. - [Understand payment statuses](https://railbed.com/docs/user-guide/payments.md): Distinguish payment confirmation from delivery. --- # Find records across Railbed > Jump to an order, customer, payment, invoice or setting from anywhere in your dashboard. Search by a name, amount, email or record ID. Source: https://railbed.com/docs/user-guide/search/ · Updated: 2026-11-18 · Railbed user guide ## Open search Choose **Search** at the top of the dashboard's sidebar, or the search icon in the bar at the top of your phone's screen. On a keyboard, press **⌘K** on Mac, **Ctrl+K** on Windows or Linux, or **/** when you aren't typing in a field. Before you type, search shows what you can do from here: **On this page** (views of the page you're on, such as **Not fulfilled** on Orders), **Recent searches**, **Go to** for other pages and **Actions** such as **New invoice**. Type at least two characters to search your records. Results come in groups, with the current page's group first. Use **↑** and **↓** to choose a result, **Enter** to open it, and **Escape** to close search. A page or action only takes you there; it doesn't complete a payment, export or change by itself. **Switch to Test mode** or **Switch to Live mode** changes the dashboard's mode. ## What you can look for | Search for | Example | What Railbed looks for | |---|---|---| | Order number | `#1042` or `1042` | A Railbed or store order number | | Customer | `alex@example.com` | That exact email, or names and phone numbers containing what you typed | | Product or reference | `consultation` | Records whose description, items or reference contain it | | Record ID | `pay_example`, `ord_example`, `cus_example` | That payment, order or customer, and the records linked to it. Type at least four characters after the underscore | | Amount | `49.00` or `$49.00` | That amount in any currency; check each result's currency | | Transaction or address | A full transaction hash or deposit address | The payment it belongs to | | Shortened chain reference | `0x1234…abcd` | Hashes and addresses with that beginning and ending | | A link | A checkout's link, or the tracking page of an invoice made in another app | That checkout or invoice, and its orders and payments | | Page or action | `customers`, `settings`, `new invoice` | Dashboard pages and shortcuts | The line under the search field says how Railbed is reading your query, such as **Looking for order #1042** or **Looking for this transaction hash**. Read it when the results aren't what you expected. A currency symbol doesn't limit an amount search to that currency. Transactions and addresses are recognised on Polygon and the other `0x` networks only. A Bitcoin, TRON, Solana or other deposit address or transaction ID isn't read as one yet; open the payment from Payments instead. ## What each group finds | Group | What it holds | |---|---| | Orders | Orders by number, customer, item, SKU or reference | | Customers | Customers by name, email or phone. Customers whose data you deleted aren't found, though their orders are | | Payments | Payments by email, product, reference, ID, transaction or deposit address, including payments toward an invoice | | Invoices | [Invoices made in other apps](https://railbed.com/docs/user-guide/payment-links.md), such as Telegram, Slack, the API or while setting up, by what or who they're for or a reference | | Checkouts | Active checkouts by name, or by a pasted checkout link | | Developers | API keys by name, webhook endpoints by address, and deliveries by their `evt_` or `whd_` ID. Shown only to owners and developers | > [!NOTE] > Invoices you build in the dashboard aren't in account search yet. To find one, use the search on the [Invoices](https://app.railbed.io/invoices) page, which looks up the invoice number, customer or item. A payment made toward one does appear under **Payments**. Search API keys by their names, never by pasting the key. Anything that looks like a Railbed secret key or webhook signing secret is refused, with a note to search by name instead, and is never saved. ## Test and Live stay separate Results belong to the current mode. If nothing matches, check the mode before assuming the record is missing: search offers **Search Test mode instead** or **Search Live mode instead**, which switches the dashboard and searches again. Changing the mode clears the old mode's results. Your records have not been deleted or moved. [Test and Live mode](https://railbed.com/docs/user-guide/test-and-live.md) explains the separation. ## See more results Each group shows up to five results. For Orders, Customers and Payments, **Show all matching …** opens that page with your search applied, where you can page through every match. Other groups say **Newest 5**; open their page to look further. Text searches read your newest 5,000 records of each kind. When a group has older records, it says **From your newest 5,000**, and a group with no recent match offers **Search all …** to search that page's full list. Exact searches (an ID, an email, an order number, a transaction) always look through every record. If a result opens the wrong view, clear that page's filters or search with the full record ID. A payment belongs to an order, so open the order when you need the purchase and fulfilment details. ## Recent searches and privacy Railbed remembers your last five searches that opened a result. They are saved in this browser for your sign-in only. Signing out, or a session that expires, removes them; choose **Clear recent searches** in the search dialog to remove them sooner, especially on a shared device. ## When search cannot load Check your connection, then choose **Try again**. You can still move around with the sidebar and search within a list page. Search never shows earlier results as if they answered a different query or belonged to the other mode. The search box on this documentation site searches public articles and code examples. It doesn't read your account or customer data. --- # Find and understand a payment > Search across your invoices, checkouts, store and API payments. See what happened, what arrived and what to do next. Source: https://railbed.com/docs/user-guide/payments/ · Updated: 2026-11-21 · Railbed user guide ## Find an order Open [Payments](https://app.railbed.io/payments) and check the mode. The list includes payments toward invoices, from checkout pages, from your store and from the API, in that mode. For the full purchase, including items, customer and fulfilment, open [Orders](https://railbed.com/docs/user-guide/orders.md). A payment is one attempt to pay; several attempts can belong to the same order. Search by buyer email, product name or payment ID. Choose a status to narrow the list, and **Show more** when there are more results. Select a payment to open its details. **Visual example: Read the status of each payment.** The sample payment list shows a $49 Paid consultation, a $250 In progress deposit and $19 of resources that need your decision. Only the Paid order is ready for normal fulfilment. *Illustrative records · read each status before delivering an order.* ## Understand each status Choose the label you see in the dashboard. The explanation shows what it means and the next step to take. **Visual example: Choose a status to find your next step.** **Open: The payment is ready for your customer.** A payment exists, but the buyer has not reached the provider hand-off yet. Your next step: Share the link or wait for the buyer. Keep the order unfulfilled. Check that the payment is in the right Test or Live mode. **In progress: Your buyer has reached a card provider.** Railbed is still waiting for payment confirmation. Opening the provider or returning to your site does not confirm a payment. Your next step: Wait and follow the payment timeline. Do not deliver yet. A Live card decline may stay In progress until the payment expires. **Paid: This order is ready for fulfilment.** The payment passed the applicable confirmation checks, or you accepted one that needed your decision. Your next step: Match the payment to the order, then deliver once. Review the reported settlement when needed. A Paid Test payment is a simulation. It does not represent money received. **Needs your decision: The money reached your wallet, and you decide.** Money arrived but didn’t pass a check, so it isn’t paid yet. Nobody at Railbed is reviewing it. Team members who can’t accept payments see Needs a decision. Your next step: Open the payment, read the reason and check your wallet. Accept it as paid, or follow up with the buyer. Do not fulfil automatically. Owners and managers can accept a payment as paid. Read the guide before accepting. [Payments that need your decision](https://railbed.com/docs/user-guide/held-payments.md) **Underpaid: Less than the full amount arrived.** Shown beside Needs your decision: money arrived, but for less than the order’s value allows. Your next step: Open the payment and compare what arrived with the order. Do not fulfil automatically. You can accept what arrived as paid, or ask for a new payment. Railbed has no top-up for the difference. [Payments that need your decision](https://railbed.com/docs/user-guide/held-payments.md) **Not received: This money may not have reached your wallet.** Money arrived, but the evidence shows it may have gone somewhere else, such as a different wallet or deposit address. Nothing of it counts as received, and it can’t be accepted. Your next step: Open the payment, read the reason and email support with the payment ID. Do not fulfil. A later valid confirmation can still settle it. [Payments that need your decision](https://railbed.com/docs/user-guide/held-payments.md) **Declined: This Test payment was ended as failed.** Declined appears only when a Test payment is simulated as a terminal failure through the API. A simulated card decline on the Test provider page leaves the payment open to try another provider, and Live card declines are handled by the provider and are not reported to Railbed. Your next step: Start a new Test payment to try another outcome. An unsuccessful Live attempt can remain Open or In progress, then expire. **Expired: The payment’s time limit has passed.** The checkout can no longer start a new payment attempt. Late settlement evidence can still change its status. Your next step: Recheck the current status and timeline before sending a replacement request. An expired payment can still become Paid or Needs your decision if money arrives late. **Canceled: You canceled this invoice.** Its link can no longer be used to start a new payment. Canceling an invoice does not reverse a transfer already in progress. Your next step: Check the payment timeline for late settlement before requesting payment again. Send a new invoice if another request is needed. *Explanations only. This example does not read or change a real payment.* | Filter | What it lists | |---|---| | **Paid** | Confirmed payments, including ones you accepted | | **Needs your decision** | Every payment whose money arrived but didn't pass a check, including any that read **Not received**. Team members who can't accept payments see **Needs a decision** | | **Underpaid** | Only the ones where less than the full amount arrived | | **In progress** | The buyer went to a card provider or was shown a crypto address, and nothing has arrived yet | | **Open** | Created, but the buyer hasn't started paying | | **Declined** | Only Test payments simulated as failed through the API. Live declines happen on the provider's page and aren't reported to Railbed | | **Expired** | The time to pay ran out. A canceled invoice made in another app reads **Canceled** | An unsuccessful Live attempt usually stays **Open** or **In progress** and later expires. Half an hour after a buyer went to a card provider with no money back, the row says so, such as **Went to Stripe 3 hours ago · no payment yet**, in Payments, Invoices and Home's recent payments. Hover over the line for the date and time of the hand-off. The **No payment yet** filter lists these payments, and each one's details say what to do next: send the buyer the same link again, where they can choose another way to pay. The status doesn't change: money that still arrives settles the payment as usual, even after it expired. Recheck the current status before acting on an old screenshot or list. ## Read the details drawer The drawer brings together what was saved for the payment and the evidence received afterwards. Depending on the payment, it shows: - **Needs your decision** at the top, with the reason and, for owners and managers, **Accept as paid** ([what to check first](https://railbed.com/docs/user-guide/held-payments.md)). - **Order and customer**, linking to the order and the customer's page, and how many attempts the order has had. - The source (**Invoice**, **Checkout** or **API**), plan, **Billed to**, customer email and **Your reference** when present. - **Provider**, or **Paid with** for a crypto payment, such as **Crypto · USDC on Base**. - **Provider sent (before fees)** or **Buyer sent (before fees)**, and **You received**: the net amount that reached your payout wallet. - For a card payment in progress with no money yet: **No money has reached your wallet for this payment yet. If the buyer finishes at Stripe, it updates here by itself.** - **Check now** on Live payments a buyer has started paying ([below](#check-now)). - **Checkout link** for an unpaid API session, to copy. - **Crypto addresses shown**: each coin and network the buyer chose, the amount asked and the address. - **Buyer** (**Payer** on an invoice's payment): the device, browser, operating system, language, time zone, country and IP address the payment was started from, as the buyer's browser and connection reported them. A payment your own server started through the API, or one started before November 7, 2026, has none. Webhooks and the API don't include them, and deleting the customer deletes them. - **Timeline** of everything that happened ([below](#follow-the-timeline)). - **Details**: the **Payment ID** with a copy button, the **Payout wallet** locked for this payment and the deposit or crypto address. If you have changed your wallet since, an open or in-progress payment says **Pays the previous wallet**: its money still goes to the address saved when it started. Use the copy button next to the payment ID when matching an order or asking for help. On Live payments, a shortened wallet, address or transaction opens on that network's explorer. ## Check a payment now When a buyer says they've paid but the payment still reads **In progress** or **Expired**, open it and choose **Check now**. Railbed asks the payment network about this payment straight away and judges anything found with the same checks as always: - **Money arrived. The payment is updated.** It now reads Paid, or Needs your decision. - **Money arrived. This payment updates once it's forwarded to your wallet.** - **Nothing has arrived yet. Railbed keeps checking by itself.** - **The payment network is busy. Try again in a minute.** Railbed already checks on its own schedule (from a few minutes to two days after the hand-off) and updates the moment money arrives, so Check now only saves the wait. It's offered on Live payments whose buyer went to a card provider or was shown a crypto address in the last 30 days, once every 5 minutes per payment. Owners and managers can use it. Each check is added to the timeline as **Checked with the payment network**. ## Follow the timeline The timeline explains the sequence. A checkout opened, a buyer entering their email and a buyer going to a provider are all earlier steps than a confirmed payment. Under **Routed to**, the timeline says who chose the provider: **Chosen by the buyer**, **Set in your provider choice**, or **Chosen by Smart Routing**. When your checkout's provider couldn't take the buyer and Smart Routing sent them to another, it says why: | Reason | Example | |---|---| | The buyer's country | Stripe doesn't take buyers in South Korea, so Smart Routing chose Banxa | | The provider's minimum | This payment is under Stripe's minimum, so Smart Routing chose Banxa | | The currency | Stripe doesn't take CAD payments, so Smart Routing chose Banxa | | The provider was paused or down | Stripe wasn't available at the time, so Smart Routing chose Banxa | | Railbed's checks found it failing | Stripe wasn't working at the time, so Smart Routing chose Banxa | | You turned it off | Stripe is turned off for your buyers, so Smart Routing chose Banxa | | Too little time left (Venmo) | This payment had too little time left for Venmo, so Smart Routing chose Stripe | | The minimum couldn't be checked | Stripe's minimum couldn't be checked at the time, so Smart Routing chose Banxa | Where no reason was recorded, as on older payments, it says **Chosen by Smart Routing because Stripe couldn't take this payment**. When a card payment expires after its buyer reached a provider, **Expired without payment** adds that the buyer went to that provider and no payment came back. A **Didn't pass a check** entry shows what arrived against what was expected, and why. A flagged entry (**A later payment notice didn't match this payment**, with its reason) records something that arrived afterwards and changed nothing: a second transfer to a payment that already needs your decision, or Railbed stopping its own status checks after repeated errors. The payment keeps its status; a later valid confirmation can still settle it. A **Webhook delivered** entry concerns the notification to your connected system. It doesn't mean that system has finished delivering to the customer. If the payment is Paid but your store hasn't updated, check the endpoint's delivery log in [Developers](https://app.railbed.io/developers), then the receiving system. ## Read the money correctly The order amount is the customer's checkout price. **You received** is the reported net amount that reached your payout wallet, in dollars. Fees and conversion make those amounts differ. **Not reported yet** means the net receipt isn't available yet. Don't treat it as zero or substitute the order price. Paid payments without it aren't in Home's received totals until it's reported. **Nothing counted** on a Not received payment means none of its money is counted as reaching your wallet. [Wallet and settlement](https://railbed.com/docs/user-guide/wallet-and-settlement.md) explains how the totals work. ## Decide whether to deliver For manual fulfilment, check that the payment is **Paid** and matches the intended order. For connected systems, use the [fulfilment guide](https://railbed.com/docs/guides/fulfilment.md) so repeated notifications can't fulfil the same order twice. For **Needs your decision** or **Not received**, read [Payments that need your decision](https://railbed.com/docs/user-guide/held-payments.md) first. Never deliver automatically from Open, In progress, Needs your decision, Not received or an unconfirmed browser return. ## Next step - [Payments that need your decision](https://railbed.com/docs/user-guide/held-payments.md): When money arrives but doesn't pass a check. - [Orders](https://railbed.com/docs/user-guide/orders.md): See the whole purchase and mark it fulfilled. --- # Payments that need your decision > Why a payment reads Needs your decision or Not received, and when you can choose to accept the amount that arrived. Source: https://railbed.com/docs/user-guide/held-payments/ · Updated: 2026-11-18 · Railbed user guide ## What Needs your decision and Not received mean Railbed checks the evidence for every payment before it counts as paid. When money arrives but doesn't pass a check, the payment isn't marked paid, and its status says what it waits on: - **Needs your decision:** the money reached your wallet, and you decide whether it's right for this order. When the only problem is that less arrived than expected, **Underpaid** shows beside the status, and your buyer's page says so too. Team members who can't accept payments see **Needs a decision**. - **Not received:** the evidence shows the money may have gone somewhere else, such as a different wallet or deposit address, or a transaction already counted on another payment. It can't be accepted, and none of it is counted as reaching your wallet. A payment counts as paid when what arrives is worth at least 85% of the order, card or crypto, which leaves room for a provider's flat fee, an exchange's withdrawal fee or a price that moved while the buyer paid. Less than that reads **Underpaid**. A payment never needs your decision just because of the coin or the network it arrived on. What arrived is valued in dollars (a dollar coin at face value, any other coin at the payment network's price) and judged against the order, whichever provider sent it, including the few that pay on [another network](https://railbed.com/docs/user-guide/buyer-experience.md#apple-pay-and-google-pay). Owners and managers get an email when a Live payment needs a decision. Each person can turn it off under **Payments that need a decision** in [Settings → Email notifications](https://railbed.com/docs/user-guide/branding-and-settings.md#email-notifications). Nobody at Railbed is reviewing these payments, and Railbed never holds your money: payments go straight to your wallet. In the API and webhooks they have the status `held` and the event `payment.held`. ## Find the payment 1. Open the bell at the top of any dashboard page and choose **See payments**, or open **Payments** and choose **Needs your decision**. It lists every payment that didn't pass a check, including any that read Not received; **Underpaid** shows only the short amounts. Home's wallet card also counts them under **Needs your decision**. 2. Select the payment and read the reason at the top of the drawer. 3. Match the payment ID, amount, currency and reference to the order you expected. 4. Compare what the provider or buyer sent with **You received**, and check your payout wallet. On a Live payment, open the transaction on the network's explorer. 5. Decide your next step from the reason and the controls Railbed shows. An invoice with such a payment reads **Needs your decision** in Invoices, and the payment doesn't count toward what's paid on it until someone accepts it. ## When Accept as paid is available For a payment that needs your decision, owners and managers see **Accept as paid** in the drawer. Use it only after checking your wallet and deciding that the amount received is right for this order. The confirmation, **Accept this payment as paid?**, marks the payment as Paid with what arrived and sends `payment.paid` to your webhooks, which can trigger order fulfilment. It can't be undone. It doesn't charge the customer for a difference, create another transfer or add anything to your wallet. > [!IMPORTANT] > Accept as paid is an order decision. Check the wallet and the intended order first. Don't use it just to make a warning go away. ## When a payment reads Not received A Not received payment can't be accepted in the dashboard, because the evidence doesn't show that its money reached your wallet. The drawer says why and gives the support address. **You received** reads **Nothing counted**. Keep the order undelivered while you find out what happened. When asking for help, include the payment ID, the exact reason shown, the order amount and whether it is Test or Live. Never send an API key, signing secret, seed phrase or private key. ## Don't top up the original payment A payment can't be topped up. Don't ask a buyer to send the difference to the original payment address. If more is needed, first establish what already arrived, then send a new request, such as an [invoice](https://railbed.com/docs/user-guide/invoices.md) for the difference. If a second transfer does reach a payment that needs your decision, it isn't added to the first. The payment keeps the first transfer's amount and transaction. The timeline gains a new **Didn't pass a check** entry with the second transfer's amount and a flag saying a second transfer arrived, and you're notified again: a `payment.held` webhook, and the Telegram, Slack and email alerts you've set up. Decide what to do from the payment's details and your wallet, as for any other. A later valid confirmation can still settle the payment by itself. Refresh its status before taking another action, especially if you come back to it later. ## Practice before you need it Make a Test payment, and on the simulated provider page choose **Simulate an underpayment**, which sends half the amount. Find the payment, read its details and try accepting it with simulated money. [Test and Live mode](https://railbed.com/docs/user-guide/test-and-live.md) has the full walkthrough. ## Next step - [Find and understand a payment](https://railbed.com/docs/user-guide/payments.md): The drawer, the timeline and Check now. - [Understand your wallet and settlement](https://railbed.com/docs/user-guide/wallet-and-settlement.md): Why amounts received differ from order prices. --- # Understand your wallet and settlement > Know where the money goes, how received totals are calculated, and why your checkout price and wallet balance can differ. Source: https://railbed.com/docs/user-guide/wallet-and-settlement/ · Updated: 2026-11-21 · Railbed user guide ## Your wallet is yours Railbed sends each payment to the payout wallet saved for it, as USDC on Polygon for almost every card payment. It keeps no balance for you and there's no payout to request. **Home** shows your checkout activity and your wallet; it isn't a separate Railbed account. Use a self-custody wallet whose keys you control. Your public address belongs in Settings; your seed phrase and private key never do. To turn what's in your wallet into money in your bank, follow [Move money to your bank](https://railbed.com/docs/user-guide/move-money-to-your-bank.md). **Visual example: Read your wallet balance and receipts.** The sample wallet balance is 182.40 USDC. The sample last-24-hours Railbed receipts are $46.31, counted in dollars whatever coin arrived. The wallet can include other transfers; Railbed receipts include reported net settlements. *Illustrative amounts, not a fee quote. Wallet balance and Railbed receipts measure different things.* ## Balance and received totals are different | Number | What it represents | |---|---| | **Your wallet** on Home, in Live | The USDC balance read from your payout wallet on Polygon, shown in dollars with when it was checked. It can include money from elsewhere and reflect transfers out, and it leaves out money that arrived as another coin or on another network, such as Ethereum or Bitcoin | | **Received** for the period you choose, and **Received today** | Reported net receipts from Railbed payments, in dollars, whatever coin or network each arrived in | | Received in Test mode | Simulated receipts, marked **Simulated**; no money in a real wallet | | Original order amount | The price the buyer was asked to pay, in the checkout currency | | **You received** on a payment | The reported net amount for that payment, in dollars. A payment that arrived in a coin other than a dollar coin also shows the amount of that coin, valued at its price when the payment was checked | A wallet balance goes down when you send money out of the wallet. Received is a record of receipts, so the two numbers don't need to match. The wallet card also counts payments under **Needs your decision** (their money is already in your wallet) and **Buyers paying now** (not received yet). A buyer who went to a card provider more than half an hour ago with no payment back moves to **Went to a provider** (no payment yet), which opens those payments. **Verify balance** opens your wallet on the public Polygon explorer, and in Live, **Move to your bank** opens a short guide. ## Why the amount received differs Your checkout can be priced in USD, EUR, GBP, CAD, AUD, INR or SEK, but almost every card payment settles as USDC on Polygon. [A few providers pay on another network](https://railbed.com/docs/user-guide/buyer-experience.md#apple-pay-and-google-pay): Apple Pay (as a provider of its own), Alipay, WeChat Pay, Rampnow and Venmo on Ethereum, where forwarding to your wallet costs more and comes out of your share, and Cash App as USDT on BNB Chain. Provider pricing, conversion and fees affect what arrives. When your account has a Railbed fee, **Settings → Payout wallet** shows what comes out of each card payment: the card provider's charge, a 1% network fee and your Railbed fee. Use the rate shown for your account; not every business has the same one. The fee and payout wallet are locked when a payment starts. Later changes apply to payments started afterwards, so use the payment's own details when looking into an older one. An illustrative amount in these docs is not a promise of what you'll receive. The buyer's provider quote and the payment's reported settlement have the actual figures. ## What Not reported yet means A payment can be Paid before the amount that reached your wallet is reported. The dashboard shows **Not reported yet** rather than guessing from the order price or what the provider sent. Those payments are left out of received totals until the amount is reported, and Home's **Received** card says how many, for example **1 paid payment isn't in the total until its amount is reported**. Open the payment for its latest details. ## Check a particular receipt 1. Open **Payments** and choose the payment. 2. Confirm its mode, payment ID, order amount and status. 3. Read **You received** and the **Payout wallet** for that payment. 4. For a Live payment, open its transaction in the timeline on that network's explorer (Polygonscan for most). 5. If it reads Needs your decision or Not received, follow [Payments that need your decision](https://railbed.com/docs/user-guide/held-payments.md) before delivering the order. A live balance read can fail on its own. If the wallet card shows an error, choose **Try again**; a failed later check keeps the last balance with when it was read. An error doesn't mean a payment failed or that the wallet is empty. ## Change the payout wallet Only an owner can change the payout wallet. 1. Go to **Settings → Payout wallet**. 2. Choose **Connect a different wallet** and pick the wallet, or paste the new public address into **Polygon address**. On Home in Live, the wallet card's **Ending …** label turns into **Change wallet** and opens the same wallet list. 3. Choose **Save settings**, review the full address in **Change your payout wallet?**, and choose **Change wallet**. With crypto payments on, you also confirm the new wallet works on every network. Settings shows which wallet app a connected address came from. Railbed refuses an address that can't receive your payouts: a token's own address (such as USDC's contract), Railbed's own fee address, an example address from documentation, a payment's deposit address, or a contract that isn't a wallet on Polygon. A wallet change needs a sign-in from the last five minutes. If yours is older, Railbed asks you to sign in again first (**Sign in again to save your payout wallet. What you entered stays here.**); nothing changes until you do, and the address you entered is kept for you to save. The business's first payout wallet, added during setup, accepts a sign-in from the last hour instead, since there's no saved wallet yet for anyone to redirect. A wallet added after Railbed support removed yours counts as a change and needs the five minutes. If someone else saved a wallet while you were adding the first one, yours isn't saved: Railbed says **This account changed while you were saving. Reload and review the latest settings.** Reload to see the saved wallet, and change it from there if it isn't the right one. After the change, Railbed: - Records it under the wallet in Settings (**Changed on … by … from …**, with the previous address, or **no saved wallet** for the first, and the wallet app it came from) and in the owners' [latest activity](https://railbed.com/docs/user-guide/branding-and-settings.md#see-what-changed) (**Payout wallet added** for the first, **Payout wallet changed** after that). - Signs you out of every other device, so only the browser you used stays signed in. - Emails the business's owners and, where they're connected, alerts Telegram and Slack. If you see a change you didn't make, sign in and change the wallet back. Payments already in progress keep their saved address; in **Payments**, an open or in-progress payment that will settle to the old address says **Pays the previous wallet**. An invoice made in another app that still pays the old wallet, and whose customer hasn't reached a card provider yet, can be replaced in one step: its page offers **Replace link**, which makes the same invoice paying the current wallet and cancels the old one. Keep access to the old wallet for the payments that stay on it. Changing the setting doesn't move the old wallet's balance. ## Other payout wallets An invoice can pay a different wallet of yours instead of the payout wallet, for example one you keep for a client or one part of the business. 1. Under **Settings → Payout wallet → Other wallets**, choose **Add a wallet**. 2. Give it a **Name** your team will recognise (up to 40 characters; buyers never see it) and paste its **Polygon address**, then choose **Continue**. 3. Check the full address and choose **Save wallet**. A business can save up to ten. Then pick one under **Pays to** in an invoice's **Payment settings** ([Pay another wallet](https://railbed.com/docs/user-guide/invoices.md#pay-another-wallet)). An invoice never takes a typed address. Card payments to that wallet settle as USDC on Polygon, and such an invoice takes card payments only. > [!NOTE] > **Using the API?** An invoice made through the API names the wallet by its ID (`payout_wallet_id`, which starts `pw_`). Each wallet under **Other wallets** shows its **ID for the API**; choose **Copy ID**. Each wallet gets the same protections as the payout wallet. Only an owner can add or remove one, after a sign-in from the last five minutes. Railbed checks it the same way, and again whenever those checks change; if a saved wallet stops passing, it reads **Can't take Live payments**, says why, and invoices can't pay it in Live. Every change is recorded in the owners' latest activity, emailed to the owners, sent to Telegram and Slack where they're connected, and signs you out of your other devices. To stop using a wallet, choose **Remove**, then **Remove wallet**. Railbed won't remove a wallet while an unpaid invoice pays it (for one made in another app, until its customer starts paying): void or cancel those invoices first, or wait until they're paid or expired. A payment that already started keeps the wallet it started with and still settles there, so keep access to the wallet until those payments finish. ### Wallets on other networks While [crypto payments](https://railbed.com/docs/user-guide/crypto-payments.md) are on, **Wallets on other networks** holds one wallet for each network with its own kind of address, such as Bitcoin, TRON and Solana. Choose **Add** (or **Change**) beside a network, paste the address and save it; Railbed checks it against that network's format and checksum first, with the same sign-in, records and alerts. A network without a wallet isn't offered to buyers. > [!NOTE] > Railbed turns these networks on one at a time, and none is offered while your crypto fee is 0%, so the section lists only the networks your buyers can pay on today, and doesn't appear while there are none. A network where you already saved a wallet stays listed, saying buyers aren't offered it right now, so you can still change or remove the wallet. Your main payout wallet still needs to be set. A buyer who pays in that network's coins (BTC on Bitcoin, USDT or TRX on TRON, USDC, USDT or SOL on Solana, and so on) pays straight into the wallet you saved for it, with Railbed's crypto fee taken from what arrives as on the other networks. **You received** shows the payment in dollars: USDC and USDT at face value, any other coin at the network's price when the payment was checked, with the amount of that coin beside it. The fee and wallet are locked when the buyer is shown the address, so removing or replacing the wallet stops new addresses for that network but doesn't move a payment already on its way. Keep access to the old wallet until those payments arrive. ## Refunds and card disputes Railbed has no refund control that reverses a settled payment; settled sales can't be pulled back from your wallet. A refund is something you arrange and send yourself. Recording a refund in WooCommerce doesn't send money. Card disputes are handled by the card provider; a payment status in Railbed is not a dispute-management service. Establish what was paid and what arrived before deciding how to handle a customer's request. Deleting a checkout or canceling or voiding an invoice is never a refund. ## Next step - [Move money to your bank](https://railbed.com/docs/user-guide/move-money-to-your-bank.md): Sell what arrived and withdraw it. - [Find and understand a payment](https://railbed.com/docs/user-guide/payments.md): What happened to a payment and what arrived. --- # Move money from your wallet to your bank > Your sales are already in your own wallet. Sell the USDC for dollars through an exchange or your wallet app, then withdraw it to your bank. Source: https://railbed.com/docs/user-guide/move-money-to-your-bank/ · Updated: 2026-11-18 · Railbed user guide ## Your money is already yours Railbed card sales settle as USDC, almost always on Polygon, to the payout wallet you control. Railbed never holds or moves the money, so there is no payout to request in the dashboard. USDC is a digital dollar: to spend it as ordinary money, you sell it for dollars, or your local currency, and withdraw it to your bank through a service that works where you live. There are two common ways to do that: - **An exchange account in your name.** You send the USDC from your wallet to the exchange, sell it there and withdraw to your bank. Coinbase and Kraken, for example, accept USDC on Polygon and pay out to bank accounts in many countries. - **Your wallet app's Sell or Cash out.** Some wallet apps sell through a built-in provider and pay your bank directly. MetaMask, for example, offers **Sell** in the US, the UK and parts of Europe; the coins and networks it accepts depend on your country. Each service shows its fees and how long the bank transfer takes before you confirm. On **Home** in Live mode, **Move to your bank** under your wallet opens a short version of these steps, with a link back to this guide. Moving money never needs your recovery phrase or private key: never type them into a website or give them to anyone. ## Send USDC to an exchange and withdraw 1. Open an account with an exchange that pays out to banks where you live, and finish its account setup. 2. On the exchange, choose to deposit or receive **USDC**, and choose **Polygon** as the network. Copy the deposit address it shows. 3. In your wallet app, choose to send **USDC**, check that the network is **Polygon**, and paste the exchange's address. 4. For your first transfer, send a small amount and wait until it shows on the exchange. Then send the rest. 5. Sell or convert the USDC to dollars, or to your local currency. 6. Withdraw the money to your bank account. > [!WARNING] > Send on the Polygon network, and choose USDC as the coin. Money sent on the wrong network, or to an address made for another coin, can be lost. ## Sell from your wallet app 1. Open your wallet app and choose **USDC** on Polygon. 2. Look for **Sell** or **Cash out**. If your app doesn't offer it where you live, use an exchange instead. 3. Choose your bank account and the amount, and follow the provider's steps. ## If something goes wrong **Your wallet won't send the USDC.** Sending on Polygon needs a small network fee. Some wallet apps, such as MetaMask, can take it from your USDC; others need a little POL, Polygon's own token, in the wallet first. **The deposit hasn't shown on the exchange.** On **Home**, choose **Verify balance** to open your wallet on the public explorer, and find the transfer. Send its transaction link and the deposit address you used to the exchange's support. **Some payments arrived as another coin or on another network.** [A few card providers](https://railbed.com/docs/user-guide/buyer-experience.md#apple-pay-and-google-pay) pay on another network: Apple Pay (as a provider of its own) pays USDC on Ethereum, Alipay and WeChat Pay pay USDT there, Rampnow pays ETH there, Venmo pays PayPal USD (PYUSD) there, and Cash App pays USDT on BNB Chain. If you turned on [crypto payments](https://railbed.com/docs/user-guide/crypto-payments.md), buyers can also pay in USDT, or on networks such as Base and Arbitrum, into the same wallet, and in coins such as Bitcoin into the wallets you saved for those networks. Send each coin on the network it arrived on, to an exchange address made for that coin and network. Sending on Ethereum needs a little ETH in the wallet for the network fee, and on BNB Chain a little BNB. **Your Home balance looks lower than what arrived.** The wallet card reads only USDC on Polygon. Money that arrived as another coin or on another network is in your wallet too; see it in your wallet app or on that network's explorer. ## Next step - [Understand your wallet and settlement](https://railbed.com/docs/user-guide/wallet-and-settlement.md): Why your wallet balance and your received totals can differ. - [Find and understand a payment](https://railbed.com/docs/user-guide/payments.md): See what happened to a payment and what arrived. --- # Make Railbed your own > Put your business name, logo and brand on checkout, choose how Railbed reaches you, secure your sign-in and manage your team. Source: https://railbed.com/docs/user-guide/branding-and-settings/ · Updated: 2026-11-18 · Railbed user guide ## Find your settings Open [Settings](https://app.railbed.io/settings): choose your name at the foot of the dashboard's sidebar, then **Settings**. On a phone, open the menu first. The page is in five sections, listed in a rail beside it (or as a row of links above it on a narrow screen): | Section | What's in it | Who sees it | |---|---|---| | Business | **Business details** and **Brand**: what buyers see on your checkouts | Owners; managers see **Brand** | | Getting paid | **Payout wallet** and **Crypto payments** | Owners | | Your account | **Account** and **Two-factor sign-in** | Everyone, for themselves | | Notifications | **Email notifications** and **Telegram** | Everyone, for themselves | | This device | **Appearance**, **Google Analytics** and **Railbed on your device** | Everyone, for this browser | Business and payout settings are shared across Test and Live mode: a change made while viewing Test mode is a real change to your business. Your account, notifications and device choices belong to you and cover every business you're on. ## Business details buyers recognize **Business details** controls the identity customers see on your checkouts and invoices. Only owners can change it. | Setting | Where it is used | |---|---| | Logo | Your checkouts, invoices and tracking pages | | Business name | Your checkouts and invoices | | Support email | A way for buyers to contact your business about an order. Optional | | Checkout brand color | The accent on checkouts and buy buttons that don't set their own or match your website | Use a support email you watch. It is your business's address for buyers; it doesn't make Railbed send receipts. If you hid the **Your first payment** checklist on Home, a **Setup checklist** card here offers **Show it on Home**. ## Save text and color changes 1. Change your business name, support email, brand color or your own name. 2. Check the **You have unsaved changes** bar at the bottom of the page. 3. Choose **Save settings**, or **Discard** to go back to the saved values. 4. Open one of your checkouts to see the result. If you try to leave Settings with something unsaved, including a website you typed under **Brand** but haven't saved, the dashboard asks first. If your session expires before you save, what you typed comes back after you sign in. ## Upload a logo or profile photo Choose the image control, pick your image and adjust the crop. **The image saves as soon as you finish cropping it**; you don't need **Save settings** afterwards. Choose a simple logo that still reads at small sizes. Use an ordinary image such as PNG, JPEG or WebP; SVG files aren't accepted. If an image is refused, follow the message and try a plain PNG or JPEG export. The business logo and your profile photo are separate. Changing your photo doesn't change the logo buyers see. ## Your name and photo **Settings → Account** holds your profile photo (shown next to your name in the dashboard) and **Your name** (your team sees it on the **Team** page). If you sign in with Google or GitHub, Railbed fills both in from that account when you haven't set them yet. Type your name and choose **Save settings** with any other changes on the page, or upload a different photo. A photo you remove stays removed; signing in again doesn't bring it back. ## Match your website **Settings → Brand** reads your website and finds your logo, name, brand color and fonts, so your checkouts look like your site. 1. Add your site under **Your website** (owners; it may already be there from sign-up) and choose **Save website**. Use your own site, not a social profile or link-in-bio page: those show the platform's look, so Railbed refuses them. 2. Choose **Pull from your website**, or **Pull from another link** to read a different site. 3. Review what Railbed found. Nothing changes yet. 4. Choose **Use this brand**, or **Cancel**. Owners can also tick **Also use this logo as your business logo** and use the name it found as the business name. You can read five new sites a day; a site read in the last 30 days is free to read again. When Railbed finds your brand by itself, the card shows it as a suggestion with **Use this brand** and **Dismiss**. Owners and managers can use Brand; managers can read sites but not change the website or business details. A saved brand sets your checkouts' accent color and fonts. Checkouts you create afterwards start with **Match my site** on; existing checkouts keep their look until you turn it on in their **Appearance**. ## Set an individual checkout's appearance Open **Checkouts**, choose your checkout, then **Edit**, and find **Appearance**. Your checkout keeps Railbed's design; you choose: | Setting | What it changes | |---|---| | Match my site | Uses the brand saved in **Settings → Brand** | | Light or dark | Railbed's light or dark theme for this checkout | | Accent | The pay button, links and the focus ring. If no text reads clearly on a color, the editor says so and the checkout uses Railbed's ink on it instead | | Text font, Heading font | Any Google Font. Display and handwriting fonts are used for headings only | | Show your logo and name | Whether your logo and business name appear at the top | | Header image | A logo or brand banner across the top of the checkout. It saves as soon as you choose it | The fonts, logo and header image are under **Fonts, logo and header image**. A checkout's own settings win over the brand. The layout, the order summary, the other colors and the corners are Railbed's and don't change. For checkout pages and widgets, **Button text** in the editor changes the payment button inside the checkout. For a buy button on your own website, set its label under **Share → Add it to your site**, or in the `label` attribute of its snippet. Save the checkout, then open its real buyer page and any embed that uses it. The editor's preview is good for the layout; the buyer page shows the whole flow. ## Keep the payout address accurate The **Payout wallet** card, shown to owners, has your Polygon address, your fees and a history of wallet changes. Changing the wallet asks for a sign-in from the last five minutes and confirmation of the full new address; afterwards your other devices are signed out. Payments already in progress still use the wallet they started with. Only the business's first wallet, added during setup, accepts a sign-in from the last hour. Read [Wallet and settlement](https://railbed.com/docs/user-guide/wallet-and-settlement.md#change-the-payout-wallet) before changing it. Never paste a seed phrase or private key into the address field. ## See what changed Owners see the business's five latest changes at the end of the bell's panel, at the top of every dashboard page. Each row says what changed and who changed it, such as **Business renamed**: Now “Northstar Studio”, by Alex Morgan. | Row | When | |---|---| | **Payout wallet added** | The business's first payout wallet was saved, or an owner saved one of the [other wallets](https://railbed.com/docs/user-guide/wallet-and-settlement.md#other-payout-wallets), shown with its name | | **Payout wallet changed** | A saved wallet was replaced. Payments already started keep the previous wallet | | **Payout wallet removed** | Railbed support removed the payout wallet, and Live payments can't start until you save a new one; or an owner removed one of the other wallets | | **Bitcoin payout wallet added**, **changed** or **removed** (and the same for each other network) | An owner saved, replaced or removed the wallet for that network under **Wallets on other networks** | | **Business named** | The business got its first name, during setup | | **Business renamed** | The business name changed in Settings | | **Crypto payments turned on**, **Crypto payments turned off** | Someone changed **Settings → Crypto payments** | | **Card provider turned off**, **Card provider turned back on**, **Card providers changed** | An owner changed an **Offer to buyers** switch under [Integrations → Card providers](https://railbed.com/docs/user-guide/buyer-experience.md#choose-card-providers). Turning one off also says which checkouts moved to another provider | | **Card provider order changed**, **Card provider order reset** | An owner saved [their own order](https://railbed.com/docs/user-guide/buyer-experience.md#provider-order), naming the provider now first, or went back to Smart Routing's order | The panel also lists changes to webhook endpoints and their signing secrets, API keys, connected AI agents and assistants, and Shopify ad tracking, and when Railbed paused, suspended, archived or restored the business. A change a tool made through the API names its API key instead of a person, and one Railbed support made says **Railbed support**. A change made in Test mode says so. ## Email notifications Railbed emails your team when something needs attention, from **notifications@mail.railbed.com** to each person's sign-in address. Replies go to Railbed support. Open **Settings → Email notifications** to see where yours go and choose which you get. The card lists only the emails your role receives. | Email | Who gets it | Can be turned off | |---|---|---| | Your payout wallet was added, changed or removed | Owners | No, it's a security notice | | A new Live secret key was created | Owners and developers | No, it's a security notice | | A tool used a Live secret key to add a webhook endpoint (such as a Zapier or n8n workflow being turned on) | Owners and developers | No, it's a security notice | | Railbed paused new payments for your business, suspended or archived it, or restored it | Owners and managers | No, it changes what your business can do | | A payment needs a decision | Owners and managers | Yes | | A paid Shopify order needs a stock check | Owners and managers | Yes | | A paid order couldn't be created in your Shopify store | Owners and managers | Yes | | Your Shopify store stopped taking checkouts through Railbed, lost Railbed's code or was disconnected | Owners and developers | Yes | | Your webhook endpoint is failing | Owners and developers | Yes | | A buyer couldn't pay because of something in your setup (your payout wallet, a price under the smallest card payment, a one-provider choice with no fallback, a way of taking payments turned off), at most once a day for each reason. The bell shows it for a day too | Owners and managers | Yes | Emails cover Live mode only. They never include your buyers' names or email addresses, or a full secret key. Your choices apply to every business you're on, and each email's button opens the business it's about. Choose **Send test email** to check that emails reach you (one a minute). If an email to your address bounces or is marked as spam, Railbed stops emailing it and the card says so; write to support to turn emails back on. Sign-in codes and team invitations come from Railbed's sign-in service and always arrive, whatever you choose here. If Railbed's emails land in spam, add notifications@mail.railbed.com to your contacts. ## Telegram alerts **Settings → Telegram** connects your own Telegram to Railbed for payment alerts, a daily summary and quick checks on your sales from the chat. Each person connects their own. [Connect Telegram](https://railbed.com/docs/user-guide/integrations.md#telegram) has the steps, the alert choices and the chat commands. ## Choose Light, Dark or Match system Open **Settings → Appearance** and choose a theme, or use the three icons beside **Theme** at the foot of the sidebar, just above your name: | Choice | What happens | |---|---| | Light | Railbed's paper background and dark text | | Dark | Charcoal surfaces and light text throughout the dashboard | | Match system | Follows this device's appearance setting, including changes made while Railbed is open. This is the default until you choose | The choice applies at once, without **Save settings**, and is saved in this browser. Other dashboard tabs in the same browser follow it; another browser or device keeps its own choice. If your browser blocks storage, the choice lasts until you reload and the card says so. The dashboard's theme doesn't change what buyers see. A checkout's own **Appearance** sets its buyer page, and logos and previews keep the backgrounds they need to stay readable. These docs have their own **Light**, **Dark** and **Match system** choice beside the collection links, remembered separately from the dashboard's. **This device** also holds **Google Analytics**, where **Share usage with Google Analytics** turns Google Analytics on or off in this browser, and **Railbed on your device**, which explains how to [add the dashboard to your home screen](https://railbed.com/docs/user-guide/mobile.md#add-the-dashboard-to-your-device). ## Account access Railbed's sign-in checks who you are by email, Google or GitHub. If access fails, see [Troubleshooting](https://railbed.com/docs/user-guide/troubleshooting.md#i-cannot-sign-in). **Settings → Account** shows the address you're signed in as, and has **Sign out of other devices**. It ends your Railbed sessions everywhere else; the browser you're using stays signed in. Use it after working on a shared or lost device. It asks for a recent sign-in, like a wallet change. ### Two-factor sign-in Two-factor sign-in asks for a six-digit code from an authenticator app each time you sign in, after Google, GitHub or your email. It is optional, belongs to you, and covers every business you're on. Any authenticator app works, such as Google Authenticator, Microsoft Authenticator, 1Password or Authy. To turn it on, open **Settings → Two-factor sign-in** and choose **Turn on two-factor sign-in**. It asks for a sign-in from the last five minutes. Then: 1. Scan the QR code with your authenticator app. If you can't scan it, type the key shown under **Can’t scan it? Enter this key** into the app, or choose **Copy key**. 2. Enter the code the app shows and choose **Turn on**. 3. Save your ten recovery codes with **Copy codes** or **Download**, and keep them somewhere safe away from your phone. Railbed shows them only this once. Choose **I saved my codes** when you're done. If the setup can't start, choose **Try again**. A setup left unfinished for 15 minutes expires; choose **Start again** for a new QR code. Turning it on signs you out of your other devices; the browser you're using stays signed in. AI assistants you connected and your secret keys keep working; review them under **Developers**. Railbed emails you, and messages you on Telegram if you've linked it, whenever two-factor sign-in is turned on or off, new recovery codes are made, or a recovery code is used to sign in. If that wasn't you, email support straight away. Once it's on: - **Signing in** asks for the code after your usual sign-in. Codes change every 30 seconds, and each one works once. The code step lasts ten minutes and takes five tries; after that, sign in again. - **Changes that ask for a recent sign-in**, such as your payout wallet, crypto payments or a webhook signing secret, take a code from your app instead. Choose **Sign in again instead** if you'd rather sign in. - **A recovery code** works once in place of a code when you sign in or turn two-factor sign-in off, if you don't have your phone. Choose **Use a recovery code instead** when Railbed asks for a code. A change that asks for a recent sign-in takes only a code from your app, so without your phone choose **Sign in again instead** and use a recovery code there. - **New recovery codes:** when you have two or fewer left, the card asks you to make new ones. **Make new recovery codes** needs a code from your app, and your earlier recovery codes stop working. - **To turn it off**, choose **Turn off** and enter a code from your app or a recovery code. Telegram and Slack never ask for a code. If you've linked your Telegram account or connected Slack, Railbed in Telegram and Railbed for Slack keep working as before, including what they let you do, such as creating invoices. If you want every way into your account to need the code, disconnect them: **Disconnect** under **Settings → Telegram**, and `/railbed disconnect` in Slack. Ten wrong codes in 15 minutes, counting recovery codes and the code you enter while turning it on, stop Railbed taking any code until the 15 minutes are up. Railbed support can see whether two-factor sign-in is on for your account, never your key or recovery codes. **If you lose your phone and every recovery code**, email support from your sign-in address. Once support has checked it's you, they turn two-factor sign-in off for your account. That signs you out on every device, and Railbed emails you, and messages you on Telegram if you've linked it, to say Railbed staff turned it off. Then sign in as usual, with no code, and set it up again in **Settings → Two-factor sign-in**. ### Your team and roles Owners invite people and choose their roles on the **Team** page. [Work with your team](https://railbed.com/docs/user-guide/team.md) lists the five roles, what each can do, and how to invite, change or remove someone. --- # Work with your team > Invite the people you work with, give each one the role they need, and change or remove access at any time. Source: https://railbed.com/docs/user-guide/team/ · Updated: 2026-11-18 · Railbed user guide Each person on your team signs in with their own account and gets one role. Owners manage the team on the **Team** page in the sidebar; other roles don't see that page. ## What each role can do | Role | What they can do | |---|---| | Owner | Everything, including the payout wallet, business settings, crypto payments and the team | | Manager | Checkouts, invoices, orders and customers (including exports), and accepting payments that need a decision. No wallet, settings or team changes | | Developer | API keys, webhooks, integrations and [AI agents](https://railbed.com/docs/agents.md#connect-an-agent), and reading records. No wallet, settings or team changes | | Sales | Making, sending and changing their own [invoices](https://railbed.com/docs/user-guide/invoices.md#sales-teams), and seeing only those; reading the rest like a Viewer | | Viewer | Reading payments, orders, customers and reports. Can't change anything | ## Invite someone 1. On **Team**, choose **Invite member**. 2. Enter their email, choose their role, then **Send invitation**. 3. They get an email from Railbed's sign-in service and join with that role once they accept. Someone who already has a Railbed sign-in finds it waiting under their **Accounts**. Open invitations are listed under **Invitations**. Each works only for the email it was sent to, until it expires. Use **Resend** to send it again, or revoke it to stop the link working at once. The Team page's **What each role can do** card lists every role's permissions in full. ## Change a role or remove someone 1. On **Team**, choose the person's name under **Members**. 2. Pick a new role and choose **Save role**, or choose **Remove from team** and confirm. They lose access to this business only; their sign-in and any other businesses they belong to aren't affected. To leave a business yourself, open your own name and choose **Leave team**. A business always keeps at least one owner, so make someone else an owner before you step down. Removing someone, or moving them to a role that can't manage keys, disconnects the AI agents they approved for good; connect them again if they're still needed. - [Sales teams and invoices](https://railbed.com/docs/user-guide/invoices.md#sales-teams): Give salespeople their own invoices and see totals by owner. - [Two-factor sign-in](https://railbed.com/docs/user-guide/branding-and-settings.md#two-factor-sign-in): Ask for a code from an authenticator app when you sign in. - [See what changed](https://railbed.com/docs/user-guide/branding-and-settings.md#see-what-changed): Follow who changed what in the business. --- # 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. Source: https://railbed.com/docs/user-guide/integrations/ · Updated: 2026-11-19 · Railbed user guide ## Choose a supported connection Open [Integrations](https://app.railbed.io/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](https://railbed.com/docs/user-guide/buyer-experience.md#choose-card-providers) | Telegram isn't on this page: each person connects their own Telegram in **Settings → Telegram** ([below](#telegram)). | Your setup | Start here | |---|---| | No website, or you bill customers one at a time | [Invoices](https://railbed.com/docs/user-guide/invoices.md) | | A website with an HTML or custom-code block | [Widgets and buy buttons](https://railbed.com/docs/user-guide/widgets-and-buttons.md) | | A Shopify store | [Set up Shopify](#set-up-shopify) | | A WordPress store using WooCommerce | [Install WooCommerce](#install-woocommerce) | | A custom store, app or game | Give your developer the [API quickstart](https://railbed.com/docs/quickstart.md) | 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](https://app.railbed.io/integrations/shopify) and follow its four steps. Railbed checks each one on your store and opens the next when it passes. 1. **Connect your store.** Type your store's .myshopify.com address, your own domain or any link to the store, then choose **Connect store**. 2. **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. 3. **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. 4. **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](https://railbed.com/docs/user-guide/checkout-pages.md#choose-how-buyers-reach-a-provider). 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](https://app.railbed.io/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. 1. **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. 2. **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. 3. **Send a test webhook.** Choose **Send a test webhook** on the setup page. Reload the plugin settings and confirm they say **Connection verified**. 4. **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](https://railbed.com/docs/guides/woocommerce.md) 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](https://railbed.com/docs/user-guide/troubleshooting.md#railbed-says-paid-but-my-store-does-not). ## Follow store orders and customers New WooCommerce checkouts send the purchase details to [Orders](https://railbed.com/docs/user-guide/orders.md) and the buyer to [Customers](https://railbed.com/docs/user-guide/customers.md): 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](https://railbed.com/docs/guides/woocommerce.md) 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. 1. Open **Settings → Telegram** and choose **Connect Telegram**. 2. In Telegram, tap **Start** in the chat with Railbed, then **Connect**. The link works once and lasts 10 minutes. 3. 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](https://railbed.com/docs/user-guide/slack.md). ## 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](https://railbed.com/docs/guides/zapier.md). - **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](https://railbed.com/docs/guides/n8n.md). 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](https://railbed.com/docs/mcp.md) 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](https://railbed.com/docs/mcp.md#connect-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 quickstart](https://railbed.com/docs/quickstart.md): Create and check a payment from a server. - [Fulfil orders safely](https://railbed.com/docs/guides/fulfilment.md): Confirm the right order and prevent duplicate delivery. - [Webhooks](https://railbed.com/docs/webhooks.md): Receive signed payment events and recover missed deliveries. - [Your own checkout](https://railbed.com/docs/guides/custom-checkout.md): Build 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](https://railbed.com/docs/agents.md#connect-an-agent). --- # Railbed for Slack > Connect your Slack workspace to get payment alerts and a daily report in the channels you choose, check your account, create invoices and accept payments without leaving Slack. Source: https://railbed.com/docs/user-guide/slack/ · Updated: 2026-11-18 · Railbed user guide ## What it does Railbed for Slack connects one Slack workspace to your Railbed business. Once it's connected, your team can: - get **alerts** in the channels you choose: payments that are paid or need a decision, and account notices such as a changed payout wallet or a failing webhook endpoint; - get a **daily report** of yesterday's sales and the last 7 days, at the hour you pick; - **check the account** with `/railbed stats`, `/railbed recent`, `/railbed review` and `/railbed status`; - **create, edit, share and cancel invoices** for one amount; - **accept a payment that needs your decision**, from the alert itself; - **ask Slackbot** about sales and payments, if you allow it when connecting. Buyers always pay on Railbed's own checkout page. Slack only shows the link, never card details. Railbed can't read your messages, files or channel history. ## Connect your workspace You need the Owner or Developer role. 1. Open [Integrations → Slack](https://app.railbed.io/integrations/slack) and choose **Add to Slack**. 2. Slack asks you to pick the workspace and approve. You come back to the dashboard, which shows the workspace as **Connected**. 3. Choose **Open Railbed in Slack** to pick the channels for alerts ([below](#choose-where-alerts-go)). Railbed also sends you a direct message in Slack with an **Add a channel** button. A Slack workspace can be connected to one Railbed business, and a business to one workspace. Some workspaces only let admins add apps; if Slack says the app needs approval, ask your Slack admin. Until Slack's directory approves Railbed, Slack may show "App is not approved by Slack" when you add it. If the dashboard shows **Needs reconnecting**, choose **Reconnect Slack**. Your channels and people stay as they are. ## Connect yourself Each person who uses Railbed in Slack connects their own Railbed login once. The first time you use a command or a button, Railbed shows you, privately, **Connect your Railbed login**. It opens a page that names the workspace, your Slack name and the business, and asks you to confirm. The link works once and lasts ten minutes. You can only connect if you're on that business's team in Railbed. What you can do in Slack is what your role allows in the dashboard, checked again on every click: | You want to | Roles that can | |---|---| | See stats, recent payments and what needs a decision | Every role | | Create, edit and cancel invoices | Owner, Manager | | Accept a payment that needs your decision | Owner, Manager | | Choose channels for alerts | Owner, Developer | If you're removed from the business, your Slack connection stops working at once. Disconnect yourself with `/railbed disconnect` or from Railbed's **Home** tab in Slack. An Owner or Developer can remove anyone's connection under **People connected** on Integrations → Slack. ## Choose where alerts go In the channel you want, type `/railbed alerts`, or choose **Add a channel** on Railbed's Home tab in Slack. For a private channel, add the app first: type `/invite @Railbed` in the channel. Each channel's settings: | Setting | Choices | |---|---| | **Payment alerts** | **Paid**, **Needs a decision**, **Checkout started**, **Declined**, **Expired unpaid**, and **Test payments too** (on by default; Test alerts start with "Test mode") | | **Account notices** | **Payout wallet changed**, **Webhook endpoint failing**, **Stock short on a paid order**, **Paid order not in Shopify**, **Shopify store problem**, **A buyer couldn’t pay** | | **In each alert** | **Buyer’s name and email** (anyone in the channel sees them, including guests from outside your company, so a private channel is safer) and **What was bought** (off shows the order number instead) | | **Daily report** | The hour and **Time zone**, or Off. It covers your Live sales | A new channel starts with paid, needs a decision and every account notice. The first save posts a short note in the channel saying what Railbed will post there. You can change or remove channels under **Alerts** on Integrations → Slack too. Anyone connected can also get alerts in their own direct messages: on Railbed's Home tab in Slack, choose **Turn on**, then pick the events. Each person changes their own; an Owner or Developer can remove anyone's from Integrations → Slack. ## Commands Replies to commands are visible only to you. | Command | What it does | |---|---| | `/railbed stats` | Sales and what was received today, in the last 7 days and in the last 30 days. "Today" follows the time zone of your direct-message alerts, or UTC | | `/railbed recent` | Your five latest paid payments | | `/railbed review` | Payments that need a decision, then any marked Not received | | `/railbed link 49 Logo design` | An invoice for $49; put a currency after the amount for another (`49 EUR Logo design`). `/railbed link` alone opens the full form | | `/railbed status` | Your business, mode and connection, and whether your payout wallet can take Live payments | | `/railbed alerts` | This channel's alert settings (in a direct message, your own) | | `/railbed test`, `/railbed live` | Switch between Test and Live for your commands and Home tab | | `/railbed disconnect` | Disconnect yourself | | `/railbed help` | The list of commands | ## Invoices in Slack 1. Use the **Create invoice** shortcut (the plus menu or the shortcut search), the **Create invoice** button on Railbed's Home tab, or `/railbed link` alone. 2. Fill in the **Amount**, **Currency** and **What it’s for**. Optionally choose a channel under **Post it in** or a person under **Send it to**, how long it **Can be paid for** (7 days to start, up to a year), and the **Customer name**, **Customer email** and a **Note to the customer**. Leave both **Post it in** and **Send it to** empty to keep it to yourself. 3. Choose **Create link**. Slack shows **Invoice created** with the link. In Live mode you need a payout wallet that can take Live payments first; Slack says so if you don't have one. In Test mode the invoice takes simulated payments only. A channel post has **Edit**, **Cancel link** and **View in Railbed**. A person you sent it to gets their own message with one **Open payment page** button. You can edit an invoice only until someone starts paying it; if a buyer has the page open when you change the amount, they're asked to check the new amount before paying. Once it's paid, canceled or expired, the message says so and keeps only **View in Railbed**. These invoices ask for one amount and let the customer choose from every card provider you offer. Railbed doesn't email them; they're listed in **Invoices** with the rest. See [Invoices made in other apps](https://railbed.com/docs/user-guide/payment-links.md). ## Payments that need your decision When a payment needs your decision and the money reached your wallet, its alert has **Accept as paid** (so do `/railbed review` and the Home tab). It asks you to confirm, then accepts the payment as the dashboard would, and the alert shows who accepted it. If the payment changed in the meantime, Slack says so and nothing is accepted. A payment marked **Not received** has nothing to accept. See [Payments that need your decision](https://railbed.com/docs/user-guide/held-payments.md). ## Ask Slackbot When you add Railbed and allow it, people in your workspace can ask Slackbot about sales and payments. Each person signs in to Railbed the first time, and any change Slackbot prepares waits for them to confirm in Railbed. Integrations → Slack shows **Ask Slackbot** as On or Off; to turn it on later, an Owner or Developer chooses **Add to Slack again** and allows it. It uses the same connection as [AI assistants](https://railbed.com/docs/mcp.md). ## Disconnect Slack Choose **Disconnect Slack** on Integrations → Slack, or remove the app in Slack's own settings. Either way, Railbed deletes the workspace's connection, channels, people and unsent alerts straight away. Your payments and records in Railbed are not affected, and messages already posted stay in Slack. --- # Use Railbed on your phone > Manage payments from your phone's browser, move around with the tab bar, and add the dashboard to your Home Screen for quicker access. Source: https://railbed.com/docs/user-guide/mobile/ · Updated: 2026-11-18 · Railbed user guide ## Use the dashboard anywhere Open [the dashboard](https://app.railbed.io/) in your phone's browser and sign in. It's the same dashboard and account as on a computer, laid out for the smaller screen, so you can share an invoice, check a payment or decide on one that needs your decision without installing a store app. ### Move around with the tab bar On a phone or a narrow window, a bar along the bottom of the screen holds the pages you open most: | Tab | Opens | |---|---| | **Home** | Your sales, wallet and recent payments | | **Payments** | Every payment and its status | | **Create** | A new invoice or checkout (shown when your role can create one) | | **Orders** | Orders and their fulfilment | | **More** | The full menu: Customers, Invoices, Checkouts, Integrations, Developers and Team, your business and Test or Live, Settings, and the Light, Dark or Match system switch | A line above the tab marks where you are. Pages that open from the menu light up **More**. ## Add the dashboard to your device Open **Settings → Railbed on your device** (under **This device**) and follow the steps for your browser: - **iPhone or iPad:** open Railbed in Safari, open the Share menu and choose **Add to Home Screen**. If shown, leave **Open as Web App** on, then tap **Add**. - **Android or desktop:** open your browser's menu and choose **Install app** or **Add to Home screen**. - **Safari on a Mac:** choose **File → Add to Dock**. Browser wording can vary. The installed app opens the same dashboard with the same sign-in; you still sign in as usual. On Android, pressing and holding its icon offers shortcuts to **Payments** and **Create a payment**. The Settings card is hidden once you're using the installed app. Checkout and invoice links you open as a buyer stay ordinary browser pages; saving one never replaces the installed dashboard. ## Choose light or dark The dashboard follows your device's light or dark setting to start (**Match system**). To choose for yourself, use the switch in the menu (**More** on a phone) or **Settings → Appearance**. Your choice is kept in this browser. See [Choose Light, Dark or Match system](https://railbed.com/docs/user-guide/branding-and-settings.md#choose-light-dark-or-match-system). ## Stay connected when managing payments You need an internet connection to load current payment and wallet information and to save changes. When your connection drops, the dashboard says **You’re offline. Reconnect to refresh payment and account information.** and keeps any form you're filling in. If a page can't load at all, you see **We can’t connect right now** with **Try again**. That screen is not an offline copy of your payments, and nothing you do offline is queued for later. Once you're back online, refresh the payment before deciding whether to deliver an order. Don't use an old screen as confirmation of a payment's current status. ## Get alerts on your phone For a message the moment a payment is paid or needs your decision, connect [Telegram](https://railbed.com/docs/user-guide/integrations.md#telegram) in Settings, or have your team use [Railbed for Slack](https://railbed.com/docs/user-guide/slack.md). Railbed also emails you about [account changes and payments that need you](https://railbed.com/docs/user-guide/branding-and-settings.md#email-notifications). ## Help a buyer returning from a provider A provider can open a new browser tab when the buyer pays. They should keep the original Railbed checkout tab open and return to it after finishing. If the browser blocks the new tab, payment can continue in the original tab. See [The buyer experience](https://railbed.com/docs/user-guide/buyer-experience.md#why-there-are-two-tabs) for what the buyer should expect and why a return page alone doesn't prove payment. --- # Find your next step > Start with the symptom, check the current payment state, and take the next action without losing track of the order. Source: https://railbed.com/docs/user-guide/troubleshooting/ · Updated: 2026-11-21 · Railbed user guide ## My invoice, checkout or payment is missing Check the mode shown under your business name at the top of the dashboard's sidebar. Invoices, checkouts, payments, API keys and webhook endpoints belong to either Test or Live mode. Switch to the mode in which the item was created, then search Payments using the payment ID or customer email. If you still cannot find it, confirm that you are signed in to the intended Railbed account. An existing buyer URL is not changed by your current dashboard mode. ## The customer did not receive an email Railbed doesn't email an invoice made in Telegram, Slack or the API ([Invoices made in other apps](https://railbed.com/docs/user-guide/payment-links.md)); copy and send its link yourself, or **Duplicate** it into the builder. An invoice made in the dashboard is emailed when you choose **Send invoice** or **Email invoice**, once it has the customer's name and email; its **Emails** card says whether each email was delivered ([Send it](https://railbed.com/docs/user-guide/invoices.md#send-it)). An invoice built in the dashboard emails a receipt for each payment only when **Email a receipt for each payment** is on, and a Test invoice never emails your customer. Checkouts, pricing tables and API payments send no receipt email: the paid checkout shows an on-screen receipt, or follows your success URL. Store order emails come from your store or integration. ## The payment is stuck In progress Open its details and timeline. In progress means the buyer went to a provider; it does not mean Railbed has confirmed payment. Ask the buyer whether the provider completed the payment, requested another step or showed a decline. Half an hour after a buyer went to a card provider with no money back, the payment's row says where they went and when, such as **Went to Stripe 3 hours ago · no payment yet**, in Payments, Invoices and Home's recent payments. Its details say **No money has reached your wallet for this payment yet. If the buyer finishes at Stripe, it updates here by itself.** and then the next step: send them the same link again, where they can choose another way to pay. Home's wallet card counts these buyers under **Went to a provider**, apart from **Buyers paying now**. The status stays In progress until money arrives or the payment expires. When it expires, its timeline says the buyer went to the provider and no payment came back. Keep the original checkout tab available. Live provider declines are not sent directly to Railbed, so an unsuccessful attempt can stay in progress until it expires. Avoid creating another charge request solely because the buyer's browser has not updated. For an API or reusable-checkout payment, the normal payment window is 24 hours. An invoice made in another app is paid within its **Can be paid for** setting, and each payment toward an invoice made in the dashboard has seven days, or until the customer starts a new one. Late payment evidence can still change the result; check the latest status before following up. ## The payment says Needs your decision or Not received Open **Payments → Needs your decision** and read the reason on that payment. **Needs your decision** means the money reached your wallet and you decide whether to accept it (**Underpaid** beside it means less than the full amount arrived); **Not received** means its money may have gone elsewhere, so it can't be accepted. Follow [Payments that need your decision](https://railbed.com/docs/user-guide/held-payments.md). Only use **Accept as paid** when it is offered and you have checked what arrived in your wallet. That action can trigger fulfilment. Do not ask a customer to top up the original payment address. ## Railbed says Paid but my store does not Match the order to the correct Railbed payment ID and mode. In **Developers**, inspect the endpoint's delivery log. A failing endpoint may need a corrected URL, public access to that URL, or the correct signing secret in your store. After fixing the cause, use the available retry or resend action for the event. Your receiver must handle duplicate events safely. In WooCommerce, also check the plugin's connection status and that WordPress cron is running. When an endpoint fails three deliveries in a row, or Railbed gives up on one after every retry, the bell at the top of the dashboard shows a dot and its panel names the endpoint by its host, with a link to Developers for owners and developers. For a Live endpoint, owners and developers also get an email, and your linked Telegram account gets an alert. The item clears once a delivery succeeds. A delivered webhook means the endpoint accepted the request. Your own store still needs to process it correctly. [Webhook delivery and retries](https://railbed.com/docs/webhooks.md) and [WooCommerce](https://railbed.com/docs/guides/woocommerce.md) explain the integration checks. ## My wallet balance does not match my sales The Live wallet balance is read from Polygon and can include non-Railbed deposits or transfers out. It leaves out money that arrived on another network, such as Apple Pay and Google Pay payments on Ethereum. Railbed's received totals include reported net receipts, not the full original order prices. If a Paid payment shows **Not reported yet**, it is missing a reported net settlement amount and may not be included in the received totals. If the wallet balance itself failed to load, use **Try again**. [Read the balance correctly](https://railbed.com/docs/user-guide/wallet-and-settlement.md). ## There are no available card providers Provider eligibility depends on the buyer's country, currency, amount, minimums and current availability. Test mode's fixed providers do not prove that the same choices are available for a Live buyer. A checkout set to **One provider** with Smart Routing turned off stops buyers that provider can't serve, with a message naming it. Turn the Smart Routing option back on, or choose Smart Routing, to let those buyers pay. Providers you turned off under **Integrations** → **Card providers** are never offered. If buyers keep being turned away, turn more back on there: with fewer providers on, the smallest payment you can take may be higher and fewer countries may be covered ([which providers buyers see](https://railbed.com/docs/user-guide/buyer-experience.md#choose-card-providers)). If **Integrations** says **Provider list unavailable; showing the last known list**, Railbed could not refresh provider availability and is routing buyers with the last list it has. Buyers can still pay; the list updates by itself when availability can be read again. Check the amount and currency you intended to charge, and that the checkout is in the intended mode. Do not promise a specific provider or an ID-free checkout to every customer. If asking for help, include the country, price, currency, mode and checkout URL; do not include card details. ## A buyer couldn't pay When something in your setup turns a Live buyer away, Railbed tells you once a day for each reason, by email, in Telegram or Slack if you connected them, and in the bell: **A buyer couldn't pay**. The message says why and opens the page that fixes it: - **Your payout wallet** is missing, can't receive payments, or was refused by the card network when the buyer tried to pay. Change it in **Settings → Payout wallet**; a new wallet clears the problem at once. If you're sure the refused wallet is right, email support. - **The price is under the smallest card payment.** Raise it, or turn on crypto payments. - **One provider with no fallback** can't take that buyer. Turn on **If it can't take a buyer, use Smart Routing instead** in the checkout's provider choice. - **A way of taking payments is turned off.** Turn it on in **Integrations**, or ask support if Railbed turned it off. - **Card providers you turned off** could have taken the buyer. The message names them and says how many times it happened in the last day. Turn one back on in **Integrations** → **Card providers**. **Integrations** → **Card providers** keeps the last 7 days under **Buyers who couldn't pay**: each reason, how many times it happened and when it last did, including buyers no card provider could take from their country. The buyer was told that you can't take the payment right now and that nothing was charged. If the card network refused your setup for another reason, Railbed's team is told too; email support if it keeps happening. If **Developers** says **A revoked key is still being used**, a store or server still has a secret key you revoked, and its checkouts fail. Create a new key and put it there in place of the old one. ## A button or widget does not appear Check that your site contains the embed script and the matching `railbed-button` or `railbed-checkout` element. Use the slug copied from the saved checkout, and verify that the checkout still exists. Some website editors strip scripts or do not execute them in preview. Test the published page and use the site's supported custom-code block. [Widgets and buy buttons](https://railbed.com/docs/user-guide/widgets-and-buttons.md#troubleshoot-an-embed) has copyable examples. ## The buyer did not reach my thank-you page Check that the success URL was saved on the right link or checkout. Railbed redirects from the original checkout tab only after payment confirmation. A buyer who closes it or remains on the provider's page may not reach your URL. Check payment status in Railbed instead of treating a missing redirect as a failed payment. Do not alter a provider's own return links. [The two-tab flow](https://railbed.com/docs/user-guide/buyer-experience.md#why-there-are-two-tabs) explains the behavior. ## My AI agent can't connect or stopped working An AI agent connects through a link it gives you, which you approve on a Railbed page ([how it works](https://railbed.com/docs/agents.md#connect-an-agent)). What the page or the agent says usually tells you which of these it is: | What you see | What to do | |---|---| | The request expired, or the code didn't work | The link and the code each last only a few minutes. Ask your agent to start connecting again, then use the new link straight away | | The agent asked with a different email address | Sign in with the email address you gave the agent, or ask the agent to start again with yours | | Only owners and developers can connect agents | Ask an owner to make you a developer, or to connect the agent themselves | | Agents use the Checkout API, which is off | The API is turned off for this business. Contact support to ask about turning it on | | The agent reports `agent_disconnected` | Someone disconnected it under **Developers → AI agents**, or the person who approved it left the business or can no longer manage keys. Connect it again | | The agent reports `insufficient_scope` | It was approved with **Read only**. Connect it again with **Full access** if it needs to create checkouts or update orders | | The agent can't find a payment you can see | It works in the mode it was approved for. An agent connected in Test sees only Test data | Railbed never asks you for the code. If someone you didn't ask contacts you about one, don't share it. ## I cannot sign in Return to [Railbed sign-in](https://app.railbed.io/login) and choose the way you signed up: **Continue with Google**, **Continue with GitHub** or **Continue with email**. Use the same email address as your Railbed account and complete the verification prompts shown. If your session expires while you are editing a checkout, a new invoice, Settings or business setup, the dashboard keeps what you typed in that browser tab for 30 minutes and brings it back after you sign in. Review it and save again; nothing is submitted by itself. A wallet change, turning crypto payments on or off, and **Sign out of other devices** ask for a sign-in from the last five minutes even when your session is still valid. Saving the business's first payout wallet during setup accepts a sign-in from the last hour; if yours is older, Railbed says **Sign in again to save your payout wallet. What you entered stays here.** and keeps the address for you ([details](https://railbed.com/docs/user-guide/getting-started.md#sign-in-again-at-setup)). An offline page or failed connection cannot confirm current account access. Do not share a one-time code, password or session details in a support message. If you turned on [two-factor sign-in](https://railbed.com/docs/user-guide/branding-and-settings.md#two-factor-sign-in), Railbed asks for a code from your authenticator app after your usual sign-in: | What you see | What to do | |---|---| | **That code didn’t work** | Enter the newest code your app shows. If codes keep failing, check that your phone's time is set automatically | | **That code was already used** | Wait for the next code in your app; each one works once | | **Too many wrong codes** | Sign in again and enter the newest code. If Railbed asks you to wait 15 minutes, wait first | | You don't have your phone | Choose **Use a recovery code instead** and enter one of the codes you saved. Each works once | | You lost your phone and every recovery code | Email support from your sign-in address. Once support has checked it's you, they turn two-factor sign-in off; then sign in as usual and set it up again in Settings | With two-factor sign-in on, a change that asks for a recent sign-in, such as your payout wallet, asks for a code instead. Enter it, then submit your change again. ## Prepare a useful support request Include the payment ID, Test or Live mode, the time of the issue, what you expected, and the exact message shown. For a website issue, include the checkout URL and browser/device. For a store issue, include the store order reference and its matching payment ID. Leave out passwords, seed phrases, private keys, card numbers, API keys and webhook signing secrets. Screenshots should be cropped to the issue and any unrelated customer details removed. --- # Railbed, in plain language > A short reference for the words you will see in checkout, the dashboard and your payment records. Source: https://railbed.com/docs/user-guide/glossary/ · Updated: 2026-11-18 · Railbed user guide ## Payment and checkout terms | Term | Meaning | |---|---| | Invoice | A bill for one customer: line items or one amount, shared as a link or QR code or emailed by Railbed, paid in full or in parts. See [Invoices](https://railbed.com/docs/user-guide/invoices.md). In the API, invoices made outside the builder are called payment links | | Invoices made in other apps | Invoices for one amount made while setting up, in Telegram or Slack, through the API or by an AI assistant. Listed with the rest; see [Invoices made in other apps](https://railbed.com/docs/user-guide/payment-links.md) | | Invoice number | The number Railbed gives each invoice you build, such as `INV-0042` | | Due date | The day an invoice should be paid by. It counts as due until that day ends everywhere, so no customer is late early | | Part payment | A payment toward part of an invoice, when you let the customer pay in parts | | Tip | An extra amount a customer adds when paying an invoice that offers tips | | Checkout page | A reusable product page; every buyer creates a separate payment | | Pricing table | A reusable checkout with several plans and optional two-way price choices | | Payment widget | A compact checkout placed inside your own website | | Buy button | A website button that opens a Railbed checkout in an overlay | | Tracking link | A shareable, status-only view of an invoice made in another app | | Reference | Your own order or purchase order number, attached to a payment or invoice | | Payment ID | Railbed's identifier for one payment, beginning with `pay_` | | Order | The purchase record containing items, totals, customer and one or more payment attempts; see [Orders](https://railbed.com/docs/user-guide/orders.md) | | Customer | The purchase history associated with one email address in one mode; see [Customers](https://railbed.com/docs/user-guide/customers.md) | | Payment attempt | One try at paying an order; a retry can belong to the same order | | Success URL | The page your customer goes to after paying, set under **After payment, send them to** (or **After payment, send buyers to** on a checkout) | | Provider | The licensed service whose page takes the buyer's card details and payment | | Smart Routing | The checks and preferences that choose which card providers can take each buyer, and the provider choice that sends buyers straight to the top one | | Buyers choose, One provider | The other provider choices: buyers pick from the ranked list, or every buyer goes to the provider you pick | | Best match | The provider marked first in the list a buyer sees | | Card provider order | The order you put your card providers in under **Integrations → Card providers**; buyers see the providers that can take them in that order. See [Put card providers in your order](https://railbed.com/docs/user-guide/buyer-experience.md#provider-order) | ## Payment statuses | Status | Meaning | |---|---| | Open | The payment exists, but the buyer hasn't reached a provider yet | | In progress | The buyer reached a card provider; Railbed is waiting for confirmation. Don't deliver yet | | Paid | The payment passed its checks, or you accepted it; safe to deliver once | | Needs your decision | Money reached your wallet but didn't pass a check, so it isn't paid until you decide. Team members who can't accept payments see **Needs a decision**. The API status is `held` | | Underpaid | Shown beside Needs your decision when the only problem is that less than the full amount arrived | | Not received | The money may have gone elsewhere, so there is nothing to accept and nothing is counted as received. The API status is `held` | | Declined | A simulated payment declined in Test mode. A Live card decline isn't reported, so the payment stays Open or In progress, then expires | | Expired | Nobody paid in time. Money that arrives late can still settle it | | Canceled | You canceled the invoice or session before it was paid | | Accept as paid | Your decision to accept a payment that needs your decision, with the amount that arrived. See [Payments that need your decision](https://railbed.com/docs/user-guide/held-payments.md) | For what to do next in each status, see [Payments and statuses](https://railbed.com/docs/user-guide/payments.md#understand-each-status). ## Invoice statuses | Status | Meaning | |---|---| | Draft | Saved but not created yet; it has no page and can be changed or deleted | | Sent | Created and ready to pay; the customer hasn't opened it yet | | Viewed | The customer opened it | | Partially paid | Some of it is paid and the rest is still due | | Overdue | Not fully paid by its due date | | Paid | Paid in full | | Void | You stopped it; it can't be paid any more | | Expired | Its time to be paid ran out | ## Wallet and money terms | Term | Meaning | |---|---| | USDC | The dollar stablecoin your card sales settle in | | Polygon | The blockchain network almost every card payment settles on; [a few providers](https://railbed.com/docs/user-guide/buyer-experience.md#apple-pay-and-google-pay) pay on another network | | Self-custody wallet | A wallet whose private keys you control | | Payout wallet | Your saved public wallet address (on Polygon) for receiving your sales | | Other payout wallets | Further wallets an owner saves in Settings: ones an invoice can pay instead of the payout wallet, and one for each network with its own kind of address for crypto payments. See [Other payout wallets](https://railbed.com/docs/user-guide/wallet-and-settlement.md#other-payout-wallets) | | Crypto payments | An opt-in extra in Settings that lets buyers pay with crypto instead of a card. See [Crypto payments](https://railbed.com/docs/user-guide/crypto-payments.md) | | Deposit address | An address made for one payment that forwards the money to your wallet; never use it as your payout wallet | | Settlement | The money reaching your wallet for a confirmed payment | | Net receipt | The amount that reached your wallet after fees | ## Account terms | Term | Meaning | |---|---| | Owner, Manager, Developer, Sales, Viewer | The five team roles. Sales makes and sends invoices and sees only their own; see [Your team and roles](https://railbed.com/docs/user-guide/team.md#team-roles) | | Test mode | A separate copy of your account for simulated payments; no card is charged. Test pages open only for your team | | Live mode | The mode for real card payments | | Two-factor sign-in | An optional six-digit code from an authenticator app, asked for after your usual sign-in. See [Two-factor sign-in](https://railbed.com/docs/user-guide/branding-and-settings.md#two-factor-sign-in) | | Recovery code | One of ten single-use codes you save when you turn on two-factor sign-in, for signing in without your phone | ## Integration terms | Term | Meaning | |---|---| | Secret key | A private credential, also called an API key, that lets your server, plugin or automation tool use Railbed in one mode, with Full access or Read only | | AI assistant | An app such as Claude or ChatGPT connected to one business through Railbed's MCP server, or an agent you approved through agent sign-in. Manage them under **Developers → AI assistants**; see [AI assistants](https://railbed.com/docs/mcp.md) | | Webhook | A signed message from Railbed to a server when a payment event happens | | Signing secret | A private value your server uses to check that a webhook came from Railbed | | Fulfilment | Your delivery record, separate from payment status; see [Orders and fulfilment](https://railbed.com/docs/user-guide/orders.md#payment-and-fulfilment-are-separate) | | Idempotency | Retrying the same request without creating the same payment twice | For API fields and event payloads, use the [developer reference](https://railbed.com/docs/api.md).