POS Integration service

Architecture

How the system works

Token operators, by using the Token X admin panel, register customers. Then, operators organize the store branches, pump OKC terminals, and market terminals in the branches. So, the system pairs the terminals.

As the oil is released to the customer, the Token Pump OKC moves to the payment acceptance mode. Users can make the payment either in Pump OKC or from market POS. Therefore, Pump OKC adds the sale order to the Token X cloud. Market POS gets the order from the Token x cloud when the Market operator presses the menu of Market POS. Market pos must lock the order with the Token X cloud as it moves into the payment state.

As the Market POS finalizes the sale and takes the payment, it must return the sale info to the Token X cloud for Pump OKC to register to the fiscal memory and inform the GIB systems.

The Integration Checklist

Setup

API Environments - Test environment base URL: https://test-api.devtokeninc.com Authentication & Authorization - Token will share the Client Credentials for Authentication and the virtual terminalId.

Sale Flow

Please follow Energy->Instore POS Integration

1. 1000TR adds order after filling fuel is done.

2. Instore POS lists orders by consuming Get Order Summary List API

3. The POS gets order details by consuming Get Order API, when cashier selects related plate number from order list.

4. The POS locks the order, when cashier proceeds to payment. If lock is successful, then the POS allows to payment, otherwise, not allowed.

5. According to payment status,

   1. If payment unsuccessful, then POS must send unlock request.

   2. If payment successful, then POS sends payment request with customer slip data.

6. 1000TR completes order with receipt info.

Access to API's

Token X (Digital Sales Platform)Token X (Digital Sales Platform)