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.

On this page

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.

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.

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.

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 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 has the full walkthrough.

Next step

Updated · This page as Markdown