🔍 Read the full analysis: Don’t Give Your AI Agent Your Bank Password. A Simple Guide To Letting It Handle Money Safely on ThorstenMeyerAI.com
Get the latest gadgets 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 share banking passwords with AI assistants, saying they are responsible for activity resulting from that access. The warning comes as banks report concerns about third-party agents entering accounts and as financial firms explore agent-led payments and trading. Safer approaches can limit what an agent may see or spend, but legal responsibility and protections remain unsettled.
Bank of America has warned customers not to give their banking usernames and passwords to AI assistants, saying customers who share credentials are responsible for activity resulting from that access. The warning, confirmed by the bank to TechCrunch after a customer posted the email, comes as banks and payment companies confront AI agents that can access accounts or make transactions.
The email, titled “Protecting your finances in the AI World,” says 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.”
TechCrunch reported the message on October 27 after a customer posted a screenshot on Bluesky; a Bank of America spokesperson confirmed the email was authentic. Separately, Axios reported on October 22, citing unnamed sources, that major U.S. banks had found third-party AI agents accessing customer accounts, often with the customer’s own password. The report said banks may struggle to tell whether such activity is authorized by the customer.
The source report also points to developments elsewhere in finance: Visa told investors trust is a major barrier to AI agents making payments, while Robinhood said customers had put more than $250 million into accounts that AI agents trade. Those statements indicate growing use and interest, but they do not establish that all such agents have the same permissions, safeguards or legal treatment.
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 Account Access Changes the Risk
A password can give an agent the same broad access a customer has, rather than permission for one defined task. That can expose money and account information to mistakes, misuse or instructions planted in material the agent reads. The central risk is not simply whether an agent can act, but whether its access can be limited and whether a customer can distinguish its actions from their own.
Bank of America’s warning also puts responsibility in focus. The source article interprets U.S. and European payment rules as potential risks for customers who deliberately give software access, but says no court or regulator has settled how those rules apply to AI agents. The warning is not a legal ruling, and its wording does not by itself determine whether a bank must reimburse a particular loss.
For consumers, that uncertainty matters before linking an agent to an account or enabling payments. For financial firms, the challenge is to support useful automation without treating every password-based login as proof that the account holder personally approved each action.
Products Worth Considering

Apple AirPods Pro (2nd Generation) Wireless Earbuds with USB-C MagSafe Charging Case

Apple MacBook Air 15-inch Laptop with M5 Chip, 16GB Memory, 512GB SSD, Midnight

Kindle Paperwhite Signature Edition 32GB (2024 Model) – Metallic Black
As an affiliate, we earn on qualifying purchases.
From Passwords to Limited Permissions
The source material frames a password as a master key: an agent logging in as the customer may be able to do much more than the single job the customer intended. A bank may see the resulting activity as coming from the customer’s credentials, making it difficult to separate an authorized instruction from a stolen password or an agent acting unexpectedly.
One safer design principle is to give an agent a narrower permission than a full account login. Examples in the source include read-only access, approval before each payment, a capped virtual card, or a token restricted to a merchant, amount and time window. A separate account or pot of money can also limit potential losses. These are suggested safeguards, not evidence that every bank or agent currently offers them.
The source also identifies prompt injection: instructions hidden in web pages, emails or files that may influence an agent as it reads them. It cites the OWASP project’s AI application risk list, but the material does not establish that a particular agent has been manipulated in the banking cases described. The practical point is that access limits can reduce the consequences if an agent is misdirected.
“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
It is not clear how existing consumer-protection rules apply when an account holder gives credentials to an AI agent, or to a service operating that agent. The source article offers its own reading of U.S. Regulation E and the EU Payment Services Directive, while explicitly saying the relevant application to AI has not been tested in court, as far as its author could determine. Those interpretations should not be treated as legal advice.
The underlying bank reports also leave questions open: the source material does not identify the banks, agents or specific transactions involved in the unauthorized-access report, or say how many customers were affected. It does not specify the full terms of Robinhood’s agent-trading accounts or the exact period covered by the reported $250 million. The safeguards and customer protections differ by product, and the available details do not show how each company handles disputed agent actions.
Watch for Permission and Liability Terms
Customers considering an AI tool for financial tasks should check what access it receives, whether it can move money without approval, and what the provider’s terms say about losses and disputes. Where available, narrow permissions, spending caps and confirmation steps can reduce the amount an agent can do on its own. Consumers should not assume these controls transfer legal responsibility or guarantee reimbursement.
The next developments to watch are how banks describe agent access in their terms, whether payment providers introduce restricted credentials for AI agents, and whether regulators or courts clarify responsibility when software acts using a customer’s authorization. For now, Bank of America’s confirmed email establishes a clear warning from one major bank—not a settled rule for every bank, agent or transaction.
Key Questions
What did Bank of America tell customers?
The bank’s email said customers should not share usernames or passwords with outside services, including AI-enabled tools or agents. It also said customers who share credentials are responsible for activity resulting from that access.
No. The email states the bank’s warning, but it does not resolve how a specific loss would be handled. The source material says the application of relevant U.S. and EU rules to AI agents has not been tested in court, as far as its author could determine.
What is a safer way to let an AI agent handle a financial task?
The source recommends limiting permissions instead of giving an agent a full bank login. Options may include read-only access, approval for each payment, a capped virtual card, or a token restricted by merchant, amount and time. Availability depends on the service.
What is prompt injection?
Prompt injection refers to instructions placed in material an AI agent reads, such as a web page, email or file, that may steer its behavior. The source identifies it as a risk for AI applications; it does not say that prompt injection caused the reported banking activity.
Source: ThorstenMeyerAI.com
