Open Banking Framework: Providers, Security, and Section 1033

The open banking framework is the combination of laws, regulations, and technical standards that lets you authorize third-party apps and services to access your bank account data through secure digital connections, instead of handing over your username and password. In the United States, it rests on Section 1033 of the Dodd-Frank Act, with a Consumer Financial Protection Bureau rule finalized in October 2024 that is currently stayed and under reconsideration. In the European Union, banks have been required to share account data with authorized third parties since the Payment Services Directive (PSD2) took effect in January 2018. The underlying principle is simple: your financial data belongs to you, and regulated intermediaries can touch it only when you say so.

How the APIs Work

At the center of open banking are application programming interfaces, or APIs. These are standardized digital doorways that let different software systems exchange information in a predictable format. When you link a budgeting app to your checking account, the app doesn’t log in as you and read the screen. It sends a structured request through the API asking for a specific piece of data, such as your balance or your last 30 transactions, and the bank’s system responds with exactly that. Faster, more reliable, and far more secure than credential sharing.

A critical piece of the plumbing is ISO 20022, a global messaging standard that functions as a common dictionary for financial data. A payment amount in one system means the same thing in another, down to the metadata describing the transaction. The Bank for International Settlements has described the standard as easing interoperability between financial institutions, market infrastructures, and end users by standardizing data objects, rules, and processes.1Bank for International Settlements. The Future of Financial Messaging: Navigating the ISO 20022 Migration Journey Without that shared vocabulary, an app pulling transactions from five banks would be translating five different formats and losing information along the way.

Because every covered bank exposes data through the same technical playbook, developers can build products that work across institutions without custom integrations for each one. A small fintech connects to the same endpoints as a large financial platform. That is why you can combine a checking account at one bank with a savings tool from another and a payment app from a third, all drawing on the same underlying data.

What Data Is Covered

Under the CFPB’s finalized rule, the categories banks must make available include transaction history, account balances, terms and conditions, upcoming bill information, payment initiation details for checking and savings accounts, and basic account verification information.2Consumer Financial Protection Bureau. Required Rulemaking on Personal Financial Data Rights The statute itself, 12 U.S.C. § 5533, frames the right broadly: a covered financial institution must make available information “relating to any transaction, series of transactions, or to the account including costs, charges and usage data” in a usable electronic form.3Office of the Law Revision Counsel. 12 USC 5533 – Consumer Rights to Access Information

Account types covered in the initial rule include checking accounts, savings accounts, credit cards, prepaid cards, and digital wallets. Not everything in your financial life is in scope. The statute carves out confidential commercial information such as the algorithms behind credit scores, data collected for fraud prevention or anti-money-laundering purposes, and information the institution cannot retrieve in its ordinary course of business.3Office of the Law Revision Counsel. 12 USC 5533 – Consumer Rights to Access Information

The Three Types of Regulated Providers

Open banking creates distinct roles with different permissions. Knowing which one you’re dealing with tells you what a provider can see and do.

Account Servicing Payment Service Providers (ASPSPs)

ASPSPs are the banks and credit unions that hold your money. They maintain your accounts, serve as the source of truth for balances and transactions, and provide the technical gateways through which authorized third parties connect. PSD2 defines an ASPSP as a provider that provides and maintains a payment account for the user.4EUR-Lex. Directive (EU) 2015/2366 – Payment Services Directive In jurisdictions with open banking mandates, participation is not optional.

Account Information Service Providers (AISPs)

AISPs can view your data across one or more accounts but cannot move money. A budgeting app that pulls deposits and spending from three different banks into a single dashboard is the typical example. PSD2 defines this as an online service providing consolidated information on one or more payment accounts held with other providers.4EUR-Lex. Directive (EU) 2015/2366 – Payment Services Directive Access is strictly read-only.

Payment Initiation Service Providers (PISPs)

