Home › Banking › AI agents & bank account access

If I Let an AI Agent Into My Bank Account, Who Pays if It Goes Wrong?

Direct answer: If you share your bank login, passcode, or active browser session with an AI agent, you generally bear the loss until you notify your bank. Federal Regulation E (12 CFR 1005.2(m)(1)) excludes transfers made by anyone you gave an access device to, whereas read-only OAuth tokens never share passwords or payment authority.

By the numbers: Under 12 CFR § 1005.6(b), consumer liability for an unauthorized EFT is capped at $50 if reported within 2 business days ($500 up to 60 days), but 12 CFR § 1005.2(m)(1) excludes transfers by anyone furnished your access device until you notify the bank. Source: CFPB Regulation E, 12 CFR § 1005.2(m) & § 1005.6

“If the consumer furnishes an access device and grants authority to make transfers to a person (such as a family member or co-worker) who exceeds the authority given, the consumer is fully liable for the transfers unless the consumer has notified the financial institution that transfers by that person are no longer authorized.” — CFPB Official Interpretation, Supplement I to Part 1005 — 2(m) Comment 2(m)-2

Updated 2026-10-24

Quick Q&A

Who pays if an AI agent with my password sends money from my bank account?

You generally do, until you notify the bank that the agent's access is no longer authorized. Regulation E (12 CFR § 1005.2(m)(1)) treats transfers made with a furnished access device as authorized, even when the agent exceeds your instructions.

Does Regulation E cover a payment I approve myself after an AI agent gives bad advice?

Generally no. If you initiate and approve the payment yourself (for example, confirming a Zelle or wire transfer based on an AI hallucination), it is an authorized consumer-initiated transfer under Regulation E.

How can I let a tool read my bank transactions without giving up Regulation E protection?

Use your bank's official OAuth 2.0 read-only connection (where you log in on the bank's own domain and grant a revocable, read-only token) rather than typing your username, password, or 2FA code into an AI agent or screen-driving browser.

Answer-First Summary · Federal Regulation E & Bank Agreements (Data as of 2026-10-24)

If you type or share your bank username, password, 2FA code, or active signed-in browser session with an AI agent, you generally bear the financial loss for transfers it makes until you notify your bank and cut off access.

Under federal Regulation E (12 CFR § 1005.2(m)), banks must reimburse consumers for "unauthorized electronic fund transfers." However, 12 CFR § 1005.2(m)(1) and the CFPB's Official Interpretation (Supplement I to Part 1005 — 2(m), Comment 2(m)-2) explicitly exclude any transfer initiated by a person or third party to whom the consumer furnished an "access device" (such as login credentials, a passcode, or an authenticated session)—even if that agent exceeds your instructions—unless and until you notify the bank that transfers by that party are no longer authorized.

Method A — Sharing login credentials, 2FA, or a screen-driving browser session: Furnishes an access device under 12 CFR § 1005.2(m)(1) and breaches major bank digital agreements.Consumer pays until bank is notified
Method B — Approving a Zelle, wire, or ACH push yourself after an AI hallucination: Treated as an authorized consumer-initiated payment because you clicked send yourself.Consumer pays (authorized transfer)
Method C — Tokenized, read-only open-banking OAuth connection: You sign in on the bank's own domain and issue a revocable read-only token; no password or payment authority is shared.Reg E unauthorized-EFT rules stay intact

Primary sources verified 2026-10-24: CFPB 12 CFR § 1005.2(m) & Official Interpretations · 12 CFR § 1005.6 (Liability limits) · CFPB Personal Financial Data Rights (12 CFR Part 1033). Educational overview of federal banking rules and published bank agreements, not legal advice.

1. Interactive Scenario Checker & Access Method Breakdown

Select how the AI agent or tool interacted with your bank account and what went wrong to see how federal Regulation E (12 CFR Part 1005) and published bank agreements classify the transfer:

How did the AI agent access your bank?What went wrong?

High consumer liability risk (Furnished Access Device)

You furnished an access device under 12 CFR § 1005.2(m)(1)

Because you typed or shared your bank username, password, 2FA code, or active authenticated browser session with the AI agent, federal Regulation E (12 CFR § 1005.2(m)(1) and Comment 2(m)-2) treats transfers initiated with those credentials as authorized—even if the AI agent misunderstood your prompt or exceeded the dollar limit you gave it. It also violates every major bank's Online Banking Agreement.

What to do: Immediately revoke the session, change your bank password, and call your bank under 12 CFR § 1005.6 to state that transfers by that party are no longer authorized. Only transfers occurring after you notify the bank regain unauthorized-transfer protection.

The Three Access Methods Compared Under Federal Law

