Hi HN, working in the monetization field, we kept seeing the same problem. Product teams want to price in credits or tokens. Finance wants clean USD accounting. Engineering ends up stitching conversion logic across services, and over time rounding errors, inconsistent invoices, and reconciliation headaches creep in. So we added Custom Pricing Units to Flexprice! You can now define your own unit (e.g. CRD), attach a conversion rate to a base currency (like USD), and use that unit across plans, recurring charges, usage pricing, and wallets. Customers see and are charged in credits. Flexprice computes, stores, and invoices in the base currency. Conversion is deterministic. Rounding only happens at invoice calculation. There’s a single source of truth for the rate. Example: 1 credit = 0.01 USD → 100 credits = 1 USD. This has been especially useful for teams selling tokens, running credit wallets, or operating in multiple regions while keeping accounting in one currency. Docs and API examples are live: https://docs.flexprice.io/docs/product-catalogue/custom-pric... Happy to answer questions on how we model conversion and precision internally or join us here: http:// bit.ly/4huvkDm |