Open Banking: Data, Consent & Payments
Table of Contents
Open banking lets you permit another financial service to use information from an account you already have. A budgeting app can assemble transactions from several banks, a lender can examine cash flow with your permission, and a checkout service may help initiate a bank payment. Understanding which permission you are granting matters more than the label on the connection screen.
This guide explains the participants, the life of a data connection, how payment initiation differs, and who pays for the infrastructure. The default perspective is a U.S. consumer; UK examples are identified separately. The U.S. regulatory discussion is dated November 15, 2026, because the Section 1033 rule has been subject to a court stay and reconsideration.
What Is Open Banking?
Open banking is an arrangement for permissioned access to financial account data and, in some markets, separately authorized payment initiation. Its purpose is to let a customer use services beyond the institution where the account sits. A connection might support account aggregation, budgeting, identity or account verification, or an application for credit.
“Open” does not mean that anyone can inspect your bank account. A useful permission identifies the recipient, the accounts, the data or action, the purpose and the period of access. Permission to retrieve transactions is different from an instruction to transfer money.
Open banking is also different from opening a new bank account. The connection can leave the existing account and its provider in place while changing where you view or use its information. Broader questions about banks, fintech firms and banking-as-a-service belong to banking industry structure.
Who Does What?
| Participant | Role | Question to ask |
|---|---|---|
| Customer | Chooses whether to connect an account and for what service. | What benefit am I requesting? |
| Data holder | Maintains the account information, such as a bank or credit union. | Which accounts and information will it release? |
| Aggregator | Connects institutions to apps and can standardize the information they exchange. | Which intermediary also receives or processes my information? |
| User-facing app | Uses the connection to deliver the requested service. | What will it store, infer or share? |
Not every connection needs a separate aggregator, and one company can perform more than one role. Nevertheless, knowing the app’s name may not identify every company handling the data. The CFPB describes the common arrangement in which an app selects an aggregator to facilitate access. [1]
How an Open Banking Connection Works
Consider Maya and a fictional budgeting app. She wants a spending summary for one checking account. The service needs balances and transaction history; she is not asking it to pay a bill. A bank-hosted authorization journey can work as follows:
- Request a service. Maya chooses the budgeting feature. The app explains which data it needs and identifies any connection provider.
- Authenticate at the bank. In an OAuth connection, she is sent to her bank’s website or mobile app to establish that she controls the account.
- Authorize access. She reviews the accounts and available permissions, then approves the requested sharing. Account selection and data choices depend on the institution and integration.
- Receive and use data. Software retrieves the permitted information, potentially through an aggregator, and the app builds the spending summary. A one-time check and an ongoing feed have different access needs.
- Manage or end the connection. Maya reviews connected services and disconnects the budgeting app when she no longer needs it. She separately asks about deletion of previously collected information.
Plaid’s OAuth documentation provides a real example of the bank-hosted authentication and permission flow, including institution-dependent choices about accounts and data categories. It illustrates one implementation, rather than a guarantee about every service calling itself open banking. [2]
The important boundary in Maya’s example is that the app receives information for budgeting. Her money does not move simply because a transaction feed has been connected. Even so, transaction details can reveal sensitive information about income, health-related spending, location and relationships; an information-only connection still deserves scrutiny.
Disconnecting Is Different From Deleting
Revocation ends permission for further access under that connection; deletion concerns information already collected. These are separate tasks. Removing an app from your phone is not a reliable way to revoke server-side access, and changing your bank password may not terminate an independently authorized connection. [1]
For example, Plaid’s consumer instructions say that disconnecting an app stops future sharing through Plaid but does not delete data the app already holds. The app must be contacted separately about that data. Plaid also explains that some information can remain in its own systems after a deletion request where law permits or requires retention. [3] [4]
Use the app’s and bank’s connection controls where available, keep the confirmation, and ask what happens to stored data. If the service also has a paid subscription or payment mandate, check its cancellation process separately. Disconnecting an information feed does not establish that every other agreement has ended.
APIs vs Credential-Based Access
An application programming interface (API) defines how software requests and receives information. OAuth is an authorization framework that can let a customer delegate limited access without handing the recipient the bank login. The terms describe different parts of a connection: an API is not, by itself, proof of the authorization method or its quality. The OAuth specification distinguishes the customer’s credentials from access tokens with defined scopes and durations. [18]
In credential-based access, a third party may receive the customer’s reusable login and use it to retrieve information from the bank’s customer interface. This is often associated with screen scraping. In a bank-hosted OAuth flow, the customer authenticates with the bank, and the connection uses delegated access credentials or tokens. Plaid documents that distinction. [2]
| Feature | Bank-hosted delegated access | Credential-based retrieval |
|---|---|---|
| Where the bank login is entered | The bank’s genuine site or app in the flow described here. | A third party’s connection interface may collect it. |
| What supports continued access | A delegated authorization, commonly represented by tokens. | The customer’s credentials and the retrieval arrangement. |
| Permission controls | May offer account, data-category and duration choices. | May be less granular; inspect the actual service. |
| Risks that remain | Deceptive consent, compromised tokens, breaches and misuse of copied data. | Those data risks plus exposure of reusable login credentials. |
Delegated access can reduce the need to share a reusable password, but it does not make the recipient trustworthy or the collected data harmless. A token is still a sensitive means of access. Verify the destination of an authentication redirect and read the permission screen instead of assuming a bank logo proves legitimacy.
Data Access vs Account-to-Account Payments
Data access answers a question about an account; payment initiation requests an action on it. A lender may ask to verify income or transactions without being authorized to debit the account. A payment service may request a transfer for a particular amount and recipient. The same platform can offer both functions, but the permissions and consequences require separate attention.
Account-to-account payments move money between accounts using the relevant payment infrastructure. Open banking can provide the authorization and initiation experience; it does not replace the underlying rail or determine settlement speed by its name. For the distinction among rails and forms of money, see digital payment systems and central bank digital currency.
Suppose a shopper approves a hypothetical £80 purchase. A payment initiation service can prepare the amount and beneficiary and take the shopper through bank authorization. This permission concerns a payment, unlike Maya’s budgeting feed.
TrueLayer’s GBP/EUR payment documentation separates payment configuration, end-user authorization and payment monitoring. It also distinguishes the payment request from the scheme over which banks complete it. This is a documented provider process, not a claim that every U.S. bank supports that checkout. [5]
A successful consent or return-to-merchant screen is not, by itself, evidence that a payment has settled. Check the actual status, recipient and amount. Information such as routing and account numbers can also help initiate payments, so “data” is not synonymous with “nonsensitive.” The adopted U.S. Section 1033 rule expressly includes certain payment-initiation information among its covered data categories; that classification does not itself authorize a transfer. [6]
For U.S. consumer accounts, qualifying electronic transfers can carry Electronic Fund Transfer Act and Regulation E protections, including when initiated through a nonbank provider. Coverage, authorization and reporting circumstances matter; a pay-by-bank label neither guarantees a refund nor removes statutory rights. Report an unexpected transfer promptly to the account-holding institution. [7]
How Open Banking Businesses Make Money
The customer using an app is not necessarily the customer paying the connection provider. Aggregators can charge businesses for connectivity, recurring information feeds, verification, analytics or payment services. Plaid’s published billing documentation, for example, describes one-time, subscription, per-request and transfer-related fee models, depending on the product and contract. [8]
| Illustrative business model | Possible payer | What to examine |
|---|---|---|
| Data connectivity | The app or financial institution integrating the service. | Coverage, recurring connection costs and reliability. |
| Verification or analysis | A lender, account provider or other requesting business. | Which inputs and conclusions are supplied, and how errors are corrected. |
| Payment services | A merchant or platform accepting bank payments. | Processing fees, completion, refunds and fraud exposure. |
| Customer-facing application | The user, or a business funding the service. | Subscriptions, referral incentives and the actual data-use terms. |
These are analytical categories, not a claim that every provider uses each model. In particular, charging for an API service does not establish that a firm sells personal transaction data. Conversely, a free app is not evidence that its data use has no commercial consequences.
A Hypothetical Infrastructure Bill
Assume a fictional app has 1,000 billable connections at $0.40 per month and buys 50 one-time verifications at $0.75 each. These assumed prices are solely for teaching and are not Plaid or TrueLayer quotes.
Recurring connection cost: 1,000 × $0.40 = $400.00.
Verification cost: 50 × $0.75 = $37.50.
Combined assumed bill for the month: $400.00 + $37.50 = $437.50.
If 10% of those connections belong to inactive users but remain billable under this hypothetical contract, their cost is 1,000 × 10% × $0.40 = $40 per month. The example shows why an app cares about connection management. It says nothing about the app’s profit: staff, security, support, compliance and other costs are excluded.
For a lender, permissioned cash-flow information may help assess a borrower whose situation is not clear from other records. It can reduce some asymmetric information, but the lender still needs a defensible decision process. More data is not proof of better underwriting; bank credit risk management also considers repayment capacity, verification and monitoring.
U.S. Open Banking Rules: November 2026 Status
It is useful to separate the statute, the adopted rule, the court’s relief and the reconsideration process. Treating these as one event can turn an old implementation date into misleading consumer guidance.
The CFPB’s compliance page reports that the Personal Financial Data Rights Rule’s compliance dates were stayed on October 29, 2025. The court’s order enjoins CFPB enforcement until it completes reconsideration. OIRA’s November 14, 2026 snapshot lists the reconsideration at the proposed-rule stage, pending review. Do not assume the original rollout deadlines are currently operative. [9] [10] [11]
The statutory foundation remains distinct. Section 1033 of the Consumer Financial Protection Act, codified at 12 U.S.C. 5533, addresses access to information about a consumer’s financial product or service, subject to CFPB rules. It includes exceptions, such as confidential commercial information and certain fraud-prevention information. It is not a promise that every app can retrieve every record from every account. [12]
The adopted 2024 text is not a substitute for checking present implementation status. For example, it limits authorized third-party collection to one year without renewed authorization and restricts secondary uses such as treating targeted advertising or sale of covered data as necessary to provide another requested service. Those provisions describe the adopted rule; the stay and reconsideration mean readers should not assume identical protections and expiry controls are operating across all current connections. [13]
Reconsideration is not a replacement final rule. The CFPB’s August 22, 2025 advance notice sought input on representatives, fees, security and privacy. A notice seeking comments, or a proposal undergoing review, does not by itself put a new final framework into effect. Check the current CFPB status page and the actual service’s terms before relying on a particular access right or deadline. [14]
UK and EU Terminology Does Not Establish U.S. Rights
In the UK, the FCA distinguishes account information service providers, which can consolidate selected account information, from payment initiation service providers, which can enable direct bank payments. Its consumer guidance calls for explicit consent and checking that a firm is authorized or registered for the relevant activity. An FCA register check is a UK safeguard, not a U.S. authorization system. [15]
The EU developed a separate payment-services framework under PSD2, applicable from January 2018, with later reform work. That history helps explain the terminology, but a UK or EU description should not be copied into a U.S. promise about permission duration, account coverage, fees or fraud reimbursement. Specific national rules and the effective dates of reforms require their own check. [16]
How to Evaluate an Open Banking Connection
Start with the task you actually want to accomplish. A one-time account verification, an ongoing budget feed and a recurring payment arrangement need different permissions. Use the following questions before approving access:
- Identify the parties. Name the app, connection provider and account provider. Find a usable support and privacy contact.
- Match access to the task. Check accounts, data categories, history, refresh frequency and duration. Ask why an unrelated account or payment permission is needed.
- Check the data’s usefulness. Look at the last refresh time and compare important figures with bank records. Pending transactions, transfers and merchant categories can require interpretation.
- Follow the information after collection. Read what is stored, who receives it, why it is shared and what happens after disconnection.
- Inspect payment permissions separately. Confirm the amount, beneficiary, frequency and cancellation process, plus the protections for the actual account and transfer.
- Plan your exit. Find the revocation control, deletion-request route and subscription cancellation terms before you need them.
An app connection also does not change the economic nature of the underlying account. Viewing deposit information in another interface does not transform it into a different claim; the account provider’s balance sheet still matters. See bank balance sheet management for that separate banking function.
Common Mistakes
- Assuming a single consent covers every purpose. Read data access, payment instructions and additional data-use choices separately.
- Equating an API with safety. An interface can improve controlled exchange, but fraud, excessive access and insecure storage remain possible.
- Deleting the app and assuming access ended. Use connection controls and obtain confirmation; request deletion of stored data separately.
- Calling every connected product a bank. A data aggregator’s role does not establish a bank charter or deposit protection. Those questions belong to financial regulation and deposit insurance.
- Assuming every bank payment is instant or refundable. The payment rail, account, authorization and applicable rules matter.
- Reading an old implementation deadline as current law. Check the dated status of the U.S. rule and distinguish a proposal from an effective requirement.
Limitations and Consumer Risks
Open banking can make information more portable, but it does not ensure complete or accurate coverage. Institutions may support different account types, data fields and update frequencies. A connection can break, an app can misclassify a transfer as income, or an outdated balance can mislead a spending decision. An attractive consolidated screen is not a substitute for checking the underlying records when the decision is consequential.
Sharing also expands the places where sensitive information may be processed or retained. Authentication protects an entry point; it does not prevent all later misuse, breach or unwanted inference. Dependence on a common aggregator can make several otherwise separate apps vulnerable to the same outage. These are risks to evaluate, rather than claims that a particular provider has failed.
Finally, consent can be poorly understood or obtained through deception. Strong bank authentication does not establish that a recipient is legitimate or that a payment’s commercial purpose is sound. If fraud occurs, preserve records and report it promptly. The legal treatment of an unauthorized transfer differs from a blanket promise to reimburse every bad transaction; sharing account access also does not automatically waive U.S. statutory protections. [7]
Frequently Asked Questions
Sources
- CFPB: What to consider when sharing your financial data, July 24, 2020, archived consumer guidance. Participants, access and account-management cautions.
- Plaid: OAuth guide. Bank-hosted authorization and scoped permissions; provider-specific technical documentation.
- Plaid: How do I disconnect my financial accounts from an app? Future sharing versus data already held by an app.
- Plaid: Can I remove app access or delete my data from Plaid? Deletion options and retention exceptions.
- TrueLayer: Create a payment. GBP/EUR payment configuration, user authorization, schemes and monitoring.
- CFPB: 12 CFR 1033.211, Covered data. Adopted rule text; read with the stay/status sources below.
- CFPB: Electronic Fund Transfers FAQs. Consumer-account coverage, unauthorized transfers and nonwaivable rights.
- Plaid: Pricing and billing. Fee structures, not the hypothetical rates used in this article.
- CFPB: Personal financial data rights compliance resources. Agency notice of the October 29, 2025 stay.
- Forcht Bank v. CFPB: October 29, 2025 Memorandum Opinion and Order, docket 90, court-authored record reproduced by Justia. Enforcement injunction pending reconsideration.
- OIRA: CFPB Executive Order submissions under review. November 14, 2026 snapshot, RIN 3170-AB39, proposed-rule stage.
- U.S. Code: 12 U.S.C. 5533, Consumer rights to access information. Statutory foundation and exceptions.
- CFPB: 12 CFR 1033.421, Third party obligations. Adopted authorization and use restrictions; subject to the described stay.
- CFPB: Personal Financial Data Rights Reconsideration, August 22, 2025 advance notice.
- FCA: Account information and payment initiation services, updated June 25, 2025. UK consumer guidance.
- European Commission: Payment services. PSD2 history and payment-services reform context.
- FCA: Open banking and open finance. Distinction between banking-data access and broader financial data sharing.
- IETF RFC 6749: The OAuth 2.0 Authorization Framework, October 2012, sections 1 and 1.4. Foundational authorization and access-token concepts, rather than a current implementation-security checklist.
Sources accessed November 15, 2026. Provider documentation describes particular services and can change. Numerical examples are hypothetical; regulatory status should be rechecked for later decisions.
Disclaimer
This article is for educational and informational purposes only and does not constitute legal, investment or cybersecurity advice. Data-access rights, payment protections and provider practices depend on the account, jurisdiction, service and effective rules. Consult current official guidance and an appropriately qualified professional about your circumstances.
