Skip to main content
Prices a payout that lands in a bank account you name. No virtual account is involved - this is the one-off direction, for a user paid out once or irregularly. If the user already banks with you through a virtual account, see Pay out from a virtual account instead. Anonymous: no account, no identity, so the price can be shown before anyone commits.
Needs the bank-payouts permission on your API key. See Authentication.

​
Request

​
string
required
The asset the user is paying out with (e.g. "USDC").
​
number
required
Chain id the stablecoins are sent from. Must be enabled on your key.
​
string
required
ISO 4217 code the bank account is credited in (e.g. "GBP").
​
string
required
ISO 3166-1 alpha-2 of the destination bank. The same currency reaches different countries over different rails at different cost, so it is priced per country.
​
string
The amount of stablecoin the user gives up. Send this or fiatAmount.
​
string
The amount that must arrive in the bank account, solved backwards.
​
string
Force a specific rail (e.g. "sepa_instant", "faster_payments", "ach", "pix"). Omit and the cheapest rail that serves the pair is chosen.

​
Response

​
string
Pass to POST /v1/bank/payout.
​
string
What the user sends.
​
string
What arrives in the bank account, after both fees.
​
string
Exchange rate used, fiat per unit of crypto.
​
string
The rail this price is for. Read it - a forced rail that is closed is refused, but an omitted one may resolve to something slower than you assumed.
​
string
How long the rail takes once sent, as a coarse label: instant, same_day, t+1, t+3. Never a promise - see the warning below.
​
string
The banking partner’s fee, in fiat. Already deducted from fiatAmount.
​
string
Rheon’s markup, in fiat.
​
string
ISO 8601. Execute before this or the quote is refused as expired. Bank payout quotes hold for two hours, which is the banking partner’s own window - shorter than a card quote and far longer than a crypto one.
estimatedSettlement is the rail’s normal behaviour, not a commitment. A receiving bank can hold a transfer for its own checks, and cut-off times push a late instruction to the next working day. Show it as an expectation.
Rails differ enough that a percentage taken from one payout misprices the next. Quote the amount you are about to send, per country, every time.

​
Errors