The problem: splitting a bill is slow
When a group splits the check, the terminal is worked one person at a time. For every diner the waiter repeats the same loop: start the transaction, capture the card and PIN, then wait for the network to authorize before moving on.
A table of ten can take 5–10 minutes. The waiter is stuck at one table, other tables wait, and every extra step is another chance for an error.
Same table, a fraction of the time
The idea collapses that sequential loop into one capture burst, then authorizes everyone in parallel.
How it works
Set up once
The waiter enters the total, the number of parts (equal or custom) and the tip style, one time.
Tap all around
The terminal sits on the table in “reading mode”. Each diner taps, dips or scans in quick succession, with no waiting between them.
Hold & batch
Each credential is captured and its authorization request is stored temporarily instead of being sent one by one.
Authorize in parallel
Requests are sent together and a summary shows what cleared, isolating only the cards that declined.
Why it's novel
It decouples capturing the card from authorizing it. Once those two steps no longer have to happen back-to-back, many payers can tap first and the network round-trips can run in parallel, turning a serial queue into a batch. Same terminals, same kernels, same rails: only the orchestration changes.
Built from existing building blocks
No new hardware. The split-payment logic sits on top of the components a modern POS terminal already has.