Open Finance in Brazil: What Your Open Banking API Platform Must Handle
Brazil's Open Finance rules fix your API scope, security profile, Pix journeys and certification before anyone writes code. Here's what your platform has to handle, what it typically costs and how long it takes to go live.
Your participation role decides most of your API obligations
Settle one question before you compare vendors: what role will your institution play in Open Finance Brasil? That role sets the scope of the open banking API platform Brazil's rules require you to run. It decides which APIs you expose, which you consume and which licenses you need. A large retail bank, a payment institution and a foreign fintech entering the market end up with very different builds.
The Banco Central do Brasil (BCB) and the National Monetary Council (CMN) set the framework. Day-to-day technical standards come from an industry governance structure that the regulator oversees. The scope is wider than UK or EU open banking. Beyond current accounts and payments, it covers credit, investments and foreign exchange. Insurance and pensions run under a parallel Open Insurance regime supervised by SUSEP, the insurance regulator.
The rollout came in four phases, and they still map onto the API families vendors will ask you about:
- Phase 1: public data. Product, channel and fee information, published through open APIs with no customer consent.
- Phase 2: customer data sharing. Registration data, accounts, credit cards and credit operations, shared with the customer's consent.
- Phase 3: services. Pix payment initiation through licensed initiators, plus forwarding of credit proposals.
- Phase 4: extended data. Investments, foreign exchange and other products.
Data sharing is mandatory for the largest prudential segments (the S1 and S2 banking conglomerates). Smaller institutions can generally join voluntarily, but reciprocity then applies: if you receive data, you must share the equivalent data you hold. Institutions that offer Pix through transactional accounts are generally expected to accept initiation requests from authorized initiators. Any third party that wants to initiate payments needs BCB authorization as a payment initiation service provider (an ITP, iniciador de transação de pagamento).
An international fintech usually has three routes:
- Set up a Brazilian entity and get your own authorization.
- Partner with a licensed participant that runs Open Finance for you.
- Start as a data receiver through a licensed partner while your own authorization is in progress.
Segment, reciprocity and licensing rules are detailed and get revised regularly. Have a Brazilian regulatory adviser confirm your obligations in writing before you fix the platform scope.
API scopes and Pix payment initiation journeys you have to support
Once your role is clear, platform scope becomes a list of API families and versions published by the governance structure. Each family has a mandatory version and a deadline for adopting new ones. Under-scoping is the most common RFP mistake. Teams cost out the account and consent APIs, then discover metrics reporting, service desk integration and version migrations after signing.
| Capability | Who typically needs it | What the platform must do |
|---|---|---|
| Public product data APIs | All participants | Publish product, channel and fee data without authentication, kept in sync with core systems |
| Consent and resource APIs | Data transmitters and receivers | Create, authorize, read and revoke consents and map them to permitted data groups |
| Accounts, cards, credit and customer data APIs | Transmitters holding these products | Serve standardized data from core banking, card and loan systems within performance limits |
| Payment initiation (Pix) | Account holders and ITPs | Process single, scheduled and recurring Pix payments, including status notifications and cancellations |
| Investments, FX and other Phase 4 data | Institutions offering those products | Map varied product systems to the standard schemas |
| Metrics, service desk and directory integration | All participants | Report availability and performance, handle inter-participant tickets and keep directory registrations current |
Pix initiation is where scope grows fastest. The basic flow redirects the payer from the initiator to the account holder to authenticate and approve. The standards now go further: scheduled payments, recurring payments (including automatic sweeps between accounts held by the same owner, known as smart transfers) and no-redirect journeys. In a no-redirect journey, the customer links a device once and later approves payments without leaving the initiator's app. That model underpins contactless-style Pix, and it needs device enrollment, FIDO-based authentication and risk signals your stack may not have today. If your current authentication layer can't do device binding, price that work separately; it is rarely in a platform vendor's base quote.
Consent journeys are prescribed in unusual detail. The customer experience guidelines set the steps, wording, permission groupings and what the customer must see before redirect and on return. Consent management must also handle revocation from either side, expiry and renewal under current validity rules, and a customer-facing dashboard of active consents. The governance structure monitors journey performance, including how many customers complete the account holder's authentication step, so a slow or confusing journey is a compliance issue, not just a UX one.
Security profile, directory registration and open banking certification in Brazil
Brazil runs a localized version of the OpenID Foundation's Financial-grade API (FAPI) profile. In practice your platform needs:
- Mutual TLS with ICP-Brasil certificates. Transport and signing certificates come from Brazil's public key infrastructure, so you need a process to issue and rotate them.
- Dynamic client registration. Receivers register with transmitters automatically using software statements from the central participant directory, and transmitters must validate them in real time.
- Signed and, where required, encrypted messages. Payment requests and responses use signed JWTs, verified against keys published in the directory.
- An authorization server that conforms to the Brazilian profile. Many general-purpose identity products need extra work for Brazil-specific claims, consent binding and token rules.
The directory is the trust anchor. Every participant registers its organization, authorization servers, API endpoints and software statements there. If your directory entries drift from production behavior, other participants' calls fail.
Certification has two layers. Security conformance is tested against the OpenID Foundation's FAPI and dynamic client registration suites, configured for the Brazilian profile. Functional conformance checks each API family and version against the specifications. Both must be passed and published before go-live, and again whenever you adopt a mandatory new version. The security baseline will also move as the standards roadmap shifts toward newer FAPI versions. Ask each vendor how it handled earlier migrations and who paid for them; the answer tells you who will pay for the next one.
Red flags in a vendor pitch:
- No current certifications for the Brazilian profile and API versions, either in the vendor's name or on live client deployments
- Certification priced as a one-off project fee rather than a recurring obligation
- No ICP-Brasil certificate lifecycle tooling, or certificates tracked manually
- No production references with Brazilian participants on core systems similar to yours
Build versus vendor: what drives the cost
Few institutions build the full stack. The usual pattern is a specialist Open Finance platform for the gateway, consent, authorization server and directory integration, with the institution building adapters to its own core banking, card and Pix systems. The market includes Brazilian API management specialists such as Sensedia, international open banking platform vendors with Brazilian deployments, directory and trust specialists such as Raidiam, and aggregators and initiation providers such as Belvo, Pluggy, Iniciador and Celcoin for institutions that mainly want to consume rather than expose. Their capabilities only partly overlap, and authorization status changes, so map each one to your role and confirm its current licenses before comparing prices.
| Cost component | Specialist vendor (indicative) | In-house build (indicative) |
|---|---|---|
| Implementation and integration | USD 150,000-600,000 | USD 600,000-2,000,000 in engineering effort |
| Annual platform license or subscription | USD 80,000-400,000 | Not applicable; replaced by internal maintenance |
| Annual run and maintenance (versions, certification, support) | Sometimes included, otherwise USD 50,000-200,000 | A permanent team, often in the range of 6-15 engineers and specialists |
| Initiation as a service via a licensed ITP | Per-transaction fees or monthly minimums, often from a few thousand USD a month | Requires your own ITP authorization and full stack |
These are typical 2026 market ranges. They vary widely with scope, volume and contract terms, and quotes in Brazilian reais can differ from USD pricing. Confirm with vendors.
What moves the number most:
- Number of API families and products. A bank offering investments, FX and credit cards has several times the mapping work of a digital payment institution.
- Core system readiness. Legacy cores that can't serve near-real-time data within required response times need caching or event-streaming layers.
- Version cadence. Mandatory versions arrive regularly, and each one means development, testing and recertification.
- Pix journey depth. No-redirect and recurring payments add device binding, fraud controls and more certification.
- Service levels. Availability and latency targets require resilient infrastructure and 24/7 operations.
A hypothetical example: say a mid-sized payment institution with accounts, cards and Pix wants to become a transmitter and an account holder for initiation. On a specialist platform, a plausible first-year budget is USD 400,000-900,000 including integration, with later years at USD 150,000-450,000. An in-house build would typically cost materially more in year one and put version and certification risk on a team that's hard to hire in Brazil's competitive engineering market.
Our position: outside the S1-S2 segments, buy the platform. Build only if open APIs are central to your product strategy and you already run a mature API and identity engineering team.
Realistic go-live timelines and how to sequence the work
Plan in months. With the right authorizations already in hand, a voluntary participant on a specialist platform typically goes live with an initial scope in 6-12 months; an in-house build usually takes 12-24. For foreign entrants, licensing often sets the schedule. Establishing a Brazilian entity and obtaining BCB authorization as a payment institution or ITP can take a year or more, which is why many start through a licensed partner.
- Confirm role and obligations (weeks 1-6). With a local regulatory adviser, confirm your segment, reciprocity exposure, required API families and licensing path.
- Join governance and the directory (weeks 4-12). Sign the participation agreements, set up your organization in the sandbox directory and order ICP-Brasil certificates.
- Select the platform and map your cores (months 2-4). Run proofs of concept against your actual core, card and Pix systems, not vendor demo data.
- Build, integrate and test in the sandbox (months 3-9). Build adapters and consent journeys to the experience guidelines, then run interoperability tests with other participants.
- Certify and launch (months 6-12). Pass the security and functional suites, publish results, register production endpoints and start metrics reporting.
- Run continuously. Budget from day one for annual version changes, recertification and service desk handling.
A decision rule: if authorization, directory registration and core-data access aren't confirmed by month four, go live first as a data receiver or through an initiation-as-a-service partner, and add transmitter and account-holder scope once that foundation is stable. Before issuing an RFP, get a written scope memo from your regulatory adviser and require every shortlisted vendor to price against it line by line.
Quick answers
Is participation in Open Finance Brasil mandatory for my institution?
Data sharing is mandatory for the largest banking conglomerates in the S1 and S2 prudential segments, and institutions offering Pix through transactional accounts are generally expected to accept initiation requests from authorized initiators. Others can usually join voluntarily, but reciprocity then requires them to share equivalent data. Segment rules change over time, so have a Brazilian regulatory adviser confirm your status.
Can a foreign fintech initiate Pix payments in Brazil without a local license?
Initiating payments as a principal requires BCB authorization as a payment initiation service provider, which in practice means a Brazilian entity. Many foreign entrants start with an already-licensed initiator offering initiation as a service while they pursue their own authorization. The partner contract should state clearly who is responsible for consumer protection, data protection and fraud.
How long does open banking certification in Brazil take?
On a mature platform, the security and functional conformance tests for an initial scope usually take a few weeks to a few months, most of it spent fixing failures found in testing. Certification isn't one-off: each mandatory API version and security update requires new conformance runs, so budget for it every year.
What does an open banking API platform in Brazil typically cost?
As a typical 2026 market range, a specialist vendor deployment often costs USD 150,000-600,000 to implement plus USD 80,000-400,000 a year in licensing, depending on scope, volume and contract terms. In-house builds usually cost considerably more in the first year and need a permanent team. Pricing in reais can differ from USD quotes, so confirm with vendors.
How does Brazilian data protection law interact with Open Finance consent?
Open Finance consent is a specific, regulated authorization to share defined data groups. It sits alongside your obligations under the LGPD, Brazil's general data protection law, rather than replacing them. You still need a lawful basis, retention rules, data-subject rights processes and security controls for the data you receive. Have privacy counsel review how consent records, revocations and downstream uses are handled.
Should we start as a data receiver or a transmitter?
If your obligations allow it, starting as a receiver is usually faster and cheaper because you consume standardized APIs instead of mapping your own cores to them. Bear in mind that voluntary participants who receive data generally take on reciprocity obligations to share equivalent data, so plan the transmitter build even if it comes second. Confirm the sequencing with your regulatory adviser.
Written by the Trustdeskapp editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.