Simpleswap crypto is a Non-Custodial Cryptocurrency Exchange Built Around Deposit-to-Payout Swaps

Moving a balance from Bitcoin to Ethereum

A SimpleSwap order gives a self-custody user a two-transfer lifecycle: a Bitcoin deposit leaves one wallet, and an Ethereum payout enters another. A Coinbase route normally separates deposit, trade, and withdrawal, while a Uniswap trade remains on one EVM network unless it’s paired with a bridge such as Across. Within this Simpleswap crypto lifecycle, one Exchange ID binds the deposit TXID, conversion state, and final payout or refund.

Fixed-rate lock versus floating-rate settlement

SimpleSwap rate selection controls how the deposited amount maps to the incoming balance after the order enters the blockchain.

A SimpleSwap fixed-rate order locks the quoted rate for 20 minutes and requires at least 1 blockchain confirmation within that window. The timer starts when the order is created, not when your wallet broadcasts. Your deposit-side network fee sits outside the order amount, while the receiving-side network fee is included in the displayed fixed-rate payout. A floating-rate order removes the strict rate-lock window and upper amount restriction, yet its displayed receiving amount remains an estimate until conversion.

Worked example: use three hypothetical inputs - a 0.010 BTC order deposit, a 0.32 ETH fixed-rate payout, and a 0.0001 BTC wallet fee. The sending wallet debits 0.0101 BTC because the network fee doesn’t reduce the specified deposit. SimpleSwap credits 0.010 BTC. If the required confirmation lands before minute 20, the receiving wallet gets 0.32 ETH. The concrete wallet outflow is 0.0101 BTC, and the terminal ETH balance change is 0.32 ETH. Under a floating rate, the 0.32 ETH figure would remain an estimate until processing before settlement completes.

Broadcasting the exact asset on the exact network

A SimpleSwap deposit must match the order’s asset, network, amount threshold, address, and any required routing identifier.

An address alone can’t identify an EVM settlement rail. An Ethereum account address contains 20 bytes, written as 40 hexadecimal characters plus the 0x prefix for 42 characters total. The same 42-character shape appears on Ethereum chain ID 1, OP Mainnet 10, BNB Smart Chain 56, Polygon PoS 137, Base 8453, and Arbitrum One 42161. Those identifiers matter when a wallet lets several EVM networks share the same account string. The network selected in the order determines which ledger must record the deposit for that order.

The deposit amount is the order amount; the wallet’s network fee is a separate debit. For USDT, ERC-20 on Ethereum and TRC-20 on TRON are distinct rails despite sharing Tether’s ticker. Copy the generated deposit address after the order exists, use it for that order only, and send at least the displayed minimum. A small test below that threshold creates a different problem because the order expects the full qualifying deposit.

How do I read the exchange status?

Typically, SimpleSwap’s exchange status shows whether your action, the blockchain, the converter, or the payout controls the next step.

Nine main labels cover the standard route: Pending deposit, Confirming, Exchanging, Sending, Finished, Failed, Verifying, Expired, and Refunded. Pending deposit waits for your transfer. Confirming waits for the network. Exchanging and Sending belong to conversion and delivery. Finished and Refunded are terminal outcomes. Failed, Verifying, and Expired require an order-level response rather than another blind transfer. A tenth label, New Swap Created, applies when SimpleSwap replaces an inconsistent order with a new one.

One Exchange ID identifies the service order, whereas each blockchain movement has its own independent TXID.

Bitcoin encodes a TXID as a 32-byte hash, normally displayed as 64 hexadecimal characters. An EVM transaction hash is also 32 bytes and appears as 66 characters after its 0x prefix. Query the deposit hash with Mempool for Bitcoin, Etherscan for Ethereum, Arbiscan for Arbitrum One, or Solscan for Solana. The explorer shows whether a transfer exists and confirms; SimpleSwap status shows whether the service recognized and processed it. Together, those views separate blockchain progress from the exchange’s internal state.

Record the deposit TXID before conversion and the payout TXID after Sending. The pair establishes the route between two independently settled wallet movements.

Reconciling the received balance

A SimpleSwap payout closes successfully when the receiving wallet shows the correct asset on the selected network. Bitcoin expresses 1 BTC as 100,000,000 satoshis across 8 decimal places; Ethereum expresses 1 ETH as 10 ¹⁸ wei across 18 decimals. XRP uses 1,000,000 drops per XRP, while Stellar uses 10,000,000 stroops per XLM. Token contracts set their own decimals, so a wallet’s rounded display should be checked against the payout TXID’s raw amount.

Refund path after an order stops

A SimpleSwap refund returns the deposited asset through a separate blockchain transaction after the order qualifies for that outcome.

In the simplest case, SimpleSwap’s refund procedure allows up to 31 calendar days for processing and limits unclaimed-fund recovery assurances after 1 calendar year. Two address paths exist: the original sending address and a separately supplied refund address. The service can restrict a return to the original address, and it can request evidence linking the deposit to the requester. Keep the Exchange ID, deposit TXID, asset, network, amount, and accessible return address together because each item describes a different part of ownership and routing.

Refunded means the return has become the order’s terminal route; the receiving wallet still waits for the refund transaction to confirm. Once the original deposit is confirmed, routine cancellation no longer resembles abandoning an unfunded order. The refund TXID, rather than the status label alone, closes the on-chain record.

Late deposits, repeated sends, and routing identifiers

Late SimpleSwap deposits and repeated transfers change the order context, so the original Exchange ID must remain attached to every follow-up action.

A late fixed-rate deposit can move the order to Failed when the locked quote no longer applies, after which the available paths are a refund or completion at a new rate. A second transfer to the same deposit address isn’t a second valid order, because SimpleSwap generates that address for the specific transaction. If a replacement order appears as New Swap Created, retain both Exchange IDs and distinguish their deposit instructions before moving any additional balance.

Shared receiving accounts add another routing field. An XRP Ledger Destination Tag is a 32-bit unsigned integer, spanning 0 through 4,294,967,295. Stellar defines a MEMO_ID as a 64-bit unsigned integer, a MEMO_TEXT of up to 28 bytes, and hash-based memos of 32 bytes. Copy the exact tag or memo when the order requests it; the wallet address alone doesn’t identify the intended sub-account.

The Simpleswap crypto order remains the reliable grouping object across a late deposit, a changed rate, a replacement order, and the final unwind.