How a Non-Custodial Crypto Swap Actually Works

The moment you hit confirm, your wallet starts talking to the blockchain, not to the swap site. A swap platform may show a friendly “Waiting for deposit” screen, but in reality your coins have not gone anywhere yet — your wallet is simply constructing and broadcasting a transaction to the public network. Here is what actually happens in those first few seconds, whether you use SimpleSwap, FixedFloat, or any other non-custodial exchange.

Think of it like handing a package to a courier. The swap platform creates a shipping label — a deposit address it controls for this one swap — but the package does not leave your hands until the courier scans it and starts moving. In crypto, that scan happens when the transaction is broadcast to the mempool, not when the platform displays your deposit address.

The order is created, but custody has not changed

A non-custodial swap begins with a quote request. You tell the platform what you want to send and what you want to receive, and it replies with a deposit address and an expected rate. That address is typically generated for your order alone, and it is the only thing tying your future transaction to that swap. Until your transaction is actually broadcast, the platform cannot move, hold, or see your coins beyond what the blockchain already shows publicly.

This is the moment where a common mistake appears: users copy the deposit address, go back to their wallet, and wait too long before sending. The quote has an expiry window, and once it passes, the same address may no longer be valid, or the rate may update. For real-time conditions, check the official site of the platform you are using — rate windows, address reuse, and minimum amounts differ between services like StealthEX, LetsExchange, and SideShift.ai.

What your wallet does after you press confirm

1. You press confirm

   The wallet builds a signed transaction that spends your chosen coins to the deposit address

2. Transaction is broadcast

   The signed transaction is sent to the blockchain network and appears in the mempool

3. The network sees it

   Miners or validators check that the transaction is valid and include it in a block

4. The swap platform sees it

   Once the transaction appears in a block with the required number of confirmations, the platform recognises your deposit as received

Notice who is not involved until the last step: the swap platform itself. A non-custodial service does not receive your coins the way a bank receives a wire. It only notices your deposit after the blockchain has already accepted it. That detail matters because it means the platform’s website, server status, and support team are not part of those first seconds at all.

It also explains why the “processing” stage can feel slow even when the site is snappy. Your wallet may show the transaction as sent within a second or two, but the platform will normally wait for the transaction to be included in a block, and often for several additional confirmations, before it considers the deposit final. That is not a delay caused by the swap service — it is the blockchain reaching consensus that your coins have genuinely moved.

Why address locking comes before custody

The deposit address is “locked” to your quote at the moment the order is created, not when your coins arrive. That lock tells the platform which rate, which receiving address, and which output asset belong to that particular incoming transaction. If your coins arrive after the lock expires, the platform may still detect them, but the terms of the original quote may no longer apply.

In practice, this means you should treat the whole swap — from quote to broadcast — as one continuous action, not as two separate visits. Copying a deposit address in the morning and sending coins in the evening can produce a mismatch: the rate has moved, the address has expired, or the minimum amount is no longer the one you saw earlier. The safest habit is to generate the quote only when your wallet is open and you are ready to send immediately.

1. Your walletThe only party that can spend your coins before broadcast
2. The public mempoolWhere the signed transaction waits until picked up in a block
3. The blockchain networkConfirms the move; no swap platform can alter or reverse it
4. The swap platformDetects the confirmed deposit and matches it to your order
5. The receiving addressWhere the swapped coins will later be sent by the platform

One more thing to watch in those first seconds: the network fee you choose in your wallet. If you set it too low, your transaction may sit in the mempool longer than the quote window allows. The swap platform is not checking on you and cannot remind you — it only sees an incoming transaction eventually, or it sees nothing at all. Choose a fee that is adequate for current network conditions, and if you are unsure what “adequate” means right now, check your wallet’s own fee estimate rather than relying on the swap site’s displayed numbers.

A swap quote is never a single price. It is a pair of numbers: the amount you send and the amount you are supposed to receive, valid for a window that can stretch or shrink depending on how the service matches orders across two independent networks. Once you understand that window, you understand why the number on the confirmation screen sometimes differs from what lands in your wallet.

