A US 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.
US institutions commonly use Plaid. Large banks may hand the user to a bank-hosted OAuth page; other institutions may complete authentication inside Plaid’s secure window. In both cases, the user chooses which accounts to share.
US coverage is broad, but it is not identical across every product at the same bank. A retail checking account may be available while a business card, co-branded card or brokerage arm is not. BankSync’s institution card shows the account-type tags available for that specific connection.
This guide covers the United States-specific connection, the Claude setup, the checks to run after authorisation and the limitations to keep in mind.
Accounts and balances
List supported US 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 US 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 institution’s Plaid or bank-hosted authorisation flow. Account selection also happens there. Tick only the accounts needed for the Claude workflow.
Connect a US 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 Plaid connection
Follow the institution’s Plaid or bank-hosted authorisation flow, 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 US 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.
Re-authentication is event-driven: a password change, MFA challenge or institution-side connection update can require the user to reconnect.
Common US connection issues
| Issue | What it usually means | What to do |
|---|---|---|
| Large-bank OAuth | The bank opens its own sign-in and approval page. | Complete the bank-hosted flow and return to BankSync. |
| Business card missing | The issuer may not expose that product through its data-sharing layer. | Reconnect to review the account picker; if absent, the product is not available. |
| Investment account absent | The retail bank connection may not expose brokerage data. | Search for the brokerage entity and connect it through SnapTrade where supported. |
| Login or MFA loop | The institution may be waiting for a verification step or imposing a temporary lockout. | Confirm the login on the bank’s site, allow pop-ups and retry after any lockout. |
| Connection needs attention | Plaid or the bank requires fresh authentication. | Use Reconnect / Add Accounts from the bank card. |
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 US accounts
| Goal | Prompt | Verification |
|---|---|---|
| Cash position | Show current and available balances for every US checking and savings account, with timestamps. | Confirm every expected account is present. |
| Credit-card review | List card purchases and payments separately for the last complete month. | Ensure payments are not counted as spending. |
| Recurring charges | Find recurring USD charges and show the evidence for each cadence. | Check merchant, dates and amounts. |
| Loan summary | List supported loan balances, rates and payment fields, and state what is missing. | Compare with the lender statement. |
| Portfolio concentration | Summarise supported US investment holdings by account and calculate position concentration. | Check valuation time and excluded accounts. |
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 US ChatGPT guide.
US bank accounts and Claude: FAQs
Sources and further reading
The bottom line
The reliable way to connect a US 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.