Confirm start input
Check whether the bay controller uses relay, pulse, coin input, button signal, or serial control.
Guides
Car wash control
Car wash payment controller for timed bays and QR scan-to-start.
QuLink's car wash controller starts a bay through a relay or pulse output, runs a timed session, and returns session and fault events. The 12V/24V control signal and start input are confirmed per bay; verification is pending sample.
Timed relayPulse / dry contactQR paymentSession telemetry
Part of Pulse Relay Controller for Laundry and Timed Machines
Project fit
For self-service wash bays and vacuum stations
Buyer signals
- Self-service car wash bays that start a pump, valve, or timer after payment.
- Vacuum, air, foam, or rinse stations with coin, pulse, relay, or button control.
- Operators adding QR payment or app control to existing wash equipment.
- Projects that need session time, device status, and fault events in one backend.
What to send first
- Machine photo or existing board photo
- Interface or wiring note if available
- Target action after API command or payment
- Whether telemetry or data upload is required
Not the right fit if
- You only need a pure payment acquiring account and no machine-side control.
- There is no physical machine action after payment, booking, or API approval.
- The project has no machine photo, board photo, wiring note, or interface clue yet.
Integration model
Payment approval becomes a timed wash session
QuLink maps QR payment or server approval to the wash controller start input, relay channel, or pulse path, then reports session and device status back to your platform.
- Machine interface
- relay output, pulse input, dry contact, serial/RS485 option
- Trigger source
- QuLink QR payment, app approval, wallet callback, or operator command
- Session control
- start, timed run, stop, extend, query status
- Data returned
- session.started, session.completed, fault, online/offline, usage log
- Project mode
- bay retrofit, vacuum station, operator rollout, OEM wash controller
Workflow
From machine interface to API-controlled result.
Map payment to session
Define bay ID, price, duration, start/stop behavior, and whether extension is allowed.
Trigger wash session
QuLink activates the output after payment or server approval and tracks the timer.
Report result
Your backend receives start, completion, fault, and usage events.
API example
A clear server command or webhook for the machine-side action.
The exact command fields depend on machine interface, firmware profile, and whether payment or your own app triggers the action.
POST /v1/devices/WASH-BAY-03/commands
{
"command": "start_session",
"source": "qr_payment",
"machine_action": {
"type": "relay",
"channel": 2,
"duration_ms": 480000
},
"reference_id": "WASH-ORDER-103"
}
Project RFQ
Send a machine photo. We help identify the board, interface, and next test step.
Send the wash bay controller photo, wiring notes, start signal type, session duration, target payment flow, and rollout quantity.
A good first message
If you are unsure about the exact interface, send what you have. Photos often answer more than a long spec.
- Machine type and target country
- Machine photo, board photo, or wiring photo
- Action after payment or API command
- Need data upload? expected quantity?
Fastest first step
- Send a machine photo
- Describe the action after API or payment
- Tell us if data upload is needed
FAQ
Questions buyers usually ask before a sample test.
Can QuLink control an existing car wash timer?
Often yes if the timer accepts a relay, pulse, or dry-contact start signal. Photos of the controller and wiring are the first step.
Can each bay have its own QR code?
Yes. A QR code can map to a bay ID, price rule, duration, and relay channel.
Can it report usage and faults?
Yes. Session start/completion, online status, and available fault signals can be sent to your server.
Can we keep our own payment app?
Yes. Your app or payment provider can approve payment and call the QuLink command API.
Related use cases