Simpleswap is a Cryptocurrency Exchange Service With a Deposit-to-Receipt Checklist

Price the deposit before committing it

A Simpleswap quote exposes three economic inputs: the receiving estimate, the sending wallet’s network fee, and the selected rate mode. A fixed quote incorporates the payout network fee into the displayed receive amount, while the wallet pays its deposit transaction fee separately. A floating quote leaves the final output market-set; execution rate, liquidity, and confirmation time drive the difference. Check the displayed minimum and requested deposit amount for this order because both are live values. Fixed mode prioritizes a defined output, while floating mode prioritizes timing flexibility.

Build the receiving route before creating the order

The recipient route needs a wallet address, an exact network match, and any account-level identifier before a Simpleswap order is created.

Recipient address and network

Copy the address from the receiving wallet’s deposit screen, then pair it with the network name shown beside the asset.

Matching a 0x address alone doesn’t resolve the route, because Ethereum, BNB Smart Chain, Polygon PoS, Arbitrum One, Base, and Avalanche C-Chain share EVM-style encoding. Their EIP-155 chain IDs are 1, 56, 137, 42161, 8453, and 43114, respectively. An EIP-55 Ethereum address carries 20 bytes as 40 hexadecimal characters, or 42 characters with the 0x prefix. These identical shapes don’t make the ledgers interchangeable. If a quote names USDT on Ethereum, select the ERC-20 route; USDT on TRON requires the TRC-20 route.

Memo and tag

Shared-account destinations add a second routing field. An XRP destination tag is a 32-bit unsigned integer, covering 0 through 4,294,967,295. Stellar supports a 64-bit unsigned Memo ID, while its hash memo holds 32 bytes. Copy the identifier exactly when a hosted wallet supplies it: the address identifies the service, while the tag or memo identifies the customer account. Follow the receiving wallet’s instructions when no extra field appears.

Refund route

Add a refund address on the deposit asset’s original network when the order presents that field. Simpleswap’s order terms treat the sending address as the refund address when none is supplied, yet exchange withdrawals and smart-contract sends don’t always return cleanly to their source. A separately entered self-custody address provides a clearer return route. Check it with the same asset-and-network test used for the recipient, then save it beside the Exchange ID.

Which rate mode fits the transfer?

The rate mode should match the transfer’s timing constraint: fixed for a defined output, and floating for a flexible send window and market-set result.

Fixed-rate timing

A Simpleswap fixed-rate order locks the quote for 20 minutes and requires at least one blockchain confirmation within that window. The clock covers confirmation, not merely wallet broadcast, so a slow Bitcoin deposit or a low-priority Ethereum fee creates a timing mismatch. Use fixed mode when the recipient needs the stated amount and the sender can fund immediately.

Floating-rate flexibility

A floating-rate order shows an estimate rather than a locked receive amount. Its final output is calculated during processing from the market rate, liquidity, and confirmation time. Floating mode places no strict sending-time or upper-amount restriction on the order, although the displayed minimum still applies. Choose it when the sending schedule is uncertain and movement in the output amount is acceptable.

A funded wallet and preselected network make the 20-minute fixed window realistic; an unprepared sender has more room with floating mode.

Fund the single-use deposit correctly

A Simpleswap deposit should be one exact transfer of the named asset and network to the address generated for that Exchange ID.

Amount and asset precision

Enter the amount from the order into the sending wallet, then check whether the wallet adds its network fee or subtracts it. Bitcoin represents BTC to 8 decimal places, with 1 satoshi equal to 0.00000001 BTC. Ether uses 18 decimal places, and 1 wei equals 0.000000000000000001 ETH. Those units explain tiny balance remainders; the order amount still governs the required deposit.

USDT uses 6 decimal places on its established ERC-20 and TRC-20 contracts, while transaction fees spend ETH on Ethereum or TRX on TRON. Keep enough native asset outside the token amount to broadcast. If a Bitcoin wallet offers “subtract fee from amount,” leaving it enabled reduces the deposit output below the entered figure. Fund the mining fee from the remaining wallet balance instead. Send the transfer once, because a second payment creates a separate on-chain event the original order doesn’t request.

Transaction proof

Save the Exchange ID before sending, then capture the deposit TXID after broadcast. A Bitcoin TXID contains 32 bytes and displays as 64 hexadecimal characters. An EVM transaction hash also contains 32 bytes; with its 0x prefix, the displayed form has 66 characters. These two identifiers serve different systems: the Exchange ID locates the Simpleswap order, while the TXID locates the deposit on its blockchain. Together, they connect the wallet broadcast to the order record.

Track the handoff through each status

The exchange tracker maps the deposit-to-payout handoff, while the blockchain explorer proves what has actually settled on each network.

The core forward path has five states. “Pending deposit” means the service is waiting for the transfer. “Confirming” means the deposit has appeared and is accumulating the required network confirmations. “Exchanging” marks conversion through the selected liquidity route, and “Sending” marks preparation or broadcast of the payout. “Finished” closes the service record after the outgoing transfer. Failed, Verifying, Expired, and Refunded are branch states rather than progress steps; preserve the order and transaction identifiers when any branch appears.

Read the tracker and both blockchain records together, then retain the Exchange ID, deposit TXID, and payout hash until the wallet receipt agrees.

How do you confirm the wallet receipt?

Wallet receipt is confirmed by matching the payout hash, network, recipient address, asset, and amount against the completed Simpleswap order.

Open the payout transaction on the explorer for the selected network. A Bitcoin payout should create an output for the recipient’s script or address. An ERC-20 payout should show a Transfer event from the token contract to the recipient, while native ETH appears as a value transfer. For TRC-20 USDT, inspect the token transfer on TRON rather than an Ethereum explorer. The same ticker on another chain doesn’t satisfy the order.

Compare the wallet’s balance change with the explorer record. A portfolio total might refresh later, so use the transfer amount and recipient address as primary evidence. One confirmation is the fixed-rate timing threshold for the incoming deposit, not a universal spending-finality rule for every payout. Receipt confirmation ends when the wallet, explorer, and completed order agree.

Resolve edge cases, then close the record

Edge cases stay contained when the next action follows the transaction’s observable state rather than a fresh guess. If no deposit was broadcast, leave the unused order and create a new quote. If a TXID exists, don’t send a replacement while the first transfer remains unresolved. Preserve the Exchange ID, deposit TXID, requested network, and refund address for a Failed, Verifying, Expired, or Refunded branch. After the payout matches on-chain, archive both hashes and remove the generated deposit address from saved recipients. That documented exit is stronger than treating the Finished badge as sole receipt proof.