Laundromat Card and App Payment Systems: Reporting That Survives Diligence

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

The Payment Mix Is Hybrid

The CLA's 2024 survey allowed multiple responses, and the result is a picture of a mixed market, not a cashless one:

Because responses overlap, those percentages must not be added together and the market must not be described as fully cashless. Most stores accept several methods, and a great many still take coin.

The Systems

This site does not rank them. The right system for a store depends on the installed equipment's control generation, local distributor support, processing costs, and what the operator actually needs to see.

The Distinction That Decides Everything

Payment-system reports are powerful and easy to misread. Six terms have to be separated before any number means anything:

A store growing its card base quickly shows loads exceeding cycle revenue. A store where customers are drawing down old balances shows the reverse. Neither is a problem. Presenting either figure as revenue without the distinction is.

The Stored-Value Liability

Customers hold unspent balances on cards. After closing, the new owner honors them. That is cash the seller already collected for a service the buyer will deliver.

It is usually a four-figure number and sometimes five. It should be:

1. Quantified during diligence, from the outstanding balance report.
2. Adjusted for at closing, as a credit to the buyer.
3. Tracked afterward, because it moves with promotions and card-base growth.

Discovering it in month two is a small unpleasant surprise. Discovering a five-figure version of it is a larger one. See stored-value liability.

What to Request in Diligence

For any store with a payment system:

1. Twelve months of machine-level revenue and start reports
2. Vend price change history, so you can see when pricing moved
3. Refunds and promotions identified by period
4. Management and test starts, so they can be excluded
5. Processor settlement statements, 24 months
6. Current outstanding stored-value balance
7. The processing agreement, including fees and assignment terms
8. Hardware ownership documentation — owned, leased, or financed
9. Operator account credentials and the machine mapping
10. Any revenue-share arrangement with the system provider

Then reconcile: cycle revenue against processor settlements, settlements against bank deposits, and the whole against the tax returns. Variances are expected; unexplained variances are not.

Transfer Mechanics at Closing

The item most often left to the last week, and it does not always go smoothly.

• Hardware ownership. Owned outright, leased, or financed with a UCC lien to release.
• Operator account. Whether it transfers or the buyer must open a new one, and what happens to historical data.
• Machine mapping. The association between physical machines and the account, which has to be re-established if the account changes.
• Processing agreement. Whether it is assignable, and what the buyer's rate will be.
• Stored-value balances. Whether they travel with the account or need migration.
• Timing. Some transfers require lead time from the provider; start it two to three weeks before closing.

Should a Seller Install One Before Selling?

Often yes — for the evidence, not the convenience.

The single largest objection a buyer and lender raise about a coin store is that the revenue cannot be independently corroborated. A payment system with exportable machine-level data addresses that objection directly, and evidence quality is the driver that most reliably moves a store up the multiple range.

The caveats are real. It needs two or three quarters of data behind it to be persuasive, so it is a 12-month decision and not a pre-listing tactic. It costs four to five figures installed. And converting from coin can temporarily disrupt older customers, which shows up in the trailing twelve months you are about to be valued on.

Why Does the Data Matter More Than the Payments?

Because verifying revenue is the hardest part of laundromat diligence, and a payment system with reporting is the only thing that solves it directly.

A coin store generates no transaction record. Its revenue exists in the owner's collections and deposits, both of which are the owner's own reporting. Every verification technique available — reconciling deposits, analysing water consumption, attending collections, rebuilding revenue from observed turns — is an attempt to construct independent evidence that the business does not naturally produce.

A card or app system produces that evidence continuously, without anyone being present. Starts by machine, by day and by hour. Cycle revenue. Price history. Refunds. Exportable.

That changes three things at once.

It shortens diligence and reduces the discount. A buyer who can see three years of machine-level history does not have to price the uncertainty that a coin store's records leave behind.

It makes the store financeable more easily. An underwriter cannot pull a processor statement on a coin business, which is precisely why the water bill has become a standard cross-check. Machine data removes the problem rather than working around it.

It is an operating tool now. Which machines earn, when the store is actually full, what happened after a price change, whether a competitor's opening moved anything. Most owners running coin are making these decisions on impression.

The important caveat is timing. The benefit accrues to the history, not to the hardware. A system installed two months before listing produces two months of data, which is not what a valuation is built on — which is why this is a decision to make years before an exit, not in preparation for one.

What Should a Buyer Request and Verify?

Six things, and the first two are the ones most often skipped.

Full machine-level exports for the longest available period. Not a summary the seller prepared — the raw export, from the system, covering every machine.

Confirmation that the data can be exported by the new owner. Some arrangements make history difficult to retrieve or tie access to the seller's account. Establish this before closing, because a store whose data you cannot take with you has lost much of the advantage.

The outstanding stored-value balance. Customers holding loaded cards have paid the seller for laundry not yet done, and that liability transfers to you. It should be quantified from the system and credited at closing. Buyers discover this after the fact far more often than before.

The vendor agreement. Term, fees, whether it is assignable, what happens at the end, and whether the hardware is owned or leased.

The full fee schedule. Percentage, per-transaction charge, platform or per-machine software fees, gateway and kiosk fees. Model it per dollar of revenue rather than per transaction.

Reconciliation of the exports against deposits and returns. The data's value is that it corroborates; a buyer who receives it without checking it against the other sources has collected a document rather than performed a verification.

Should a Seller Install One Before Selling?

It depends almost entirely on how far away the sale is, because the benefit accrues to the data and not to the hardware.

Years out — usually yes. The verification advantage is real and it compounds. A store that can hand a buyer three years of machine-level history removes most of the friction from the hardest part of laundromat diligence, which supports both the price and the financeability. Add the operating benefits — practical pricing changes, visibility of which machines earn and when the store is full — and the case is strong on its own terms, independent of any sale.

Months out — usually no. A system installed shortly before listing produces a short history, which is not what a valuation is built from. You will have spent the capital and taken the disruption without acquiring the asset, and a buyer deducts near-term capital from what they will pay rather than crediting recent spending.

Where a retool is imminent — wait and do both together. New machines arrive card-ready, the installation labour is already committed, and the compatibility constraint disappears. Doing them separately means paying twice for one disruption.

One item to settle either way: confirm you can export the history and that access transfers to a buyer. A system whose data cannot leave with the store has given up much of the advantage you paid for.

What Happens to the System at Closing?

Three items to settle in the agreement rather than discover afterwards.

The outstanding stored-value balance. Customers hold loaded value — money the seller has already received for laundry not yet done. That liability transfers with the store, it can be quantified from the system, and it should be credited at closing.

Account and data transfer. Confirm the vendor account moves to the buyer, that historical data remains accessible, and that the export capability transfers. Establish this before closing rather than assuming it.

The vendor agreement itself. Whether it is assignable, what the remaining term is, whether hardware is owned or leased, and what any early termination would cost.

Alongside those, take the practical steps on the day: confirm the merchant account and settlement destination are yours, test a transaction end to end, and make sure refunds can be processed by whoever will be in the store.

Summary

Card and app systems are worth more to a transaction as a reporting platform than as a convenience. The market is hybrid, not cashless. Loads are not revenue, and the difference is a liability that belongs on the closing statement. Request ten specific items in diligence, reconcile them against deposits and returns, and start the account transfer weeks before closing rather than days.

The budgeting side is covered in cost to convert to card.

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.