RoxPos | Pavo Integration Setup

Setup Steps

1. Prepare the Pavo Device

Have your Pavo device's connection and terminal/serial details ready.
Make sure the device is connected to your business's local network and up to date.
Contact the RoxPos support team to start the activation suitable for your device model.

2. Define It in the RoxPos Panel

In the admin panel, go to Settings > Integration > POS Integration.
Select Pavo as the provider and enter the device/terminal details.
Save the definition; the device is assigned to the relevant branch.

3. Test and Go Live

Send a payment through a test check to verify communication with the device.
Check that the receipt/document printout and the collection record are reflected correctly in the panel.
If there is an issue, our support team provides remote guidance.

Connection Types

UniCloud

How it connects: The RoxPos server sends the sale to the Pavo cloud; it lands in the device's pending list and the result comes back to RoxPos.
Local program: Not needed.
Panel setting: Settings ▸ POS Integration ▸ Pavo: 'UniCloud (Pavo cloud)', Terminal Code, device serial no., AppToken, ApiKey, Merchant Uid and the device pairing code.
Payment type: Optional: if a type linked to the fiscal device is chosen the device opens with that type, otherwise the type is chosen on the device.
Table / Quick Sale receipt: Sent from the table and Quick Sale (the device must be paired); split payment is done on the device.
Online order receipt: No automatic receipt; it is sent manually from the order details with 'Send to POS (Receipt)' and lands in the device's list.
Invoice information slip / receipt limit: No document type choice: if the customer details are complete they go to the device as the customer, otherwise the device asks for them. If the amount reaches the receipt limit in General Settings, the device asks for customer details.

REST (local network)

How it connects: A client on the same local network as the device runs the sale: the web panel through Print Agent, the mobile app directly (HTTPS 4567 / HTTP 4568).
Local program: Print Agent on a PC on the same network if you send from the web panel; not needed in the mobile app.
Download and setup →
Panel setting: Settings ▸ POS Integration ▸ Pavo: 'REST (device on the local network)', Terminal Code, serial no., the device's local network address and REST pairing; optional 'Payment type required'.
Payment type: Depends on the setting; off by default (with no type it is chosen on the device).
Table / Quick Sale receipt: Sent from the table and Quick Sale; from the web panel it cannot be sent unless Print Agent is running. Split payment is done on the device.
Online order receipt: Manual and automatic. The automatic receipt is issued by a web panel open on the same network as the device (with Print Agent) or by the mobile app in the foreground.
Invoice information slip / receipt limit: No document type choice: if the customer details are complete they go to the device as the customer, otherwise the device asks for them. If the amount reaches the receipt limit in General Settings, the device asks for customer details.

Compare all brands and connection types →

Why Use It?

Payment and collection are taken through the Pavo device and posted to the check automatically.
Receipt/document processes run integrated with the operation.
Collection records are reflected correctly in the reports.
REST (local network) — the register connects directly to the device over the same Wi-Fi/network; a one-time pairing with 'Accept' on the device, fast collection.
UniCloud (Pavo cloud) — the device pairs through the Pavo cloud (you enter the on-screen code on the device); the same network is not required and every table lands in the device's pending list.
Fiscal sale on the device — items and VAT rates go to the device; cash, card and meal-card collection is completed on the device and the result is written to RoxPos automatically.
Flexible payment type — if you pick the type in RoxPos the device opens with it; if not, the cashier picks it on the device. In REST the 'Payment type required' setting is optional.

Frequently Asked Questions

What is the difference between REST and UniCloud?

With REST the register connects directly to the device over the local network (the print agent in the web panel, the phone in the mobile app); it pairs once with 'Accept' on the device and collection starts immediately. With UniCloud RoxPos sends the sale to the Pavo cloud and the device receives it from there; the same network is not required and every table waits in the device's pending list until the cashier picks it. The device runs one integration type at a time; the type is chosen in the device settings and in RoxPos under Settings > POS Integration.

Which one should I choose?

If the register and the device are on the same network and speed matters, REST; if the register is elsewhere, you want no network setup, or you will queue tables and collect on the device, UniCloud.

How is pairing done?

With REST, pressing 'Pair' in RoxPos shows a confirmation screen on the device, completed with 'Accept'. With UniCloud, RoxPos generates a pairing code; you enter it via the pairing icon on the device's sales screen and the approval reaches RoxPos on its own.

Is a payment type required?

Not with UniCloud; if you do not choose one, the cashier picks it on the device. Not by default with REST either; you can make it required with the 'Payment type required' switch in Settings > POS Integration. If the chosen type is linked to the fiscal device, the device opens directly with it.

Is an additional device required for the Pavo integration?

Your existing Pavo device is enough. RoxPos runs in the cloud; the activation steps are completed together with our support team.

Are collections reflected in the reports?

Yes. Payment and collection records are reflected in the reports by channel; you see turnover and payment breakdown from a single panel.

Can I use it in multiple branches?

Yes. You can define a separate device for each branch, manage all branches from a single account and get comparative reports.