
Quick answer
The 1033 rule is a 2024 CFPB regulation requiring banks and card issuers to share your account data, free, with you and apps you authorise, through secure interfaces instead of password sharing. As of October 2026, a federal court bars the CFPB from enforcing it while the agency reconsiders it[3][10].
Key points
- Section 1033 of the Dodd-Frank Act gives US consumers a right to access their financial account information in electronic form.
- The CFPB's final rule, published on 18 November 2024, made banks, card issuers and some payment providers share six categories of data for free.
- It banned screen scraping as a way to comply and set a 99.5% monthly response-rate standard for bank interfaces.
- Apps receiving data may use it only for what is reasonably necessary for your request, and must get your permission again at least once a year.
- A federal court enjoined the CFPB from enforcing the rule on 29 October 2025 until it finishes reconsidering it; a proposed revision has been under White House review since August 2026.
On this page
#What is section 1033?
Section 1033 is a short part of the Dodd-Frank Act, the big US financial reform law. It says that, subject to rules from the Consumer Financial Protection Bureau (CFPB), a financial company must make available to a consumer, on request, information about the product or service the consumer got from it, including transactions, costs, charges and usage data, in an electronic form the consumer can use[1]. In plain words: your financial data is yours to get, and to pass on.
The law needed a detailed rule to work in practice, and that rule arrived only in 2024. If you are new to the idea of sharing bank data with apps, start with what is open banking; this article focuses on the US version.
#What did the 2024 rule require banks to do?
The CFPB announced the final Personal Financial Data Rights rule on 22 October 2024[2] and published it in the Federal Register on 18 November 2024. It requires data providers to make consumers' data available on request to consumers and to authorised third parties in a secure and reliable manner, and it prohibits fees or charges for that access[3].
The rule covers consumer accounts governed by Regulation E (such as checking accounts), credit cards governed by Regulation Z, and products that facilitate payments from those accounts or cards[4]. The data that must be shared falls into six categories[5]:
| Category | What it includes | Example use by an app |
|---|---|---|
| Transaction information | Amounts, dates, payment types, payees, fees; at least 24 months of history is deemed sufficient[5] | A lender checking regular income |
| Account balance | The balance information for the account[5] | A budgeting app's dashboard |
| Payment initiation information | Details needed to start a payment, such as account and routing numbers, or a tokenised number[5] | Setting up a pay-by-bank payment |
| Terms and conditions | Fee schedules, interest rates, credit limits, rewards terms[5] | Comparing your card's rate with others |
| Upcoming bill information | Scheduled payments and amounts due[5] | Reminding you of a bill due date |
| Basic account verification | Name, address, email, phone and a truncated account number[5] | Confirming the account belongs to you |
Banks must offer a developer interface, meaning an API that apps connect to, in a standardised, machine-readable format. The interface must answer properly at least 99.5% of requests in each calendar month, not counting scheduled downtime, and a bank must not let a third party use your own login credentials to access it[6]. That last line is how the rule shuts the door on screen scraping as a way of complying[3].

