Skip to main content

​
The idea: you hold the key, AI2Fin only reads

AI2Fin’s bank feeds are bring-your-own. You connect your bank at a provider you choose — or at the bank itself, where it publishes an API — and hand AI2Fin a read-only key or token. AI2Fin never sees a banking credential, has no payment surface to misuse, and you revoke access at the provider without asking us. That shape has two consequences worth knowing before you pick:
  • Coverage is per provider, not per app. Your bank is reachable if one of the providers below reaches it. Search by bank or country on the Connectors page and it tells you which.
  • Where the key lives decides where the feed can run. A token that a bank licenses for your personal use can live on your own machine — the desktop app or a single-tenant self-hosted instance — but not on a server we operate. So some feeds are desktop-only, and that is a licence fact, not a missing feature.

Open Connectors

Type your bank or country. The matching option opens; anything unmatched falls through to a statement file, spreadsheet or CSV — which work for every bank on earth.

​
Coverage by country

Country reach is what each provider states on its own site. It means the provider operates there, not that every institution in that country is supported — only the provider can answer that for a specific bank. The Connectors search is deliberately conservative for the same reason.

​
Where each feed runs

“Desktop app” and “self-hosted” mean the credential stays on hardware you control, which is exactly the case every one of those providers’ terms contemplates. See Deployment options for what each shape is.

​
How a feed behaves once connected

  • First sync reads about 13 months of history (400 days) where the provider offers it. Monzo is the exception — see its page.
  • Then it polls every 15 minutes, the same read the sync button runs. Akahu personal apps refresh about once a day, so that feed is polled less often on purpose.
  • Deduplicated on date, amount, description and account, so the same transaction arriving from two sources is caught and nothing is silently collapsed across accounts.
  • Read-only, always. There is no code path that writes to a bank.
  • Disconnecting keeps what arrived. Those are your records; disconnecting stops new ones.
Bank-fed transactions never leave AI2Fin through Outbound Destinations or webhook automations. Those carry only what you entered, imported from a file, captured from a receipt, or created through the API. Your bank feed stays put.

​
Pick a feed

SimpleFIN

US & Canada via SimpleFIN Bridge; any SimpleFIN-speaking provider, including RedBark.

BankSync

AU, NZ, US, CA, UK, IE, DE, FR, ES, NL from one workspace key.

RedBark

Australian CDR, New Zealand and US banks, through your RedBark account.

Akahu

New Zealand — free personal app, all major banks.

Up

Australia — Up’s own API, no one in the middle.

Starling

UK — Starling’s own API with a personal access token.

Monzo

UK — your own Monzo developer client.

Statement files

OFX / QFX, QIF, CAMT.053, MT940 — no subscription, works offline.

​
Not a live feed, but documented

Kraken

Import Kraken trades and ledgers from CSV for capital-gains treatment.

Any other bank

CSV or PDF statement upload, with column mapping and multi-currency.

​
Security & privacy

No, and it cannot — there is no field in the product that accepts a banking password. Every feed here is a key or token issued by the provider or the bank for read access, revocable there.
The key or token, encrypted at rest. On the desktop app it is sealed with a key held in your operating system keychain and never leaves the machine — see where your data lives. In the cloud it is encrypted in AI2Fin’s database and used only by the sync worker.
Because the provider’s terms say where the credential may live. Up’s Acceptable Use Policy prohibits sharing your token with any third party; Akahu, Starling and Monzo personal credentials are for your own use. On your own machine AI2Fin is software you run, reading your own account — the case those policies contemplate. On our servers it would be us holding your credential, which is a different thing. We would rather say so than blur it.
Yes — it is simply yours, chosen and revocable by you. If that is one party too many, statement files and CSV upload put nobody in the middle.