Introduction

A payment terminal, also known as a point of sale (POS) terminal is a device used to authorize bank cards and conduct payment transactions. A terminal contacts the r_keeper 7 cash station using one of the supported protocols described below. Depending on the protocol, a bank card can be read using its own bank terminal reader or a reader connected to the r_keeper 7 cash station.

Payment terminals allow paying for orders using bank cards, with an automatic request for transactions to the r_keeper cash station. For this:

  1. Allow using the terminal for the selected card type. To do this, go to Money > Currencies > Credit cards and check the Use POS terminal box in the Interface section of the card properties
  2. Add the appropriate device to the configuration. To do this, go to Service > Stations and Devices, select the required cash station and add the driver you need on the Drivers tab
  3. Create a logical device on the Printers tab. To do this, go to Service > Stations and Devices and open the Printers tab of the required cash station
  4. Select the created device as the POS Terminal. To do this, go to Service > Stations and Devices, select the required cash station and in the Printer Assignments section of its properties, select the created device in the Authorization Terminal field.

The general settings for the Verifone vx510 and Ingenico 5100 terminals are as follows:

The vx510 driver has the CmdRetries configuration parameter. It determines the number of attempts to execute the authorization command if the terminal does not give either a positive or a negative response to it.

Interaction Scheme

Schematic diagram of the interaction between the authorization terminal and r_keeper 7:

There may be no bank software.

Document views can be found in Printing Schemes. To do this, go to Options > Printing > Printing Schemes. Select the Main > Card authorization group. Make sure the Document type is Terminal Authorization.


Supported protocols
EFTPos
The r_keeper 7 driver file is EFTPos.dll.
Supported by UnitedCardService.
TrPosX
The r_keeper driver file is Hyp4220.dll.
Lanter support.
Installation Guide
ZVPos
r_keeper driver - ZVTPos.dll
Support from EasyCash
Inpas
r_keeper driver - SA Pos INPAS
For detailed information on the authorization protocol, see the article Setting up authorization with POS terminals using the SA protocol by INPAS.

Arcus
The r_keeper driver is Arcus.dll.
Support from Arcom.
Configuration file ops.ini
Below is an example of a configuration file - ops.ini, usually configured by banking software. Some parameters from it can be used when setting the properties of the arcus.dll driver in the r_keeper 7 Manager Station:

# COMPATIBLE for PIN-PADS software for processing OPENWAY,SMARTVISTA,TIETO (NewWay v4.0.2.x)
# The structure of the operation description string (operation configuration)
#
# [op code] [op class] [op id] [op name]
#
# 1 = 1, 1, PAYMENT
# Comment sign - "#" at the beginning of the line - OPERATION IS NOT USED and cannot be called from POS software
# to ENABLE operation processing in Arcus2 mode - DELETE COMMENT SIGN
#
# Op code - operation code for the cash register, CAN BE EDITED FOR A SPECIFIC CCM IMPLEMENTATION
# Op class Op id - DO NOT EDIT !!! these codes are HARDWASHED into the PIN-PAD SOFTWARE
# Op class - operation class (1 - financial, 2 - technical, 3 - administrative)
# Op id - operation ID
# Op Name - the name of the operation to display in the cash register interface, YOU CAN CHANGE THE FORMULATION ( without changing the essence of the operation !!! )
#
# For class 1:
#1 OP_PURCHASE_SMS
#2 OP_PURCHASE_DUAL, //2
# 3 OP_PREAUTHORIZATION, //3
#4 OP_CONFIRMATION, //4
#5 OP_CANCEL, //5
#6 OP_CANCEL_ADVICE, //6
# 7 OP_BALANCE_INQUIRY, //7
#8 OP_MINI_STATEMENT, //8
#9 OP_UNIVERSAL_REVERSAL, //9
# 10 OP_UNIVERSAL_REVERSAL_ADVICE, //10
#11 OP_REFUND, //11
# 12 OP_CASH_SMS, //12
# 13 OP_CASH_DUAL, //13
# 14 OP_CREDIT, //14
# 15 OP_CREDIT_VOUCHER, //15
# 16 OP_UTILITY_PAYMENT, //16
# 17 OP_BILLING_PAYMENT_SMS, //17
#18 OP_BILLING_PAYMENT_DUAL //18
#
# For class 2:
#0 - Print log
# 1 - Reconciliation of results
#2 - Cashier Menu
#3 - Technical reversal of the last operation
#
# For class 3:
# 1.2 - Time Synchronization
#4 - TMS session
#5 - Admin Menu

