For a team managing treasury swaps, payouts, or regular transfers, ParaSwap offers five main trade types: Market swaps, Delta intent swaps, limit orders, TWAP orders, and OTC trades. Market settles an immediate transaction; Delta seeks a solver fill; limit orders wait for a price; TWAP spreads execution over time; and OTC settles terms agreed with a known counterparty.
ParaSwap Has Five Main Trade Types
The five types differ in who submits the trade, when it can fill, and what the team commits to signing. Start with the obligation behind the transfer: a fixed amount to receive, a price threshold, a deadline, or an agreed counterparty. Those constraints matter more than the quoted rate alone.
- Market swap — best for immediate, atomic settlement. The wallet signs and broadcasts a transaction that routes through available on-chain liquidity. It does not fit a workflow that needs to wait for a target price or move value between chains in one order.
- Delta intent swap — best when the team can allow solver execution. The wallet signs an order; competing solvers seek a fill that satisfies its terms. It does not fit a transaction that must compose synchronously with another contract call. A crosschain swap is a Delta route, subject to available bridge routes.
- Limit order — best when a minimum sale return or maximum purchase spend matters more than timing. It is a resting Delta order with a price constraint and expiry. It does not fit a payout that must settle on a particular day: the price may never become reachable.
- TWAP order — best for spreading a larger trade across scheduled slices. One signed Delta order governs the schedule and its remaining balance. It does not fit an exact, immediate payout, and it still needs sufficient liquidity when each slice becomes eligible.
- OTC trade — best when two known parties have agreed the terms directly. A maker signs an AugustusRFQ order naming the taker, who fills it on-chain. It does not fit an open search across liquidity sources for an unknown counterparty.
Routing and Settlement Determine What Actually Trades
The ParaSwap DEX aggregator prices the specified token pair, trade size, side, and chain against liquidity available for that request. A route can use one pool, several pools, or intermediate tokens; splitting helps only when the improved execution exceeds the extra gas and venue fees. Compare the expected output after route costs, then check the route again near signing because the price is not reserved.
For a Market swap, the price response contains a priceRoute with the expected output, gas estimate, and path. The transaction build uses that route unchanged to produce calldata for the Augustus router. After the source token has the required allowance, the wallet broadcasts the swap; the router executes its hops and enforces the minimum destination amount. A failed hop or breached minimum reverts the whole swap, while the sender still pays gas.
Delta uses a different commitment. The team obtains a route, approves the Delta spender for an ERC-20 source, signs an EIP-712 order, and submits it for a private solver auction. The winning solver supplies settlement calldata; the contract checks the signed terms before transferring funds. Track the order through completion, expiry, failure, or cancellation instead of treating signature submission as a completed transfer.
Networks, Fees, and Approvals Set the Practical Limits
Execution cost depends on the mode and the particular route. Market requires network gas for the swap and, if allowance is missing, usually a separate approval transaction; pool fees and price impact are reflected in the rate. Delta handles settlement gas within the solver flow, so “gasless” describes what the user pays on-chain, not a free economic execution. Check the net amount delivered, including any partner fee configured by an integration.
A treasury holding USDC on Polygon cannot execute an Arbitrum Market quote as though both balances lived on one chain. Check ParaSwap supported networks before fixing chain IDs and token contracts for a recurring flow. The ParaSwap exchange quote must use the actual source chain; a crosschain Delta route has separate bridge availability, fees, timing, and refund states to account for.
Approvals follow the execution contract, not the brand shown in a wallet interface: Market uses the Augustus spender, Delta orders use the Delta spender, and bilateral OTC uses AugustusRFQ. Verify the spender returned for the selected flow and approve the amount needed. Resting limit and TWAP orders need an on-chain allowance that remains usable when a later fill occurs; a short-lived permit is not a substitute for that schedule.
A Treasury Workflow Needs a Quote-to-Settlement Rule
The common payout mistake is to use SELL when the recipient must receive an exact amount. Selling, say, 50,000 USDC might quote 49,800 USDT before the allowed slippage; it does not promise a 50,000 USDT payout. Use BUY to fix 50,000 USDT as the destination and cap the USDC spend, then reject a route that exceeds the treasury budget.
Set slippage from the pair’s depth and the cost of a failed transfer, rather than leaving one setting across every token. For example, 50 basis points permits a 0.5% move between quote and execution; a tighter limit increases reverts on volatile or thin routes. For a TWAP, quote one slice, approve the total source amount, and leave enough time before expiry for every interval. The schedule requires at least two slices and intervals of at least 60 seconds.
Three Questions Clarify the Choice
How does a route become a completed trade?
A Market route becomes a completed trade only after its transaction confirms on-chain. A Delta quote becomes an order after build, signature, and submission; it completes only when a solver settles it. Record the transaction receipt or terminal order status against the treasury instruction. A quote, approval, or accepted signature is evidence of an earlier step, not proof that the recipient received tokens.
How long does execution take, and what does it cost?
Market timing follows transaction inclusion and chain confirmation; its cost includes gas and the price embedded in the selected route. Delta adds solver competition and can expire without a fill. Limit orders may rest until their price is met, while a TWAP lasts across its chosen intervals. Compare delivered tokens and operational timing together, especially when a payout has a cutoff.
Which limits decide whether a type fits?
Check token support, chain support, available routes, allowance, and the team’s maximum spend or minimum receipt. Then check whether the workflow can tolerate a resting order, partial progress across TWAP slices, or crosschain refund timing. An OTC trade also requires the named taker to act. If any of those conditions conflicts with the payment obligation, choose a different trade type before signing.
ParaSwap is most useful as a set of execution choices. Match the trade type to the amount, price constraint, chain, and settlement deadline, then reconcile the actual fill before marking a treasury transfer complete.
Top comments (0)