# Monical's Payment Activation Proof Brief

Generated: 2026-08-10T07:17:12.085Z
Sales page: https://www.apps.betteritgroup.com/monicals
Guided preview: https://www.apps.betteritgroup.com/?demo=1

## Buyer-Safe Purpose

This brief explains the proof required before public card entry turns on. It is designed for corporate review without exposing secret values, readable source, buyer records, or real license keys.

## Current Payment Mode

- Stage: Demo ready, checkout gated
- Checkout surface: Stripe-hosted Checkout Sessions
- Public checkout mode: request_review
- Safe to demo: yes
- Safe to accept payment: no

## Activation Gate

- [ ] Stripe Checkout prices configured - Both purchase paths have Stripe Checkout prices before card entry can turn on.
- [ ] Live Stripe mode confirmed - Test-mode Stripe is for proof only; public buyer card entry requires live Stripe mode.
- [ ] Signed payment confirmation configured - Signed payment confirmation must create access records and enforce hosted subscription access.
- [x] Hosted access sessions signable - Hosted access needs signed app sessions.
- [x] Buyer handoff path ready - Approved buyers need a controlled access code and next-action handoff.
- [ ] Admin launch proof completed - Public checkout waits until the payment setup checklist is fully checked and current.
- [ ] Manual public checkout approval - Public card entry stays off until a human deliberately approves the cutover.

## Proof Run Required Before Public Checkout

1. Create a hosted subscription Checkout Session in test mode and confirm it opens a Stripe-hosted payment page.
2. Create a source purchase Checkout Session in test mode and confirm it opens a Stripe-hosted payment page.
3. Send a signed checkout-complete event for the hosted path and confirm exactly one MIC-SUB key is created.
4. Send the same hosted event again and confirm no duplicate key is minted.
5. Send a signed checkout-complete event for the source path and confirm exactly one MIC-SRC key is created.
6. Redeem the MIC-SUB key and confirm it opens hosted workflow access for the approved buyer email.
7. Open the Stripe Billing Portal from the MIC-SUB confirmation and confirm invoices and payment-method changes stay on Stripe-hosted pages.
8. Redeem the MIC-SRC key and confirm it shows the source handoff plan without opening hosted pilot hours.
9. Prove buyer handoff by sending the approved email or saving the admin manual handoff text.
10. Record the completed proof in the admin launch ledger, then intentionally switch public checkout from request-review to live checkout.
11. Rerun the release gate against the live URL and keep checkout gated if any proof step fails.

## Payment Proof Fingerprint

- Fingerprint algorithm: SHA-256.
- Stored on license as: payment_proof_hash.
- Summary field: payment_proof_summary.
- Purpose: Binds the paid Stripe event, Checkout Session, buyer email, accepted terms, Price, amount, and currency to the issued MIC-SUB or MIC-SRC license record.
- Canonical proof fields:
  - Stripe event id
  - Stripe live/test mode
  - Checkout Session id
  - Checkout request id
  - Buying path
  - License type
  - Stripe Price id
  - Paid amount
  - Currency
  - Buyer email
  - Terms version
  - Terms hash
- Audit result: A matching fingerprint lets an admin trace a Stripe-issued key back to one signed, paid, app-scoped checkout completion without exposing card data or secret values.

## Commercial Continuity

- Hosted pilot: $495 quarterly under the 90-day paid pilot, then quarterly renewal; key family MIC-SUB.
- Source purchase: $9,500 source buyout starting point; key family MIC-SRC.
- Hosted keys grant hosted app access only. Source keys start source handoff planning only.

## Buyer Safeguards

- This app does not collect card numbers.
- Card entry belongs to Stripe Checkout after activation proof passes.
- Hosted subscription billing changes stay in Stripe's hosted Billing Portal, not in this app.
- Public buttons stay in request-review mode until the full payment-to-key and handoff chain passes.
- The source purchase path does not deliver readable source until approval, payment or approved invoice, authority verification, and handoff controls are recorded.

## Not Included

- No real license keys.
- No secret values, webhook values, private service credentials, SMTP passwords, or session secrets.
- No internal environment variable names.
- No readable source files, generated PDFs, raw FoodTec exports, buyer records, admin records, or payment records.