1. Photo audit
Machine, controller, payment module, wiring, and model label come first.
Illustrative case studies
Three machine integration profiles for planning.
These are illustrative project profiles, not customer claims. Use them to compare interface, payment, machine action, data, and sample-test scope before requesting a real assessment.
3 profilesVending / laundry / lockerPayment + dataSample-first
Case library
Choose the profile closest to your machine.
Malaysia · Vending
An MDB cashless retrofit profile with a DuitNow QR callback, vend authorization, fallback relay path, and vend-result upload.
Read profile
Indonesia · Laundry
A pulse and relay retrofit profile with QRIS payment approval, timed start, session result, and fault upload for washers and dryers.
Read profile
Thailand · Smart locker
A relay lock and door-sensor profile with PromptPay QR or app approval, unlock, rental status, return event, and heartbeat.
Read profileCase 01 · Malaysia · Vending
QR payment retrofit for a 60-machine vending fleet
An MDB cashless retrofit profile with a DuitNow QR callback, vend authorization, fallback relay path, and vend-result upload.
- Market
- Malaysia (illustrative)
- Fleet
- 60 vending machines (illustrative)
- Interface
- MDB cashless path with relay fallback
- Payment
- DuitNow QR callback through the operator's provider
- Action
- Vend authorization and slot dispense
- Data
- payment reference, vend result, fault, heartbeat
- Sample
- 2 machines, then a phased pilot
Case 02 · Indonesia · Laundry
QRIS timed-session retrofit for a laundry room
A pulse and relay retrofit profile with QRIS payment approval, timed start, session result, and fault upload for washers and dryers.
- Market
- Indonesia (illustrative)
- Fleet
- 24 washers and dryers (illustrative)
- Interface
- pulse input and relay output
- Payment
- QRIS callback through a local provider
- Action
- timed relay start for one wash or dry cycle
- Data
- session start/end, fault, online status
- Sample
- 2 machines, then one laundry room
Case 03 · Thailand · Smart locker
PromptPay QR unlock profile for a smart locker bank
A relay lock and door-sensor profile with PromptPay QR or app approval, unlock, rental status, return event, and heartbeat.
- Market
- Thailand (illustrative)
- Fleet
- 36 locker doors (illustrative)
- Interface
- relay lock and door sensor
- Payment
- PromptPay QR or app approval
- Action
- unlock, rent, return, query status
- Data
- door status, unlock event, heartbeat, fault
- Sample
- 4 doors, then one locker bank
Comparison
What changes between the three profiles.
Market
Machine / interface
Payment to action
Data
Malaysia
Vending / MDB cashless + relay fallback
DuitNow QR → vend authorization
vend result, fault, heartbeat
Indonesia
Laundry / pulse + relay
QRIS → timed session
session result, fault, online status
Thailand
Locker / relay + door sensor
PromptPay QR → unlock
door status, unlock event, heartbeat
What stays the same
Five steps that apply to every machine.
2. Interface map
Confirm MDB, pulse, relay, serial, or OEM behavior before choosing a board.
3. Payment ownership
Decide who confirms payment and how the callback reaches the machine command.
4. Failure behavior
Define timeout, retry, cancel, and what the machine should do if payment fails.
5. One-unit sample
Validate the action and result data before a pilot or fleet rollout.
Project RFQ
Send a machine photo. We help identify the board, interface, and next test step.
Send machine photos, controller and payment module photos, the target action after payment or API approval, and the 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 about these profiles.
Are these real customers?
No. They are illustrative profiles created to show a typical planning path. They are not customer claims, performance guarantees, or deployment references.
Can the same path work for our machines?
The overall path is common, but the board, wiring, firmware, and payment callback must be confirmed on a real machine.
What should we send first?
Machine photos, controller and payment module photos, wiring notes, the target action, and the expected quantity.
Can we use our own payment provider?
Yes. Your provider can confirm payment first, then call the QuLink command API for the machine-side action.