Start with the machine, not the card reader. Before you buy anything, identify each washer and dryer's model, its controller, and the payment interface it supports. Some laundry machines accept a pulse or contact closure, some use other coin or control interfaces, and some are poor candidates for a retrofit. Once that is confirmed, the rest of the project is a card reader, interface hardware, connectivity, software, and an acquiring relationship.
This guide covers each piece, then walks through approval, activation, failures, and a pilot rollout.
Step 1: identify the machine and its interface
Record the make, model, and age of every machine, then find out what the controller supports from the manual or the manufacturer. Do not assume pulse. If you need a primer, read MDB vs. Pulse: which interface does your machine need and the Pulse overview. For why pulse-based equipment is still worth upgrading, see Modernize Your Pulse-Based Systems with Cashless Payments.
What a retrofit needs
| Component | Role | What to confirm |
|---|---|---|
| Card reader | Accepts contactless and card payments | Supported payment types, mounting, weather and tamper needs |
| Interface hardware | Turns an approval into the signal the machine expects | Compatible with the machine's confirmed interface |
| Connectivity | Connects the reader to the processor | Wi-Fi, cellular, or wired at each site |
| Software and backend | Handles transactions, device status, pricing, and reports | Who builds, hosts, and supports it |
| Acquiring and processing | Merchant account, processor, or gateway | Onboarding requirements and reporting |
| Power and mounting | Keeps the reader running | Available power near each machine |
| Support and monitoring | Finds offline or failing devices | Who gets alerts and who visits the site |
From tap to wash cycle
- The customer selects a machine and taps a card or phone.
- The reader requests authorization for the cycle price.
- The processor approves or declines.
- On approval, the interface hardware sends the credit signal the machine expects.
- The machine starts, and the system records what happened.
A sent signal is not proof that the cycle started. Decide how the system detects a start, for example through a machine status input where one exists, and how it handles an unclear result. The design questions are covered in Payment approved, machine didn't start.
Refunds, failures, shared rooms, and pilots
▸ Refunds and failures: define what happens when a payment is approved but the machine does not start. Decide between an automatic reversal or refund, who can issue it, and how the customer is told.
▸ Shared rooms: customers need to know which machine they are paying for. Per-machine readers, clear labels, and a visible machine number reduce wrong-machine payments.
▸ Pilot rollout: start with a small number of machines at one site, watch real transactions and failures, then expand once the failure handling holds up.
Compatibility worksheet
Fill one row per machine type before ordering hardware.
| Item | What to record |
|---|---|
| Make and model | From the machine plate |
| Age and serial number | Helps the manufacturer confirm options |
| Controller or board label | Photograph it |
| Supported payment interface | Confirmed in writing by the manufacturer or distributor |
| Current coin or card system | What it accepts today |
| Cycle prices and options | Including any variable pricing |
| Power near the machine | Source and access |
| Network at the site | Wi-Fi, cellular signal, or wired |
| Owner permissions | Landlord or lessor approval for changes |
Cost categories
Pricing depends on the machines, the site, and the processor, so this lists categories only.
| Category | Examples |
|---|---|
| Hardware | Readers, interface boards, cabling, mounts |
| Installation | Site visits, labor, testing |
| Software and backend | Development or licensing, hosting, reporting |
| Processing | Fees and merchant account costs |
| Connectivity | Data plans or network equipment |
| Support | Monitoring, replacements, site service |
FAQs
Do all laundry machines use pulse?
No. Interfaces vary by manufacturer and model, so confirm each one before choosing hardware.
Can coin acceptance stay in place?
Often that is a configuration question for the machine and the interface hardware. Ask the manufacturer or your integrator before assuming either way.
Should we pilot first?
Yes. A few machines at one site will show how failures, refunds, and connectivity behave before you commit to a full rollout.
What if a machine has no usable interface?
Ask the manufacturer about options. Some machines may need a different approach or may not be good candidates.
Next step
If you can share your machine models, controller details, site connectivity, and processor, we can help map the interface and plan a pilot. Start at the Pulse page.
Sources
Software executive with over three decades of experience. Focus primarily on the payment industry and FinTech technologies