# Find and understand a payment > Search across your payment links, checkouts and API orders. See what happened, what arrived and what to do next. Source: https://railbed.io/docs/user-guide/payments/ · Updated: 2026-09-26 · Railbed by DeepWork user guide ## Find an order Open [Payments](https://app.railbed.io/payments) and check the mode. The list includes payments from payment links, reusable checkouts and the API in that mode. For the full purchase, including items, customer and fulfilment, open [Orders](https://railbed.io/docs/user-guide/orders.md). A payment is one attempt to pay; several attempts can belong to the same order. Use the search field for a buyer email, product name or payment ID. Choose a status filter to narrow the list, and **Show more** when there are additional results. Open a payment to view its details drawer. **Visual example: Read the status of each payment.** The sample payment list shows a $49 Paid consultation, a $250 In progress deposit and $19 Being reviewed resources. 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 below 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 explicitly accepted an eligible hold. 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. **Being reviewed: Payment evidence needs your attention.** Evidence arrived, but the amount or another confirmation check needs review. Your next step: Open the payment and read the hold reason. Do not fulfil automatically. Accept as paid is available only for eligible holds. Read the held-payment guide before accepting. [Review a held payment](https://railbed.io/docs/user-guide/held-payments.md) **Declined: This simulated payment was declined.** Declined is the Test-mode outcome. Live card declines are handled by the provider and are not directly 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 Being reviewed if money arrives late. **Canceled: You canceled this payment link.** The link can no longer be used to start a new payment. Canceling a link does not reverse a transfer already in progress. Your next step: Check the payment timeline for late settlement before requesting payment again. Use a new payment link if another request is needed. *Explanations only. This example does not read or change a real payment.* Live card declines are handled by the provider and are not directly reported to Railbed. An unsuccessful Live attempt may remain open or in progress and later expire. **Being reviewed** is the current label for a hold, including a short amount; there is no separate Underpaid filter. A payment that expires can still receive late settlement evidence. Recheck the current status before acting on an old screenshot or list view. ## Read the details drawer The payment drawer brings together the information saved for the order and the evidence received afterwards. Depending on the payment, it includes: - The description, original price and currency, customer email, source and payment ID. - Your reference, selected pricing plan or integration metadata when present. - Provider information, the amount sent by the provider and the amount reported as received by your wallet. - The payout address locked for that payment and available settlement transaction links. - A timeline of creation, payment start, provider hand-off, confirmation, review and webhook delivery events. Use **Copy** next to the payment ID when matching an order or asking for help. A shortened wallet or transaction address can be opened in the linked explorer for its full details on Live payments. ## Follow the timeline The timeline explains the sequence. A checkout being created, a buyer entering their email and a buyer going to a provider are all earlier steps than a confirmed payment. A **Webhook delivered** entry concerns the notification to your connected system. It does not mean the connected system has completed delivery to the customer. If the payment is Paid but the store has not updated, inspect the endpoint's delivery log in [Developers](https://app.railbed.io/developers), then check 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. Fees and conversion can make those amounts different. **Not reported yet** means the net receipt is not yet available in that record. Do not treat it as zero, or substitute the order price as the amount received. Some Paid payments are not included in received totals until the receipt amount is reported. [Wallet and settlement](https://railbed.io/docs/user-guide/wallet-and-settlement.md) explains how those totals work. ## Decide whether to deliver For manual fulfilment, check that the payment is **Paid** and that it matches the intended order. For connected systems, use the [fulfilment guide](https://railbed.io/docs/guides/fulfilment.md) so repeated notifications cannot fulfil the same order twice. For **Being reviewed**, read [Review a held payment](https://railbed.io/docs/user-guide/held-payments.md) before making a decision. Do not deliver automatically from Open, In progress, Being reviewed or an unconfirmed browser return.