Open Finance Beyond Open Banking: How Data Portability Is Reshaping Financial Services
Open finance extends open banking from payments to investments, insurance, and pensions, enabling true financial data portability.
Open finance extends the principles of open banking far beyond payment accounts. Where open banking gave consumers the ability to share transaction data with third-party apps, open finance applies the same data portability to investments, mortgages, insurance policies, pensions, and credit records. The result is a shift from fragmented financial profiles locked inside individual institutions toward a world where consumers own and control a comprehensive view of their financial lives.
This transition is not hypothetical. Brazil already operates the most comprehensive open finance system in the world, processing over 102 billion API calls in 2024 alone. The EU has proposed FIDA (Financial Data Access) regulation to extend data sharing to pensions, insurance, and crypto assets. The UK's FCA published a formal open finance roadmap in April 2026 targeting a 2028-2030 launch. Globally, 137 billion open banking API calls were made in 2025, projected to reach 722 billion by 2029, according to Juniper Research.
What Is Open Finance and How Does It Differ from Open Banking?
Open banking, as implemented under the EU's PSD2 directive and the UK's Competition and Markets Authority order, focused on a narrow data set: payment account information and payment initiation. Third-party providers could access current account balances, transaction histories, and initiate payments on behalf of consumers. This created a wave of fintech innovation in budgeting apps, account aggregation, and account-to-account payments.
Open finance takes the same regulatory and technical framework and applies it across the full spectrum of financial products. The scope expansion is significant: instead of seeing only what flows through a current account, consumers and authorized third parties can access data from savings accounts, investment portfolios, mortgage products, insurance policies, pension entitlements, and even crypto-asset accounts.
| Dimension | Open Banking | Open Finance |
|---|---|---|
| Data scope | Payment accounts (current/checking) | All financial products: savings, investments, mortgages, insurance, pensions, crypto |
| Primary use cases | Account aggregation, payment initiation | Cross-product financial planning, competitive switching, credit assessment |
| Regulatory examples | PSD2 (EU), CMA Order (UK), Section 1033 (US) | FIDA (EU), FCA Roadmap (UK), Open Finance Brasil, CDR (Australia) |
| Data holders | Banks only | Banks, insurers, asset managers, pension funds, crypto exchanges |
| Compensation model | Free API access (PSD2) | Compensation frameworks under discussion (FIDA allows data holders to charge) |
| Maturity | Live in 78+ countries | Live in Brazil; regulatory proposals in EU, UK, Australia |
Key distinction: Open banking is a subset of open finance. Every open banking implementation is part of the open finance vision, but open finance extends coverage to product categories that open banking never reached: pensions, insurance, investments, and non-bank lending.
The Regulatory Landscape: Who Is Leading Open Finance?
The path to open finance varies dramatically by jurisdiction. Some countries have built comprehensive frameworks from scratch. Others are incrementally extending existing open banking mandates. A few remain stalled. Understanding where each major market stands is essential for fintechs, financial institutions, and developers building payment infrastructure that needs to work across borders.
European Union: PSD3, PSR, and FIDA
The EU is pursuing open finance through two parallel regulatory tracks. The first is the PSD3/PSR package, which modernizes the existing payment services framework. A provisional political agreement was reached in November 2025, with publication in the Official Journal expected by the end of Q2 2026. PSR mandates "performance parity" for open banking APIs: third-party providers must receive the same quality of access as a bank's own digital channels.
The second track is FIDA (Financial Data Access), proposed by the European Commission in June 2023. FIDA extends data-sharing obligations beyond payment accounts to savings, investment accounts, mortgage credit, crypto-asset accounts, occupational and personal pensions, and non-life insurance. It creates a new regulated entity category: the Financial Information Service Provider (FISP).
Unlike PSD2, which mandated free API access, FIDA introduces a compensation framework where data users pay data holders for access. Data sharing is organized through Financial Data Sharing Schemes (FDSS), industry-governed bodies that set technical standards, compensation methodologies, and liability rules. The first trilogue between Parliament, Council, and Commission took place in April 2025, but negotiations paused afterward. Best-case estimates put FIDA's operational obligations around 2029, with a base case of 2030.
United Kingdom: The FCA's Open Finance Roadmap
The UK's Financial Conduct Authority published "Open Finance: Our vision for a smart data future" in April 2026, laying out a phased plan spanning 2026-2030. Phase 1 (2026) prioritizes two high-impact use cases: SME lending and consumer mortgage access. The FCA is running PolicySprints and a Smart Data Accelerator in Q2 2026, with a formal discussion paper on the first open finance scheme planned for Q4 2026. Phase 2 (2027) shapes the regulatory framework. Phase 3 (2028-2030) launches sustainable open finance schemes with governance standards and consumer protections.
The UK's open banking ecosystem is already one of the most mature globally. As of July 2025, the system processed 2 billion API calls in a single month at a 99.46% success rate, with 15.16 million active users representing 26% year-over-year growth. Pension dashboards add another layer: the legal deadline of 31 October 2026 requires occupational pension schemes to connect, with approximately 60 million private pension records (75% of in-scope records) already linked.
Brazil: The Most Advanced Implementation
Brazil's Banco Central do Brasil launched open banking in phases starting February 2021 and rebranded to "Open Finance" in March 2022 when it expanded beyond banking to include insurance, investments, pension funds, and foreign exchange. The system processed 102 billion API calls in 2024 (a 96% year-over-year increase), with over 800 participating institutions connecting more than 100 million customers. Active data-sharing consents grew 44%, reaching 62 million by January 2025.
Brazil's approach is notable for integrating open finance with Pix, the country's instant payment system. Payment initiation through open finance APIs connects directly to Pix rails, creating a seamless flow from data access to payment execution. In late 2025, the BCB launched a credit portability pilot with 26 financial institutions, allowing consumers to transfer loan agreements to competing lenders using standardized open finance APIs.
United States: Section 1033 in Limbo
The CFPB finalized its Section 1033 "Personal Financial Data Rights" rule in October 2024, mandating API-based data access and banning screen scraping. However, a preliminary injunction from the Eastern District of Kentucky in late 2025 prevented enforcement, tolling the first compliance deadline to June 30, 2026. In August 2025, the CFPB issued an Advance Notice of Proposed Rulemaking to reconsider key aspects, including whether financial institutions may charge for data access. As of September 2026, the CFPB has submitted a revised Notice of Proposed Rulemaking to the Office of Information and Regulatory Affairs, but the rule remains described as existing "on paper, but not in practice."
Australia and Asia-Pacific
Australia's Consumer Data Right (CDR) is active in banking and energy, with Version 8 Rules extending coverage to non-bank lenders (including buy now, pay later products) from July 2026. In Asia, South Korea leads with over 50 million registered users on its open banking platform and a MyData framework covering insurance, investments, and pensions. India's Account Aggregator framework, backed by the RBI, connects over 200 financial entities and integrates with UPI's 10 billion monthly transactions. Singapore's SGFinDex has expanded to include CPF, tax, and insurer data across 12+ financial apps.
Open Finance Maturity by Jurisdiction
The gap between leaders and laggards is substantial. While Brazil and the UK operate at scale, the EU's broader open finance regime may not become operational until 2029-2030, and the US remains in regulatory limbo.
| Jurisdiction | Framework | Scope | Status | Maturity |
|---|---|---|---|---|
| Brazil | Open Finance Brasil (BCB) | Banking, insurance, investments, pensions, FX | Live since 2022; 102B API calls in 2024 | Champion |
| UK | FCA Open Finance Roadmap + Pension Dashboards | Banking (live); mortgages, SME lending, pensions (planned) | Roadmap published April 2026; schemes by 2028-2030 | Champion |
| South Korea | KFTC Open Banking + MyData | Banking, insurance, investments, pensions | 50M+ registered users | Champion |
| India | Account Aggregator (RBI) | Banking, investments, insurance, tax | 200+ entities connected; expected mandatory by 2026 | Strong |
| Australia | Consumer Data Right (CDR) | Banking, energy; non-bank lending from July 2026 | Expanding to BNPL and non-bank lenders | Strong |
| EU | PSD3/PSR (payments) + FIDA (all financial data) | Payments (live via PSD2); savings, investments, insurance, pensions, crypto (planned) | FIDA trilogue paused; operational by 2029-2030 | In progress |
| US | CFPB Section 1033 | Transaction data, account terms | Rule enjoined; revised NPRM submitted August 2026 | Stalled |
Use Cases Driving Adoption
The expansion from open banking to open finance unlocks use cases that were impossible when only payment account data was accessible. These use cases explain why regulators, fintechs, and incumbents are investing heavily in the infrastructure needed to make cross-product data sharing work.
Cross-Platform Financial Planning
With open finance, wealth management platforms can consolidate data from bank accounts, brokerage firms, retirement plans, insurance policies, and mortgage lenders into a single view. This enables advisors and automated tools to deliver portfolio analysis, risk assessments, and investment recommendations that account for a consumer's full financial picture rather than just the assets held at one institution. Singapore's SGFinDex already demonstrates this by aggregating bank, CPF, tax, and insurance data into participating financial apps.
Competitive Lending and Credit Portability
Open finance enables lenders to access a more complete picture of a borrower's finances: not just checking account flows, but savings balances, investment portfolios, existing loan terms, and insurance coverage. This allows more accurate risk pricing and enables consumers to shop for better rates without manually gathering statements from multiple institutions. Brazil's credit portability pilot, launched in November 2025 with 26 financial institutions, lets consumers transfer existing loan agreements to competing lenders through standardized APIs. The UK's FCA has identified SME lending as one of its two priority open finance use cases, recognizing that small businesses are disproportionately harmed by information asymmetries in credit markets.
Pension Dashboards and Retirement Planning
Pension data is among the most fragmented in financial services. Workers accumulate pension entitlements across multiple employers and providers over decades, often losing track of smaller pots. The UK's pension dashboard program requires schemes to connect by 31 October 2026, with approximately 60 million private pension records already linked. Open finance principles make it possible not just to view these entitlements but eventually to compare providers, consolidate small pots, and switch to better-performing funds: all through authorized third-party applications.
Insurance Comparison and Switching
Under FIDA, non-life insurance data (excluding health and sickness policies) would become shareable with authorized third parties. This means consumers could authorize an app to pull their current motor insurance policy details, coverage limits, and claims history, then automatically compare those terms against competing offers. FIDA phases this in after banking data, recognizing that insurance data is less standardized and more heterogeneous.
The 63/28 split: Globally, Account Information Services (viewing data) still dominate open banking API traffic at 63%, while Payment Initiation Services (moving money) account for 28%. Open finance will likely follow the same pattern: data aggregation use cases will lead, with action-oriented capabilities (switching, porting, initiating) following as trust and infrastructure mature.
Infrastructure Challenges
Extending data portability beyond payment accounts introduces technical and governance challenges that open banking only partially solved. The infrastructure required for open finance must handle more diverse data types, more complex consent relationships, and higher volumes than current open banking systems were designed for.
Consent Management at Scale
Open banking consent is relatively simple: a consumer authorizes a third party to view their current account. Open finance consent is multi-dimensional: a consumer might authorize different levels of access to different products, with different durations, for different purposes. FIDA addresses this through Financial Data Sharing Schemes (FDSS), industry-governed frameworks that define consent standards, but the complexity of implementing fine-grained, revocable, auditable consent across dozens of product categories remains substantial.
The technical foundation for securing these APIs uses Financial-grade API (FAPI) security profiles built on OAuth 2.0 and OpenID Connect. These eliminate credential sharing (a major weakness of screen scraping) and give consumers granular visibility into active permissions. The Financial Data Exchange (FDX) published User Experience Guidelines 2.0 covering consumer consent dashboard design, but adoption remains uneven.
Data Standardization
Unlike payment account data (which is relatively uniform: date, amount, counterparty), financial product data is inherently heterogeneous. An insurance policy has fundamentally different attributes than a pension entitlement or an investment portfolio. No single standard covers all these categories today.
In North America, the FDX API has become the dominant standard, with over 130 million consumer accounts connected as of early 2026 (doubled from 65 million in December 2023). In Europe, the Berlin Group's NextGenPSD2 framework is used by nearly three out of four European banks. Its extended Account Information Service specifications already cover many of the data scopes FIDA would mandate. FIDA itself proposes phased implementation: highly standardized, already-digital data (savings, loans) first, followed by partially digitized products (motor insurance), and finally heterogeneous, under-digitized data (occupational pensions).
API Performance and Reliability
Open finance APIs must operate at financial-grade reliability. The UK's open banking ecosystem currently processes approximately 860 API calls per second with a 99.46% success rate. The EU's PSR mandates "performance parity": open banking interfaces must match the performance of a bank's own customer-facing channels. Scaling these standards to cover the volume of data categories envisioned by FIDA and similar frameworks requires significant investment from data holders, many of whom (insurers, pension funds) have less mature API infrastructure than banks.
Where Blockchain Meets Open Finance
The intersection of open finance and blockchain technology reveals a deeper question about financial data portability: who should control the infrastructure? Traditional open finance relies on regulated intermediaries granting API access to consumer data held in institutional databases. Blockchain-based approaches offer an alternative where financial history is inherently portable because it lives on a public ledger.
On-Chain Transaction History as a Credit Signal
DeFi lending protocols have historically required overcollateralization because they lacked borrower credit history. This is changing. On-chain credit scoring systems analyze wallet transaction histories, protocol interactions, repayment behavior, and governance participation to generate transparent, auditable creditworthiness measures. Protocols like Spectral Finance, RociFi, and Providence tie credit scores to wallet addresses rather than personal identities, enabling credit assessment without KYC.
This approach has limitations: on-chain history captures only blockchain-native activity, missing the vast majority of a person's financial life. But it demonstrates a principle that open finance regulators are converging toward: financial behavior data should be portable, verifiable, and controlled by the individual rather than locked inside institutional silos.
Self-Sovereign Financial Identity
The W3C Verifiable Credentials Data Model v2.0 (published as a W3C Recommendation in May 2025) provides a standard for issuing, holding, and verifying digital credentials without centralized intermediaries. Self-sovereign identity (SSI) enables selective disclosure: a borrower could prove their credit score meets a threshold without revealing the underlying score, or demonstrate a repayment history without exposing specific transactions.
Applied to open finance, SSI could complement API-based data sharing by giving consumers portable, privacy-preserving credentials that work across jurisdictions and institutional boundaries. A borrower could present a "reputation credential" to any lender globally, without each lender needing a direct API connection to every data holder where the borrower has accounts. This is particularly relevant for digital identity and payment convergence in cross-border contexts.
Self-Custodial Data Portability
Traditional open finance architectures are institution-centric: the bank holds the data, the regulator mandates access, and the consumer authorizes sharing through the bank's infrastructure. The consumer never truly "owns" the data in a technical sense. Self-custodial financial infrastructure inverts this model. When users hold their own keys and manage their own transaction history, data portability becomes a property of the architecture rather than a regulatory mandate.
On-chain financial activity is inherently portable: a wallet's transaction history can be verified by any party with access to the blockchain, without requiring institutional intermediaries to grant API access. This makes self-custodial protocols a natural complement to open finance principles, even though they operate outside the traditional regulatory perimeter.
The Market Trajectory
The numbers paint a clear picture of where open finance is heading. The global open banking market reached $35.72 billion in 2025 and is projected to hit $240.31 billion by 2035, growing at a 24.8% CAGR according to Precedence Research. Global active users reached 470 million in 2025, projected to hit 600 million by 2027. Over 3,200 licensed third-party providers operate globally, and 85% of fintech apps launched in the past year integrated at least one open banking API.
AI is accelerating adoption. Juniper Research projects that AI will become increasingly integrated with open banking and open finance, deployed for personalized financial management, automated credit assessment, and customizable lending products. This aligns with the broader trend toward AI-driven financial services where embedded finance APIs become the substrate for autonomous financial agents.
From Data Portability to Financial Sovereignty
Open finance represents a fundamental shift in who controls financial data. But the current regulatory approach still depends on institutional gatekeepers: banks, insurers, and pension funds must build and maintain the APIs that make data sharing possible. The consumer's right to data portability is only as strong as the data holder's compliance and infrastructure quality.
Self-custodial financial infrastructure offers an alternative path. When users hold their own assets and control their own transaction records, portability is a property of the system rather than a regulatory overlay. Protocols like Spark demonstrate this principle: users maintain self-custody of their Bitcoin and stablecoin balances, and their transaction history is verifiable without relying on any single institution to grant data access. The Spark SDK enables developers to build applications where financial data portability is architectural rather than mandated.
Whether open finance ultimately succeeds through regulated API mandates, self-sovereign identity credentials, blockchain-native transparency, or some combination of all three, the direction is clear: financial data is moving from institutional silos to user control. For developers building the next generation of embedded financial services, understanding this landscape is essential for designing systems that meet consumers where open finance is taking them.
This article is for educational purposes only. It does not constitute financial or investment advice. Bitcoin and Layer 2 protocols involve technical and financial risk. Always do your own research and understand the tradeoffs before using any protocol.

