...
Svea can be used as payment in cashier mode in EG POS. To pay by Svea cashier needs to register customer's mobile phone number and social security number.
Svea payment in cashier mode:
When items are added and cashier chooses Svea as a tender, a dialogue is shown to cashier, telling him to ask customer to scan Instabank QR code:
RTP-25485)
During payment a message is shown telling an SMS is sent to customer's mobile phone:
...
| Expand |
|---|
|
| POS Configuration |
|---|
New parameter: SveaCardIssuerId (default 213)
Card issuer used for Svea payments. The matching issuer ID must be added in Reporting database. Existing parameters: ButtonConfig
Add a new button to pay by Svea using function "Pay with mobilepayment" with argument 'Svea'. 
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.
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.
https://paymentservice.lindbaktest.com should be used for test environments.
PayTerminalVerboseLogging (default false)
Should be activated, to extend logging to research any problems. |
|
Integration with WebDok for Boarding Pass validation
(RTP-25485)
A Boarding Pass can be scanned in POS to add flight data to the receipt. (Flight data must be synchronized from Avinor and the unique flight id in the boarding pass must match the unique flight id of an active flight)
The header in POS will show flight information and the number of passengers and the number of available quotas for alcohol and tobacco.
Image Added
| Expand |
|---|
|
| POS Configuration |
|---|
BoardingPassRegEx Used to identify that boarding pass was scanned.  Image Added
Fake data for test: In test, the parameter can be configured to recognize all barcodes starting with BP. Then, the following format can be used to use fake data for testing purposes: BP-uid-numpax-alc-tob
uid = unique flight id
numpax = number of passengers/persons
alc = number of available alcohol quotas
tob = number of available tobacco quotas Example: BP-12004693-1-1-1 The unique flight id must match a synchronized flight in POS database fetched from Avinor. PosServicesWebdokServiceUri URL to Webdok service in POS Services.  Image Added
|
| POS Services host configuration |
|---|
New endpoint ... must be copied from template file to the active configuration file: New service ... must be added to EnabledServices parameter. |
|
Sealing items and printing STEB receipt in self checkout POS
...
