How Bank Connections Work: A Plain-English Guide to Plaid and Read-Only Bank Data

You have almost certainly seen the screen: an app asks to "connect your bank account", a familiar bank login pops up, and moments later the app knows your balance and recent transactions. If that gave you a flicker of unease — good instinct. It is worth understanding exactly what happens in that moment. The short version is reassuring, but only because of how the plumbing is designed.

Much of that plumbing is a company called Plaid. Here is what it is and what it actually does, in plain English.

What Plaid is

Plaid is the connective tissue between your bank and the apps you use. Thousands of financial apps — the well-known payment and budgeting names among them — do not each build a separate, fragile integration with every bank. Instead they use Plaid as a single, secure bridge that speaks to banks on their behalf.

When you connect an account through Plaid, you are authenticating directly with your bank through Plaid's secured flow, and then granting the app permission to receive specific data. Plaid currently connects banks across the United States, Canada, the United Kingdom, and Europe. (South African bank feeds run on different rails — but if you or your clients bank in those regions, Plaid is very likely the bridge involved.)

"Read-only" is the whole point

This is the part that matters most, and the part most people never have explained to them.

The kind of connection apps use for accounting, budgeting, and transaction import is read-only. That means the app can:

• See your account balances and transaction history.

And it explicitly cannot:

• Move money out of your account.
• Make payments or transfers.
• Change your account details.

Reading data and moving money are two completely different permissions on two different tracks. An app importing your transactions for bookkeeping is looking through a window, not holding a key. That distinction is designed in, not a promise you have to take on faith.

Is Plaid safe?

No connection is risk-free, but the design is built to minimise what can go wrong.

• Bank-grade encryption. Data in transit and at rest is encrypted to the standards banks themselves use.
• You are not sharing your password with the app. In the modern flow, you authenticate with your bank, and the app receives a revocable token — not your banking credentials. The app never sees your password.
• Scoped access. The app receives only the data types you permit, and read-only access cannot be silently upgraded into the ability to move money.
• Revocable. You can cut the connection at any time (more on that below), and access ends.

The reason apps as large and regulated as major payment and banking brands rely on Plaid is precisely this security posture — they would not route their customers' bank connections through something they did not trust.

What data is actually shared

It is fair to want specifics before you connect anything. Typically an app requests some combination of:

• Account and balance information — which accounts exist and what is in them.
• Transaction history — dates, amounts, and merchant descriptions, so the app can categorise and reconcile.
• Basic identity or account-verification details — sometimes, to confirm the account is yours.

Crucially, you see what is being requested at the moment you connect, and a good app only asks for what it genuinely needs. If a simple bookkeeping tool asks for far more than transactions, that is your cue to pause.

How to disconnect

Access is not permanent, and you hold the off switch — in more than one place:

1. In the app. Any reputable app that connected your bank provides a way to disconnect or remove the linked account in its settings.
2. At Plaid. Plaid operates a portal (my.plaid.com) where you can see which apps you have connected through it and revoke any of them.
3. At your bank. Many banks also list third-party connections and let you cut them from your side.

Once revoked, the app stops receiving new data. It is a good habit to periodically review your connections and remove any for apps you no longer use.

How KAZI uses it

For KAZI's financial and bookkeeping features, bank connections do exactly one job: read-only transaction import. If you (or clients whose books you keep) bank in a Plaid-supported region, connecting an account lets KAZI pull in transactions automatically so your income and expenses categorise themselves instead of being typed in by hand at tax time.

To be explicit about the boundary: KAZI's bank connection reads transactions to help with bookkeeping. It does not, and by the nature of read-only access cannot, move your money. Payments in KAZI happen on a separate, deliberate track through dedicated payment processors — never silently through a data connection.

The takeaway

"Connect your bank" sounds scarier than it is once you know the shape of it: a secured bridge, read-only by design, sharing only the data you approve, revocable whenever you like. Understanding that is what lets you use the genuinely useful features — automatic bookkeeping chief among them — without giving up control.

KAZI puts that automatic bookkeeping alongside your invoicing, projects, and clients in one platform. We are in early access: join the waitlist at kazii.ai and let your transactions file themselves.