Enable Banking: what this connector can do

Member·4 minutes to read

What this page is for

docs/connectors/enable-banking.md is the setup guide for whoever runs your organisation's Botseon deployment — creating the vendor application and entering its credentials. This page is the other half: what Enable Banking actually lets a bot do once it is connected to your account, what it asks you for along the way, its limits, and how to take the connection away again, in Botseon and at Enable Banking.

Read balances and transactions of your bank, card and investment accounts. Read-only: it can never move money.

What a bot can do with it

Read — Enable Banking tells a bot things, nothing changes

Tool	What it does
`enable-banking.list_accounts`	List the accounts this bank consent covers, with the institution, the kind (current, card or investment) and the currency.
`enable-banking.get_balances`	Read one account’s balances, with their type and the time they are as of.
`enable-banking.list_transactions`	List one account’s booked and pending entries in a date range.
`enable-banking.get_account_details`	Read one account’s own details: holder name, masked identifier, product and currency.

Write

This connector has no write tools. A bot can only read through it.

The permissions it asks for, in plain words

Every call a bot makes through this connector is tagged with what kind of thing it is. Only the tags below ever apply here — a tag this connector's tools never carry is not listed, because it can never ask you for it.

read — Looks something up. Nothing changes, and nothing is sent anywhere. A bot never has to ask first for this.

Limits

Read balances and transactions of your bank, card and investment accounts. Read-only: it can never move money. Nothing outside that list is possible through this connector, however a bot is asked to use it.

Enable Banking is also only ever as wide as the consent you give at your own bank: you choose the accounts to share on your bank's own page when you press Authorise, and the consent lapses after at most 90 days. The deployment's side of the setup is on the operator's page, docs/connectors/enable-banking.md.

Once you are connected, Linked accounts under the connection lists each account you chose at your bank, by its name and kind. A bot can read those accounts and no others: asked for any other account, even one at the same bank, it is refused before anything is sent to Enable Banking.

If the bank picker says Bank linking is not available here yet., nothing is wrong with your account or your bank: whoever runs your deployment has not registered its Enable Banking application yet. Ask them — the steps are in the first real link.

Disconnecting

In Botseon

Open Plugins from the sidebar, press this connector's card to open its detail page, and under Accounts press Remove next to the account — or Uninstall to remove the plugin and every account connected to it at once. Either one revokes the stored connection immediately: nothing more is read or changed through it from that moment on. Install a plugin walks through the same screen step by step.

At Enable Banking and your bank

The authorisation behind this connector is a consent you gave your bank through Enable Banking's hosted flow. Disconnect bank on the account, or removing the account, in Botseon deletes that consent at Enable Banking first, which ends it at your bank, and only then clears it here.

If that delete does not succeed, Botseon tells you so: the account is removed here either way, but the consent may still stand at your bank. Withdraw it in your bank's own app or online banking.

What Botseon keeps, and how your data is used

Whatever a bot reads or writes through this connector becomes part of your conversations and the record of that run — the same records, and the same retention schedule, as everything else a bot works on. Botseon is the processor for that content; your organisation decides what it may read and remember, and can delete it sooner than the schedule would on its own.

Your data is sent to a model provider only to produce the bot's answer, and for nothing else — it is not used to train any model. The Privacy Policy's Models and How long we keep it sections have the full detail, including exactly how long each kind of record is kept for.