Crypto Deposit Not Showing on Exchange: Follow the Evidence Ladder

A zero exchange balance does not identify the failure. The sender may not have broadcast anything, the transaction may still be waiting on-chain, the exchange may require more confirmations, or the blockchain payment may have reached an address that the exchange cannot automatically assign to your account. Even a technically correct deposit can remain unavailable while the exchange performs wallet maintenance, account screening or a Travel Rule check. Treat the transfer as a chain of evidence rather than one status label. The Exchange Deposit Evidence Ladder starts with the sender’s record, moves through the correct block explorer and deposit route, and ends at the exchange’s internal ledger. The first missing piece tells you who controls the next action and which specialist guide you actually need.

The fastest useful diagnosis

Find the transaction ID in the sender’s history and open it in the explorer for the network actually used. If no transaction exists, the sender still controls the problem. If it is pending, the blockchain controls the wait. If it is successful but lacks the exchange’s required confirmations, wait for finality. If confirmations are sufficient, compare the asset, network, destination, memo and net amount with the exchange’s deposit instructions. When all route evidence matches, the receiving exchange owns the posting investigation.

• No TXID: sender-side status.
• TXID pending: network-side status.
• Success with too few confirmations: finality wait.
• Success with route mismatch: specialist recovery path.
• Complete matching evidence: exchange-side posting or review.

This page is a router, not five recovery guides

The broad symptom “deposit not showing” can lead to several different intents. Wake Up To Crypto already has separate pages for a deposit pending for hours, a deposit with no transaction ID, a confirmed transaction not credited, a missing memo, a below-minimum amount and a wrong-network transfer. This page does not compete with them. It identifies the missing evidence and routes the reader to the narrow page that owns the next action.

• Broad symptom triage: this page.
• On-chain timing: pending-deposit page.
• No blockchain record: no-TXID page.
• Enough confirmations but no credit: confirmed-not-credited page.
• Known route error: memo, minimum or wrong-network page.

Why the previous article did not diagnose anything

The old page discussed trading fees, spreads and what to check before exchanging crypto. Those topics did not explain a missing incoming deposit. It also repeated generic headings used across many exchange pages and offered a test-transfer suggestion without first checking the receiving minimum. The replacement removes conversion advice and makes every section answer one diagnostic question.

• No generic exchange-fee tutorial.
• No assumption that every test amount will be credited.
• No automatic jump to wrong-network recovery.
• No claim that blockchain success equals exchange credit.
• No duplicate solution before the failure stage is known.

The seven rungs of the Exchange Deposit Evidence Ladder

A normal deposit creates seven increasingly strong records. The sender accepts the withdrawal, a TXID appears, the transaction reaches the correct chain, confirmations accumulate, the route matches the exchange instructions, the exchange detects or reviews the deposit, and finally the account balance becomes available. Do not skip directly from “sender says completed” to “exchange lost my money.”

• Rung 1: sender withdrawal record.
• Rung 2: transaction ID.
• Rung 3: correct-chain transaction status.
• Rung 4: required confirmations.
• Rung 5: deposit-route match.
• Rung 6: exchange detection and review.
• Rung 7: credited and available account balance.

Rung 1 — verify that the sender released a withdrawal

An earning site, wallet or another exchange can show Requested, Pending, Approved, Processing or Completed. These labels are internal and do not necessarily mean a blockchain transaction exists. Open the detailed withdrawal record and look for the asset, network, amount, destination, timestamp and transaction ID. When no TXID has been created, the receiving exchange has nothing public to trace.

• Withdrawal request ID.
• Internal status.
• Selected asset and network.
• Destination address and memo.
• Gross and net amount.
• Transaction ID when broadcast.

A sender status is not blockchain evidence

A platform may mark a withdrawal completed when it has finished its internal batch or handed the payment to a processor. The strongest sender-side evidence is a TXID that resolves on the intended blockchain. If the platform provides only an order number, contact its support and ask whether the withdrawal was broadcast. Do not ask the receiving exchange to locate an order number belonging to another company.

• Order ID belongs to the sender.
• TXID belongs to the blockchain transaction.
• Processor reference may require a third stage.
• No TXID means no explorer diagnosis.
• The sender must explain an unbroadcast withdrawal.

Rung 2 — open the TXID on the correct explorer

