A UK bank account does not connect to Claude by sharing a password or uploading a screenshot. The secure path has three layers:
- the bank or provider authenticates the account holder;
- BankSync receives the financial data the user approves; and
- Claude calls authorised BankSync tools when a question needs that data.
UK institutions connect through Salt Edge, an FCA-authorised Account Information Service Provider, under UK Open Banking. The user reviews read-only access on the bank’s own pages and chooses the accounts covered by the consent.
Personal and business banking are often separate institutions. “HSBC” and “HSBC Business”, for example, may be different results with different consent flows. Choose the entity that actually holds the account rather than the most familiar brand name.
This guide covers the United Kingdom-specific connection, the Claude setup, the checks to run after authorisation and the limitations to keep in mind.
Accounts and balances
List supported UK accounts and current or available balances with currency and timestamps.
Transactions
Query a defined date range, merchant descriptions, amounts and provider-supplied categories.
Investments and loans
Review supported holdings, trades or liabilities where the institution exposes those data types.
Controlled access
The bank connection is read-only. MCP configuration actions still depend on the BankSync scopes authorised.
Before you start
You need:
- a BankSync workspace on Standard or above;
- access to the UK online-banking login and its verification method;
- a supported institution and account type;
- a Claude account that can use connectors; and
- authority to share the account data with the Claude account or organisation involved.
Confirm that you can sign in to the institution directly before starting. A bank-side lockout or unfinished verification challenge will also stop the provider connection.
Connect the bank first
BankSync uses one institution search across regions. Search the full bank name, inspect the country and provider on the result card, and choose the exact personal, business or investment entity that holds the account.
Authentication happens through the UK Open Banking consent flow on the bank’s own pages. Account selection also happens there. Tick only the accounts needed for the Claude workflow.
Connect a UK bank account to Claude
Open Banks in BankSync
Select Connect a new bank and search the institution’s full name. Check the country, provider and account-type tags before choosing a result.
Complete the Salt Edge connection
Follow the UK Open Banking consent flow on the bank’s own pages, finish every MFA or approval step and select only the accounts you intend to use.
Confirm the bank is active
Return to BankSync and check that the institution appears as an active bank card with the expected accounts attached.
Open BankSync in Claude’s Connectors Directory
In Claude, find the BankSync connector, review its details and select Connect. Organisation owners may need to enable the connector first on Team or Enterprise.
Authorise the correct BankSync workspace
Sign in to BankSync, choose the intended workspace and review the requested access. Do not use a personal workspace for a business or client workflow.
Verify with a narrow question
Ask Claude to list the UK accounts it can access, including type and currency. Compare the result with the BankSync Banks page before asking broader questions.
What the connection can and cannot do
Depending on the institution and account type, Claude can use BankSync to retrieve supported transactions, balances, holdings, trades and loans. It can also inspect BankSync workspaces, feeds and sync jobs when the connector authorisation includes those tools.
The connection does not guarantee every field at every institution. The bank and provider determine the available history, account products and refresh behaviour. Claude should state missing data instead of filling gaps.
Claude cannot use the BankSync bank connection to transfer money, pay bills, change bank settings or place trades.
UK Open Banking access commonly requires reconfirmation on a rolling cycle, often around 90 days. BankSync displays the expiry date and a renewal prompt before the consent lapses.
Common UK connection issues
| Issue | What it usually means | What to do |
|---|---|---|
| Wrong bank entity | Personal and business services may be listed separately. | Choose the exact entity that holds the accounts. |
| Consent is expiring | The Open Banking authorisation is approaching its reconfirmation date. | Use Renew now and re-approve on the bank’s page. |
| Accounts disappear after renewal | An account was not re-selected during the fresh consent. | Renew again and tick every account that should remain shared. |
| Transaction history is shorter than expected | The bank controls the available history window. | Use older statements for periods the bank does not expose. |
| Bank not found | The service may be listed under a parent brand or legal name. | Search the parent brand and filter to United Kingdom. |
Start with the institution and consent state before changing anything in Claude.
Prompts that are useful and easy to verify
A good first workflow is narrow, date-bound and reversible. Ask Claude to show the evidence behind a categorisation or pattern. Treat a generated summary as analysis, not as a bank statement or professional financial advice.
Example Claude prompts for UK accounts
| Goal | Prompt | Verification |
|---|---|---|
| Cash position | Show current and available GBP balances across all connected current and savings accounts. | Check currency and account coverage. |
| Monthly outflows | Summarise non-transfer outflows for the last complete calendar month. | Exclude transfers and card repayments. |
| Direct debits | Identify repeating direct-debit patterns and show supporting transactions. | Confirm cadence and merchant evidence. |
| Business review | Compare inflows and outflows for the authorised UK business workspace only. | Ensure no personal workspace is included. |
| Consent check | List the connected UK banks and identify any BankSync connection requiring attention. | Confirm against the Banks page. |
Availability depends on the institution, account type and permissions granted to BankSync.
Security checklist
- Never paste an online-banking password, one-time code or full account number into Claude.
- Connect only the accounts required for the task.
- Use separate BankSync workspaces for personal, business and client entities.
- Turn on multi-factor authentication for Claude, BankSync and the bank.
- Review the connector permissions before authorising.
- Verify important totals against the institution.
- Remove the Claude connector and revoke the underlying bank connection separately when access is no longer needed.
For a platform-wide explanation, see how to connect Claude to a bank account. If your team uses ChatGPT instead, see the UK ChatGPT guide.
UK bank accounts and Claude: FAQs
Sources and further reading
- BankSync: connecting UK banks
- BankSync: managing UK Open Banking consents
- BankSync: MCP server guide
- Anthropic: use connectors in Claude
The bottom line
The reliable way to connect a UK bank account with Claude is to keep authentication at the institution, keep the financial connection read-only and give Claude controlled access through BankSync.
Connect the exact institution and accounts you need, authorise the correct BankSync workspace, then verify one narrow answer before relying on broader analysis.