Laundromat Card Processing Fees: What the Percentages Cost You

By Jason Taken, business broker · HedgeStone Business Advisors · Updated 2026-09-05 · 10 min read

What Are You Actually Paying?

The distinction that matters most is between the percentage and the fixed component. Consider the same fixed per-transaction fee applied two ways: charged once on a $20 card reload, it is a small fraction of the amount. Charged separately on each individual machine start, it recurs every time and compounds into a meaningfully larger share of the same total revenue.

That single fact explains most of the design decisions in laundry payment systems.

For scale, the Coin Laundry Association's 2024 survey of owner-operators put utilities at a median 20% of gross revenue and rent at 18% for 2023 operations (Source: CLA, 2024). Payments sit well below either, which is the argument for fixing the larger lines first — but it is a recurring percentage of every dollar you take, and unlike rent it is negotiable.

Why Reload Models Exist

Because they convert many small transactions into one larger one.

When a customer loads $20 onto a stored-value card or an app balance, the processor sees one transaction. The subsequent machine starts are drawn down against a balance you already hold — they are not card transactions and carry no processing fee. When the same customer taps a card at each machine instead, every start is a transaction with its own fixed cost.

This is also why reload bonuses can make economic sense rather than being pure giveaway: a bonus that increases the average reload size reduces the number of transactions per dollar of revenue, and part of the bonus is funded by the fees you no longer pay. It also holds a customer's money on your system, which is a retention mechanism in itself. See loyalty programs for the rest of that arithmetic.

The trade-off is friction. Requiring a card excludes the occasional customer who has none and does not want one, and in a competitive trade area that is a real cost. Most stores that have worked through this now offer both — a reload path for regulars and a tap-to-pay path for everyone else — and accept the higher effective fee on the convenience transactions.

Can You Surcharge?

Sometimes, and it is one of the areas where a confident answer from a forum is worth nothing.

Two separate constraints apply. Card network rules govern surcharging: they impose disclosure requirements, cap the amount, distinguish credit from debit, and require notification before you begin. And state law applies independently — a number of states have restricted or prohibited surcharging, and the legal position in several has moved through litigation over recent years.

The practical guidance:

1. Ask your processor what surcharging they support and what their compliance requirements are.
2. Confirm the position in your state, and get that in writing where the amount is material.
3. Consider the alternative. A cash discount structured properly is treated differently from a surcharge in some frameworks, but "structured properly" is doing real work in that sentence.
4. Weigh the customer response. A visible surcharge at the point of use is a different experience from a price that already includes the cost.

Nothing here is legal advice, and this is a genuine take-it-to-counsel question, not a polite disclaimer.

How Do You Compare Vendors Honestly?

Headline rates are not comparable across vendors because they cover different things. Ask every candidate for the same list and build your own comparison:

• The full fee schedule, not the advertised rate — interchange treatment, markup, per-transaction fee, monthly minimums.
• Platform fees, including whether they are per store or per machine.
• Hardware cost and ownership. Who owns the readers, and what happens at the end of the term.
• Contract length and exit terms. This is where the real cost of a bad decision sits.
• Settlement timing. How long your money takes to arrive.
• Reporting. Whether you get machine-level start data, and whether you can export it.
• Support response times, because a dead reader is a dead machine.

That reporting line deserves weight beyond its operating value. Machine-level start data is what lets you reconcile collections, price by machine size, and — years later — prove your revenue to a buyer. A cheaper system with worse reporting can cost more than it saves. See laundromat card payment systems.

What Should You Actually Do About the Cost?

Model it per dollar of revenue, not per transaction. The question is what share of your gross the payments layer consumes in total, including monthly fees. That is the number to compare year over year and against alternatives.

Push the average transaction up where you can do so without friction, since that is what dilutes the fixed component.

Renegotiate once you have history. Rates offered to an unproven account are not the rates available to one with two years of volume.

Do not price the fee into a vend increase without checking the rest of your cost first. Utilities are usually the larger and more addressable line — see lowering water and sewer bills.

Why Does the Per-Transaction Fee Matter More Than the Rate?

Because laundromat transactions are small, and a fixed charge is a much larger proportion of a small ticket than of a large one.

Card pricing typically combines a percentage of the transaction with a fixed amount per transaction. On a large purchase the fixed component is negligible. On a single wash cycle it is not — and a store processing thousands of small transactions a month is paying that fixed charge thousands of times.

This is the entire reason reload models exist. When a customer loads value onto a card once and then spends it across many cycles, there is one card transaction rather than many. The percentage still applies to the amount loaded, but the fixed per-transaction charge is incurred once instead of a dozen times. On a small-ticket business that difference is substantial.

It also explains why encouraging larger reloads is worth more than it appears. A customer loading a larger amount less often reduces your processing cost per dollar of revenue, which is why reload bonuses can pay for themselves through fee reduction alone before any loyalty effect.

The practical instruction is to model your processing cost per dollar of revenue rather than per transaction, and to compare that against what coin handling actually costs you in collection time, counting, banking and coin-box losses. Owners frequently assume coin is free because no invoice arrives. It is not free; the cost is simply paid in labour and risk, not in fees.

What Should You Ask a Vendor?

Six questions, and the answers should be in writing.

What is the full fee schedule? Percentage, per-transaction amount, and every other charge by name. Ask specifically whether there are monthly minimums, gateway fees, statement fees, PCI compliance fees or annual charges.

Are there per-machine software or platform fees? Some systems charge per store and some per machine, and on a large fleet the difference is significant.

What is the total monthly cost at my actual volume? Give them your real transaction count and average ticket and ask for a dollar figure and not a rate.

What happens to funds if the system fails? Settlement timing, and what your recourse is.

Who owns the customer data, and can I export it? This matters operationally and it matters enormously at sale, because exportable machine-level history is one of the strongest verification assets a laundromat can have.

What is the term, and what happens at the end? Contract length, renewal terms, early termination charges, and whether the hardware is yours.

Then compare offers on total monthly cost at your volume, not on the headline rate. A lower percentage with a higher fixed charge is worse for a laundromat, and comparing rates alone will lead you to the wrong answer.

Does This Change What the Store Is Worth?

Indirectly, and in two directions that are worth separating.

Processing fees are an operating cost, so they reduce earnings and therefore reduce the price at a multiple. That is the straightforward half, and it argues for negotiating them properly rather than accepting a default schedule.

The other direction matters more. A payment system that produces exportable machine-level history is one of the strongest verification assets a laundromat can have, because verifying revenue is the hardest part of laundromat diligence. A store that can hand a buyer three years of cycle data removes most of that friction, which supports both the multiple and the financeability.

So the fees buy something beyond the ability to take cards. Whether that trade is favourable depends on the store, but it should be evaluated as a trade rather than as a cost line — and the data only accumulates while you own the store, which is an argument for not deferring the decision if you expect to sell eventually.

One caution: confirm you can export your own data and that you retain access to the history. A system that holds your data hostage is worth considerably less at exit.

Summary

Fees come in three layers and the fixed per-transaction component is the one that matters most in a small-ticket business. Reload models exist to dilute it, and reload bonuses are partly self-funding for the same reason. Surcharging is constrained by both network rules and state law, so confirm rather than assume. When comparing vendors, compare full fee schedules and weigh reporting quality heavily, because that data is an operating tool now and a diligence document later.

The Next Step

This page is general information about laundromat transactions, not legal, tax, or investment advice, and not a guarantee of sale price, timing, or financing approval. Verify current rules with your own CPA, attorney, lender, and the relevant state or municipal agency before acting.