ASApexlink Suite
Guides › Compliance

Joining Open Finance Brasil: Central Bank Rules, API Platform Costs and Timeline

Whether the Central Bank requires you to join Open Finance Brasil or you're choosing to, here's what participation involves, what the API and consent layer typically costs, and a realistic 9 to 18-month timeline.

Apexlink Suite editorial team · November 2026 · 10 min read

Mandatory participant or voluntary entrant: where your institution falls

Before you look at architecture or vendors, settle one question: do Brazilian rules already require you to participate, or would you be joining by choice? The answer sets your deadline, your scope and how much room you have to negotiate with vendors.

Open banking Brazil began under a 2020 joint resolution of the National Monetary Council (CMN) and the Central Bank of Brazil (BCB). The regime was renamed Open Finance Brasil once its scope grew beyond current accounts to cover credit, investments, foreign exchange and other products. Insurance and pension data sit in a parallel regime, Open Insurance, supervised by SUSEP rather than the BCB.

Advertisement

The basic split works like this:

  • Mandatory participants. Institutions in the largest prudential segments (S1 and S2) have to share customer data in the regulated categories. Institutions that hold customers' transactional accounts and take part in Pix generally also carry obligations as account holders for payment initiation.
  • Voluntary participants. Other BCB-authorized institutions, such as smaller banks, credit cooperatives, payment institutions, direct credit companies (SCDs) and peer-to-peer lending companies (SEPs), can join to receive data, initiate payments, or both.
  • Payment initiation service providers (ITPs). Firms whose business is initiating payments need a specific BCB authorization as an ITP.

Voluntary entrants usually miss the reciprocity rule. If you join to receive customer data, you're generally required to share the equivalent data you hold. Joining "just to consume" isn't an option, so a lender that wants account data for underwriting has to budget for a sharing stack too.

Foreign institutions can't passport in. You'll need a Brazilian entity authorized by the BCB, or a licensed local partner. Segment classification, reciprocity scope and Pix-related obligations change through new resolutions, so confirm your exact obligations with Brazilian regulatory counsel before you fix a budget.

What a participant actually has to run under Central Bank rules

Brazil standardizes almost everything, unlike markets that leave much to bilateral agreements. The Open Finance Brasil governance structure publishes API specifications, security profiles, customer-experience guidelines and performance requirements, and every participant implements the same ones. That cuts design work. It also leaves little room to cut corners.

Core requirements for a typical participant:

  • Directory registration. Every participant registers in the central Directory, publishes its API endpoints there and obtains the digital certificates used for transport and signing. Brazilian certificate requirements (ICP-Brasil) apply.
  • Security profile. APIs follow the Brazilian FAPI (Financial-grade API) profile: OAuth 2.0 and OpenID Connect with mutual TLS, signed requests and strict token handling. Your authorization server has to pass the official conformance tests.
  • Functional certification. Each API family you expose, such as accounts, cards, loans, consents or payments, must pass functional conformance testing before production.
  • Consent management. Customers grant consent for specific data groups and a limited period, with a maximum duration set by the rules. They can see and revoke consent through either institution. You need a consent store, revocation propagation and dashboards that meet the customer-experience guidelines.
  • Performance and availability. Specifications set minimum uptime, response-time limits and call limits. Participants report operational metrics to a central platform, and poor performance is visible to the ecosystem.
  • Data protection. Brazil's LGPD applies on top of the open finance rules, with oversight from the national data protection authority (ANPD). Open finance consent doesn't automatically cover every downstream use, so your legal basis for analytics or marketing needs separate review.
  • Dispute handling. Participants must support inter-institution incident and dispute processes and keep service desks that meet response deadlines.

Plan for continuous change. Specifications are updated regularly, and an update can mean re-certification. A platform that can't absorb those updates will cost you more than it saved at launch.

Pix API integration: the payment-initiation scope entrants underestimate

Most payment initiation in Open Finance Brasil runs over Pix. If you're the account holder, your systems receive a payment consent from an ITP, authenticate the customer in your own channel (usually the mobile app), and then execute the Pix transfer through your existing connection to the BCB's instant payment infrastructure. If you're the ITP, you build the mirror image of that flow.