PISPs can trigger payments directly from your bank account. That enables bank-to-bank transfers that bypass card networks entirely. The directive defines the role as a service to initiate a payment order at the request of the user for a payment account held at another provider.4EUR-Lex. Directive (EU) 2015/2366 – Payment Services Directive A PISP verifies fund availability and sends a secure instruction to your bank to complete the transfer. It does not hold your money or see your wider financial picture unless it also operates as an AISP. The “pay by bank” option appearing at more online checkouts is a PISP transaction: the payment settles as a direct bank transfer rather than a card charge.

Security and Consent

Strong Customer Authentication (SCA) is the security backbone. Before any data share or transaction, you verify your identity using at least two independent factors drawn from three categories: something you know (a PIN), something you have (your phone), and something you are (a fingerprint or face scan). The European Banking Authority’s technical standards define SCA as authentication based on two or more independent elements, so that a breach of one does not compromise the others.5Open Banking. Strong Customer Authentication A stolen password alone is not enough to authorize a data share.

What keeps your bank credentials private is OAuth 2.0. When you connect an app, it redirects you to your bank’s own login page. You authenticate directly with the bank, and the bank issues a time-limited digital token back to the app. That token grants access to specific data for a specific period. Your actual credentials never leave the bank’s systems, so a compromised third-party app cannot leak them.

Consent is designed to be granular and time-limited. You pick exactly which data a third party can access, and the permission expires. Under the CFPB’s finalized rule, third-party authorization expires after a maximum of one year; if you don’t actively reauthorize, the third party must stop collecting your data and may retain previously collected data only if doing so remains reasonably necessary for the service you originally requested.6Consumer Financial Protection Bureau. Required Rulemaking on Personal Financial Data Rights In the UK, the Financial Conduct Authority applies a tighter cycle, requiring reauthentication or consent reconfirmation at least every 90 days.7Financial Conduct Authority. Strong Customer Authentication

You can revoke access at any time, and third parties are required to maintain systems that process revocation. Once you revoke, the third party must stop collecting data and may no longer use or retain previously collected data unless retention remains reasonably necessary to provide your requested service.6Consumer Financial Protection Bureau. Required Rulemaking on Personal Financial Data Rights

The CFPB rule also places hard limits on what a third party can do with your data. It prohibits using the data for targeted advertising, cross-selling other products, or selling the data to anyone else. Third parties may collect and process your personal financial information only when doing so is reasonably necessary to provide the service you actually asked for.6Consumer Financial Protection Bureau. Required Rulemaking on Personal Financial Data Rights That is a sharp break from the older screen-scraping model, where a third party with your credentials could in theory reach anything and use it however it pleased.

Section 1033 and the Current U.S. Status

Section 1033 of the Dodd-Frank Act is the statutory basis for open banking in the United States. It requires covered financial institutions to make account information available to consumers in usable electronic form upon request.3Office of the Law Revision Counsel. 12 USC 5533 – Consumer Rights to Access Information The CFPB is responsible for the detailed implementing rules.8Consumer Financial Protection Bureau. Dodd-Frank Act Section 1033 – Consumer Access to Financial Records

In October 2024, the CFPB finalized its Personal Financial Data Rights rule, specifying what data must be shared, through what technical standards, with what privacy protections, and on what timeline.9Consumer Financial Protection Bureau. CFPB Finalizes Personal Financial Data Rights Rule to Boost Competition, Protect Privacy, and Give Families More Choice in Financial Services The rule effectively phases out screen scraping by imposing authorization and authentication requirements that credential sharing cannot satisfy. The CFPB warned that once secure APIs are available, third parties continuing to screen-scrape could face enforcement under prohibitions on unfair and deceptive practices.6Consumer Financial Protection Bureau. Required Rulemaking on Personal Financial Data Rights

Implementation is on hold. Banking industry groups, including the Bank Policy Institute and the Kentucky Bankers Association, challenged the rule in the U.S. District Court for the Eastern District of Kentucky. On July 29, 2025, the court stayed the litigation while the CFPB began a new rulemaking process, and it later stayed the rule’s compliance deadlines as well. No financial institution is currently required to comply with the original timeline. On August 22, 2025, the CFPB published an Advance Notice of Proposed Rulemaking seeking public comment on four areas it is reconsidering: who qualifies as a consumer’s “representative” for data requests, whether financial institutions can charge fees to cover compliance costs, data security implications, and data privacy risks.10Consumer Financial Protection Bureau. Required Rulemaking on Personal Financial Data Rights