Access method	What the AI / tool receives	Regulation E status (`12 CFR § 1005.2(m)`)	Online banking agreement status
a) Credential sharing or screen-driving AI agent Typing your bank login/2FA into an agent, or letting a computer-use bot drive a logged-in bank tab	Full "access device" (`12 CFR § 1005.2(a)(1)`): ability to view balances, add payees, and initiate ACH, Bill Pay, Zelle, or wire transfers as you.	Excluded from unauthorized EFT protection under `12 CFR § 1005.2(m)(1)` & Comment 2(m)-2—even if the agent exceeds your prompt—until you notify the bank that transfers are no longer authorized.	Prohibited. Chase, BofA, Wells Fargo, Citi, Capital One, and Ally agreements forbid sharing credentials or passcodes with third-party software or agents.
b) Approving a payment yourself based on AI advice AI reads an email/invoice or hallucinates a payee, and you click send on Zelle, ACH push, or wire	No direct payment credentials required, or draft-only preparation that you confirm with your own 2FA/passkey.	Authorized transfer. Because you initiated the payment yourself, it is not an "unauthorized EFT" under `12 CFR § 1005.2(m)` (unless an attacker obtained your access device through fraud or robbery under specific statutory rules). Wires fall under UCC Article 4A.	Permitted to use your own login, but bank disclaimers state that final review of payee details and amounts rests with the customer.
c) Tokenized, read-only open-banking OAuth Redirecting to your bank's own domain to grant a scoped read-only API token	Scoped, revocable read-only OAuth token (balances & transaction history only). Zero access to your password, 2FA, or money-movement rails.	Full Regulation E protection preserved. Because no payment-capable access device was furnished, any separate unauthorized debit remains subject to `12 CFR § 1005.6` liability caps ($50 within 2 business days).	Supported & recommended via each bank's official Security Center / Connected Apps dashboard.

2. CFPB Personal Financial Data Rights Rule (Dodd-Frank Section 1033, `12 CFR Part 1033`)

Section 1033 of the Dodd-Frank Wall Street Reform and Consumer Protection Act (12 U.S.C. § 5533) requires financial institutions to make consumer financial data available to the consumer and authorized third parties. On October 22, 2024, the CFPB issued its final Personal Financial Data Rights Rule (12 CFR Part 1033, 89 Fed. Reg. 90,838, published Nov. 18, 2024).

What Part 1033 covers: Regulation E asset accounts (checking and savings accounts), Regulation Z credit cards, and payment facilitation products (12 CFR § 1033.111). Covered data providers must maintain standardized, credential-free developer APIs so consumers can share transaction and balance data without handing over their online banking username or password (12 CFR § 1033.301 & § 1033.311).
Ban on credential screen-scraping & strict secondary-use limits: Authorized third parties must certify that they will not collect or use consumer login credentials to scrape data once a compliant developer API is available, must limit data collection strictly to what is reasonably necessary to provide the product the consumer requested (no targeted advertising, cross-selling, or training unrelated models on secondary data under 12 CFR § 1033.421), and must expire access after 1 year unless the consumer re-authorizes.
One-click revocation right: Both the bank and the third party must provide a simple mechanism to revoke data access immediately (12 CFR § 1033.331(e) & § 1033.421(h)).
2025–2026 Litigation & Implementation Status (as of Oct. 24, 2026): Immediately after the rule was finalized in October 2024, the Bank Policy Institute, Kentucky Bankers Association, and Forcht Bank filed suit in the U.S. District Court for the Eastern District of Kentucky (Forcht Bank, N.A. et al. v. CFPB, No. 5:24-cv-00304), arguing among other points that the rule unlawfully required banks to enable third-party access without addressing liability and fee allocation. Following a change in CFPB leadership in 2025—and alongside broader Fifth Circuit and federal litigation over CFPB rulemakings—the CFPB published an Advance Notice of Proposed Rulemaking on August 22, 2025 (90 Fed. Reg. 40,946) to reconsider Part 1033 (including credential security, AI/third-party liability, and API cost recovery). On October 29, 2025, the federal court in Kentucky granted a preliminary injunction staying the rule's compliance deadlines until the CFPB completes its reconsideration rulemaking. Even while the federal mandate is stayed, all six major banks below voluntarily operate OAuth 2.0 data-sharing dashboards and restrict credential-based screen scraping under their own agreements.

3. Bank-by-Bank Table: Online Banking Agreements, AI Agents & How to Revoke Access

How six major U.S. banks connect to third-party apps, what their published Digital Services / Online Banking Agreements say about sharing credentials with third-party software or AI agents, and where to revoke connected apps (verified Data as of 2026-10-24; federal baseline: CFPB Regulation E, 12 CFR § 1005.2):

