Map slots and locks
Confirm lock wiring, slot numbering, sensors, and board channel count.
Guides
Power bank cabinet control
Power bank cabinet control board for slot unlock, payment, and status upload.
Use QuLink when a shared power bank cabinet, charging station, or rental locker needs QR payment or app approval to unlock a slot, track return status, and upload usage data.
Slot unlockReturn sensingQR / app triggerUsage upload
Part of Pulse Relay Controller for Laundry and Timed Machines
Project fit
For shared power banks, charging stations, and rental lockers
Buyer signals
- Power bank rental cabinets with lock or slot control.
- Shared charging stations that need QR payment or app unlock.
- Lockers and rental devices that need return or occupancy sensing.
- Operators that need slot status, rental events, and fault alerts.
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 unlocks the right slot
QuLink maps a payment or app request to a slot lock, then reports unlock, return, occupancy, and fault events to your backend.
- Machine interface
- slot lock relay, door sensor, pulse input, RS485/serial, 4G option
- Trigger source
- QuLink QR payment, app approval, user account, or server command
- Machine action
- unlock slot, release lock, query slot, detect return
- Data returned
- slot status, rental start/end, return event, fault, online/offline
- Project mode
- cabinet retrofit, shared charging rollout, OEM controller
Workflow
From machine interface to API-controlled result.
Define rental rules
Set price, deposit, rental duration, return behavior, and timeout handling.
Unlock after approval
QuLink opens the requested slot after payment or app authorization.
Report return and status
Your backend receives unlock, return, occupancy, and fault 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/PB-CAB-03/commands
{
"command": "unlock",
"source": "app_command",
"reference_id": "PB-RENTAL-003",
"machine_action": {
"slot": 5
}
}
Project RFQ
Send a machine photo. We help identify the board, interface, and next test step.
Send cabinet photos, lock and sensor wiring, slot count, rental rules, target payment flow, and 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.
Can one board control multiple slots?
It depends on the lock count, sensor inputs, wiring distance, and board channels. Send the cabinet layout and slot count for evaluation.
Can it detect when a power bank is returned?
Yes when the cabinet provides a slot sensor or return signal that the board can read.
Can it work with QR payment?
Yes. QuLink QR payment or your own app can authorize the unlock action.
Can it upload rental data?
Yes. Unlock, return, slot status, fault, and online status can be sent to your server.
Related use cases