The original rule used a staggered rollout based on institution size, with the largest banks facing the earliest deadline and the smallest covered institutions getting several more years to build API infrastructure. Depository institutions with $850 million or less in assets are exempt entirely. The original compliance dates ran from April 1, 2026 through April 1, 2030.11Consumer Financial Protection Bureau. 12 CFR 1033.121 – Compliance Dates Given the current stay, those dates will almost certainly shift.

When the rule is in force, violations carry civil penalties under the Consumer Financial Protection Act: up to $5,000 per day for any violation, up to $25,000 per day for reckless violations, and up to $1,000,000 per day for knowing violations, subject to annual inflation adjustments.12Office of the Law Revision Counsel. 12 USC 5565 – Relief Available

The EU and UK Framework

The European Union moved first. Directive 2015/2366, known as PSD2, took effect in January 2018 and requires banks to provide third-party providers with access to payment accounts on a non-discriminatory basis. It is the source of the ASPSP, AISP, and PISP structure most open banking discussions reference.4EUR-Lex. Directive (EU) 2015/2366 – Payment Services Directive The United Kingdom adopted these rules under its own Open Banking Standard, which went further by mandating identical technical specifications across all participating institutions.

PSD2 is being superseded. In November 2025, the European Parliament and Council reached a provisional political agreement on a new Payment Services Regulation (PSR) and an updated directive (PSD3).13European Parliament. Payment Services Regulation – Legislative Train Schedule Moving from a directive, which member states transpose through national law, to a regulation, which applies directly, is meant to eliminate the inconsistencies that arose when different countries implemented PSD2 differently. Formal adoption is still required before the new rules take effect.

Security requirements under the current EU and UK framework include SCA and the 90-day consent reconfirmation cycle. The FCA has exempted consumers from needing to reauthenticate for account information access where the ASPSP adopts the Article 10A exemption, though third-party providers must still obtain explicit consent at least every 90 days.7Financial Conduct Authority. Strong Customer Authentication

If Something Goes Wrong

If an unauthorized transaction hits your account through a third-party connection, federal law caps your liability based on how quickly you report it. Under 15 U.S.C. § 1693g, your maximum exposure is $50 if you notify your bank before any unauthorized transfers occur or promptly after discovering the problem. Wait more than two business days after learning of a lost or compromised access device and your liability can rise to $500 for unauthorized transfers during the delay. Let more than 60 days pass after your bank sends a statement reflecting the activity, and you could be on the hook for the full amount of subsequent losses the bank can show would have been prevented by earlier reporting.14Office of the Law Revision Counsel. 15 USC 1693g – Consumer Liability

Your bank must investigate any error you report within 60 days of the statement date. You have to identify yourself, explain why you believe an error occurred, and give the type, date, and amount of the transaction to the extent you can. The bank cannot delay starting its investigation while waiting for written confirmation.15Consumer Financial Protection Bureau. 12 CFR 1005.11 – Procedures for Resolving Errors If the investigation takes longer than 10 business days, the bank must provide provisional credit while it continues looking into the issue. Check your statements. The protections are generous, but only if you catch the problem and report it.

Where Things Stand Now

The technical infrastructure of open banking largely exists. Major banks have built APIs, thousands of third-party apps connect to them, and millions of consumers use open-banking-powered products daily for budgeting, lending, and payments. But the U.S. regulatory framework meant to formalize all of this is paused mid-implementation, the EU is transitioning from PSD2 to its successor, and fundamental questions about fees, data security obligations, and who counts as an authorized representative remain open in the American rulemaking.

For now, the practical steps on the consumer side are to review which apps have access to your financial data, revoke connections you no longer use, and report any unauthorized activity immediately to preserve your federal liability protections. Institutions and fintechs building on the existing APIs can keep working to current technical standards, but the final U.S. compliance requirements may look meaningfully different from the October 2024 rule once the CFPB’s reconsideration concludes.