Open banking lets customers authorize regulated or approved providers to access account data or initiate payments through standardized interfaces.
Open banking is a framework that lets a customer authorize an approved third-party provider to access specified bank-account data or, where permitted, initiate a payment through an application programming interface (API). The customer does not transfer ownership of the account to the third party, and the bank or payment institution remains responsible for holding the account and executing services within the applicable rules.
Open banking is not one universal product. Its legal scope, eligible accounts, provider-approval process, consent rules, liability standards, and technical specifications differ by jurisdiction.
| Capability | What the customer permits | Typical use | What it does not necessarily mean |
|---|---|---|---|
| Account-information access | Read specified balances, transactions, or account details | Multi-bank dashboards, cash-flow analysis, affordability checks | The provider can move money |
| Payment initiation | Send a payment instruction from a selected account | Account-to-account checkout or bill payment | The provider holds or settles the funds |
| Account aggregation | Combine data from several connected institutions | A consolidated financial view | Every balance is current to the same timestamp |
| Product or service connection | Use authorized data in another financial workflow | Accounting, lending, or treasury tools | Approval, pricing, or suitability is guaranteed |
These capabilities may appear in one application, but they should remain distinct in the permission screen and in a reader’s analysis.
Technical access does not eliminate ordinary payment checks. A payment may still be rejected, delayed, returned, or reversed because of insufficient funds, fraud controls, sanctions screening, an invalid beneficiary, or rules of the underlying payment system.
Suppose a small business connects checking accounts at Bank A and Bank B to a cash-management application.
| Event | Permission involved | Financial effect |
|---|---|---|
| The application retrieves balances and recent transactions | Account-information access | No money moves |
| The dashboard shows Bank A at $18,000 and Bank B at $7,000 | Aggregation and presentation | Displayed data may have different retrieval times |
| The owner asks the application to initiate a $3,000 supplier payment from Bank A | Payment-initiation permission | A payment instruction is sent |
| Bank A authenticates the instruction and processes it through an applicable payment rail | Bank and payment-system execution | Funds move only if the instruction is accepted and settled |
| The dashboard later refreshes Bank A to $15,000, ignoring fees and other activity | New account-information request | The display reflects the updated bank record |
The example shows why “connected account,” “payment initiated,” and “payment settled” are not interchangeable statuses. The application may organize data and transmit instructions without becoming the deposit-taking bank or the settlement system.
For consumers, open banking can reduce repeated data entry and make it easier to compare or manage accounts in one interface. For businesses, it can support bank reconciliation, cash forecasting, accounting integrations, and account-to-account collections. For lenders and analysts, permissioned transaction data may supplement other evidence when evaluating cash flow.
Those uses do not make the data complete or decision-ready by themselves. Coverage may exclude certain institutions, account types, pending transactions, older history, or manually recorded activity. Any consequential decision should document the data source, retrieval time, covered accounts, and known gaps.
Disconnecting an account may stop future access, but it may not automatically delete data already lawfully collected. Review the provider’s retention and deletion terms separately.
Before relying on a connection, verify:
“Open banking means a third party can see everything.” Access should be limited by the customer’s authorization, available API scope, and local rules.
“An account aggregator is a payment network.” An aggregator may collect and display information. Payment initiation and settlement are separate functions.
“API access guarantees real-time data.” An API can provide timely data, but refresh schedules, pending entries, outages, and institution-specific behavior can still affect the result.
“Revoking access reverses a completed payment.” Revocation generally concerns future access. A payment already executed follows the rules of the payment service and rail.
Open banking models range from regulatory mandates to market-led standards. The European Union’s payment-services framework, the United Kingdom’s implementation, and U.S. consumer financial data initiatives do not use identical terminology or impose identical duties. Because these frameworks continue to develop, use the current regulator or official program page for the jurisdiction rather than assuming that a rule from another market applies.