Connecting Centara to Loyalty

In order for the POS to connect to a Loyalty server, the POS needs to have instructions to activate the Loyalty plugin. Prior to that, Centara loyalty plugin must be enabled in Centara server. When that has been done, a Loyalty plugin option appears so that an instance of a Loyalty plugin tag can be assigned to a POS in the RDM.

To enable Loyalty plugin in Centara server

1. Click Admin -> Server configuration -> Plugins

2. Find and check CENTARA-LOYALTY

3. Click Save at the bottom of the screen

Gather access tokens to apply to each POS

Access tokens authenticate a client to the server. POS in this case is a loyalty client so an access token must be acquired for each POS that will communicate with the loyalty server. The loyalty server pairs merchants to stores that has been set up in the Centara device web. So once a merchant has been paired with a store, the merchant is aware of all the POS within that store and can generate access token for it.

1. Log on to Loyalty server.

2. Click the details link to the right of an existing Merchant.

3. Click Request access token button to view access token for a given POS.

Assign loyalty plugin instance to a POS

Loyalty plugin instance must be assigned to each POS with information about where to connect to a Loyalty server and also with an access token to use which identifies the client to the user.

1. Click Setup -> POS to expand the configuration of each POS to apply settings to

2. In the right side banner of the screen, click << New loyalty to add a new instance of the Loyalty plugin to the POS

3. Navigate into the newly created plugin instance by clicking "Plugin" (as seen on the picture below).

4. Add value containers for Access token and Loyalty server and assign appropriate values to their inputs.

   1. Access token: Copy/paste access token value from the loyalty web.

   2. Loyalty server: https://centara.online/loyalty/gw

5. Click Change ID and change the ID from default "1" to "loyalty"

6. Publish the changes.

Just like it is, with every plugin change to a POS, it will have the effect that the server issues a new subversion of the POS application which in turn is downloaded by the POS.

Because of this, the plugin will not be activated on the POS until it is restarted after the POS has downloaded that new version. Click Admin -> Workstations to monitor when the POS has downloaded that new version.