Confirm the machine interface
Send the controller label, wiring photos, and the action the machine must perform.
Guides
MDB controller board
QL-MDB-100 MDB controller board
A machine-side MDB controller for vending and coffee machines. Connect your payment system, trigger vend or machine actions, and receive result data in your own backend.
MDB pathAPI commandVend result4G telemetry
Part of MDB Vending Machine API Gateway
Project fit
For vending and coffee machines with an MDB cashless path
Buyer signals
- Vending machines with an MDB controller or cashless harness.
- Coffee machines that need payment or app approval to start a drink.
- Projects where the existing cabinet and controller should stay.
- Teams that need vend result, fault, or session data in their own backend.
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 need a payment acquirer account or card settlement.
- The machine has no MDB, pulse, relay, serial, or other controllable interface.
- You need a guaranteed compatibility statement before a sample.
Integration model
From API command to MDB action
Your payment provider, app, or backend approves the transaction, then calls QuLink to trigger the machine action. QuLink reports the result and status back to your server.
- Product model
- QL-MDB-100
- MDB
- MDB master / slave; MDB 4.2 / 4.3 profile
- Pulse input
- 1 channel; 12/24V opto-isolated
- Pulse output
- 2 channels; 50–500 ms configurable
- Relay
- 2 channels; NO / NC / COM
- Relay rating
- 10A 250VAC / 10A 30VDC
- Power input
- 12–24V DC; 2A
- Communication
- UART / RS232 / RS485
- Connectivity
- 4G LTE Cat.1; Wi-Fi optional
- Offline storage
- 8 GB; up to 30 days
- Firmware
- Standard firmware; OTA update support
- Indicative sample price
- USD 229–329 for one sample; final quote after interface review
- Applications
- Vending machines, coffee machines, lockers
Workflow
From machine interface to API-controlled result.
Map the command
Define the API command, machine action, result fields, timeout, and fault behavior.
Test one machine
Validate the command, machine action, result, and reconnect behavior on a sample.
Configure the rollout
Confirm connector, firmware, quantity, and support before production.
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/VEND-01/commands
{
"command": "vend",
"slot": "B04",
"reference_id": "ORDER-1001"
}
Project RFQ
Send a machine photo. We help identify the board, interface, and next test step.
Send the machine model, controller photos, and target action. We will confirm the MDB path and the next sample test.
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.
Does QL-MDB-100 replace the existing vending controller?
No. It works with the MDB path exposed by the existing controller. The exact behavior is confirmed on a sample.
Can we keep our own payment provider?
Yes. Your provider or backend approves the transaction, then calls the QuLink API.
What data can it return?
Available vend result, fault, session, and device status fields are confirmed from the machine interface.
What should we send first?
Machine model, controller label, reader or payment module, harness photos, and the target action.
Related use cases