ACH Unauthorized Debits WSUD Refund Timing Issues
Unauthorized ACH withdrawals can drain an account fast; knowing WSUD steps helps correct errors and recover funds sooner.
ACH debits are designed to make bill payments and subscriptions easy, but the same system can be used for unauthorized pulls that are hard to notice until the balance drops or fees start stacking up.
When an ACH debit was not authorized, timing and documentation matter. A clear notice to the bank, a proper Written Statement of Unauthorized Debit (WSUD), and organized evidence can shape how quickly the dispute is handled.
- Delays can increase overdraft fees and missed payments
- Deadlines can limit reimbursement or provisional credit
- Wrong dispute framing may be treated as a “stop payment” only
- Incomplete facts can slow investigations and reversals
Quick guide to ACH unauthorized pulls and WSUD
- What it is: An ACH debit withdrawn from a consumer account without valid authorization.
- When it shows up: Subscriptions, “trial” offers, account takeovers, fake billers, or merchant data leaks.
- Main legal framework: EFTA / Regulation E for consumer electronic fund transfers (with some limits).
- What gets worse over time: Fees, cascading payment failures, and longer resolution time.
- Basic path: Notify the bank, identify each unauthorized entry, submit a WSUD when required, track the investigation timeline, and escalate if needed.
Understanding ACH unauthorized debits in practice
ACH (Automated Clearing House) debits are “electronic fund transfers” used for recurring payments (rent portals, utilities, memberships) and one-time debits (online bill pay). Many disputes happen because an authorization was never given, was obtained by deception, or was revoked but debits continued.
In practice, banks often separate these situations into categories that affect how they process the claim. Describing the issue accurately helps the bank route the dispute correctly.
- Unauthorized debit: no permission was given, or an account takeover initiated the debit.
- Authorization revoked: permission existed, then was canceled, but debits continued.
- Wrong amount/date: permission existed, but the debit did not match what was agreed.
- Stop-payment need: future debits must be blocked while the dispute is pending.
- Business vs consumer account: protections can differ depending on account type and circumstances.
- Identify each entry: date, amount, company name, and trace/reference details
- Use clear wording: “I did not authorize this ACH debit” (or “authorization was revoked on…”)
- Ask about WSUD: some banks require it to finalize the claim
- Request fee review: overdraft and NSF fees linked to the unauthorized debit
- Block repeats: place a stop payment or ACH block where appropriate
Legal and practical aspects of ACH disputes
For consumer accounts, Regulation E sets a framework for error resolution. Typically, a consumer must notify the bank promptly after discovering the issue, and banks must investigate and correct confirmed errors within defined timeframes.
Many banks can take notice by phone, chat, branch, or secure message, but they may require a written follow-up. A WSUD is commonly used to document that an ACH debit was unauthorized and to lock in the dispute details.
- Notice window: often tied to the statement cycle, so monitoring statements matters.
- Investigation timeline: banks may provide provisional credit while investigating in certain cases.
- Evidence standard: a WSUD and supporting records help validate the claim quickly.
- Stop-payment vs dispute: stopping future payments does not automatically reverse past debits.
Important differences and possible paths
ACH issues can look similar on an account statement, but the remedy can differ. An account takeover or a debit from a fake “merchant” is handled differently than a legitimate merchant that failed to stop charging after cancellation.
- Account takeover: secure the account first (passwords, new account number, device checks), then dispute entries.
- Revoked authorization: provide proof of cancellation and request reversal plus future blocks.
- Wrong amount: document the agreed amount and request correction for the difference.
Possible paths often include: resolving directly with the bank’s dispute team, submitting a complaint to the appropriate regulator if the process stalls, or seeking legal help when large losses or repeated failures occur. Each path depends on the amount, the bank response, and the documentation quality.
Practical application of WSUD in real cases
WSUD is most relevant when the bank needs a signed statement describing why the ACH debit was unauthorized. The goal is to clearly state what happened, list each transaction, and confirm that no permission was granted (or that permission was revoked).
Common situations include “free trial” sign-ups that turned into recurring debits, fraudsters using routing/account numbers, or companies with confusing names that make the charge hard to recognize until it repeats.
Useful evidence often includes bank statements, screenshots of cancellation attempts, emails confirming cancellation, chat logs with the merchant, police report numbers (when appropriate), and notes about when the issue was discovered.
- Collect the details: list every unauthorized ACH debit with date, amount, and description from the statement.
- Notify the bank promptly: state clearly whether it was unauthorized, revoked authorization, or wrong amount.
- Ask for the WSUD form or method: confirm how to submit it and by when, and keep proof of delivery.
- Request protective actions: stop payments, ACH blocks, account number change, and fee review if charges caused overdrafts.
- Track deadlines and follow-ups: write down case numbers, agent names, and promised dates for updates or credits.
Technical details and relevant updates
Regulation E disputes often turn on timing. The sooner the bank receives notice after the consumer discovers the problem, the easier it is to prevent repeat debits and limit downstream fees.
Banks may require a written confirmation after an initial oral notice. In those situations, the WSUD functions as the written record of the claim, and incomplete statements can slow the investigation.
Separately, ACH network rules and internal bank procedures may affect how returns and reversals are processed, especially when a debit is old, repeated, or tied to a complex merchant chain.
- Confirm account type: consumer protections may differ from business-account handling.
- Clarify classification: unauthorized vs revoked authorization vs wrong amount.
- Prevent repeats: a dispute alone may not stop new debits from posting.
- Keep a clean paper trail: case number, submitted documents, and timestamps.
Practical examples of ACH unauthorized debit disputes
Example 1 (more detailed): A consumer notices two ACH debits labeled with an unfamiliar company name. After checking email and subscriptions, nothing matches. The consumer contacts the bank the same day, states the debits were not authorized, and requests a stop on future ACH debits from that payee name.
The bank provides a WSUD form. The consumer lists each transaction, states no authorization was given, and attaches a short timeline showing when the account was reviewed and when the bank was notified. The consumer also requests reversal of overdraft fees triggered by the debits. The bank opens an investigation and provides an update timeline, with provisional credit discussed depending on internal policy and the claim details.
Example 2 (shorter): A consumer canceled a subscription but an ACH debit posted again the next month. The consumer submits proof of cancellation and asks the bank to treat the debit as unauthorized after revocation, while placing a stop payment to block future pulls.
Common mistakes in ACH unauthorized debit cases
- Waiting too long to review statements and report the unauthorized entry
- Reporting only one transaction when multiple related debits exist
- Requesting a stop payment but not opening a dispute for the posted debit
- Submitting a WSUD with missing dates, amounts, or unclear authorization details
- Failing to prevent repeats (no block, no stop payment, no account security update)
- Not requesting fee review for overdrafts caused by the unauthorized withdrawal
FAQ about WSUD and ACH unauthorized withdrawals
What is a WSUD in an ACH dispute?
A WSUD is a Written Statement of Unauthorized Debit used by many banks to document that an ACH debit was not authorized (or that authorization was revoked). It typically lists each disputed entry and confirms key facts in writing, which helps the bank process the investigation.
Does a stop payment automatically get money back?
No. A stop payment is mainly about preventing future debits from posting. To recover funds for a debit that already posted, the bank usually needs a dispute opened under the applicable error-resolution process, often supported by a WSUD.
What documents help the bank resolve an unauthorized ACH debit faster?
Helpful items include statements showing the debits, any cancellation confirmation, emails or chat transcripts with the merchant, screenshots of account settings, and a short timeline. If there are signs of account takeover, records of password changes and device/security actions can also be relevant.
Legal basis and case law
Unauthorized ACH debits in consumer accounts are commonly analyzed under the Electronic Fund Transfer Act (EFTA) and its implementing rule, Regulation E (12 CFR Part 1005). The framework generally covers error resolution for electronic fund transfers, including investigation duties and correction mechanisms when an unauthorized transfer is confirmed.
In practice, outcomes often depend on whether the transfer was truly unauthorized versus a transfer the consumer initiated but later regretted (for example, certain scam scenarios). Dispute handling also depends on whether the account is a consumer account and whether notice and documentation were provided in a timely, consistent way.
Courts and regulators evaluating these disputes often focus on authorization, revocation, and the bank’s compliance with procedural obligations, including whether the institution followed the required steps for receiving the claim, investigating, and correcting confirmed errors.
Final considerations
Unauthorized ACH pulls can trigger a chain reaction: fees, missed bills, and repeat withdrawals. A disciplined approach—fast notice, accurate transaction listing, and a complete WSUD—improves the odds of a clean, timely resolution.
Separating the issue into the correct category (unauthorized, revoked authorization, wrong amount) and preventing repeat debits (stop payment or ACH block) can be just as important as the dispute itself.
This content is for informational purposes only and does not replace individualized analysis of the specific case by an attorney or qualified professional.

