Skip to content

How 4u Check works

flowchart LR
  subgraph People
    G["Guest<br/>phone browser"]
    S["Restaurant staff<br/>tablet or laptop"]
    O["4u Check operations"]
  end

  subgraph Platform["4u Check"]
    GA["Guest app"]
    RA["Restaurant dashboard"]
    AA["Admin console"]
    CORE["Core engine<br/>orders, bills, pricing,<br/>payments, alerts"]
    W["Background worker<br/>retries, POS sync,<br/>fees, payouts"]
    DB[("Database<br/>each restaurant<br/>walled off")]
  end

  subgraph Outside["Partner systems"]
    POS["Restaurant POS"]
    PSP["Payment provider"]
    BANK["Restaurant bank account"]
  end

  G --> GA
  S --> RA
  O --> AA
  GA --> CORE
  RA --> CORE
  AA --> CORE
  CORE --> DB
  W --> DB
  W <-->|"orders, bill, payment record"| POS
  W <-->|"card payment status"| PSP
  PSP -->|"settlement"| BANK

Guests, restaurant staff and the 4u Check operations team each get their own app. All three talk to the same core engine, and only the engine and its background worker talk to the database, the POS and the payment provider. A browser never talks to a partner directly.

Almost every restaurant 4u Check serves already has a POS, so 4u Check works beside it, never instead of it.

  • Orders placed by QR are sent to the POS, which sends them to the kitchen.
  • The bill a guest sees is checked against the POS check line by line before anyone can pay. If they differ, payment is held and staff see why. See bill check.
  • After a guest pays, the payment is recorded on the POS check so the till knows the bill is paid.

The guest pays the payment provider. The provider settles the money to the restaurant. 4u Check never holds a guest’s money and never sets settlement timing; in the UAE those are licensed activities that belong to the payment provider.

4u Check tracks three things separately for every payment, so nothing is lost between them:

  1. Card charged: the payment provider confirmed it.
  2. Recorded in the POS: the POS knows the bill is paid.
  3. Money settled: the restaurant received the funds.

Every change a guest or staff member makes carries a unique key. Pressing Pay twice, reloading the page or a network retry replays the first result instead of charging twice. The background worker retries POS and payment work until it gets a definite answer, and raises a staff alert when it cannot.

Every restaurant’s data is separated at the database level, not only in the app. A request for one restaurant cannot read or change another restaurant’s tables, bills, payments or staff, even through a bug in the app.

The POS and the payment provider each sit behind one connection point with a fixed contract. The simulated POS and payment provider pass the same contract tests a real partner must pass, so adding a real partner is a connection job, not a redesign. See integrations.