Will a hardware wallet receive the converted asset?

Yes, a hardware wallet can receive the payout when it supports the selected asset and network. Enter the address shown by Ledger, Trezor or Tangem software, then keep the network aligned with the quote. The device doesn’t need to stay connected while the service sends the asset, because reception happens on-chain. Spending the balance later still requires the wallet’s normal signing process and the native fee asset for that network.

Can a business embed the swap flow in its own product?

Yes, a business can embed the conversion flow through the service’s developer API. The integration passes pair, amount, rate type and recipient details while preserving transaction tracking through an exchange ID. Partner onboarding can include business verification and separate commercial terms. An embedded flow still needs clear network labels, memo fields and deposit instructions because the underlying blockchain transfers remain the same.

Why must the deposit amount match the quote?

The quoted deposit amount anchors the provider route and expected payout. Sending less than the displayed minimum leaves the order ineligible for normal execution and may leave too little value for a refund after network costs. Sending a different amount or several payments moves the transfer outside the original instruction set and triggers provider-specific handling. Treat the generated address, asset, network and amount as one transaction-specific set.

Can the receiving address belong to Binance or Kraken?

Yes, a receiving address can belong to Binance or Kraken when the venue supports the exact asset and network selected in the order. Shared deposit addresses frequently require a memo, destination tag or other account identifier, and the receiving venue supplies that value. Copy both fields before creating the swap. A correct address without its required tag may reach the venue’s wallet without being credited automatically to the intended account.

When should I provide a separate refund address?

Provide a separate refund address when the original sending address isn’t suitable for receiving a return transfer. This matters for withdrawals from custodial venues, smart-contract wallets or systems using shared addresses. The refund address must accept the deposited asset on the same network. If no refund address is entered, the service treats the original sender as the default, subject to the order’s refund conditions and any required ownership checks.

Does receiving USDT require a native fee token?

Receiving USDT doesn’t require the recipient to pay a fee at the moment of delivery. Moving it later requires the network’s native fee asset: ETH for ERC-20 USDT on Ethereum, BNB for BEP-20 USDT on BNB Smart Chain, SOL for a Solana token account and TRX resources or fees for TRC-20 USDT on TRON. The ticker alone doesn’t determine the fee asset; the selected network does.

Does a standard order create a token allowance?

No, the standard deposit-address flow doesn’t create an ERC-20 or BEP-20 token allowance in the sending wallet. The wallet signs a transfer to the generated deposit address rather than approving an on-chain router contract to spend tokens. Integrated wallet experiences may present their own transaction interface, so read the transaction type before signing. A normal direct order should show a transfer amount and destination, not a standing service allowance.

Will the converted token appear automatically in my wallet?

The converted token appears automatically when the wallet already indexes the relevant network and token contract or mint. If the blockchain shows a successful payout but the balance stays hidden, add the verified ERC-20, BEP-20 or TRC-20 contract or Solana mint in the wallet interface. MetaMask, Phantom and TronLink handle token discovery differently. Display settings don’t change custody; the receiving address still owns the on-chain balance.

Simple swap

Simple swap is wallet-to-wallet routing without an order book

Simple swap is a crypto conversion where one asset leaves your wallet and another reaches a destination address you choose. The service collects a quote from external liquidity providers, assigns a transaction-specific deposit address and sends the converted asset after the incoming transfer confirms. You don’t fund a standing exchange balance or place bids and asks on a trading screen. That makes the format useful for direct BTC-to-ETH conversions, cross-network rebalancing and access to assets outside one trading venue. The important choices come before payment: asset, network, amount, destination details and whether the quote floats with the market or locks for a short window.

A fixed quote holds for 20 minutes and needs at least one blockchain confirmation inside that window.

Choose the rate promise before sending

The rate decision settles whether Simple swap prioritizes output certainty or flexibility while the deposit moves across a blockchain.

A trade order starts with 4 core fields: the trading pair, deposit amount, rate type and recipient address. Extra details include a refund address or memo when the selected asset requires one. Fixed and floating are the 2 quote modes. A floating quote estimates the payout at creation and recalculates it when processing begins, so liquidity, market movement and confirmation time all influence the final amount.

A fixed quote holds the displayed rate for 20 minutes. The deposit needs at least 1 blockchain confirmation inside that window. Bitcoin’s roughly 10-minute block interval makes the timing less predictable than an account-based chain with faster blocks; a transaction can land sooner or later because block discovery is probabilistic.

Choose fixed when the exact receiving amount matters to a downstream payment. Choose floating when you accept a market-set payout and want no strict sending window. The service still shows a minimum deposit for both modes. That minimum belongs to the specific pair and route, so copy the value shown on the live order rather than relying on a remembered threshold.

Where do the costs enter the quote?

Simple swap prices the conversion inside the quoted rate, while blockchain fees sit at the deposit and payout edges.

