Simpleswap Exchange Changes Before and After Funds Move
Before funds leave your wallet, you can stop using an unpaid Simpleswap exchange and create a corrected one. After you send funds to the assigned deposit address, the available action depends on the order status, blockchain finality, and any review already in progress. The Exchange ID, order status, and any deposit, payout, or refund TXIDs then distinguish a completed swap from a delay, failure, changed outcome, or returned deposit.
Control, progress, and proof in one exchange record
The exchange record serves different purposes as the order advances. Before payment, it preserves the pair, rate type, amount, destination, and any extra identifier for a final check. During processing, it shows the service state. After an exit, it ties the order to the relevant blockchain transactions.
| Order state | Available action | Evidence already needed |
|---|---|---|
| Before deposit | Leave the order unused and create a corrected one | Saved order details and confirmation in the sending wallet that no transfer was broadcast |
| Confirming, exchanging, or sending | Track progress or ask support to review an exception | Exchange ID and deposit TXID |
| Finished, failed, or refunded | Reconcile any payout or refund, or ask support to review a failed order | Exchange ID plus every issued TXID |
These states do not offer equivalent control. A form value remains easy to replace while no transfer exists. A processing label describes work already attached to a deposit, so it is not an invitation to edit the order. A Finished or Refunded label narrows the task to proving where funds went and whether the recorded exit matches the blockchain.
The deposit as the commitment boundary
The deposit transfer changes a prepared order into an on-chain event. Until that transfer, closing the exchange does not require a cancellation request; a new order can carry the corrected values. Once the wallet broadcasts funds, the original order and its assigned deposit address become part of the evidence trail.
Blockchain finality sets the harder limit. A wallet or network might leave a transfer pending for some time, yet the exchange cannot promise to cancel it. A confirmed deposit cannot be pulled back or redirected. At that point, the service may process the order, pause it, create an approved replacement, or return eligible funds through a separate transaction.
Which details can still change?
Before the deposit, create a new exchange if the asset, network, amount, rate type, recipient address, refund address, or required memo is wrong. Sending values that differ from the saved order can make the deposit inconsistent with that order.
Changes are unavailable while an order is confirming, exchanging, or sending. A failed order requires a case-specific review, and support may request proof before approving a change. Simpleswap may create a new swap when a deposit conflicts with the original order, including a wrong asset, wrong network, or second deposit, but that remedy is discretionary rather than guaranteed.
Rate commitments and late deposits
Fixed-rate commitment
The fixed-rate option makes time part of the commitment. It protects the displayed receiving amount only when the deposit meets the stated rate conditions, so wallet confirmation speed matters before funds move.
Inside the rate window
A fixed rate is locked for 20 minutes, and the deposit must gain at least one blockchain confirmation within that window for the exchange to use it. Sending near the end leaves less time for the network to confirm. The wallet broadcast time alone does not satisfy that condition.
After a late arrival
A late deposit does not create one automatic outcome. If the quoted rate has not changed, the order may continue at that rate. If it has changed, the exchange may fail and present a refund or completion at a new rate. Treat a revised amount as settled only after you accept completion at the new rate.
Floating-rate outcome
The floating-rate option keeps the receiving amount provisional until processing. Market movement, liquidity, and confirmation time can move the final output above or below the estimate. It has no strict deposit-time or upper-amount restriction, but the displayed minimum, current route availability, and transaction review still apply.
Evidence that survives each state change
The strongest record combines the service identifier with independent blockchain entries. Each item answers a different question, so one screenshot should not replace the underlying transaction data.
Order-side evidence
- The Exchange ID identifies one swap and helps support locate its exchange record.
- The saved order values show the intended asset, network, amount, and recipient.
- A memo, tag, Payment ID, or Extra ID records routing information when required.
- Status labels show whether the service awaits, processes, finishes, fails, verifies, expires, or refunds the order.
Chain-side evidence
The deposit TXID records the transfer the sending wallet broadcast on the selected network. A payout TXID shows the destination and amount the service dispatched. A refund TXID records a separate return transfer. Keep these identifiers private except when sharing them through a trusted support channel, since the combined record can expose transaction history and invite impersonation attempts.
Reconciliation when the displayed amount changes
A changed output needs a line-by-line comparison, not an assumption about one fee. Start with the amount the deposit TXID delivered, then compare the order estimate, rate type, payout TXID, and value received at the destination. This separates an input shortfall from a floating-rate movement or an incomplete payout.
For a fixed-rate order, the displayed receiving amount includes the network fee for sending the exchanged asset. The sending wallet can still charge its own deposit-side network fee. For a floating-rate order, the receiving amount remains an estimate until execution, and network conditions can affect the final calculation.
A Finished label closes the service workflow, but the payout TXID supplies the chain evidence. If the destination record and service status disagree, preserve both rather than recalculating the swap from a current market quote. A later quote does not reconstruct the rate or conditions applied to the original order.
Failure, verification, and refund exits
Failed, Verifying, Expired, and Refunded describe different states. None of the first three proves a refund has reached a wallet.
A Failed status means processing stopped. A Verifying status means monitoring or client checks are underway and can require identity or source-of-funds information. Expired records show a required action missed its applicable time.
Refund eligibility depends on the deposit and order history. Wrong networks, missing mandatory identifiers, expired fixed-rate deposits, or amounts below the shown minimum can restrict recovery. Even an eligible return creates a new blockchain transaction rather than reversing the original deposit.
A refund may go to the supplied refund address or the original sending address. The service can limit the exit to the original address, request ownership evidence, deduct a network fee, or apply a recovery charge in some cases. The Refunded status and refund TXID together provide the useful completion proof.
Unsupported inputs and recovery limits
An address can be syntactically valid yet wrong for the chosen asset or network. A missing memo can also prevent a custodial recipient from assigning the payout to the intended account. Once either mistake reaches the chain, editing the order cannot rewrite the transaction data, and recovery may depend on the receiving platform or a case-specific service review.
The assigned deposit address belongs to one exchange. Sending another payment to it does not extend the first order, and a refund is not guaranteed. If a mismatch occurs, preserve the order values and TXID before seeking review. Repeated transfers or attempts to repair the amount can add another transaction without resolving the first discrepancy.
Completion proof and the final record
Completion requires agreement between the order exit and the relevant blockchain record.
For a normal payout, Finished should align with a payout TXID directed to the recorded recipient. For a return, Refunded should align with a refund TXID directed to the accepted refund destination. A wallet interface may update later than the chain, so the transaction record remains the better first check.
Keep the original Exchange ID, deposit TXID, final TXID, and the accepted address or memo together until reconciliation ends. If the evidence shows the expected asset on the expected network at the expected destination, and the received amount matches the order's final recorded outcome, the record supports a completed exit. If any element differs, it identifies the exact mismatch for support instead of reopening every choice in the order.
After funds move, a clean evidence chain replaces the correction freedom available before deposit.
Helpful answers about Simpleswap
Can a failed exchange be changed instead of refunded?
A failed exchange may qualify for a corrected order, completion under revised terms, or a refund, depending on its history. There is no automatic right to edit the original record. Support can request additional confirmation before choosing an available path, and Simpleswap may create a replacement swap at its discretion. Treat the new terms as accepted only after the exchange record identifies the approved outcome.
What happens if the same deposit address receives a second transfer?
That deposit address was assigned to one exchange, so a second transfer does not automatically extend or repeat the order. Simpleswap may create a new swap when it detects another deposit, but it does so at its discretion. Preserve both transaction IDs and the Exchange ID, then request a review. Do not send another transfer in an attempt to make the first one match.
Where does a refund go when no refund address was entered?
The original address from which the deposit was initiated becomes the refund address when no separate address was supplied. The service may require that original address even when another destination would be more convenient. Before treating the return as complete, compare the refund TXID with the accepted destination and confirm the transfer on the relevant blockchain.
Which evidence may be requested to prove deposit ownership?
Evidence can include screenshots, video confirmation, transaction checks, account statements, and documents showing an eligible source of funds. The exact request varies by case. The Exchange ID and deposit TXID identify the order and transfer, but they may not prove control of the sending account by themselves. Provide sensitive material only through a trusted support channel and keep it out of public messages.
Are network fees deducted from refunded funds?
Network fees may be deducted from the original deposit when an eligible refund is sent. If the refunded asset is a token rather than the network's native coin, an additional payment in the native coin may be required to cover the return transaction. A recovery charge can also apply in some cases, so the refunded amount can be lower than the original deposit.
Does a Verifying status mean the deposit has been refunded?
No. Verifying records an active monitoring or client-check stage, not a completed return. The review may request identity, address, source-of-funds, or transaction information before an outcome is selected. A refund becomes distinguishable only when the order reaches Refunded and a return transaction exists. Until then, neither cancellation nor payout should be inferred from the Verifying label.
When should a third-party recipient's rejection be escalated?
Escalate the issue promptly when a third-party recipient rejects the payout or fails to process it. Do not ask that recipient to send the assets back to the address shown as the payout source, because it may not be a reusable return address. Supply the Exchange ID, payout TXID, recorded recipient, and rejection details through a trusted support channel.
Could an amount above the order value be processed unchanged?
An amount above the order value is not guaranteed to be processed under the original terms. The service may cancel the order and offer a refund when the transferred amount exceeds the applicable network fee, or it may handle the mismatch through a new order at its discretion. Keep the TXID and avoid treating the quoted output as valid until the exchange record shows the accepted path.