The Day-58 R10
Wellness Club Billing (WCB) originates WEB debits for 22,000 gym memberships through a Third-Party Sender, Zephyr Payments, to ODFI Summit Bank. On March 3 Summit receives a return from member D. Okafor's bank: $39.99, R10 (customer advises not authorized), transmitted on day 58 after the original settlement date. WCB's billing platform automatically retries returned items three calendar days later with a new "retry" sequence number; in February it retried this same R10 item twice. Okafor had phoned WCB in month three to cancel. The representative typed "member cancelled" into a free-text notes field, sent no confirmation, and the account was not suppressed from the billing file until month five.
1. Is the R10 timely, and may Summit Bank dishonor it?
Read the worked answer
Timely. R10 is one of the codes the Rules allow an RDFI to use when a consumer says the entry was not authorized, and for those codes the RDFI's window is 60 calendar days from the settlement date of the original entry - far longer than the two-banking-day window that governs ordinary returns. Day 58 is comfortably inside it.
Timeliness is measured by when the RDFI transmits the return (its settlement date), not by when Summit receives it. Two days in transit do not make a day-58 return late.
Dishonor is not available. A dishonored return is a narrow remedy aimed at defective returns - untimely returns, wrong trace numbers, field errors, or a return of an entry the RDFI already returned. "The member actually did authorize it" is a factual dispute about the underlying transaction, not a defect in the return itself. Summit must accept the return, pass it to Zephyr and WCB, and let the authorization warranty process and the RDFI's Regulation E investigation run their course.
2. May WCB retry or re-originate the item? What is the significance of the two February retries?
Read the worked answer
No. R10 is not a funds-availability return. R01 and R09 tell you the money was not there; R10 tells you the authorization is missing or was revoked. Re-originating after an unauthorized return requires a new authorization obtained from the receiver, not a retry flag on the old one.
Okafor's phone call is the more serious problem. A consumer may revoke an authorization by any reasonable means, and revocation is effective when received. The representative's note is evidence that revocation was received in month three - which means every debit after that point, including both February retries, was originated without authorization regardless of what the original enrollment said.
The retries compound the exposure in two directions: retrying the same returned item without new authorization violates the limits on reinitiating returned entries, and if the retries ever did post, they created duplicate-entry (R24) exposure. The platform rule should be explicit: R01/R09 may re-enter the retry queue within the Rules' limits; R05/R07/R10/R29 stop the queue until the Originator produces a fresh, documented authorization.
3. What should Summit and Zephyr do now, beyond processing this one return?
Read the worked answer
Treat the return as a signal and work the account, not the item.
Summit (ODFI): (1) pull WCB's return rates - overall and unauthorized - because an elevated unauthorized rate for a WEB originator is a standard trigger for ODFI action; (2) demand the authorization evidence for this account: enrollment record, timestamp/IP log, the exact authorization language, and proof the consumer received a copy; (3) test whether the platform's retry logic can fire after an unauthorized return and require it be corrected if it can; (4) consider a temporary limit or suspension of WCB's WEB origination while the answer is pending.
Zephyr (TPS): must perform the same due diligence on WCB that Summit would perform itself, supply Summit the information it needs to meet its Rules obligations, and carry the contractual consequences if WCB's practices are non-compliant.
The allocation of responsibility does not move with the processing: Summit remains answerable to the network even though Zephyr touches the files.