Confirm machine interface
Check MDB, pulse, relay, serial, or cabinet-controller wiring from photos.
Guides
Coffee vending control
Coffee machine payment controller for QR, app, and API-triggered drinks.
Use QuLink when a coffee vending machine, bean-to-cup machine, or self-service coffee kiosk needs payment approval to trigger drink selection, brewing, dispensing, or a timed session.
Drink selectionMDB / pulse / relayQR paymentResult upload
Part of MDB Vending Machine API Gateway
Project fit
For coffee vending, kiosks, and office machines
Buyer signals
- Coffee vending machines that need QR or app payment.
- Machines with MDB, pulse, relay, serial, or cabinet-controller interfaces.
- Operators adding drink selection, pricing, or telemetry.
- Projects that need a sample test before a venue rollout.
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
Payment approval becomes a drink command
QuLink maps payment or app approval to the coffee machine interface, then reports drink result, fault, and status to your backend.
- Machine interface
- MDB, pulse, relay, serial/RS485, or custom cabinet controller
- Trigger source
- QuLink QR payment, app approval, wallet callback, or server command
- Machine action
- select drink, start brew, dispense, cup release, timed session
- Data returned
- drink result, payment reference, fault, telemetry, online status
- Project mode
- coffee vending retrofit, kiosk integration, OEM controller
Workflow
From machine interface to API-controlled result.
Map drinks and prices
Define product IDs, prices, cup size, recipe selection, and timeout behavior.
Trigger the drink
QuLink sends the selected drink or brew command after payment or app approval.
Report the result
Your backend receives drink result, fault, and usage 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/COFFEE-12/commands
{
"command": "start_session",
"source": "qr_payment",
"reference_id": "COFFEE-ORDER-012",
"machine_action": {
"type": "drink",
"product": "latte"
}
}
Project RFQ
Send a machine photo. We help identify the board, interface, and next test step.
Send coffee machine photos, controller and payment module photos, interface notes, drink menu, target payment flow, and 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 select a specific drink?
That depends on the machine interface. MDB, serial, or cabinet-controller profiles may support product selection; simpler relay machines may only start a fixed cycle.
Can it work with MDB coffee machines?
Yes, when the machine exposes a compatible MDB path. The sample test confirms vend behavior and event reporting.
Can we offer free vend or app-only control?
Yes. Your app or backend can authorize a drink without a payment step, or combine payment and authorization.
Can it report faults and usage?
Yes, when the machine exposes the necessary signals or controller events.
Related use cases