← Docs
Data & implementation
Stripe provisioning
Idempotent upserts, cohort migration, and sandboxed smoke tests.
When you approve a design, Albi can provision it into your own Stripe account as real entities — Products, Prices, Coupons, Entitlements, Portal, and Webhooks.
How it stays safe
- Provisioning is idempotent — re-running skips what already exists and only creates what is missing.
- A full dry-run shows exactly what will change before anything is written.
- Cohort migration rewrites existing subscriptions with a strategy you choose (immediate, at renewal, grandfathered, or new customers only).
- Smoke tests validate self-serve tiers in a sandbox and refuse live keys.
Your responsibility
Provisioning makes real changes to your Stripe account and can affect your customers' billing. Review the dry-run, and communicate changes to your customers. Albi provides the tooling; you own the decision to apply it. Start in test mode.
Run your pricing on Albi.
Tell us what you sell and how you bill. A scoping call gets you the shape of the engagement and a number.