Currently, there appears to be a critical flow issue with the handling of failure payments for POS stations that use dedicated EMV terminals like the Pax A35.

When a payment fails to make it to the POS for whatever reason the POS overlays a red ribbon over where the payment should be and a text box pops up asking users to swipe the payment. At this point the transaction stays in the Batch on the Pax device but is not visible on the copy of the batch on the POS. If the user swipes the red ribbon the payment is checked for on the Pax device and is taken care of. However if the user selects Delete the payment is deleted only on the POS side, but is left on the Pax Batch. This gives the appearance to the user that everything is taken care of and the user will go ahead and attempt to charge the customer again. However at the end of day, when the user submits the batch there are now 2 charges being submitted leading to double charging the customer which ultimately becomes chargebacks for the merchant.

Currently everything hinges on the text box which pops up when the error comes up. There are many problems with using this as the solution.

1. The only interaction users would typically have with the payment is deleting it to refund the customer. The pop up only appears once so if they cleared that message too fast, or just didn’t understand what it meant they will likely try the delete method to remove the failure payment.
2. The correct option(Retrieve) is hidden and dependent on an action, whereas the option which can lead to double charges(Delete) is plainly visible and is allowed to be done before the correct action.
   1. Should consider making sure it is not selectable at all. I don’t know what the purpose would be for allowing that to be visible when it is a double charge risk.
3. Users get fairly numb to the textboxes. I see employees just exit out of that text box as soon as it pops up. They assume it’s the same knowledge they’ve done hundreds of times to remove a payment. This is made worse by the high volume of errors that the Pax A35 produces(particularly with Tap to Pay).

Overall when it comes to the flow of the Failure payments I would like to see Linga make it easier to perform the right action and harder to perform the wrong action. I think this can be handled easily within the design of the app rather than relying on the text box.

Add Enroll date and last visit date in Customer export file when exporting customer data from Back office and also when uploading the customer data to back office. 

This columns can be marked as optional field when uploading the customer data to back office.

Currently if pre auth is enabled you can not tip on CDS with the preauth transaction.

Customer must sign paper and tip added to batch screen manually

The "notes" are a nice touch; however, it would make more sense for it the show on the schedule instead of the employee having to click on the shift and search for it.

Can some Labor reporting be added to the Close Day/Sales Recap report for management that might not have access to employee reporting in the back office. 

Labor Hours worked that Day
Labor Cost % of Days Sales

Hey there,

One feature that we need is a way to change the default tip to 10%. For example, when the customer comes to pay for their order and the tip screen pops up, it shows the total amount of the order plus the tip, which is currently set to 0. We would like to set it to default to 10%, and the customer can choose whether to leave that amount or not. We need this because our tip amount has decreased by more than 60% since we changed the POS system. In our previous system, we could set 10% as the default for all our customers, and most of them would tip accordingly. However, now that we don't have this feature, we barely receive any tips.

If you could please take a look at this matter since we really need it, and it's a basic feature that most systems have, we would be really glad!

Need to have the app in fullscreen mode and hide the android  navigation buttons , app should also require manager pin to quit or close from the screen. this is a issue with servers inadvertently closing the app or wifi. 

Got a lot of requests for 7Shifts integration

It would be nice to have a pop up after clicking void under the check options to confirm that the client wants to void the entire check.  I know they will learn the hard way after accidentally deleting a few large checks but it would be nice to have a confirmation.

In restaurants and bars, employees will often work 2 shifts in the same day (working a double). If the employee cashiers out for the morning shift and continues working or if the employee cashiers out, clocks out, then clocks in under a different role, it should separate the reports so they can see what they owe the house for each shift. 

Ex. If an employee works as a bartender and uses the drawer for lunch. They should be able to cashier out, clock out, then clock in as a server for dinner. The server should have a way to separate the reports so they can see what they owe the house for the dinner shift. This should also occur if an employee works server for morning and lunch, cashiers out and comes back later to work the dinner shift. Right now, they have to complete math by subtracting the morning shift from the night shift and that could lead to errors.