I sent the crypto payment and the order is still waiting: what to do
The four reasons a sent transfer does not show up on the order, how to tell them apart, and what data support needs to close it.
One: the network has not confirmed yet
This is the most frequent case and the one that resolves itself. A transfer goes through two moments: when it is seen on the network and when it is confirmed. The order is settled against what is confirmed, not against what is seen, because what has not confirmed can still vanish.
On Tron and BSC that is usually a matter of minutes; on Ethereum it depends on congestion. The order page updates itself: no need to refresh constantly or send again.
Two: less arrived than the order asked for
Almost always because of the exchange's withdrawal fee. In that case the order is not abandoned: it is flagged as an incomplete payment and moves to manual review, where a person closes it with you.
Do not send the difference on your own without telling anyone: a second small transfer matches no order and adds one more payment to attribute by hand.
Three: the network was not the order's
If you sent on a network other than the one the order shows, the payment is not credited automatically because verification only compares against that specific network's contract. It is the slowest case to resolve, which is why spotting it early matters.
Check it in your exchange's withdrawal history: the network it left on is listed there. If it does not match the order's, write to support immediately with that information.
Four: the transfer predates the order
A transfer sent before the order was created is not attributed to it, because the order only looks at what arrives from the moment it opened. Sending first and creating the order afterwards does not work.
It is not lost either: every transfer reaching one of our addresses is recorded, attributed or not. It is resolved by hand with the order reference and the transaction hash.
Final checklist before you send
Confirm the recipient number from a current source before paying. A saved contact can be outdated, copied with extra characters, or tied to a SIM the recipient no longer uses.
Review country and carrier together. A correct number with the wrong operator can fail or route incorrectly, especially when a family member has changed lines.
Choose the product for the recipient's next real need: flexible airtime for plan control, data when connectivity is the priority, and promotions only when the rules are clear.
Keep one checkout session open and wait for the final status before retrying. Multiple attempts can create duplicate payments or confusing pending states.
Save the receipt until the recipient confirms the balance or package. The transaction reference is the fastest path for support if the operator takes longer than expected.
Useful next steps
Article FAQs
What data does support need?
The order's public reference and the transaction hash. With those two the transfer is located on-chain without any screenshots.
Can I lose the money?
Every transfer arriving at a receiving address is recorded, whether or not it can be attributed automatically, and that record is never deleted. Cases that do not fit on their own are resolved by a person.
Does the order expire meanwhile?
Only what nobody paid expires. Once an associated transfer is seen, the timer stops deciding and a late payment is charged and delivered anyway.
Should I send again if it takes long?
No. A second send is a second payment, and recovering it requires a manual refund. Write to support before sending anything else.
About the author
Computer engineer and founder of RecargaDoble.com, writes about international mobile top-ups, mobile operators, telecommunications, and technology, combining his technical expertise with in-depth industry knowledge.
Related guides