The open finance APIs are only one part of Pix API integration. Most of the real work sits behind them:

  • Redirect journeys. Customers move from the ITP's app to the account holder's app and back. App-to-app deep linking, session handling and timeouts must meet the experience guidelines, and conversion depends on getting them right.
  • Recurring and scheduled payments. Scheduled Pix, recurring consents and Pix Automático, Brazil's direct-debit-style recurring product, need extra consent types, limit handling and lifecycle management.
  • Journeys without redirection. Newer flows that skip the app redirect add device binding and risk controls.
  • Fraud and limits. Pix fraud controls, transaction limits and the special return mechanism (MED) all interact with initiated payments. Your fraud engine has to tell initiated payments apart from customer-originated ones.

A practical test for vendors: ask them to show a recurring-payment consent being created, used, modified and revoked, end to end, against the current specification version. A vendor that can only demo single immediate payments is selling last year's scope.

Build, buy or hybrid for the open banking API platform

You have three realistic options for the API, security and consent layer. Choose based on how many API families you need, how much regulated engineering capacity you already have in Brazil, and whether open finance is central to your product or a compliance line item.

OptionBest fitMain advantageMain risk
Build in-houseLarge S1/S2 banks with established API and identity teamsFull control over performance, customer journeys and the roadmapOngoing cost of keeping up with specification changes and re-certification
Buy a specialist open banking API platformMid-sized banks, payment institutions and lenders that need sharing and receivingPre-certified components and specification updates bundled into the contractLock-in, plus dependence on the vendor's release speed
Hybrid or as-a-serviceFintechs and ITPs that need fast entry or want to receive data onlyQuickest route to production, with usage-based pricingLess control over the customer experience, and per-call costs that rise at scale

The vendor market splits into layers. Brazilian providers such as Sensedia sell API management and open finance platforms for institutions. Belvo, Pluggy and Iniciador are among those offering data aggregation, payment initiation or ITP-as-a-service. Raidiam provides directory and trust-framework technology, and international open banking vendors have also entered the market. Each covers a different slice, so verify the exact Brazilian certifications each one holds rather than relying on marketing.

For most mid-sized institutions, buying the security and consent layer and building the customer journeys in-house is the better fit. Conformance testing and specification churn sit mostly in the authorization server and consent store. Customer experience and fraud controls separate you from competitors and should stay in-house.

Red flags in vendor proposals:

  • Certification claims with no specific API families or specification versions listed
  • No contractual commitment on how quickly the vendor adopts new mandatory specification versions
  • Uptime SLAs below the regulatory minimum, or no service credits tied to them
  • Pricing that charges for consent renewals or failed calls without saying so
  • Data hosted outside Brazil with no LGPD transfer analysis

Indicative cost ranges and what drives them

The figures below are typical 2026 market ranges in USD for a single institution. They vary widely with contract terms, volumes, currency movements and scope. Brazilian vendors usually quote in BRL, so treat these as planning ranges and confirm current pricing directly with vendors.

Cost lineBuild in-houseBuy platformAs-a-service
Initial implementation$1.5M to $4M (internal team of 12 to 25 over 9 to 15 months)$150K to $600K, plus internal integration work$20K to $150K setup
Annual platform or run cost$500K to $1.5M (staff, infrastructure, re-certification)$120K to $600K subscriptionMonthly minimums of roughly $2K to $15K
Usage-based feesNone beyond infrastructureSometimes tiered by API call volumeOften priced per call or initiated payment; fractions of a dollar
Specification updatesInternal engineering, a meaningful share of run costUsually included; confirmIncluded

Every option carries additional costs: governance and directory contributions, certificate issuance and renewal, conformance testing, external security testing, legal and LGPD review, and customer-service staffing for open finance disputes. Budget roughly $100K to $400K a year for these at mid-size scale.

