Crypto Payment Not Found on PerkShelf: What to Check and What Happens Next
Most not-found payments are a confirmation delay, a network mismatch or an amount mismatch. What to check, and why you usually do not need to paste again.
When you paste a transaction ID, PerkShelf looks it up in Binance's deposit or Pay history. "Not found yet" means the lookup has not returned a successful deposit that matches your invoice.
What to check
- Confirmations. Binance credits a deposit after the network's required confirmations. Your wallet showing "sent" is earlier than that.
- Network. The coin must be sent on the network the invoice names, to that invoice's address.
- Amount. The amount that arrives must equal the invoice. Exchange withdrawal fees taken out of the send cause a mismatch. See choosing a USDT network.
- The right ID. On-chain sends need the transaction hash. Binance Pay needs the Pay transaction or order ID, not an on-chain hash.
- The right invoice. Paste the ID against the invoice you paid. In Telegram, the bot checks all your open crypto invoices.
You usually do not need to paste again
When an ID is not found yet, PerkShelf saves it on your open invoice and re-checks it automatically every few minutes for up to 72 hours. When Binance marks the deposit successful and it matches, your wallet credits on its own.
When to contact support
Open a ticket with the invoice number and TxID if the deposit shows as completed in your wallet history but has not credited after an hour, or if you sent on the wrong network or the wrong amount.
Frequently asked questions
How long does a USDT deposit take to credit?
Usually a few minutes after the network confirms. The invoice shows the typical arrival time for each network.
Can a payment be credited twice?
No. Each transaction ID can only ever credit one invoice.