Custom Pricing Units in Flexprice (price in credits, bill in USD)
Custom pricing units solve real credit/token billing chaos, but Stripe + Chargebee already do this.
Dual conversion rates for credits, but existing billing platforms already handle this.
Product and finance teams at SaaS companies with credit/token-based billing systems.
Stripe Billing · Recurly · Zuora
We shipped explicit Wallet Conversion Rate controls in Flexprice to answer that cleanly.
Each wallet can now define: • conversion_rate — how credits map to currency when spending • topup_conversion_rate — optional rate used only when adding credits
This supports use cases like promotional top-ups, bonus credits, or discounted purchases while keeping invoice calculations consistent.
Wallets store credits.Invoices remain in a single base currency. Conversion defines the relationship between the two.
The goal is simple: make credit systems flexible for product teams and predictable for finance teams. Happy to answer questions about edge cases or implementation details.
Custom pricing units solve real credit/token billing chaos, but Stripe + Chargebee already do this.
Makes billing config prompt-operable; non-engineers can change pricing via their IDE.
Shareable URLs encode the entire receipt so no screenshots needed in group chats.
MCP server for credit cards is clever but only works if you have a Klutch card.
Removes S3 setup friction, but Stripe Billing, Lago, and Chargebee already own this space.
AUSTRAC compliance as a moat beats fleeing to lower-fee platforms.