Copy page

Nudle

Nudle is a separate Kwik Nkap product: an offline-first operating system for Cameroonian restaurants, bars, and counters. Diners scan a table QR code, browse the menu, order for themselves, split the bill across the table, and pay by Mobile Money or cash. Nudle is its own application with its own surfaces and data model. It reuses Kwik Nkap's shared Mobile Money collection engine to move money, but it is not part of the public payments API.

What Nudle is

Nudle turns a restaurant or bar into a self-service ordering venue without the merchant writing any code. A merchant who already runs a KYC-verified Kwik Nkap business creates a Nudle workspace, defines their venues, tables, and menu, and prints a QR code for each table. From there:

• A diner scans the table QR, joins (or opens) that table's shared session, and orders items directly from their phone.
• The bill is shared across everyone seated at the table. Splitting the bill means multiple participants each make partial payments against one running balance.
• Mobile Money collections (MTN MoMo / Orange Money) are confirmed asynchronously; staff can also record cash or manual payments.
• When the outstanding balance reaches zero, the session settles and staff close it out.

Nudle scales from a street kitchen taking quick tickets at a counter all the way up to full table service in a sit-down restaurant. It is offline-first: the experience is built to keep working through patchy connectivity, with Mobile Money outcomes reconciled when the network confirms them.

Money in Nudle moves in a single direction: collection (pay-in) only. There is no payout or disbursement logic inside Nudle. Settled funds land against the workspace's linked Kwik Nkap merchant business through the shared payment engine. Currency is XAF throughout.

The five surfaces

Nudle is delivered through five distinct surfaces over one shared backend.

Surface	Who uses it	What it does
Diner app	Customers at a table	Scan the table QR, view the menu, self-order, see the shared bill, split, and pay by Mobile Money
Staff app	Waiters / floor staff	See pending scans, greet and verify a session, add items, hand sessions over between waiters, record cash
POS mobile	Counter and roaming staff	Quick-ticket ordering and payment capture on a phone
POS desktop	Front-of-house / cashier station	Full point-of-sale on a larger screen for higher-volume table service
Owner dashboard	The merchant owner	Onboard the workspace, manage units, tables, the menu catalog, inventory, and staff invites

Core concepts

Nudle's data model is a small hierarchy. Understanding it makes the rest of the product obvious.

Concept	What it is
Workspace	The top-level Nudle account for a merchant, linked one-to-one to a KYC-verified Kwik Nkap business
Unit	A venue within a workspace (a specific restaurant, bar, or counter location)
Table	A physical table inside a unit; each table has its own QR code
Session	The shared order and running bill for a table, opened when the first diner joins and closed at settle-out
Participant	One diner within a session, identified by a device fingerprint, optionally with a display name
Catalog / menu	Categories and items, each item carrying a basePriceXaf; the menu a diner sees when they scan

A session carries the line items everyone has ordered and an expectedTotalXaf (the sum of those line items). Each participant's orders are tagged with their participantId, so the table can see who ordered what while still settling one shared balance.

The QR self-order flow

This is the end-to-end path a diner takes, from scanning the table to a closed-out session.

1. Scan. The diner scans the table QR and opens the public menu for that workspace and unit.
2. Join the session. The diner joins the table's open session, or one is created if the table is fresh. Nudle mints a signed public-session token so the anonymous diner can act within that session.
3. Order. The diner adds items to the session. Each line item is tagged with their participantId. The session accumulates line items and recomputes expectedTotalXaf.
4. Staff greet (optional). On the floor, staff see pending scans and greet or verify a session, moving it from pending to active. Staff can also add items and hand a session over between waiters.
5. Split. Any participant can pay part of the bill. Multiple partial payments from different participants settle the one shared running balance.
6. Pay. A participant pays by Mobile Money (the diner enters an amount and phone number) or staff record a cash payment.
7. Settle. Only confirmed payments count toward paidTotalXaf. When the outstanding balance (expected - paid) reaches zero or below, the session auto-settles.
8. Close. Staff close the settled session, with an optional manager PIN override.

Splitting the bill

"Split bill" in Nudle is not a fixed N-way division. It is a shared balance that any participant can pay down. Several diners can each contribute partial amounts (some by Mobile Money, some by cash recorded at the counter), in any order, against the same expectedTotalXaf. The session tracks how much has been confirmed and how much remains, and settles the moment the remainder hits zero.

Money movement

Nudle delegates all real money movement to the shared payment-service, the same collection engine that backs Kwik Nkap's public payments API. Nudle never moves money out on its own and has no disbursement path.

Mobile Money collections

When a participant pays by Mobile Money:

1. Nudle records a PENDING payment against the session.
2. It calls the shared collection engine with the workspace's businessId, the amount, the payer's phone number, and metadata tagging the payment as coming from Nudle (the session and payment IDs travel in that metadata).
3. The payer receives an MTN MoMo or Orange Money prompt on their phone and approves the debit with their PIN.
4. The provider settles the collection and calls back into Nudle. The payment flips from PENDING to CONFIRMED (or FAILED), the session balance is recomputed, and a realtime event fires so the surfaces update.
5. Clients can poll the payment to observe the outcome.

Only CONFIRMED payments count toward the paid total. A FAILED collection leaves the session balance unchanged, and the diner can try again.

Cash and manual payments

Staff can record a cash or manual payment directly against the session. These are captured by staff on the floor or at the counter and count against the same shared balance as Mobile Money payments.

Settlement

Funds collected through Nudle land against the workspace's linked Kwik Nkap merchant business via the shared payment engine, in XAF. From there, the merchant's balance and any payout follow Kwik Nkap's standard platform flows, the same as for every other collection across the platform. A session is "settled" when its outstanding balance reaches zero; settlement is about the table's bill being fully paid, not about money leaving the platform.

Onboarding and setup

Nudle is gated. To create a Nudle workspace, a merchant must be the owner of an existing Kwik Nkap business with verified personal and business KYC. Once that gate is cleared:

1. The owner creates a Nudle workspace linked to their businessId.
2. From the owner dashboard, they create units, then tables (each generating a QR code), then a menu catalog of categories and items priced in basePriceXaf, plus inventory.
3. They invite staff by phone number. Staff then sign in to the staff app and POS surfaces.

Workspace creation depends on Kwik Nkap's business and KYC systems; if a merchant is not yet KYC-verified, see Identity Verification (KYC) for how activation works.

Where Nudle sits versus the public payments API

Nudle is built on its own gateway and service, authenticated by Kwik Nkap user identities with workspace-member permission checks for staff and dashboard surfaces, and a separate signed public-session token for the anonymous diner QR flow. None of those routes are part of the documented public developer API, and they are not authenticated with an X-API-Key.

The one piece Nudle shares with developers is indirect: the generic Mobile Money collection. Nudle calls the same internal collection engine that the public payments API exposes as POST /v1/payments. So while a developer can build their own Mobile Money collection flow against the public API, they cannot reach Nudle's sessions, tables, menus, or split-bill logic through it.