Bank / Institution	Third-Party Connection Method	Online Agreement Terms & Public Position on Credential Sharing / AI Agents	How to View & Revoke Connected Apps	Official Agreement & Security Links
Chase (JPMorgan Chase Bank, N.A.)	OAuth 2.0 tokenized API (Chase Security Center / Data Sharing). Blocks credential-based screen scraping on supported endpoints.	JPMorgan Chase's Digital Services Agreement prohibits sharing your username, password, or one-time passcode with any third party or automated software, and states that providing credentials to an AI agent, bot, or aggregator treats resulting activity as authorized by you. In public open-banking security statements, Chase's CISO has warned that handing login credentials or active browser sessions to third-party intermediaries or AI agents exposes customers to credential harvesting and unauthorized money movement outside Chase's OAuth controls.	Sign in at chase.com or the Chase Mobile app → Security & Privacy (Security Center) → Linked Apps and Websites → select the app or aggregator → Stop sharing / Revoke access.	Chase Digital Services Agreement · Chase Data Sharing & Linked Apps Data as of 2026-10-24
Bank of America, N.A.	OAuth 2.0 tokenized data sharing via Bank of America Security Center (FDX-aligned API).	The Online Banking Service Agreement states that if you give your Online ID, passcode, or one-time code to any person, aggregator, or software agent, you authorize that party to act on your behalf and you may be liable for all transactions and transfers initiated until you notify Bank of America and change your credentials.	Sign in → Security Center → Third-Party App Access (Connected Apps) → select the third-party app → Remove / Revoke access, then rotate your passcode.	BofA Online Banking Service Agreement · BofA Security Center Data as of 2026-10-24
Wells Fargo Bank, N.A.	OAuth 2.0 tokenized API (Control Tower). Replaces legacy username/password screen scraping.	The Wells Fargo Online Access Agreement warns not to share your username, password, or one-time passcodes with third-party websites, apps, or automated tools. Giving credentials to a third-party service grants that service authority over your account until you notify Wells Fargo and revoke access.	Sign in → Security & Privacy → Control Tower → Connected Apps → toggle off or remove the third-party connection.	Wells Fargo Online Access Agreement · Wells Fargo Privacy & Security Data as of 2026-10-24
Citibank, N.A. (Citi)	OAuth 2.0 tokenized API access for approved data recipients.	Citi's Client Manual and Online Access Agreement require you to keep your User ID, password, and security codes confidential. If you furnish your access credentials to another person or automated tool, transfers it initiates are treated as authorized until you notify Citi that transfers are no longer authorized.	Sign in → Profile & Settings → Security Center → Manage Linked Apps / Third-Party Access → Disconnect app and change password.	Citi Security Center Data as of 2026-10-24
Capital One, N.A.	OAuth 2.0 tokenized API (100% OAuth migration for third-party data connections; blocks credential-based scraping).	Capital One's Digital Services Terms state that you must not disclose your username, password, or multi-factor code to any third party or software agent, and require using Capital One's official OAuth consent flow rather than typing credentials into third-party prompts.	Sign in → Profile → Security → Connected Apps → select the linked third-party service → Revoke access.	Capital One Online Banking Terms & Conditions Data as of 2026-10-24
Ally Bank	OAuth token-based permissions via aggregator connections and security settings.	Ally Bank's Online Banking Services Agreement states that if you share your login credentials or security codes with any third party, aggregator, or software tool, you authorize all transactions initiated with those credentials until you notify Ally Bank and reset your login.	Sign in → Profile & Settings → Security → Connected Apps / Third-Party Access → Remove connection, then update your password and 2FA.	Ally legal agreements (Online Banking Services Agreement) · Ally Security Center Data as of 2026-10-24

Federal baseline across all U.S. consumer deposit accounts: CFPB Regulation E — 12 CFR § 1005.2(m) (Unauthorized EFT definition) · 12 CFR § 1005.6 (Liability of consumer for unauthorized transfers) · 12 CFR § 1005.11 (Procedures for resolving errors). Data as of 2026-10-24.

4. What to Do Next: Step-by-Step Checklist

If you have ever typed your bank login into an AI agent, browser automation tool, or third-party app—or if you want to connect a budgeting tool without risking your Regulation E rights—follow these five steps:

