Documentation

MaxMenu — ordering and payment infrastructure

Public documentation for agencies, developers and investors. What we do, how we do it and why.

Last updated: June 2026 · MaxMenu Inc.

What is MaxMenu

MaxMenu is ordering and payment infrastructure for restaurants. Its purpose is concrete: embed a script on any website, control it remotely and process payments on a food catalogue — anywhere on the Internet and in multiple currencies.

The restaurant does not need to build checkout, manage translations or maintain code every time a price changes.

1

Insert the widget

2

Control everything from the dashboard

MaxMenu applies origin control: only authorised domains can display the menu on a website. Even if someone has the script, the widget does not render outside domains allowed in the dashboard.

In short Menu with integrated checkout, embeddable on any web stack, remotely updatable and built to operate at scale.

MaxMenu covers menu design, languages, allergens, tips, routing to multiple KDS stations — several screens if the venue requires it — and bank settlement. It is a vertical product for hospitality.

How it works

Three surfaces connected to the same engine:

  • Embeddable widget — a snippet inserted on the restaurant's website (WordPress, Shopify, React, static HTML…).
  • Public URL — menu accessible via QR, multilingual, with checkout available.
  • Management dashboard — design, content, translations, stations, payments and publishing.

Order & Pay is the table ordering and payment layer: the guest selects dishes, pays and the order reaches configured KDS stations — kitchen, bar, desserts or other screens depending on operations. The restaurant receives funds in its connected bank account.

Commercial model: SaaS subscription (Free, Basic, Max) + regional commission on sales. Fee details in Pricing.

Quantum Delivery

Quantum Delivery is MaxMenu's publishing system. It solves two things at once: keeping the embedded menu always up to date and serving it with minimum latency.

How it works

  1. The restaurant edits its menu in the dashboard — prices, dishes, design, languages, allergens.
  2. On publish, MaxMenu generates a menu version and distributes it to the edge network.
  3. The guest receives that version from the node closest to their location.
  4. Changes propagate to all embeds in seconds, without touching the client's website code.

Menu reads happen at the edge: the guest does not query the central database every time they open the menu. The database is involved when there is a publish, an order or a payment — moments where transactional consistency matters.

Dashboard → Publish → Menu version → Edge network → Widget / public URL

The result: a remote menu the restaurant controls from the dashboard, with stable response times under high traffic and no dependency on redeploys on the client's website.

Infrastructure

MaxMenu is built as a cloud-native platform, designed to handle traffic at scale: service peaks, multiple locations, embeds distributed across countries and continuous operation without maintenance windows.

Google Cloud Spanner Cloud Run Cloud Build Pub/Sub Cloud Scheduler Cloudflare Workers Stripe Connect Auth0 Docker

Backend services run in Docker containers, deployed on Cloud Run with automatic replicas behind load balancers — we scale containers on demand. Cloud Spanner acts as the transactional source of truth with guaranteed consistency. Cloudflare Workers serves menus at the edge through Quantum Delivery. Stripe Connect processes payments. Auth0 manages dashboard access.

Pub/Sub and Cloud Scheduler coordinate asynchronous events and scheduled tasks. For example, although it is extremely unlikely that a webhook would be lost for an already paid order, within 30 seconds at most we reconcile any affected order if something failed at any point in the flow.

The architecture separates reads and writes: the menu is consumed at the edge; orders, payments and publishes go to the transactional core. This allows each layer to scale independently.

Payments

Payments are processed through Stripe Connect. Each restaurant connects its account and receives settlements directly to its bank. MaxMenu orchestrates checkout; Stripe processes and regulates transactions.

Order & Pay is active in 38 countries, with payment methods and currencies localised by region: cards, Apple Pay, Google Pay, Bizum, iDEAL, SEPA, Klarna and others depending on jurisdiction. Digital tips go entirely to the restaurant.

Agency programme

MaxMenu includes a module for marketing agencies, hospitality consultants and developers who want to offer menu + orders + payments as their own product.

An agency prepares the restaurant in its partner dashboard — design, menu, integrations — and when the client is ready, executes an ownership transfer to the restaurant owner, similar to how Shopify transfers stores.

The programme is designed so the agency transfers ownership and does not remain the account holder: otherwise it would not earn transaction commissions. The transfer is part of the revenue share model — not an optional step.

  • White-label: the widget integrates on the client's website without visible MaxMenu branding.
  • Plug and play: ready infrastructure; the agency focuses on the client and design.
  • Revenue share on subscription and transactions — terms in Agency.

Coverage

MaxMenu operates in any market. Active payments in 38 countries with commissions and fees localised by currency.

Eurozone · United Kingdom · Switzerland · United States · Canada · Australia · New Zealand · Japan · Singapore · Hong Kong · Malaysia · Poland · Sweden · Norway · Denmark · and more.

Contact

For support, partnerships or legal enquiries:

MaxMenu Inc. · 1111B S Governors Ave STE 25367, Dover, DE 19904, United States