A transaction ID has meaning only on the network where it was created. Use the explorer linked by the sender or the official network documentation. Check the status, block, sender, recipient, amount, token contract and confirmations. A hash not found on one explorer may simply belong to another network, but a hash absent from the correct chain can indicate that the transaction was never propagated or was replaced.

• Correct blockchain explorer.
• Status: pending, success, failed or dropped.
• Recipient address.
• Native amount or token-transfer event.
• Token contract.
• Confirmation or finality count.

A token transfer can hide inside a contract transaction

On account-based chains, the top-level transaction value can be zero while an event log shows the actual token movement. Compare the token contract and transfer event with the asset supported by the exchange. A successful contract call is not enough when the contract represents an old, bridged or unsupported version of the token. The exchange’s deposit page and contract information decide compatibility.

• Transaction status.
• Token-transfer event.
• Official token contract.
• Amount transferred.
• Destination address.
• Exchange-supported contract version.

Rung 3 — classify the on-chain state

Pending means the transaction has been broadcast but is not yet final. Failed means the intended transfer did not complete, although a fee may still have been charged. Success means the network executed and recorded the transaction, not that the exchange has credited a user account. This rung decides whether the delay remains on-chain or has moved to the exchange boundary.

• Pending: monitor the network.
• Failed: return to the sender or wallet.
• Success: continue up the ladder.
• Dropped or replaced: identify the surviving transaction.
• Never send a duplicate merely because the balance is still zero.

Rung 4 — compare confirmations with the exchange requirement

Exchanges wait for a network-specific level of finality before crediting or releasing funds. Coinbase Exchange explains that deposits can appear as pending until the configured confirmation requirement is reached. Gemini publishes different requirements for different assets, while Bitvavo notes that a deposit can remain under processing even after the public confirmation count is sufficient because internal checks continue. Use the current requirement for the exact asset and network.

• Current public confirmation count.
• Exchange-required confirmation count.
• Whether the deposit record already appears.
• Expected additional processing window.
• Exchange status or node incident.

Do not use one universal waiting time

Bitcoin, Ethereum, Solana, Litecoin and other networks have different block or finality behavior, and exchanges choose their own risk thresholds. A website claiming that every deposit should arrive in ten minutes is not a reliable clock. Start with the exchange’s live network page, then check whether confirmations are still increasing. The specialist pending-deposit article owns the deeper timing analysis.

• Network block or finality behavior.
• Exchange risk threshold.
• Node synchronization.
• Congestion and fee priority.
• No escalation while the published requirement is still unmet.

Rung 5 — rebuild the deposit route from the receiving screen

Once the transaction is successful, compare it with the exact deposit instructions generated for your account. Do not rely on an old screenshot, a previous deposit or a third-party tutorial. The route consists of the supported asset or contract, blockchain network, receiving address, memo or tag, and minimum net amount. One mismatch can prevent automatic posting even when the chain transaction is valid.

• Asset and contract.
• Network.
• Deposit address.
• Memo, tag or payment ID.
• Net amount.
• Current route status and maintenance notice.

Asset and contract mismatch

An exchange can support a ticker but not every contract that uses that ticker. Token migrations, bridged assets and counterfeit contracts can all create a valid blockchain transfer that the exchange does not recognize. OKX and MEXC instruct users to verify the contract address rather than relying only on the token name or symbol. This problem belongs to asset support, not confirmation timing.

• Full token name.
• Contract address.
• Legacy or migrated version.
• Native versus wrapped asset.
• Current exchange listing and deposit status.

Network mismatch

The same token may exist on Ethereum, TRON, BNB Smart Chain, Polygon, Solana or another chain. The explorer can show success while the exchange does not monitor that asset on the network used. Do not attempt recovery inside this broad guide. Preserve the evidence and move to the dedicated wrong-network checklist, where address control and the exchange’s recovery policy can be assessed.

• Actual network from the explorer.
• Network selected on the deposit page.
• Whether the exchange supports that asset on the actual chain.
• No assumption based on a matching 0x address.
• No second transfer to activate the first.

Address mismatch or retired address

Compare the full on-chain recipient with the deposit address shown for your account. Some exchanges rotate or retire addresses, while others continue to monitor old addresses under conditions or fees. Kraken’s current guidance says expired addresses can sometimes still be credited with a deduction, whereas Binance documents separate handling for degraded addresses. The receiving platform controls this outcome.

