As currently works on iOS, in the event an auto gratuity is added to a check, the Tip line description on an authorization slip is changed from Tip to Additional Tip for Android

Our merchants frequently experience auto batch settlement when there are transactions without proper tip adjustment. This mostly happens during Internet outages. The issue is if the Internet service resumes and auto batch is turned on all transactions will batch including those still needing tip adjustment. This creates a lot of work for the merchant, the Linga support team, and the Hybrid payments team Or processor. If there was somehow an option to omit non adjusted transactions from the batch, this would be and amazing feature.

many times a customer will make a partial payment with a gift card. After making the payment the POS shows the remaining balance due, but when printing the chit for the customer to show 'balance due' the chit does not reflect the balance due. Please show the partial gift card payment on the chit.

It would be nice to have a feature where you can type in the payment through the iPad instead of the pax device. This way we can charge two cards at the same time. 

we are having issues with our EMV Device where the device will beep before it is actually ready for the card to be removed. Customers mistake the beeping for meaning that it is ready to be removed, and after they remove their card the EMV device says an error message. Even though the error message plays their card receives a charge, resulting in a double charge after they try it again.
We need to fix the timing of the beeps to play 1-2sec after the card is finished processing(after the "Remove the card" screen appears).

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

We have had a situation where a Cashier would quickly tap a large % on the Cashier side when the Tip screen appears and then quickly tapping the CONTINUE button so the total is sent to the PAX device. The cardholder does not see the added tip and simple taps/inserts their card.  The ticket is paid for with the unknown tip and customers are advising later that day and next day they did not tip that amount. 

When someone pre-auths a card and has "prompt tip before credit card screen" turned on. It will not allow them to prompt a tip when closing out the tab. I believe this is due to the credit card screen being bypassed due to the pre-auth. 

If a Credit Card Payment is processed on the incorrect table.  Having the ability to select the Credit Card Payment and select the option to Move Payment to another check 

This should be a permission under Job Codes.