Partner has addressed how complex and back and forth the process is between a Cashier and Customer on a POS & CDS set up. Partner would like the process to be smoother and the cashier shouldn't have to walk the customer through the checkout on the CDS per his recent experiences. Occurs the same on iOS and Android.

Partner suggests that once the card button has been hit on the merchant side, the customer should be able to present their payment method on the device, then the tip screen should appear, then a submit or continue button, lastly the receipt screen. This would make the checkout process much smoother and less confusing.

The App sign out button,being on the top right of the log in

Screen is causing inadvertent log outs of the app. This button should be moved to the settings page and only the same pin that logs in can log it out. 

Can we make a reverse of the hide. I have a customer that wants a more dumbed down version of their Modifiers for there Kiosk and Online ordering. So I want ot make new Modifier groups to be only seen from the Kiosk and Online but not show up for the normal employees.

We need to be able to disable the sign out button on the FOH,

Servers keep signing out and manager does not know how to sign in

Gratuity is being calculate differently in UK and we need this changed ( or given possibility to change it via Back Office ) so can make sure it calculates Gratuity on the totals, tax included.

Allow more control of the time the Linga POS software waits for a response back from the PAX

This is useful for clients that have slower internet connections or unstable connections. or even a S300

This will help in situations where the payment shows as failed in the POS but did process in the Terminal.  

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.

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

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. 

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.