What Happens if a Customer Sends the Wrong USDT Amount?
October 10, 2026 · 5 min read
If a customer sends a different USDT amount than the payment page asked for, the money is not lost. It is in the merchant’s account. It just can’t be matched to the order automatically. The customer adds their transaction ID on the payment page, the payment moves to Needs review, and the merchant approves or rejects it in a couple of clicks. Here is exactly what happens in each situation, and how to prevent most of them.
Why does the amount have to be exact?
Each order gets a unique amount, such as 25.0037 USDT. That is how a payment to a shared Pay ID or address is linked to one specific order. A payment of 25.0000 or 24.0037 doesn’t match any open order, so it cannot be confirmed automatically. How unique-amount matching works.
The most common causes
- Rounding. The customer types 25 instead of 25.0037.
- Withdrawal fee deducted. On an exchange the fee is taken from the amount sent, so 25.0037 sent becomes 24.0037 received. The fix is to set the receive amount to the exact figure.
- Paying twice, or paying an amount from an older, expired order.
- Wrong coin. Sending USDC or another coin instead of USDT.
What the customer does: add the transaction ID
On the payment page, under “Already paid? Add your transaction ID”, the customer pastes one of:
- the Binance Pay order ID (digits only), from the transaction details in Binance Pay, or
- the transaction hash (64 characters, sometimes starting with
0x) for TRC20 or BEP20 transfers.
Clearqo looks for that transaction in the merchant’s Binance history. If it finds it but something doesn’t match (amount, timing, or the transaction was already used), the invoice becomes Needs review. The page tells the customer that the payment is being checked and that nothing else is needed. The store gets an invoice.review webhook, and a WooCommerce order is placed On hold.
What the merchant does: approve or reject
- Open Dashboard → Payments and find the payment marked Needs review. The reason is shown, for example “received 24.0037 USDT, expected 25.0037”.
- Check the transaction in your own Binance history.
- Click Approve payment and confirm the amount actually received, or click Reject payment.
Expired payments can be approved the same way, even without a submitted transaction ID, after you have checked that the money arrived. Every transaction can only ever pay one invoice, so the same deposit can’t be approved twice.
What happens to the order?
| Situation | Result |
|---|---|
| Approved, full amount or more received | Invoice paid, order completes as normal. |
| Approved, less than the total received | Invoice paid with the real amount, but the WooCommerce order stays on hold with a note such as “received 24.0037 USDT, less than the order total”. You decide what to do next. |
| Rejected | Invoice rejected, order cancelled. Refund the customer from your Binance. |
| TeraWallet top-up approved | The wallet is credited with exactly what was received, never more. |
For an under-payment, the usual options are to ask the customer to pay the difference as a new small order, to refund what they sent, or, for tiny differences, to complete the order manually as goodwill.
Other situations
The customer paid late
Invoices expire after 30 minutes by default, but an exact payment arriving up to 24 hours after expiry is still confirmed automatically. Its amount stays reserved during that time, so it can’t be confused with a newer order. Later than that, or with a different amount, the payment is handled through review.
The customer paid twice
The first payment completes the order. The second is an ordinary deposit in your account that matches no open order. Refund it from your Binance.
The customer sent more
Over-payments don’t match automatically either. Approve the real amount received. The order completes, and you can refund the difference or, for wallet top-ups, the customer keeps it as balance.
The customer used the wrong network
Whether funds sent on the wrong network can be recovered depends on the receiving exchange. Some deposits can be recovered through Binance support, others are lost. A payment only confirms when it arrives on the network and address configured for your account. Prevention matters most here. See TRC20 vs BEP20.
The customer sent a different coin
Only USDT is matched. Another coin sent through Binance Pay is still in your account. Handle it manually and refund or approve as you see fit.
How to prevent wrong amounts
- Offer Binance Pay first. It sends exactly what the customer types, with no fee deducted and no network to choose. About the Pay ID.
- Rely on the copy buttons. The payment page has one-tap copy for the amount, the Pay ID and the addresses. They also work inside in-app browsers like Telegram’s.
- Explain the receive amount. The page reminds on-chain payers to set the amount that arrives. Repeat it in your own FAQ.
- Show the countdown. The visible timer encourages customers to pay within the window.
- Answer quickly. Reviews only take a minute. A quick approval turns a confused customer into a happy one.
Refunds: who sends them?
You do. Clearqo is non-custodial: payments go straight into your Binance account, and Clearqo has read-only access that cannot move funds. Send refunds from your Binance, for example with Binance Pay to the customer’s Pay ID, or on-chain to an address they give you on the right network. Keep the transaction ID for your records.
FAQ
Is money ever lost when the amount is wrong?
No. The money is in your Binance account. Only the automatic link to the order is missing, and the review step restores it.
Can a customer reuse an old transaction to pay a new order?
No. A transaction can pay only one invoice, and payments older than the invoice are flagged for review instead of being accepted.
Does the store get notified about reviews?
Yes. The invoice.review and invoice.rejected webhooks are sent, and WooCommerce orders move to On hold or Cancelled automatically.
Accept USDT on your website
Paid straight to your own Binance, verified automatically.