What it touches
Order total only.
Internal debug / Internal test only
Fake payment tester
An internal mock can randomly accept or reject a test payment during local debugging.
For a pizzeria
Not something a restaurant should read as a live offer. It exists to test ugly edge cases before any real payment direction exists.
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 real provider.
Current state
Internal test only
executable in pilot-node when explicitly selected
Current declared data-access summary: Order total 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 mock only makes sense after you read the simple pay-at-pickup module that represents the current live edge.
See the current provider boundary
The provider page explains why this remains internal test scaffolding, not a public money claim.
Back to the full module catalog
If you want the broader shape again, return to the grouped module stack.
Technical identity
p4p.payment.godpay-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/.