Frequently asked questions

NexaSwap provides a no-registration cross-chain exchange interface. After an order is created, the user pays to a dedicated deposit address and the system exchanges funds after on-chain confirmation.

The order flow is designed as non-custodial. Deposit addresses are tied to individual orders and the platform does not provide user balances or wallet accounts.

Orders are recovered with high-entropy query codes. Order pages are excluded from search indexes, and the lookup endpoint requires rate limiting and abuse protection.

A fixed rate locks the amount for the quote validity period. A floating rate uses the market price when the required confirmations are reached.

Choose a fixed rate when you want to lock the estimated amount and can send the exact matching amount before the quote expires.

Timing depends on payment confirmations, network congestion, and liquidity execution. The order page shows the current stage and on-chain details.

Common causes include a network mismatch, incorrect length, spaces, or an unsupported chain. Select the correct network and enter the address again.

Market prices change continuously, so the page updates the quote on a timer. Only the quote snapshot saved with the order is binding.

Yes. Select Add output and allocate percentages. Each destination asset and address is validated independently.

Floating rates are affected by market prices, network fees, and execution prices. Spreads and service fees must be shown in the quote details.

The order page updates status in real time. Save the query code and use the lookup page to reopen it later.

Do not pay an expired order. If you already paid late, keep the transaction hash and contact support for manual review.

KYC may be required when an order triggers risk rules, sanctions screening, or regulatory requirements.

The order may be paused, require more information, or be refunded based on the circumstances. The formal process must be defined in the terms.