We have a customer using the Apple terminal who requires the payment method to be printed on the receipt. Could you please prioritize making this option available at your earliest convenience?

When a customer presents a Visa card and the available balance is less than the purchase total, the card issuer may return a unique response code along with a partial amount approved. Currently on the POS, Linga lacks a clear notification for the merchant.

We would like to see a prompt or notification on the POS screen when a partial authorization is received. The notification should:

Clearly alert the merchant that only a partial amount was approved.

Display the approved amount and remaining balance.

Offer the merchant the option to either accept the partial payment and request an additional form of payment (split-tender), or decline the transaction altogether, based on the return code.

Currently, Linga POS allows merchants to configure a Debit payment type; however, selecting this payment type does not result in a true debit transaction being initiated on the payment device. Instead, selecting Debit simply adjusts surcharge calculations but still sends the transaction to the device and processor as a standard credit transaction.

The key issue is that Linga POS does not currently send any instruction or indicator to the integrated payment device to initiate debit transaction logic. As a result, while the cardholder may be prompted to enter a PIN, the transaction is still processed as credit at the device and processor level.

Business Need:

For solutions like ours, the ability for the POS to correctly initiate debit vs credit at the device level is essential. Most payment devices expect a specific transaction type to be initiated to handle debit properly:

• Initiating debit triggers the device to handle routing, PIN entry, network logic, and correct processing with the processor.

• Initiating credit bypasses debit networks entirely, even if a PIN is entered.

Without Linga sending the correct transaction type to the payment device, debit-capable cards are always routed as credit, resulting in:

• Incorrect interchange qualification.

• Missed cost savings for merchants who intend to process true PIN-debit.

• Inability to comply with some processor requirements or merchant agreements.

• Confusion at the merchant level when "Debit" is selected but does not function as expected.

Requested Enhancement:
We are requesting that Linga POS implement proper debit support by:

1. Allowing the POS system to distinguish between credit and debit when communicating with the integrated payment device.

2. Sending the appropriate transaction type instruction to the device when the Debit tender type is selected in Linga.

3. Ensuring that when Debit is selected:

   • The device initiates a debit transaction flow.

   • The device controls PIN entry, routing, and processing in accordance with the card brand and processor requirements.

4. Maintaining the existing surcharge logic as applicable.

Why This is Critical:

• The current behavior prevents merchants from leveraging true PIN debit.

• Payment processors and devices rely on POS software to properly identify the intended transaction type.

• Proper debit support is already expected and standard across many other POS platforms.

• Linga already handles EBT properly, which shows device-level transaction type control is possible.

Reference Ticket:
Case #206888 (Joshua Fox, Partner Support)

When network can't be found, printer not found message takes around 60 seconds or more to pop up. Due to this lag, there is no indication if the order was sent to the kitchen or not. There is also no way to retrieve order to resend. It would be helpful to receive an immediate alert that an order didn't send.

Cash payment option closing out a check the same way as credit card payment option. Removing the Submit button to close check when using cash.

On behalf of Clovis from Mr. Hookah -  Please add a role restriction to be able to hide the sales total that displays on the Batch/Tip Adjustment screen on the POS. He does not want employees to see how much the store has made.

A way to configure pre-auth so that it does not pop up when starting a tab, but still have the custom button to apply a pre-auth if desired.

Site does not want to pre-auth for every customer every time, only on specific nights when they have a band playing and don't know the customer by name.

If pre-Auth is enabled I can set a custom button, but it still pops up on every new tab.

If pre-Auth is NOT enabled you cannot set a custom button

Clients wish to have the suggested tip amount based on subtotal. Currently it's set to total. If the subtotal is a certain amount, the suggested tip decreases if a discount is applied and staff are displeased because they may receive a lesser tip.