Refund Address vs Receiving Address in Crypto Swaps: 5 Checks Before You Send (2026)

By Swappr Editorial (GSPTeck) · Published 2026-10-14 · Last verified 2026-10-14

Instant crypto swaps ask for addresses in more than one place: where you want the new coin delivered, and sometimes where a refund should go if the order cannot complete. Mixing those up — or pasting a memo-based address without the memo — is one of the most common ways a careful user still loses time or funds. This guide gives five checks to run before you send the deposit. Educational only; Swappr processes swaps via FixedFloat’s public flow described on swappr.website.

Swappr in one line: a free Android app for multi-coin swaps — pick the coin you have and the coin you want, check the estimate and limits, choose Fixed or Float rate, paste the receiving address, send the deposit. Features that matter here:

Honest comparison: an exchange withdrawal UI keeps an address book inside one account; a DEX sends on-chain from the wallet you connect; an instant swap asks you to paste destinations yourself and then send a deposit. That last model is flexible, and it puts address hygiene entirely on you.

Receiving address vs refund address

Two columns: receiving or payout address for coin B versus refund address for coin A on the deposit network
Two address fields.

The receiving address (sometimes called payout or destination) is where coin B should arrive if the swap succeeds. The refund address is where coin A should be returned if the order cannot be completed under its rules (for example an expired fixed-rate order that is eligible for refund per the partner’s FAQ). They are not interchangeable. A receiving address on the wrong network for coin B will not “become” a safe refund path for coin A. Read the labels on each field carefully before you paste.

If a form only asks for one address, that address is almost always the payout address for coin B — still match its network. When a second field appears for refunds, slow down: two correct pastes beat one fast mistake.

Check 1: coin and network match the field you are filling

Grid of coin and network match checks: field coin, network label, wallet network, paste once, compare characters, memo if required
Coin + network match.

Every address belongs to a network. USDT on TRC20 is not the same destination as USDT on ERC20. Before pasting: Copying the right address is only half the job; our six checks against clipboard malware and look-alike addresses cover pasting it safely. Bitcoin adds its own wrinkle with four address formats; see which Bitcoin address type to paste in a swap. When a swap form rejects an address, the network is usually the reason; our guide to fixing an invalid wallet address error in a crypto swap lists six causes.

  1. Confirm which coin the field is for (deposit asset vs payout asset).
  2. Confirm the network label next to that field.
  3. Copy the address from a wallet that is set to that same network.
  4. Paste once, then visually compare the first and last characters.

For stablecoin network choice in more detail, see USDT on TRC20 vs BEP20 vs ERC20. Partner documentation for order behaviour is published on FixedFloat’s FAQ; read the live FAQ on the day you swap because rules can change.

Check 2: destination tags and memos when the coin requires them

Some assets (notably XRP, XLM, TON, Cosmos-family coins and others) need a destination tag or memo in addition to the address. Missing the memo can credit the wrong account on an exchange-style recipient, or leave funds stranded until support intervenes — if recovery is possible at all. Our guide to destination tags and memos walks through when the extra field appears and what to do. If the order form shows a memo field, fill it from the same place you copied the address; do not invent a memo.

A practical habit: paste address and memo into a notes draft first, label which is which, then copy into the swap form. Rushing on a phone keyboard is how digits swap places.

Check 3: refund address uses the deposit coin’s network

Four-step refund field hygiene: refund is coin A, deposit network, separate from payout address, recheck before send
Refund field hygiene.

If the form asks for a refund address, it must be able to receive the deposit coin on the deposit network — not the payout coin. Using your payout address as a refund address is a frequent mistake when both fields sit on one screen. Create or select a wallet address you control for coin A, paste it into the refund field only, and leave the payout field for coin B.

If you do not control a wallet for coin A on that network, do not start the order yet. Solving custody after a failed order is harder than solving it before you send. If your coins currently sit on an exchange, our guide to the risks of sending a swap deposit straight from an exchange explains a wallet-first route.

Check 4: fixed-rate windows and “what if I sent late?”

Fixed-rate orders have time rules. Sending after expiry, sending the wrong amount, or splitting a deposit can change whether you get a refund, a recalculated rate or a support path. Read the order screen before you broadcast, and if something already went wrong, follow expired, short, or duplicate deposit troubleshooting instead of sending a second deposit “to fix it.”

Float-rate orders behave differently on timing and final amounts; the important shared rule is still “one intentional deposit.” Extra deposits create ambiguity for automated matching.

Check 5: keep TXIDs and never share a seed phrase

Four-step after send: save deposit TXID, wait without resending, save payout TXID, support gets IDs never a seed
After you send.

After you send, save the deposit TXID. If the payout appears, save that TXID too. Support can work with order ids and transaction ids; support will never need your recovery phrase. To read pending vs confirmed states on an explorer, use how to track a crypto swap with TXIDs. If someone DMs you claiming to be support and asks you to “verify” by signing a message or entering a seed, that is a scam — stop and use only the contact channel listed on the official Play listing / site (gspteck@gmail.com as published for Swappr support).

Store TXIDs in a private note with the order id and UTC time. Screenshots help, but copy-pasteable ids help support more.

Vertical Pinterest graphic: refund versus receiving address in crypto swaps with five checks
Pinterest pin: refund vs receiving.

Why address mistakes are expensive in instant swaps

Unlike an exchange internal transfer you can sometimes reverse with support, a confirmed on-chain deposit to the wrong network or without a required memo is often final. Instant-swap UIs make the happy path fast, which is good, but speed is exactly when people paste from the wrong clipboard entry. The five checks above exist to force one slow minute before an irreversible send. If you feel rushed by a rate timer, it is usually safer to cancel and recreate the order than to paste blindly.

A pre-send one-minute card

  1. Payout field = coin B + correct network (+ memo if required).
  2. Refund field (if shown) = coin A + deposit network.
  3. Amount within min/max; rate mode understood.
  4. Ready to send once; TXID note open.

FAQ

Can I use the same address for refund and receiving?

Only if it is actually valid for both coins and networks — which is uncommon when you are swapping different assets. When in doubt, use separate addresses that match each field’s coin and network.

What if I pasted the receiving address into the refund field?

Do not send the deposit until you correct the form. If you already sent, collect the order id and TXID and contact official support; do not send again.

Why does my coin ask for a memo?

Some networks and exchange deposit systems route funds with a memo/tag. Without it, automated credit may fail even if the base address is correct.

Is a swap reversible after the deposit confirms?

Usually no. Treat confirmed deposits as final and rely on the order’s documented refund rules only when the partner’s FAQ says a refund applies.

Sources

More guides on the Swappr blog.