SolutionsPricingWorkshopsBlogNewsAboutLet's Talk

Bank of America bans AI agents from accessing passwords

The second-largest US bank sent customers a warning against sharing passwords with AI agents. Citi, Morgan Stanley, and Wells Fargo restrict similar access.

AutomushPublished 2 min readSource: ZDNET

What happened

Bank of America, the second-largest bank in the United States, sent customers a message titled ‘Protecting your finances in the AI world’ with a clear warning: do not share banking passwords with AI agents. This is not a quiet internal policy - it is a public notice to customers, reflecting real concern about the risk.

This move is not isolated. Citi, Morgan Stanley, and Wells Fargo are already restricting third-party AI agent access to their systems. What used to be technical convenience - giving an automation tool your password so it could perform actions on your behalf - is becoming a defined risk that banks are starting to actively block.

Why it matters beyond the headline

When a bank says “don’t share passwords”, it is not just advising - it is starting to build detection systems that will block suspicious behaviour. If an automation system logs into your account with your password, the bank sees it as a normal human login. The moment something looks automated or comes from an unexpected location, the account may be blocked.

In Israel the situation is more severe. Security standards of banks here are stricter, and they have been blocking automated access that does not go through official approval processes for years. A business building automation that relies on password sharing - even if it works today - risks it stopping without warning.

The problem is not just technical. If an AI agent gets full access to an account, and it is breached or makes a mistake, the responsibility falls on the account holder. The bank can claim the customer violated terms of use, and refuse to cover damages.

What to do this week

If you have automation that connects to a bank or financial system, check how it gets access. If it asks for a password directly, or if you enter it into the tool itself, this is the time to stop and check alternatives. Look for integration that goes through the bank’s official API, or through an approved payment provider that has a direct agreement with the bank.

If you are building an internal system that needs access to financial data, start with the question of how the bank allows third-party access. Most banks in Israel offer a dedicated API for businesses, but the process to get access to it takes time and requires meeting security standards. A system built correctly from the start saves interruptions midway.

If you are not sure how to build integration that meets banking and regulatory standards, it is worth working with someone who has already done it in production systems. Secure integrations for regulated systems require practical experience, not just technical knowledge.

Sources

Frequently asked questions

Is it allowed to use automation tools that connect to the bank through an official API?

Yes, if the tool uses the bank's official API and has gone through its approval process, this is the recommended and secure way. The problem is only when the tool asks for your personal password or connects in a way the bank has not approved.

What happens if the bank detects I am using automation with my password?

The bank can temporarily block the account until you prove it is legitimate activity, or refuse to cover damages if something goes wrong. In serious cases, it can be considered a violation of terms of use.

Related guides

To the blog

Which of your processes could run on its own?

A free 30-minute discovery call, no commitment. We map your processes together and tell you honestly whether and how automation can help.

Try a call with agent now