Introduction / State of Play
Open banking — the regulatory and technical framework that enables third-party access to bank account data and payment initiation with consumer consent — has been transforming financial services infrastructure for nearly a decade in Europe and is finally accelerating in the United States. In 2026, the combination of regulatory momentum (CFPB Rule 1033 in the US, PSD3 progress in the EU), maturing API infrastructure, and proven fintech use cases has made open banking a practical reality for finance teams and technology builders.
The core promise of open banking is eliminating information silos: rather than financial data living locked in bank portals accessible only through manual export or screen scraping, open banking APIs expose account balances, transaction history, and payment capabilities to authorized applications in real time. This data access is the foundation for a wave of financial software innovation — from automated cash management to AI-powered lending to frictionless accounting integrations.
For finance teams, open banking means tools that know exactly what is happening in their bank accounts at all times, without manual intervention. For fintechs and software developers, open banking creates a data and payment infrastructure layer that enables products that were previously impossible or impractical to build.
The Current Landscape
The open banking landscape in 2026 is bifurcated between a more mature European framework and an accelerating — but still evolving — US market.
In Europe, PSD2 (the Second Payment Services Directive) has been operational since 2019, requiring banks to provide standardized API access to licensed third parties. The market has matured significantly, with aggregators like Tink (acquired by Visa) and TrueLayer providing broad coverage across European banking relationships. PSD3, which began phased implementation in 2025, is tightening API standards, improving reliability requirements, and expanding payment initiation capabilities.
In the United States, the CFPB finalized Rule 1033 in late 2024, establishing a right for consumers and small businesses to access their financial data in machine-readable format and share it with authorized third parties. Banks are required to provide API access on a phased implementation timeline based on asset size, with the largest banks required to comply first.
US open banking infrastructure providers — Plaid, MX, Finicity (acquired by Mastercard), and Akoya — provide aggregation services that connect fintech applications to bank data. Plaid alone connects to over 12,000 financial institutions and facilitates data access for thousands of fintech applications used by over 100 million consumers and businesses.
Key Trend #1: Account Data Access and Aggregation
From Screen Scraping to Proper APIs
The foundational open banking use case is simple but powerful: giving financial applications real-time, authorized read access to bank account data. The history of this capability has been messy — before open banking, fintech companies that needed bank data used screen scraping: programmatically logging into bank portals as if they were the user and extracting data by parsing HTML. This approach was fragile, insecure, and deeply disliked by banks.
Proper API-based open banking access is a fundamental improvement:
- Security: Users grant specific data access permissions without sharing login credentials. Access can be revoked at any time from the bank's portal.
- Reliability: API connections are more stable than screen scraping, which breaks whenever bank portals change their interface.
- Data quality: Structured API responses provide cleaner, more consistent data than scraped HTML parsing.
- Regulatory clarity: Authorized data sharing under open banking frameworks provides legal clarity for both users and the fintech applications accessing data.
For accounting software, bank API connectivity enables automated transaction feeds that update in near-real-time rather than waiting for daily export files or manual imports. QuickBooks Online, Xero, and Sage all now connect directly to bank APIs where available, dramatically reducing the manual reconciliation effort that has historically consumed significant bookkeeper and business owner time.
For financial management applications, real-time account data enables genuinely current dashboards — cash balances, daily spending summaries, and AP/AR status — that reflect the actual state of the business's finances rather than the state as of the last manual update.
Key Trend #2: Automated Cash Management via APIs
Banks as Plumbing, Software as the Interface
Modern cash management platforms are using open banking APIs to create a software-defined treasury layer above traditional bank infrastructure. Rather than logging into a bank portal to view balances and initiate transfers, finance teams can manage cash positions, sweep between accounts, and initiate payments through their financial management software — with the bank providing the underlying regulated rails.
Mercury, Brex, and Ramp are the clearest examples of this approach in the mid-market. These platforms provide a software interface for cash management that connects to banking infrastructure through a combination of their own bank partnerships, BaaS providers, and open banking APIs. The user experience is defined by the software company; the regulatory and settlement infrastructure is provided by the banking layer underneath.
Payment initiation — not just data read access but the ability to initiate bank transfers through APIs — is the more powerful and more regulated component of open banking. In Europe, PSD2-licensed Payment Initiation Service Providers (PISPs) can initiate bank transfers directly from user accounts. In the US, payment initiation through open banking is still largely mediated through ACH and RTP networks rather than direct API-initiated transfers, but the trajectory is toward more direct payment initiation capability as Rule 1033 implementation matures.
For AP automation platforms, API-based payment initiation means closing the loop from invoice approval to payment execution without the user ever leaving the AP system to initiate transfers manually in a bank portal. Platforms like Ramp AP, Bill.com, and Tipalti are integrating payment initiation capabilities that execute approved payments automatically through connected banking relationships.
Key Trend #3: Embedded Lending Powered by Open Banking Data
Real-Time Cash Flow as Credit Score
Traditional small business lending relies on a credit assessment process that is slow, backward-looking, and poorly calibrated to the actual creditworthiness of many small businesses. Credit bureaus, tax returns, and bank statements — the traditional inputs — provide a historical view that often misses the current financial reality of a dynamic small business.
Open banking data enables a fundamentally different approach: cash flow underwriting based on real-time transaction data. A lender with API access to a business's bank accounts can see:
- Current cash balance and recent trend
- Revenue consistency and growth rate
- Major customer concentration risk
- Fixed payment obligations (loan payments, rent, payroll patterns)
- Seasonal patterns and their magnitude
- Days of runway at current spending rate
This real-time cash flow picture provides a more current and often more accurate assessment of a business's ability to repay a loan than traditional credit metrics. Fintech lenders including Kapitus, Fundbox, and numerous embedded lending platforms are using open banking data to underwrite faster, approve more businesses that traditional lenders would decline (but that have strong cash flow), and price loans more accurately.
The CFPB's Rule 1033 implementation is expected to further accelerate cash-flow-based lending by standardizing and expanding business bank data access, making it easier for lenders to conduct consented real-time cash flow underwriting.
Key Trend #4: Open Accounting
Bank Feeds That Actually Work
The accounting-specific manifestation of open banking is the elimination of CSV import workflows and the replacement of fragile screen scraping with direct bank API connections to accounting software. The vision — called "open accounting" by some in the industry — is a world where every transaction in a bank account appears automatically in the accounting system within hours, correctly categorized, with supporting data attached, without any manual intervention.
This vision is largely achievable in 2026 for businesses using modern cloud accounting platforms (QuickBooks Online, Xero, Sage Accounting) in markets with mature open banking API infrastructure. The remaining friction points are:
- Not all financial institutions have robust, reliable open banking APIs
- Connection reliability varies, requiring monitoring and occasional reconnection
- Categorization accuracy, while high, still benefits from human exception review
- Complex transactions (transfers between accounts, split categorization) still require configuration
QuickBooks, Xero, and Sage are all investing heavily in expanding direct API bank connections and improving the reliability of transaction feeds, knowing that seamless bank connectivity is a core product differentiator.
Regulatory Landscape and What It Means
The CFPB's Rule 1033 is the transformative US regulatory development. It establishes that consumers and small businesses have a right to their financial data in machine-readable format and can direct banks to share it with authorized third parties. Banks cannot charge fees for this data sharing, cannot limit access to data as a competitive tactic, and must meet API reliability standards.
Implementation is phased: the largest banks (over $500B in assets) must comply first, with smaller institutions following on a rolling schedule through 2027-2028. The practical effect is that US open banking infrastructure will reach effective universality within the three-year window.
Challenges and Risks
Data standardization remains a significant challenge in the US open banking ecosystem. Unlike Europe, where PSD2 drove toward consistent data formats, US bank APIs vary significantly in their data schemas, coverage depth, and transaction categorization — requiring aggregators like Plaid and MX to do substantial normalization work.
API reliability and uptime varies substantially across banking institutions. Finance teams that depend on API-connected data flows need monitoring tools and fallback processes for when connections fail.
Security of credential-free connections must be maintained through regular permission audits, ensuring that only currently-needed applications retain data access.
What to Watch in the Next 12–18 Months
The CFPB Rule 1033 compliance timeline will drive the most significant US open banking changes — watch for large bank API launches and the fintech ecosystem response. In Europe, PSD3's stronger API reliability and payment initiation standards will mature the European market further.
The combination of open banking data access and AI analysis will generate a new category of financial intelligence products for businesses — systems that continuously analyze bank transaction patterns, identify anomalies, and generate actionable financial recommendations without requiring any manual reporting workflows.
Conclusion
Open banking in 2026 represents genuine infrastructure progress for finance teams and fintech developers alike. The combination of regulatory momentum, maturing API standards, and proven use cases in account aggregation, cash management, lending, and accounting integration makes open banking one of the most consequential financial infrastructure developments of the decade. Finance leaders who understand and leverage open banking capabilities will unlock automation, intelligence, and efficiency gains that remain invisible to those still managing finances through manual bank portal processes.