Crypto Swap Pending? A Step-by-Step Troubleshooting Guide

Swap troubleshooting · Evidence before action

By Marcus Richardson — Founder & Privacy Research Lead · Published September 19, 2026

A crypto swap that appears stuck does not tell you, by itself, where the delay is. Your sending wallet may still be preparing the payment, the blockchain may be confirming it, the exchange may be processing the conversion, or the receiving service may not yet have credited the payout. Those are different problems with different owners. The useful first step is to locate the last independently verifiable event, then ask the party responsible for the next event to investigate.

This guide is an evidence-based troubleshooting workflow, not a promise that every delayed or incorrectly sent transfer can be recovered. The examples are hypothetical and contain no customer transactions. You can use the method for many crypto exchanges; the AceChange links help you locate the relevant tools when your order was created here.

The one-minute triage table

Start with what you can verify, rather than the most alarming interpretation of the screen. A status label belongs to one system. A withdrawal marked “completed” by your sending platform is not necessarily a completed swap, and a completed swap does not necessarily mean a receiving exchange has finished its own crediting process.

Use this as a routing table, not a diagnosis. For example, a missing hash might reflect a platform display issue rather than an unbroadcast payment. Ask the sender to confirm which situation applies. When two screens disagree, record both and the time you checked them; that discrepancy is useful evidence instead of a reason to guess.

Build a small evidence pack before changing anything

Open the original order through your saved bookmark, your own browser history, or the official website. For an AceChange order, use the order tracker. Avoid search advertisements and links sent by strangers. Save the order ID separately from the full order URL: a tracking URL can contain access information that should not be posted publicly.

Record the sending asset and network, receiving asset and network, expected deposit amount, amount actually transferred, destination address, and any required memo or destination tag. Note whether you selected a fixed or floating rate. Capture the current status and the order’s deadline if one is shown. Keep the unredacted copy privately, and redact balances and unrelated activity before sending screenshots to support.

Your blockchain transaction hash and your exchange order ID are different identifiers. The order ID describes the service’s record. The transaction hash identifies a transfer on a particular blockchain. A swap can have an incoming hash and a separate outgoing hash, often on different networks. Label them “deposit” and “payout” in your notes so that neither you nor support searches the wrong transfer.

Find the explorer through the wallet’s own transaction details or official network documentation. Check the network name before searching. A transaction absent from an Ethereum explorer may exist on another network; absence on one explorer is not proof that nothing was sent. Where the explorer shows token transfers, inspect the actual asset movement rather than assuming the top-level native-coin amount describes the token payment.

Branch A: the deposit has not reached the required stage

No transaction hash: start with the sender

If you withdrew from another exchange and have only a withdrawal reference, ask that exchange whether the transfer has been broadcast and request the blockchain hash and network. Internal withdrawal approval and on-chain settlement are separate events. Reopening the swap page cannot force the sending platform to release a withdrawal that is still inside its own queue.

If you used a self-custody wallet, open the relevant account and network and inspect its activity. Did you approve a token allowance instead of sending the payment? Did you reject a confirmation prompt? Is the pending item an actual transfer to the order’s address? Do not create a new transfer until you understand what the existing item represents. Two outgoing transfers can become two real payments even if one interface looked unresponsive.

A hash exists, but the transaction is pending

A pending transaction has not reached the same state as a successful confirmed transfer. On Ethereum, transactions pass through submission, inclusion, and later finality stages; the official Ethereum transaction documentation explains that lifecycle. The practical question is whether the explorer shows your transfer included successfully, not simply whether your wallet has produced a hash.

For supported pending transactions, some wallets offer a speed-up or cancellation attempt. These actions have conditions and may cost additional network fees. Follow the wallet’s official instructions rather than copying advanced nonce settings from a stranger. MetaMask’s pending-transaction guide distinguishes pending replacement from confirmed transfers, which cannot be reversed through its cancellation control.

If the sending account belongs to a custodial platform, you generally cannot use your own wallet to replace that platform’s transaction. Ask the sender what options it supports. Never pay an unsolicited “accelerator” or “support agent” on the assumption that they control the next block. A useful support answer identifies the transfer, the current state, and the available action; it does not require your recovery phrase.

The transfer succeeded, but the details differ from the order

Compare the destination address character by character with the order, and compare the network and asset explicitly. A familiar ticker is not enough. Also check the amount that reached the deposit address rather than only the amount entered on the withdrawal screen. A withdrawal fee deducted from the entered amount can leave the recipient with a different quantity.

If you discover a mismatch, stop experimenting and contact the swap service with the evidence. Do not assume that sending the difference will automatically combine two payments or repair the first one. Whether a service can match, combine, return, or recover a payment depends on the actual order and network. Ask for instructions tied to your existing order before taking another irreversible step.

Branch B: the deposit is confirmed, but conversion has not finished

First distinguish “has a confirmation” from “has met the order’s required confirmations.” A provider may wait for more than the first block. Use the requirement shown for your order, rather than a universal number from a blog. Different assets and services can have different requirements, and the same service can change them.

Once the required confirmation threshold is met, compare the order’s last update with the explorer evidence. If the tracker remains unchanged, a recognition or processing issue is one possible explanation. Send the incoming hash and the exact observed status to support. Asking “Has this deposit been matched to order X?” is more useful than asking only “Where is my money?” because it names the unresolved step.

Look for an explicit action request. AceChange has a separate refund and emergency-status guide describing the controls for continuing an eligible order or requesting a refund. Read the current order instructions and displayed amounts before choosing. Continuing at a new rate is a financial decision; a refund can involve a network fee and needs a compatible receiving address.

