How it works

Underpaid, overpaid or late: how OpenReceive confirms crypto payments

An order is paid only when your own wallet says the money arrived. Bitcoin over Lightning can't be paid wrong. Stablecoins that arrive short, over or late get a refund screen.

Accept crypto with OpenReceive

Free & open source · No approval necessary · Paid to your own wallet

The amount and the deadline are part of the invoice

Paid means your wallet says so

Customer paysBitcoin, or a stablecoin through a swap
Your walletreceives it and settles it
Order paidmarked once, by OpenReceive
  • Not when the customer clicks "I paid"
  • Not when a swap provider says the swap is done: the Bitcoin has to reach your wallet too
  • Checked again in the background, so a customer who closes the tab still gets their order

Too little, too much, too late

What happens on each way to pay.

Strict by design

Bitcoin over Lightning

The amount is written into the invoice, so the customer's wallet pays exactly that.

  • UnderpaidCan't happen
  • OverpaidCan't happen
  • LateStart over: a new invoice
  • RefundsNone needed

OpenReceive keeps checking for a few minutes after the countdown ends, so a payment sent just before the end still counts.

Through a swap provider

USDT USDC ETH SOL Stablecoins

A provider you choose gives the deposit an amount and a time limit, then converts it into the same Lightning payment.

  • Slightly overpaidUsually goes through
  • UnderpaidRefund screen
  • Overpaid by more than the provider allowsRefund screen
  • Late, after the deposit windowRefund screen

The refund screen

When a swap can't go through, the customer gets their deposit back without having to email anyone.

  1. 1 It replaces the payment screen No QR code and no amount, so the deposit can't be sent twice.
  2. 2 The customer gets an address On the coin's own network, usually in another wallet app. The refund waits on the order's page.
  3. 3 They confirm it twice Enter, check, confirm. Nothing is sent before the second step.
  4. 4 The whole deposit goes back The order stays unpaid, and the customer can pay again.

You don't do anything. The money never reached your wallet, so you have nothing to send back. Developers: see Swap refunds.

Questions

What if the customer closes the tab after paying?

The order is still marked paid. OpenReceive checks your wallet in the background, not just while the checkout is open.

How long does a customer have to pay?

The checkout shows a countdown. When it runs out, the customer taps Start over and gets a new invoice at the current price.

Why does an overpayment get the whole deposit back, not just the extra?

The swap was for a fixed Lightning payment. The provider has nothing to convert the surplus into, so it refunds the whole deposit and the customer pays again.

Can I refund a Lightning payment?

Not through OpenReceive. Its wallet code is receive-only, so it can't send money. Send a refund from your wallet's own app.

What if a customer pays the same order twice?

OpenReceive fulfills each order once. A second stablecoin deposit onto an order that is already paid is flagged for a person. The checkout shows the transaction IDs to give the swap provider's support.

Do I have to set any of this up?

No. It is built into every OpenReceive plugin and package. For your own checkout screens, read Checkout UX.

Get paid, exactly

Free, open source, and paid straight to your own wallet.

Get started with OpenReceive