This bill restricts what payment vendors can charge for school meal collections, requires districts to offer at least one payment method without fees, and forces clear, upfront disclosure of any platform charges. It tasks the Rhode Island Department of Education (RIDE) with writing uniform standards and enforcing compliance.
The measure matters because families pay for school meals frequently and small transaction fees can add up; at the same time, districts rely on third‑party processors for convenience and recordkeeping. The bill attempts to preserve free access to meals while bringing transparency and state oversight to vendor practices that affect budgets and household affordability.
At a Glance
What It Does
The bill limits permitted collection fees to those that match ‘‘actual costs’’ and caps allowable fees at no more than 2% of the amount deposited into a student meal account (or a lower percentage set by RIDE). It requires vendors to disclose any fees before a transaction completes and allows districts to void vendor contracts entered after the law’s effective date if they fail to meet disclosure rules.
Who It Affects
Meal service collection providers (defined to include payment processors and vendors), public school districts and local education agencies, RIDE as regulator, and families who pay for school meals or other school-administered fees through digital platforms.
Why It Matters
Schools will need to revisit vendor contracts and payment workflows; vendors must adapt pricing and disclosures; families gain guaranteed access to at least one no‑fee payment channel and clearer information at checkout. The provision therefore shifts compliance and budget questions onto districts and the state regulator while constraining vendor revenue models.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill creates a new statutory rule that vendors collecting school meal payments can only charge fees that reflect the direct, actual cost of processing those payments and must not extract profit from those charges. The statute defines who counts as a ‘‘meal service collection provider’’ so the rule covers traditional point‑of‑sale vendors, cloud‑based platforms, payment processors, and contractors the district hires.
RIDE gets explicit authority to interpret ‘‘actual costs’’ and to set lower fee caps through regulation.
To preserve a no‑cost option, the bill requires each public school and district to offer at least one method for families to pay that does not carry vendor‑imposed fees. It lists examples—such as in‑person payments, mailed payments, or electronic transfers that incur no vendor fee—but leaves the final, standardized definitions and accessibility expectations to RIDE rulemaking.
Local education agencies must actively notify parents and guardians about no‑fee options using multiple channels, which creates an operational task for school offices and communication teams.On disclosures, any digital or online payment portal used by a district must clearly state whether the user will be charged, show the amount and type of each fee, and explain how to use the no‑fee option. Those disclosures must appear before a transaction completes and cannot rely on hidden checkboxes or buried language.
The bill ties vendor compliance to district contracting: contracts executed after the law takes effect that fail to include the required disclosures are voidable by the district, giving districts an enforcement lever while shifting legal review responsibility onto local officials.Finally, RIDE must promulgate rules to implement the statute, covering vendor compliance checks, accessibility standards for no‑fee methods, and uniform disclosure formats. The law also requires that funds collected for meals be applied primarily to meal costs and allowable collection costs, which could affect accounting practices and how districts reconcile vendor fees with federal meal program funds.
The Five Things You Need to Know
The statute caps allowed vendor fees at no more than 2% of the amount deposited into a student meal account, with RIDE authorized to set a lower percentage by regulation.
Contracts signed after the law’s effective date that fail to meet the bill’s disclosure requirements are voidable at a district’s option.
Disclosures must be presented before a payment completes, cannot be obscured or pre‑checked, and must list whether fees apply, the amount and type of each fee, and how to access a no‑fee option.
RIDE must create statewide, uniform standards for no‑fee payment access and require districts to notify families through multiple channels (email, websites, written communications).
The law requires that money collected from families or public agencies go primarily to meal service costs and the limited collection costs expressly allowed by the statute.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Limits on permissible fees and definition of covered vendors
This subsection forbids vendors from charging fees that generate profit beyond actual processing or collection costs and defines the covered entities as any vendor, contractor, payment processor, or entity engaged by a school, district, or RIDE. Practically, districts and vendors will need to document cost bases so fees can be justified as ‘‘actual costs,’’ and vendors that relied on convenience or service margins will need to recast their pricing or risk noncompliance.
Fee cap and allocation of collected funds
The law imposes a percentage cap—expressly set no higher than 2%—calculated against the amount deposited into a student meal account, and mandates that funds collected from families or public agencies be applied primarily to meal costs and allowable collection expenses. This requires changes to accounting and reconciliation: districts must ensure vendor deductions and ledger entries align with the statutory allocation requirement and be ready for audits or regulatory review by RIDE.
Mandatory no-fee payment option and notice duties
RIDE must ensure every district provides at least one no-fee way to pay for meals, and will set uniform standards for access. Districts must notify families about these options via multiple channels. Operationally, schools will need processes for accepting and reconciling in‑person, mailed, or direct-transfer payments that avoid vendor fees, and communications teams must implement templates and outreach to meet the accessibility and timeliness requirements the statute contemplates.
Upfront disclosure and contract compliance
Payment platforms must clearly disclose fee existence, type, and amount before transaction completion and cannot hide disclosures in pre‑checked boxes or small print. Districts must ensure vendor contracts include these disclosure obligations; the statute gives districts the right to void noncompliant contracts signed after the law takes effect. That creates a contract‑management imperative—district legal teams will need to add compliance clauses, and vendors must supply disclosure mechanisms that integrate with district portals.
RIDE rulemaking and enforcement authority
RIDE must write rules to implement and enforce the statute, covering vendor compliance, uniform disclosure formats, and accessibility for no‑fee options. The breadth of rulemaking authority means RIDE will determine key operational details—how ‘‘actual costs’’ are calculated, what counts as an acceptable no‑fee method, and how enforcement works—so stakeholders should monitor forthcoming regulations to understand practical compliance obligations.
This bill is one of many.
Codify tracks hundreds of bills on Education across all five countries.
Explore Education in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Low- and middle-income families: They gain a guaranteed, no‑fee payment option and clearer upfront fee information that reduces surprise charges and cumulative cost burden for routine meal purchases.
- Students eligible for reduced-price or paid meal programs: More predictable access and fewer transaction costs lower barriers to participation, which can increase meal uptake and food security.
- School finance officers and auditors: The bill’s requirement that collected funds be applied primarily to meal costs simplifies financial oversight by aligning vendor deductions with program accounting rules.
- Consumer advocates and parents’ groups: Clear disclosure rules and enforced no‑fee access provide concrete protections they can use to hold districts and vendors accountable.
Who Bears the Cost
- Payment processors and third-party vendors: They must restructure pricing to limit charges to ‘‘actual costs,’’ implement new disclosure interfaces, and accept a statutory cap on fees, potentially reducing revenue from school clients.
- Local education agencies and district staff: Districts will need to revise contracts, run public outreach about no‑fee options, implement reconciliation processes for non-digital payments, and manage enforcement decisions—tasks that create administrative burdens and possible new costs.
- RIDE and state regulators: RIDE must draft, implement, and enforce new regulations, requiring staffing and rulemaking resources without an appropriation in the bill.
- District technology and customer-service operations: Providing alternative no‑fee payment paths and integrating mandated disclosures into existing portals will require IT work and ongoing maintenance, which may fall to under‑resourced districts.
Key Issues
The Core Tension
The bill pits two legitimate goals against each other: protecting families from recurring transaction charges and maintaining the convenience and recordkeeping third‑party payment services provide. Tight limits on vendor fees and mandatory free options reduce cost barriers but risk shrinking vendor offerings, shifting costs to districts, or reducing convenience—forcing a trade‑off between affordability and operational capacity that RIDE’s rulemaking and district procurement choices will ultimately resolve.
Two practical implementation questions will drive how effective this statute is. First, the bill leaves ‘‘actual costs’’ undefined and gives RIDE rulemaking authority to interpret that term and to set a cap lower than 2%.
Determining whether a vendor’s line‑item costs truly reflect processing expenses (versus embedded overhead or amortized software costs) is complex and invites disputes; RIDE’s methodology and audit powers will determine whether the law controls fees in practice or simply changes how they are labeled.
Second, the statute’s cap and prohibition on profit from fees create incentives for vendors and card networks to shift revenue elsewhere. Vendors might refuse to offer low‑cost ACH or bank‑transfer options, decline contracts, charge districts higher platform subscription fees, or impose minimums or flat fees not framed as transaction percentages.
The bill empowers districts to void noncompliant contracts signed after enactment, but that remedy creates legal friction and administrative burden for local authorities who must conduct contract reviews and manage procurement consequences. Finally, guaranteeing at least one no‑fee option could reproduce inequities if the no‑fee path is less convenient or less accessible (e.g., requires in‑person payments during business hours), so the access standard RIDE adopts will materially affect equity outcomes.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.