Do I need a customer account to revisit a tracked Simpleswap exchange?

No customer account is required to revisit a standard crypto-to-crypto exchange when you saved its exchange ID or tracking link. A registered account adds exchange history, which is useful across devices and after browser history is cleared. Without an account, the unique ID remains the direct lookup key for that one swap. Store it with the deposit TXID and payout TXID until the wallet balance and Finished status agree.

Can browser history recover a Simpleswap exchange ID?

Browser history can recover the exchange page when the original address-bar entry remains available. The exchange ID appears in the tracking information and may also sit inside that saved page address. Open the matching entry, then copy the alphanumeric ID into your transaction record. Browser history is a convenience rather than a durable archive, because cleared history, private browsing and device changes remove that route back to the exchange.

Does refreshing the status page create another swap or payment?

Refreshing the status page only retrieves the record attached to the existing exchange ID. It does not sign a wallet transaction, broadcast another deposit or create a second order. A new swap begins only when the exchange flow creates a new exchange ID and deposit instruction. Compare the ID before sending again, especially when several browser tabs show the same BTC-to-ETH pair simultaneously.

Which timestamp should identify a completed exchange in personal records?

Use the confirmed payout transaction time as the settlement timestamp, then retain the Simpleswap Finished status as supporting workflow context. The service status marks completion inside the exchange process, while the receiving blockchain records when the payout entered its ledger. If a wallet displays a later notification time, that reflects local indexing rather than a second settlement. Keep both timestamps when reconciliation rules require an application time and an on-chain time.

Can I track the exchange without connecting my wallet?

Yes, the exchange ID tracks the Simpleswap workflow without a persistent wallet connection. The sending wallet broadcasts the deposit independently, and the receiving wallet displays the payout after its chain settles. Tracking still needs the exchange ID for service status and the two TXIDs for blockchain evidence. Wallet connectivity affects how conveniently data moves between screens; it does not replace the identifiers attached to the exchange.

Is the exchange ID sufficient when support needs transaction details?

The exchange ID is the primary lookup key, but a complete request also includes the relevant blockchain TXID. Add the asset, selected network, sent amount and receiving address so the record can be matched without ambiguity. For a payout question, provide the payout TXID if one exists; for a deposit question, provide the deposit TXID. Include any required XRP destination tag or Stellar memo when attribution is part of the issue.

Why do two swaps for the same pair move through statuses at different speeds?

Two swaps share a ticker pair without sharing the same blockchain conditions or provider route. Deposit confirmation speed reflects source-network blocks and fee selection, while Exchanging reflects route execution and Sending reflects payout-chain broadcast. A BTC-to-ETH swap and another created later can therefore spend different periods in each status. Compare each exchange ID with its own deposit and payout TXIDs instead of using the earlier swap as a timer.

Simpleswap

Simpleswap is tracked from deposit to wallet receipt with one exchange ID

Simpleswap is a crypto swap service whose exchange ID links one order to its deposit, confirmation, conversion, payout and wallet receipt. Save the alphanumeric ID as soon as the exchange page creates it. The ID retrieves the service-side status, while the deposit and payout transaction hashes show the two on-chain movements.

August 2026 Last updated:

Following those three identifiers together separates service processing from blockchain settlement. The sections below map each status, the figure to compare and the point at which the receiving wallet becomes the final record.

Cost signals recorded before status tracking begins

The Simpleswap tracking record begins with two cost signals: the quoted receive amount and the deposit network fee charged by the sending wallet.

For a fixed-rate exchange, the displayed receive amount already incorporates the payout-side network fee. The sending wallet pays its own chain fee when it transmits the deposit. Simpleswap does not publish a classical percentage commission for crypto-to-crypto swaps; its exchange economics sit inside the offered rate. That makes the saved quote and final receive amount the two figures worth comparing after completion.