The displayed output blends the provider’s market price, available liquidity, routing cost and the service component. Simple swap doesn’t publish a universal percentage commission for crypto-to-crypto orders. On a fixed-rate order, the payout network fee is already reflected in the shown receiving amount. Your sending wallet still pays the input network fee separately. A complete conversion therefore exposes 2 user-facing blockchain transfers: 1 deposit and 1 payout. Internal provider execution adds its own costs inside the quote, yet the user doesn’t sign those route-level trades. Compare the final asset amount across available routes before funding the order.

Network fees move with demand because each chain has its own auction or resource model. Ethereum charges gas in ETH, BNB Smart Chain uses BNB, Solana charges in SOL and TRON settles resource shortfalls in TRX. Low market depth widens the conversion spread as well. The fixed number here is the 20-minute lock; every price and fee input remains tied to the order shown on screen.

Routing from deposit address to payout

The routing process joins 1 incoming transfer, provider execution and 1 outgoing transfer under a single trade order.

Once the order contains its 4 required inputs, the service generates 1 deposit address for that transaction. Reusing it for a later order breaks the link between the payment and the new quote. After the chain records the deposit, the route moves through the selected liquidity provider. The provider converts the asset, then the service sends the result to the recipient address.

Three identifiers describe different layers. The exchange ID tracks the service order, the deposit transaction hash identifies the incoming blockchain record and the payout transaction hash identifies delivery. A Bitcoin transaction ID doesn’t become an Ethereum transaction hash during a BTC-to-ETH conversion; each chain records its own transfer. That separation lets a reader check confirmation, execution and delivery without an order-book account.

Network identity before asset identity

Network identity determines the real token route, because one ticker such as USDT represents separate contracts or token programs on several chains.

Ethereum ERC-20, BNB Smart Chain BEP-20, TRON TRC-20 and Solana Program Library Token Program assets use different fee currencies and address rules. An Ethereum account carries a 20-byte address rendered as 42 characters including 0x. BNB Smart Chain follows the same Ethereum Virtual Machine address size, while its mainnet chain ID is 56. Those matching shapes don’t make the networks interchangeable.

Network	Common token form	Fee asset	Hard address-length limit
Ethereum	ERC-20	ETH	20-byte payload; 42-character text
BNB Smart Chain	BEP-20	BNB	20-byte payload; 42-character text
Solana	SPL token	SOL	32-byte public key
TRON	TRC-20	TRX	21-byte payload; 34-character Base58Check

Solana account addresses are 32-byte public keys, and 1 SOL contains 1,000,000,000 lamports. TRON’s user-facing Base58Check address is 34 characters and encodes a 21-byte value; 1 TRX contains 1,000,000 sun. Ethereum uses 1,000,000,000,000,000,000 wei per ETH. These constants explain why a wallet can accept a pasted string yet still need the correct network selection, token contract and native fee asset. The quote screen must match both wallets at the protocol level. MetaMask, Phantom and TronLink expose those details differently, while a contract address or mint separates assets sharing the same ticker. USDT on TRON remains distinct from USDT on Ethereum throughout settlement.

A clean first exchange

A first exchange works best when 5 order details remain unchanged from quote creation through deposit and receipt.

Start with the exact send asset and network displayed by the wallet, then choose the receive asset and its network. Enter a recipient address controlled by your wallet or assigned by another service. If that destination supplies an XRP Destination Tag, Stellar memo or another extra identifier, copy it into the dedicated field. Add a refund address from the sending network when the interface offers one. Finally, check the live minimum, quoted amount and rate mode before creating the order. These 5 checks preserve the assumptions the route uses and keep the deposit attached to the intended conversion.

Save the exchange ID before sending. It remains the direct key for status tracking and support without opening an account.

Match the asset ticker and contract or mint.
Match the sending network to the deposit network.
Match the recipient network to the payout network.
Include every required memo or destination tag.
Send the exact amount within the chosen rate window.

The deposit address belongs to 1 trade order, so generate a fresh address for every new conversion. A wallet such as Exodus, Tangem or MetaMask may show the balance through a different interface, but the blockchain transaction still settles to the recipient address. Keep enough native fee asset in the sending wallet to broadcast the deposit.

Custody, compliance and irreversible transfers

The custody model limits the service relationship to 1 conversion, yet the deposit remains outside your wallet while execution is pending.

The service doesn’t ask users to maintain a long-term trading balance for a standard crypto-to-crypto order. Funds leave the sending wallet, pass through a transaction-specific deposit address and return as another asset. That structure removes ongoing exchange-balance exposure, but it doesn’t remove counterparty exposure during the swap. Once the deposit reaches a confirming or processing state, edits and cancellation are generally unavailable. Compliance screening also applies to transaction flow. Low-risk orders may proceed without registration, while a review can request identity, residence and source-of-funds information under 2 check levels: standard and enhanced. The order can pause during that review.

