Payment Provider Adapter
blueprint · 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
Isolates all payment logic behind a single PaymentProvider interface with a Stripe test-mode implementation, guarded by a feature flag that is off by default. While the flag is off, pricing CTAs collect pre-order intent only: no network call, no charge. When it is on, the adapter refuses anything but a test key, so a live key in configuration is treated as an error rather than an accidental go-live; enabling real payments remains an explicit operator decision, and the provider can be swapped without touching pricing logic.
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: constrained-by
- stripe-sandbox-only
- Uses: uses
- page-templates
- Required by: constrains
- stripe-sandbox-only
Metadata and provenance
- id
- tal-blueprint-payment-provider-adapter
- type
- blueprint
- version
- 0.1.5
- origin
- created in Talomnia
- lifecycle
- public_sanitized
- tags
- payments, stripe, tz-5-12, feature-flag
The source is the private knowledge repository; only the sanitized public projection reaches this site.
verified · tal-blueprint-payment-provider-adapter · v0.1.5