Changelly Changelly transaction tracking separates deposit confirmation from exchange and payout progress
Changelly assigns each swap a transaction ID that identifies its exchange record. Open that record to check whether your deposit is awaiting confirmation, the exchange is processing, or the payout is underway. Your sending wallet's transaction hash identifies the incoming transfer; the payout hash identifies the outgoing transfer. Those records help locate a delay and determine whether the next step belongs with the sending wallet, Changelly support, or the receiving service.
In this guide
Key takeaway: The exchange status identifies the processing stage, while the payout hash helps establish what happened to the transfer toward your wallet.
Follow the exchange record through to its payout
Your transaction history opens the exchange details, including the service's transaction ID and recorded status. Keep that ID alongside the deposit hash. They identify different records, so entering the service ID into a blockchain explorer won't retrieve the payment. A completed exchange also has an outgoing transfer to distinguish from your original deposit.
The ordinary successful progression runs through the stages below. A hold or failure interrupts that progression; it isn't another mandatory step. A status label records processing progress; it doesn't certify the transaction's security.
| Exchange stage | Recorded progress | What this establishes |
|---|---|---|
| Created | The exchange request has an ID. | A request exists; payment hasn't been established. |
| Waiting for payment | The exchange awaits the incoming payment. | Deposit recognition remains incomplete. |
| Confirming | The deposit is accumulating required confirmations. | Recognition doesn't yet mean exchange readiness. |
| Exchanging | The confirmed deposit enters exchange processing. | The outgoing transfer isn't yet established. |
| Sending | The payout is underway. | Its transfer record needs separate examination. |
| Finished | The service reports successful payout. | The payout record identifies the destination transfer. |
| Deposit confirmation, exchange processing, and payout are distinct events within the same order. | ||
Why is my swap still waiting after I sent the deposit?
A waiting status means the service hasn't recognized the expected payment, even when your wallet shows an outgoing transfer.
Compare the deposit's actual destination, asset, network, and required memo with the original exchange instructions. A successful transfer to a different address or network doesn't satisfy that order. An omitted memo can also prevent automatic matching, despite a transfer appearing on the blockchain.
Refreshing the exchange record can resolve an outdated display. If the mismatch remains, give support the order ID and deposit hash.
Confirming has a different meaning: the service has recognized the deposit and awaits the required blockchain confirmations. The required confirmation count depends on the incoming currency. A transfer appearing in an explorer doesn't establish that it has met this requirement.
Don't send a duplicate deposit to make the status advance. A second payment doesn't correct the original transfer's address, network, or memo.
A hold requires attention to the verification request
Changelly can pause an exchange for anti-money laundering and know-your-customer procedures. Blockchain confirmations alone won't resolve that hold. Follow the verification request associated with the transaction, and keep any case correspondence together. If an embedded exchange interface doesn't provide those instructions, ask its operator for them: API partners must communicate hold instructions to their users. A previously completed identity check doesn't establish that no additional information will be requested.
Separate exchange delays from outgoing transfer delays
Exchanging indicates that the confirmed payment has reached conversion processing. Trading backlogs or technical problems at an exchange partner can delay that stage. Increasing a fee in your sending wallet won't repair processing that happens after deposit confirmation. Report the unchanged stage and transaction ID when requesting an explanation.
Sending shifts attention to the outgoing transfer. Look for its payout hash rather than continuing to monitor the deposit hash. If no payout hash appears, request the payout details; absence from the interface alone doesn't identify the cause. Once a hash is available, its network record provides information about that transfer's progress. Network congestion can delay delivery after the exchange itself has processed.
A quoted processing estimate isn't a deadline covering every confirmation delay or verification hold. Identify the unresolved stage before judging elapsed time.
Why does Finished appear before my wallet shows the funds?
A Finished status reports successful payout, while a receiving wallet can still show an outdated balance or an uncredited deposit.
Examine the payout on the correct network and compare its destination with the exchange record. Where the network exposes transfer details, check the delivered asset and amount as well. An address can look valid while belonging to a network that the receiving service doesn't support. Address appearance alone therefore doesn't establish compatibility.
An unsynchronized wallet can display an incorrect balance after a transfer. Refresh or synchronize a compatible wallet when its display is behind. If the receiving service requires a memo that the payout lacks, its support team must investigate the unassigned deposit. A confirmed payout to the expected destination moves the investigation toward the receiving service's display or crediting process.
Read the identifiers in detailed transaction records
Detailed API records distinguish payinHash, payoutHash, and refundHash for incoming, outgoing, and returned funds. The id field identifies the exchange order. These fields aren't interchangeable: an incoming hash cannot establish payout, and a refund hash describes a return rather than delivery of the requested output. Availability flags such as canPush and canRefund describe permitted handling after an order stops; they don't establish that either action has happened. Keep the transfer record that matches the resolution you expect.
Changelly: quick answers
Can I top up a deposit that left my Changelly swap below the required amount?
Don't send a separate top-up to repair an insufficient deposit. The transaction instructions state that you can't pay the missing amount later. Ask support what handling is available for the existing order. An amount below the minimum can prevent automatic exchange, and a deposit that cannot cover the network fee may be non-refundable.
Does an expired swap status mean a late deposit has disappeared?
An expired status identifies a missed fixed-rate payment window; it doesn't establish the location of a late transfer. Preserve the deposit hash and ask support to investigate the existing order. Late payments can require manual handling, so creating another order doesn't automatically assign the original deposit to it.
How can I confirm that a promised swap refund has actually been sent?
A refund transfer hash provides a record of the return payment. Request it if support has confirmed a refund but your wallet shows nothing. Match its destination with the agreed refund address and examine the transfer's status on the relevant network. Approval of a refund and execution of its transfer are separate events.
Why does the completed payout amount differ from the original swap estimate?
A floating-rate swap can produce a different output when market conditions change during processing. Compare the completed transaction's actual payout with the original estimate and its fee treatment. In API records, the expected output is an estimate before the network fee, while the actual output records the amount sent to the payout address.
Is there a fixed refund deadline after a Changelly swap fails?
Refund timing depends on the circumstances and recovery work required. The API FAQ describes a normal range of 1-10 business days, with exceptions that can take longer. Sending an unsupported asset or using a different chain can extend the process. Ask support for the estimate attached to your particular case rather than treating that range as a guarantee.
Updated on