One request,
every device.
Whichever manufacturer made the device, a sale starts with the same request; the connection is made app to app, through the local interface or via the manufacturer's cloud.
Products that work together in this industry
- In-store POS
- Identity Intelligence
What gets harder across devices?
- 01
Separate code per manufacturer
Writing a separate integration for each device brand slows you down.
- 02
Different connections
A device may connect through an app, a local interface or the cloud.
- 03
Model differences
Not every model supports every operation; support should be known per model.
- 1
Register the device
The connection method is set in the device record.
- 2
Send the request
A sale starts with the same request on every device.
- 3
It reaches the device
The command is delivered to the device by the selected method.
- 4
The result arrives
The payment result is sent by webhook.
Features chosen
for your needs.
- In-store POS
Connection methods
The payment request reaches the device through the Lunixi app or the manufacturer's cloud; the API request is the same for every device.
Details - In-store POS
Payment operations
Full and instalment sales, pre-authorisation, void; full, partial and item-level refunds, meal cards and tracking of uncertain outcomes.
Details - In-store POS
Stores and devices
Stores and tills, logical terminals and bank merchant numbers, device registration and pairing; the terminal stays when the device changes.
Details - Identity Intelligence
Mobile and POS threat
Verify with hardware that the native app is genuine, see clones and interception; assess in-store terminal and cashier risk per transaction.
Details
Other use cases in this area
Let's plan the right setup
for your industry together.
We'll listen to how your banks, channels and processes work and map out the setup that fits you, together with our team.
For enterprise inquiries: [email protected]