Enable Banking (open banking)

The Enable Banking integration gives your pipelines a read of bank accounts and transactions via European open banking (PSD2 / AIS). It is the ideal fuel for a treasury agent or a CFO IA.

What you can do with it

• List the available banks and open a consent session to a bank.
• List the authorized accounts and fetch their transactions.
• Produce a deterministic treasury snapshot, broken down by currency, usable by an agent.

All capabilities are read-only: Enable Banking does not allow initiating a payment from betool.

Tools and nodes

• Read tools: enablebanking.list_banks, enablebanking.list_accounts, enablebanking.get_transactions, enablebanking.report.
• enablebanking_report node — computes a deterministic treasury position per currency (balances, inflows, outflows, net flow, per-account breakdown) over a window of 7 days to 12 months, and publishes it into the context (the agent only rephrases it, never derives it itself).

Connection (BYO)

The connector works in two layers, both under Settings → Services → Enable Banking, Accounts tab:

1. Application account — your Enable Banking application_id, the environment (production or sandbox) + an RSA private key (the platform signs each call with a JWT RS256; the key is never shown again).
2. Consent sessions — Connect a bank starts, for each bank, a consent flow protected against CSRF; access is bounded to the accounts you have explicitly authorized. Bank consent expires (about 90 days): the bank must then be reconnected.

The host is locked to the Enable Banking API. Depending on your configuration, betool can route through a shared vendor account (resolution your account > shared account).

Use cases

• Treasury briefing — every Monday, a CFO IA reads the week's balances and movements and sends a summary per currency.
• Threshold alert — a scheduled pipeline flags any balance dropping below a defined floor.