What drives the numbers up:

  • Number of API families. Sharing accounts, cards, loans, financing, investments and FX each adds endpoints, tests and data mapping from your core systems.
  • Core system quality. Pulling clean, real-time data out of legacy cores is often the biggest cost, and buying a platform doesn't remove it.
  • Payment scope. Recurring Pix and non-redirect journeys cost far more than single immediate payments.
  • Volume. Usage pricing that looks cheap at launch can overtake a flat subscription once data receivers poll your APIs at scale.

Hypothetical example: say a mid-sized payment institution with around 2 million accounts must share account and card data under reciprocity and act as account holder for Pix payment initiation. A platform purchase at $350K implementation and $250K a year, plus $400K of internal core integration and $200K a year in governance, certificates and staffing, comes to about $1.2M in year one and $450K a year after that. A full in-house build at the same scope would plausibly cost two to four times more in year one.

A phased timeline from scoping to production

Realistic timelines run 9 to 18 months for institutions that already hold a BCB authorization. A firm that needs a new authorization, such as an ITP or payment institution license, should add the regulator's review period, which can take many months.

PhaseTypical durationKey outputs
Regulatory scoping4 to 8 weeksCounsel's opinion on mandatory and reciprocal scope, list of roles and API families
Vendor selection and contracting6 to 12 weeksSigned contract with certification, SLA and specification-update commitments
Directory onboarding and certificates4 to 8 weeks, run in parallelDirectory registration, ICP-Brasil certificates, sandbox access
Build and core integration4 to 9 monthsAPIs mapped to core data, consent store, customer journeys, fraud rules
Security and functional certification6 to 12 weeksPassed FAPI conformance and functional tests for each API family
Controlled production and scale-up2 to 3 monthsLive traffic with metric reporting, a tuned service desk, and a roadmap for the next specification versions

Two scheduling mistakes come up again and again. The first is starting core integration after the platform is installed; data mapping is the longest task and should begin in week one. The second is treating certification as a final gate. Run conformance tests from the first sandbox build, because late failures are expensive to fix.

The decision rule: if you're in S1 or S2, or Pix account-holder obligations already apply to you, start regulatory scoping and vendor selection now, because your timeline is set for you. If you're a voluntary entrant, commit only once you can name the revenue that received data or initiated payments will produce, and once you've priced the reciprocity obligation that comes with it.

Common questions

Is participation in Open Finance Brasil mandatory for every bank?

No. Data sharing is mandatory for institutions in the largest prudential segments (S1 and S2), and institutions holding transactional accounts generally have payment-initiation obligations. Smaller authorized institutions can join voluntarily, but reciprocity rules then usually require them to share equivalent data. Confirm your specific status with Brazilian regulatory counsel.

Can a foreign fintech access Brazilian open finance data without a local license?

Not directly. Participants must be institutions authorized by the Central Bank of Brazil, so a foreign firm needs a licensed Brazilian entity or a partnership with a licensed provider, such as an authorized ITP or data-aggregation platform. The partner route is faster but gives you less control over the customer journey.

How long does it take to go live?

For an institution that already holds a BCB authorization, 9 to 18 months is a realistic range from scoping to production. Core system integration and certification are usually the longest tasks. If you need a new authorization first, add the Central Bank's review period, which can take many months.

What does an open banking API platform cost in Brazil?

As typical 2026 market ranges, buying a platform usually costs about $150K to $600K to implement and $120K to $600K a year, while a full in-house build often runs $1.5M to $4M upfront. As-a-service options start much lower but charge per call or per payment. Prices vary by contract and are often quoted in BRL, so confirm with vendors.

Do we need to support Pix Automático and recurring payments from day one?

That depends on your role and on which specification versions are mandatory when you launch, and that changes over time. Account holders should plan for recurring and scheduled Pix consents early, because adding them later can mean re-certification. Ask vendors to demo the full recurring-consent lifecycle before you sign.

Does open finance consent cover our use of the data under LGPD?

Not automatically. Open finance consent covers specific data groups for a stated purpose and period, while other uses such as marketing or model training may need a separate legal basis under LGPD. Have a data protection lawyer review your intended uses before you design data pipelines.

Written by the Apexlink Suite editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.