The fixed rate remains locked for 20 minutes and requires at least 1 blockchain confirmation within that window. A floating rate has no strict time limit; its receive figure is an estimate recalculated during processing. The minimum deposit is pair-specific and shown before sending because network economics set a usable floor. Record four items at creation: send amount, estimated receive amount, rate type and minimum deposit. Those four values explain later changes without turning the tracking page into fee arithmetic. The final visible comparison belongs between the quoted receive amount and the wallet’s settled balance.

The three identifiers to save before sending

A complete Simpleswap record uses three identifiers: the exchange ID, the deposit TXID and the payout TXID created near completion.

Capture the exchange ID

Save the alphanumeric exchange ID immediately. It identifies one swap and restores its status page without requiring a customer account.

Record the deposit TXID

The deposit TXID is written by the source blockchain, not by the exchange page. Bitcoin TXIDs are 32-byte hashes displayed as 64 hexadecimal characters. Ethereum transaction hashes are also 32 bytes and appear with a 0x prefix, yielding 66 visible characters. The exact string lets Etherscan, Blockchair or another explorer answer whether the deposit entered a block.

Keep the payout TXID

The payout TXID appears when the receiving-chain transfer is broadcast. Keep it beside the exchange ID, because it proves a different movement. A BTC-to-ETH swap therefore creates a Bitcoin deposit TXID and an Ethereum payout hash; neither substitutes for the service’s exchange ID.

Pending deposit starts with the exact chain and address

Pending deposit means Simpleswap has created the order and is waiting to detect the selected asset at its displayed deposit address.

The deposit address must match both the asset and selected network. A USDT deposit on Ethereum follows ERC-20 token handling, while USDT on TRON uses TRC-20 and USDT on Solana uses its SPL token program. Choose by chain, not ticker alone. Send the exact asset to the displayed deposit address and include any required memo or tag. The minimum shown on the order remains the lower usable amount; deposits below it do not support a normal completion path. The exchange ID ties those four destination details to one record before the wallet broadcasts anything.

After broadcast, copy the deposit TXID from the sending wallet and open it in the matching explorer. Confirm the destination, asset, network and amount against the exchange record. The transition occurs when the service detects the qualifying deposit on the selected chain and begins counting its required confirmations.

What does confirming mean for the deposit?

Confirming means Simpleswap has detected the deposit and is waiting for the source network to reach its required confirmation threshold.

Confirmation counts advance differently across chains because each network packages transactions on its own schedule. Bitcoin targets a block about every 10 minutes: 1 confirmation means the transaction sits in one block, while 6 confirmations represent six blocks built in sequence. Ethereum divides time into 12-second slots and groups 32 slots into one 6.4-minute epoch; an empty slot adds no block. TRON uses 3-second slots under normal production conditions. These protocol clocks explain the pace visible in Etherscan, Blockchair and Tronscan, but Simpleswap changes status only after its configured deposit threshold is met.

The explorer’s first confirmation starts the chain count; it does not guarantee the service threshold has been reached. Match the TXID, watch additional blocks and leave the exchange ID unchanged. Confirming ends when the route accepts the deposit as sufficiently settled.

Exchanging and sending separate conversion from payout

Exchanging and Sending mark two separate tasks within Simpleswap: provider-side asset conversion first and receiving-chain payout creation second.

Conversion belongs to exchanging

Exchanging begins after the required deposit confirmation and marks conversion of the deposited asset into the chosen output asset. A public explorer has no second-chain payout to inspect yet. The exchange ID remains the main lookup key because provider processing occurs between the two blockchain transfers.

Payout broadcast belongs to sending

Sending begins while the payout transaction is being constructed or broadcast on the receiving network. Once a payout TXID appears, follow that chain. An ERC-20 transfer exposes its token contract, recipient and amount in Etherscan, while an SPL transfer exposes corresponding token movement in Solscan.

Compare the payout asset, network, destination and amount with the saved order before updating the wallet record. Sending reaches its practical limit at broadcast; the receiving blockchain then determines inclusion and settlement.

