What this guide covers—and does not
This is a checklist for an existing, authorized request with a named account provider. It is not a form for requesting a withdrawal, a list of Deep's supported assets, a fee schedule or a promise of processing time. It does not turn virtual points or play chips into money. The relevant provider's current terms and your location's rules govern any actual service.
Never give a seed phrase, private key or one-time login code to someone claiming to investigate a transfer. MetaMask's wallet-security guidance explains that anyone with recovery secrets can control the assets. A legitimate case record can start with a request ID and, if one exists, a public transaction hash; it does not need wallet recovery secrets.
Identify the party that can see each part of the record
An account provider may hold a withdrawal request; a sending wallet or service may create the on-chain transaction; the receiving wallet or service decides when and how it credits an account. Those are distinct records and support queues. A Club name, referrer or message sender is not automatically authorized to act for any of them.
Ask the provider that accepted your request for its ID and current state. If a transaction hash exists, verify the chain and then contact the receiving service through its own official route about a missing credit. Do not submit documents, addresses or account records to an unsolicited contact. For account-identity concerns, use the impersonation checklist.
Before authorizing a crypto transfer
- Confirm the exact asset and network in the receiving provider's current instructions; the same token name can exist on multiple networks.
- Compare the complete destination address and any required memo or tag in the official interface. A saved contact or screenshot may be stale.
- Record the displayed amount, unit, fee, limit, review condition and time before confirming. Do not assume terms from another provider or a past request apply.
- Check who controls the sending account and who will receive the asset. If someone pressures you to use a new address or off-platform process, pause and verify independently.
A small test transfer, where the provider permits one, may reveal an address or network mistake before a larger transfer. It cannot authenticate the counterparty or guarantee future performance.
Evidence to preserve without oversharing
On a narrow screen, swipe within the table. With a keyboard, focus the table area and use the left and right arrow keys.
| Record | Why it matters | Privacy caution |
|---|---|---|
| Request ID and provider | Connects the case to the account service that accepted it; a Club or messenger's claim is not a substitute. | Keep the full ID in the provider's authenticated support channel. |
| Time, timezone and terms | Shows when the request was made and which displayed fee, limit or review condition applied then. | Save the original page or confirmation privately; redact personal account data before any public discussion. |
| Asset, network and amount | Separates the token from the network and preserves the exact amount and unit. | Check the receiving provider's own current instructions; avoid posting balances publicly. |
| Destination and memo/tag | Helps the receiving provider identify whether the address and any required destination field match. | A public address can link transactions. Share details with verified support only when necessary. |
| Transaction hash, if broadcast | Lets you look up network broadcast and confirmation; it does not prove an account was credited. | Do not confuse a hash with a private key; still avoid linking it to your identity publicly. |
| Status and support history | Keeps the sequence of provider messages and case numbers without relying on memory. | Keep original screenshots and emails; send minimal copies through the official support route. |
Do not relabel game credits, points or a displayed virtual-item count as currency. A transaction hash proves neither the identity of a claimant nor a receiving account's credit. Keep the request and the transfer as separate events in your notes.
Four states that need different questions
Coinbase's pending-transaction guide distinguishes an unconfirmed network transfer from a confirmed transfer awaiting account credit; its send/receive troubleshooting also checks address and network. These are examples of how one provider explains transfer states, not a universal timeline or guarantee for another service.
On a narrow screen, swipe within the table. With a keyboard, focus the table area and use the left and right arrow keys.
| Recorded state | What it does and does not mean | Safer next question |
|---|---|---|
| Request recorded, no hash | The provider may still be reviewing or preparing the transfer. No on-chain broadcast is evidenced by the request screen alone. | Ask the account provider for the current status and the applicable terms. Do not invent a network delay. |
| Broadcast, not confirmed | A hash exists, but the transfer has not reached the receiving provider's required network-confirmation state. | Check the hash on an independent explorer for that exact network and contact the sender if the transaction is stalled or rejected. |
| Confirmed, not credited | The chain recorded the transfer; the recipient may still need to match the network, address, memo/tag or its own crediting rules. | Contact the receiving provider through its official channel with the minimum identifiers it requests. Confirmation is not proof of account credit. |
| Wrong address or network | The funds may not be recoverable, even if an explorer shows confirmation. | Contact the sending and receiving providers immediately; do not pay an unsolicited recovery service or disclose wallet secrets. |
Write a factual support message
Through the provider's authenticated support channel, state the request ID, submission timestamp and timezone, asset, network, amount and unit, current displayed status, and the exact question you need answered. Add the transaction hash only if one exists. Preserve the original confirmations and terms; send only the records needed for that provider to investigate. Do not accuse a named person of fraud on the basis of a delay alone.
For a broader private-evidence and dispute-routing workflow, see the dispute-record guide. For basic network terminology, use the separate crypto education hub. Neither guide guarantees recovery, reversibility or a provider response.
Frequently Asked Questions
Does this page promise a withdrawal time, fee or supported asset?
No. It is general record and transfer-safety education, not a current service-level offer for Deep or another provider. Confirm the named provider's present terms, supported network, fees and review status through its authenticated official channel.
Does a transaction hash mean the recipient credited my account?
No. A hash can identify an on-chain transaction. The receiving service may require a supported network, correct address or memo, enough confirmations and its own crediting steps. Check both the chain status and the recipient's account status.
Can a confirmed crypto transfer be reversed?
A confirmed on-chain transfer generally cannot be cancelled by the sender. Some provider-specific recovery paths may exist, but they are not guaranteed; contact the actual sending and receiving providers promptly. Never share a seed phrase or private key with a person offering recovery.
What should I do if a request has no transaction hash?
First establish whether the account provider has accepted, reviewed or rejected the request. Ask for the request ID, current state and applicable review terms through the authenticated support route. Without a hash, do not describe the transfer as confirmed or assume a blockchain outage.
Does a small test transfer verify the provider or agent?
No. A completed small transfer demonstrates only that one transfer reached its destination under those conditions. It does not verify identity, authority, future behavior or a standing promise. Verify the responsible provider independently.
Sources and method
Checked 26 September 2026 UTC: Coinbase's pending-transfer explanation, Coinbase's status and wrong-network troubleshooting and MetaMask's recovery-secret safety guidance. Their instructions apply to their own products; this article uses only the general distinctions that a request, broadcast, confirmation and recipient credit are different events, and that wallet secrets must stay private.
No provider-specific fee, speed, address, supported network, legal eligibility or recovery path was verified here. The provider's current authenticated instructions take precedence for an actual request. This page is independent safety education, not financial or legal advice and not a service audit of Deep or another named provider.