Stripe Sandbox-Only Constraint
constraint · created
Evidence record
- What is verified
- Uses in published workflows: 0
- Revision
- Version 0.1.5
- Validation status
- Public-sanitized publication; no independent validation is claimed.
What this is and why
A hard operator boundary: the Stripe integration runs in test mode only, and no agent may enable live payment collection under any circumstances. Until the operator's explicit go, pricing calls to action collect pre-order intent, never money. The boundary is structural: only verifiably test-scoped keys are accepted, the adapter refuses a live key at runtime, and the payments feature flag defaults to off with its state owned by the environment, not the code.
Where it was applied and what it helped deliver
No published workflow records this capability yet — the count includes only ledger mentions that resolve.
Relations
- Uses: constrains
- payment-provider-adapter
- Uses: derived-from
- honesty-presentation
- Required by: constrained-by
- payment-provider-adapter
- Required by: governed-by
- talo-0024-launch-validation
Metadata and provenance
- id
- tal-constraint-stripe-sandbox-only
- type
- constraint
- version
- 0.1.5
- origin
- created in Talomnia
- lifecycle
- public_sanitized
- tags
- payments, stripe, operator-gate, tz-5-12, tz-12-2
The source is the private knowledge repository; only the sanitized public projection reaches this site.
verified · tal-constraint-stripe-sandbox-only · v0.1.5