What it touches
Order total and fulfillment type only.
Customer + operator side / Shown in proof
Pay at pickup / cash
The restaurant can keep payment simple by taking cash or direct in-person payment outside the protocol.
For a pizzeria
This is the easiest first live shape: order online, pay when the customer arrives.
Where it fits
Payment and business trust
This is where payment stays intentionally simple and where identity or business verification can later become reviewable.
This page is the readable P4P explanation for one module. It is meant to be understandable before you open the raw manifest.
What it does not own
It does not hold card data, wallets, settlement, or merchant-of-record responsibility.
Current state
Shown in proof
enabled in the demo node and executable in the pilot node when enabled
Current declared data-access summary: Order total and fulfillment type. No card or account data.
Read next
Do not stop at one module page.
Start from the customer order surface
The payment edge only matters after the customer has first seen the direct menu.
Then see the customer follow-up
After ordering and paying at pickup, the next customer-facing surface is the status page.
See the current provider boundary
The provider page keeps the current ownership and proof boundary explicit.
Technical identity
p4p.payment.cash
If you need the developer-facing version, open the GitHub module reference or the raw manifest. The public P4P page stays focused on what the module means operationally.
Open provider page / Open GitHub module reference / Open GitHub provider reference / Open raw manifest
Contact
This module page is still part of the same narrow proof story.
Questions about this module, the provider layer, or the live-pilot boundary: hedegreen.research@gmail.com.
Public proof front door: https://pizza4people.com/.
Broader protocol-family direction: https://protocols4people.com/.