If your Crypto.com send is stuck on pending, ⏳+1 877➥719➥1076 that does not automatically mean your crypto is lost. In many beginner cases, the transfer is still waiting for one of two things: either the recipient has not completed the required step yet, or the blockchain transaction has not finished confirming. Crypto.com says transfers sent through Crypto.com Send to non-users can remain pending for up to 7 days while the recipient signs up and claims the transfer. For onchain transactions, Crypto.com says a transfer remains pending until at least one confirmation is received, and some transactions can stay pending for 2 to 3 days during congestion or when a lower fee setting was selected. (help.crypto.com)
The safest response is to stop before resending. First identify whether this is an internal Crypto.com Send transfer or an onchain transfer to a wallet address. Then verify the recipient details, transaction status, network, and TxHash if one exists. That verification-first approach usually shows whether the issue is timing, claim status, network delay, or a destination mismatch. (help.crypto.com)
Before trying any workaround, do these checks in order:
Identify the transfer type.
Was this a Crypto.com Send transfer to a person inside the app, or an onchain send to an external wallet or exchange address? Crypto.com treats these flows differently. (help.crypto.com)
Check the exact status shown in transaction history.
Crypto.com says users should check the transaction history and confirm whether the transfer is marked Processed or still Pending. (help.crypto.com)
If this was sent to a person, verify the recipient details.
Crypto.com says users should confirm that the correct phone number or email was used and make sure the recipient has access to the correct Crypto.com account. (help.crypto.com)
If this was onchain, find the TxHash and open the blockchain explorer.
Crypto.com says users should check the explorer to see whether the transfer is pending, confirmed, or failed and how many confirmations it has. (help.crypto.com)
Refresh the wallet or app view.
Crypto.com says users can refresh the wallet home screen to sync the latest balances and transaction status. (help.crypto.com)
Do not send the funds again yet.
A pending transfer can still complete later. Sending again too early can turn one unresolved transfer into two completed transfers. This is the safest practical conclusion from Crypto.com’s published pending and confirmation guidance. (help.crypto.com)
A pending status can look scary, but it usually means the transaction is waiting for one specific step, not that the funds have disappeared.
This is one of the most common reasons for a Crypto.com Send transfer to stay pending.
Crypto.com says that if you transfer crypto to someone who is not yet a Crypto.com App user, the transfer can remain pending for up to 7 days so the recipient has time to sign up and claim it. If they do not claim it within that time, the transfer is canceled and the funds are returned. (help.crypto.com)
For beginners, this matters a lot. A pending transfer to a person is often not a blockchain problem at all. It is simply a claim-status problem.
For onchain sends, Crypto.com says a transaction remains pending until at least one confirmation is received. Confirmation time depends on network traffic, the blockchain itself, and the selected fee tier. Crypto.com’s guide gives estimated first-confirmation times such as 10 / 30 / 60 minutes for BTC and 30 seconds / 2 minutes / 30 minutes for ETH/ERC-20, depending on the fee setting, but these are only estimates. (help.crypto.com)
That means a pending send can simply mean the network has not processed it fully yet.
Crypto.com says some pending transactions can remain stuck for 2 to 3 days during heavy congestion or when a lower fee setting was selected, and these transactions may never confirm. (help.crypto.com)
This is especially important for beginners because the interface may just say “pending,” while the real issue is a blockchain fee and timing problem.
Crypto.com says incoming blockchain funds are updated after confirmation and that deposit crediting can depend on network-specific confirmation thresholds. It also says users may see a pending deposit notice after the first block confirmation while the system waits for the required number of confirmations. (help.crypto.com)
So a send can be pending from the recipient’s perspective even when the blockchain has already started processing it.
Crypto.com says that if the on-chain status is successful or completed, users should double-check the wallet address details. It also says missing or incorrect memo/tag entries can require manual recovery and may not always be recoverable. (help.crypto.com)
This means some transfers that look “stuck on pending” may really be destination-detail issues.
This is not unusual. The recipient may be:
checking the wrong wallet section
checking the wrong account
expecting instant deposit credit before confirmation requirements are met
looking at the wrong chain or asset view
This is a reasonable inference from Crypto.com’s guidance around recipient account access, correct details, explorer status, and deposit confirmation rules. (help.crypto.com)
Many users say “stuck” when a transaction is still within a normal pending window. Crypto.com’s own help material makes clear that pending time varies by transfer type, network conditions, and whether the recipient must claim the transfer. (help.crypto.com)
That does not mean every pending transfer is normal, but it does mean you should compare the elapsed time with the actual transfer type before assuming something broke.
If this was Crypto.com Send to a non-user, Crypto.com says the transfer can remain pending for up to 7 days while they sign up and claim it. (help.crypto.com)
That means “pending all day” may still be completely normal in that case.
That usually points to an onchain transfer. Crypto.com says onchain transactions remain pending until at least one confirmation arrives, and the explorer should be checked first. (help.crypto.com)
The first high-value check here is the TxHash, not the wallet screenshot.
That usually means the transaction has been broadcast, but it is still in the confirmation phase. Crypto.com says users should wait for confirmations and use the explorer as their source of truth for onchain status. (help.crypto.com)
Maybe, but not always. If it was Crypto.com Send, the recipient may be checking the wrong account or may not have completed the needed step yet. Crypto.com says to verify the correct email or phone number and ensure the recipient has account access. (help.crypto.com)
That can happen during congestion. Crypto.com says some pending transactions may remain stuck for 2 to 3 days and never confirm when fee conditions are poor or the network is very busy. (help.crypto.com)
At that point, you should move from waiting to evidence gathering.
This is exactly when duplicate transfer mistakes happen. A pending transfer can still finish later. Sending again before understanding the first transfer is one of the most common and costly beginner errors.
Use this checklist before escalating:
Confirm the exact asset sent
Confirm the exact amount
Confirm the exact date and time
Confirm whether the transfer was Crypto.com Send or onchain
Check the exact transaction status
Verify the recipient email or phone if it was Send
Verify the destination wallet address if it was onchain
Check whether the correct network was used
Check whether a memo or tag was required
Find the TxHash if one exists
Open the correct blockchain explorer
Check whether the transaction is pending, confirmed, or failed
Count the confirmations shown
Ask the recipient what wallet or exchange they are checking
Ask whether they see a pending deposit notice
Refresh both sender and receiver app views
Save screenshots before taking any new step
These checks follow Crypto.com’s guidance on transaction history, recipient verification, explorer review, and deposit confirmation rules. (help.crypto.com)
Step 1: Was it Crypto.com Send or onchain?
Crypto.com Send:
Focus on recipient account access, claim status, and correct email/phone. Crypto.com says non-user recipients can leave the transfer pending for up to 7 days. (help.crypto.com)
Onchain transfer:
Focus on TxHash, confirmation count, fee conditions, and destination details. Crypto.com says onchain sends remain pending until the first confirmation. (help.crypto.com)
Step 2: What does the explorer or status show?
Pending or unconfirmed:
The transfer may still complete normally. (help.crypto.com)
Successful or completed onchain:
Now check destination details and receiving-side crediting. (help.crypto.com)
Failed:
Treat it as a sending-side issue first. (help.crypto.com)
Step 3: Is the recipient or destination verified?
No or unsure:
Reconfirm the correct phone/email, wallet address, network, and any memo/tag. (help.crypto.com)
Yes:
Continue to timing and receiving-platform checks.
Step 4: Has enough time passed for this transfer type?
No:
It may still be within a normal pending window.
Yes:
Gather evidence and move toward official support review.
Send to person is still pending
Likely cause: Recipient has not claimed or accessed the account
What to check first: Correct email/phone and recipient account access
Best next step: Wait within the 7-day claim window or verify recipient setup
On-chain send pending with TxHash
Likely cause: Waiting for the first confirmation
What to check first: Explorer status and confirmation count
Best next step: Monitor confirmations
Pending much longer than expected
Likely cause: Network congestion or low fee setting
What to check first: How long it has been pending
Best next step: Gather records and keep monitoring for a stuck status
Sender sees pending, recipient sees nothing
Likely cause: Deposit not yet credited or recipient checking the wrong place
What to check first: Recipient wallet/exchange view
Best next step: Check pending deposit notices and the correct account section
Explorer shows success but app still says pending
Likely cause: Receiving-side processing or wrong destination details
What to check first: Address, network, and memo/tag
Best next step: Verify destination details and deposit rules
User wants to resend immediately
Likely cause: Panic response
What to check first: Whether the first transfer may still complete
Best next step: Do not resend until the first transfer is fully understood
There is no single answer because pending timing depends on the type of send. (help.crypto.com)
Crypto.com says:
transfers to eligible Crypto.com App users are processed instantly
transfers to non-users can remain pending for up to 7 days while they sign up and claim the transfer
if unclaimed after that window, the transfer is canceled and the funds are returned (help.crypto.com)
Crypto.com says onchain transactions stay pending until at least one confirmation is received. It gives estimated first-confirmation times such as:
BTC: about 10 / 30 / 60 minutes depending on fee tier
ETH / ERC-20: about 30 seconds / 2 minutes / 30 minutes depending on fee tier
Crypto.com also says some pending transactions may remain stuck for 2 to 3 days in congestion or low-fee conditions. (help.crypto.com)
Crypto.com says incoming funds may appear only after confirmation and that some deposits need a specific number of confirmations before they are credited. (help.crypto.com)
For beginners, the practical rule is:
Minutes can be normal
Hours can still be normal
Days may happen in edge cases
Up to 7 days can still be normal for unclaimed Send transfers to non-users (help.crypto.com)
If your Crypto.com send is still stuck on pending, follow this action plan.
This is the first big distinction. If it was Crypto.com Send, pending may mean the recipient has not claimed the transfer yet. If it was onchain, pending usually means the blockchain has not confirmed it yet. (help.crypto.com)
Crypto.com says users should check the blockchain explorer to see whether the transaction is pending, successful, or failed. (help.crypto.com)
That gives you objective evidence instead of guessing based on app labels alone.
Check:
recipient email or phone
wallet address
network
memo/tag
destination platform support
Crypto.com repeatedly points users back to correct recipient details and correct deposit details when troubleshooting missing or delayed transfers. (help.crypto.com)
Instead of only asking “Did you get it?”, ask:
Are you checking the correct account?
Are you using the right email/phone?
Do you see a pending deposit notice?
Are you checking the correct wallet section?
Does your platform support this asset on this network?
These are the kinds of checks Crypto.com’s help guidance implies through its recipient-access and deposit-confirmation rules. (help.crypto.com)
Before opening support, collect:
asset
amount
date/time
status shown
recipient detail used
network
TxHash
explorer screenshots
recipient screenshots if available
This makes the official support path much more effective.
Crypto.com says users should verify communications through Crypto.com Verify and avoid suspicious channels. (help.crypto.com)
A pending-transaction problem is exactly when scammers try to exploit stress. Crypto.com says users should verify that communications are official through Crypto.com Verify and avoid engaging with suspicious channels. (help.crypto.com)
Do not trust anyone who asks you to:
share your seed phrase
reveal private keys
connect your wallet to a random website
send another transfer to “unstick” the first one
pay a stranger for “manual recovery”
install remote-access software
A real pending-transfer review starts with transaction history, explorer checks, destination verification, and official support paths only. (help.crypto.com)
Usually because the recipient has not claimed the transfer yet, or because the blockchain transaction is still waiting for confirmations. Crypto.com says non-user Send transfers can remain pending up to 7 days, and onchain transfers stay pending until at least one confirmation is received. (help.crypto.com)
It depends on the transfer type. Crypto.com says Send transfers to non-users can stay pending up to 7 days, while onchain transactions may remain pending for minutes, hours, or even 2 to 3 days in congestion cases. (help.crypto.com)
No. Not until you confirm the first transfer’s real status. Sending again too quickly can create a duplicate transfer.
That is usually normal. It means the blockchain has not fully confirmed the transaction yet, so the receiving side may not display or credit it. (help.crypto.com)
Crypto.com says you should check the correct phone number or email and make sure the recipient has access to the correct account. (help.crypto.com)
Yes. Crypto.com says some onchain transactions may remain pending for 2 to 3 days in congestion or with a low fee setting. (help.crypto.com)
A crypto.com send stuck on pending issue usually comes down to one of four things: the recipient has not claimed the transfer yet, the blockchain has not confirmed it yet, the destination details need correction, or the receiving side has not fully credited it yet. Crypto.com’s own help articles point users back to the same core checks every time: identify the transfer type, review transaction history, use the blockchain explorer, verify the recipient or destination details, and understand the confirmation rules of the receiving side. (help.crypto.com)
For beginners, the safest next move is calm verification, not a second send. Gather the status details, check the TxHash if it was onchain, confirm the recipient detail if it was app-based, and move through official Crypto.com channels only if you need case-specific help. (help.crypto.com)
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.