# Trading and service operations (TSP)
1=1,1, PAYMENT FOR GOODS
3=1.11, RETURN OF GOODS

# Automated Banking Systems (ABS)
#1=1,12,CASH WITHDRAWAL
#3=1,14,CREDIT
#5=1,7,BALANCE REQUEST

# Hotels and gas stations
5=1,3, PRE-AUTHORIZATION
8=1,4, CALCULATION
#9=1,15,CREDIT_VOUCHER

# Cancels
2=2,3, CANCEL LAST
4=1.5, UNIVERSAL CANCEL

# reports and shift closing
6=2.0, REPORT
7=2,1, VERIFICATION OF RESULTS

# special functions (compatible with special versions of pin-pad software)
#10=2,4, READ MAP
#11=9,2, READ MAP2
#12=9,7, READ MAP3

# menu and administrative operations
#13=2,2, CASHIER MENU
99=3,5,SERVICE MENU
100=3.4, SESSION TMS

# additional functions
80=3,1,TIME SYNCHRONIZATION
#80=3,2,TIME SYNCHRONIZATION
Note

As an example of use: in the properties of the arcus.dll driver connected to work with the pinpad, 

It can be configured to automatically perform reconciliation of results when closing a shift at the checkout. That is, in the CmdClose field, write the value 7 in the Reports and closing shift section in ops.ini.

In the r_keeper manager station, configure:

Driver for cash station. Go to its properties and in the Options section specify:
Path - path to the arccom.dll library
FileRC - path to the RC.out file Registered in cashreg.ini
FileCheq is the path to the cheq.out file. Registered in cashreg.ini
CmdAuth - authorization command code. Must match the one specified in ops.ini
CmdReversal - return command code. Must match the one specified in ops.ini
CmdClose - close command code. Must match the one specified in ops.ini
IdPrint - print value identifier
NeedAskBeforePrint - ask before printing

Logical printer driver
Logical printer for POS in print destination
Authorization terminal selected as print layout for current print scheme
The authorization terminal is selected as the representation of the document with the purpose of printing

The currency has the Use terminal setting enabled. To do this, go to the properties of the currency used and expand the Interface section

If you are using a terminal without a built-in printer, the setup is identical, except:

In the copy of the Authorization Result layout, add the [SlipToPrint] memo to the created band or to the Report Title band
Instead of the Authorization terminal assignment, select the printer assignment that is used to print receipts and reports
Add a layout to the print scheme you are using.
Settings in the manager station for the GazpromBank terminal
For the terminal to work in the manager station, configure:

In the manager station, go to Tools > Stations and Devices
Select your restaurant, then go to the checkout of the cash server. Open the Devices tab

Add the POS authorization terminal > Universal driver for card validators (HTTP) driver to the checkout

In the Options section, in the FiscRegTypeID line, select 189 GasPromBank terminal (Russia) from the drop-down list

Click on the 3 dots in the LowDriverParams line and fill in the actual values ​​in the lines:
full path to emvgatessl.dll and emvgate.cfg
KKM number
Send number of guests

Save Changes
Go to the Printers tab
Using the right mouse button, create a new printer in the empty field.
Select the created printer and in the sidebar
Name your printer
Select status Active
In the Module line, select the added Universal driver for card validators (HTTP) driver from the drop-down list
Save your changes.

Go to Properties tab
In the Assign printers section, in the Authorization terminal line, select the created printer from the drop-down list

Save Changes
Go to Money tab > Currencies
From the list on the left, select Credit Cards > Credit Card Discount
Go to the Properties tab. In the Main section, in the Status row, select Active

Save your changes.
Setup completed. Slips from the bank must come in CP866 encoding.