🔍 Read the full analysis: The Safer Way To Put An AI Agent In Charge Of Money Tasks on ThorstenMeyerAI.com
Get the little things that make your day 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 passwords with AI assistants, saying they are responsible for activity resulting from shared access. The warning comes as financial firms grapple with AI agents operating in customer accounts and products that let agents spend or trade. Safer approaches limit access and require approval, but legal responsibility and protections remain uncertain.
Bank of America has warned customers not to give banking passwords to AI assistants, saying customers are responsible for activity resulting from shared access. The warning comes as financial companies report growing use of AI agents for money tasks, raising questions about how to limit what an agent can do and who bears losses if it makes an unwanted transaction.
The bank’s email, titled “Protecting your finances in the AI World,” says usernames and passwords 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 added that it is “excited about what AI used responsibly can deliver.” A customer posted the email on Bluesky; TechCrunch reported on it October 27 and said a bank spokesperson confirmed it was authentic.
The warning coincides with financial firms testing or responding to agent activity. According to the source report, Visa told investors that trust is the biggest barrier to AI agents that make payments. Robinhood said customers had put more than $250 million into accounts that AI agents trade; the source does not specify the period covered by that figure. Robinhood has also described using a separate account and spending limits, while saying customers “assume all risk” for trades made by AI agents.
A password can give an agent the same account access as its owner, rather than permission to complete one limited task. The article identifies narrower controls as safer alternatives: read-only access, approval before each payment, a virtual card with a spending cap, a token restricted by merchant, amount and time, or a separate account funded with money the customer can afford to lose. These safeguards limit exposure but 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 Limited Access Matters
Giving an agent a full banking login can make it difficult to distinguish authorized customer activity from an error, an unwanted action or account theft. The source report says banks have encountered third-party agents logging in with customers’ own passwords and may be unable to tell whether a transaction reflects the customer’s intent. That can create risks in both directions: an agent may move money without the user’s knowledge, or a bank may flag the login and restrict the account.
Control and liability are separate issues. An approval step or spending limit can reduce the amount at stake, but customers should not assume those protections guarantee reimbursement. The source describes legal questions under US and EU rules that have not been resolved specifically for AI agents. For readers, the practical consequence is to check what access an agent receives, what actions it can take without confirmation, and what the service’s terms say about losses.
Products Worth Considering
Ring Floodlight Cam 2K Wired Security Camera, 3-Pack, Black
Ring Outdoor Cam 4K Plus Battery Security Camera, 3-Pack, White
Bose TV Speaker (2nd Gen) Compact Soundbar with Bluetooth and HDMI-ARC, Black
As an affiliate, we earn on qualifying purchases.
Banks Confront Agent Logins
Axios reported on October 22, citing unnamed sources, that major US banks were finding unauthorized third-party AI agents inside customer accounts, typically using passwords supplied by customers. The report said banks could have trouble determining whether customers intended the activity. The account in the source material says banks are blocking some agents and revising their terms in response.
The concern is not limited to how an agent signs in. Agents can read websites, messages, invoices and documents, and text in those materials can attempt to redirect an agent’s behavior—a risk known as prompt injection. The source identifies this as a leading risk on the OWASP list for AI applications. Restricting account permissions can reduce the consequences of a compromised or misdirected agent, though it cannot guarantee the agent will behave as intended.
The source also points to consumer-protection rules, while cautioning that their application is not settled. In the United States, Regulation E excludes some transfers initiated by a person who was given access by the consumer; applying that provision to an AI agent or its operator is the author’s interpretation, not a ruling. In the European Union, PSD2 requires customers to take reasonable steps to protect security credentials, and sets out potential liability for certain failures. Whether sharing credentials with an AI agent meets the relevant legal standard has not been tested in court, according to the source.
““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
Who Covers Agent-Made Losses
No court or regulator ruling identified in the source settles whether giving an AI agent a password counts as furnishing account access under US Regulation E, or whether doing so breaches the credential-protection duties described under EU payment rules. The legal discussion in the source is the author’s reading, not legal advice. Individual outcomes may depend on the facts, the account agreement and the applicable law.
It is also unclear how widely unauthorized agents are operating across bank accounts, how banks identify customer-approved activity, and how consistently financial services will apply spending limits or approval controls. The reported $250 million Robinhood figure has no stated time window in the supplied material, so it should not be treated as a rate of growth or a measure of market-wide adoption.
Check Permissions Before Connecting
Customers considering an AI money tool can check whether it needs full credentials or offers a restricted connection, whether it can initiate transfers or trades without approval, and whether limits can be set by amount, merchant and time. They should also read the provider’s terms for responsibility when an agent acts, and ask their bank how it treats third-party access. A separate, limited balance may reduce potential losses, but it does not settle liability.
Financial firms’ next steps are not specified in the source material. Banks may continue adjusting account controls and terms as agent activity develops, while payment and trading companies face questions about trust, permissions and responsibility. Until clearer rules or decisions emerge, the source’s central practical distinction remains: grant an agent only the access needed for a task, rather than a password that opens the whole account.
Key Questions
What did Bank of America tell customers?
It told customers not to share their banking username or password with another person or an outside service, including an AI-enabled tool. The email says customers are responsible for activity resulting from shared access.
Why is sharing a bank password with an AI agent risky?
A password may let an agent access the account as if it were the customer, rather than limiting it to one task. It can also make it harder for a bank to distinguish customer-directed activity from an unwanted action or theft.
What is a safer way to let an agent handle a payment?
Options described in the source include read-only access, approval for every payment, a capped virtual card, or a token limited to a merchant, amount and time window. A separate account with a limited balance can also cap exposure.
Will a bank reimburse money moved by an AI agent?
The source does not establish a general answer. It describes unresolved questions about how existing US and EU rules apply when a customer gives an AI agent access. Customers should check their bank’s terms and relevant legal protections rather than assume reimbursement is guaranteed.
Does an account limit remove the customer’s risk?
No. Limits can restrict how much an agent can spend or trade, but they do not necessarily determine who is responsible for losses. Robinhood, according to the source, says customers assume all risk for trades by AI agents.
Source: ThorstenMeyerAI.com
