Find and understand a payment

Search across your invoices, checkouts, store and API payments. See what happened, what arrived and what to do next.

On this page

Find an order

Open 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. 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.

Payments Illustrative records
PaymentAmountStatus
Design consultationalex@example.com$49.00Paid
Project depositjules@example.com$250.00In progress
Studio resourcessam@example.com$19.00Needs your decision
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.

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 →
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 →
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 →
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.
FilterWhat it lists
PaidConfirmed payments, including ones you accepted
Needs your decisionEvery 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
UnderpaidOnly the ones where less than the full amount arrived
In progressThe buyer went to a card provider or was shown a crypto address, and nothing has arrived yet
OpenCreated, but the buyer hasn't started paying
DeclinedOnly Test payments simulated as failed through the API. Live declines happen on the provider's page and aren't reported to Railbed
ExpiredThe 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).
  • 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).
  • 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).
  • 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:

ReasonExample
The buyer's countryStripe doesn't take buyers in South Korea, so Smart Routing chose Banxa
The provider's minimumThis payment is under Stripe's minimum, so Smart Routing chose Banxa
The currencyStripe doesn't take CAD payments, so Smart Routing chose Banxa
The provider was paused or downStripe wasn't available at the time, so Smart Routing chose Banxa
Railbed's checks found it failingStripe wasn't working at the time, so Smart Routing chose Banxa
You turned it offStripe 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 checkedStripe'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, 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 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 so repeated notifications can't fulfil the same order twice.

For Needs your decision or Not received, read Payments that need your decision first. Never deliver automatically from Open, In progress, Needs your decision, Not received or an unconfirmed browser return.

Next step

Updated · This page as Markdown