Section 1033 Reconsideration: Data Access Fees and Authorized Representatives
The CFPB open banking rule is paused, not gone. Here is what the Section 1033 reconsideration means for fintech builders, and how to make your open banking APIs ready for whatever rule emerges.
Status reflects public records as of November 17, 2026. Check the latest before relying on it.
A bank's API team may have spent months preparing for open banking compliance. Then, on October 29, 2025, a federal court in Kentucky enjoined the Consumer Financial Protection Bureau (CFPB) from enforcing its Personal Financial Data Rights Rule while the agency reconsiders it.
That order did not repeal Section 1033 of the Dodd-Frank Act. It changed the enforcement position around the 2024 CFPB open banking rule. For fintech leaders, the distinction matters. Consumer-permissioned data access remains a statutory and commercial issue, but the details of the original rule are back on the table.
As of November 17, 2026, the CFPB's proposed rule, Personal Financial Data Rights Reconsideration (RIN 3170-AB39), is still listed as pending review at the Office of Information and Regulatory Affairs (OIRA). The proposed text is not public. Builders can still improve their architecture now without treating the 2024 rule as settled law. For teams planning around the open banking rule 2026, the smart move is to build flexibility into infrastructure while the regulatory position develops.
What Is Section 1033 of the Dodd-Frank Act?
Dodd-Frank Section 1033 gives consumers the right to access information about their financial accounts in electronic form, subject to rules issued by the CFPB. The statute defines a "consumer" as an individual or an agent, trustee or representative acting on that individual's behalf. This single definition is why so much of today's debate centers on who counts as a representative.
In its 2025 reconsideration notice, the CFPB estimated that more than 100 million consumers had used consumer-authorized data access through third parties as of 2024. That scale explains why the outcome matters to banks, data aggregators and fintech apps alike.
The CFPB Section 1033 Rule and Why the Injunction Matters
The CFPB Section 1033 rule, formally the Personal Financial Data Rights Rule, was finalized in late 2024. It required covered data providers to make consumer financial data available electronically to consumers and authorized third parties, with compliance dates phased from April 2026 through 2030 based on institution size.
Dodd-Frank Act becomes law, including the Section 1033 data access right.
CFPB finalizes the Personal Financial Data Rights Rule.
CFPB recognizes the Financial Data Exchange (FDX) as a standard-setting body.
CFPB publishes an ANPR to reconsider the rule.
Court in Forcht Bank, N.A. v. CFPB stays compliance dates and enjoins enforcement.
The first original compliance date passes without becoming an enforcement trigger.
Proposed reconsideration rule (RIN 3170-AB39) is sent to OIRA for review.
Proposed rule published in the Federal Register, followed by public comment.
The injunction paused enforcement, not the underlying question
In Forcht Bank, N.A. v. CFPB, the Eastern District of Kentucky stayed the rule's compliance dates and enjoined CFPB enforcement until the Bureau completes its reconsideration. This CFPB 1033 injunction did not erase the consumer financial data rights created by statute. It means the original Section 1033 compliance date schedule is not currently a binding enforcement trigger.
Is the CFPB open banking rule still in effect?
Not in an enforceable sense. The 2024 rule is on the books, but its compliance dates are stayed and the CFPB cannot enforce it while reconsideration continues. The statutory right in Section 1033 still exists.
What the Section 1033 Reconsideration Covers
The CFPB's August 2025 Advance Notice of Proposed Rulemaking (ANPR) opened the Section 1033 reconsideration around four issues:
Who qualifies as a representative that can request data on a consumer's behalf.
How data access costs are allocated, including whether providers may charge fees.
Information security risks of implementing the rule.
Consumer privacy risks created by third-party data access.
OIRA review is a procedural stage, not a published replacement rule. You can track the rulemaking on the Reginfo.gov entry for RIN 3170-AB39. Until the CFPB releases proposed text and completes the process, product teams should avoid coding assumptions about final fees, eligible representatives or new compliance dates into fixed business logic.
Not sure how exposed your data flows are?
Get a review of your consent records, API connections and audit readiness before the new rule lands.
Three Issues That Could Reshape the Open Banking API Contract
1. Section 1033 data access fees: who pays for the pipes?
The 2024 rule prohibited data providers from charging consumers or authorized third parties for establishing and maintaining required interfaces or for responding to covered data requests. The ANPR asks whether that approach is the best reading of Section 1033 and how fixed and marginal costs should be allocated. Industry reporting in 2026 suggested the Bureau was weighing models that could allow some charges, but no proposal text has been published.
The debate over Section 1033 data access fees is a material architecture question, not only a legal one. Interface providers carry authentication, uptime, monitoring, fraud control, support and delivery costs. A changed fee framework could reshape provider contracts and API operating models.
Free required access
Providers could not charge consumers or authorized third parties for required interfaces or covered data requests.
Cost allocation reopened
The CFPB is asking how fixed and marginal costs should be shared. No fee model is approved today.
What builders should do: Keep a usage ledger that records requests by client, endpoint, data category, response size, latency and outcome. Separate ordinary consumer-authorized access from retries, polling and abusive traffic. This evidence supports capacity planning today and fee analysis later.
Do not assume fees are permitted now, or that a future rule will authorize any particular charging model. The question is unresolved.
2. Authorized third parties under Section 1033: who can act for the consumer?
The ANPR asks whether "representative" should be limited to parties with fiduciary duties or extend to fintech apps and aggregators. The 2024 rule took the broader view, using authorization procedures and substantive obligations for authorized third parties that access data on a consumer's behalf. The scope of authorized representatives is therefore one of the most important open questions for product and compliance teams.
2024 rule approach
Option under review
For builders, this uncertainty makes consent and authority records core infrastructure.
A checkbox is not a consent system. Record the consumer, the receiving application, the purpose, the accounts covered, the data categories, the permissions granted, the time of authorization and the expiry or revocation state. Preserve authentication evidence and bind each grant to its recipient.
Where a fintech acts through another service provider, model the delegation chain explicitly.
Your platform should be able to answer:
requested access?
and for which service?
and when does that authority end?
3. Open banking data security and privacy: make consent enforceable
The CFPB is also reconsidering security and privacy risks. Valid permission can still lead to excessive collection, indefinite retention or unintended disclosure.
Build purpose limitation into the data path. A budgeting service may need transaction history, but it may not need every account attribute. Strong open banking data security means putting these controls in place:
These controls belong in your wider fintech compliance architecture from day one, not as a retrofit.
How Does Section 1033 Affect Fintech Companies Right Now?
The rule is paused, but the market is not. Banks and aggregators continue to sign commercial data access agreements, and the shift from screen scraping to APIs keeps moving. For fintechs, that means three practical realities:
Access economics are a planning variable
Fees, rate limits and contract terms may change, so they should live in configuration, not code.
Consent quality is a competitive asset
Partners and banks increasingly ask how you prove authorization.
Standards reduce rework
Aligning with a common API standard now lowers the cost of adapting to whatever rule emerges.
If you are still choosing between direct bank connections and an aggregator, our open banking API integration guide walks through the models, costs and trade-offs.
FDX API Integration: A Practical Standard While the Rule Is Rewritten
The Financial Data Exchange (FDX) API is a useful reference. In January 2025, the CFPB recognized FDX as a standard-setting body under the 2024 rule. Its user-permissioned model emphasizes control, access, transparency, traceability and security, using REST, OAuth 2.0 and financial-grade API (FAPI) security profiles.
Screen scraping
FDX-aligned API
FDX API integration gives institutions and third-party apps a consistent foundation for permissioned access. It is not a guarantee of legal compliance, and it does not mean every institution must adopt one specific implementation. It does reduce bespoke integration work, which is often where API integration debt begins.
Section 1033 Readiness Checklist: Five Steps for Fintech Teams
Use the reconsideration window to move in five steps:
Teams that already run continuous compliance monitoring can feed these consent and access events straight into their audit evidence.
Reference Open Banking API Architecture for Permissioned Access
A Section 1033-ready open banking API architecture follows one clear path from consent to data use:
Read left to right, row by row. No data moves without passing the consent gate.
This flow needs a clear failure path:
Must stop new access immediately.
Must fail closed, never silently grant broader access.
Stays subject to retention, deletion and purpose controls.
How Seaflux Helps Fintechs Build Section 1033-Ready Open Banking APIs
The rule will change. Your need for secure, traceable, consumer-permissioned data access will not. Seaflux is a fintech software development partner that helps banks, lenders and fintech platforms build open banking infrastructure that can adapt to the final CFPB Section 1033 rule without a rebuild.
Our engineers work alongside your product, compliance and security teams to turn regulatory uncertainty into clear architecture decisions:
Open banking API development services
We design and build FDX-aligned APIs, API gateways and developer-facing interfaces with OAuth 2.0 and financial-grade security profiles.
Consent management system development
We build consent services that capture purpose, scope, expiry and revocation, with versioned records your compliance team can query during audits and disputes.
Financial data API integration
Through our custom software development services, we replace brittle screen scraping with standardized bank, aggregator and third-party API integrations.
Traceable data pipelines
Our data engineering services add correlation IDs, API audit logging and usage metering across the full data journey, so cost and consent evidence is ready when fee rules arrive.
Secure cloud infrastructure
Through our cloud and DevOps services, we deploy compliance-ready infrastructure on AWS with encryption, access controls and monitoring built in.
Fintech compliance software
We connect consent, KYC, AML and audit workflows so your teams spend less time assembling evidence and more time on product decisions.
From embedded finance infrastructure to production fintech platforms, Seaflux builds financial software that is ready for regulators, partners and scale. Our expense management system for a US fintech startup cut reimbursement turnaround by 60%.
Build for the Section 1033 Rule That Emerges
Open banking regulation in the USA is delayed, but the demand for secure, consumer-directed data portability has not gone away. Section 1033 remains law, the CFPB is reconsidering its implementation, and the pending OIRA review signals that the next regulatory step is in progress.
Fintech teams should use this period to remove brittle connections, standardize API contracts, strengthen consent logging and measure the cost of serving data. These investments improve security and open banking compliance whether deadlines or cost allocation change.
If your data-sharing flow were audited tomorrow, could you show exactly which consumer authorized each connection, what data was accessed, which service used it and whether permission had since been revoked?
If the answer is not a confident yes, book a free consultation with Seaflux. We will map one consumer data journey end to end with you and identify the consent or audit gap worth fixing first.
Frequently Asked Questions (FAQ): Get the Answers You Need
What is Section 1033 of the Dodd-Frank Act?
Section 1033 gives consumers the right to access their financial account data in electronic form and to share it with authorized representatives, subject to rules issued by the CFPB. It is the legal foundation for open banking in the United States.
Is the CFPB open banking rule still in effect?
The 2024 Personal Financial Data Rights Rule has not been repealed, but a federal court stayed its compliance dates and enjoined CFPB enforcement on October 29, 2025, until the Bureau completes its reconsideration. The statutory right under Section 1033 still exists.
What happened to the CFPB open banking rule?
Bank groups led by Forcht Bank, the Kentucky Bankers Association and the Bank Policy Institute challenged the rule in court. The CFPB opened a reconsideration through an August 2025 ANPR, and its proposed replacement, RIN 3170-AB39, was listed as pending OIRA review as of November 2026.
Can banks charge fees for open banking data under Section 1033?
The 2024 rule prohibited fees for required data access, but the CFPB is reconsidering that position. No final rule allows or bans fees today, so fintechs should track request-level costs and keep pricing rules configurable rather than assume any outcome.
Who qualifies as an authorized third party under Section 1033?
Under the 2024 rule, a third party could access data on a consumer's behalf after following authorization procedures and accepting obligations on data use. The CFPB is now considering whether the term "representative" should be narrower, for example limited to parties with fiduciary duties.
How should fintech companies prepare for the Section 1033 reconsideration?
Inventory every data connection, separate consent from connectivity, keep versioned consent records, add end-to-end traceability and avoid hard-coding fee assumptions. Aligning APIs with the FDX standard also reduces rework once the final rule is published.

Hardik Dangodara
Business Development Manager