Skip to content

Foodics

Foodics’ public API lets a partner read the menu, tables and a table’s active order, but it does not let a partner add a payment to an order that is still open. Foodics’ own pay-at-table guide, and other pay-at-table apps on Foodics, work the same way: after the guest pays by QR, the cashier closes the order with the partner’s payment method. 4u Check then reads the order back and checks it.

sequenceDiagram
  actor Guest
  participant QR as 4u Check
  participant F as Foodics
  actor Cashier

  Guest->>QR: Opens the bill
  QR->>F: Read the table's active order
  F-->>QR: Items, charges, taxes, payments
  QR-->>Guest: Bill matches, ready to pay
  Guest->>QR: Pays
  QR-->>Cashier: Table paid by QR: close it with "4u Check"
  Cashier->>F: Close the order with the "4u Check" payment method
  QR->>F: Read the order again
  alt Closed with "4u Check" for exactly the QR amount
    QR-->>QR: Recorded in the POS
  else Closed another way, or for another amount
    QR-->>Cashier: Alert: check the order
  end
  1. Create the payment method in Foodics

    In the Foodics console, add a payment method named “4u Check” of the type Foodics uses for partner payments. The cashier closes QR-paid orders with it.

  2. Connect Foodics

    A manager opens Settings, Foodics in the 4u Check dashboard and presses Connect. Foodics asks the Foodics account owner to approve 4u Check, then returns to the dashboard. 4u Check stores the Foodics access token encrypted.

  3. Choose the branch and payment method

    Pick the Foodics branch this outlet is, and the “4u Check” payment method. Only branches and payment methods Foodics lists for the business can be chosen.

  4. Link tables

    Link each 4u Check table to its Foodics table. Each Foodics table can be linked to one 4u Check table. Check reads a linked table’s open order exactly as the payment flow will, which is the quickest way to confirm the connection works.

Choosing another branch removes the table links, since they named the old branch’s tables. Disconnect revokes the token at Foodics and deletes it from 4u Check.

Foodics 4u Check
Active order on the table (status: active) The table’s check
Products, with options and quantities Bill lines
Charges such as service charge, with their taxes Spread over the lines they apply to, to the fils
Taxes VAT per line
Existing payments Already paid
Rounding amount Kept, so totals match Foodics exactly

If the lines do not add up to Foodics’ total, 4u Check refuses the order rather than show a guessed amount, and the table needs review. Foodics in the UAE requires tax-inclusive prices.

After a QR payment, 4u Check reads the order again. The check below is built; running it automatically after each payment, with the staff reminder, is the next step.

What 4u Check finds Result
Order still open Waits, and reminds staff to close it with “4u Check”
Closed, with a “4u Check” payment equal to what was paid by QR Recorded in the POS
Closed without a “4u Check” payment Alert: the order was closed another way
Closed with a “4u Check” payment of a different amount Alert: the amount differs
Closed abnormally (voided or returned) Alert
  • 90 requests per minute per business, so 4u Check reads only what a step needs.
  • Foodics webhooks are not signed, so a webhook only tells 4u Check to read the order again; it is never trusted on its own.
  • Sending QR orders into Foodics is supported by the adapter, but the first launch is pay at table.