Pay off the check? But of course! With our deep focus on creating the best pay at table solution available for restaurants, staff, and guests, we go the extra mile on our tech, all the time. We can now detect if someone is likely the last payer splitting the check via QR code and can guide them towards increasing their payment in the event they may not be paying enough. With Up 'n go, we have your back, restaurants! We make paying restaurant checks secure and easy for everyone involved.
What does it mean to be the best pay at the table solution? Some restaurants believe that "good enough" is "good enough." Lucky for them, there are many Up 'n go copycats. Many copycat QR code pay at table solutions lack what may seem easy but is a very technically complicated feature: split the check. Split the check for QR code payments gets complicated because you take what is normally a serial process and make it parallel. What do I mean by that? Here's what I mean: When a server splits a check, or when a tablet or handheld is used to split the check, you take payments serially, meaning one payment after the other. In this model, which is the old model, you are safe. The balance due is always adjusted before the next payment is tendered, so you always know exactly how much is due for the next person to pay. When you put splitting the check in the hands of multiple guests and the server at the same time, suddenly the paradigm restaurants have had for splitting the check for decades is turned on its head! Now, you can have any combination of the server or however many guests at the table all trying to make partial payments at the same time! These payments are being made in parallel. The challenge here is that you are throwing multiple partial payments at the POS at the same time and the POS doesn't have a chance to recalculate balance due before each payment. You could have an issue where if you add up all the inbound partial payments, the check would get overpaid. What does the typical POS do with an overpayment? Typically, it rejects it, which actually means money lost. (Don't worry, we fixed that problem a long time ago.) But what happens if guests are not doing math right and the sum of their partial payments won't add up to the whole amount due? Well then you could end up with a check that is not fully paid. Enter our newest feature: Underpayment prevention! Using a series of algorithms we've created, we can detect when a partial payment is most likely to be the last payment, but also that the guest is not trying to pay enough! When we detect such a situation, we now prompt the "last" guest to pay more. When you select a pay at the table provider that does nothing but pay at the table, like Up 'n go, you get a company that goes deep to solve every problem, and not one that does it by simply stripping features. This feature is now live on Up 'n go!
