Keep the existing reader
The reader works and the machine already accepts cards. Add a board only when you need remote status, vend results, or an independent data path.
Guides
Vending cashless retrofit
How to add cashless payment to a vending machine.
To add cashless payment to a vending machine, first confirm whether the controller has an MDB cashless path, a pulse/relay input, or a serial interface. Then choose between keeping the existing reader, adding an MDB cashless board, or using a QR/API trigger. QuLink handles the machine-side action and returns vend results; payment acquiring stays with your provider. Machine-level verification is pending sample.
MDB cashlessQR / card readerVend resultSample-first
Part of MDB Vending Machine API Gateway
Payment paths
Four ways to add cashless payment.
Start with the machine interface and the reader you already have. The right path is the one that keeps the machine stable.
Add an MDB cashless board
The vending controller has a standard MDB cashless path. The board handles vend authorization, events, and result upload.
Use a QR / API trigger
Payment is approved by your app, wallet, or server, and the machine accepts a relay, pulse, MDB, or serial action.
Replace the payment module
The reader is old, 3G-only, or unstable. A new reader or integrated payment board may be cleaner than repairing it.
Before you choose
Check these four things first.
Controller interface
Confirm MDB, pulse, relay, UART/serial, RS485, or cabinet-controller wiring before choosing a board.
Existing payment hardware
Check the reader model, power, MDB harness, SIM/antenna, and whether the reader is still supported.
Payment ownership
Decide whether QuLink QR payment, your PSP, or an existing reader will confirm payment.
Result and data
Define vend success, failure, timeout, fault, and telemetry events you need in your backend.
Retrofit flow
From machine photos to a sample test.
Send machine photos
Machine front, controller board, payment module, model label, and connectors.
Choose the payment path
MDB cashless, QR/API trigger, pulse/relay, or a new reader.
Test one machine
Validate payment, vend, timeout, failure, and result reporting.
Roll out with a profile
Lock firmware, wiring, enclosure, and event schema before the fleet.
Where QuLink fits
Machine-side payment, not payment acquiring.
What QuLink can do
- Add an MDB cashless or QR/API payment path to an existing controller.
- Keep the existing reader when it is stable and only add machine-side visibility.
- Return payment reference, vend result, failure, timeout, and fault events.
- Support relay, pulse, serial, or custom interfaces when MDB is not available.
What it does not replace
- Payment acquiring, bank settlement, or wallet balance.
- A repair shop for a damaged card reader.
- A guaranteed replacement for every machine controller.
- Certified electrical installation or machine safety.
Not the right fit if
- You only need a payment acquiring account and no machine-side action.
- There is no physical vend, unlock, relay, pulse, or session to trigger.
- You have no machine, controller, reader, or wiring information.
Interfaces and data
What the retrofit needs to handle.
- Machine interface
- MDB cashless, pulse, relay, UART/serial, RS485, or custom cabinet controller
- Payment options
- QuLink QR payment, existing card reader, PSP callback, wallet, or server approval
- Data returned
- payment reference, vend.result, failure, timeout, fault, online status
- Project mode
- single-machine pilot, cashless retrofit, OEM payment board, fleet rollout
FAQ
Cashless retrofit questions.
Can I add cashless payment without replacing the vending controller?
Often yes. If the controller exposes an MDB cashless path, pulse/relay input, or serial interface, the retrofit can start there. Photos and a sample test confirm the path.
Should I keep my existing card reader?
Keep it when it is stable and supported. Add a machine-side board if you need vend results, telemetry, or an independent status path. Replace it when it is old, 3G-only, or unreliable.
What is the difference between MDB cashless and a QR/API trigger?
MDB cashless uses the vending controller's cashless path. A QR/API trigger can use relay, pulse, serial, or MDB to start the machine after your app or server approves payment.
Can QuLink process the payment?
QuLink can provide an optional QR payment workflow. You can also keep your own PSP, wallet, or card reader and use QuLink only for the machine-side action and result.
What should I send first?
Machine model, controller and payment module photos, wiring notes, country, and the action after payment. A photo is usually more useful than a long spec.
Project RFQ
Send a machine photo. We help identify the board, interface, and next test step.
Send the vending machine model, controller and payment module photos, country, and the action that should happen after payment.
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
Related use cases