MySchoolBucks Fees: What District Administrators Can Do

The board packet on Linda Reyes’ desk had item 4b underlined in red ink. Constituent inquiry: MySchoolBucks per-transaction fee — staff response and board options for the May meeting.
Linda had been the business manager at Toledo Public Schools for eleven years. She knew the cooperative purchasing agreement that put MySchoolBucks on the parent portal, she knew the line on the parent’s deposit receipt that said “Program Fee — $3.25,” and she knew that until the constituent inquiry hit the board agenda, MySchoolBucks fees had been a quiet fact of life for everyone involved. The fee was disclosed. The cooperative agreement was public. Three of the surrounding districts in the cooperative ran the same arrangement.
What had changed wasn’t the fee. What had changed was that one parent had read the July 2024 Consumer Financial Protection Bureau report on school payment processor fees, walked it to the board, and asked the board to do something about it. And now Linda was the staff member assigned to draft the response.
The honest version of a board response on MySchoolBucks fees is the one most district business officers haven’t had to write yet — and the one most boards aren’t quite ready to hear. The federal regulatory pressure that produced the CFPB report has, since the report’s release, mostly evaporated. The class-action lawsuit that hung over Heartland’s MySchoolBucks fees has settled. The fee itself has not gone anywhere, and is unlikely to. But the operational levers a district administrator actually has — the ones Linda would write into the staff response — are still live, more so than people realize. This is what they look like.
What’s actually being charged, and to whom
The fee that lands on a parent’s MySchoolBucks deposit confirmation is a per-transaction program fee charged by Heartland Payment Systems (a Global Payments subsidiary since 2016) to the parent — not to the district. The current fee structure as of the 2025-26 school year is $3.25 per credit or debit card transaction, charged regardless of deposit amount. E-check (ACH) deposits run lower, typically $2.75 per transaction or less, and some districts have negotiated zero-fee e-check.
The CFPB’s July 2024 sample of the 300 largest US public school districts found the average per-transaction fee was $2.37 (or 4.4% of the transaction). MySchoolBucks raised its credit/debit fee to $3.25 effective August 1, 2025 — putting it at the top of the range the CFPB had documented one year earlier.
The structural detail that makes MySchoolBucks fees a different conversation than your district’s merchant processing relationship: the parent pays the fee directly. The district’s contract with Heartland for cafeteria POS, food-service software, USDA reimbursement reporting, and free-and-reduced-lunch eligibility is a separate commercial relationship. That relationship, which most districts negotiated through TIPS, E&I Cooperative Services, Choice Partners, OMNIA Partners, or a state-level cooperative, runs separately from MySchoolBucks fees and can have a different fee structure entirely — and is the subject of the broader Heartland alternatives conversation for K-12 schools if your district is also evaluating its merchant-side relationship.
This post is about the parent-side MySchoolBucks fees only. The MySchoolBucks fees structure described below is what shows up on parent receipts; everything else is a separate conversation at the board.
The Federal Pressure Linda’s Constituent Was Citing — And Where It Stands Now
The parent who walked into the Toledo Public Schools board room with the CFPB report on MySchoolBucks fees and the parallel platforms had read it correctly. The findings were strong. The political environment around them, since, has shifted.
What the CFPB report on MySchoolBucks fees and parallel platforms actually found
The CFPB’s Issue Spotlight: Costs of Electronic Payments in K-12 Schools sampled the 300 largest US public school districts and found that 87% contract with payment processors for online lunch payments. Across that sample, processors charge an average of $2.37 or 4.4% per transaction, collectively extracting between $30 million and $102 million annually from families. The report identified three dominant platforms — MySchoolBucks (Heartland), SchoolCafe (Cybersoft), and LINQ Connect (EMS LINQ, ~30% of districts).
The most cited finding from the report, and the one Linda’s constituent had highlighted: families who qualify for reduced-price lunch may pay up to 60 cents in fees for every dollar they actually spend on lunch. The report classified these fees as “junk fees” and noted that despite USDA’s National School Lunch Program requirement to offer fee-free cash/check payment options, those options are “not always well advertised or accessible.”
What’s happened to that pressure since
The CFPB itself has been functionally dismantled. In February 2025, acting director Russell Vought ordered staff to stop work, attempted to lay off ~88% of employees, and announced the agency would not draw further funding. Federal courts blocked the most aggressive shutdown actions, but the agency’s enforcement capacity has been gutted. As of early 2026, the CFPB is — in the words of one industry analysis — “an agency on paper only.”
The class-action lawsuit that had been the secondary pressure point on MySchoolBucks fees, Story v. Heartland Payment Systems, settled. Heartland agreed to pay $18.25 million, the court granted final approval on September 25, 2025, and payments began distribution to claimants on January 9, 2026. The settlement covered fees charged between June 2013 and July 2019. The lawsuit is closed and provides no further leverage going forward.
What this means for Linda’s response
Two consequences. First, the framing in Linda’s draft response cannot lean on “federal action is coming, so we should get ahead of it.” That framing, which would have worked in late 2024, no longer reflects reality. Second — and this is the more useful point — the CFPB’s findings remain in the public record and remain citable as a negotiating instrument, even though the agency that produced them isn’t enforcing anything. A district business officer sitting across the table from a cooperative purchasing coordinator at contract renewal can still cite the report’s conclusions. The state legislators who’d want to hear about junk fees in school payment systems can still cite the report. The findings haven’t been rescinded; only the enforcement apparatus has weakened.
The honest version of Linda’s response separates “we should expect regulators to fix this” (no, mostly not) from “we have operational levers we can pull right now” (yes, and they don’t depend on federal enforcement).
What a District Business Officer Can Actually Do About MySchoolBucks Fees
In order of difficulty, lowest to highest. Each lever is independently actionable on MySchoolBucks fees; districts can pursue any subset without committing to all four.
Lever 1: USDA fee-free disclosure compliance
What it is: Districts participating in the National School Lunch Program are required to offer fee-free payment options (cash or check) as an alternative to MySchoolBucks fees. The CFPB report’s most damaging finding for districts — separate from the fees themselves — was that fee-free options were “not always well advertised or accessible.” An audit of how fee-free options are disclosed on your district’s web pages, parent communications, enrollment packets, and MySchoolBucks portal language is a 30-day project that requires no vendor cooperation.
Why it matters: Even if zero parents shift to cash/check after the audit, the disclosure improvement insulates the district from the most likely class-action theory that would replace Story v. Heartland in the next regulatory cycle on MySchoolBucks fees — failure to disclose, not the fee itself.
What it costs: Staff time. Maybe a small parent-communication line item.
Who needs to approve: Superintendent, ideally board sign-off on the parent communications update.
Lever 2: E-check default switching in the parent portal
What it is: MySchoolBucks (and the other major platforms) charge lower fees for ACH/e-check transactions than for credit or debit. At MySchoolBucks current pricing, the gap is roughly $0.50 per transaction ($2.75 vs. $3.25). Most cooperative purchasing agreements allow districts to configure the parent portal’s default payment method. Switching the default from credit/debit to e-check captures the lower fee for any parent who doesn’t actively change it back.
Why it matters: A 30-50% take rate on e-check defaults across a district doing $1M+ in MySchoolBucks volume is real money — typically $15K-$30K per year in MySchoolBucks fees savings that stay in family pockets rather than going to processor fees. Doesn’t require renegotiating the cooperative agreement.
What it costs: A configuration change request to the cooperative purchasing coordinator and a parent communication explaining the change.
Who needs to approve: Business office; cooperative purchasing coordinator if the change requires their action.
Lever 3: Cooperative agreement fee-cap addendum at next renewal
What it is: Cooperative purchasing agreements typically run 3-5 years. At renewal, member districts can request addenda or modifications. A fee-cap addendum can take several forms: a hard cap on per-transaction fee escalation (e.g., “fees may not increase more than 3% annually without member vote”), a sliding scale for low-income families (reduced-price-lunch families get reduced or zero fees), or a fee-revenue-sharing model where a percentage of MySchoolBucks fees revenue from member districts comes back as a vendor rebate.
Why it matters: Cooperatives have leverage individual districts don’t. A 30-district cooperative renegotiating jointly can move a vendor in ways one district can’t. The catch: cooperatives move slowly, vendors push back, and the timing has to align with renewal cycles.
What it costs: Sustained engagement with the cooperative purchasing coordinator and member-district business officers on the MySchoolBucks fees renegotiation, typically 12-18 months of preparation before renewal.
Who needs to approve: Cooperative member vote, district board sign-off on participation in the renegotiation.
Lever 4: District-absorbs-fee model
What it is: The Minneapolis Public Schools template, documented in the CFPB report itself: the district covers part of the per-transaction fee from cafeteria budget or operating funds, leaving families with a smaller residual fee. MPS pays $1.60 of LINQ Connect’s $2.60 fee; families pay $1.00. The model is reproducible at any district willing to absorb the cost.
Why it matters: Most direct relief for families. Doesn’t require vendor cooperation, doesn’t require cooperative renegotiation, doesn’t require waiting for federal enforcement that isn’t coming. The district makes a budget decision and the relief is immediate.
What it costs: Real money. For a district doing 50,000 MySchoolBucks transactions per year, absorbing $1.50 per transaction is $75,000 from the cafeteria or operating budget. The political question is whether the district treats MySchoolBucks fees as a permanent cost of doing business with cashless cafeteria payments, or a temporary measure pending other levers landing.
Who needs to approve: Board vote on the budget allocation, ideally as a multi-year commitment.
For Linda’s draft staff response, the recommendation would be: pursue Levers 1 and 2 in the next 90 days as a no-budget-impact action, schedule Lever 3 preparation for the cooperative’s next renewal cycle, and present Lever 4 to the board as a budget option with full cost analysis but without staff recommendation either way. That last call belongs to the board.
Why This Is Harder Than the Levers Make It Sound
Each of the four levers is real. Each of them also runs into resistance that’s easy to miss when reading a strategy memo from outside.
Cafeteria budget pressure. Cafeteria operations at most districts run on thin margins, and absorbing parent-side MySchoolBucks fees (Lever 4) means either cutting elsewhere in the cafeteria budget or pulling from the operating budget — which means cutting elsewhere in the operating budget. Boards typically don’t pass budget allocations of $50K-$200K without a longer conversation than a single board meeting affords.
USDA non-program food rule. The Healthy, Hunger-Free Kids Act includes a non-program food rule (7 CFR 210.14(f)) requiring districts to recoup the full cost of food sold outside the federally reimbursed meals program. Some districts have interpreted absorbing payment fees as potentially conflicting with this rule. The conservative read is that the absorption applies to the meal program itself (which is fee-allowable), not to non-program food. But the rule creates enough ambiguity that some districts decline to absorb fees on advice of legal counsel rather than risk an audit finding.
Vendor relationship and SIS integration. If the district is using Heartland for both MySchoolBucks (parent portal) and the underlying nutrition compliance and SIS integration with PowerSchool or Skyward, putting pressure on the parent-fee side can affect the broader vendor relationship. This is more felt than documented — vendors won’t put it in writing — but business officers report that aggressive parent-fee renegotiation can cool the support relationship on the compliance side. Worth weighing.
Parent fatigue and convenience tradeoff. Not all parents want the district to renegotiate. The parents using MySchoolBucks at scale typically value the convenience over the fee. Parents who object loudly to the fee are often the same parents who would benefit most from switching to the fee-free cash/check option but find the option logistically unworkable (drop-off times, work schedules, language barriers in disclosure). Lever 1 (better disclosure of the fee-free option) is the cleanest response to this segment. Lever 4 (district absorbs the fee) is the second-best response. Levers 2 and 3 help everyone but slowly.
The honest framing in Linda’s response: “We have four options on MySchoolBucks fees. None of them are free. The combination most likely to produce real relief for families without straining the cafeteria budget is Levers 1 + 2, with Lever 3 prepared for our cooperative’s next renewal in 2027. Lever 4 deserves a separate board conversation about whether the district treats payment-processor fees as a parent cost or a district cost.”
Frequently Asked Questions
Yes, generally — districts can use cafeteria budget funds to subsidize per-transaction MySchoolBucks fees on meal-program transactions. The complication is the USDA non-program food rule (7 CFR 210.14(f)), which requires full cost recovery on food sold outside the reimbursed meals program. The conservative read: absorption applies to meal-program transactions but not non-program ones (à la carte, adult meals, summer-program sales), so it must be transaction-coded by category. Talk to your state child nutrition director and auditor before the board vote.
No. The compliance and chargeback protections sit on the district’s merchant processing relationship (its cafeteria POS contract), not on the parent’s payment method. Parents can still choose credit/debit; the default change just shifts which method is preselected. Some districts see 30–50% take rates on the new default, capturing the e-check fee differential at scale. Configure it with the cooperative purchasing coordinator and pair it with transparent parent communication.
Aggregated, the leverage is real. Cooperatives like TIPS, E&I, Choice Partners, and OMNIA Partners exist to aggregate purchasing power — a 30-district co-op renegotiating jointly at renewal can move terms an individual district can’t. The catch: it only works if members coordinate before the renewal vote, usually a 12–18 month lead time. Fee-cap addendums, low-income sliding scales, and revenue-share rebates are all things vendors concede under cooperative pressure but not bilaterally. Timing must align with your co-op’s renewal cycle.
No. Story v. Heartland Payment Systems settled for $18.25 million, received final approval September 25, 2025, and paid claimants beginning January 9, 2026 — the case is closed, with no admission of liability. It covers parents who paid MySchoolBucks fees between June 2013 and July 2019; it does not extend forward and carries no ongoing court oversight of fee structures. Use the CFPB report findings (still public record) and the operational levers above for leverage — not the lawsuit.
Switching parent-side processing mid-contract is harder than merchant-side because the cooperative agreement, USDA reporting integration, and SIS link are usually bundled with MySchoolBucks (or LINQ Connect, SchoolCafe — same logic). A clean switch typically waits for the cooperative renewal cycle. Exiting the co-op to bring compliance in-house is a 12–18 month project usually justified only by other reasons (size threshold, co-op dysfunction, contract dispute). For most districts the renegotiation lever is the cooperative agreement, not a unilateral switch. The merchant-side picture, where the district is the customer, is more flexible — that’s the conversation in Heartland alternatives for private K-12 schools.
More on School Payment Processing and Cooperative Agreements
If You’re Drafting a Board Response on MySchoolBucks Fees
Send us your current cooperative purchasing agreement and the most recent MySchoolBucks fee disclosure. We’ll map the four levers above against your specific cooperative, your renewal cycle, and your current fee structure — and tell you honestly which combination is realistic for your district this year vs. which belongs in the next renewal cycle’s preparation docket. No cost. No vendor pitch.
Request a Cooperative Agreement ReviewNo obligation • For school district business officers and cooperative purchasing coordinators • Response within one business day