• Full recipient address.
• Current account deposit address.
• Address-generation date when known.
• Old or retired-address policy.
• Never accept a replacement address from social-media support.

Missing or incorrect memo, tag or payment ID

Some exchanges use one blockchain address for many customers and assign an additional identifier to each account. The transaction can reach the exchange’s wallet while the internal ledger cannot determine the owner. Coinbase, Kraken and Binance all document mandatory memo or tag rules for selected assets. Use the dedicated memo-recovery guide because the receiver’s process, fee and eligibility rules vary.

• Was an identifier required?
• Was it included in the blockchain transaction?
• Does it match the current account?
• Could it belong to another customer?
• Only the receiving platform can investigate its shared address.

Below-minimum net deposit

The amount written by the sender can be larger than the amount received after a withdrawal fee. Compare the on-chain amount with the exchange minimum for the exact asset and network. Binance and OKX state that deposits below the required minimum are not credited under their ordinary process, while Kraken warns that some below-minimum deposits can be permanently lost. Move to the minimum-deposit article for the platform-specific recovery question.

• Gross requested amount.
• Sender withdrawal fee.
• On-chain net amount.
• Current exchange minimum.
• Recovery or accumulation rule, if any.

Unsupported deposit source or transaction type

Some platforms reject deposits that use privacy-enhancing transaction types, obsolete chains, direct mining rewards, smart-contract sources or combined transfers they cannot process. Kraken currently warns that selected obfuscation methods are not credited, and OKX documents limitations for blockchain reward and combined deposits. A correct address and network do not override these route-specific restrictions.

• Direct mining or validator reward.
• CoinJoin, PrivateSend or privacy pool.
• Smart-contract deposit support.
• Combined or batched transfer.
• Old chain after a protocol migration.
• Current receiving-platform policy.

Rung 6 — determine whether the exchange detected the deposit

An exchange can show no record, a pending record, confirming, awaiting processing, under review, completed or credited. A visible record proves that the exchange’s monitoring system has associated at least part of the transaction with the account. No record after sufficient confirmations and a complete route match makes the TXID and deposit-page evidence especially important for support.

• No internal record.
• Detected or confirming.
• Awaiting processing.
• Under review.
• Credited but unavailable.
• Completed and available.

Wallet maintenance and node synchronization

The blockchain can continue operating while the exchange pauses deposits or its node falls behind. Binance lists wallet maintenance as a reason for temporary non-crediting, and OKX’s May 2026 guidance names wallet upgrades, hard forks, project issues and node-connection difficulty as causes of suspension. Check the official status page before opening several tickets.

• Asset deposit status.
• Network status.
• Scheduled wallet maintenance.
• Mainnet upgrade or hard fork.
• Exchange node synchronization.
• Published resumption notice.

Compliance and Travel Rule review

A technically correct deposit can require account information before it becomes usable. Crypto.com currently notes that users in selected jurisdictions may need to submit deposit information under the Travel Rule. Gemini states that EU and EEA users can receive a pending deposit attestation asking who owns the sending wallet, and the associated crypto may remain unavailable for trading or withdrawal until the information is provided and screened. This is neither a blockchain failure nor a memo problem.

• Pending deposit attestation.
• Sender or wallet-ownership information.
• Compliance or source-of-funds review.
• Account verification state.
• Restrictions on trading or withdrawal after credit.
• Respond only inside the official exchange account.

Credited, available and withdrawable are different states

An exchange may display the incoming asset while temporarily restricting trading, internal transfer or withdrawal. The deposit has then crossed the posting boundary even though it is not fully usable. Do not continue diagnosing it as a missing deposit. Read the account notice, compliance request or confirmation policy that controls availability.

• Detected: exchange found the transfer.
• Credited: internal balance updated.
• Available to trade: market use enabled.
• Available to withdraw: security and finality hold cleared.
• A balance in the wrong sub-account may need an internal transfer.

Check the correct exchange wallet or sub-account

Large exchanges can separate funding, spot, trading, derivatives, earn and Web3 wallet balances. An incoming deposit may be credited to the funding account while the user looks only at the spot balance. Search the complete transaction history and asset page before treating the deposit as absent. An internal transfer between exchange accounts is not another blockchain deposit.

• Funding or main account.
• Spot or trading account.
• Sub-account.
• Earn or staking account.
• Exchange Web3 wallet versus custodial exchange balance.
• Internal transfer history.

