For SNAP systems, paying less was harder than paying nothing
During the 2025 shutdown, court orders pushed states toward partial and then full November SNAP payments within days. Eligibility logic, EBT issuance and public communication were each built for benefits paid in full or not at all.
Looking Back revisits one week at a time, from January 2020 to today, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
The week
The federal shutdown that began on October 1, 2025 left November SNAP funding in doubt. On October 31, federal judges in Rhode Island and Massachusetts ruled that the administration had to use contingency funds to pay benefits. USDA said it would pay partial November benefits, first signaling about half of the usual amount and then, in revised guidance on November 5, up to 65% of the maximum allotment.
On November 6, the Rhode Island court ordered full November payments, and some states began issuing them. Late on November 7, Justice Ketanji Brown Jackson granted an administrative stay of that order. The next day USDA told states that full-benefit issuances were unauthorized and should be undone. The shutdown ended on November 12 with a law that funded SNAP for the rest of the fiscal year.
The politics of that fortnight are well covered elsewhere. The narrower question is what it revealed about the systems that deliver benefits. States were asked to pay a fraction of a benefit, then possibly the whole benefit, under instructions that changed within days. Stopping payment entirely would have been simpler, since every system already handles a month with no issuance. Paying a reduced, recalculated amount was the hard case. The strain showed in three places, each with a different owner: the benefit calculation logic, the issuance rails, and communication with recipients.
Calculation logic: no setting for “partial”
State eligibility systems calculate SNAP benefits from household size, income and deductions, within federal rules. They are built to calculate the correct benefit, not a percentage of it. USDA’s revised method reduced the maximum allotment and then subtracted 30% of household net income, as the normal formula does. Many households therefore received less than 65% of their usual benefit, and some households with income could see the amount fall to zero. Interactions with minimum benefits, prorated first-month benefits and mid-month changes added edge cases.
Several states said publicly that recalculating at a reduced level would take days or weeks. Some had to choose between speed and precision. The underlying issue is configurability. Many state eligibility systems are large, heavily customized platforms in which a change to benefit logic goes through a full release cycle, often with a systems integrator. That process suits policy changes made through legislation and rulemaking. It fits poorly when the policy may change again before the release ships.
Agencies can reduce this risk in advance. A parameterized control can apply a percentage, a cap or an alternative formula across a caseload, with defined rules for edge cases. Policy staff should be able to switch it on with recorded approvals rather than a code release. It needs testing against real caseload data every year, the way disaster recovery is tested. Contracts with integrators should treat emergency benefit changes as a defined service with a response time, not a change request priced after the fact.
Issuance rails: the EBT processor in the middle
SNAP benefits reach households through electronic benefit transfer cards. A small number of processors run EBT systems for the states. Issuance files move from the state system to the processor on a schedule, often staggered by case number or last name across the month. Changing the amount, timing or sequence of those files at short notice depends on the processor’s capacity and contract terms as much as on the state.
November also exposed a question few agencies had planned for. What happens if benefits are issued and the legal basis then changes? USDA’s November 8 instruction to undo full issuances ran into the reality that loaded funds can be spent within hours. Reversing them would be operationally difficult and would damage trust in the program. Benefits issued under legal uncertainty are, in practice, final.
That has design consequences. Agencies should agree procedures with their processors for staged, delayed or supplemental issuance before they need them. A supplement, issued later to top up a partial payment, is far easier than a clawback. Issuance decisions during litigation should carry a documented legal and program sign-off, because they cannot be walked back. Reconciliation between the state system and the processor should be able to report, per household, what was issued under which instruction.
Communication: telling people what they will get
The third strain fell on recipients. They needed to know whether they would be paid, how much and when. Agencies answered through websites, call centers, text messages and community partners while the answer itself kept moving. Because the reduced formula hit households differently, a single percentage in a press release was misleading for many of them.
Call volumes rose, and caseworkers fielded questions they could not answer. Food banks and community organizations became de facto information channels and absorbed demand. Agencies with established text messaging programs and plain-language status pages could update people quickly. Those relying on mailed notices and general press releases could not.
Good practice is not complicated, but it must exist before the crisis. Keep one authoritative status page per program, in plain language and timestamped. Use direct channels, such as text and app notifications, that recipients have already opted into. Where the system can show each household its own expected amount through a portal or balance inquiry, do that rather than quoting averages. Brief call center staff and community partners from the same script at the same time, and say clearly what is not yet known.
Language access and retailer communication are easy to forget under pressure. Updates should go out in the languages the agency already uses for notices, at the same time as the English version. Grocers and farmers markets that accept EBT also field questions at the register, and a short bulletin through retailer associations reduces confusion at the point where recipients feel it most.
All three strains come from one assumption: that benefits flow on a stable monthly cycle in full amounts. Shutdowns, disasters and court orders break that assumption. Building for variability in calculation, issuance and communication is a resilience investment that agencies will use again.
With hindsight
The law that ended the shutdown on November 12 funded SNAP through September 30, 2026, so the most difficult scenarios did not play out at scale. USDA said it would release full November funding promptly, though some states took days to complete issuance.
The episode remains relevant because the same systems face more change. The July 2025 reconciliation law expanded SNAP work requirements, raised states’ share of administrative costs from fiscal 2027, and ties a share of benefit costs to state payment error rates from fiscal 2028. Each of those changes runs through the same eligibility logic and issuance rails. Agencies with configurable benefit parameters, pre-agreed processor procedures and direct messaging channels are better placed for the next disruption. The test for any benefits platform is whether it can pay less, pay later or pay in stages under clear controls, and tell each household the same day.