What it touches
Order total and order state.
Internal debug / Internal test only
Ugly-case payment tester
An internal mock for timeouts, wrong amounts, duplicate callbacks, and other payment chaos scenarios.
For a pizzeria
This exists to break things safely in local testing before any broader payment layer is discussed.
Where it fits
Internal tests and future extras
These modules are not the live restaurant offer today. They are internal test scaffolding or planned next-step pieces.
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 is not real money, not real settlement, and not a live customer payment option.
Current state
Internal test only
declared only; scenario executor intentionally not enabled yet
Current declared data-access summary: Order total and order state only. No customer funds, wallet data, card data, settlement, or real provider data.
Read next
Do not stop at one module page.
See the real live payment baseline
This ugly-case tester only makes sense after you read the small live payment shape it is meant to protect.
See the current provider boundary
The provider page explains why this remains internal failure testing, not a public payment promise.
Back to the full module catalog
If you want the broader module layout again, return to the grouped stack.
Technical identity
p4p.payment.chaospay-mock
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/.