RELEASED    

Prerequisites are located in the menu on the left.

Integration with BaxiAgent pay terminal solution

(RTP-27856)

EG POS has added support for "BaxiAgent" pay terminal solution from Nets. The solution uses existing DLL as Baxi.Net solution also uses. In addition a separate BaxiAgent program needs to be installed and run locally, preferably as a service. Typical pay terminal types used are Lane/5000 and Lane/3000, but these will have different software that similar types used for Baxi.Net. Terminals may be connected via ethernet cable.

NB!

For now there is a bug in BaxiAgent making it impossible to configure terminal via existing 'BaxiConfig' parameter, hence manual editing 'Baxi.ini' file must be done.

POS Configuration

'BaxiAgentInUse' (default 'False') - must be activated to use BaxiAgent.

'BaxiAgentIp' (default "127.0.0.1") - Where to find Baxi.Agent. Normally installed / running on each POS so use default value.

'BaxiAgentPort' (default 6000) - Where to find Baxi.Agent. Normally installed / running on each POS so use default value.

'BaxiAgentTerminalId' (default empty) - TerminalId of the payterminal to use. Must match the Id set in terminal settings.

'BaxiAgentEcrId' (default "ECR1") - Always use default value. 

'PayTerminalType' (default 'None')  - must be set to 'BaxiDotNet'

'PayTerminalVerboseLogging' (default 'False') - must be acivated (at all time) to get detailed logging to EG's logfile.

'PayTerminalReportTime' (default 'Disabled') - must be activated by setting HH:MM, on 1 POS only, to trigger automatic reconciliation.

Integration of Signotec signature pad in Self-service

(RTP-26667)

Signotec Sigma LCD Signature pad can be used in SCO to get a customer signature if the bank terminal is offline or if the payment card require a signature. POS will display a message to the customer saying "Signature required - One of our staff is coming to assist you" and a the same time a surveillance message will be displayed to staff alerting them to help the customer with the signature. A staff member will have to scan their cashier card in self-service POS to enable the signature pad. Customer will then sign and staff member can confirm the signature on screen. In the event that the signature is rejected the customer must sign again. 

If the customer should leave without signing, the bank transaction is completed but without the signature it is not valid. POS will be waiting with the "Signature required...." message on screen. If a staff member encounter this situation it is possible to press the (POS) screen and scan a cashier card while in the empty signature view to end the transaction. The customers receipt and a signature receipt will be printed. POS is then available for new customer. 

Other requirements

The Signotec Sigma signature pad needs Microsoft Visual C++ Redistributable 2010 and 2015 installed. If the cash register does not run SQL server 2018 or newer the mentioned redistributable packages must be installed manually.

POS Configuration 

Parameter SignotecEnabled - default value 'False' - if activated will enable the Signotec Sigma LCD signature pad to be used for customer signatures for bank terminal transactions which requires a signature from the customer.

Parameter PublicKeyForSignatures default empty - when specified is used by POS to encrypt the digital signatures from the Signotec signature pad. The value will be generated by Chain Web.

Existing parameter: 

BankShowSignatureMessage - default value 'True' - should be deactivated (set to 'False') to prevent POS from displaying two messages about the signature needed to the customer, and thus requiring the cashier to log on twice to enable the signature pad.

Improvements POS

AreaDescription
Convenience

Epsilon Express widget fixes(RTP-28404)

When selecting one of the pumps in the Epsilon Express widget, options are shown and can be selected. Also, when logging out or logging in out of Convenience Sales View, widget is displayed correctly.

Fuel integration

Error handling improvements (RTP-28979)

Error when not authorized to Fusion, is being handled in a better way.

Loyalty

Only optional coupons in the 'Select optional coupons' view. (RTP-28642)

Only optional coupons will be visible in the 'Select optional coupons' view. Previously, both optional and non-optional coupons would be visible it this view, causing the view to open automatically when entering tender view even if the only coupon for the member was non-optional (redeem automatically). This happened if 'ShowOptionalCouponsOnTender' was enabled (True).

Foreign mobile phone numbers shown in 'Loyalty header' (RTP-28891)

If configured in parameter 'LoyaltyHeaderInSaleView' the members mobile phone number will be displayed in the loyalty header in POS regardless of what country the mobile number belongs to. Previously, the mobile phone number would only be displayed if it was from the same country as specified in parameter 'Country' for the cash register.

Payment

Improvement in asynchronous payment capture (RTP-28845)

We've improved our logic around handling asynchronous payment capture, so that we can make sure when the different stages of the order import maintains the correct store number on receipts in the given order.

  • No labels