Finished status and the wallet receipt

Finished means Simpleswap has completed its exchange workflow; wallet receipt requires the payout transaction to settle and the wallet to index it.

Token units can make the same settled amount look different across interfaces. Bitcoin records 8 decimal places, making 1 BTC equal to 100,000,000 satoshis. Ethereum denominates native value in wei, with 1 ETH equal to 1,000,000,000,000,000,000 wei.

XRP uses 6 decimal places and 1,000,000 drops per XRP. Stellar uses 7 decimal places and 10,000,000 stroops per XLM. A wallet may round those base units or delay token indexing, while the explorer exposes the exact settled value. Compare the same unit, token contract and network before treating a display mismatch as a balance change. Once the exact payout matches the saved receive record, close the swap at wallet receipt rather than at the status word alone.

How do you reconcile exchange status with a block explorer?

Use the exchange ID for service state and the relevant TXID for chain state; neither identifier answers both questions.

Pending deposit: confirm the sending wallet produced a deposit TXID and used the displayed network.
Confirming: compare the explorer’s confirmation count with time since inclusion, not time since wallet broadcast.
Exchanging: follow the exchange ID because conversion sits between the two blockchain transfers.
Sending: open the payout TXID on the receiving chain and watch inclusion or finalization.
Finished: match the recipient, asset or token contract and exact settled amount to the saved exchange record.

Etherscan indexes Ethereum and ERC-20 transactions, Solscan covers Solana, Tronscan covers TRON and XRPScan covers the XRP Ledger. Blockchair can inspect Bitcoin transfers. Choose the explorer by network rather than ticker, because USDT exists on several chains. The service page owns lifecycle labels; the explorer owns on-chain evidence after a TXID exists.

Tags and memos preserve recipient attribution

Destination tags and memos connect one shared receiving address to a specific customer or exchange record, so they remain part of lifecycle tracking.

XRP Ledger source and destination tags use 32-bit unsigned integers, covering values from 0 through 4,294,967,295. Stellar supports 4 memo forms: text, ID, hash and return. Its text memo holds up to 28 bytes, its ID memo stores a 64-bit unsigned integer and its hash forms hold 32 bytes. These values let custodial wallets and exchanges assign one payment arriving at a shared address to the intended internal balance. Record the extra identifier beside the recipient address before creating the exchange. A copied address alone does not preserve that routing instruction.

When a required tag is omitted, the on-chain transfer still reaches the shared address, while attribution needs manual handling. Supply the exchange ID, payout TXID and intended tag when resolving the record. The tag closes the attribution gap between chain receipt and the user balance.

Rate choice explains amount changes across the lifecycle

Rate type explains why the amount can change between exchange creation and wallet receipt even when every lifecycle status advances normally.

A Simpleswap fixed rate locks for 20 minutes and requires at least 1 blockchain confirmation inside that window. The quoted output stays tied to that rate when both conditions are met. A floating exchange calculates output during processing, so its estimate moves with the market rate, route liquidity and confirmation delay.

Worked example: take a hypothetical quoted receive amount of 0.05000000 ETH and a hypothetical 2% downward rate movement before a floating exchange executes. Multiply the estimate by 0.98. The calculation is 0.05000000 × 0.98 = 0.04900000 ETH, producing a concrete rate-only result of 0.04900000 ETH. The 8-place display supports readable arithmetic; Ethereum still accounts for ETH in 18 decimal places. Keep the original estimate, selected rate type and finished amount in the same exchange record.

Exception statuses and reverse settlement

The lifecycle has 9 named statuses: 5 main stages from Pending deposit through Finished and 4 exception states requiring a separate outcome.

Failed and verifying pause the normal path

Failed indicates the exchange did not complete, while Verifying indicates additional monitoring. Preserve the exchange ID and deposit TXID before contacting support. Those two identifiers locate the service record and its source-chain transfer without creating a second order for the same deposit.

Expired marks a missed action window

