Fiat payout fee
Fee schedule for a fiat payout. Use at quote/display time to show the user
what they’ll be charged. Echo the returned fixed + bps on the payout
submit as expectedFeeSchedule to guard against config drift between
quote and submit.
Headers
Bearer token. Format: Bearer <api_key>
Query Parameters
Transfer method (e.g. SWIFT). Accepted for future extensibility — v1 prices by asset only.
Asset code of the withdrawal (e.g. USD, EUR).
Response
The request has succeeded.
Fee schedule for a given transaction type + asset (+ method or chain).
Describes the pricing rule without running a calculation — clients apply it
to their own amount to display a running total:
fee = fixed + round(amount × bps / 10_000)
where bps are integer basis points (1 bp = 0.01%) and rounding is half-up
at the asset's subunit precision. Clients displaying the fee before the
user commits can calculate locally; the server re-validates at submit time
(via the payout request's expectedFeeSchedule), so a stale local rate
can't result in a wrong charge — it just fails the submit with a
drift error, prompting the client to refresh.
Missing fees (a currency or chain not explicitly priced) return zeros across the board — adding a new asset without a configured fee rule means it's free.
Flat component charged regardless of the principal. Zero when the schedule has no fixed component.
Rate applied to the principal, in basis points (1 bp = 0.01%, so 50 bps = 0.5%). Zero when the schedule has no rate component.
Asset code the schedule is denominated in. Fees are always charged in the same asset as the principal — no FX.