Where the buying flow shifted
Stripe pricing-model docs split products, prices, intervals, usage, and currencies into objects, which is useful for auditing whether the front-end pricing page explains the buying facts.
Back-end pricing can be complex, but the public page must clarify subscription interval, one-time fees, overages, discounts, trials, and cancellation.
Do not trust one metric
The signal matters when it clarifies the buying path, not when it adds another isolated commerce feature.
Check the transaction boundary
- Map product object, price object, billing interval, currency, trial, discount, and overage fee into pricing-page copy
- Keep the test narrow: one priority product or checkout flow before expanding recommendation, authorization, payment, and support work
What still needs proof
Supporting hybrid billing in the back end does not mean buyers understand how they will be charged. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.