Payments for Daycare Centers: What Stripe, Square, and the Big Processors Actually Cost You

The short version: tuition is a recurring, card-on-file business, and card-on-file is exactly where the big processors charge their worst rates. Stripe bills card-on-file at 3.4% + $0.30; Square at 3.5% + $0.15. Meanwhile ACH — a bank-to-bank pull — costs 0.8%, capped at $5. On a $1,400 monthly tuition, that's $47.90 versus $5.00, per child, per month. The second leak is late payments: centers that chase tuition by hand lose weeks of cash flow every quarter. Rates checked October 2026. Also see Daycare Centers, AI for Daycare Centers, and Tech for Daycare Centers.

The fee table: what each processor charges on monthly tuition

Daycare tuition runs on card-on-file recurring charges — and the big processors price card-on-file worse than almost anything else. Here is the math, per child per month, at real tuition levels. Rates checked October 2026.

• $900/month tuition: Stripe card-on-file 3.4% + $0.30 = $30.90. Square card-on-file 3.5% + $0.15 = $31.65. ACH (0.8%, capped at $5) = $5.00. You save $25.90 per child per month.
• $1,400/month tuition: Stripe = $47.90. Square = $49.15. ACH = $5.00. You save $42.90 per child per month.
• $2,000/month tuition: Stripe = $68.30. Square = $70.15. ACH = $5.00. You save $63.30 per child per month.

Multiply: a 60-child center at $1,400 tuition saves $2,574 a month — $30,888 a year — by running tuition on ACH instead of stored cards. That is a teacher's salary, donated to Stripe every year. ACH is not instant — it takes 1 to 3 business days to settle — but tuition is predictable, so settle time doesn't matter. What matters is that parents authorize it once, at enrollment, as the default.

The killer angle: late-fee automation beats fee negotiation

Almost nobody writes about this, so here it is: the most expensive payments problem in daycare isn't the processing rate — it's the manual chase. A center with 15 percent of families chronically late is missing roughly $10,000 a month in a 60-child center. The fix is rule-based, not personal. First: autopay on a fixed day — Friday mornings work because payroll just landed. Second: automatic late fees — a flat $25 after the 5th, applied by the system, not by a director deciding whether she likes the family. Third: late-pickup fees — $1 a minute is standard in many markets, and it only works if the check-in system timestamps it and the invoice generates itself; anything manual gets forgiven, which teaches parents the deadline is fiction. Fourth: failed-payment dunning — when a card expires, the system retries on a schedule, texts the parent a one-tap update link, and escalates to the director only after the third failure. Centers that automate all four typically cut late tuition by two-thirds in a quarter. Compare that to shaving 0.2% off your processing rate: the dunning workflow is worth ten times the rate negotiation.

The workflow checklist the big processors fail

Stripe, Square, Adyen, Chase, Fiserv, Global Payments, and Worldpay will all happily take your money. None of them was built for this workflow. Before you sign anything, check these boxes — the processor or platform you choose has to handle all of them:

• Recurring tuition on a parent's schedule: weekly for some families, monthly for others, with proration when a child starts mid-month. Generic subscription tools do monthly-or-nothing.
• Sibling discounts: 10% off the second child is industry standard. If your processor can't do family-level pricing rules, someone does it in a spreadsheet — badly.
• Subsidy splits: the state pays part, the parent pays part, and the two amounts reconcile on one ledger. This is the feature that separates childcare billing from generic invoicing.
• Waitlist and registration deposits: a $100–$200 deposit that converts to first-month tuition or refunds cleanly. Deposits handled as regular charges create refund messes.
• Drop-in and late-pickup charges: one-off charges attached to the family's stored payment method, no new checkout.
• Failed-payment dunning: scheduled retries, parent-facing update links, escalation rules. Stripe has this as an add-on product; Square barely has it at all.

