Pay out from a virtual account

Sends a bank transfer for a user who already holds a virtual account. The money comes from the stablecoins their wallet sends, exactly as in a bank payout - what the virtual account adds is the user’s existing identity, corridor and settlement setup, so nothing is collected twice.

The virtual account never holds a fiat balance, so this is not a withdrawal. Money that arrives on the account is converted and settled the moment it lands. Paying out means the user’s wallet sends stablecoins back and we transfer fiat to the beneficiary you name - the account itself has nothing to draw on.

Needs the virtual-accounts permission on your API key. See Authentication.

Path parameter

string

required

The virtual account id from POST /v1/virtual-accounts.

Request

string

required

ISO 4217 code the beneficiary is credited in. It does not have to match the currency the virtual account receives - a user funded in AED can pay out in BRL.

string

The amount that must arrive. Send this or cryptoAmount.

string

The stablecoin the user gives up, if you would rather pin that side.

object

required

Who gets paid - the user themselves or a third party. Same shape as bank payouts: name plus the fields the rail needs.

string

Your idempotency key, up to 64 characters. Send one - a retry without it is a second transfer.

Response

string

The payout id. Poll with POST /v1/bank/payout/status - virtual account payouts share that endpoint and vocabulary.

string

Where the user’s wallet sends the stablecoins. Single-use, derived per payout.

string

The exact amount to send.

number

The chain depositAddress lives on - the network the account settles on.

string

What the beneficiary receives, after fees.

string

The rail chosen for the destination country and currency.

string

pending on creation.

The corridor a virtual account was opened with governs what arrives, not what leaves. A payout to a country or currency outside your account’s agreed corridors is refused with 422 no_route rather than routed anyway.

curl -X POST "$RHEON_API/v1/virtual-accounts/va_8f2c91d0a4/payouts" \
  -H "Authorization: Bearer $RHEON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "fiatCurrency": "BRL",
    "fiatAmount": "1500.00",
    "beneficiary": {
      "name": "Ana Ribeiro",
      "pixKey": "ana.ribeiro@example.com"
    },
    "reference": "payout-2026-09-02-116"
  }'

{
  "id": "bpo_9f0c4e2a18",
  "depositAddress": "0x5E81c0A7fB29d6431aC08e57D2b96f10E4c7a3B2",
  "depositAmount": "281.44",
  "chain": 42161,
  "fiatAmount": "1500.00",
  "rail": "pix",
  "status": "pending"
}

Errors

HTTP	`code`	When
400	`invalid_request`	A field is missing or malformed, or both amounts were sent.
401	`unauthorized`	Missing, malformed, or unknown API key.
403	`permission_denied`	Your key does not carry the virtual-accounts permission.
404	`not_found`	No such virtual account under your key.
422	`no_route`	The destination country and currency are outside your corridors.
422	`requires_action`	The user needs a higher verification tier before paying out.
429	`rate_limited`	Over your key’s rate limit.
502	`upstream_error`	The banking partner is unavailable.
500	`internal`	Unexpected server error.

Getting started

Crypto deposits

Card payments

Card payouts

Bank transfers

Bank payouts

Virtual accounts

Reference

Pay out from a virtual account

Path parameter

Request

Response

Errors

​Path parameter

​Request

​Response

​Errors

Path parameter

Request

Response

Errors