Think of the rate as a handshake between two ledgers that do not talk to each other. Bitcoin does not know what Ethereum is doing, and neither network knows you are swapping. The swap service steps in as the translator. It watches prices on external markets, applies its own margin, and prints a quote that says: send X on network A, get Y on network B. That quote is not a promise about the blockchain — it is a promise about the service’s own order book or liquidity pool.

Floating versus fixed: two ways to pin the same number

With a floating quote, the displayed rate is an estimate. The service recalculates it while your deposit is being confirmed, and the final payout follows the market at the moment the swap actually executes. That is why the amount you receive can drift upward or downward between the preview screen and the transaction itself. It is not a hidden fee; it is the market moving underneath you.

A fixed quote works differently. The service locks the rate for a set amount of time, often several minutes, and guarantees the output if your deposit arrives within that window in the expected amount. The trade-off is that fixed quotes usually carry a slightly wider spread, because the service is taking on the risk that the market moves against it while your coins are still confirming. In practice, that means the fixed quote you see is often a little worse than the floating estimate, but it will not change if you act on time.

1. You click swapthe service snapshots its current buy and sell prices across the two networks
2. The quote window opensa rate is pinned for a limited time, or left floating until the deposit confirms
3. Your deposit landsthe service checks the amount, the network fees, and the elapsed time
4. The rate is finalizedfor fixed swaps, the pinned rate applies; for floating swaps, the current market price replaces the estimate
5. The payout is sentthe service broadcasts the transaction on the destination network with its own fee deducted

Here is a concrete example. You want to swap Litecoin for Monero. The preview says you will receive 14 XMR for 100 LTC, but those are two independent order books. By the time your Litecoin deposit has enough confirmations, the LTC-XMR pair may have moved half a percent. A floating service will update your payout to 13.93 XMR and show you the new amount before sending. A fixed service will still send 14 XMR if your coins arrived inside the quoted window. Both are honest — they are just pricing risk differently.

Why the payout amount rarely matches the preview exactly

Even with a fixed rate, the final received amount can differ from the preview by a few percent once network fees, miner fees, and the destination chain’s own mechanics are accounted for. The quote typically covers the exchange itself. What happens after the service broadcasts the payout is a separate layer: the destination network may charge a fee that reduces what appears in your wallet, or the receiving wallet may display an estimated value based on a different exchange rate than the service used.

The most common user error is reading the preview as a settlement statement. It is not. It is a snap quote taken at the moment the swap request was created. Treat it as a range, not a receipt. What you should actually compare is the minimum guaranteed amount on a fixed swap, or the final amount the service shows you at the confirmation step before it sends the payout.

• Preview screenthe service shows its best estimate based on current market prices
• Deposit broadcastyou send coins from your non-custodial wallet; the preview may already be stale
• Confirmations beginthe service monitors the mempool and its own liquidity; the effective rate starts shifting
• Executionthe swap is filled against the service’s liquidity, and the final amount is calculated
• Payout broadcastthe destination transaction is sent; network fees on the receiving chain are subtracted from what you actually get

When you send coins to a non-custodial swap address, your wallet will usually show the transaction as pending almost immediately. That pending state does not mean the swap service has accepted your deposit yet. It only means your wallet has broadcast the transaction to the network and is waiting for miners or validators to include it in a block.

The swap platform updates its own status separately. First you see something like awaiting deposit, then deposit received, and only later confirming, exchanging, and sending. These labels are not confirmed on-chain events by themselves. They are the platform reflecting what its own system observes.

What "confirmations" actually mean

A network confirmation is not a single event. Each new block added after the one containing your transaction increases the confirmation count. Different blockchains reach practical finality at different depths, and different services request different numbers of confirmations before they consider a deposit spendable. You may see a swap stuck at "confirming" even though your wallet already says "confirmed" once. That happens because the service is waiting for a higher confirmation target.

1. Wallet broadcasts transactionyour address signs and pushes the transfer to the mempool
2. Miner or validator includes it in a blockthe first on-chain confirmation appears
3. Blocks build on topconfirmation count increases toward the platform threshold
4. Platform marks deposit as confirmedthe swap system now treats the coins as spendable
5. Exchange step beginsthe service sends the outgoing asset

