Overdraft and non-sufficient funds (NSF) fees are supposed to be predictable: you don’t have enough money, you get charged. But regulators have warned that some fee setups can create unexpected charges that consumers couldn’t reasonably anticipate, leading to real financial harm.
Below is a consumer-friendly guide to the fee practices that raise the biggest red flags—and the steps you can take to avoid or dispute them.
The two fees people mix up
Overdraft fee: Your institution pays a transaction even though your account didn’t have enough money, and charges you for covering it.
NSF fee: Your institution declines/returns a transaction (like a check or ACH payment) because you didn’t have enough money—and charges you for the return.
Both can be expensive, but the biggest problems tend to come from how transactions are authorized, processed, and re-tried behind the scenes.
Red-flag fee practice #1: “Authorized Positive, Settled Negative” overdraft fees
This is one of the most commonly criticized “gotcha” patterns:
- A debit card transaction is approved when you have enough money (authorized on a positive balance),
- But later—because of timing, holds, or other transactions—the purchase posts when your account is negative,
- And an overdraft fee is charged even though the purchase looked safe when you made it.
How to reduce the risk
- Keep a small buffer in checking (even $25–$100 can help).
- Turn on low-balance alerts.
- Ask whether your institution assesses overdraft fees based on available balance vs. current/ledger balance, and how debit-card holds work.
Red-flag fee practice #2: Multiple NSF fees on the same payment
Sometimes a merchant (or biller) will re-submit a payment after it bounces. If your institution charges an NSF fee each time the same item is re-presented, a single missed payment can trigger multiple NSF fees. Regulators have specifically flagged this as a consumer harm risk.
How to reduce the risk
- If a payment bounces, contact the biller quickly and ask them not to re-present automatically (or ask when they will retry).
- If you see repeat NSF fees tied to the same merchant for the same amount/date pattern, ask your institution whether they can waive repeat-presentment fees.
Red-flag fee practice #3: Fees triggered when you couldn’t reasonably anticipate them
Regulators have emphasized problems where consumers couldn’t reasonably predict the fee outcome based on what they saw at the time (for example, how balances display, how holds work, or how posting order and timing create the fee).
How to reduce the risk
- Don’t rely only on a single “balance” number—look at pending transactions and holds.
- Avoid running your account near $0 if you have scheduled payments or frequent small card purchases.
A quick checklist to “clean up” your account settings
- Confirm your overdraft setting for debit/ATM transactions (opt-in vs. opt-out).
- Link a backup source (like savings) if your institution offers transfers that are cheaper than overdraft fees.
- Enable alerts (low balance, large transactions, daily balance).
- Review your last 2–3 statements for patterns:
- overdraft fees after debit transactions that seemed approved normally
- multiple NSF fees tied to the same merchant/payment being retried
If you were charged: what to ask for (script-style)
When you call or message support, ask:
- “Was this fee related to an authorized positive, settled negative transaction?”
- “Was this NSF fee charged multiple times because the same payment was re-presented?”
- “Can you refund these fees as an accommodation and note my account to prevent repeat fees on re-presentments?”
If the explanation doesn’t match what your balance/history showed at the time, ask them to provide the authorization time, posting time, and the balance type used (available vs. current) for the fee decision.