A human example: the TXID moves responsibility twice

Ania withdraws LTC from a reward platform to an exchange. For thirty minutes the sender shows Processing and provides no TXID, so the sender owns the delay. A hash then appears, but the explorer shows only two of the exchange’s required confirmations, so the network owns the wait. After the requirement is reached, the exchange still shows Awaiting Processing because its status page reports Litecoin wallet maintenance. The evidence changes the responsible party without changing the original transaction.

• No TXID: sender.
• TXID with insufficient confirmations: network.
• Enough confirmations plus maintenance: exchange.
• No duplicate deposit was needed.
• One support ticket was opened only after the relevant wait ended.

Build the Missing Deposit Evidence Card

Create one compact record instead of sending a paragraph that says only “my crypto is missing.” The card should connect the sender record, blockchain record, receiving instructions and exchange account. Hide unrelated balances and identity data, but preserve every identifier needed to locate the transfer.

• Sending platform and withdrawal ID.
• TXID and correct explorer link.
• Asset, token contract and network.
• Amount and timestamp.
• Deposit address and memo or tag.
• Confirmation count and exchange requirement.
• Screenshot of the current deposit instructions.
• Exchange account ID or support-request identifier.

Use the Deposit Owner Matrix

Send the question to the party that controls the first missing rung. The sender controls an unbroadcast withdrawal. The blockchain controls an unconfirmed transaction, although the sender may support fee replacement on some networks. The exchange controls account matching, wallet maintenance, compliance and internal credit. A recovery specialist found through a direct message controls none of these systems.

• No TXID: sender support.
• Pending on-chain: sender wallet tools or wait.
• Enough confirmations, route matches: receiving exchange.
• Known missing memo or unsupported route: receiving exchange recovery process.
• Wrong external address: actual address owner, if identifiable.
• Never give a recovery agent wallet secrets.

When the support ticket is ready

Open a receiving-exchange ticket when the transaction is successful, the required confirmations have been reached, the route evidence has been checked and the platform’s normal posting window or status incident no longer explains the delay. Use the exchange’s own deposit appeal or recovery tool when it provides one. Binance, Crypto.com, MEXC and Bybit currently document self-service or guided processes for selected missing deposits.

• Correct support category.
• One transaction per case unless the platform says otherwise.
• Complete Evidence Card.
• Exact symptom and missing rung.
• No unsupported conclusion such as “the blockchain stole it.”
• Keep the ticket number and every reply.

Do not open duplicate tickets or resend the deposit

Multiple tickets can split the evidence and slow manual review. A second deposit does not attach a memo to the first, increase its confirmation count or prove ownership of an unsupported route. It can create another below-minimum loss or repeat the same network mistake. Use one case, one TXID and one chronological evidence packet.

• Do not send a larger deposit to push the first through.
• Do not pay an activation amount.
• Do not submit several recovery forms for one TXID.
• Do not edit evidence screenshots.
• Update the existing ticket when new confirmations or status information appears.

Recovery can cost more than a small deposit

Manual recovery uses technical and compliance resources and is not always free. Crypto.com currently lists possible manual recovery charges for unsupported tokens and missing memos. Bybit EU says its missing-memo process can deduct a multiple of the standard withdrawal fee, while Binance and MEXC also document fees or minimum-value limits for selected retrievals. For a tiny faucet deposit, the rational result may be that recovery is unavailable or uneconomic.

• Eligibility is platform-specific.
• Recovery is not guaranteed.
• Fee may be deducted from the returned asset.
• Minimum recovery value can exceed the deposit.
• Processing can take days or weeks.
• Do not send outside money to unofficial support.

The missing-deposit scam that starts after the real mistake

Public complaints attract fake support accounts and recovery services. They may ask for a release fee, wallet synchronization, remote access, seed phrase or a small transfer to prove ownership. A real exchange can require information, verification or an official handling fee inside its recovery workflow, but it does not need your self-custody secret. Enter support only through the verified app or domain.

• No seed phrase or private key.
• No screen-sharing with an unsolicited account.
• No payment to a social-media address.
• No wallet connection to “recover” a centralized exchange credit.
• Verify every support domain independently.

Why tiny rewards are especially vulnerable

A small faucet or microwallet withdrawal can fall below the exchange minimum after the sender’s fee. A test transaction can therefore create the exact missing-deposit problem it was meant to prevent. Before sending tiny rewards to an exchange, compare the net amount with the current deposit minimum and the possible recovery fee. When the result is too small, aggregation in a compatible collection account can be safer.

