Updated yesterday
Bank of America warns against giving AI agents a banking password

Bank of America warns against giving AI agents a banking password

A customer email warns against sharing login credentials with AI agents. The bank’s existing guidance separates passwords from supported data access and explains revocation limits.

The warning concerns passwords given to an outside agent

Bank of America is warning customers against giving their banking username and password to an AI‑enabled service that offers to act for them. A [customer email posted publicly on October 27](https://bsky.app/profile/btoporek.bsky.social/post/3myuzetgir2u6) explicitly includes AI tools and agents in its warning about sharing credentials. [TechCrunch reported](https://techcrunch.com/2026/10/27/bank‑of‑america‑kindly‑asks‑that‑you‑dont‑share‑your‑banking‑password‑with‑your‑ai‑assistant/) that a bank spokesperson confirmed the email’s authenticity. The message says customers are responsible for activity resulting from access they provide by sharing credentials. That is the bank’s stated warning. It does not establish the outcome of a disputed transaction, change every customer’s legal rights or document an actual loss caused by an AI agent. The immediate question for someone connecting a financial assistant is what access the service is requesting. Handing over the password is different from granting a supported service a defined connection to account data.

Supported data sharing uses a different access mechanism

Bank of America’s [official third‑party data‑sharing guidance](https://web.bankofamerica.com/en/security/tools‑resources/third‑party‑app‑service‑data‑sharing) describes a consent‑based mechanism in which the customer signs in directly with the bank rather than giving a third party their login credentials. The bank says this reduces the information a connected service can access and removes the need for that service to store and use the customer’s password. The guidance contrasts this with credential sharing: a service holding the login may have the same access to account information as the customer, without a choice about how much information it retrieves. The bank also warns that access can continue after a person stops actively using the service. These distinctions concern access to account information. The FAQ does not certify a particular AI assistant, establish that every service uses the supported connection, or grant an agent permission to make payments. A product describing itself as an assistant does not, by that description alone, identify how it connects to a bank.

Revoking access does not erase previously shared information

For services using its supported protocol, Bank of America [says customers can view connected third parties and revoke permission](https://web.bankofamerica.com/en/security/tools‑resources/third‑party‑app‑service‑data‑sharing) in Mobile or Online Banking. Its guidance treats services using shared login details differently, describing a password change as the most secure way to stop that form of access. The bank separately warns that a third party may retain information it has already received. Removing an ongoing connection and deleting previously collected data are therefore different questions; the FAQ points readers to the third party’s own privacy and retention policies for the latter. The AI‑specific email is a current warning, while the reviewed data‑sharing FAQ has no established publication date. It should not be presented as a newly introduced October 27 policy. Together, the sources explain why password sharing and supported consent‑based access deserve separate treatment, without establishing a bank breach or the safety of any particular agent. *Bank of America branch at 5135 River Road in Bethesda, Maryland, photographed November 26, 2021. Archive bank context, not an AI‑agent demonstration or evidence of an account incident. Photo: [G. Edward Johnson](https://edwardjohnson.com/) / [Wikimedia Commons](https://commons.wikimedia.org/wiki/File:Bank_of_America_River_Rd_Bethesda_MD_2021‑11‑26_15‑12‑05_1.jpg), [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Cropped and downsampled; no semantic edits.*

Share this article

PostShare

Related News