> ## Documentation Index
> Fetch the complete documentation index at: https://docs.caratuva.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Payouts

> Where settled BRL lands, and how to register the destination.

When a buyer's payment clears, Caratuva pays out the BRL equivalent to a Brazilian bank account you nominate. This page covers how to register the destination, when payouts arrive, and what to do if something looks off.

## How payouts work

Every approved organization gets an internal virtual account that briefly holds buyer funds between collection and payout. You don't manage this account — it's invisible in normal operation.

When an invoice settles, Caratuva initiates a PIX transfer from the virtual account to your registered destination. PIX is Brazil's instant payment rail; transfers typically post in seconds and are irrevocable on the receiving side once cleared.

## Registering your destination

From the dashboard, open the **Payout** page and complete **Step 3 — register your PIX key**.

The destination form takes a single value:

* The **PIX key** registered to your Brazilian bank account — enter it as one field, and our settlement partner auto-detects the key type. There's no separate bank-name input. The receiving account's legal name must match your verified KYB entity; that matching is enforced through KYB (collected earlier in the Payout flow), not on this form.

Caratuva supports every PIX key type:

| Key type         | Format                      | Notes                                             |
| ---------------- | --------------------------- | ------------------------------------------------- |
| CPF              | 11 digits                   | Use the CPF of the entity's legal representative. |
| CNPJ             | 14 digits                   | Recommended — directly tied to the legal entity.  |
| Email            | Standard email              | Must be the email registered with the bank.       |
| Phone            | E.164 (e.g. +5511999999999) | Must be the phone registered with the bank.       |
| Random key (EVP) | UUID                        | The "random key" minted by your bank app.         |

We strongly recommend using a **CNPJ key** — it's the cleanest mapping between your legal entity and the receiving account.

## Destination must match KYB entity

The legal name on the receiving account must match the legal name we verified during KYB. This is regulatory: we cannot disburse to an entity we haven't verified.

If you need to change the receiving entity (e.g. you acquired a different operating company), re-run KYB from the **Payout** page first. The new destination becomes available once the new entity clears.

## Multiple destinations

Most organizations use a single payout destination. If you operate multiple legal entities under one organization, contact us — we'll set up entity-scoped destinations.

## Payout timing

For invoices that settle during a Brazilian banking day, payout initiates as soon as the buyer's bank transfer settles on the source rail (timing depends on the buyer's country and rail — ACH, wire, or SEPA).

For invoices that settle outside banking hours, the payout may queue until the next PIX cycle. PIX runs 24/7 in normal operation, but bank cutoffs occasionally introduce a brief lag.

The invoice timeline shows the exact timestamp when payout was initiated and when it confirmed.

## Confirming receipt

Once the PIX transfer settles on the receiving side, the invoice transitions to `settled` and a `payment_intent.settled` (or `invoice.settled`) webhook fires. The dashboard timeline shows the PIX end-to-end ID, which you can match against your bank statement.

If your bank shows the deposit but Caratuva still shows `offramp_pending`, give us a few minutes — we reconcile against incoming PIX confirmations on a short cadence. If it's still mismatched after 30 minutes, contact support.

## Failed payouts

A payout can fail if:

* The destination PIX key was deactivated or transferred to a different bank account.
* The receiving account was closed.
* The destination bank rejects the transfer (rare, usually a name-mismatch).

When this happens the invoice goes to `offramp_failed` with the reason, and the funds remain in your virtual account. You can update the destination and we'll retry — or, if the destination problem is structural, we'll reach out directly.

## Fees

Caratuva's fees are deducted from the buyer's payment, before the BRL net amount is paid out. Your dashboard's invoice detail shows the breakdown:

```
Buyer paid (USD)             12,500.00
FX rate                       5.05
BRL gross                    63,125.00
Caratuva fee                   -631.25
Network / banking fee           -15.00
BRL paid out                 62,478.75
```

The exact fee structure depends on your contract. Talk to your account manager if you need a detailed breakdown for accounting.

## Tax reporting

For Brazilian sellers, every settled invoice generates an entry in your transfer-pricing report, available via the API (`GET /v1/reports/transfer-pricing`) as JSON, CSV, or PDF, sliced quarterly. (There's no dashboard reports screen yet.) Hand it to your accountant directly.

We do not file your taxes for you. We do hand you exactly the data your accountant needs.

## Changing your destination

Updating the PIX key is a single click on the **Payout** page. The new key takes effect for any invoice that hasn't yet entered `offramp_pending`. Invoices already in flight pay out to the previous destination — we won't redirect mid-flight.

Admin action. Treasurers and viewers can view but not change.

## Best practices

* **Use a CNPJ-keyed account** — clearest audit trail.
* **Keep your PIX key clean** — registering a CPF key on a corporate account works but adds friction during reconciliation.
* **Reconcile by external ID** — if you create invoices with a stable external/reference ID, every PIX deposit traces back to the original order in seconds.
* **Don't pool destinations** — one organization, one destination, with rare exceptions. Pooling makes reconciliation painful for everyone.