The published refund procedure allows up to 31 calendar days to process an eligible request. Network costs or a recovery fee can reduce the returned amount, and a deposit below the displayed minimum may not cover the network fee. Address and network selection deserve the most attention because confirmed blockchain transfers aren’t editable. The strongest control is precise order data before broadcast, followed by the saved exchange ID.

Where wallet-to-wallet conversion earns its place

Wallet-to-wallet conversion fits rebalancing, direct asset substitution and access to a chain outside a user’s regular trading venue. A BTC holder can request ETH at an Ethereum address, while a USDT holder can move between supported network-specific forms through a quoted conversion. The format also suits a hardware-wallet workflow because the payout goes to a supplied address. It remains a one-off route, not a portfolio account, lending position or limit-order system. The convenience matters most when the reader values a single quoted path over manual venue selection.

Should you use Simple swap, a DEX or an order-book exchange?

Use Simple swap for quoted wallet delivery, a decentralized exchange for on-chain execution and an order book for active price control.

Uniswap executes swaps against automated market maker pools and asks the connected wallet to sign on-chain contract calls. 1inch searches decentralized exchange liquidity and builds a route across supported venues. THORChain focuses on native cross-chain swaps through protocol liquidity rather than issuing wrapped representations for the swapped assets. Coinbase Advanced keeps funds inside a custodial exchange account and exposes order-book tools such as limit orders. Each model places routing, custody and transaction signing in a different location, so the right choice follows the user’s preferred control surface rather than a universal winner.

Quoted services reduce interface complexity and handle provider selection. DEX routes require compatible wallet interaction and native gas; ERC-20 inputs also require an allowance unless an existing allowance covers the amount. Order-book venues supply limit prices and deeper trading controls, while account onboarding and withdrawal remain part of the path. Pick the model matching the task: direct wallet delivery, programmable on-chain routing or repeated trading from an exchange balance.

Blue computer monitor with shield and orange padlock

Details worth knowing about Simple swap

Will a hardware wallet receive the converted asset?: Yes, a hardware wallet can receive the payout when it supports the selected asset and network. Enter the address shown by Ledger, Trezor or Tangem software, then keep the network aligned with the quote. The device doesn’t need to stay connected while the service sends the asset, because reception happens on-chain. Spending the balance later still requires the wallet’s normal signing process and the native fee asset for that network.
Can a business embed the swap flow in its own product?: Yes, a business can embed the conversion flow through the service’s developer API. The integration passes pair, amount, rate type and recipient details while preserving transaction tracking through an exchange ID. Partner onboarding can include business verification and separate commercial terms. An embedded flow still needs clear network labels, memo fields and deposit instructions because the underlying blockchain transfers remain the same.
Why must the deposit amount match the quote?: The quoted deposit amount anchors the provider route and expected payout. Sending less than the displayed minimum leaves the order ineligible for normal execution and may leave too little value for a refund after network costs. Sending a different amount or several payments moves the transfer outside the original instruction set and triggers provider-specific handling. Treat the generated address, asset, network and amount as one transaction-specific set.
Can the receiving address belong to Binance or Kraken?: Yes, a receiving address can belong to Binance or Kraken when the venue supports the exact asset and network selected in the order. Shared deposit addresses frequently require a memo, destination tag or other account identifier, and the receiving venue supplies that value. Copy both fields before creating the swap. A correct address without its required tag may reach the venue’s wallet without being credited automatically to the intended account.
When should I provide a separate refund address?: Provide a separate refund address when the original sending address isn’t suitable for receiving a return transfer. This matters for withdrawals from custodial venues, smart-contract wallets or systems using shared addresses. The refund address must accept the deposited asset on the same network. If no refund address is entered, the service treats the original sender as the default, subject to the order’s refund conditions and any required ownership checks.
Does receiving USDT require a native fee token?: Receiving USDT doesn’t require the recipient to pay a fee at the moment of delivery. Moving it later requires the network’s native fee asset: ETH for ERC-20 USDT on Ethereum, BNB for BEP-20 USDT on BNB Smart Chain, SOL for a Solana token account and TRX resources or fees for TRC-20 USDT on TRON. The ticker alone doesn’t determine the fee asset; the selected network does.
Does a standard order create a token allowance?: No, the standard deposit-address flow doesn’t create an ERC-20 or BEP-20 token allowance in the sending wallet. The wallet signs a transfer to the generated deposit address rather than approving an on-chain router contract to spend tokens. Integrated wallet experiences may present their own transaction interface, so read the transaction type before signing. A normal direct order should show a transfer amount and destination, not a standing service allowance.
Will the converted token appear automatically in my wallet?: The converted token appears automatically when the wallet already indexes the relevant network and token contract or mint. If the blockchain shows a successful payout but the balance stays hidden, add the verified ERC-20, BEP-20 or TRC-20 contract or Solana mint in the wallet interface. MetaMask, Phantom and TronLink handle token discovery differently. Display settings don’t change custody; the receiving address still owns the on-chain balance.