How read-only bank connections work

A read-only bank connection allows a service to receive agreed account information without giving that connection the ability to send money. It can support a budgeting view, but it is useful to understand what travels through the connection and what the app adds afterwards. The bank record and the app's interpretation are different things.

You do not need to understand software development to make sense of this. Follow the journey from your choice of account, through the information received, to the decisions you make from the display. At each stage, ask what has been confirmed and what still depends on your own knowledge.

Information access has a specific purpose

The FCA describes account information services as online services providing consolidated information about payment accounts held elsewhere. Payment initiation instead starts a payment order at the user's request. Its explanation for providers makes the distinction clear. Viewing a transaction through an information connection is different from instructing the bank to pay someone.

Think of the connection as a source for a spending record. It may help answer where a transaction appeared or what balance was supplied. It does not establish whether a purchase was sensible, whether a future bill has been allowed for or how much of an account belongs to someone else.

The phrase read-only applies to the access being described. If an app offers another service involving payments, read that service's permissions separately. Our Open Banking safety guide explains why the name of the technology alone cannot tell you which activity you are approving.

You choose, then the bank confirms

A typical journey starts in the service you want to use. MoneyHelper explains that the account connection process usually takes you to your bank's app or online portal to confirm the sharing request. The information involved can include balances, transactions and regular payment details. See its guide to digital banking.

Before beginning, decide what the connection is for. If you want to understand personal everyday spending, consider how a shared account would affect that picture. Connecting an account because it appears on a selection screen is a different decision from connecting it because you need its information.

Read the account names and the request as you go. When you return to the budgeting service, compare the accounts displayed with the ones you intended to select. If something is missing or unfamiliar, resolve that question before treating the combined total as a reliable starting point for your plan.

Permissions describe the boundaries

The FCA's data exchange rules require account information providers to prevent access outside the designated accounts and associated transactions covered by consent. Those rules also address continuing consent for background access. Check the app's current instructions when it asks you to confirm or reconnect.

Do not treat a permission screen as a permanent description of everything you might later use. A different account or feature may raise a new decision. Keep the purpose of each connection clear so that you can tell whether a later request belongs to the task you started.

When a service explains its access in vague terms, ask a concrete question. Which accounts does this cover? What information will appear? Which company supplies the account information service? Those questions are more useful than asking for an unqualified promise that everything is safe.

The display adds interpretation

Once account information appears in an app, review how it has been organised. The bank's description of a payment may be different from the name you remember from the shop. A category may be inferred from the merchant rather than from the individual items you bought.

If a supermarket payment included food and household supplies, a single category may not reflect your preferred budgeting split. That does not necessarily mean the bank information is wrong. It means the way you want to plan can be more detailed than the source record.

Choose a practical level of detail. Correct a category when doing so helps a decision, such as separating a work expense from household spending. Avoid spending your whole review trying to reconstruct every small purchase if that leaves no time to consider the bills ahead. The connection should support your planning process.

Connected does not mean complete

Look for the date of the latest information or a connection status, where the app provides one. Compare a recent transaction with your bank's own view if a total seems surprising. Treat missing information as a question to investigate rather than assuming there has been no spending.

Accounts outside the connection still matter. Cash, a separate card or a bill paid by someone else can change the budget even when the connected information is accurate. Keep a note of what your chosen view leaves out so you do not repeatedly mistake a partial picture for the whole household.

Transfers need particular care in your own review. Moving money between accounts you own changes its location, but does not by itself create new earnings. Check how the app treats both sides before interpreting an income or spending total. The same principle applies when you compare a card purchase with a later card repayment.

A concrete example of limited access

Ulsa™ describes its UK bank connections as read-only through a regulated provider, with no access to bank passwords and no ability to move money. Its Open Banking page explains that arrangement. This describes the connection's purpose and limits, rather than guaranteeing that every bank or account can connect.

For any app, judge availability against your actual account before rebuilding your budgeting routine around it. The fact that a bank appears in a general description does not answer every question about account types or the current connection. Follow the provider's support guidance if the expected account does not appear.

You can use our factual app comparison to identify questions to check. Keep your assessment grounded in the task you need to complete, such as reviewing a household category or seeing the accounts used for bills. A long feature list is not a substitute for that check.

Keep an exit route and a working budget

Know where to find the controls for ending access. Our disconnecting guide separates stopping new information from dealing with an app account and existing records. Understanding those choices early makes a later change of mind easier to handle.

Keep essential bill dates somewhere you can reach independently of a single connection. If a refresh is interrupted, you should still know what needs attention. A short record of upcoming commitments can provide continuity while a support issue is being resolved.

Finally, review what the information means before acting on it. A balance answers a question about the account at a particular point; a budget answers a question about commitments and choices over time. Read-only connections can help supply the first part, while your own plan supplies the context.