Your customer pays BTC, SOL, DOGE — whatever they have. Your balance receives the settlement coin you configured, usually a stablecoin. The conversion quote is locked when the invoice is created and executed with a slippage guard. We add no markup on the conversion.
settlement_coin on any white-label payment. The conversion quote locks at invoice creation, so the amount your customer sees already prices the swap in.APIswap_fallback) — funds never hang in between.GUARANTEEDpayment.paid carries settled_coin + settled_amount alongside what the buyer actually paid — your books see both legs.SIGNED{
"amount": "149.00",
"fiat_currency": "USD",
"currency": "BTC", // what the buyer pays
"settlement_coin": "USDT_TRC20", // what YOU receive
"order_id": "order_8841"
}
// Later, in the signed payment.paid webhook:
{
"status": "PAID",
"coin": "BTC",
"amount": "0.00131", // buyer's leg
"settled_coin": "USDT_TRC20",
"settled_amount": "148.61" // your leg — already in your balance
}
Accepting many coins maximizes conversion at checkout; holding many coins is a bookkeeping and volatility problem. Auto Settle gives you the first without the second — wide acceptance, one-line treasury.
A non-custodial swap venue, quoted before execution and checked after. If delivery falls outside the slippage bound, the conversion is refused and you keep the original coin.
Any supported coin. In practice nearly everyone picks USDT (TRC20 for cheap withdrawals) or USDC — see the full list.
Yes — the account-wide default converts every credited deposit, whichever product it arrived through. Per-payment settlement_coin is for invoice-level control.
No — splits distribute the deposit coin, Auto Settle converts it; one per payment. Split recipients can convert their own credit any time.
One field on the API, or one dropdown in settings. Every coin your customers love, one coin on your books.