• Gross reward balance.
• Withdrawal deduction.
• Net on-chain amount.
• Exchange minimum.
• Recovery fee exposure.
• Alternative collection route.

Where FaucetPay fits—and where it does not

FaucetPay can collect supported micropayments before a larger withdrawal, reducing the number of tiny exchange deposits. It does not repair a deposit already sent to an exchange, change the network used or add a missing memo after confirmation. Use it only as a future route-planning option when the reward sources and eventual destination support the same asset and network.

• Useful before the exchange transfer.
• Not an exchange recovery service.
• Not a network bridge.
• Not a replacement for an exchange memo.
• Live withdrawal fee and minimum still apply.
• Keep the CTA away from an active recovery emergency.

The keyword ownership map

This page owns the broad symptom and the diagnostic fork. The confirmed-not-credited page owns cases where the blockchain requirement is complete. The pending-for-hours page owns elapsed-time and confirmation analysis. The no-TXID page owns an incoming deposit with no public transaction. Memo, minimum and wrong-network pages own their known route errors.

• This page: identify the first missing evidence.
• Confirmed-not-credited: exchange posting after sufficient finality.
• Pending-for-hours: timing and confirmation state.
• No-TXID: sender has not produced public evidence.
• Forgot-memo: shared-address account assignment.
• Below-minimum: hard crediting threshold.
• Wrong-network: recovery after a known chain mismatch.

The final diagnostic rule

Do not ask “where is my crypto?” until you can state the highest rung reached. A usable report sounds like this: the sender broadcast transaction X on network Y; the explorer shows success and Z confirmations; the address, memo, asset and amount match the exchange’s current instructions; the exchange has or has not detected the deposit. That sentence identifies the next owner and prevents repeated transfers, duplicate tickets and recovery scams.

• Name the sender status.
• Name the on-chain status.
• Name the confirmation state.
• Name the route match.
• Name the exchange status.
• Escalate only to the owner of the first missing rung.

How this article was researched

Wake Up To Crypto reviewed the live page and the nearest internal articles covering confirmed-but-uncredited deposits, pending deposits, missing transaction IDs, minimums, memo recovery and wrong-network transfers. Current documentation from Coinbase, Kraken, Binance, OKX, Crypto.com, Gemini, MEXC, Bybit, Bitvavo and Bitpanda was checked for confirmation rules, route mismatches, status incidents, Travel Rule reviews and recovery workflows. Twenty search-landscape pages were reviewed for missing-deposit checklists and support advice. The keyword boundary was designed so this page routes the symptom without replacing the specialist pages.

• Research date: July 24, 2026.
• Author and reviewer: Kamil Sobczak.
• Primary intent: broad missing-exchange-deposit diagnosis.
• Known error and recovery terms excluded from secondary keywords.
• No universal confirmation time or recovery promise was invented.

Sources used for the July 2026 revision

Primary sources support current exchange mechanics and account procedures. Search-landscape pages were reviewed to identify competing structures, common advice and factual gaps. Inclusion does not endorse an exchange or third-party recovery service.

