Integrations
4u Check connects to two kinds of partner, each through one connection point with a fixed contract:
| Partner | What 4u Check needs from it | First ones |
|---|---|---|
| POS | Menu, tables, the table’s live check, sending orders, and recording payments | Foodics (sandbox, in review) |
| Payment provider | Charging cards and wallets for a restaurant, signed confirmations, refunds, payouts to the restaurant | Stripe (test mode, in review) |
The same tests for every partner
Section titled “The same tests for every partner”The simulated POS and payment provider used in the demo pass the same contract tests a real partner must pass: idempotent retries, signed confirmations, outages, timeouts with no answer, and edits at the till. A new partner is added by writing its adapter and passing those tests, without changing the guest flow, the dashboard or the money rules.
flowchart LR CORE["4u Check core"] --> PA["POS connection point"] CORE --> PP["Payment connection point"] PA --> MP["Simulated POS"] PA --> F["Foodics"] PA --> N1["Next POS"] PP --> MS["Simulated provider"] PP --> ST["Stripe"] PP --> N2["UAE provider"]
Credentials
Section titled “Credentials”Partner credentials are set up by the restaurant (for example by approving 4u Check inside Foodics) or by the operations team in the admin console. They are encrypted with a key per restaurant and never shown again after saving. Test and live credentials are kept apart: test-mode adapters refuse live keys.

