How it works
Show each guest their allocated amount and the remaining unpaid balance. A shared dish can be allocated through the supported split controls; the amount must remain consistent across devices.
Offer receipt download and email, with an optional hospitality-expense form, editable participant names and signature capture. A receipt QR must grant access to the intended receipt rather than exposing all restaurant bills.
A practical example
One guest covers the wine and another covers dinner. After the first payment, the server must prevent a conflicting split or duplicate charge.
Scope and readiness
Simulated payment is not a payment confirmation. Legal receipt content, electronic signatures, refunds and tax treatment need country-specific validation before live use.
IQ Order is in pilot development. Test payments do not move money. Live payment, tax and POS connections, mail services and physical devices need their own provider access and acceptance. Public marketing pages do not grant access to administration.
Before your first guest
- Compare the unpaid total with the sum of the shares.
- Check the same share on two devices and after reloading.
- Distinguish confirmed test payment, tip and remaining balance.
From the first menu to a connected visit
- Select your menus, service areas, ordering channels and staff roles.
- Run a complete visit using fictional guests and clearly labeled test payments.
- Validate the selected country, providers and physical devices before production.
Questions before your pilot
What should I know about Split restaurant bills on guests’ phones?
Offer an explicit “one person pays everything” choice, equal division by guest count, automatic allocation by the person ordering, or reassignment of individual dishes. Keep the original order and the chosen payment allocation distinguishable.
What is the scope and what still needs validation?
Simulated payment is not a payment confirmation. Legal receipt content, electronic signatures, refunds and tax treatment need country-specific validation before live use.
How can a table avoid paying the same share twice?
Each guest must see the remaining unpaid share before confirming. Confirmed amounts must not be allocated again. Check the flow with two phones and a repeated payment confirmation. The pilot simulates payments; a real payment provider needs separate acceptance testing.
Explore related workflows
QR ordering and shared table sessions · Restaurant reports and tip allocation · Restaurant payments, receipts and POS integrations