🔍 Read the full analysis: Let An AI Agent Handle Routine Money Tasks With Care on ThorstenMeyerAI.com
Get privacy and security gear delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
Bank of America has warned customers not to give banking passwords to AI-enabled tools, saying customers are responsible for activity resulting from shared access. The warning comes as AI agents begin handling financial activity, but the legal responsibility for an agent’s actions remains unsettled.
Bank of America has warned customers not to share their banking usernames or passwords with AI assistants or agents, saying customers remain responsible for activity resulting from that access. The warning, confirmed by the bank to TechCrunch after a customer posted the email, comes as financial firms discuss trust and risk around AI-powered payments and trading.
The email, titled “Protecting your finances in the AI World,” says credentials should not be given to another person or an outside service, including an AI-enabled tool that acts on a customer’s behalf. It adds that people who share their credentials are responsible for activity resulting from that access. Bank of America also said it is “excited about what AI used responsibly can deliver.”
The warning highlights a practical problem: an agent logging in with a customer’s password may appear to the bank as the customer, or as someone who has stolen the password. That can make it harder to distinguish an approved action from fraud, and could lead to disputed transactions or account restrictions. The source material does not establish how often either outcome has occurred.
Other recent developments point to agents’ growing role in finance. Visa told investors that trust is a major barrier to AI agents making payments, while Robinhood said customers had placed more than $250 million into accounts that AI agents trade. The source does not specify the period for that figure, so it should be treated as a reported amount, not a rate of growth. Robinhood’s separate account structure and spending limits also do not remove its stated liability caveat: customers “assume all risk” for agent trades.
Before your agent touches money
Give it a valet key, not the master key
Logging in with your password makes the agent you. A credential made for the agent can do only the job you gave it, and you can take it back.
- What it opensEverything you can do: transfers, payees, settings, statements
- LimitsNone that the agent cannot get around by logging in as you
- What the bank seesYou, or a thief. It cannot tell which
- If a web page tricks itThe trick reaches your whole account
- To take it backChange your password everywhere it was used
- If money goes missingUS rules can exclude transfers by someone you gave access to; Bank of America: “you’re responsible”
- What it opensOnly what you allowed: read-only, one card, one pot of money
- LimitsBuilt in: amount, merchant, time window, approval on your phone
- What the bank seesAn identified agent acting for an identified person
- If a web page tricks itThe damage stops at the limit
- To take it backDisconnect the agent or delete its card. Your password never moved
- If money goes missingDepends on the terms. Read them first: some still put all risk on you
A comparison of two set-ups, not a measurement. Which limits exist depends on your bank, card and app.
Sources: Bank of America customer email, confirmed to TechCrunch (27 Oct 2026); 12 CFR 1005.2(m); OWASP LLM01. Comparison: Thorsten Meyer.
Powered by Thorsten Meyer AI
Why Password Access Changes the Risk
A banking password is a broad credential, not a narrow permission for one task. If an agent uses a customer’s login, it may gain access well beyond a single intended payment. That creates risk if the agent misunderstands instructions, takes an action the user did not expect, or is steered by hostile material it reads online.
There is also a dispute over who bears the loss. The source article describes US Regulation E as excluding certain transfers initiated by someone who was given account access by the consumer. It also notes that applying this provision to an AI agent or its operator is an interpretation, not a settled legal ruling. In the EU, payment rules require customers to protect their personalised security credentials; whether sharing them with an AI agent amounts to gross negligence has not been tested in court, according to the source.
For customers, the immediate implication is to read the permissions and liability terms before connecting an agent to an account. For companies building payment agents, it is a design challenge: useful automation must be paired with limits that reduce the consequences of mistakes and make authorization clearer.
Products Worth Considering
DJI Osmo Pocket 3 Filter Bundle – Vlogging Camera with 1 CMOS Sensor and 4K/120fps
Jackery Solar Generator 1000 v2 with 200W Solar Panel
Amazon Kindle Scribe Colorsoft 64GB (1st Generation)
As an affiliate, we earn on qualifying purchases.
Banks Face Ambiguous Agent Logins
Bank of America’s email follows an October 22 Axios report, citing unnamed sources, that major US banks were finding third-party AI agents inside customer accounts, often using customers’ own passwords. The report said banks could have difficulty determining whether such activity reflected a customer’s instructions. This is a reported account of banks’ concerns, not a public count or a finding about every bank.
One concern is prompt injection: text embedded in a webpage, email, invoice or file may try to redirect an AI system’s behavior. The source identifies this as a leading risk in OWASP’s AI application risk list. That does not mean every agent will be manipulated, but it shows why giving an agent unrestricted account access could magnify the effect of a failure.
Safer approaches described in the source include read-only access, requiring approval for each payment, using a virtual card with a spending cap, issuing a token limited to a particular merchant, amount and time period, or placing funds in a separate account. These controls narrow what an agent can do; they do not, by themselves, determine who is legally responsible when something goes wrong.
““If you do share your credentials, keep in mind that you’re responsible for activity resulting from that access.””
— Bank of America, in its customer email
Liability Rules Remain Untested
No court or regulator ruling is identified in the source that settles how existing consumer-protection rules apply when an AI agent uses credentials supplied by its customer. The source’s readings of US and EU rules are presented as interpretations, not legal advice or established outcomes. The terms customers may face can also differ by bank, agent and account type.
It is also unclear how widespread bank encounters with unauthorized or disputed agent activity are. The Axios account cited unnamed sources, and the material provides no industry-wide figures. Robinhood’s reported $250 million figure lacks a stated time window in the source, and the exact protections available to customers using different agent-payment systems are not fully detailed.
Check Permissions Before Connecting
Customers considering financial automation can review the provider’s permissions and liability terms before linking an account, and favor controls such as read-only access, transaction-by-transaction approval, low spending limits or a separate balance. A password that gives an agent the same access as its owner is broader than necessary for many routine tasks.
Banks, payment networks and agent providers will need to clarify how authorization is recorded, what transactions customers can challenge, and who is responsible when an agent acts unexpectedly. The source material does not identify a specific upcoming rule, product change or deadline. For now, the confirmed development is a bank warning; the limits and protections governing AI agents’ financial activity remain unsettled.
Key Questions
What did Bank of America tell customers?
It warned customers not to share banking usernames or passwords with people or outside services, including AI-enabled agents, and said customers are responsible for activity resulting from shared access.
Does giving an AI agent a password make the customer liable for every transaction?
The source does not establish a universal legal answer. It describes relevant US and EU rules but says applying them to AI agents has not been settled by a court or regulator in the situations discussed.
What are safer ways to let an agent handle a payment?
Options described in the source include read-only access, approving each payment, using a virtual card with a spending cap, limiting a token to a merchant and amount, or keeping agent-accessible funds in a separate account.
What is prompt injection?
It is an attempt to steer an AI system through instructions placed in material it reads, such as a webpage, email or file. The source identifies it as a key risk for AI applications.
Are banks already seeing AI agents in customer accounts?
An October 22 Axios report, citing unnamed sources, said major US banks were finding third-party agents in customer accounts, often logged in with customers’ passwords. The source provides no industry-wide count, and the report does not establish how common the activity is.
Source: ThorstenMeyerAI.com
