The most consequential P2P mistakes happen when an order's instructions are replaced by a private request. Buyers can send money to the wrong account; sellers can release crypto before receiving payment. Check the actual payment state before acting on pressure from the other party.
Confirm receipt before releasing crypto
If you are selling, open your own bank or payment account and verify the amount, sender and receiving account. A screenshot, text message or PDF supplied by the buyer is not proof that you received the funds.
Releasing crypto ends the protection of holding those coins in the order. Support can investigate records, but recovery is not guaranteed once assets have moved. A claim that the bank is slow does not justify release before receipt.
For buyers, the button to report payment is different from the seller's release button. Report payment only after it has been sent as instructed; do not mark an unpaid order paid merely to stop the timer.
Read the bank state and the order state together
| Your role and observation | What it establishes | Next check |
|---|---|---|
| Buyer: bank says processing | A payment request exists, but its final result is unresolved | Check with the bank and explain the state in the order; avoid a duplicate payment or an improvised cancellation |
| Buyer: bank reports completed, seller reports no receipt | The two parties' records need reconciliation | Retain the bank reference and use the order's support process |
| Seller: notification arrived, no corresponding entry in your payment account | The notification alone is insufficient evidence of receipt | Inspect your own account and do not release based on the notification |
| Seller: amount or payer name does not match | The payment differs from the expected order | Report the discrepancy before releasing or making any refund |
These checks do not give either party permission to keep money or assets that do not belong to them. They identify a disagreement that needs resolution through the order and, where relevant, the bank or payment provider. A private request to “refund to this other account” introduces a new destination that the original payment record does not support.
Keep payment instructions in the order
If asked to move to WhatsApp, Telegram or another private channel, keep the transaction discussion in the platform's order chat. It gives support a direct record of what the parties agreed and what changed.
A new receiving account
Do not substitute a bank account sent in chat for the verified order instructions. Before payment, clarify or cancel through the official process. After payment, preserve the order and use support rather than sending money again.
A different amount
If the order shows 3,200 and chat asks for 3,190, the payment would no longer match the order. Do not improvise with underpayment or overpayment to make the figures agree later.
Keep identity documents and payment receipts out of private “verification” exchanges. Evidence requested for a dispute belongs in the official support flow.
Open support from your own account
| Request | Response |
|---|---|
| Send crypto to a safe account to unlock the order | Do not transfer; open official support yourself. |
| Release now and the bank payment will follow | Check your own receiving account before release. |
| Enter a password on a new verification link | Return to your saved official address. |
| Close the appeal before receiving the resolution | Keep following the official dispute process. |
A staff badge, formal language or familiar logo can be copied. Check the channel, not the claimed title. HuiBonus does not operate exchange accounts or collect security codes.
Compare offers without ignoring the conditions
Check completion rate together with order count and the period covered. Compare price using the same currency, amount and payment method. A seller's past results do not prove that the payment instructions for this order are correct.
A better price does not compensate for being asked to pay outside the order. Once an order exists, use its confirmed amount rather than a later verbal discount that changes the transfer.
Watch for a second transaction disguised as a correction
A counterparty may describe another transfer as a small verification payment, a release charge, an overpayment refund or a way to fix the first order. The label does not make the transfer necessary. Identify the original order, the actual money movement and the requested new destination separately, and ask official support to resolve the discrepancy before any further transfer.
For example, suppose a seller receives more fiat than the order specifies. That excess does not justify releasing additional crypto outside the order. Equally, a buyer's request to send the excess to a different name should not be treated as a verified refund instruction. Keep the full amount and reference in the dispute record, and follow the official resolution rather than creating an informal side deal.
Prepare evidence for the actual dispute
Keep the order number, original bank receipt, names, amount, time and transaction reference. State clearly whether the bank transfer is pending, completed, returned or disputed, and whether the crypto has been released.
The platform's available measures depend on the order and asset state. Do not assume that an appeal can reverse an external transfer, and keep any private settlement offer out of it.
If only part of the money arrived, do not release the full crypto amount on a promise that the remainder will follow. Report the discrepancy through the order.
A concise dispute timeline
Separate observations from claims when presenting evidence. An illustrative timeline might say: the order was opened; the bank accepted the payment request; the bank later displayed completed; the seller stated that no receipt was visible; an appeal was opened. Add the actual times and time zone from your own records. Do not replace “the seller stated” with “the bank lost the money” unless you have evidence for it.
Each identifier also has a different purpose. The P2P order number locates the platform transaction, while the bank reference locates the fiat payment. Preserve both, including any later returned-payment record. A chat screenshot without the order number or a payment receipt without the receiving account may leave support unable to connect the two records.
When a resolution arrives, reconcile its outcome with the accounts involved. Check whether crypto was released, the fiat payment was returned, or another specific action remains pending. A closed chat window is not proof of a completed refund. If the stated outcome and your records differ, continue through the same official case with the new evidence.
Payment problems during an active order
I paid but the seller has not released. What should I do?
Check the transfer status, retain its receipt and communicate in the order. Use the appeal or help option when available. Binance's cancellation guide says not to cancel an order after paying.
My bank has restricted the account. Should I use another card?
Not yet. Ask the bank about the first payment's status before doing anything that could duplicate it, and explain the restriction through the order's official support flow. The counterparty has no way of knowing why your bank acted.
I marked an unpaid order as transferred by mistake.
Explain the actual status in the order and follow the official correction or support process. Do not send an unverified payment simply to make the earlier click appear correct.
They say the money has left. Can I release first?
No. Watch your own receiving account. If it has not credited, do not tap release.
They want WhatsApp to keep talking. Does the order still count?
The order may remain active, but private conversations are harder for the platform to verify directly. Keep instructions in the order and do not make an additional off-platform payment.
Can an appeal pull coins that already left escrow?
Recovery is not guaranteed once the crypto has been released or transferred. Submit the order and payment evidence through official support.