🔍 Read the full analysis: How To Delegate Money Tasks To AI Without Sharing Credentials on ThorstenMeyerAI.com
Prime made for students and young adults
- Fast, free delivery for dorm and study essentials
- Prime Video and Amazon Music included
- Member-only deals
TL;DR
Bank of America has warned customers not to share banking usernames or passwords with AI agents, saying customers are responsible for activity resulting from shared access. The source article recommends limited permissions, payment approvals and capped funds instead, while noting that how existing consumer-protection laws apply to AI agents has not been tested in court.
Bank of America has warned customers not to give their banking usernames or passwords to AI-enabled tools, saying customers who share credentials are responsible for activity resulting from that access. The warning, confirmed as authentic by a bank spokesperson to TechCrunch, comes as financial firms and customers explore AI agents that can handle payments or trades.
The bank’s 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 agent acting on a customer’s behalf. It also says the bank is “excited about what AI used responsibly can deliver.” TechCrunch reported on the email on October 27 after a customer posted it on Bluesky.
The source article says the warning is part of a broader concern about agents logging into financial accounts with customers’ own passwords. Axios reported on October 22, citing unnamed sources, that major U.S. banks were encountering unauthorized third-party AI agents inside customer accounts. Banks may have difficulty distinguishing activity directed by a customer from activity the customer did not intend, according to that report.
The source article points to narrower ways to delegate: read-only access, requiring approval for each payment, a virtual card with a spending cap, a token restricted to a specific merchant, amount and time window, or a separate account with limited funds. Those controls can limit what an agent can do, but they do not by themselves establish who is legally responsible 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
Why Account Access Changes the Risk
A password can give an agent access far beyond the single task a customer wants done. If an agent logs in with the customer’s credentials, the bank may see activity that appears to come from the customer—or may treat it as suspicious activity and restrict access. That creates practical risks alongside the possibility of an unwanted payment or trade.
Consumer protections may also depend on how access was granted. The source article cites U.S. Regulation E, which excludes some transfers initiated by a person given access to an account by the consumer. It also cites EU payment rules requiring customers to take reasonable steps to protect personalised security credentials. How these provisions apply to AI agents remains legally unsettled, according to the article; no court or regulator ruling on that specific question is identified.
For readers, the distinction is between giving software a master credential and granting a tightly bounded permission. Limits and approval steps can reduce the amount an agent can move or the actions it can take. They do not guarantee reimbursement or remove the need to understand the service’s terms.
Popular right now
Apple AirPods Pro 3 Wireless Earbuds
Ninja Flip Toaster Oven & Air Fryer, 8-in-1, Stainless Steel, SP151
Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Black
As an affiliate, we earn on qualifying purchases.
Banks Confront Agent Logins
The warning arrives as financial services begin to intersect with autonomous software. The source article says Visa told investors on the same Tuesday that trust is a major barrier to AI agents making payments. It also reports that Robinhood said customers had put more than $250 million into accounts that AI agents trade. These are separate developments and do not establish that every agent has direct access to customers’ bank credentials.
According to the source article, Robinhood has built a separate account and spending limits for its AI-agent trading feature, but the company says customers “assume all risk” for trades made by agents. The example illustrates why technical safeguards and financial liability are separate questions: a spending limit can constrain activity, while the service’s terms still determine what the provider says about responsibility.
Another risk is prompt injection: instructions hidden in web pages, emails or files that may influence an agent reading them. The source article identifies this as a leading AI application risk in OWASP’s list. The practical implication is that an agent given broad financial access may encounter content designed to redirect its actions, even when the user’s original request was limited.
““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 on whether giving an AI agent banking credentials triggers the cited U.S. or EU legal provisions is identified in the source article. The article’s interpretation of Regulation E and the EU Payment Services Directive is the author’s reading, not a legal determination. Whether a particular transfer qualifies as unauthorized, or whether a customer’s conduct affects protection, will depend on applicable law and the facts.
It is also unclear how widely banks are seeing agent logins or what steps each institution is taking. The October 22 account cited by Axios relies on unnamed sources, and the source material does not provide figures for affected customers or transactions. Bank of America’s email states its position on credential sharing, but the material does not describe a new technical system for safely authorizing agents.
Limits, virtual cards and scoped tokens can narrow access, but the source does not compare specific providers or independently verify how their controls work. Customers should not assume that a safety feature guarantees reimbursement or prevents every unwanted action.
Check Permissions Before Connecting
Before connecting an AI service to a financial account, customers can review what permissions it requests, whether access is read-only, and whether each payment requires approval. If a payment method is needed, a capped virtual card or a separate account with limited funds may restrict potential losses compared with sharing a primary account password. Customers should also read the provider’s terms to see how it describes responsibility for agent activity.
The source material does not give a date for new bank rules, a regulatory decision or a common standard for agent payment access. The next developments to watch are how banks define and detect third-party agents, what permission controls financial services offer, and whether regulators or courts clarify how existing consumer protections apply. Until then, sharing a password gives an agent broad access, while the legal and financial consequences of that choice remain uncertain.
Key Questions
What did Bank of America tell customers?
It warned customers not to share banking usernames or passwords with other people or outside services, including AI-enabled tools and agents. The bank said customers are responsible for activity resulting from shared access.
What is a safer way to let an AI handle a money task?
The source article suggests options with narrower permissions, such as read-only access, approval for every payment, a virtual card with a spending cap, a token restricted by merchant and amount, or a separate account holding limited funds. Availability depends on the service.
Does sharing a password mean a customer loses fraud protection?
That is not settled for AI agents. The source article discusses U.S. and EU rules that may make credential sharing relevant to liability, but says the specific application has not been tested in court. The result may depend on the facts and applicable law.
Can an AI agent be influenced by a web page or email?
Yes. The source article describes prompt injection, in which instructions in content an agent reads may influence its actions. It recommends limiting an agent’s access rather than relying on its ability to ignore every unsafe instruction.
Do spending limits guarantee that customers will be reimbursed?
No. Limits may constrain an agent’s actions, but they do not establish who is liable for a loss. Customers should review the service’s terms and the permissions they grant.
Source: ThorstenMeyerAI.com
