Generate QR
Create a QR code for a device, product, relay channel, price rule, or timed session.
QR payment trigger board
QR payment controller board for scan-to-start machines.
Use QuLink when customers scan a QR code, payment is confirmed, and a real machine needs to start, unlock, dispense, pulse, or run for a timed session.
QuLink QR payment availableOwn payment callback supportedRelay / pulse / serial outputWebhook result
Project fit
Best-fit machine scenarios
Buyer signals
- Payment boxes, lockers, charging devices, vending machines, laundry, and access devices.
- Machines where payment confirmation should trigger a physical action.
- Projects that need QuLink QR payment or your own payment provider callback.
- Operators that want a machine-side board without building a closed SaaS platform.
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
Integration model
Payment is optional, the control layer stays the same
QuLink can provide the QR payment workflow, or you can keep your own checkout. Either way, payment confirmation becomes a signed machine command.
- Trigger source
- QuLink QR payment, wallet callback, app approval, operator panel, or server command
- Machine output
- relay, pulse, unlock, serial action, timed run, dispense command
- Data returned
- payment reference, command accepted, machine started, session completed, fault alert
- Project mode
- payment box retrofit, scan-to-start device, OEM payment controller
Workflow
From machine interface to API-controlled result.
Confirm payment
Use QuLink QR payment or send your own payment callback after the customer pays.
Trigger action
The board starts, unlocks, dispenses, pulses, or runs the machine.
Report result
Your server receives action result, telemetry, and session status.
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/LOCKER-22/commands
{
"command": "unlock",
"source": "qr_payment",
"machine_action": {
"type": "relay",
"channel": 2,
"duration_ms": 900
}
}
Start the project
Send the first machine details before writing a full spec.
Send the machine type, price/session rule, payment provider, and the action that should happen after payment.
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 QuLink only a payment gateway?
No. QuLink is the machine-side control layer. QR payment is available when scan-to-start is needed.
Can we keep our own payment provider?
Yes. Your system can confirm payment and call the QuLink command API.
Can one QR code map to different actions?
Yes. QR can map to device ID, product, relay channel, price rule, or timed session depending on the project.
Related use cases