If your childcare platform (Brightwheel, Procare) already runs billing through its own gateway, you're not choosing a processor — you're choosing a platform, and the processing rate is bundled. Ask for the card rate and the ACH rate separately, in writing, before you sign. And ask whether you can route ACH yourself, because the platform's cut is where your $30,888 a year quietly goes.

The honest verdict on each processor

Stripe: the best API and the worst card-on-file rate in this list (3.4% + $0.30). Fine if you're building custom billing and routing tuition through ACH, where Stripe charges 0.8% capped at $5. Bad as a default for stored-card tuition — you're paying the premium rate on your biggest, most predictable revenue.

Square: the easiest setup and the worst card-on-file math here (3.5% + $0.15). Fine for the front-desk card reader on drop-in fees. Bad as your tuition engine — and Square's aggregated-risk model has a documented habit of holding funds when a batch of large charges looks unusual, which a 60-family tuition run absolutely does.

Adyen: enterprise-grade, quote-based, built for marketplaces and global commerce. Overkill for a daycare unless you're running a 20-location chain with a payments team.

Chase Payment Solutions, Fiserv (Clover), Global Payments, Worldpay: quote-based, sold through ISOs and bank reps, with no published childcare-specific anything. They can do the job, but you'll negotiate blind unless you bring the fee table from the first section of this page to the meeting. Do that — it's your leverage.

Your childcare platform's bundled processing: the most common setup in the industry, and the least examined. Convenience is real — billing, attendance, and payments in one place — but you're accepting whatever rate the platform negotiated for itself. The question to ask isn't "what's the rate," it's "what's the rate on ACH, and can I keep the difference."

How a daycare actually wires this up: notes from Finix's public docs

If you run multiple centers — or you're done renting your billing from a platform — the alternative is owning the payments layer. Finix's public documentation (docs.finix.com) describes exactly the primitives a daycare billing system needs. Subscriptions charge a stored payment instrument on a recurring schedule, and they support both recurring card payments and recurring bank payments (ACH in the US). The details map suspiciously well to childcare: trial periods for the first-week guarantee some centers offer; discount phases for sibling discounts that expire after a set number of cycles; billing-cycle-day control so all 60 families bill on the 1st with proration for mid-month starts; fixed-length intervals for a school-year contract that ends in June. On the failure side, Finix documents smart retry logic for failed recurring payments plus network tokens and account updater, which silently refresh expired card numbers — the number-one cause of "mysterious" late tuition. All of it is manageable from the Finix Dashboard with no-code tools, or via API if you're building a parent portal. That's the stack for a center that wants ACH-first tuition, automated retries, and dunning it controls — instead of a platform's bundled rate and a prayer. For the voice-to-invoice side — speaking a late-tuition charge and texting the parent a payment link — ClaroPro handles the four-minute workflow from our AI guide.

FAQ

What's the cheapest way to collect daycare tuition? ACH autopay: 0.8% capped at $5 per transaction, versus 3.4–3.5% plus a fixed fee on stored cards. On typical tuition ($900–$2,000/month), ACH saves $25–$63 per child per month.

Can I charge late fees automatically? Yes — every serious childcare platform (Brightwheel, Procare, Lillio) supports rule-based late fees: a flat amount applied after a grace period, no director involvement. Check your state's childcare regulations for any caps first.

Why did my processor hold our tuition batch? Aggregated processors like Square flag unusual batch sizes. A full tuition run — 60 families charged at once — can look like fraud to an algorithm. Dedicated merchant accounts and platform-bundled processing don't have this problem.

Should parents pay by card or bank account? Default to bank account (ACH) for recurring tuition and keep cards as the backup method for one-off charges like late pickup fees. Offer both; make ACH the default at enrollment.

The move, in order: 1) shift tuition to autopay with bank account as the default — the ACH math above pays for everything else. 2) turn on rule-based late fees so the policy enforces itself. 3) add failed-payment retry automation so one expired card doesn't become a 30-day chase. 4) only then negotiate the processor — the workflow fixes are worth more than a tenth of a point. Then read Tech for Daycare Centers to see which platforms actually run this billing well and which just claim to.