FAQ
Practical answers for the questions merchants ask first.
This page exists to clear the practical hurdles: setup effort, payment trust, restaurant fit, and what support looks like if the merchant still has doubts.
Setup and launch
Setup and launch
Do I need new hardware to run Pizza x402?
No. The public setup path is built around phones and browsers, not a new countertop device. The goal is to fit beside the current operation, not replace it all at once.
Is this a delivery marketplace?
No. Pizza x402 is focused on direct prepaid pickup ordering. It is meant to reduce phone-order chaos and pickup friction, not become a discovery marketplace or dispatch system.
What happens after I click signup?
The first step is a lightweight owner account. From there, Launchpad saves progress while the merchant finishes profile details, payment setup, storefront review, and go-live checks.
Payments and trust
Payments and trust
Is this basically a crypto product?
No. Card is the simple customer path today. x402 stays available as an optional merchant-enabled branch, but it should not define the mainstream first-run experience.
Who controls the promised pickup timing?
The merchant does. The product is designed so staff can confirm timing and keep the pickup promise realistic instead of locking the kitchen into a bad default.
Do I keep the customer relationship?
Yes. The product is positioned as a merchant-first direct ordering channel, not a third-party marketplace layer that takes the brand and relationship away from the shop.
Operations and support
Operations and support
Will customers actually use it instead of calling?
That depends on the merchant and rollout, but the product is designed around the simplest customer behavior change possible: order on a phone, pay before pickup, and arrive ready to collect.
What if I need help during setup?
There should be a clear support path for merchants, but the public site and setup flow should not assume founder hand-holding is required to get through the basics.
Still Need Help?
Support should be visible as a fallback, not the whole setup model.
Merchants should be able to ask for help, but the site should still leave them feeling that the self-serve path is clear enough to start.
CTA