On Monday, November 16, 2026, the search “chase bank outage” jumped across the United States as customers reported trouble reaching their online accounts. According to NBC Chicago, Downdetector showed more than 4,000 error reports for Chase by 12:19 p.m. Central time. In a statement reported by the Associated Press that afternoon, a Chase spokesperson said that, because of a technical issue, some transactions were taking longer than usual to complete, that customers still had access to their accounts and funds, and that the bank was working to resolve the problem as quickly as possible; the spokesperson described it as a technical bug, not a cyber issue. The Associated Press also reported that users listed problems at several other large banks and payment services on Downdetector the same day. The discussion that follows is general in scope: it describes checks useful in comparable situations and makes no findings about Chase’s situation. The question behind the searches is practical. If a bill payment, a transfer or a card purchase failed or stalled while a bank’s systems were struggling, who absorbs the late fee, the overdraft charge or the missed deadline? For consumer accounts, federal law gives a fairly precise answer through the Electronic Fund Transfer Act and the Consumer Financial Protection Bureau’s Regulation E, and recent federal court rulings show how those rules play out once a dispute reaches a judge. The short version: a bank can owe you the damages caused by a transfer it failed to make, it has real defenses for malfunctions you knew about when you tried, and your most useful tool is a precise notice of error sent within the sixty-day window that opens when the problem first shows up on a statement.
I. When a transfer fails during a bank outage, what does federal law make the bank owe you?
A. The Electronic Fund Transfer Act makes a bank answer for transfers it fails to make, with built-in exits
Everything starts with whether your transaction is covered at all. The federal definitions section, 15 U.S.C. § 1693a, defines an electronic fund transfer as any transfer of funds, other than a transaction originated by check, draft or a similar paper instrument, that is initiated through an electronic terminal, a telephonic instrument, or a computer or magnetic tape so as to order, instruct or authorize a financial institution to debit or credit an account. The same provision says the term includes point-of-sale transfers, automated teller machine transactions, direct deposits or withdrawals of funds, and transfers initiated by telephone. It also limits the protected person and the protected account: a “consumer” is a natural person, and an “account” is a demand deposit, savings deposit or other asset account established primarily for personal, family or household purposes. In practice, that means the debit card purchase that was declined at a register, the payment you pushed from your phone, the ATM withdrawal and the paycheck that was supposed to land by direct deposit are the kinds of transactions federal law has in mind, while a business operating account and a paper check sit outside this statute and depend on the account agreement and on state law.
For covered transfers, the liability rule is in 15 U.S.C. § 1693h. Subject to two later subsections, a financial institution is liable to a consumer for all damages proximately caused by its failure to make an electronic fund transfer, in accordance with the terms and conditions of an account, in the correct amount or in a timely manner when properly instructed to do so by the consumer. The statute lists the situations in which that failure is not the bank’s responsibility: your account has insufficient funds, the funds are subject to legal process or another encumbrance, the transfer would exceed an established credit limit, an electronic terminal has insufficient cash, or a regulation provides otherwise. Two further paragraphs matter during an outage. Under § 1693h(a)(2), the bank is also liable when a transfer fails for insufficient funds because the bank itself failed to credit a deposit, in accordance with the terms and conditions of the account, that would have covered it. Under § 1693h(a)(3), it is liable when it fails to stop payment of a preauthorized transfer after being instructed to do so in accordance with the account terms. If a delayed direct deposit caused a later payment to bounce, paragraph (a)(2) is the provision to read first.
Notice the yardstick the statute uses for timing. A transfer is late, for purposes of § 1693h(a)(1), when it is not made “in a timely manner” in accordance with the terms and conditions of the account. That sends you back to your own deposit agreement and to the bank’s disclosures about processing times, cut-off hours and posting schedules. A transfer that was slow on an outage afternoon but still completed within the time the account terms promise is a different case from a transfer that never went through, or one that went through days after the date the terms commit to. The phrase “when properly instructed” matters just as much: the statute protects a consumer who gave a complete and correct instruction through a channel the account allows, so saved confirmation screens and reference numbers are not a formality.
The exits are in subsection (b), and both put the burden on the bank, which must show its defense “by a preponderance of the evidence.” The first covers an act of God or other circumstance beyond the institution’s control, but only if it also exercised reasonable care to prevent such an occurrence and such diligence as the circumstances required. The second covers “a technical malfunction which was known to the consumer at the time he attempted to initiate an electronic fund transfer” or, for a preauthorized transfer, at the time the transfer should have occurred. Read literally, the second exit means that when the app or website tells you on screen that a service is unavailable and the attempt fails, the bank has a statutory defense for that attempt. The harder cases are the ones where nothing looked wrong: a payment that showed as sent but was never delivered, a scheduled automatic payment that silently failed, or a deposit that did not post. Subsection (c) then caps exposure in a different way. If the failure was not intentional and resulted from a bona fide error despite procedures reasonably adapted to avoid it, the institution is liable for actual damages proved. And the account agreement cannot contract out of any of this: under 15 U.S.C. § 1693l, “No writing or other agreement between a consumer and any other person may contain any provision which constitutes a waiver of any right conferred or cause of action created by this subchapter.” An agreement may give you more protection, never less.
A recent federal ruling shows that the duty in § 1693h is treated as a real legal duty, not a slogan. In Jennings v. Citibank, N.A., No. 3:25-cv-906 (D. Conn. Jan. 16, 2026), the United States District Court for the District of Connecticut ruled on a motion to dismiss filed by the bank. The customer alleged that the bank had declined many properly payable debit card transactions even though his accounts held enough money to cover them, and he sued for breach of contract, statutory damages for failure to make electronic fund transfers under § 1693h(a)(1), negligence, recklessness and a violation of the Connecticut Unfair Trade Practices Act. Because the ruling addressed a motion to dismiss, the court took the customer’s allegations as true and decided only whether the claims could go forward; according to the ruling, the bank specifically denies having improperly declined the transactions, and no finding of liability was made. On the negligence count, the court held that Connecticut’s economic loss rule barred the theories built on common-law duties arising from the banking contract, but not the theory built on the federal statute, because the defendant’s duty to the plaintiff under that statute “exists independently of the contractual relationship between the plaintiff and the defendant.” For a customer whose card was repeatedly declined while the account held enough money, Jennings v. Citibank shows that a federal transfer duty under § 1693h can support a state-law negligence theory that survives a motion to dismiss even where a contract-based theory is cut off.
B. Who these rules protect and what a claim can actually recover
Coverage questions are not limited to ordinary checking accounts. Many households receive wages, refunds or public benefits on prepaid cards, and those cards can be hit by the same outages. In Mohamed v. Bank of America, N.A., No. 22-1954 (4th Cir. Feb. 16, 2024), the United States Court of Appeals for the Fourth Circuit considered pandemic unemployment assistance that Maryland’s unemployment agency arranged to pay through bank-issued prepaid debit cards. The claimant said his entire $14,644 balance had been spent on transactions he did not recognize, and the district court dismissed his federal claim on the ground that the account was not covered by the Act. The Fourth Circuit vacated that judgment, holding that the account was a “government benefit account” under Regulation E because it was brought into existence through the state agency, even though the bank issued the card and ran the account day to day. The opinion also records that the bank later told the claimant it would credit him for the full amount of his benefits, more than six months after his first error claim. If your money sits on a prepaid benefits card or another prepaid account when an outage or an error hits, Mohamed v. Bank of America shows that the Act’s protections can apply even though the card is administered by a bank under contract with a government agency.
What can a successful claim recover? The remedies section, 15 U.S.C. § 1693m, provides that a person who fails to comply with the subchapter is liable for any actual damage sustained by the consumer; in an individual action, an additional amount of not less than $100 nor greater than $1,000; in a class action, an amount the court may allow, capped for the class at the lesser of $500,000 or 1 percent of the defendant’s net worth; and, in a successful action, the costs of the action together with a reasonable attorney’s fee. In setting the individual award, the court considers the frequency and persistence of noncompliance, its nature, and the extent to which it was intentional. Two features of the same section shape any outage dispute. First, subsection (e) gives a business a cure: it has no liability under the section if, before the consumer files suit, it notifies the consumer of the failure, complies with the subchapter, adjusts the account and pays actual damages or, where applicable, damages under § 1693h. A bank that promptly reverses fees and reimburses documented losses after an outage may therefore close off a later lawsuit. Second, subsection (g) states the deadline: an action may be brought in any United States district court or other court of competent jurisdiction, without regard to the amount in controversy, “within one year from the date of the occurrence of the violation.” The sources read for this guide do not decide whether any later event restarts that year, so the safe working assumption is to count from the day of the failed transfer itself.
The words “all damages proximately caused” in § 1693h(a) are broad, and they are where a late fee charged by someone else could enter the picture. Suppose a properly instructed payment to a utility, a landlord or a lender was not made in a timely manner under the account terms, and the payee charged a late fee as a direct result. The statutory text points to the bank’s liability for damages proximately caused by that failure, unless one of the exits in subsection (b) or the actual-damages cap in subsection (c) applies. None of the decisions read for this guide rules on whether a particular third-party late fee qualifies, so that question is decided case by case on causation and on the account terms. What a consumer controls is the proof: the instruction, its time, what the screen showed, the payee’s fee notice and the amount.
State law can add remedies, and the Connecticut ruling is a useful map of where those remedies stop. In Jennings, the court dismissed the recklessness count because Connecticut courts require an unreasonable risk of bodily harm for that tort, and a pattern of declined card transactions did not involve one. It allowed the Connecticut Unfair Trade Practices Act count to proceed at the pleading stage, finding that the allegations could satisfy each of the three criteria Connecticut uses to identify an unfair practice. On loss, the court treated lost business opportunities as a plausible “ascertainable loss” under the Connecticut statute and noted a Connecticut appellate decision holding that emotional distress does not count as an ascertainable loss of money or property. Those holdings are Connecticut law, applied by a federal trial court at the start of a case; other states have their own consumer statutes and their own limits. The practical lesson travels better than the doctrine: a consumer who can show money lost, such as fees, penalties or a canceled sale, is in a far stronger position than one who can show only frustration.
II. What should you do now: notices, fees and the payments the Act does not cover
A. Turn the outage into a documented notice of error
The Act’s error-resolution machinery is the part most consumers can use without a lawyer. Under 15 U.S.C. § 1693f, an “error” includes an unauthorized transfer, an incorrect electronic fund transfer from or to the consumer’s account, the omission from a periodic statement of a transfer that should have been included, a computational error by the institution, the receipt of an incorrect amount from an electronic terminal, and “a consumer’s request for additional information or clarification concerning an electronic fund transfer or any documentation required by this subchapter.” The Bureau’s rule, 12 CFR 1005.11, adds that the covered requests include a request the consumer makes to determine whether an error exists, while a routine inquiry about the account balance, a request for tax or recordkeeping information, or a request for duplicate copies is not an error. The difference is important after an outage: asking “what is my balance?” does not trigger the bank’s legal duties, but a written request asking what happened to a specific transfer, on a specific date, for a specific amount, can.
Timing and content are set by the regulation. Under 12 CFR 1005.11(b)(1), the bank must follow the error-resolution procedure for an oral or written notice that it receives no later than 60 days after it sends the periodic statement on which the alleged error is first reflected, that enables it to identify your name and account number, and that indicates why you believe an error exists, including to the extent possible the type, date and amount of the error. The bank may require written confirmation within 10 business days of an oral notice, but only if it tells you so, and gives you the address, when you call. When your notice of error follows documentation or a clarification you asked for, paragraph (b)(3) makes the notice timely if the bank receives it no later than 60 days after it sends the information you requested. Once a valid notice arrives, paragraph (c)(1) requires the bank to investigate promptly, determine within 10 business days whether an error occurred, report the results within three business days after completing the investigation, and correct an error within one business day after finding it. Under paragraph (c)(2), the bank may take up to 45 days instead, but only if it provisionally credits the account within 10 business days, tells you within two business days of the amount and date of the credit, and gives you full use of the funds during the investigation. Paragraph (c)(3) extends those periods in listed situations: 20 business days in place of 10, and 90 days in place of 45, when the notice involves a transfer made within 30 days after the first deposit to the account, and 90 days in place of 45 when the transfer resulted from a point-of-sale debit card transaction or was not initiated within a state.
If the bank concludes that no error occurred, 12 CFR 1005.11(d) requires a written explanation that notes your right to request the documents it relied on, and it must provide copies promptly on request. If it reverses a provisional credit, it must tell you the date and amount and, for five business days after that notice, honor checks and preauthorized transfers payable to third parties without an overdraft charge, to the extent it would have paid them if the provisional credit had not been debited. The statute adds a strong incentive to take these deadlines seriously. Under § 1693f(e), a consumer is entitled to treble damages if the court finds that the bank did not provisionally recredit within the ten-day period and either did not make a good faith investigation or lacked a reasonable basis for believing the account was not in error, or that it knowingly and willfully concluded there was no error when that conclusion could not reasonably have been drawn from the evidence available to it at the time.
A ruling from this spring shows how a clarification request works in court. In Ghiya v. TD Bank, N.A., No. 25-cv-4056 (D.N.J. Apr. 28, 2026), the United States District Court for the District of New Jersey considered a customer who sent $1,000 by Zelle after a bank representative allegedly told him a deposited check had cleared, then opened a dispute by phone and sent several letters asking for the documents the bank relied on. He alleged that the bank never investigated, never provisionally credited his account and never explained its findings; the bank argued that it had fully complied and pointed to letters it said it sent in April 2024, which the court could not consider at the motion-to-dismiss stage. Taking the allegations as true, the court held that the customer’s requests for information about the transfer were enough, writing that “Plaintiff’s allegations are sufficient to trigger § 1693f via subsection (f)(6),” and it allowed the federal claim to proceed while dismissing his misrepresentation claims under New Jersey’s economic loss doctrine and his New Jersey Consumer Fraud Act claim. The ruling is not a finding that the bank violated the Act. For anyone whose transfer vanished, stalled or posted twice during an outage, Ghiya v. TD Bank shows that a written request for information or clarification about a specific transfer can itself start the bank’s investigation clock under the Act.
The other side of that lesson came from the Fifth Circuit. In Reyna v. Block, Inc., No. 25-50966 (5th Cir. May 18, 2026), an unpublished decision, the United States Court of Appeals for the Fifth Circuit affirmed the dismissal of a consumer’s claim against a payment app and its partner bank. The opinion records that the app had restored the disputed $67.66, and the consumer argued that part of the reimbursement came too late. The court explained that the statutory notice must identify the consumer and account, state the belief that there is an error and its amount, and give the reasons for that belief, and it held that a complaint referring to an undescribed “Litigation Preservation Notice” did not show that a valid notice had been given within 60 days. The point for an outage is simple: keep the text of what you sent, and make sure it contains the account, the transfer, the date, the amount and your reasons.
Put together, a good notice after an outage is short and specific. It names you and the account, lists each affected transaction with its date, amount and confirmation number, says what you instructed and what happened instead, asks the bank to investigate and to explain what happened to each transfer, and asks it to reverse any fee that resulted. Send it in a way you can prove, such as the bank’s secure message center plus a saved copy, or a letter to the address the bank designates for error notices. Mark your calendar from the date of the first statement that shows the problem, because the 60-day period runs from that statement, and from the date of the failed transfer itself, because the one-year period to sue under § 1693m(g) runs from the violation.
B. Late fees, credit cards, overdrafts and wires: where the Act stops
Credit card payments follow a separate federal rule set, the Truth in Lending Act’s Regulation Z. Under 12 CFR 1026.10, a creditor must credit a payment as of the date of receipt, except when a delay does not result in a finance or other charge. A creditor may set reasonable payment requirements, including cut-off times for mail, electronic, telephone and in-person payments, but those cut-off times cannot be earlier than 5 p.m. on the payment due date at the location the creditor specifies. If a creditor promotes a method for making payments, payments made by that method are considered conforming and must be credited as of the date of receipt. Payments made in person at a branch of a card issuer that is a financial institution, before the branch closes, are considered received that day. And if a creditor fails to credit a payment as these rules require in time to avoid finance or other charges, paragraph (c) requires it to adjust the account so that the charges are credited during the next billing cycle. The section read for this guide does not contain an outage-specific rule, and paragraph (d)(2) cuts the other way in one respect: when a creditor accepts electronic or telephone payments on the due date, it is not required to treat a payment made by that method on the next business day as timely. If an outage blocked a card payment on the due date, the practical sequence is to pay by another accepted channel the same day if you can, such as an in-person payment at a branch before closing, keep proof of each failed attempt, and then ask for any resulting fee or interest to be reversed.
Payments to other billers are governed mainly by your contract with that biller. A landlord, utility or lender that is not your bank can charge a late fee under its own terms, and nothing in the provisions read for this guide requires it to waive that fee because your bank had a technical problem. The realistic steps are to make the payment as soon as another channel works, send the biller a short explanation with your evidence, and request a courtesy waiver. If the fee stands, the place to recover it under federal law is the bank, and only if the failed transfer meets the elements of § 1693h(a): a covered transfer, properly instructed, not made in a timely manner under the account terms, with no applicable exit.
Some transfers that people think of as electronic are carved out of the Act. The definitions section excludes, among other things, automatic transfers from a savings account to a checking account made under an agreement to cover an overdraft or maintain a minimum balance, and transfers made by a financial institution through a service that moves funds held at Federal Reserve banks or other depository institutions and that is not designed primarily to transfer funds on behalf of a consumer, other than transfers processed by automated clearinghouse. The Bureau’s coverage rule, 12 CFR 1005.3, says the term electronic fund transfer does not include any transfer of funds through Fedwire or a similar wire transfer system used primarily for transfers between financial institutions or between businesses, and it separately excludes certain automatic transfers between a consumer’s own accounts at the same institution made under an agreement without a specific request. An overdraft-protection sweep that misfired during an outage is therefore usually a contract question under the account agreement rather than a question for the federal transfer statute.
Wires are the clearest example. In Nazimuddin v. Wells Fargo Bank, N.A., No. 24-20343 (5th Cir. Jan. 6, 2025), an unpublished decision, the Fifth Circuit affirmed the dismissal of a consumer’s federal claim over three wire transfers totaling $23,657.71 that he said he had not made; according to the opinion, the bank’s investigation had concluded that he or someone with his login credentials made them. The court held that the transfers, being wire transfers, were outside the scope of the Act, and it noted that the district court had dismissed his contract claim because he did not identify the provision of the online access agreement the bank allegedly breached. If a wire you sent during an outage went astray or was delayed, the federal transfer statute will generally not be your tool; your rights depend on the wire agreement and on state law, and any contract claim needs to point to a specific promise in the documents.
Outages and fraud are different problems with different rules, and they sometimes arrive together, because scammers like to exploit moments when customers are anxious and cannot see their balances. If money left your account because someone else initiated the transfer, the unauthorized-transfer rules apply instead of the failed-transfer rule discussed here; our guide on who pays if a thief drains your bank account walks through those liability tiers and reporting deadlines. During and after any outage, use only the bank’s own app, website or the number printed on your card, and treat unsolicited calls or texts offering to “fix” a stuck payment with suspicion.
Finally, build the file while the facts are fresh. Useful items are screenshots of error messages with the time visible, confirmation or reference numbers for each attempted transfer, the account statement on which each problem first appears, the bank’s public statements about the outage, any fee or overdraft notice, any late-fee notice from a biller, and copies of every message you send. If a fee hits, ask for its reversal in writing and say that you are also requesting an investigation of the underlying transfer. Most outage problems end there, because banks often reverse fees and reprocess payments once the systems recover. The statute’s remedies matter for the cases that do not resolve: the transfer that never happened, the fee the bank will not reverse, the investigation that never comes.
Conclusion
A bank outage is mostly an inconvenience, but it can become a legal problem when a payment fails, a deposit does not post or a fee follows. For consumer accounts, federal law is clearer than most people expect. A bank is liable for damages proximately caused by its failure to make a properly instructed transfer in the correct amount or in a timely manner under the account terms, subject to defenses for circumstances beyond its control handled with reasonable care, for malfunctions you knew about when you tried, and for bona fide errors, and no account agreement can waive those rights. The error-resolution rules give you a concrete lever: a specific written notice, within 60 days of the statement that first reflects the problem, starts deadlines the bank must meet, and a request for clarification about a transfer can be enough. Credit card payments follow their own crediting rules, wires and certain automatic sweeps fall outside the transfer statute, and a lawsuit under the Act must be filed within one year of the violation. Keep the evidence, write early, and measure every claim against the exact words of the statute and of your account terms.