Payments are the one part of a POS that has to work every single time, so it's worth being specific about how NUA actually handles them rather than waving at "integrated payments" as a feature bullet.
Splitting a bill without starting over
Split-by-seat, split evenly, split by item, or a custom manual split: all available from the same checkout screen, on the same open order, without voiding anything or asking a guest to wait while a ticket gets rebuilt.
Running a tab
Tabs stay open against a table, a name, or a card pre-authorisation, with items added throughout a session and a single close-out at the end: the same pattern bars and pubs already run, just without a separate tab-tracking system bolted on.
Contactless, chip, and card-on-file
Contactless and chip payments run through PCI-compliant payment processors integrated at the terminal level, NUA's own systems never touch or store raw card numbers, which keeps the compliance burden with specialists built for exactly that.
What happens when the internet drops
Because NUA runs offline-first at the terminal, a dropped connection doesn't stop service. Orders keep taking, payments keep authorising against cached rules where the processor supports it, and everything syncs the moment connectivity returns: a sync delay, not a lost sale.
Every transaction (split, tab close-out, refund) is logged with a timestamp and the staff member who actioned it, which matters as much for dispute resolution as it does for daily reconciliation.
Why this matters more than it sounds
Payment friction is one of the few things guests actively notice. A checkout that handles a complicated split or a running tab without a manager override request is invisible when it works, and it's exactly the kind of detail that separates a POS built for hospitality from one adapted from retail.