Railbed, in plain language

A short reference for the words you will see in checkout, the dashboard and your payment records.

On this page

Payment and checkout terms

TermMeaning
InvoiceA 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. In the API, invoices made outside the builder are called payment links
Invoices made in other appsInvoices 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
Invoice numberThe number Railbed gives each invoice you build, such as INV-0042
Due dateThe day an invoice should be paid by. It counts as due until that day ends everywhere, so no customer is late early
Part paymentA payment toward part of an invoice, when you let the customer pay in parts
TipAn extra amount a customer adds when paying an invoice that offers tips
Checkout pageA reusable product page; every buyer creates a separate payment
Pricing tableA reusable checkout with several plans and optional two-way price choices
Payment widgetA compact checkout placed inside your own website
Buy buttonA website button that opens a Railbed checkout in an overlay
Tracking linkA shareable, status-only view of an invoice made in another app
ReferenceYour own order or purchase order number, attached to a payment or invoice
Payment IDRailbed's identifier for one payment, beginning with pay_
OrderThe purchase record containing items, totals, customer and one or more payment attempts; see Orders
CustomerThe purchase history associated with one email address in one mode; see Customers
Payment attemptOne try at paying an order; a retry can belong to the same order
Success URLThe page your customer goes to after paying, set under After payment, send them to (or After payment, send buyers to on a checkout)
ProviderThe licensed service whose page takes the buyer's card details and payment
Smart RoutingThe 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 providerThe other provider choices: buyers pick from the ranked list, or every buyer goes to the provider you pick
Best matchThe provider marked first in the list a buyer sees
Card provider orderThe 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

Payment statuses

StatusMeaning
OpenThe payment exists, but the buyer hasn't reached a provider yet
In progressThe buyer reached a card provider; Railbed is waiting for confirmation. Don't deliver yet
PaidThe payment passed its checks, or you accepted it; safe to deliver once
Needs your decisionMoney 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
UnderpaidShown beside Needs your decision when the only problem is that less than the full amount arrived
Not receivedThe money may have gone elsewhere, so there is nothing to accept and nothing is counted as received. The API status is held
DeclinedA simulated payment declined in Test mode. A Live card decline isn't reported, so the payment stays Open or In progress, then expires
ExpiredNobody paid in time. Money that arrives late can still settle it
CanceledYou canceled the invoice or session before it was paid
Accept as paidYour decision to accept a payment that needs your decision, with the amount that arrived. See Payments that need your decision

For what to do next in each status, see Payments and statuses.

Invoice statuses

StatusMeaning
DraftSaved but not created yet; it has no page and can be changed or deleted
SentCreated and ready to pay; the customer hasn't opened it yet
ViewedThe customer opened it
Partially paidSome of it is paid and the rest is still due
OverdueNot fully paid by its due date
PaidPaid in full
VoidYou stopped it; it can't be paid any more
ExpiredIts time to be paid ran out

Wallet and money terms

TermMeaning
USDCThe dollar stablecoin your card sales settle in
PolygonThe blockchain network almost every card payment settles on; a few providers pay on another network
Self-custody walletA wallet whose private keys you control
Payout walletYour saved public wallet address (on Polygon) for receiving your sales
Other payout walletsFurther 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
Crypto paymentsAn opt-in extra in Settings that lets buyers pay with crypto instead of a card. See Crypto payments
Deposit addressAn address made for one payment that forwards the money to your wallet; never use it as your payout wallet
SettlementThe money reaching your wallet for a confirmed payment
Net receiptThe amount that reached your wallet after fees

Account terms

TermMeaning
Owner, Manager, Developer, Sales, ViewerThe five team roles. Sales makes and sends invoices and sees only their own; see Your team and roles
Test modeA separate copy of your account for simulated payments; no card is charged. Test pages open only for your team
Live modeThe mode for real card payments
Two-factor sign-inAn optional six-digit code from an authenticator app, asked for after your usual sign-in. See Two-factor sign-in
Recovery codeOne of ten single-use codes you save when you turn on two-factor sign-in, for signing in without your phone

Integration terms

TermMeaning
Secret keyA 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 assistantAn 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
WebhookA signed message from Railbed to a server when a payment event happens
Signing secretA private value your server uses to check that a webhook came from Railbed
FulfilmentYour delivery record, separate from payment status; see Orders and fulfilment
IdempotencyRetrying the same request without creating the same payment twice

For API fields and event payloads, use the developer reference.

Updated · This page as Markdown