Audit connected apps in your bank's Security Center today: Log in directly on your bank's official website or mobile app (see the table above for Chase Linked Apps, BofA Connected Apps, Wells Fargo Control Tower, Citi Security Center, Capital One Connected Apps, or Ally Security settings) and review every third party with active access.
Revoke any unused or unrecognized OAuth tokens: Click Stop sharing, Remove, or Revoke access on any app you no longer use. Revoking an OAuth token cuts off data access immediately without affecting your direct login.
Rotate your password, passkeys, and 2FA if you ever shared credentials: If you ever typed your actual bank username, password, or one-time passcode into an AI agent, aggregator, or browser extension, revoking a token is not enough—change your bank password immediately, register a hardware or device passkey where supported, and sign out of all active sessions.
Notify your bank immediately under 12 CFR § 1005.6 if an agent had your login: Under 12 CFR § 1005.2(m)(1), authority you granted by furnishing an access device continues until you notify the financial institution that transfers by that party are no longer authorized. Call the phone number on the back of your debit card and send a secure message stating that third-party/automated access is revoked.
Dispute any unauthorized transfer within 2 business days (and in writing within 60 days): Under 12 CFR § 1005.6(b), reporting an unauthorized EFT within 2 business days of learning of the loss caps your statutory liability at $50 (waiting past 2 business days raises the cap up to $500, and waiting past 60 days after your statement is sent can expose you to unlimited loss for subsequent transfers). Follow up in writing under 12 CFR § 1005.11 so the bank must investigate within 10 business days (or provide provisional credit while taking up to 45 days).

Disclaimer: Educational overview of federal banking rules and published bank agreements, not legal advice.

FAQ

If I give my bank username, password, or 2FA code to an AI agent and it sends money by mistake, does Regulation E require my bank to refund me?

Generally no, until you notify your bank and revoke access. Under federal Regulation E (12 CFR § 1005.2(m)(1)) and Official Interpretation Supplement I to Part 1005 — 2(m) (Comment 2(m)-2), an 'unauthorized electronic fund transfer' excludes transfers initiated by a person or third party to whom the consumer furnished an access device (such as login credentials, a passcode, or an active authenticated session), unless the consumer has notified the financial institution that transfers by that party are no longer authorized. Even if the AI agent exceeds your instructions, federal law treats you as responsible until you notify the bank (https://www.consumerfinance.gov/rules-policy/regulations/1005/2/, verified 2026-10-24).

What if an AI agent hallucinates a bill or payee and I approve the Zelle, wire, or ACH transfer myself?

If you personally initiate or approve a transfer (for example, typing a one-time code to confirm a Zelle payment or wire), Regulation E generally treats it as an authorized transfer because you initiated it yourself, unless a third party fraudulently induced you to hand over your access device or obtained the transfer through robbery or deceptive credential theft (https://www.consumerfinance.gov/compliance/compliance-resources/deposit-accounts-resources/electronic-fund-transfers/electronic-fund-transfers-faqs/). Consumer-initiated Wires are also governed by UCC Article 4A rather than Regulation E (https://www.consumerfinance.gov/rules-policy/regulations/1005/2/).

Is a read-only open-banking OAuth connection safer than letting an AI agent use my login or browser?

Yes. With an OAuth 2.0 open-banking connection, you sign in on your bank's own website or app and issue a scoped, revocable read-only token. The third-party app never sees your password, cannot pass multi-factor challenges to move money, and can be disconnected anytime in your bank's security center without changing your master password (https://www.consumerfinance.gov/personal-financial-data-rights/).

What does the CFPB Personal Financial Data Rights Rule (Section 1033) say about AI agents and screen scraping?

Under Dodd-Frank Section 1033 (12 CFR Part 1033, finalized Oct. 2024 at 89 Fed. Reg. 90,838), covered banks must provide standardized, credential-free developer APIs for checking, savings, and credit card data, allow one-step revocation, and restrict third parties to using data only for the product the consumer requested. Third parties are barred from screen-scraping with saved credentials once compliant APIs are available. However, in October 2025 the U.S. District Court for the Eastern District of Kentucky stayed the rule's compliance deadlines while the CFPB reconsiders Part 1033 through a new rulemaking (https://www.federalregister.gov/documents/2025/08/22/2025-16139/personal-financial-data-rights-reconsideration, verified 2026-10-24).

What should I do right now if I already typed my bank login into an AI agent or browser extension?

1) Immediately change your online banking password and passkeys on your bank's official site or app. 2) Open your bank's Security Center (Linked / Connected Apps) and revoke all third-party tokens and active sessions. 3) Call the number on the back of your debit card or statement to notify the bank under 12 CFR § 1005.6 that any third-party or automated access is no longer authorized, and review recent transactions within the 60-day statement window (https://www.consumerfinance.gov/rules-policy/regulations/1005/6/).

Educational overview of federal banking rules and published bank agreements, not legal advice.