Use cases
SilentSwap's quote, review, place, and track flow supports more than one-to-one swaps. These recipes show how the same typed request becomes a batch payout, a private payment, an invoice, an arbitrary-asset payout, or an integrator revenue stream.
| Use case | SDK feature | Hard constraint |
|---|---|---|
| Payroll and batch payouts | Multiple outputs[] | 1–20 recipients; at least 10 USDC each |
| Private same-chain payment | Same source and destination chain | Direct USDC pays out on Base or BNB Chain |
| Private invoices | Exact output with no top-level amount | Recipient amount is fixed; at least 10 USDC |
| Pay out in any asset | outputs[0].dest | One recipient; operator-enabled assets only |
| Revenue share with integrator fees | integratorId with a split | Fee terms and payout address are owner-configured |
Sources in, destinations out
SilentSwap accepts wallet-funded inputs from many source chains. Read them from
listSourceChains() rather than copying chain metadata into your application; see
assets and chains.
Direct USDC payouts land on Base (8453) or BNB Chain (56). A payout in another asset or on
another destination uses outputs[0].dest, which is a single-recipient route and can
be disabled by the operator.
For every use case, render all outputs, assets, fees, and expiry in trusted UI before calling
placeOrder.