Audit the machine
Photograph the controller, payment module, wiring, and label; note voltage and start signal.
Guides
Control board buying guide
How to choose a vending machine control board for payment and data integration.
Use this guide when you need to compare MDB, pulse, relay, serial, QR payment, and data upload options before requesting a sample.
MDB / pulse / relayPayment triggerData uploadOEM option
Part of MDB Vending Machine API Gateway
Project fit
When you need a board selection, not another closed platform
Buyer signals
- You are retrofitting existing vending or self-service machines.
- Your app, payment provider, or backend must trigger a physical action.
- You need telemetry, vend result, or fault upload.
- You want a sample test before a fleet 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
Start from the machine interface, then choose the board
The right board depends on the machine's existing controller, payment module, start signal, and data requirements, not only on the product name.
- 1. Machine interface
- MDB, pulse, relay, dry contact, UART, RS485, or custom cabinet controller
- 2. Trigger source
- QR payment, wallet callback, app approval, operator panel, or server API
- 3. Machine action
- vend, dispense, relay on/off, pulse count, unlock, timed session
- 4. Data returned
- payment reference, vend result, session result, fault, telemetry, online status
- 5. Deployment
- sample test, firmware profile, wiring, enclosure, certification, rollout
Workflow
From machine interface to API-controlled result.
Define the action
Write down what must happen after payment or API approval, including timeout and failure behavior.
Choose the interface
Select MDB, pulse, relay, serial, or OEM based on the evidence, not assumptions.
Test one unit
Validate payment callback, machine action, result upload, and fault handling before rollout.
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": "dispense",
"source": "payment_or_api",
"reference_id": "SAMPLE-ORDER-001",
"machine_action": {
"interface": "mdb_or_relay",
"slot": "A01"
}
}
Project RFQ
Send a machine photo. We help identify the board, interface, and next test step.
Send machine photos, controller label, payment flow, target action, and expected quantity. We will help map the interface and sample path.
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.
Should I choose MDB or pulse?
Use MDB when the machine has a compatible MDB path and you need richer vending events. Use pulse or relay when the existing controller exposes a coin or start input and MDB is not practical.
Do I need a new vending controller?
Not always. Many projects keep the existing controller and add a machine-side payment and control board. OEM replacement is a separate decision.
What photos should I send?
Machine front, controller board, payment module, wiring connectors, model label, and the action that should happen after payment.
Can one board support QR payment and data upload?
Yes, depending on the interface and firmware profile; the project can combine both.
How do we start?
Run one sample test with the real machine before discussing fleet pricing or OEM customization.
Related use cases