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

# Overview

> Scope, architecture and conventions of the Fincle payments API.

The Fincle API is a programming interface for processing payments by Pix, credit card and boleto. This documentation describes the full lifecycle of a transaction: creation of the charge, confirmation of payment, retrieval, refund, handling of infractions under the Special Return Mechanism (Mecanismo Especial de Devolução, MED) and transfer of the balance to the payee.

## Scope

This documentation is intended for engineering teams responsible for integrating their own systems with the platform. It assumes familiarity with the HTTP protocol, the JSON format and the basic concepts of the Brazilian payment schemes.

| Domain | Content |
| - | - |
| Charges | Creation of charges by [Pix](https://docs.fincle.com.br/guides/pix.md), [credit card](https://docs.fincle.com.br/guides/card.md) and [boleto](https://docs.fincle.com.br/guides/boleto.md), and recurring billing through [subscriptions](https://docs.fincle.com.br/guides/subscriptions.md). |
| Transactions | Statuses of a transaction and the transitions between them, described in [Transaction lifecycle](https://docs.fincle.com.br/guides/transaction-lifecycle.md). |
| Notifications | Asynchronous communication of events through [webhooks](https://docs.fincle.com.br/guides/webhooks.md). |
| Post-payment | [Refunds](https://docs.fincle.com.br/guides/refunds.md), [infractions and MED](https://docs.fincle.com.br/guides/infractions-and-med.md) and [balance and transfers](https://docs.fincle.com.br/guides/balance-and-transfers.md). |
| Compliance | [Security and data protection](https://docs.fincle.com.br/guides/security.md) and [regulatory references](https://docs.fincle.com.br/guides/regulatory-references.md). |

## Interface characteristics

The API follows the REST architectural style over HTTPS. Messages are exchanged in JSON (RFC 8259), encoded in UTF-8. The production base URL is `https://api.fincle.com.br`.

Monetary amounts are integers expressed in cents of Brazilian real (BRL, ISO 4217). Dates and times follow ISO 8601. Authentication relies on a short-lived access token issued from an API key.

## Operating model

Creation of a charge is synchronous: the response contains the transaction identifier and the data required for payment. Confirmation of payment is asynchronous for Pix and boleto, and the platform communicates it to the integrator's system by notification. It is recommended that the integration treat the notification as the trigger for releasing the product or service and use retrieval of the transaction as the reference source for verification.

> [card] [Quickstart](https://docs.fincle.com.br/quickstart.md)
>
> From issuance of the token to confirmation of the first payment.

> [card] [Transaction lifecycle](https://docs.fincle.com.br/guides/transaction-lifecycle.md)
>
> Statuses, transitions and associated events.

> [card] [Infractions and MED](https://docs.fincle.com.br/guides/infractions-and-med.md)
>
> Effects of an infraction report on the transaction and the balance.

> [card] [Regulatory references](https://docs.fincle.com.br/guides/regulatory-references.md)
>
> Applicable laws, regulations and technical standards.


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