Expired means the required action did not complete within the order’s available time. If the wallet never broadcast a deposit, create a fresh exchange with a new ID. If a deposit TXID exists, keep the expired record intact so the sent funds remain tied to one traceable order.

Refunded starts a reverse chain movement

Refunded means the deposit is being returned or has been returned on its original network. The refund transaction has its own TXID, separate from the deposit TXID. Add that hash to the same exchange record and close the lifecycle against the balance restored by the refund.

Closing the exchange record after receipt

A Simpleswap exchange is fully closed when Finished aligns with a confirmed payout TXID and the receiving wallet shows the expected asset balance, as documented in Simpleswap rewards.

Archive six fields: the exchange ID, deposit TXID, payout TXID, asset-and-network pair, sent amount and received amount. For an ERC-20 receipt in MetaMask, add the token contract used to display the balance. For native BTC in Exodus, keep the 64-character transaction ID and final satoshi amount. Tangem users should retain the same chain-specific evidence beside the swap record. This compact bundle reopens the exact service state and both blockchain movements without reconstructing them from memory. Once the wallet balance, payout TXID and Finished record agree, the exchange lifecycle is closed.

Simpleswap questions worth asking

Do I need a customer account to revisit a tracked Simpleswap exchange?: No customer account is required to revisit a standard crypto-to-crypto exchange when you saved its exchange ID or tracking link. A registered account adds exchange history, which is useful across devices and after browser history is cleared. Without an account, the unique ID remains the direct lookup key for that one swap. Store it with the deposit TXID and payout TXID until the wallet balance and Finished status agree.
Can browser history recover a Simpleswap exchange ID?: Browser history can recover the exchange page when the original address-bar entry remains available. The exchange ID appears in the tracking information and may also sit inside that saved page address. Open the matching entry, then copy the alphanumeric ID into your transaction record. Browser history is a convenience rather than a durable archive, because cleared history, private browsing and device changes remove that route back to the exchange.
Does refreshing the status page create another swap or payment?: Refreshing the status page only retrieves the record attached to the existing exchange ID. It does not sign a wallet transaction, broadcast another deposit or create a second order. A new swap begins only when the exchange flow creates a new exchange ID and deposit instruction. Compare the ID before sending again, especially when several browser tabs show the same BTC-to-ETH pair simultaneously.
Which timestamp should identify a completed exchange in personal records?: Use the confirmed payout transaction time as the settlement timestamp, then retain the Simpleswap Finished status as supporting workflow context. The service status marks completion inside the exchange process, while the receiving blockchain records when the payout entered its ledger. If a wallet displays a later notification time, that reflects local indexing rather than a second settlement. Keep both timestamps when reconciliation rules require an application time and an on-chain time.
Can I track the exchange without connecting my wallet?: Yes, the exchange ID tracks the Simpleswap workflow without a persistent wallet connection. The sending wallet broadcasts the deposit independently, and the receiving wallet displays the payout after its chain settles. Tracking still needs the exchange ID for service status and the two TXIDs for blockchain evidence. Wallet connectivity affects how conveniently data moves between screens; it does not replace the identifiers attached to the exchange.
Is the exchange ID sufficient when support needs transaction details?: The exchange ID is the primary lookup key, but a complete request also includes the relevant blockchain TXID. Add the asset, selected network, sent amount and receiving address so the record can be matched without ambiguity. For a payout question, provide the payout TXID if one exists; for a deposit question, provide the deposit TXID. Include any required XRP destination tag or Stellar memo when attribution is part of the issue.
Why do two swaps for the same pair move through statuses at different speeds?: Two swaps share a ticker pair without sharing the same blockchain conditions or provider route. Deposit confirmation speed reflects source-network blocks and fee selection, while Exchanging reflects route execution and Sending reflects payout-chain broadcast. A BTC-to-ETH swap and another created later can therefore spend different periods in each status. Compare each exchange ID with its own deposit and payout TXIDs instead of using the earlier swap as a timer.