Money-in is now a browsable public path.
This page shows the first real commercial route without pretending the native settlement story is finished. Hosted checkout, credits, checkout security, revenue launch paths, and the go-live posture stay visible together so a builder can see how money enters the runtime and how that work is carried forward into proof and delivery.
Hosted checkout
The hosted checkout operator summary keeps the money-in path explicit instead of hiding it behind generic payment copy.
- Purchase intents: 0
- Checkout pending: 0
- Paid intents: 0
- Credits issued: 0
- Execution dispatched: 0
- Refund review required: 0
Operator shell · Operator shell JSON · Purchase intents · Demo purchase intents · Credit bridge grants
Checkout security
The checkout event security summary keeps webhook verification explicit so money-in doesn't become a soft trust boundary.
- Verification required: false
- Secret configured: false
- Max age seconds: 300
- Signature mode: hmac_sha256_timestamped
- Ready: false
- Blockers: 1
Checkout security JSON · Checkout normalize · Purchase intents
Revenue launch path
The revenue path keeps the money-in story tied to paid execution, proof carry, and reversal so it stays useful after the first payment arrives.
- First money-in paths: 2
- Paid execution paths: 2
- Proof followthrough paths: 3
- Refund or reversal paths: 2
- Operator reconciliation paths: 3
- Hosted checkout paths: 2
Revenue launch paths · Delivery summary · Runtime durability
Launch posture
Go-live and money-in should stay adjacent so the commercial path remains bounded and readable.
- Launch state: current
- Blocking issues: 0
- Configured treasury profiles: 0
- Native settlement ready: undefined
- Checkout ingress security ready: undefined
Go-live · Receipt · Activation · Release kit · Governance disputes
Related surfaces
Money-in is easiest to understand when it sits next to the rest of the public map.
Start · Try · Stack · Catalog · Money-in · Operator shell · Proof · Claim · Releases · Site map