Check MDB compatibility
Confirm machine model, MDB wiring, and existing payment module behavior.
MDB cashless retrofit
MDB cashless vending retrofit board for QR and API payment flows.
Use QuLink when existing MDB vending machines need cashless payment, QR scan-to-pay, wallet callback, vend authorization, and event upload without replacing the whole machine.
MDB cashlessQR/wallet callbackVend resultTelemetry
Project fit
For existing MDB vending fleets
Buyer signals
- Operators adding QR or wallet payment to MDB vending machines.
- Payment apps that need a machine-side board for vend authorization.
- Retrofit projects where the vending controller should remain in place.
- Deployments that need telemetry, vend result, and fault upload.
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
Cashless payment plus machine-side MDB handling
QuLink bridges payment approval and MDB vend behavior, then reports vend result and machine events to your backend.
- Machine interface
- MDB cashless path, vending controller, optional auxiliary relay/serial
- Trigger source
- QuLink QR payment, wallet callback, payment app, or server approval
- Data returned
- payment reference, vend.result, fault, telemetry, online status
- Project mode
- MDB retrofit, payment app integration, vending operator rollout
Workflow
From machine interface to API-controlled result.
Map payment approval
Define wallet/QR/payment callback and vend authorization rules.
Authorize vend
QuLink handles the machine-side vend action and timing.
Report result
Your backend receives vend result and fault/status 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/MDB-77/commands
{
"command": "dispense",
"source": "wallet_callback",
"machine_action": {
"interface": "mdb_cashless",
"slot": "C03"
}
}
Project RFQ
Send a machine photo. We help identify the board, interface, and next test step.
Send the MDB machine model, current payment module photo, target payment flow, vend behavior, 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 work with a third-party wallet?
Yes. The wallet or payment app can confirm payment and trigger QuLink through the API.
Is this different from a full vending controller?
Yes. This page targets retrofit and cashless integration, while OEM controller projects can go deeper into firmware and board design.
Can it support vending fleets?
Yes. Fleet rollout needs sample validation, interface confirmation, and deployment profile tuning.
Related use cases