Confirm payment flow
Decide whether QRIS is handled by QuLink, your payment partner, or your own backend.
QRIS machine payment hardware
QRIS payment controller hardware for vending and self-service machines.
Use QuLink when a Indonesia machine project needs QRIS payment approval to trigger a real machine action such as vend, relay, pulse, unlock, or timed start.
QRISPayment callbackRelay / pulse / MDBResult upload
Project fit
For Indonesia operators, payment apps, and machine integrators
Buyer signals
- Projects using Indonesian bank apps, e-wallets, payment gateways, or QRIS payment callbacks.
- Machines such as vending machines, laundry machines, smart lockers, charging sockets, and self-service retail cabinets.
- Teams that already have a payment provider but need machine-side hardware.
- Operators that need payment reference, machine action, and result callback in one workflow.
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
QRIS approval becomes a machine command
QuLink does not need to replace your payment provider. Your checkout or wallet callback can approve payment, then the QuLink controller executes the machine-side action and reports the result.
- Payment source
- Indonesian bank apps, e-wallets, payment gateways, or QRIS payment callbacks
- Machine output
- MDB vend, relay output, pulse simulation, unlock, serial command, timed session
- Data returned
- payment reference, command accepted, machine started, vend.result, session completed, fault
- Project mode
- payment app integration, operator retrofit, OEM machine controller, pilot rollout
Workflow
From machine interface to API-controlled result.
Identify machine interface
Check MDB, pulse, relay, serial, RS485, or custom controller wiring from photos.
Map approval to action
Define device ID, product, price, session duration, relay channel, or vend slot.
Run sample test
Validate the payment callback, machine action, timeout behavior, and result upload on one machine.
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/{device_id}/commands
{
"command": "start_session",
"source": "qris_callback",
"reference_id": "PAYMENT-REFERENCE",
"machine_action": {
"type": "relay_or_mdb",
"duration_ms": 900000
}
}
Project RFQ
Send a machine photo. We help identify the board, interface, and next test step.
Send the Indonesia payment flow, machine photos, interface notes, target action after QRIS payment, and expected rollout 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.
Does QuLink process QRIS directly?
QuLink can discuss QR payment workflows, but many projects keep QRIS with the customer's payment provider and use QuLink for the machine-side action.
Can this work with our own wallet or payment backend?
Yes. Your backend can confirm payment first, then call QuLink to trigger the machine.
What should we send first?
Send machine photos, current payment module photos, target payment flow, and the physical action needed after payment.
Related use cases