Payments

Simple checkout for customers, flexible rails behind the scenes.

The public site should make payments feel safe and easy to understand: card works today, optional modern rails stay optional, and the merchant payment story should not feel platform-opaque.

Start setup See the live demo Open payment docs

Pickup-only flowCard-first todayLaunchpad setup pathLive storefront demo

Payment Trust

The payment page should reduce fear, not add technical curiosity.

Card works today

The live rollout is card-first because it is the lowest-friction path for mainstream customers and the safest path for merchant conversion.

Modern rails stay optional

x402 and onchain payments remain available when a merchant deliberately enables them, not as the first thing every customer must understand.

The payment story stays readable

The site should explain how checkout works in plain language, without pushing crypto mechanics into the hero or the setup path.

Merchant control stays visible

Payment setup belongs to the merchant activation path, and the payout story should feel clear rather than platform-opaque.

Merchant Questions

Where does the money go, and who controls it?

The site should answer this in plain language. Payment setup belongs to the merchant activation path, and the payout story should be visible enough to feel credible.

Card-first checkout is the current live launch posture.
Optional x402/onchain payments appear only when the merchant enables them.
The merchant setup path should make payment readiness explicit before go-live.

What This Page Must Not Do

Do not turn payment explanation into protocol education.

A merchant should leave this page thinking “that seems straightforward,” not “I need to become a payments expert before I can trust the product.”

Avoid crypto mechanics in the main narrative.
Avoid technical diagrams unless the reader explicitly asks for them.
Keep the CTA close to the simple merchant setup path.

Relevant FAQ

Answer the payment doubts without overwhelming the merchant.

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.

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.

CTA

If the payment story feels clear enough, the next step should be simple.

Start setup See the setup path