Changenow swap
Changenow swap Delay Tracking and Payout Confirmation
· updated
Changenow swap delays require separate checks of the deposit, exchange status, and payout transaction. Before resending, establish whether the original transfer reached the deposit address on the selected network. A confirmed deposit does not establish delivery of the exchanged asset. Keep the exchange ID alongside the incoming transaction hash, then locate the outgoing hash when a payout exists. Compare that payout with the intended recipient and the receiving wallet record. If those records disagree, investigate the missing handoff before sending more funds. Additional deposits cannot explain what happened to the original transfer and may leave another payment to reconcile.
A confirmed deposit proves the incoming transfer, while a matching payout record establishes whether the exchanged funds reached their destination.
Deposit Recognition, Exchange Processing, and Delivery
The exchange status describes progress inside the service, while blockchain records describe individual transfers. Read both together to distinguish an unrecognized deposit from conversion in progress or an outgoing payment.
The Incoming Transfer
The deposit hash identifies the transfer from the sending wallet. Check its network, execution status, destination, and amount against the existing order. Include the memo or destination tag when the order requires one. A wallet entry showing a withdrawal request does not necessarily establish that the sender broadcast a blockchain transaction. Likewise, a successful transfer to a different address does not establish payment of this order.
The Order and Outgoing Transfer
The exchange ID identifies the service order; it is different from a blockchain transaction hash. The order progresses through deposit recognition, confirmation, conversion, and sending. An outgoing hash identifies the payout transfer when one exists. A deposit hash cannot substitute for it, because the incoming and outgoing payments represent different movements of funds.
Should I Send Another Deposit While the Exchange Is Delayed?
A delayed status alone does not justify another deposit, because the original transfer may already exist on the network or await recognition by the service. Establish its fate first. If the sender confirms that no transfer occurred, review the order's deposit conditions before proceeding. If funds already left, keep working with the existing order. A replacement order does not explain an earlier payment, and a second transfer does not repair a missing memo or network mismatch.
Confirmation Delays and Exchange Processing
A deposit awaiting network confirmations needs a different response from an order that has reached conversion. ChangeNOW waits for the required deposit confirmations before proceeding with the exchange. Network congestion and transaction validation affect that prerequisite. When an explorer shows confirmation but the order remains stalled, contact support with the hash and order ID. The exchanging stage then involves processing whose duration varies with network and market conditions; elapsed time alone does not identify the fault.
Payout Broadcast and Receiving Wallet Records
A payout needs its own confirmation check, because the sending status can cover work that precedes delivery. The receiving wallet then supplies a separate record of the incoming asset.
No Verifiable Outgoing Hash
A missing payout hash leaves broadcast unconfirmed from the information available to you. Ask support whether the service has created the outgoing transaction and which network carries it. Sending delays can involve network conditions, liquidity providers, temporary asset unavailability, or technical problems. The published sending-stage guidance recommends contacting support when that stage exceeds 10-15 minutes. That is an escalation point, not a guaranteed delivery deadline.
A Payout Exists, but the Balance Looks Wrong
The outgoing record must match the expected asset, destination network, and recipient. Where the network exposes them publicly, inspect the actual transfer details rather than relying on a generic success label. Some networks require wallet-specific evidence because public transaction details are limited. A transaction identifier alone does not establish every payment detail.
A matching confirmed payout shifts attention to the receiver. Check the wallet's selected network and account, asset visibility, and synchronization. If a hosted account receives the payout, its operator may still need to credit that account. Keep the payout hash available for reconciliation. Sending another deposit would create another transfer without resolving the missing display or credit.
Unrecognized Deposits and Orders Requiring Attention
An order with a confirmed but unrecognized deposit needs investigation of the actual transfer details. An explicit review notice instead requires attention to the request attached to that order.
Network, Memo, and Deposit Conditions
The address alone may not identify a deposit correctly. Omitting a required deposit memo prevents ChangeNOW from automatically recognizing the deposit. Wrong-network transfers, unsupported assets, and late deposits can also interrupt processing. Compare the recorded transfer with the original instructions, including the deposit deadline associated with the quote. Once funds have moved, correction or recovery requires case-specific handling; changing a field in a new order does not amend that transfer.
Review Notices and Support Records
A verification request can pause an exchange separately from blockchain confirmation. Waiting for more blocks does not satisfy an identity request. Address the notice through the existing order, and ask support to clarify anything unclear. Avoid interpreting a review notice as proof of either wrongdoing or successful completion.
A useful support message identifies the unresolved event. Include the order ID, deposit hash, selected networks, actual amount sent, relevant timestamps, and any payout hash. State the visible mismatch, such as a confirmed deposit alongside an unchanged order status. Include a screenshot of an error when it adds information, while keeping unrelated account details private. ChangeNOW accepts tickets through its help center; failed exchanges also have a request form on the exchange status page.
A Confirmed Deposit With a Later Payout
In this hypothetical exchange, the sender will compare the order status, transaction records, and receiving wallet. Before funding it, the sender defines completion as receipt of the selected output asset at the intended destination, with a matching incoming wallet record.
The sender creates the order and checks its deposit conditions before transferring funds. Later, the deposit confirms on the selected network. The order shows sending, but no outgoing hash is available. The sender cannot yet verify that the payout reached the receiving wallet.
The sender keeps the original order and requests its payout details instead of making another deposit. Deposit confirmation supports the investigation but does not resolve the missing outgoing transfer.
Support later supplies the payout hash. Its transaction record shows successful delivery to the intended address on the selected network, and the receiving wallet displays the corresponding incoming asset. The sender records the payout and does not resend.
If the payout record instead showed a different recipient, wallet refreshes would not correct the destination. The next action would remain investigation of that specific transfer.
Changenow swap: what people ask
Where Can I Recover the Exchange ID If I Lost the Tracking Page?
Your browser history may contain the original exchange page and its order ID. Search around the time you created the exchange, then reopen the matching entry. Compare its deposit details with your transfer before assuming it is the correct order. The exchange ID identifies the service order, so searching a blockchain explorer with it will not replace the deposit hash.
Can a Higher Network Fee Accelerate an Exchange After the Deposit Has Confirmed?
A higher deposit fee does not accelerate conversion or payout after the deposit has already confirmed. The original fee concerns the incoming network transaction. At that point, identify whether the order needs more confirmations, processing, or another action. Sending a separate payment with a higher fee does not increase the fee of the original transfer.
Does a Failed Exchange Status Mean That My Deposit Transaction Failed?
A failed exchange status does not establish that the blockchain deposit failed. The service can encounter an invalid payout detail, asset unavailability, or an internal error after receiving funds. Check the deposit transaction separately and ask support which condition stopped the order.
Is a Sending platform's Withdrawal ID Enough to Trace My Deposit?
An internal withdrawal ID may identify only the sending platform's record. Ask that platform for the blockchain transaction hash and the network it used. If it has not broadcast the withdrawal, the exchange cannot recognize an on-chain deposit yet. Preserve both identifiers, since the sender and the exchange may need different records to investigate the same payment.
Will a Resolved Service Incident Confirm That My Individual Exchange Finished?
A resolved incident notice does not by itself confirm completion of your order. It describes the service incident, while your exchange has its own deposit and payout records. Check the individual order and receiving transaction before treating the payment as complete. If the discrepancy remains, include the order ID when reporting the unresolved exchange.
What Happens If I Accidentally Send a Second Deposit During the Delay?
A second deposit creates an additional transfer that also needs reconciliation. Preserve both transaction hashes and tell support which order each payment was intended to fund. Do not assume the service will merge the payments or that the second transfer replaces the first. Stop further deposits while support establishes what happened to each payment.