#What rules apply to the apps that receive your data?
The rule also binds the third parties. They must limit the collection, use and retention of your data to what is reasonably necessary to provide the product or service you asked for. A permission lasts a maximum of one year; to keep collecting data, the app must get a new authorisation no later than the anniversary of the last one[3]. When you revoke access, the CFPB described deletion as the default[2].
#Who had to comply, and by when?
The rule set staggered compliance dates by size. Depository institutions (banks and credit unions) at or below the Small Business Administration size standard are excluded entirely[4]. The others were given dates from 2026 to 2030[7]:
| Original date | Depository institutions (total assets) | Non-depository institutions |
|---|---|---|
| 1 April 2026 | $250 billion or more | $10 billion or more in total receipts in 2023 or 2024 |
| 1 April 2027 | $10 billion to under $250 billion | Under $10 billion in receipts in both 2023 and 2024 |
| 1 April 2028 | $3 billion to under $10 billion | — |
| 1 April 2029 | $1.5 billion to under $3 billion | — |
| 1 April 2030 | Over $850 million to under $1.5 billion | — |
Source: eCFR text up to date as of 30 September 2026[7]. A court later extended the first deadline and then barred enforcement; see the timeline below.
To help firms agree on technical formats, the CFPB also created a process to recognise industry standard-setting bodies. On 8 January 2025 it recognised Financial Data Exchange (FDX) as a standard-setting body under the rule[8]. Our guide to how banking APIs work explains what such standards contain.
#Why is the 1033 rule on hold?
A bank and two trade associations sued in the US District Court for the Eastern District of Kentucky. In 2025 the CFPB changed course: on 29 July 2025 the court stayed the case after the Bureau said it would reconsider the rule, and on 22 August 2025 the CFPB published an advance notice asking for comments on four topics: who counts as a consumer's representative, whether banks may charge fees to cover costs, information security, and privacy risks[9]. Earlier, the court had already extended the compliance deadlines, moving the first from 1 April to 30 June 2026[10].
On 29 October 2025 the court granted a preliminary injunction stating that the CFPB is enjoined from enforcing the Personal Financial Data Rights Rule until it has completed its reconsideration[10]. A law firm analysis from April 2026 described the rule as enjoined while the Bureau reviews whether it should be modified or withdrawn[11]. The CFPB's regulatory agenda, published on 14 August 2026, still lists a rulemaking to reconsider certain aspects of the November 2024 rule[12]. On 4 August 2026 the White House Office of Information and Regulatory Affairs (OIRA) received a CFPB proposed rule titled Personal Financial Data Rights Reconsideration for review, and on 3 October 2026 OIRA still listed it as pending review[13]. A revised proposal may therefore be published for comment, but until the CFPB completes its reconsideration the court order stands.
The 1033 rule, step by step
22 Oct 2024
CFPB announces the final Personal Financial Data Rights rule[2].
18 Nov 2024
Final rule published in the Federal Register[3].
8 Jan 2025
CFPB recognises Financial Data Exchange as a standard-setting body[8].
29 Jul 2025
Court stays the lawsuit as the CFPB announces it will reconsider the rule[9].
22 Aug 2025
CFPB publishes an advance notice of proposed rulemaking; comments due 21 October 2025[9].
29 Oct 2025
Court enjoins the CFPB from enforcing the rule until reconsideration is complete[10].
4 Aug 2026
OIRA receives the CFPB's proposed rule on reconsideration for review; still pending on 3 October 2026[13].
14 Aug 2026
CFPB regulatory agenda still lists the reconsideration rulemaking[12].
Worked example
Worked example: the 99.5% response rate and the one-year permission
Imagine a bank's developer interface receives 2,000,000 requests for covered data in a month, outside scheduled downtime. Under 12 CFR 1033.311 at least 99.5% must get a proper response[6]. And if you authorised an app on 15 March 2026, the app would need your new authorisation by 15 March 2027 to keep collecting[3]. Calculated with code.
- Most failures allowed: 2,000,000 × 0.5%
- 10,000 requests
- Bank with 9,000 failures: (2,000,000 − 9,000) ÷ 2,000,000
- 99.55%, meets the standard
- Bank with 12,500 failures: (2,000,000 − 12,500) ÷ 2,000,000
- 99.375%, misses the standard
- Authorisation on 15 March 2026 + 1 year
- Reauthorise by 15 March 2027
#What does the pause mean for you as a consumer?
The injunction stops the CFPB from enforcing the rule[10]; it does not make data sharing illegal. Apps that already connect to banks may keep working under the arrangements they had before. What you lose for now is the guarantee that the rule's specific protections, such as free access, the one-year permission limit and the ban on password-based access, can be enforced by the CFPB. That makes your own checks more important.
Common beginner mistakes about the 1033 rule
Thinking the rule was cancelled
As of the latest documents we opened, the rule was enjoined and under reconsideration, not withdrawn[10][12].
Assuming 1 April 2026 was a live deadline
The court first extended the first deadline to 30 June 2026 and then barred enforcement entirely pending reconsideration[10].
Believing every bank was covered
Depository institutions at or below the SBA size standard were excluded from the start[4].
Handing an app your bank password because 'the rule allows it'
The rule pushed in the opposite direction: it said banks cannot meet their duty by letting apps use your login credentials[6].
#How does the US approach compare with Europe's?
Europe built open banking into payments law: PSD2 created regulated account information and payment initiation services and applies since 2018[14]. The US rule focuses on a consumer's right to data and how third parties may use it, and its future shape depends on the CFPB's reconsideration. If you want to see how the data then moves money, read pay by bank explained and the payments guide to ACH, wire and instant payments.
The bottom line
The 1033 rule turned a one-paragraph consumer right into detailed duties: free data access, secure interfaces, no password sharing and limits on how apps use your data. A court has stopped the CFPB from enforcing it while the agency reconsiders, so the final US model is still open. Until that is settled, judge each app on how it connects and what it asks for.
Frequently asked questions
Is the CFPB 1033 rule in effect in 2026?
Can my bank charge me to share my data with an app?
Does the rule cover investment or mortgage accounts?
They are not on its coverage list, which is limited to Regulation E accounts, Regulation Z credit cards and payment facilitation from them[4].
What is FDX?
Financial Data Exchange is an industry body the CFPB recognised on 8 January 2025 as a standard-setting body under the rule[8].
Sources
- 12 U.S. Code § 5533 — Consumer rights to access information — Legal Information Institute, Cornell Law School (US Code text) Primary
- CFPB Finalizes Personal Financial Data Rights Rule to Boost Competition, Protect Privacy, and Give Families More Choice in Financial Services — Consumer Financial Protection Bureau, 2024 Primary
- Required Rulemaking on Personal Financial Data Rights (final rule, 89 FR, 18 November 2024) — Federal Register (Consumer Financial Protection Bureau), 2024 Primary
- 12 CFR 1033.111 — Coverage of data providers — eCFR (US Code of Federal Regulations), 2026 Primary
- 12 CFR 1033.211 — Covered data — eCFR (US Code of Federal Regulations), 2026 Primary
- 12 CFR 1033.311 — Requirements applicable to developer interface — eCFR (US Code of Federal Regulations), 2026 Primary
- 12 CFR 1033.121 — Compliance dates — eCFR (US Code of Federal Regulations), 2026 Primary
- CFPB Approves Application from Financial Data Exchange to Issue Standards for Open Banking — Consumer Financial Protection Bureau, 2025 Primary
- Personal Financial Data Rights Reconsideration (advance notice of proposed rulemaking) — Federal Register (Consumer Financial Protection Bureau), 2025 Primary
- Forcht Bank, NA et al. v. Consumer Financial Protection Bureau et al., No. 5:24-cv-00304, Document 90 (order granting preliminary injunction, 29 October 2025) — US District Court for the Eastern District of Kentucky (via Justia), 2025 Primary
- Section 1033 Compliance Date: Open Banking Rule Enjoined and Under Reconsideration — Cozen O'Connor, 2026
- Consumer Financial Protection Bureau — Regulatory Agenda (published 14 August 2026) — Federal Register (Consumer Financial Protection Bureau), 2026 Primary
- Personal Financial Data Rights Reconsideration (RIN 3170-AB39), proposed rule: OIRA Executive Order submissions under review — Office of Information and Regulatory Affairs, Office of Management and Budget (reginfo.gov), 2026 Primary
- Payment Services Directive (PSD2): Regulatory Technical Standards (RTS) enabling consumers to benefit from safer and more innovative electronic payments (MEMO/17/4961) — European Commission, 2017 Primary



