Choose data points
List what the machine should report: status, fault, usage, meter, result, or session.
Machine data upload guide
Upload self-service machine data to your own cloud.
Use QuLink when machines need to report status, telemetry, usage, faults, vend results, meter values, or session events to your backend.
TelemetryFault uploadOwn cloud4G data bridge
Project fit
For operators and OEMs that need machine visibility
Buyer signals
- Machines are offline, faulted, or running without useful remote visibility.
- You need data upload but may not need payment yet.
- Legacy machines need cellular or server callbacks.
- Your own backend should own operations and analytics data.
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
Read machine-side signals and send normalized events
QuLink maps signals, serial data, RS485 frames, sensors, or controller status into callbacks your server can process.
- Data sources
- sensor input, UART, RS485, serial frames, MDB events, controller status
- Connectivity
- 4G/cellular module, webhook callback, project-specific API
- Events
- device.online, telemetry.updated, machine.fault, meter.value, vend.result
- Project mode
- data-only bridge, control plus data, OEM telemetry board
Workflow
From machine interface to API-controlled result.
Identify data source
Confirm sensor, serial, RS485, MDB, or controller output.
Map event format
Define callback fields and retry/online behavior.
Verify in field
Test real fault, offline, and recovery cases.
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 /webhooks/qulink
{
"event": "telemetry.updated",
"device_id": "CABINET-31",
"telemetry": {
"online": true,
"door_open": false,
"fault_code": null
}
}
Start the project
Send the first machine details before writing a full spec.
Send machine type, data points, photos or protocol notes, connectivity requirement, and target server format.
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.
Can this work without QR payment?
Yes. Some projects use QuLink only for machine data upload.
Can it send data to our own cloud?
Yes. QuLink is designed to connect machine-side hardware to your backend workflow.
Can data upload combine with control?
Yes. Many projects combine telemetry with relay, pulse, MDB, or API command control.
Related use cases