Retrofit the fleet without replacing every controller.
Add payment triggers, remote status, and fault visibility to existing vending, laundry, locker, or timed equipment.
Machine-side control and data hardware
Connect your self-service machine to your payment, API, and data systems.
QuLink provides the machine-side control layer for MDB, pulse, relay, serial, and RS485 equipment. Add optional QR payment triggers, API commands, telemetry, and fault reporting without rebuilding the whole machine.
MDB · Pulse · Relay · RS485
Your backend
Sample validation
OEM customization
MDB
QR
Telemetry
One board family.
Control, payment trigger, and telemetry.
Machine fit
One control layer, different machine problems.
Start from the machine you operate. The machine interface, not the industry, determines the board.
Vending & smart retail
MDB vend, QR scan-to-start, and dispense results.
Explore vending solutionsLaundry & timed service
Pulse or relay start, timed sessions, and fault events when exposed by the machine.
Explore timed controlLockers & cabinets
Relay unlock, door status when available, rental events, and heartbeat for unattended cabinets.
Explore locker controlOEM & custom machines
Custom firmware, connectors, enclosure, and protocol handling for repeat builds.
Explore OEM optionsControl paths
Select the control path your machine already supports.
Four common starting points. Sample testing confirms wiring, protocol behavior, and the exact board profile.
MDB-to-Cloud Gateway
For vending and MDB equipment that needs vend commands, events, and cloud data.
View MDB gateway
QR Payment / API Trigger Board
For scan-to-start workflows that unlock, dispense, start, or run a timed session.
View payment trigger board
Machine Data Bridge
For machines that need status, sensor values, faults, or usage logs in your backend.
View data bridge
Pulse / Relay Controller
For coin machines, laundry, amusement, charging, and other timed equipment.
View pulse / relay controllerWho it fits
Built for the team that owns the machine and the backend.
Check the fit before the project flow. QuLink is machine-side hardware; it connects to your platform without locking your data into a closed portal.
Ship connected machines with a repeatable board profile.
Customize firmware, connectors, enclosure, and data format for a product line or export market.
Turn a payment or API event into a physical action.
Keep your checkout, wallet, or platform. QuLink handles the machine-side command and result callback.
Interfaces
MDBPulseRelayUART / SerialRS485Custom OEM
MDB 4.2/4.3 is the target profile. Older versions and custom protocols require firmware review; available data and fault signals are confirmed during sample testing.
Project flow
Then prove it on one machine before the rollout.
Most projects begin with photos and a wiring check, not a full cabinet redesign.
Send machine photos
Machine front, controller board, payment module, model label, and connectors.
Map the interface
Confirm MDB, pulse, relay, serial, or RS485 behavior and the action to trigger.
Test one machine
Validate commands, payment callback, vend result, faults, and reconnect behavior.
Roll out with a profile
Lock firmware, wiring, enclosure, and event schema before the fleet deployment.
Use-case guides
Technical guides before the first sample.
Short technical guides for the most common starting points.
Cashless retrofit
How to add cashless payment to a vending machine
Compare MDB cashless, card reader, QR, and callback paths before choosing a board.
Read the guide TroubleshootingVending machine card reader offline?
Check power, SIM, antenna, MDB harness, and payment host before replacing the reader.
Read the guide MDBMDB vending machine API gateway
How MDB commands, vend results, faults, and telemetry map to your server.
Read the guide QR paymentQR payment controller board
How a payment callback becomes a relay, pulse, unlock, or dispense action.
Read the guide MDB guideMDB vending machine integration guide
Cashless authorization, vend result, API control, and data over MDB.
Read the guide DataMachine data upload board
How to move status, faults, usage, and sensor values into your own cloud.
Read the guideBuyer questions
Two questions operators ask before a retrofit.
Direct answers to the questions that usually decide whether a project moves forward.
Remote monitoring
How do I add remote monitoring to an existing vending machine?
What can be monitored, what the controller must expose, and how a data bridge reaches your own backend.
Read the answer Cashless costHow much does a vending machine cashless retrofit cost?
The interface, reader, payment path, installation, and data scope that drive the quote.
Read the answerFAQ
Questions before a sample test.
The fastest way to a useful answer is a machine photo and the action you want after payment or an API command.
Is QuLink a payment provider or acquirer?
No. QuLink is machine-side control and data hardware. We can provide an optional QuLink QR payment workflow, but we are not a bank, acquirer, or closed payment portal.
Can we keep our existing card reader?
Often yes. QuLink can add an independent machine-side status and data path while your reader and payment provider stay in place. The available signals depend on the reader and controller.
What should we send first?
Machine model, controller and payment module photos, wiring or connector photos, the target action, and whether you need data upload. A photo is usually more useful than a long specification.
Do you support pilot deployments?
Yes. A typical pilot starts with one machine, a confirmed interface, sample testing, and a repeatable rollout profile.
Start a project
Send machine photos. We will identify the interface and next test step.
No obligation. Send what you have: machine model, board photo, payment module, or wiring note. We will reply with the likely path.
- Machine model and controller photos
- Payment module or card reader photos
- Target action after payment or API command
- Whether you need telemetry or fault data