Find your next step
Start with the symptom, check the current payment state, and take the next action without losing track of the order.
On this page
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); 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).
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.
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 and WooCommerce 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.
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).
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 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 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). 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 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). 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, 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.