An expired quote and a missing transfer are not the same problem. Expiry tells you something about the order’s pricing window. The explorer tells you something about the transfer. If payment has already been sent, preserve the original order and ask about its available resolution. Creating another order does not move the first deposit into the new order automatically.

Check the service status link reached through the official website for a relevant incident. Match the incident’s network and time window to your case. A report about another asset does not explain your delay, and a green status page does not prove that an individual order has no issue. Keep a short timeline so that support can distinguish a network delay from a later processing delay.

Branch C: the order says completed, but you cannot see the funds

Find the outgoing transaction hash. It should describe the payout, not the payment you originally sent. Open it on the receiving network’s explorer and verify status, recipient, asset, and amount. If the order has no outgoing hash or the link cannot be resolved, ask the swap service to identify the payout transaction before trying wallet-display fixes.

If the payout remains pending, the destination may not yet have a confirmed incoming transfer to display or credit. If the payout is successful, compare the recipient with the address you supplied. For a token, inspect the token transfer record. A successful transaction elsewhere in the same account history is not proof that the particular payout arrived.

When a self-custody wallet shows no balance despite a successful transfer to the correct account, check that you have selected the receiving network and the right account. Some token balances need to be displayed explicitly. Verify any token contract against the issuer’s official documentation before adding it. Never follow a link embedded in an unsolicited token name, and never enter a seed phrase into an explorer to “refresh” a balance.

When the destination is another exchange, its deposit-crediting rules matter. Open that exchange’s deposit history for the exact asset and network. Check its current minimum deposit, required confirmations, and any maintenance notice. If the payout satisfies those conditions but remains uncredited, send the receiving exchange the outgoing hash and your deposit details through its authenticated support channel.

A memo or destination tag can determine which customer receives credit inside a shared address. The XRP Ledger documentation explains that destination tags can identify the beneficiary in a recipient’s own systems. If yours was missing or incorrect, contact the receiving platform. A blockchain success status alone cannot establish that its internal customer mapping was correct.

A support request that is easy to investigate

Use the official AceChange contact page for an AceChange order. Share transaction details privately with the relevant service, not in a public group. Even public blockchain information can connect your identity to balances and activity when you post it alongside your name or contact details.

Subject: Order [order ID] — deposit confirmed, order still [status]

I created the order at [time and time zone]. The requested pair was [asset and network] to [asset and network], using [fixed/floating] pricing. My deposit transaction is [hash] on [network]. The explorer currently shows [status and confirmations], checked at [time]. The amount received at the deposit address is [amount].

The order currently shows [exact message]. The payout hash is [hash / not shown]. Please confirm whether the deposit has been matched and which step is still pending. I have attached a redacted screenshot of the relevant order information.

Replace every bracketed field you can verify. If you do not know a field, write “not available” instead of guessing. Attach only relevant screenshots. Do not include passwords, two-factor codes, full wallet exports, private keys, seed phrases, or unrelated financial records. If further information is requested, verify that the request is still inside the legitimate support conversation.

Keep replies in one ticket where possible. Record the ticket number and the next update promised by support. A concise follow-up should report new evidence, such as a newly confirmed deposit or a newly available payout hash. Repeating the same message in several channels can make it harder to maintain a clear timeline.

Three worked cases: locate the missing step

Case 1: a withdrawal screen says completed

Imagine Alex withdraws a token from Exchange A to fund a swap. Exchange A displays “completed,” but the swap still awaits payment. Alex has copied the exchange’s withdrawal reference, not a blockchain hash. The first useful action is to obtain the actual hash and network from Exchange A. If the transfer is pending, the problem is upstream of the swap’s confirmation requirement. If it is successful at the right deposit address, Alex can provide the hash to the swap service for matching. The same initial symptom leads to different actions depending on the evidence.

Case 2: the payout exists, but the wallet looks empty

Jamie swaps into a stablecoin and sees a completed order. The outgoing hash shows a successful token transfer to Jamie’s address on the selected network. The wallet, however, is showing another network with an identical-looking account address. Jamie checks the receiving network and token display using the wallet’s official documentation. There is no reason to pay a recovery service or initiate another swap to make an existing confirmed balance visible. If the explorer instead showed a different recipient, the investigation would move back to the address entered on the order.

Case 3: the amount arriving is smaller than expected

Sam enters 100 units on a withdrawal screen, but the sending platform deducts a one-unit withdrawal fee and sends 99. The fixed-amount swap expected 100. Sam saves both the withdrawal record and the blockchain transfer amount, then asks the swap service how to resolve the mismatch. Sam does not send another unit blindly: a second transfer might incur another fee or need separate matching. The lesson is to compare the recipient amount at every handoff, not to treat the number typed into the first screen as the amount delivered.

When waiting is reasonable, and when to escalate

Use a checkpoint tied to the evidence. If a transfer is unconfirmed and the wallet explains that it is awaiting network inclusion, monitor the hash and review supported wallet options. If the required confirmations have been reached but the order is unchanged beyond its displayed estimate, contact the swap service. If a payout is successful but not credited under the destination platform’s stated conditions, contact that destination.

Escalate immediately when you identify a wrong network, wrong address, missing required identifier, or a suspicious message asking for secrets. Waiting does not correct those details. Conversely, elapsed time alone cannot establish theft or permanent loss. Ask for a verifiable explanation and preserve records rather than making an unsupported assumption.

For your next swap, prepare the destination before starting the quote timer, check the recipient amount after withdrawal fees, save the order ID, and confirm the selected networks. Read the basic swap walkthrough before creating an order if the process is new to you. Preparation is most useful before a transfer is signed.

Before another order, use the address, network and memo checklist and the guide to comparing swap costs to prepare the destination and quote.