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

# Receivables

> How to receive money on Trio: Pix QR codes, boletos, Pix Automático, fees, split payments and sandbox simulations.

A **receivable** is money that arrives in one of your bank accounts: a dynamic QR code your customer pays, a boleto settled at any bank, or a Pix Automático collection debited on its due date. On V2 every receivable is created against a `bank_account_id`, the account that receives the funds, and becomes an **in document** once it is paid.

## Choose how to get paid

| You want to | Use | Guide |
| - | - | - |
| Charge a known amount right now | Dynamic QR code | [Cash in](https://docs.trio.com.br/v2/guides/receivables/cash-in.md) |
| Let customers pay any amount, repeatedly | Static QR code | [QR code types](https://docs.trio.com.br/v2/guides/pix/qr-codes.md) |
| Charge with a due date, discount, fine or interest | Dynamic QR code with due date, or a boleto | [QR code types](https://docs.trio.com.br/v2/guides/pix/qr-codes.md), [Create a boleto](https://docs.trio.com.br/v2/guides/boleto/create-boleto.md) |
| Issue a bank slip that also carries a Pix QR code | Boleto | [Create a boleto](https://docs.trio.com.br/v2/guides/boleto/create-boleto.md) |
| Charge a subscription without asking each time | Pix Automático | [Pix Automático](https://docs.trio.com.br/v2/guides/receivables/using-pix-automatic.md) |

## Guides

> **[Cash in](https://docs.trio.com.br/v2/guides/receivables/cash-in.md)**
>
> Create your first dynamic QR code and read the response.

> **[QR code types](https://docs.trio.com.br/v2/guides/pix/qr-codes.md)**
>
> Static, dynamic and dynamic-with-due-date QR codes, and what each returns.

> **[Pix Automático](https://docs.trio.com.br/v2/guides/receivables/using-pix-automatic.md)**
>
> Recurrences, collections and attempts, from authorization to settlement.

> **[Create a boleto](https://docs.trio.com.br/v2/guides/boleto/create-boleto.md)**
>
> The full request: charge, payer, due date, discounts, fine and interest.

> **[Boleto types](https://docs.trio.com.br/v2/guides/boleto/boleto-types.md)**
>
> Every invoice type and wallet type value.

> **[Boleto best practices](https://docs.trio.com.br/v2/guides/boleto/best-practices.md)**
>
> Hybrid boleto and Pix, payer data, lifecycle and due date versus expiration.

> **[Fees](https://docs.trio.com.br/v2/guides/receivables/fees.md)**
>
> Charge a fee on a receivable and keep the margin above your Trio cost.

> **[Split payments](https://docs.trio.com.br/v2/guides/receivables/split-payments.md)**
>
> Distribute a receivable among split recipients.

> **[Document lifecycle](https://docs.trio.com.br/v2/guides/pix/document-lifecycle.md)**
>
> The statuses an in document goes through after the payment.

> **[Simulate a successful deposit](https://docs.trio.com.br/v2/guides/receivables/simulating-deposit-success.md)**
>
> Pay a QR code in the sandbox and watch the document settle.

> **[Simulate deposit failures](https://docs.trio.com.br/v2/guides/receivables/simulating-deposit-failures.md)**
>
> Make a sandbox account refuse deposits to test your error handling.

> **[API reference](https://docs.trio.com.br/v2/api-reference/banking-api/documents/receivables/list-receivables.md)**
>
> List, read and search in documents and their refunds.

> [!NOTE]
>
> Pix biometrics, the web enrollment and payment authorization flow, has no endpoints on the API.

## What happens after the payment

Trio records the payment as an in document, sends the webhook events you subscribed to, and credits the bank account. Read the [Document lifecycle](https://docs.trio.com.br/v2/guides/pix/document-lifecycle.md) for the statuses, and [Webhooks](https://docs.trio.com.br/v2/webhooks/introduction.md) for the events.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.