🔍 Read the full analysis: The Bank Password Rule For AI Agents Handling Money on ThorstenMeyerAI.com
Get everyday essentials 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 warned customers not to share banking credentials with AI tools, saying they are responsible for activity resulting from access they grant. The warning comes as banks grapple with AI agents entering accounts and companies explore agent-led payments, while the legal treatment of agent mistakes remains unsettled.
Bank of America warned customers not to share their usernames or passwords with AI assistants or agents, saying customers who do so are responsible for activity resulting from that access. The warning, confirmed by the bank to TechCrunch after a customer posted the email, arrives as financial firms confront AI agents accessing accounts and as companies test agent-driven payments and trading.
The email, titled “Protecting your finances in the AI World,” says banking credentials “should never be shared with another person or provided to an outside service, including an AI-enabled tool or agent that offers to act on your behalf.” It adds: “If you do share your credentials, keep in mind that you’re responsible for activity resulting from that access.” Bank of America also said it is “excited about what AI used responsibly can deliver.”
A customer posted the email on Bluesky, and TechCrunch reported on it October 27. A Bank of America spokesperson confirmed to TechCrunch that the email was authentic. The warning does not describe a new account feature or a specific breach; it sets out the bank’s position on customers sharing credentials with outside tools.
The source report says that on the same Tuesday, Visa told investors trust is the main barrier to AI agents making purchases. Robinhood said customers had placed more than $250 million into accounts that AI agents trade, while its separate-account structure and spending limits do not remove customer responsibility: the company says customers “assume all risk” for trades by AI agents. These developments illustrate that agent use is advancing even as liability and safeguards remain contested.
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
The Risks of Sharing a Master Key
A banking password can give an AI agent the same access the customer has, rather than permission for one limited task. That creates two distinct risks: an agent could take an action the customer did not intend, and the bank may have difficulty distinguishing authorized automation from stolen credentials. Depending on how the bank responds, the customer could also face an account lockout while activity is reviewed.
There is also a potential financial-liability gap. In the United States, Regulation E excludes certain transfers initiated by someone who was furnished access to an account by the consumer. The source author argues that this language may apply to an AI agent or its operator, but says no regulator or court has ruled on that question. In the EU, PSD2 requires customers to take reasonable steps to keep personalised security credentials safe; whether sharing a password with an AI agent amounts to gross negligence has not been tested in court, according to the source.
These legal uncertainties matter because a customer may assume that an unauthorized transfer will be treated like ordinary fraud. Sharing access with an agent could complicate that assessment. The bank’s email is a clear warning about its position, but it does not by itself settle how consumer-protection rules apply in every case.
Products Worth Considering
Logitech MX Master 4 for Mac, Ergonomic Bluetooth Mouse with Haptic Feedback, Ultra-Fast Scrolling, USB-C Charging, for MacOS, iPadOS, Windo
Bose QuietComfort Wireless Bluetooth Headphones with Active Noise Cancellation, Mic, USB‑C Charging, Deep Bass, 24‑Hour Battery – White Smok
Samsung 27-Inch Odyssey QD-OLED G8 4K 240Hz Gaming Monitor
As an affiliate, we earn on qualifying purchases.
Banks Confront Agent Access
On October 22, Axios reported, citing unnamed sources, that major U.S. banks were finding third-party AI agents inside customer accounts, often using the customers’ own passwords. According to that report, banks can struggle to determine whether the activity reflects a customer’s instructions. Banks have reportedly been blocking some agents and revising terms as they address the problem.
AI agents can read web pages, emails, invoices and other files while carrying out tasks. The source report identifies prompt injection—instructions hidden in material an agent reads—as a security risk, and says OWASP ranks it as the leading risk for AI applications. That creates a concern beyond an agent making an ordinary error: outside content could potentially influence what the agent does with the access it has been given.
The source author recommends limiting an agent’s permissions instead of giving it a banking password. Options discussed include read-only access, requiring approval for each payment, setting a capped virtual card, or using a token restricted by merchant, amount and time. A separate account containing only a limited balance can also limit potential losses. These are proposed safeguards in the source material, not a statement that every bank currently offers them.
“Your username and password “should never be shared with another person or provided to an outside service, including an AI-enabled tool or agent that offers to act on your behalf.””
— Bank of America, in its customer email
Liability Rules Remain Untested
No court or regulator ruling identified in the source material determines whether giving a bank password to an AI agent counts as furnishing an access device under Regulation E, or whether doing so violates a customer’s duties under EU payment rules. Those legal interpretations should not be treated as settled advice.
It is also unclear how widely banks are encountering agent access, which specific tools or account types are involved, and how many disputed transactions have resulted. The Axios account cited unnamed sources, and the source material provides no figures for affected customers or losses. Bank of America’s email does not explain how the bank would handle a particular disputed transaction involving an AI agent.
Watch for Safer Access Controls
The immediate practical step is to avoid giving an AI agent a bank username and password unless the bank and service provide clear, limited authorization methods. Customers considering an agent should check the bank’s terms, the tool’s permissions, whether payments require approval, and who bears losses if the agent acts incorrectly. A spending cap or separate account may reduce exposure, but it does not settle liability.
The next developments to watch are whether banks introduce or standardize restricted access for AI agents, how payment firms address verification and customer approval, and whether regulators or courts clarify consumer responsibility. The source material gives no announced timetable for a ruling or a new industry standard, so the legal and technical questions remain open.
Key Questions
What did Bank of America tell customers?
It said customers should not share banking credentials with another person or outside service, including an AI-enabled tool or agent. The bank said customers are responsible for activity resulting from access they share.
Has a court ruled that customers are liable for an AI agent’s banking activity?
No ruling is identified in the source material. How existing U.S. and EU payment rules apply to AI agents remains uncertain.
Why can sharing a password create a problem?
A password may give an agent broad access, and the bank may see activity under the customer’s credentials as if the customer had logged in. The agent could also be influenced by instructions hidden in content it reads.
What are safer alternatives to sharing a bank password?
The source report suggests restricted, read-only access; approval for each payment; a capped virtual card; a token limited by merchant, amount and time; or a separate account with limited funds. Availability varies, and these safeguards do not necessarily determine who bears losses.
Source: ThorstenMeyerAI.com
