Swaps, rates & orders
Float vs fixed rate
Float swaps use the market rate around the time your deposit is confirmed. The received amount can move slightly with volatility but often tracks the best available path at execution time.
Fixed swaps lock an agreed rate for a limited window. You know the target receive amount up front; sending a different amount than specified can cause refunds or adjustments per provider rules. Always match the instructed deposit.
Float
Rate around deposit confirmation time; output may move slightly with the market.
Fixed
Agreed receive amount for a window; send the instructed deposit exactly or risk refund/adjustment per rules.
GETIndicative quote
POSTOrder + deposit address
GETLatest progress
Integrators poll status or use partner webhooks for affiliate events. End users rely on the app or order link.
Quotes
The app and public API expose an indicative quote (GET /swap/quote) with currency_from, currency_to, and either amount_from (float) or amount_to with fixed=true. Responses include min/max bounds and optional USD reference fields used for analytics and affiliate math.
Creating an order
POST /swap/create accepts the pair, amounts, destination address, optional receiver_memo_tag, is_anonym, fixed, and optional source. The response returns a public order_info identifier used for status polling.
Order status
GET /swap/status?order_id=… returns the latest snapshot; the server may refresh provider status before responding. End users track progress in the app; integrators should poll or use partner webhooks where applicable.
UX principles (in-product)
The product aims for minimal friction: no account wall for swapping, clear deposit instructions, and status copy aligned to states such as awaiting deposit, routing, and payout. Partner-facing analytics and order lists live under /partner/dashboard and /partner/orders in the app.