Paying
sequenceDiagram actor Guest participant QR as 4u Check participant PSP as Payment provider participant POS as Restaurant POS Guest->>QR: Pay my share QR->>QR: Fix the amount and hold the share for 2 minutes QR->>PSP: Start the payment PSP-->>Guest: Card, Apple Pay or Google Pay PSP-->>QR: Payment confirmed (signed) QR->>POS: Record the payment on the check QR-->>Guest: Paid, here is your receipt QR-->>QR: The bill updates for everyone at the table
- Fix the amount
4u Check fixes the guest’s share, tip included, for 2 minutes and holds it so nobody else can pay the same money.
- Pay
The guest pays on the payment provider’s page or wallet sheet. 4u Check never sees the card number.
- Confirm
Only a signed message from the payment provider counts as proof of payment. A redirect back to 4u Check or a wallet animation does not.
- Record on the POS
The payment is written to the POS check so the till knows the bill is paid. See payment states.
What the guest sees
Section titled “What the guest sees”| Situation | Guest sees |
|---|---|
| Paid | “Paid” and the receipt |
| Declined or cancelled | “Payment failed”, and they can try again |
| No answer from the payment provider yet | “Checking your payment, do not pay again.” They are never asked to pay twice while a payment is unclear |
| Paid, but the POS has not recorded it yet | “Paid”. The guest is done; staff get an alert to finish the POS side |
| The provider confirms a charge after the guest saw “failed” | The charge is refunded automatically |
Pressing Pay twice, going back, or reloading the page never creates a second charge.

