Skip to main content
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

​
Guides

Cash in

Create your first dynamic QR code and read the response.

QR code types

Static, dynamic and dynamic-with-due-date QR codes, and what each returns.

Pix Automático

Recurrences, collections and attempts, from authorization to settlement.

Create a boleto

The full request: charge, payer, due date, discounts, fine and interest.

Boleto types

Every invoice type and wallet type value.

Boleto best practices

Hybrid boleto and Pix, payer data, lifecycle and due date versus expiration.

Fees

Charge a fee on a receivable and keep the margin above your Trio cost.

Split payments

Distribute a receivable among split recipients.

Document lifecycle

The statuses an in document goes through after the payment.

Simulate a successful deposit

Pay a QR code in the sandbox and watch the document settle.

Simulate deposit failures

Make a sandbox account refuse deposits to test your error handling.

API reference

List, read and search in documents and their refunds.
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 for the statuses, and Webhooks for the events.