• Coinbase pending deposit confirmations: https://help.coinbase.com/en/exchange/crypto-transfers/deposit-pending-unconfirmed-transaction
• Coinbase mandatory memo guidance: https://help.coinbase.com/en/exchange/crypto-transfers/memo-not-included
• Coinbase unsupported deposit recovery: https://help.coinbase.com/en/coinbase/trading-and-funding/sending-or-receiving-cryptocurrency/recover-unsupported-crypto
• Kraken missing cryptocurrency deposit checklist: https://support.kraken.com/articles/360001488126-cryptocurrency-deposit-is-missing
• Kraken cryptocurrency deposit process: https://support.kraken.com/articles/7078582415636-how-to-deposit-cryptocurrencies-to-your-kraken-account
• Kraken deposit minimums: https://support.kraken.com/articles/360000292886-cryptocurrency-deposit-fees-and-minimums
• Binance deposit not credited checklist: https://www.binance.com/en/support/faq/detail/115003736451
• Binance incorrect-deposit FAQ: https://www.binance.com/en/support/faq/detail/115003798632
• Binance self-service missing-deposit recovery: https://www.binance.com/en/support/faq/detail/4d1347b4d6d44564ba44ea785703a4fd
• OKX deposit not credited guidance: https://www.okx.com/help/why-has-not-my-deposit-been-credited
• OKX May 2026 missing-deposit guidance: https://www.okx.com/help/why-hasnt-my-deposit-arrived-yet
• OKX deposit and withdrawal suspension guidance: https://www.okx.com/help/why-is-my-deposit-withdrawal-suspended
• Crypto.com missing-deposit guidance: https://help.crypto.com/en/articles/5434936-missing-crypto-deposits
• Crypto.com deposit-recovery feature: https://help.crypto.com/en/articles/8820278-crypto-deposit-recovery
• Gemini confirmation and deposit-time guidance: https://support.gemini.com/hc/en-us/articles/205424836-How-long-until-my-crypto-deposit-reaches-my-account
• Gemini EU and EEA deposit-attestation requirements: https://support.gemini.com/hc/en-gb/articles/31697946211355-EU-European-Economic-Area-Deposits-Attestations-FAQ
• MEXC June 2026 deposit FAQ: https://www.mexc.com/support/crypto-deposit-withdrawals/deposit-faq
• MEXC uncredited-deposit return application: https://www.mexc.com/support/article/what-is-the-uncredited-deposit-return-application-17827791526274
• Bybit EU missing-memo self-service recovery: https://www.bybit.eu/en-EU/help-center/article/How-Recover-Missing-Deposit-Self-Service
• Bitvavo July 2026 deposit-confirmation guidance: https://support.bitvavo.com/hc/en-us/articles/4405184502673-Confirmations-when-depositing-crypto-assets
• CryptoAdventure missing-deposit guide: https://cryptoadventure.com/why-your-deposit-isnt-showing-up-confirmations-minimums-and-timing-explained/
• CryptoNakta missing-deposit decision tree: https://cryptonakta.com/crypto-deposit-not-credited/
• Walletium pending-or-not-received guide: https://www.walletium.net/en/learning/pending-transaction-not-received
• DigitalCoinReview deposit-issue guide: https://www.digitalcoinreview.com/how-to-fix-deposit-issues-on-crypto-exchanges-a-beginners-guide/
• CoinCarp confirmed-but-not-credited guide: https://www.coincarp.com/learn/crypto-deposit-confirmed-but-not-credited-check-txid-confirmations-and-network/
• Bitaigen missing-deposit guide: https://www.bitaigen.com/posts/en/crypto-deposit-not-showing-fix-en
• Flashift missing-deposit guide: https://flashift.app/blog/crypto-deposit-is-not-showing-up/
• Investopedia transaction-mechanics guide: https://www.investopedia.com/how-a-crypto-transaction-actually-happens-12003083
• OKX Learn confirmed-transfer troubleshooting: https://www.okx.com/learn/crypto/crypto-transfer-has-been-confirmed-but-not-received
• Bitpanda deposit-and-withdrawal troubleshooting: https://support.bitpanda.com/hc/en-us/articles/23553179392412-Help-with-crypto-deposits-and-withdrawals
• Bybit missing-deposit self-service guide: https://www.bybit.com/en/help-center/article/How-Recover-Missing-Deposit-Self-Service
• Gate deposit FAQ: https://www.gate.com/help/guide/deposit-withdrawa/17297/frequently-asked-questions-on-deposit
• Binance.US deposit-recovery tool: https://support.binance.us/en/articles/9842793-how-to-use-the-deposit-recovery-tool
• Crypto.com missing-deposit article: https://help.crypto.com/en/articles/5434936-missing-crypto-deposits
• Gemini delayed-transfer guide: https://support.gemini.com/hc/en-gb/articles/360007315911-Why-is-there-a-delay-in-my-digital-asset-transfer
• MEXC incorrect-deposit solutions: https://www.mexc.com/support/article/common-issues-in-incorrect-deposits-and-solutions-360002325071
• Walletium wrong-network recovery guide: https://www.walletium.net/en/learning/wrong-network-recovery-steps
• Changelly PRO deposit and maintenance guide: https://changelly.com/faq/changelly-pro/deposit-pro/
• Changelly transaction troubleshooting: https://changelly.com/faq/changelly/exchange-troubleshooting/
• Coin Bureau unconfirmed-transaction guide: https://coinbureau.com/analysis/uncomfirmed-transactions-what-they-are-overcome

FAQ