If your Crypto.com crypto sent but not arrived issue is causing panic, the most important thing to know is this: “not arrived” does not automatically mean your crypto is lost. In many cases, the transfer is still pending, the recipient has not claimed it yet, the receiving side has not credited it, or the transaction was sent onchain and is still waiting for confirmations. Crypto.com’s help content says app-based Send transfers to non-users can remain pending for up to seven days, while onchain transactions can stay pending until they receive confirmations and may take longer during network congestion.
The safest move is to stop before sending again ⏳+1 877➦719➦ 1076. First identify whether this was a Crypto.com Send transfer to a person or an onchain send to a wallet address. Then verify the recipient details, network, and transaction status, and check the TxHash if one exists. That verification-first approach helps you find the real cause without creating a duplicate transfer problem.
Before trying random fixes, use this order:
Check whether it was an internal Send transfer or an onchain send.
Crypto.com distinguishes app-based Send transfers from onchain wallet transactions, and the troubleshooting path is different for each.
Open your transaction history and read the exact status.
Crypto.com says Send transactions may show as Processed or, in rarer cases, Pending for longer than usual.
Verify the destination detail.
Check the exact email, phone number, wallet address, network, and memo/tag if relevant. Crypto.com says recipients who did not receive a transfer should confirm the sender used the correct phone number or email address.
Find the TxHash if it was onchain.
Crypto.com says users can paste the transaction hash into the relevant blockchain explorer to see the status and number of confirmations.
Do not resend yet.
If the first transfer is only delayed, sending again can turn one unresolved issue into two successful sends.
That short list is the fastest way to separate a normal delay from a real delivery problem.
When people say “my crypto was sent but not arrived,” they usually mean the receiving person or wallet does not show the funds yet. But that can happen for several different reasons.
Crypto.com says onchain transactions are shown as pending until they receive at least one confirmation. The time depends on the chosen fee level, network traffic, and the blockchain itself. Crypto.com also says that sometimes a transaction can remain pending beyond the estimated time, especially during congestion or when a low fee setting was selected.
For beginners, this is the first thing to understand: a transfer can leave your side without being final on the receiving side yet.
Crypto.com says when you use Crypto.com Send to transfer crypto to someone who is not yet a Crypto.com App user, the transfer can remain pending for up to seven days while the recipient signs up and claims it. If they do not claim it within that time, the transfer expires and the funds are returned.
So sometimes “not arrived” simply means “not claimed yet.”
Crypto.com’s deposit guidance says users can check the transaction hash to confirm whether the transfer was submitted successfully and how many confirmations it has. The same page explains that deposits may remain pending because the required number of block confirmations has not yet been reached.
This is one of the most common reasons a recipient does not see funds immediately.
Crypto.com says that if a recipient did not receive a transfer, they should confirm that the sender used the correct phone number or email address. For onchain transfers, wrong address details, unsupported tokens, or missing memo/tag information can also prevent smooth crediting. Crypto.com says unsupported-token deposits and deposits with missing or incorrect memo/tag details may require manual recovery and may not always be recoverable.
Crypto.com says that after the first block confirmation, a user may receive notice of a pending deposit, and only after the required number of confirmations is reached will the deposit be processed.
That means the blockchain can show movement while the recipient still sees nothing spendable.
This is not stated directly in the help pages, but it follows from the way confirmations, networks, and token support work: the recipient may be checking the wrong wallet tab, the wrong network, or a platform section that does not show the incoming asset yet. This is an inference based on Crypto.com’s guidance to verify onchain status, confirmations, and destination details.
This often points to a Crypto.com Send transfer rather than an onchain blockchain send. If the recipient is not already fully set up, Crypto.com says the transfer can stay pending for up to seven days while they sign up and claim it.
That usually means you need the TxHash. Crypto.com says users should check the blockchain explorer with the transaction hash to see the transfer status and number of confirmations.
This can happen if the sending side has processed the transfer, but the receiving side still needs confirmations or is checking the wrong network or asset view. Crypto.com’s deposit article makes clear that a transaction can be submitted successfully and still not be fully processed until required confirmations are reached.
That is helpful, but it is not enough by itself. The stronger proof is the blockchain record. The TxHash can show the exact destination address, network, and confirmation status. Crypto.com points users to explorers for this exact reason.
Crypto.com says some problematic onchain transactions may remain pending for 2 to 3 days and typically never confirm, often because of congestion or low fee settings.
That is a risky reaction. If the first transfer later completes, you may end up sending twice. Verification comes before any repeat action.
Use this checklist in order.
Confirm the exact coin or token sent
Confirm the amount sent
Confirm whether it was Crypto.com Send or onchain send
Check the current status in transaction history
Confirm the exact recipient email, phone number, or wallet address
Confirm the network used
Confirm whether a memo or destination tag was required
Retrieve the TxHash if the transfer was onchain
Paste the TxHash into the correct blockchain explorer
Check confirmation count
Ask the recipient to check the correct wallet or app section
Save screenshots from both sides
Do not send again until the first transfer is fully understood
Start: Was this sent to a person or to a blockchain address?
A. Sent to a person with Crypto.com Send
Is the recipient already a Crypto.com App user?
Yes: ask them to check account access and notifications.
No: Crypto.com says the transfer may remain pending for up to seven days while they sign up and claim it.
Did you use the correct phone number or email?
No or unsure: verify this first.
Has the claim window passed?
Yes: check whether the transfer expired and was returned.
B. Sent to a wallet address onchain
Do you have a TxHash?
Yes: check the relevant explorer.
No: go back and retrieve it from transaction details.
Does the explorer show pending or unconfirmed?
Yes: the recipient may not see it yet. Crypto.com says onchain sends remain pending until confirmations arrive.
Does the explorer show confirmed?
Then verify address, network, token support, and memo/tag details.
Before using the official support route, gather:
asset name
amount
date and time sent
recipient detail used
network used
current transaction status
TxHash
screenshots of your send record
screenshot or explanation from the recipient side
That evidence pack makes support conversations much easier.
Crypto sent but not arrived to a friend
Most likely cause: Recipient has not claimed the transfer
What to check first: Whether it was Crypto.com Send and whether the recipient signed up
Best next step: Wait within the 7-day claim window or confirm claim status
Crypto sent to wallet but not visible
Most likely cause: Transfer still pending on-chain
What to check first: Transaction hash (TxHash) and confirmation count
Best next step: Monitor the blockchain explorer until confirmations increase
Sender sees processed but recipient sees nothing
Most likely cause: Receiving side not credited yet
What to check first: Explorer status and receiving platform view
Best next step: Wait for required confirmations
Recipient says nothing was received
Most likely cause: Wrong phone, email, address, or network
What to check first: Exact destination used
Best next step: Recheck destination details before doing anything else
Transfer stuck too long
Most likely cause: Congested network or low fee
What to check first: How long it has been pending and explorer status
Best next step: Keep records and prepare for official review
Deposit not credited automatically
Most likely cause: Missing memo/tag or unsupported token
What to check first: Deposit requirements and token/network support
Best next step: Use official support route with full evidence
You want to resend immediately
Most likely cause: Panic, not confirmed failure
What to check first: Whether the first transaction actually failed
Best next step: Stop and verify the first transaction first
Timing depends on the transfer type.
Crypto.com says a transfer sent to someone who is not yet a Crypto.com App user can stay pending for up to seven days while they sign up and claim it. If unclaimed, the funds are returned.
Crypto.com says onchain transfers remain pending until there is at least one confirmation. Estimated first-confirmation times vary by network and fee tier. For example, the help page lists estimates such as about 10 to 60 minutes for Bitcoin depending on fee tier, 30 seconds to 30 minutes for Ethereum and ERC-20 transfers depending on fee tier, and only seconds for some other assets under normal conditions. Those are estimates, not guarantees.
Crypto.com also says some transactions can remain marked as pending for 2 to 3 days and usually never confirm when congestion is high or a low fee setting was selected.
Crypto.com says deposits may still appear as pending until the required number of confirmations has been reached, and in some jurisdictions additional deposit information may be required because of Travel Rule obligations.
For beginners, the practical rule is simple:
minutes can be normal, hours can still be normal, but days require deeper checking.
If your Crypto.com crypto was sent but has not arrived, use this action plan:
Identify the transfer type clearly
Say whether this was an app-based Send transfer or an onchain wallet transfer. That changes the whole troubleshooting path.
Verify the destination one more time
Check the exact phone number, email, wallet address, network, and any memo/tag. Crypto.com specifically says recipients should confirm the sender used the correct phone number or email address.
Pull the blockchain evidence
If it was onchain, get the TxHash and inspect it on the relevant blockchain explorer. Crypto.com says that is how you confirm status and confirmations.
Ask the recipient the right questions
Are they checking the correct account? The correct network? The correct asset view? Have they received any pending deposit notice? These are logical next checks based on Crypto.com’s guidance around confirmations and deposit processing.
Wait through the normal window when appropriate
If the transfer is still pending and within the expected time frame, patience may be the correct move. Crypto.com notes that the timing depends on confirmations, fee choice, and network traffic.
Prepare a support-ready summary
Collect the amount, asset, TxHash, date, network, recipient detail, and screenshots.
Use the official platform support path for account-specific review
Once you have the facts, use Crypto.com’s official help route for case-specific handling. A structured report is far more useful than a vague complaint.
Do not trust anyone who says they can manually “release” your Crypto.com transfer if you pay them, connect your wallet, or share sensitive credentials.
Be suspicious of anyone asking for:
your recovery phrase
your private keys
remote access to your device
a second transfer to “activate” the first one
an approval signature on a random wallet site
fees paid to a stranger for “recovery” help
Crypto.com’s official help guidance focuses on transaction history, account access, correct recipient details, TxHash checks, and explorer verification. Real troubleshooting starts there.
Usually because the transfer is still pending, the recipient has not claimed it, or the receiving side is waiting for confirmations or crediting. Crypto.com documents all of those possibilities across its Send and deposit help pages.
Yes. Crypto.com says onchain transactions can be successfully submitted and still remain pending until confirmations are received, and deposits can remain pending until required confirmations are reached.
Check the transaction history and retrieve the TxHash if it was onchain. Crypto.com says the TxHash can be pasted into the relevant blockchain explorer to confirm status and confirmations.
Crypto.com says a Send transfer to a non-user can remain pending for up to seven days while they sign up and claim it. If not claimed in time, the transfer is canceled and the funds are returned.
Then the next checks are the destination details, network used, token support, and whether the receiving side is still waiting to process the deposit. That conclusion follows directly from Crypto.com’s guidance on confirmations, deposits, and correct destination details.
A crypto.com crypto sent but not arrived problem usually looks worse than it is. In many cases, the transfer is delayed, pending, unclaimed, or waiting to be credited rather than permanently lost. The best beginner response is not to panic and not to resend right away. Identify the transfer type first, then verify the destination details, check the transaction status, and use the TxHash if the transfer was onchain. Crypto.com’s own help guidance supports that exact workflow.
If the transaction is beyond the normal window or the blockchain record and recipient view do not match, gather your screenshots and transaction details and move to the official support path for account-specific review. Calm verification is what solves these cases fastest.
John M., Independent Fintech Support Researcher
This article is for educational purposes only. There is no affiliation with Crypto.com or any named company/property, and no user accounts can be accessed.