What is Lina Pay?
Lina Pay is our payment initiation product built on top of Open Finance. It lets companies that are not Open Finance participants offer Pix payments in every modality regulated by the Central Bank of Brazil, with full compliance to the regulatory, technical, and security requirements required to operate as a Payment Transaction Initiator.
What is Open Finance?
Open Finance is an initiative led by the Central Bank of Brazil (BCB) with the goal of making the financial market more modern, efficient, and competitive. In practice, it is a technological ecosystem that connects Brazilian financial institutions in a standardized architecture, enabling the secure sharing of data and services through APIs and rigorous security protocols.
Lina's role in Open Finance
Lina is an institution authorized by the BCB to operate as a Payment Transaction Initiator (ITP), offering payment services that connect a company that is not a participant of Open Finance so that it can initiate payments.
In practice, as an ITP, Lina performs financial movements by communicating through Open Finance between the payer's financial institution and the receiver's financial institution. Lina does not take part in the financial movement between the payer's and the receiver's accounts.
The Lina Pay solution
Lina Pay is the solution that meets every regulatory, technical, and security requirement needed to connect a company that is not an Open Finance participant with more than 200 financial institutions to perform financial transactions across all Pix modalities available and regulated by the BCB.
Characteristics of Lina Pay
Companies and linked companies (tenants and subtenants)
Lina Pay allows a company (tenant) to have one or more linked companies (subtenants). This architecture separates payments by tenant and subtenant, keeping credentials isolated and unique configurations such as webhook delivery and branding customization per company.
Integration options
- White Label: a White Label portal that follows the minimum user experience requirements defined by the BCB and supports customization of logo, colors, and fonts per tenant and subtenant.
- APIs: APIs that can be integrated directly or through an SDK, allowing the journey to be fully personalized inside your own product.
Payer journey types
- Redirect-based: the user is redirected to their bank and approves the payment there.
- Redirectless: the user goes through a one-time redirect-based journey to link the device to a personal account. After finishing that journey, payments can be approved using a device credential such as fingerprint or Face ID, removing the need to redirect the user to their bank to approve payments or authorizations.
Pix modalities
Pix
| Attribute | Value |
|---|---|
| Description | Instant single payment with same-day settlement (D+0). |
| Payer | Individual and Legal Entity |
| Receiver | Individual and Legal Entity |
| Amount | Fixed |
| Use cases | E-commerce; P2P transfers |
| Supports cancellation? | No |
| Supports retry? | No. If the payment fails, a new request must be submitted. |
Scheduled Pix
| Attribute | Value |
|---|---|
| Description | Instant single payment with settlement on the date specified in the request (D+N). |
| Payer | Individual and Legal Entity |
| Receiver | Individual and Legal Entity |
| Amount | Fixed |
| Use cases | Personal services; P2P transfers |
| Supports cancellation? | Yes. It must be requested at least one day before the scheduled payment date. |
| Supports retry? | No. If the payment fails, a new request must be submitted. |
Recurring scheduled Pix
| Attribute | Value |
|---|---|
| Description | Recurring payments with quantity or dates predefined at the time of the request. |
| Payer | Individual and Legal Entity |
| Receiver | Individual and Legal Entity |
| Amount | Fixed |
| Recurrence type | Daily; Weekly; Monthly; or Custom (predefined dates). |
| Use cases | Fixed recurrences |
| Supports cancellation? | Yes. Supports cancelling every payment or just a single payment. |
| Supports retry? | No. If a payment fails, no new charge is attempted. |
Smart Pix
| Attribute | Value |
|---|---|
| Description | Immediate financial transfer between accounts owned by the same holder, triggered either by a user action or automatically. The user can define transaction limits per day and/or per amount and/or per number of payments. |
| Payer | Individual and Legal Entity |
| Receiver | Accounts owned by the same holder as the payer |
| Amount | Fixed |
| Use cases | Cash-in; BFM; PFM |
| Supports cancellation? | Supports cancelling the authorization, but does not support cancelling the payment itself. |
| Supports retry? | No. If a payment fails, no new charge is attempted. |
Automatic Pix
| Attribute | Value |
|---|---|
| Description | Payments for recurring charges with configurable limits, amounts, deadlines, periodicity, onboarding payment, and retry support. |
| Payer | Individual and Legal Entity |
| Receiver | Legal Entity |
| Amount | Fixed or Variable |
| Use cases | Streaming; Subscriptions; Utility bills; Tuition fees |
| Recurrence creation | Through a Lina recurrence engine or managed by the company. Recurrences must be created between 2 and 10 days before the charge due date. |
| Supports cancellation? | Supports cancelling the authorization and recurring payments up to one day before settlement. |
| Supports retry? | Yes. Allows up to three retries within 7 days after a recurring payment is declined. Retries must follow the payment creation rule of at least 2 days before the new attempt date. |
Next steps
- Get your credentials — request an OAuth 2.0 access token to authorize API calls.
- Onboarding — configure your sub-tenant and register redirect domains before initiating Pix payments.
- Instant Pix overview — end-to-end flow for initiating Instant Pix payments.
- Scheduled & recurring Pix — future-dated and recurring Pix with webhooks and polling after consent.
- JSR (Redirectless) — one-time enrollment at the bank, then Pix with FIDO2 without redirecting again.
- Smart Pix — Sweeping and automatic payments with recurring consent, redirect at the holder, then recurring payment APIs.
- Automatic Pix — Open Finance automatic payments (
recurringConfiguration.automatic), billing cycles, retries, and initiation APIs.