Find the start input
Identify coin acceptor wiring, relay terminals, start button, or controller input.
Coin machine relay retrofit
Relay controller for coin-operated machines that need QR or API start.
Use QuLink when a coin machine, amusement device, massage chair, laundry machine, or timed service device needs payment approval to become a pulse or relay action.
Pulse / relayCoin replacementQR/app triggerField retrofit
Project fit
For coin, token, and timed self-service devices
Buyer signals
- Machines accept pulse, relay, dry contact, or start signal input.
- Payment should move from coin/token to QR, app, or backend approval.
- The project needs timed sessions, result callbacks, or online status.
- Operators want a field retrofit before OEM design.
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
Keep the machine behavior, replace the trigger source
QuLink does not need to replace every machine controller. It can often connect to the existing start path and report the result.
- Machine interface
- pulse input, relay output, dry contact, sensor input
- Trigger source
- QR payment, payment callback, app approval, operator panel
- Control output
- pulse count, relay duration, timed run, unlock, stop
- Data returned
- session.started, session.completed, fault, online status
Workflow
From machine interface to API-controlled result.
Set trigger rule
Define pulse width, relay channel, duration, and payment reference.
Install sample
Validate with one machine before fleet rollout.
Tune deployment
Adjust enclosure, wiring harness, firmware, and operations workflow.
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/COIN-21/commands
{
"command": "trigger_relay",
"source": "payment_callback",
"machine_action": {
"channel": 1,
"duration_ms": 1000
}
}
Start the project
Send the first machine details before writing a full spec.
Send the coin acceptor photo, start wiring, target machine action, session rule, and installation environment.
Useful first message
- Machine type and target country
- Machine photo, board photo, or wiring photo
- Action after API command or payment
- Data upload and estimated quantity
FAQ
Questions buyers usually ask before a sample test.
Is relay control enough for every coin machine?
No. Some machines need pulse simulation, serial integration, or OEM review, which is why photos are the first step.
Can QuLink support multiple channels?
Yes, channel count is selected based on machine wiring and deployment needs.
Can it upload status?
Yes, if the project includes sensors, status lines, or supported data sources.
Related use cases