1 | OneTab Interface Setup

This article provides a guide for the OneTab interface with Bepoz which is commonly used in bars and restaurants to close transactions. OneTab can be used to open, manage and close restaurants and bar payments. Tabs in Restaurant POS are most commonly used for customers who want pay their accumulated balance at the end of their visit. Bepoz also supports this setup given that following requirements are fulfilled.

This article provides a guide for the OneTab interface with Bepoz which is commonly used in bars and restaurants to close transactions.

OneTab can be used to open, manage and close restaurants and bar payments. Tabs in Restaurant POS are most commonly used for customers who want pay their accumulated balance at the end of their visit. Bepoz also supports this setup given that following requirements are fulfilled.

Prerequisites

• Before setup you must have External Payments authorised
• In Venue Settings>Tables, check and take note of the Bar Tab Table group
• In Venue Settings>External Links, type OneTab as the name for External Payment 1
• If External Payment 1 is being used, rename External Payment 2
• Then replace External Payment 1 for External Payment 2, in the setups below

OneTab Adaptor

• Under Venue, Stores and tills you will need to select the server that OneTab communicate with. Typically it should be the smart controller server unless you are in a multi-venue environment it would be the venue smart controller
• You will need to add a device under the server. Pic.2 shows an example of the device setup

• As you can see in Pic.2 the device setups as followed:
• Device type: transaction Queue
• External Dll Name: TransqOneTab.Dll
• Class Name: OneTab Pic.2
• also shows Device Options
• Operator number – Enter an operator Number.
• OneTab Adaptor Key – Unique OneTab Adaptor Key. (Generally it would be set as bepozonetab.)
• OneTab Merchant ID: Supplied by OneTab (This will be different for each merchant.)
• Payment Number – This is the external Payment totaliser that will report the payments done through OneTab.
• Table Group Number – the table Group Number that OneTab Will Use.
• First Tab Number – Starting Tab Number that OneTab will use

Setting Up the OneTab Payment Device

• This device must be setup on all tills that are going to use Bar Tabs with OneTab
• Pic.3 shows an example of the device setup on the till

• As you can see in Pic.3 the device setup as followed:
• Device type: External payment Link
• External Dll Name: Extpayonetab.Dll
• Class Name: One Tab
• Device Options
• One Tab Adaptor Key: Unique OneTab Adaptor Key (Generally it would be set as bepozonetab.)
• OneTab Merchant ID: Supplied by OneTab (This will be different for each merchant)
• OneTab API Endpoint: Supplied by OneTab
• Payment Number: This is the external payment totaliser that will report the payments done through OneTab
• After you have set all devices that are required to run OneTab you will need to restart smart controller to initialise the connection to OneTab
• Then contact the Club to organize a restart of each till Installed with Onetab