Think of confirmations like an airport check-in. Your wallet saying "sent" is like walking into the terminal. A platform saying "confirmed" is like the airline scanning your boarding pass after you have actually reached the gate. Both are real events, but they describe different stages of the same trip.

• Pending in wallet

  The transaction is in the mempool or just got its first confirmation. It is not proof that the swap service can use your coins yet.

• Confirming on platform

  The service counts network blocks until it reaches its own safety threshold. The deposit may still be reversible from the platform's perspective.

• Awaiting deposit

  The address was generated, but the service has not yet seen your transaction in the mempool or on-chain.

• Exchanging

  The deposit passed the confirmation target, and the service moved to the rate execution step.

A common reason for a stalled swap is sending the correct asset but with a fee set so low that the transaction stays in the mempool for a long time. The platform simply has nothing to confirm yet. Another reason is sending the right token but on the wrong network. The coins may move quickly on that wrong chain and look "sent" from your side, while the swap service never sees them on the expected chain.

If the status sits at "awaiting deposit" for an unusually long stretch, check the transaction hash in a public block explorer. If the explorer shows it unconfirmed, the delay is on the network side. If the explorer shows it confirmed but the platform status has not changed, contact the service and share the transaction hash. The hash is the one piece of evidence that lets support look up exactly where your deposit is.

When a no-registration swap gets stuck, it usually comes down to one of three things: the deposit is still confirming, the address changed after you copied it, or the token you sent is not the one the platform expected. The good news is that these failures are rarely final — most can be traced, explained, and recovered through the refund path built into the swap flow itself.

Imagine you paste a Bitcoin address, send the coins, and then the status page keeps saying “Awaiting deposit” long after your wallet shows the transaction as complete. That pause is not necessarily a problem. Non-custodial services wait for on-chain confirmations before touching the rate or releasing the swapped asset. A stubborn status is often just the network moving slower than your expectations. Check the transaction hash in a block explorer before you contact support — you will need that hash either way.

The two failure modes people hit most often

Address reuse is the classic trap. Some interfaces show a fresh deposit address each time you open the swap widget. If you copied an address, closed the tab, reopened it, and then sent funds to the old address from your clipboard, the platform may not match the deposit to an active order automatically. This is not a theft scenario; it is a matching problem. The resolution depends on whether the address still belongs to the platform and whether the support team can link it to your swap.

Sending an unsupported token is a cousin of the same mistake. A swap may list “USDT” as a deposit option, but if that USDT lives on a different network than the one you selected, the coins arrive on the wrong chain. In that case the funds are usually visible on-chain but invisible inside the swap interface. Recovery is possible when the platform controls the receiving address, though it can involve a manual process and a fee — so before you send anything, confirm the network label next to the address, not just the coin symbol.

• Stuck pending deposit — usually a confirmation delay, not a lost transaction
• Changed address after copying — the deposit no longer matches an active order
• Wrong network for a supported token — funds exist on-chain but are not auto-detected
• Unsupported token sent by mistake — recovery depends on platform policy and address ownership

How refunds work across the six listed platforms

The practical difference is not whether a platform can refund — it is how much manual work the specific situation requires. SimpleSwap and LetsExchange are built around order-based support desks, so most stuck cases go through a ticket with your transaction hash. FixedFloat leans on automation: if the order fails cleanly, the return path is usually triggered without a human conversation. SideShift.ai sends coins directly to the address you provide, which reduces the number of steps but also means you must own that address before you start.

When people ask whether a swap “went wrong” because they sent the asset but never received the other side, the first question is always the same: what does the explorer say about your deposit? If the deposit is confirmed and the swap still shows nothing, contact the platform and include the hash. If the deposit is not confirmed, no support team can speed that up. That single distinction resolves more confusion than any other detail in a no-KYC swap.

The platforms Noaml and StealthEX position themselves around privacy, so their order pages tend to show fewer personal data prompts — but a stuck transaction still requires the same evidence: the deposit hash, the address you sent from, and the network you used. Keep those three things written down before you even send the coins. That small habit turns a scary “where did it go?” moment into a routine support request.