For independent takeout-first pizzerias
Pizza x402 gives independent pizzerias a direct ordering flow with self-serve owner signup, Launchpad activation, a one-pizzeria workspace, and a merchant-owned storefront that moves repeat takeout orders off the phone.
At a glance
Best fit
Independent pizzerias with busy pickup windowsSetup path
Owner signup -> Launchpad -> live QRTeam access
Owner, manager, and staff rolesPayments
Card-first today, crypto optional when enabledWhat gets easier
The point is not digital transformation. It is fewer interruptions at the phone, clearer orders, and an easier pickup handoff when service is busy.
QR and web ordering move repeat takeout orders away from the phone so staff can stay focused on service.
A structured mobile order is easier to review than a spoken order taken in the middle of rush-hour noise.
Prepaid pickup reduces payment friction at the counter and gives the first launch a narrow, understandable payments posture: card-first today, crypto optional when enabled.
The restaurant keeps the branded storefront and ordering touchpoint while the owner still gets Menu Studio, Workspace, QR Kit, and role-safe staff access in one place.
What is real today
This site only uses public-safe facts from the current pilot posture, launch scope, and QR rollout guidance. It does not add screenshots, metrics, or testimonials that are not approved yet.
The credibility layer on this site is built from current public facts, not from invented social proof.
The current named merchant focus is Au Comptoir à Pâtons in Lyon, France.
Source: Public pilot posture: README + AGENTS
The live merchant path already covers owner signup, Launchpad activation, workspace, storefront review, and QR Kit without requiring a founder-managed onboarding flow.
Source: AGENTS merchant routes
Axel's current launch posture is card-default. Crypto remains optional and merchant-configurable.
Source: Vision + AGENTS
V1 is built around direct prepaid pickup, not delivery dispatch or marketplace discovery.
Source: Vision
The current merchant guidance already covers stable storefront URLs, print sizes, and placement suggestions for the first QR rollout.
Source: QR Code Setup Guide
Owner, manager, and staff member accounts are already part of the current merchant app, with staff kept out of Merchant Console surfaces.
Source: AGENTS authenticated merchant surface
This is a structured explainer, not a screenshot. It is derived from the current QR setup guide and the documented storefront flow.
Start with the counter, window, flyers, or pizza boxes so repeat customers can order without calling.
Source: QR Code Setup Guide
The direct flow stays simple: menu, quote, payment, then pickup.
Source: AGENTS + storefront flow docs
The restaurant keeps timing, notes, and order status in the direct pickup flow.
Source: Vision + AGENTS
No public storefront screenshot or QR export is approved yet. This section stays text-first until a real public-safe visual is available.
Source: QR setup guide + storefront flow docs
Why the story is credible
The public site should say what exists now, what the pilot is actually testing, and what is still intentionally unpublished.
Pizza x402 should read as a merchant-aligned ordering system first. The AI-ready and onchain direction is real, but it stays secondary to the immediate merchant value.
V1 is built around direct prepaid pickup, not delivery promises or a broad restaurant platform pitch.
The restaurant keeps the customer touchpoint, the storefront stays merchant-owned, and the public site stays lightweight and cookie-free.
The launch-safe payment path is mainstream card checkout for merchants that enable it.
The site does not publish merchant logos, testimonials, or pilot metrics until they are public-safe and approved.
Pizza x402 is being shaped around a real takeout pilot in Lyon. The public story stays careful because public-safe case-study evidence is still limited.
The current named merchant focus is Au Comptoir à Pâtons in Lyon, France.
Source: README + AGENTS
The main public claim is the problem being solved: fewer phone interruptions, a self-serve setup path, and a simpler prepaid pickup flow.
Source: Vision
Public pilot metrics, testimonials, storefront screenshots, and merchant logos are not approved for the website yet.
Source: Current evidence inventory
The page stays evidence-ready by leaving a clear slot for future approved screenshots or case-study facts without inventing them now.
Source: Vision + README + AGENTS
Next step
This site is intentionally conservative: current scope, current pilot posture, and current setup guidance. If that matches your shop, start the owner account and continue through Launchpad. If you still need rollout detail first, use the merchant page or contact path.
Builders and agents
If you are integrating, use the docs and official technical surfaces. The homepage should not make merchants read an API pitch first.
Use the short builder page to find the supported docs, contract artifacts, and official integration surfaces.
Browse the mirrored contract docs, quickstarts, reference pages, and examples on-domain.
Open the current public contract artifact directly when you need schema-first detail.