Crypto withdrawal on hold: what to check with no transaction ID
Find out whether your withdrawal request was submitted, needs confirmation or is still with the provider. Check the right record before blaming the blockchain.
In this guide · 13 sections
- Identify what you are trying to withdraw
- Find the request before looking for a transaction hash
- Read the status using that provider’s definitions
- Check confirmations without approving an unfamiliar withdrawal
- Compare your total balance with funds available to send
- Distinguish a timed security hold from a manual review
- Check the correct status page and the correct clock
- Know when no public blockchain transaction is expected
- If the request failed or was cancelled, verify the outcome before retrying
- Ask support the question that identifies the missing stage
- Know when to switch from waiting to fraud or account security help
- When a hash appears, move to the right next guide
- Questions about withdrawals with no transaction ID
If your crypto withdrawal is pending with no transaction ID, start in the sending account. Find the withdrawal request, read its exact status and check whether the provider is waiting for a confirmation, available funds or an internal review. Do not submit the withdrawal again just because you cannot find a hash. First establish whether the original request is still active and whether it has reached the network.
A missing transaction ID is an incomplete piece of evidence. It does not prove that the provider is a scam, that the money has been sent, or that you can safely cancel and retry. The provider may not yet have broadcast the transaction; the interface may not expose the hash where you are looking; or you may be checking a transfer type that has no individual public blockchain transaction. Those possibilities need different next steps.
This guide is for the stage before you have a verified blockchain record for your withdrawal. If you already have a hash and the correct network, use our guide to block explorers, confirmations and fees. If your problem is a Canadian dollar deposit into an exchange, start with the Interac and crypto funding guide for Canada. A bank funding reference is not the hash of a later crypto withdrawal.
Official documentation was checked on October 22, 2026. Platform examples explain named products and interfaces; they are not claims that every service, payment method or feature is available to every Canadian customer. All scenarios and record keeping examples below are hypothetical. We did not perform a withdrawal test, contact a provider about a real account or measure processing times for this guide.
Identify what you are trying to withdraw
First establish whether you requested an external crypto transfer, an internal platform transfer or a cash withdrawal to a bank. The word “withdrawal” can appear in several processes, but it does not make their references interchangeable. Write down the product you used, the asset and the destination type before searching an explorer. That small classification step prevents several common dead ends.
| Transfer you requested | Record to look for first | What not to assume |
|---|---|---|
| Crypto to an external address | Crypto withdrawal history and selected network | That pressing Send proves broadcast |
| Crypto to another user inside a platform | Internal transfer record and recipient identifier | That an individual public transaction must exist |
| Cash to your bank after selling crypto | Cash withdrawal record and bank destination | That the bank payment has a crypto transaction hash |
| Canadian dollars into an exchange | Bank funding record and exchange deposit record | That the issue is a crypto withdrawal |
| Transfer from a wallet you control | Wallet activity and chosen payment method | That exchange account instructions apply |
Name the destination carefully. “My wallet” could mean an external address you control, an exchange deposit account or another balance inside the same application. Those are different receiving arrangements. In your notes, describe what you entered: an address and network, an email or username, a bank account, or another identifier. You do not need to publish that identifier to make the distinction.
If another person says they sent money to you, ask for the sending service, transfer type, selected network where applicable and the actual payment record. You may have no access to their withdrawal history yourself. A screenshot reading “processing” gives you something to discuss with the sender, but it is not independent proof of broadcast or proof that the destination account should already be credited.
Find the request before looking for a transaction hash
Open the withdrawal or transaction history in the genuine sending application. Look for the specific asset, amount, destination and submission time. Keep the provider’s internal withdrawal reference, even if there is no blockchain hash. That reference can help its support team identify the request; it simply serves a different purpose from a public network transaction identifier.
Check whether you reached the final submission step. A quote, preview screen or address confirmation may precede the actual withdrawal request. A browser closing after you pressed a button leaves uncertainty that the account history should resolve. Do not infer success from the amount you typed, or failure from the absence of an immediate confirmation email. Record what the account actually shows now.
Request received and funds sent are different events
Crypto.com’s withdrawal documentation distinguishes a request confirmation from a later processing notification. Its help page also explains where to open transaction details and locate the hash. This distinction matters: a message acknowledging a request answers whether the service received an instruction, while the transaction record answers what happened to that instruction afterwards.
For your own timeline, use separate entries for “request created,” “confirmation completed” and “hash first displayed.” Leave an event unknown if you cannot establish it. An email timestamp may be useful, but it does not necessarily equal the moment of broadcast. If two records appear to disagree, preserve both instead of changing one into a more convenient interpretation.
What if there is no request in the history?
Check that you are in the correct product, account and history filter. A platform may have separate views for cash, crypto, trades and transfers. Clear a date or asset filter if needed, and compare the website and app only through the provider’s genuine access routes. Do not install an unofficial “transaction finder” to compensate for a missing record.
If you still cannot locate the request, ask support whether it exists before creating another. Include the approximate time, asset, quantity and the point where the process stopped. For example, “I completed the review screen, the page closed, and I cannot see a withdrawal in my account history” is more actionable than “my transaction vanished.” It describes the evidence without assuming that a network transaction ever existed.
- No request recordAsk the sending provider whether an instruction was submitted.
- Request, no visible hashCheck confirmation and holds; ask whether broadcast occurred.
- Verified network recordRead the transaction result, then investigate receiving requirements if needed.
Read the status using that provider’s definitions
Use the status definitions for the exact service and interface you are using. “Pending” is not a universal blockchain term when it appears in an exchange account. It may describe an internal request stage, an action you still need to complete, or a transaction already being processed. Copy the wording before interpreting it, especially if another application translates or groups statuses differently.
Kraken’s Classic withdrawal status guide makes the distinction explicit. “Initiated” concerns internal checks; “Pending” means the request has reached its payment gateway; “Sending” means broadcast to the network. Its “On hold” status requires manual review. These definitions belong to the documented Classic interface. Do not automatically apply them to a different provider’s screen.
By comparison, Bitpanda’s incomplete transaction guide uses “Pending” for a withdrawal not yet confirmed by email. This is a useful terminology example, not a recommendation of Bitpanda for Canadian readers. The same visible word can point to a different action, which is why reading the named provider’s help page is more reliable than applying a general internet waiting period.
Record uncertainty instead of filling it in
Use statements such as “the app shows pending and I cannot see a hash” rather than “the blockchain has been processing my payment all day.” The first sentence states what you know. The second assumes a processing stage. Support can investigate the missing fact more efficiently when the question is whether the request was broadcast, not a conclusion that the network is responsible.
If the app says completed but the detail screen lacks a hash, capture both. Ask whether “completed” refers to an internal transfer, request handling or a network transaction. Do not make a payment to unlock extra transaction information. A legitimate question about a missing reference should be resolved through the provider’s existing account and support process, not a new wallet connected through an unsolicited message.
Check confirmations without approving an unfamiliar withdrawal
Check for a required email, passkey or authentication step in the genuine account. Complete it only if the request is yours and the asset, quantity, destination and network match what you intended. A reminder arriving while you are troubleshooting is not automatically trustworthy. If you see a withdrawal or address change you did not request, switch from routine troubleshooting to the provider’s account security process.
Use a deliberate comparison before approving anything: the request in the app, the details you intended and the confirmation being requested. If one differs, stop and resolve the difference. This is particularly important when you tried several addresses or networks while preparing a withdrawal. An older confirmation can refer to a different request from the one currently on your screen.
Confirmation emails that do not arrive
Check the account’s registered email address and ordinary spam or filtered folders. Follow the provider’s documented resend process if one exists. Do not keep restarting the entire withdrawal merely to generate another email. Ask whether the original request remains active and which confirmation relates to it. Keep the request time and any resend time separate in your notes.
If you cannot access the registered email account, use the provider’s official recovery route. Do not ask a third party to receive authentication codes for you or provide remote access so it can “finish” the withdrawal. Account recovery and withdrawal approval are different tasks. Recovering secure access should not require handing another person the credentials used to authorise a transfer.
After you complete a valid confirmation, revisit the existing request rather than assuming immediate broadcast. Note its new status and any message about processing. A completed authentication step shows that one requirement was satisfied. It does not settle whether funds are available, an account review remains open, the network is operational or the recipient supports the selected transfer.
Compare your total balance with funds available to send
Look at the balance available for the specific withdrawal, not only the portfolio total. A platform can display assets that are not currently transferable because of a funding hold, an open order or another product restriction. A Canadian dollar valuation of your holdings is also not the same as the quantity of one asset available to withdraw.
Coinbase’s available balance guidance explains that crypto purchased with held cash may be tradable inside the platform while unavailable to send until the hold clears. That is a product rule, not evidence of a blockchain delay. Use the availability information attached to your own transaction and account rather than assuming a trading balance is a withdrawal balance.
Wealthsimple’s external crypto withdrawal instructions also distinguish funding settlement from sending crypto and describe withdrawal requirements. Check the rules for your actual funding method and account. Do not take a period mentioned for one deposit method, count it from a different event, and treat the resulting date as a guarantee for every withdrawal.
Check quantity, currency and reserved funds separately
In a hypothetical example, an account shows C$1,200 of total holdings, but the intended withdrawal is BTC. The total may include several assets and cash. It does not establish that C$1,200 worth of BTC can be withdrawn. Read the BTC quantity, the amount available for that withdrawal, the displayed fee and any relevant minimum separately, preserving the exact units rather than converting everything mentally.
Kraken’s withdrawal troubleshooting page identifies open or pending orders as one reason funds may be unavailable. Before changing an order, understand which funds it reserves and what cancelling it would do. This guide is not a reason to close an investment position or rearrange trades blindly. The useful first action is identifying the restriction, then deciding whether the provider’s available options fit your intention.
If the available amount looks inconsistent, take a record of the specific withdrawal screen and ask support to explain it. Include the asset, amount you attempted, displayed available quantity and exact error. Avoid sending a full account export when a smaller, redacted record answers the question. The support issue is the missing explanation of availability, not a request to expose every holding publicly.
Distinguish a timed security hold from a manual review
A timed hold and a manual review need different follow up. A timed hold may show an expiry event or date. A manual review may depend on information from you or a decision by the provider. Do not invent a countdown for a review simply because another customer reports that theirs finished within a certain number of hours.
Kraken’s hold documentation distinguishes automatic releases from cases requiring manual review. It also describes how changes such as a password update can affect withdrawals to new addresses. Preserve the exact notice and identify the relevant event in your own account. A security change, deposit settlement and account review can involve separate conditions.
Newly added or changed withdrawal addresses
Check whether you added the destination recently and whether an address protection feature applies. Crypto.com’s official withdrawal guide states that a newly added address has a 24 hour withdrawal lock if that feature is enabled. The condition matters. Do not describe the rule as an unavoidable hold on every Crypto.com withdrawal, and do not assume another provider uses the same setting or duration.
Record the address addition time, the time zone shown and the wording of any release notice. An email arriving at one time and an address becoming active at another are not necessarily contradictory if they describe different steps. If the provider displays an exact release time, keep that record. If it displays only a date, ask about the applicable time zone instead of assuming midnight where you live.
Identity checks and account restrictions
Kraken’s account restriction guidance explains that security and compliance reviews can restrict funding functions and may involve requests for additional information. It also states that Kraken will not request login credentials or remote access by phone or email. Verify any document request through the genuine account or independently reached support before uploading information.
Respond truthfully to a genuine review request using its designated secure process. Do not split transactions, use someone else’s account or change the story of the transfer to get around a restriction. Those actions do not answer why the original request is held and can create more uncertainty. Ask what information remains outstanding and whether the request is waiting on your response or on the provider’s review.
Check the correct status page and the correct clock
Check the sending provider’s official status page for the actual asset, network and product involved. A trading outage, deposit pause and withdrawal delay are different incidents. The Kraken status page, for example, lists service components and incident updates. A status page is useful operational context, but it cannot prove the reason for a restriction on your individual account.
Read the incident’s scope and timestamps, not only its headline. An Ethereum withdrawal incident does not automatically explain a Bitcoin request. A resolved service incident also does not establish that every earlier request has already completed. Compare the provider’s follow up instructions with the status of your own request and ask about the remaining discrepancy if there is one.
Measure from the event the provider names
Write down which clock applies: time since the request was submitted, time since you confirmed it, time since an address was approved, or time since funding began its settlement period. “I have been waiting two days” is understandable but incomplete if one of those steps happened only recently. A short timeline lets you explain the delay without assuming that all clocks started together.
For example, a hypothetical reader prepares a withdrawal on Monday, confirms it on Tuesday and adds a different receiving address on Wednesday. They should not describe Wednesday’s new address as having completed every condition since Monday. Equally, they should not let a provider treat an old unanswered support request as new without acknowledging the earlier record. Keep the dates of both the transaction and the support conversation.
Do not borrow another platform’s processing estimate. A help article can describe an ordinary range, an escalation threshold or a fixed security rule, and those statements mean different things. This guide deliberately gives no universal “safe after this many hours” verdict. Follow the current instructions for the specific request, and contact support when the stated next step is missing, an applicable period has passed or account security is in question.
Know when no public blockchain transaction is expected
Some transfers do not create a separate public blockchain transaction between the sender and recipient. Coinbase’s sending documentation distinguishes external transfers from internal transfers to other Coinbase users using supported identifiers. It states that those internal transfers do not appear on the blockchain. Searching a public explorer cannot substitute for checking the provider’s internal transfer record.
This does not mean every transfer between customers of the same brand is internal. The route selected matters. If you entered an external deposit address and chose a blockchain, ask the provider which transfer mechanism it actually used. A familiar recipient name does not answer that question. Keep the sender’s transaction type and the receiving product clear in the support request.
Cash withdrawals and payment references
If you sold crypto and requested Canadian dollars to a bank, locate the cash withdrawal record. The sale, the cash balance and the bank payment are separate events. A trading order identifier can show which sale occurred without being a bank payment reference. Do not search it on a Bitcoin explorer or assume the absence of a crypto hash means the bank transfer is fraudulent.
If you used a service that combines a crypto payment and a bank payout, identify each leg separately. Ask which leg is pending and which organisation controls it. The crypto transfer may have a network record while the later bank payout has a different reference. Your evidence should not collapse both legs into one status, especially when one has completed and the other has not.
Lightning uses a different payment record
Bitcoin sent through Lightning uses a different payment process from a conventional Bitcoin blockchain transfer. Coinbase’s Lightning documentation describes invoice based payments outside the blockchain and, at our check date, explicitly states that its Lightning service is unavailable in Canada. Do not follow its setup instructions as though the feature were offered to a Canadian account.
If another service shows Lightning as the method you actually used, follow that service’s official invoice and payment troubleshooting. Preserve the payment record rather than pasting an invoice into an ordinary Bitcoin transaction search and treating no result as proof of loss. The general lesson is to identify the payment mechanism first, including whether the method was genuinely available for the account and destination involved.
If the request failed or was cancelled, verify the outcome before retrying
A failed or cancelled withdrawal request needs an account level check before another attempt. Read the reason, determine whether the original request is inactive and confirm what happened to the amount reserved for it. Do not assume that a screen returning to the withdrawal form proves that the previous request was cancelled. Likewise, a cancellation button being pressed is not proof that the cancellation succeeded.
Kraken’s Classic status documentation says cancellation can be requested only during its Initiated and Pending stages, and warns that a request while Pending is not guaranteed to cancel the withdrawal. That qualification matters even when you cannot see a hash. A process can move while you are viewing the screen. Follow the current status and support response instead of treating your last click as the final outcome.
A cancellation request is an instruction, not a receipt
Keep a record of when you requested cancellation and what confirmation you received. If the account still shows processing, ask whether cancellation remains pending or the withdrawal has moved beyond the cancellable stage. Avoid submitting a replacement withdrawal until you understand the first request’s outcome. Otherwise you may turn a single uncertain payment into two potentially valid instructions.
If the failure message concerns address format, network support, minimum amount or another input, correct the actual cause before trying again. Do not choose a different network solely to make the error disappear. The recipient must support the selected asset and network. If the intended receiving details have changed, obtain fresh instructions from the recipient through a trusted route and compare the full details.
Check the balance and any fee separately
After a final failed or cancelled status, check the available asset quantity and the provider’s treatment of any fee. Do not invent a refund amount from the original preview. Preserve the history entry and ask about a discrepancy if the available amount does not match the outcome described. If the request was already broadcast, a subsequent network failure can have different fee consequences from a request rejected internally.
This article does not offer a generic cancel, replace or fee bump instruction. Those actions depend on the actual transaction state and on who controls the sending account or wallet. An exchange customer generally cannot repair the provider’s internal review by changing a network fee in an unrelated wallet. Establish the stage first, then follow the process that applies to that stage.
Ask support the question that identifies the missing stage
Ask the sending provider whether the specific withdrawal was submitted to the network and what currently prevents completion if it was not. Give the internal request reference rather than inventing a hash. If the transfer is internal or a bank payout, say that explicitly and ask for the corresponding transfer status. A useful support question narrows the uncertainty instead of assuming the cause.
Prepare one concise record containing the product, asset, quantity, selected network if applicable, destination type, submission time and time zone, exact status and any error. State that no transaction hash is visible and where you looked. Include completed confirmation steps and the wording of any hold notice. Share the actual recipient or reference only through the provider’s appropriate secure channel.
Suggested wording for a request with no hash
You can write: “My withdrawal request is still shown as processing, and I cannot locate a blockchain transaction hash in its detail screen. Please confirm whether it has been broadcast, identify any action required from me and explain the next step. If it was broadcast, please provide the network and transaction reference. If it is an internal transfer, please confirm that transfer type.” Replace the observations with what your account actually shows.
Follow with the request reference and relevant dates. Do not attach passwords, authentication codes, recovery words or private keys. A provider can locate its own withdrawal using account and transaction information through its normal support process. An unsolicited helper requesting secret access is creating a new security problem, not explaining why the original request lacks a transaction ID.
If the first reply gives only a general processing estimate, ask which state your specific request is in and whether anything is outstanding. Keep that follow up in the same case where possible so the history remains understandable. Record promised follow up dates as statements from support, not as guarantees this publication can validate. Escalate through the provider’s documented process when the matter remains unresolved.
These are investigation paths, not a diagnosis of your account. A claim of broadcast still needs a matching transaction record; an internal transfer needs the correct provider record.
Know when to switch from waiting to fraud or account security help
A missing hash alone is not a fraud verdict. A demand for a new payment to unlock a disputed balance, an unsolicited recovery offer or a request for secret account access raises a different question. Stop treating that interaction as ordinary transaction troubleshooting and verify who is contacting you. You can investigate the withdrawal and protect your account at the same time.
The Canadian Anti Fraud Centre’s investment fraud guidance warns about fake crypto websites and recovery pitches that request fees or remote access. Reach the genuine provider independently, especially if a search result or social message presents itself as urgent support. A page appearing for a withdrawal query does not establish that it belongs to your provider.
Keep a published withdrawal fee distinct from a new request to pay a stranger. A fee shown in the genuine withdrawal flow is not the same thing as a chat instruction to transfer crypto to a new address to “activate” release. Compare the request with official documentation and your account. If you cannot verify it, pause rather than paying to find out whether the explanation is true.
Use our fake platform and withdrawal scam guide when the balance itself or the release demand is in doubt. If money was sent or access exposed, the after scam response guide for Canada separates provider contact, account protection and reporting. Preserve the exact demand and existing transaction records; do not continue paying to produce a more convincing evidence trail.
When a hash appears, move to the right next guide
Once a transaction hash is available, verify that it belongs to the intended transfer on the correct network. A hash is an identifier, not a promise that the transaction succeeded or that the receiving account has been credited. Ethereum’s explorer documentation explains the different transaction fields and results available to inspect. Keep the outcome separate from the mere existence of the identifier.
Coinbase’s transaction hash help describes where to find an explorer link and emphasizes using the correct network. If the provided link opens no matching result, check the selected network and complete identifier before drawing a conclusion. Do not connect a wallet or sign a message merely to read a public transaction record.
For pending network transactions, continue with the explorer, confirmations and fees guide. If the record shows a transfer but the receiving balance is missing, compare the recipient’s supported asset, network and reference requirements. Coinbase’s send and receive troubleshooting likewise separates sender details from receiving requirements.
If the actual network, destination or memo does not match the receiving instructions, use our wrong network and missing memo guide. Do not keep treating that situation as an unbroadcast request. The useful question has changed from “did the provider send it?” to “what happened on the selected network, and can the receiving party investigate or credit this transfer?”
Questions about withdrawals with no transaction ID
Does no transaction ID mean the exchange has not sent my crypto?
Not necessarily. It means you do not yet have a visible network reference for that transfer. Check the transaction detail screen and transfer type, then ask the provider whether broadcast occurred. An internal transfer may not have an individual public blockchain record. Do not substitute an assumption for the provider’s actual status and evidence.
Can I cancel because the transaction is not in an explorer?
An empty explorer search does not establish that cancellation is available. You may have the wrong network, an internal reference or incomplete information. Cancellation depends on the provider and current request state, and a cancellation request can fail if processing has advanced. Obtain the final outcome before submitting a replacement withdrawal.
Should I pay more gas to speed up an exchange withdrawal?
A separate gas payment does not resolve an exchange’s internal verification or funding hold. First establish whether a network transaction exists and who controls its submission. If you use a wallet you control and have a pending transaction, follow that wallet’s official guidance. Do not send crypto to unsolicited support as a supposed acceleration charge.
Why can I trade the crypto but not withdraw it?
Trading availability and withdrawal availability can differ under a provider’s funding or security rules. Check the available balance for the specific send and the notice attached to any hold. Do not assume a successful trade proves that funds have completed every requirement for an external transfer. Ask support to explain the specific restriction if the account does not make it clear.
Is a withdrawal ID the same as a TXID?
Not always. A provider can assign an internal identifier to a withdrawal request before a public transaction is available. Preserve the internal identifier for support, and ask separately for the network transaction hash if the transfer used a blockchain. The label and context matter more than whether the reference looks long or technical.
How long should I wait before contacting support?
Use the current instructions for your provider, transfer method and account status rather than a universal hour count. Contact support when an applicable period has passed, the next required action is unclear or the request and balance disagree. For an unauthorised request or suspicious access, use the account security route promptly instead of waiting for routine processing.
Sources and further reading
- Kraken: Cryptocurrency withdrawal statuses, Classic interface
- Kraken: Unable to withdraw funds
- Kraken: Why a deposit or withdrawal is on hold
- Kraken: Account restrictions
- Crypto.com: Crypto withdrawal process and transaction ID
- Wealthsimple: Withdraw crypto to an external wallet
- Coinbase: Understand your available balance
- Coinbase: Steps to send crypto, including internal transfers
- Coinbase: Bitcoin Lightning and geographic availability
- Coinbase: Locate a transaction hash
- Coinbase: Send and receive troubleshooting
- Bitpanda: Incomplete cryptocurrency deposits and withdrawals
- Ethereum: Block explorers
- Kraken: Official service status
- Canadian Anti Fraud Centre: Investment and recovery fraud