🔍 Read the full analysis: A Practical Guide To Safe Money Handling With AI Agents on ThorstenMeyerAI.com
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Bank of America has warned customers not to share banking credentials with AI tools, saying customers may be responsible for activity resulting from that access. The report recommends narrower permissions, payment approvals and spending limits, while noting that how existing consumer protections apply to AI agents has not been tested by courts or regulators.
Bank of America warned customers this week not to give banking usernames or passwords to AI assistants, saying customers who share credentials are responsible for activity resulting from that access. The warning comes as financial firms discuss agent-driven payments and trading, raising questions about how customers can authorize useful tasks without giving software broad control of their accounts.
The bank’s email, titled “Protecting your finances in the AI World,” says login details should not be shared with another person or an outside service, including an AI-enabled tool or agent acting on a customer’s behalf. Bank of America also said it is “excited about what AI responsibly used can deliver.” A customer posted the email on Bluesky; TechCrunch reported on it October 27, and a bank spokesperson confirmed its authenticity to the publication.
The source report says Visa told investors on the same Tuesday that trust is a major barrier to agents making purchases. Robinhood said customers had put more than $250 million into accounts used by AI agents. That figure is a reported amount, not a measure of agent trading performance or losses. Robinhood’s separate accounts and spending limits do not settle responsibility: the company reportedly says customers “assume all risk” for trades made by their agents.
The practical distinction is between giving an agent a full login and granting it limited authority for a specific task. Options described in the source include read-only access, approving each payment, virtual cards with spending caps, tokens restricted by merchant, amount and time, or a separate account with funds set aside for the agent. These controls can constrain access, but they do not by themselves establish who is legally liable if something goes wrong.
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
Limiting an Agent’s Access to Funds
A bank password can act as a master key: an agent using it may appear to the bank as the account holder and could potentially do more than the task the customer intended. That creates risks both when an agent makes an unwanted transaction and when a bank interprets its activity as suspicious and restricts the account.
The warning matters because customers may assume that a payment they did not personally approve will automatically qualify for the same protections as a stranger’s fraud. The source report says that assumption may be unsafe when the customer gave an agent access. Technical safety rails and legal responsibility are separate questions; a spending cap may limit a loss without determining who must bear it.
For consumers, the immediate implication is to check what permissions a service requests and what its terms say before connecting an account. For firms building payment agents, the issue is how to make authority narrow, visible and revocable, rather than relying on a customer’s broad credentials.
Popular right now
Roborock Q7 M5+ Robot Vacuum and Mop
Ninja Specialty Coffee Maker CM401, 10-Cup Carafe, Fold-Away Frother, Black
Samsung 42-Inch Class OLED S90F 4K Smart TV (2025)
As an affiliate, we earn on qualifying purchases.
Bank Warnings Meet Agent Payments
The report places the email amid growing use of AI systems that can take actions, rather than only answer questions. On October 22, Axios reported, citing unnamed sources, that major U.S. banks were finding third-party AI agents inside customer accounts, often signed in with customers’ own passwords. According to that report, banks could have difficulty determining whether the activity was authorized by the customer.
The legal discussion remains unsettled. In the United States, the source cites Regulation E’s exclusion for transfers initiated by someone given access to an account by the consumer. The author’s view that this could apply to an AI agent is an interpretation, not a court or regulator ruling. In the European Union, the Payment Services Directive requires customers to take reasonable steps to keep personalised security credentials safe; whether giving credentials to an AI agent meets the standard for gross negligence has not been tested in court, according to the source.
Liability Rules Remain Untested
No court or regulator ruling cited in the source determines whether providing a bank password to an AI agent counts as furnishing account access under U.S. rules, or whether it could amount to gross negligence under EU rules. The article’s application of those provisions to AI is the author’s reading and is not legal advice.
It is also not clear from the reported material how common agent access to bank accounts is, how many transactions have caused customer losses, or how each bank will distinguish an authorized agent from a malicious actor. The reported $250 million at Robinhood does not answer those questions. The detailed terms, limits and dispute processes for different agent-payment products may vary.
Check Permissions Before Connecting
Customers considering an AI service for financial tasks can review whether it requests a password or a narrower authorization, whether payments require approval, and whether limits can be set by amount, merchant and duration. They should also read the provider’s terms on losses, disputed transactions and responsibility before enabling autonomous activity. A separate, limited account can reduce exposure, but does not guarantee reimbursement.
Financial firms and regulators may provide more detail as agent payments develop, including how access should be authorized and how disputes will be handled. For now, the bank’s warning is clear, but the legal consequences of sharing credentials with an AI agent remain unresolved.
Key Questions
What did Bank of America tell customers?
The bank said customers should not share their usernames or passwords with outside services, including AI tools and agents. It also said customers are responsible for activity resulting from access they share.
The source report says this has not been resolved by a court or regulator. How existing rules apply may depend on the circumstances and jurisdiction.
What is a safer way to let an AI agent handle a payment?
Consider narrower permissions, such as read-only access, approval for each payment, a capped virtual card, or a token limited to a merchant, amount and time period. Check the service’s terms as well.
Does a spending limit guarantee that I will get my money back?
No. A spending limit can restrict how much an agent can spend, but it does not determine who is liable for a disputed transaction or guarantee reimbursement.
Source: ThorstenMeyerAI.com
