The CFPB’s personal financial data rights rule (12 CFR part 1033), its reconsideration and the 2025 injunction, explained
The 2024 open banking rule requires covered banks, card issuers and payment providers to make account data available to consumers and authorized third parties. The CFPB is reconsidering it, and since October 29, 2025 a federal court has barred enforcement until that is done.
What the rule asks of data providers
Part 1033 implements section 1033 of the Consumer Financial Protection Act of 2010. The final rule requires banks, credit unions and other financial service providers to make consumers’ data available on request to consumers and to authorized third parties [1].
A data provider has obligations if it controls or possesses covered data about a Regulation E account, a Regulation Z credit card, or the facilitation of payments from either, that the consumer obtained from it. The rule’s own example is that a digital wallet provider is a data provider. Depository institutions with total assets at or below the Small Business Administration size standard are outside the main requirements in subparts B and C [1].
Covered data means, as applicable [1]:
- transaction information, with at least 24 months of history deemed sufficient;
- account balance;
- information to initiate a payment to or from a Regulation E account, such as an account and routing number, which may be tokenized;
- terms and conditions, including fee schedules, rates and credit limits;
- upcoming bill information;
- basic account verification information: name, address, email address and phone number.
The interfaces the rule describes
The architecture is set out in subpart C. A covered data provider must maintain two interfaces: a consumer interface and a developer interface for authorized third parties. It may not charge consumers or authorized third parties any fee for establishing or maintaining those interfaces or for answering requests [1]. The developer interface must also meet these requirements:
- It must make covered data available in a standardized, machine-readable format.
- Its performance must be commercially reasonable, and it cannot be if proper responses fall below 99.5 percent of requests in any calendar month, with scheduled downtime excluded.
- The data provider must not let a third party reach the developer interface with the credentials a consumer uses for the consumer interface.
- The developer interface falls under an information security program that meets the Gramm-Leach-Bliley Act safeguards rules that apply to the provider [1].
Conformance to a consensus standard issued by a standard setter the CFPB recognizes counts as an indication of compliance for several of these requirements [1].
What it asks of third parties
A third party becomes an authorized third party by following the authorization procedures in section 1033.401. Among its obligations, it must limit collection of covered data to a maximum of one year after the consumer’s most recent authorization, and obtain a new authorization to continue beyond that [1]. The rule sets no separate compliance dates for third parties, because their compliance depends on data providers’ compliance [2].
The compliance schedule as written
The rule staggers data providers’ compliance by size [1]:
- April 1, 2026: depository institutions with at least $250 billion in total assets, and nondepository institutions with at least $10 billion in total receipts in calendar year 2023 or 2024.
- April 1, 2027: depository institutions with $10 billion to under $250 billion, and nondepository institutions below the $10 billion receipts threshold.
- April 1, 2028: depository institutions with $3 billion to under $10 billion.
- April 1, 2029: depository institutions with $1.5 billion to under $3 billion.
- April 1, 2030: depository institutions with more than $850 million and under $1.5 billion.
After the change of administration, the court hearing the challenge paused summary-judgment briefing for a total of 90 days so the CFPB’s new leadership could review the rule, and extended the compliance deadlines by an equivalent period, moving the first from April 1 to June 30, 2026 [3]. The CFPB’s August 2025 notice also states that the compliance dates were stayed by 90 days [2]. The eCFR version dated November 1, 2026 still shows the original dates [6].
The reconsideration
Forcht Bank, the Kentucky Bankers Association and the Bank Policy Institute sued in the Eastern District of Kentucky on the day the rule was finalized; the Financial Technology Association intervened to defend it [3]. After its review, the CFPB told the court the rule was unlawful and should be set aside and moved for summary judgment. On July 29, 2025 it instead asked the court to stay the case while it started a new rulemaking, and the court agreed [3].
The advance notice published on August 22, 2025 asks for comment on four issues: who can serve as a representative making a request for a consumer, how fees might defray data providers’ costs, the threats and costs and benefits for data security, and the threats to data privacy. It also asks about the compliance dates and says the CFPB plans to propose extending them [2].
The October 29, 2025 order
The plaintiffs asked the court to lift the stay briefly to postpone the compliance deadlines while the CFPB worked on a new rule. The court granted the motion on October 29, 2025 [3]. It found the plaintiffs likely to succeed on the merits, reasoning in particular:
- that “representative” in the statute should be read alongside “agent” and “trustee,” which describe fiduciary relationships, rather than to cover the rule’s authorized third parties;
- that the CFPB failed to consider the combined effect of four provisions on data security;
- that the plaintiffs raised a reasonable argument that the CFPB had not addressed how providers could comply where consensus standards might not yet exist by the deadlines.
It also found that the plaintiffs’ compliance costs were likely unrecoverable and so were irreparable harm. The order enjoins the CFPB from enforcing the rule until it has completed its reconsideration, and the opinion describes this as a temporary stay under 5 U.S.C. 705 pending final rulemaking [3]. These are findings on likelihood of success at a preliminary stage, not a final judgment on the merits.
Where things stand
As checked on November 14, 2026, the CFPB’s page for the reconsideration lists only the August 2025 advance notice [4]. The rule’s entry in the 2026 Unified Agenda, published August 14, 2026 [7], listed a proposed rule for July 2026 [5]. As of November 14, 2026, no proposed rule had been published: Federal Register API searches run that day for documents under the rule’s identifier, RIN 3170-AB39, and for documents affecting 12 CFR part 1033 published since January 1, 2025, each returned only the August 2025 advance notice [8]. The rule remains in the Code of Federal Regulations [6], but the CFPB may not enforce it while the injunction stands.
In our view, for platform teams the rule text still describes a target design, with consumer and developer interfaces, credential-free third-party access and a monthly performance floor, while its timing and parts of its substance are open. This explainer describes the rule and the litigation; it is not legal advice, and institutions should confirm their position with counsel.
Moraph’s teams help organizations with work like this. See our solutions.
Spotted an error? Tell us and we will check it and correct the explainer where needed.