Privilege as a Payment Type

Privilege is a type of payment, similar to credits or timeplay. Instead of spending a certain number of credits to start a machine, you are given a specific number of plays. For example, if you load 10 privilege games onto your card, you can start supported arcade machines 10 times, no matter how long or short each game lasts. Each play counts as one use.

In this document, you will be provided with quick guidance on the usage of the privilege package on the VC Touch Kiosk. When checking the balance, users are allowed to check the privilege package information, including the package name, plays left, and expiry date. In addition, the KioSoft Edge Box can be actively engaged to support the usability and ensure the stability of the privilege transactions by supporting privilege transaction processing and package information checking on the Kiosk. Upon completion of the transaction, users can log in to KioCentral Pro and navigate to the Transaction Report to check or retrieve more transaction details.

Privilege Display on VC Touch Kiosk

If a valid privilege package is deployed on the VC Touch Kiosk, the package information will also be displayed on the screen when checking the balance. You can refer to the steps below.

Tap to select the "CHECK BALANCE" option on the tablet screen.	Place and hold the card to the reader as instructed on the screen.
The card balance information and package information are displayed on the screen.
You can tap "YES" to add value to the card following the procedure in the Chapter "Add Value to Card," or tap "NO" to exit the page.

Create Privilege Packages for a Location

To create the privilege package profile, you should log in to ScoreBoard and go to CCM → Machine Groups. By entering details such as package name, descriptions, locations, and machines, you can set up its profile and see privilege usage records through ScoreBoard. Each package is assigned to a specific or multiple locations, granting access exclusively to those assigned. You can refer to the following steps to complete the configuration:

The Privilege feature is in the pilot phase and has limited availability to customers.

• Create Package

1. Click CCM → Machine Groups on the navigation menu to enter this section.

2. Click the "Create Group" button to enter the Create Machine Group page. Fill in the values for Machine Group Name, Group Description, Location, and Machines, respectively.

For your reference, fields explanations are provided in the next table:

• Edit Package

Click the "Edit" button in the created packages list to enter this section. You can edit the existing package's configuration, including the package name, package description, location, and machines. Click on Save to keep your changes.

• Delete Package

Click the "Delete" button in the list of created groups. A message box will pop up to confirm the action. If you click on "Yes", the created group will be deleted successfully. If you click on "No", it will return to the list page.

• Search Package

You can enter the keywords in the search bar to find a target privilege package. The search results will be presented in the list below.

Obtain Privileges on CenterEdge POS

Customers can go to the front desk with a Cloud Card, and the staff can add the privileges to the card using the CenterEdge POS.

Tap the Card on the Elevate Touch to Start the Machine

When customers tap the card on the Elevate Touch, it will send the payment request to the server to validate the accessibility of the privileges. If the privileges are available for use, one play count will be deducted to start the machine, and the remaining play counts will be displayed on the reader’s screen. If the transaction failed due to some reason (e.g., insufficient balance), the privilege will be refunded to the card automatically.

The display of UIs will be shown as below when the privilege is successfully used and fails to deduct due to the insufficient balance.

Note

When privileges were used in transactions, the reader will send a request to server to validate whether the privileges are eligible or sufficient for use.

• If the privileges are valid for use, plays would be deducted from the privilege group and the remaining plays count will be returned to and shown on the reader.

• If there is no valid privileges for use, the transaction would be considered to be failed.

Note

When all available privileges have been used up or proven to be invalid, the loyalty points or credits/value (depending on the location mode) will be used to start machine given the priority rules of deduction:

Timeplays > Privileges > Loyalty Points > Credits/Value.

• Prerequisites for Using Loyalty Points to Start Machine:

  1) Ensure there are available loyalty points stored in account for transactions.

  2) Make sure to enable loyalty program at location level.

• Prerequisites for Using Credit/Value to Start Machine:

  1) Ensure that the “Credit/Value” checkbox has been ticked via CCM → Universal → Universal Pulse → Payment Types and Methods → Cloud Card Payment Types (Refer to Configure Privilege as a Payment Type for Readers of this article).

  2) Please note that credits/value cannot be used to start machine during the privilege cooldown intervals.

Note

To deploy a brand-new Elevate Touch, you can log in Scoreboard → CCM to create a Universal Pulse profile for location, machine and reader's configuration or custom setup. Please refer to the article General Deployment Process for Universal Pulse Profile for more detailed instructions on the initial deployment process.

Check Privilege Records in Reports

The privilege-based plays will become fully visible for amusement operators who have the expectation to track and analyze the scenario where the privilege plays are selected by the customers. The operator can use the following elements to fully obtain the updates of privilege plays in the Transaction Report and Refund Report (Please skip to Section 2 Refund Report for more instructions in this article).

Transaction Report

A column "Privilege Change" is added in the report, which presents the change of the privilege package balance by recording the exact change amount and the package's name. When privilege is selected to start the machine, the operator can log in to check the privilege balance on a timely basis.

For the purpose of quick access to the privilege records, the operator can use the filters to search for the privilege-related records. Additionally, the columns concerned would be helpful to facilitate the privilege-related analysis.

a. Filters: select "Payment Type" as "Privilege", "Transaction Type" as "Game Card Transaction."

b. Please refer to the table below for more descriptions:

If the Privilege is used by the third-party POS system, the transaction records of it will be considered as the 3rd Party Adjustment, which can be checked on a timely basis as well.

a. Filters: select "Payment Type" as "3rd Party Adjustment" and "Transaction Type" as "3rd Party Adjustment."

b. Please refer to the table below for more descriptions:

Note: For privilege used as the 3rd party adjustment system, it's highly suggested to save the transaction details as screenshots for future retrieval. Besides, you're recommended to export the transaction records as a local file if needed.

Supported Feature: Edge Box

• Server Deployment

KioSoft Edge Box is supported when the privilege package is used for transactions on Kiosks. The KioSoft support team should go to vendor portal to enable the configurations curated for Edge Box during the deployment stage.

Log in to vendor portal → Locations, search for the target location, and click on the "Edit" button. Under the "Options" tab, you can find a section called "Others." In this section, select the "Enable" for "On-Premise Server," and there will be three mandatory fields (Network Downtime, Server IP Address, and Server Port) displaying underneath it, which should be filled in based on the actual business needs and the location’s server information.

• Known Issue

For the Edge Box version that supports the privilege feature, the privilege balance between the Edge Box and the Server is not synchronized in real time for a few scenarios. Any changes on the server side are not synchronized with Edge Box in real time. This data is only updated on the Edge Box as a trigger when the Edge Box is communicating with the server from its side (Trigger actions could be add balance on the kiosk or tap a cloud card at a reader).

For example, if there are 7 privilege packages in the server, and then a new privilege package is added through an external 3rd party request, there should ideally be 8 privilege packages on the cloud card balance. Let’s say now you use 1 privilege at a reader, your new updated balance should be 7 privileges left. With the current limitation, the card balance will display 6 packages left when it retrieves the balance from the Edge Box. This is because the Edge Box never got the new 1 package addition from the server, so it still thinks that the card originally had 7 packages, and after using 1, it has 6, and the reader will only display the balance as 6. After the transaction has been completed (the balance has been displayed), the edge box will synchronize the balance with the server.