/bank-accounts) or a registered external PIX key (/pix-keys). Request and response fields for those resources are documented on each endpoint in the API reference.
Before you start
- Origin:
origin_bank_account_idis the bank account debited for the cashout. It must be eligible per your setup (for example, an affiliated account with available balance). Use theidreturned when you list bank accounts for the merchant or company. - Destination: Register either a Company bank account or a Company PIX key (paths under
/bank-accountsor/pix-keys). In the cashout body you senddestination_bank_account_idordestination_pix_key_id—never both. Requests with both fields (or neither) are rejected with a400validation error. Theprimaryflag does not act as a fallback here: cashouts created through the API always use the destination you name in the request. - Idempotency / tracking:
request_idis required; use a unique string per cashout attempt (for example a UUID or your internal reference).
1) Register an external PIX key destination
POST accepts key (required) and optional primary. The API resolves the key via DICT; the create response can include dict_key_information (often masked per BACEN rules).
- Merchant
- Organization
2) Register an external bank account destination
Required fields:branch_number, account_number, account_type, account_holder_name, account_holder_document_number, ispb. Use digits only for branch and account numbers.
- Merchant
- Organization
3) Create a cashout
Request body includes:Send exactly one destination field. If the request contains both
destination_bank_account_id and destination_pix_key_id, or neither, the API returns a 400 validation error. For companies with automatic transfers enabled, Rinne creates cashouts on a schedule and picks the destination by priority—primary active bank account first, then primary active PIX key. If neither exists, that cycle is skipped. See Automatic cashouts.Destination: external bank account
- Merchant
- Organization
Destination: external PIX key
Omitdestination_bank_account_id and send destination_pix_key_id (the UUID returned from POST …/pix-keys).
- Merchant
- Organization
4) List, get details, and receipt
- Merchant
- Organization
For organization cashouts,
CASHOUT_ID can be internal id or external request id per API docs. Receipts are only returned for certain completed states and require an end-to-end ID—see Cashouts or the cashout receipt endpoints in the API reference.Cashout status values
Typical cashout statuses arePENDING, PROCESSING, COMPLETED, FAILED, PARTIALLY_RETURNED, and RETURNED.
Webhooks
Subscribe to:cashout.created: emitted when the cashout is successfully createdcashout.status-changed: emitted when status updates

