🔍 Read the full analysis: Don’t Give Your AI Agent Your Bank Password: A Safer Way To Handle Money on ThorstenMeyerAI.com
Get movie nights 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 their banking passwords with AI tools or agents, saying customers are responsible for activity resulting from that access. Safer approaches include limited, read-only access, transaction approvals and capped virtual cards, but responsibility for agent-driven transactions remains legally unsettled.
Bank of America has warned customers not to give their banking usernames or passwords to AI tools or agents, saying customers are responsible for activity resulting from shared access. The warning, confirmed as authentic by a bank spokesperson to TechCrunch, comes as financial firms face questions about AI agents logging into accounts and making transactions in customers’ names.
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-enabled tool or agent acting on the customer’s behalf. It adds that customers who share their credentials are responsible for activity resulting from that access. Bank of America also said it is “excited about what AI responsibly can deliver,” according to the email text reproduced in the source report.
TechCrunch reported on the email on October 27 after a customer posted it on Bluesky. A Bank of America spokesperson confirmed its authenticity to the outlet. Separately, Visa told investors this week that trust is the biggest barrier to AI agents making payments, while Robinhood said customers had put more than $250 million into accounts that AI agents trade. Those comments show agents are already being connected to financial activity, but do not establish how many transactions they have made or whether those transactions were successful.
A password can give an agent access well beyond a single task. With a customer’s login, the bank may see actions as coming from the customer, making it harder to distinguish an authorized request from misuse or a compromised agent. The source report says a safer setup can use read-only access, approval for each payment, capped virtual cards, narrowly scoped tokens or a separate account with limited funds. Those controls reduce access; they do not automatically settle who is 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
The Cost of Sharing Account Access
The warning matters because customers may assume that a bank will treat an agent’s mistaken or unauthorized transaction like ordinary fraud. That outcome is not assured. The source article discusses U.S. and European rules that place duties on account holders who provide access or fail to protect security credentials. How those rules apply to an AI agent has not been established by a court or regulator, according to the article.
There is also an operational risk: an agent using a customer’s password can look like the customer to the bank. A bank may allow activity the customer did not intend, or flag the login as suspicious and restrict account access. Limiting what an agent can do can reduce the potential damage, while keeping a person involved in payment approval gives customers a chance to catch errors before funds move.
Companies adopting agent payments face a related trust problem. A spending cap or separate account can limit exposure, but the source says Robinhood’s terms place risk for agent trades on customers. Readers should distinguish between a technical safeguard and a promise that a provider will reimburse losses.
Popular right now
Bose QuietComfort Wireless Bluetooth Headphones with Active Noise Cancellation, Mic, USB‑C Charging, Deep Bass, 24‑Hour Battery – White Smok
Philips 3300 Series Fully Automatic Espresso Machine with LatteGo Milk System
KitchenAid Classic Series 4.5 Quart Tilt-Head Stand Mixer K45SS, Onyx Black
As an affiliate, we earn on qualifying purchases.
Banks Respond to Agent Logins
The Bank of America email follows a report by Axios on October 22, which cited unnamed sources who said major U.S. banks were finding third-party AI agents inside customer accounts. The agents were reportedly logging in with customers’ own passwords, leaving banks unable to tell in some cases whether the activity was customer-directed. Axios’ account is based on unnamed sources, rather than a public bank-by-bank disclosure.
In its report about the email, TechCrunch noted that banks may block agent access and revise terms as they respond to the problem. The source article also explains that U.S. Regulation E excludes certain transfers initiated by a person who was given access by the consumer, and that European payment rules require customers to take reasonable steps to protect their credentials. Whether these provisions apply to an AI agent is an interpretation, not a settled legal ruling cited in 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 the customer email
Liability Rules Remain Untested
No court or regulator ruling on AI-agent credential sharing is cited in the source material. The source author’s reading is that U.S. rules excluding some transfers made by someone given account access could be relevant to an agent or its provider, but the author says that application has not been tested. The article likewise says it is not clear whether giving credentials to an AI agent would count as gross negligence under the cited European rules. These are legal interpretations, not settled findings or legal advice.
The available reports also do not identify the number of affected bank accounts, the scale of unauthorized transactions, or which agents were involved. Robinhood’s reported $250 million figure refers to money customers put into accounts that AI agents trade; the source gives no comparison baseline or further breakdown. It does not establish that $250 million was lost, spent or traded by agents.
Use Limited Access Before Payments
Customers considering an AI agent for financial tasks should check the bank’s and service provider’s terms before connecting an account, and avoid giving an agent their primary banking password. Where available, a customer can favor read-only permissions, per-transaction approval, restricted tokens or a low-balance account. A capped virtual card can also restrict where and how much an agent can spend. Customers should confirm what protections apply and who bears losses before enabling automatic payments or trades.
Banks and agent providers are likely to keep adjusting access controls and account terms as these tools spread, but the source material gives no timetable for new rules or a specific next policy announcement. For now, the central question is not just whether an agent can make a payment, but what access it receives and who is accountable if its actions do not match the customer’s instructions.
Key Questions
What did Bank of America tell customers?
The bank warned customers not to share their usernames or passwords with another person or an outside service, including an AI-enabled tool or agent. It said customers are responsible for activity resulting from shared access.
Does the warning mean customers automatically lose fraud protection?
No automatic outcome is established in the source material. The article says the application of U.S. and European rules to AI agents has not been tested in court, and customers should check the terms and protections that apply to their accounts.
What is a safer way to let an AI agent handle a payment?
Options described in the source include read-only access, requiring approval for each payment, a capped virtual card, a narrowly limited token, or a separate account with a limited balance. Availability depends on the bank and service.
Does Robinhood’s $250 million figure mean AI agents lost that money?
No. The source says customers had put more than $250 million into accounts that AI agents trade. It does not say that amount was lost or provide a comparison baseline or transaction breakdown.
Source: ThorstenMeyerAI.com
