Document status: RELEASED
Date:
Prerequisites are located in the menu on the left.
Highlights | |
|---|---|
Release version: 3.0.0.12001  |
|
Payment by Vipps in EG POS and self-service
(Work ID: 184178)
Vipps can be used as payment both in cashier mode and in self-service in EG POS. To pay by Vipps, the customers have to supply their phone number.
Vipps payment in cashier mode:
Dialog for cashier to enter phone number:
If a customer or member has been added to the receipt, the phone number will be suggested to make the payment process as fast as possible.
When the phone number has been supplied, the cash register will wait until the customer approves the amount in the Vipps App on their mobile phone.
After customer approval, the payment summary is shown:
Any part payments (gift card, credit note etc) should be performed before paying the remaining subtotal by Vipps.
Vipps payment in self-service:
Select Vipps as payment and enter phone number:
If a member has been added to the receipt, the member’s phone number will be suggested.
Approve payment in the Vipps App:
To start using Vipps as payment, EG PaymentService must be set up and configured by the PaymentService DevOps team.
Reporting database must be updated manually with new card types in table DimPaymentCard if version is lower than 63.
POS Configuration |
|---|
ButtonConfig Add a new button to pay by Vipps using function "Pay with mobilepayment" with argument Vipps. ShopAndGoButtonConfig Add a new button to pay by Vipps using function "Pay with mobilepayment" with argument Vipps. CloudAccessServiceUrl Address to CloudAccessService in POS Services. Default address should normally be used. PaymentServiceMerchantId Correct Merchant ID to be used will be supplied by PaymentService DevOps team. PaymentServicePollingIntervalInMilliSeconds (default 1 second) Use default value of 1000 ms. PaymentServiceTimeoutInSeconds (default 11 seconds) Timeout waiting for reply from PaymentService. PaymentServiceUrl Address that EG POS will use to contact PaymentService in the cloud. Make sure to use the correct address for your environment. https://paymentservice.lindbakcloud.com should be used for production environments, including EG Demo. https://paymentservice.lindbaktest.com should be used for test environments. PayTerminalVerboseLogging (default False) Can be enabled to extend logging to research problems. VippsCardIssuerId (default 210) Card issuer used for Vipps payments. Must be changed to 33 in Production environment. The matching issuer ID must be added in Reporting database. |
POS Services host configuration file |
|---|
New service CloudAccessService endpoint must be added from the template file: EnabledServices CloudAccessService must be added to list of active services. LRSOnPremiseCloudAccessCertificate must be added on the same machine as POS Services is running. |
Configuration of system parameter 237 in Chain Classic |
System parameter 237 – Bank card used in Key values settlements report alt. - Enter the bank card to be specified in the Key values settlements report – alternative. Value = Card type code (defined in system alternatives 80). Value = 33 to show Vipps in the report. Value = 90 to show Swish in the report.  |
Configuration of system alternatives 80 in Chain Classic | |
System alternatives 80 – Card types. Overview of valid payment cards. Code 33, Row text: Vipps, check Logical. Code 90, Row text: Swish, check Logical |  |
Payment by Swish in EG POS and self-service
(Work ID: 183248)
Swish can be used as payment both in cashier mode and in self-service in EG POS. To pay by Swish, the customer can scan a QR code in their Swish App or they can supply their phone number.
Swish payment in cashier mode:
Dialog for cashier to enter phone number or to scan QR code:
If a customer or member has been added to the receipt, the phone number will be suggested to make the payment process as fast as possible.
When the phone number has been supplied, the cash register will wait until the customer approves the amount in the Swish App on their mobile phone.
After customer approval, the payment summary is shown:
Any part payments (gift card, credit note etc) should be performed before paying the remaining subtotal by Swish.
Swish payment in self-service
Select Swish as payment, then scan the QR code in the Swish App or click the button to enter phone number instead:
Approve the payment in the Swish App to finish the transaction.
Dialog for sale of bags in POS
(Work ID: 184152)
An automatic dialog to remind the cashier to sell specific items (like bags) can be shown when going from sales view to payment view. The dialog will only be shown the first time the cashier goes from sales view to payment view and only when going to payment (not when creating or editing orders).
Select quantity for each item and press OK to add them to the sale:
A touch screen is required to use this functionality as the cashier has to click on the desired quantity.
Faster use of gift receipt stickers during returns
(Work ID: 184173)
When the cashier scans a gift receipt sticker, the correct item will automatically be added to the active receipt as a return. This simplifies and speeds up the process for the cashier. Previously, online return was started and the cashier had to select the correct item to return.
Access to cloud services from EG POS
(Work ID: 165870)
A pattern to communicate from EG POS directly with cloud services has been implemented. POS will fetch an access token from POS Services on-prem and use this when communicating with cloud services. This will be used to communicate with PaymentService and is needed for Swish and Vipps integrations.
Disable print of bundle closure report for pay terminals
(Work ID: 179808:)
We have made it possible by configuration to disable the print of bundle closure report (Z-report) for pay terminals. This report is triggered manually or automatically from the POS.
Creating new customers in POS
(Work ID: 162163)
The dynamic version of the dialog to create new customers should be used in POS. This dialog has several visual improvements compared to the older dialog.
Configurable choices for social control based on price
(Work ID: 184155)
The dialog to perform social control can be configured to contain different options when triggering manually and automatically. The automatic dialog for social control can be configured to trigger based on subtotal amount and for selected item groups.
Improvements POS
Module | Description |
|---|---|
Customer view | Member registration from customer view v2 (Work ID: 185116) The numeric buttons in the member registration form on the new version of the customer view have been fixed. Previously the borders were missing on the buttons. |
Financial counters | GrandTotal and GrandTotalNegative (Work ID: 173877) We have made improvements regarding financial counter 'GrandTotal', which is a unique counter for each POS. The value is now correctly accumulated with the summary of all sold items in a receipt, regardless of any other items being returned in the same receipt. (There is a separate counter 'GrandTotalNegative' for returned items). These numbers are used by the X/Z reports in Chain Web. |
Gift card | Dialog header when paying with empty gift card (Work ID: 185960) The dialog shown when trying to pay with an empty gift card has been improved. |
Klarna | Klarna v3 refund (Work ID: 187012) Returns with KlarnaCheckout tender type were fixed in POS by making them always use Klarna Instore. |
Order | Adding orders to item transactions (Work ID: 182888) It is not possible to add an order to item transaction receipts. Trying to do this will result in an error message. Unlock AX orders in self-service (Work ID: 186464) Orders are unlocked versus AX after order cancellation or timeout in self-service. |
Receipt | Difference between item lines and subtotal after online return (Work ID: 184056) Online return combined with subtotal discount and sale of new items could result in a difference between item lines and subtotal. This has been corrected. |
Improvement POS Server
Module | Description |
|---|---|
JournalService | Klarna MerchantId and InvoiceId in ARTS POSLog XML (Work ID: 187012) MerchantId and InvoiceId are properly passed to ARTS POSLog Xml for Klarna V3 orders. Missing PDF for digital receipt (Work ID: 187825) We've fixed an issue where subscribertype POSLogBatch (used by ReceiptService) no longer uploaded attachments (pdf) to BlobStorage. |
POS API | Method for MerchantId for payment providers (Work ID: 186501) A new method has been implemented in Itemsale\Payment, called GetCloudPaymentServiceConfiguration. This method returns the configurable MerchantId from parameter PaymentServiceMerchantId. This will be used when paying in InStore App through EG PaymentService in the cloud. AD username login in POS API (Work ID: 122568) We've added support in POS API to use the registered AD_username (found in dbo.user table) when calling NewCart requests. Sending the email registered on a user as 'operator' in NewCart requests, will now trigger a lookup in dbo.user to find the cashier linked to that email. This will be used by Mobile POS. Support for capturing 0 amount on orders in Klarna v3 (Work ID: 186960) It is now possible to capture payment when there is nothing to pay by Klarna. (Typically because the order was fully paid by gift card) |
POS Import | Improved logging - "CompletedWithNoEffect" status (Work ID: 177920) The use of “CompletedWithNoEffect” status was implemented for scheduled jobs in POS Import. This makes it easier to find relevant log entries. Wrong VAT Flags for customers (Work ID: 182882) VATExempt and ShowPricesExclusiveVAT flags were fixed and are properly set when importing data to POS Master. |
POS Service | Timezone in empty response from price synchronization method (Work ID: 185276) The procedure GetItemsWithChangedPricesInArtsXml in priceService previously delivered timezone in the response when no results were found. This has been removed since it could cause problems at receiver. Synchronization of new items in existing mixmatches (Work ID: 186284) We've corrected an issue where adding item to an already ongoing mix would not show up as a result when using GetPriceRules method in PriceInfoService. Extra decimal numbers for discounts on receipts in Receipt Journal (Work ID: 183659) When editing an order multiple times, discounts previously added was shown with an extra 0 behind the discount percent every time the order was edited. (Example: 24,50 % -> 24,500 %). This has been fixed. |