Cleforyx

Zap Biz is a multi-tenant WhatsApp AI ordering and payments platform built for Ghanaian and African businesses — restaurants, retailers, and service providers who take orders and get paid directly inside WhatsApp, without a separate app or website. Businesses connect their number through Meta's WhatsApp Cloud API. An AI assistant powered by Gemini handles the conversation — answering questions, building an order from the business's product catalog, and calculating totals. Once an order is confirmed, Zap Biz generates a Moolre-hosted payment link and drops it directly into the WhatsApp chat. Payments (Moolre is the backbone): Collections — customers pay via Moolre's hosted checkout; a webhook confirms payment and Zap Biz automatically pushes a branded receipt image to the customer, no manual confirmation step. Disbursements — business owners withdraw earnings to a configured payout destination, with OTP-verified approval. Platform wallet fallback — if a tenant's own checkout attempt fails, the platform's own Moolre wallet can still collect the payment so the customer isn't blocked, reconciled to the tenant afterward. Moolre SMS — OTP delivery for signup, login 2FA, and payout approval. Wallet auto-deduction for subscription renewal, order refunds (KYC-verified tenants only). Rich media handling — the bot doesn't just read text: Audio — incoming voice notes are transcribed (Whisper) so the AI can act on them, and the bot can reply back with a generated voice note (Kokoro TTS, OGG/Opus) for a natural WhatsApp voice-note experience. Images & stickers — processed and understood by the AI (e.g. a customer sending a photo of a product or receipt). Documents — PDF and DOCX uploads are parsed and their text extracted so the bot can act on document content sent by a customer. All of this is capability-gated per tenant/tier, so a business can enable only what fits their use case. Product catalog — businesses manage their catalog from the dashboard, and it feeds directly into what the bot can sell: the AI references live stock, pricing, and descriptions when building an order, so the catalog a business edits on the dashboard is exactly what the bot quotes to customers on WhatsApp. Enterprise integrations — on the Enterprise tier, a business's own systems can connect to Zap Biz two ways: Inbound sync API (/api/v1/products/sync, /orders, /customers) — lets an enterprise's existing database, POS, or CRM push/pull product catalogs (batched upsert by external ID), orders, and customer data, so Zap Biz's catalog and order records stay in sync with whatever system the business already runs on. Outbound webhooks, configured entirely from the dashboard — HMAC-signed, queued with exponential-backoff retries, subscribable per event type (payments, orders, escalations, and more), with a delivery log and manual retry from the UI, so an enterprise's CRM/ERP gets pushed real-time events instead of having to poll. API keys for the inbound surface are also managed from the dashboard, since the whole /api/v1/* surface is server-to-server, separate from the merchant-facing dashboard API. 24-hour conversation windows — Zap Biz tracks WhatsApp's customer-initiated 24-hour messaging window per customer, per tenant, exactly the way Meta bills it: the first message from a customer opens a new window that stays active for 24 hours, and only that first message counts toward the tenant's monthly conversation quota — every other message exchanged with that same customer inside the same 24-hour window is free. Once the window expires, the next inbound message from that customer opens a fresh window and increments the counter again. This keeps a business's usage counter aligned with Meta's own conversation-based billing model rather than counting every individual message, and it also drives trial-vs-paid quota enforcement (trial tenants draw down a fixed conversation allowance, paid tenants draw down their tier's monthly limit) without ever double-counting a back-and-forth exchange that's still inside the same window. Onboarding & platform — full onboarding flow (business registration, tier selection, KYC via Smile ID, WhatsApp connection, bot persona configuration, payout destination setup), JWT auth with 2FA, and a tiered plan structure (Starter/Business/Enterprise) in GHS with conversation-volume-based quotas — Enterprise pricing and limits are negotiated per contract rather than fixed, specifically because Enterprise is built around integrations and volumes that vary business to business. The backend is Fastify + TypeScript on PostgreSQL/Prisma with Redis + BullMQ handling webhook retries, payout polling, and message dispatch asynchronously; the frontend is React/TypeScript/Vite with Tailwind. Legal pages are grounded in Ghana's Data Protection Act 2012 and reference the Moolre/WhatsApp data flows specifically. In short: Zap Biz turns a business's WhatsApp number into a full ordering-and-payments storefront — voice, image, sticker, and document aware — with Moolre powering checkout, payouts, and OTP, and an Enterprise integration layer that lets it plug into a business's existing database, CRM, or backend systems.