Interesting! Is there an escape hatch to drop down to raw Stripe primitives if someone needs a feature you haven’t modeled yet?
This feels like something many teams eventually build internally — curious how you’re thinking about long-term API surface + compatibility with new Stripe features.
Speaking of holes in the stripe API there’s an annoying one where you can’t easily directly look up what user redeemed a specific promo code
Interesting! Is there an escape hatch to drop down to raw Stripe primitives if someone needs a feature you haven’t modeled yet?
This feels like something many teams eventually build internally — curious how you’re thinking about long-term API surface + compatibility with new Stripe features.
[dead]
Looks really interesting. Can you do custom plans for some users?
Hey Felix, yes you can.
This library is simply a wrapper around Stripe with easier implementation and some additional primitives (credits / wallets / real-time usage).
So, just as in Stripe, where you would make a new custom plan for, say, an enterprise use, simiarly here, you'd do the same.
Though, I will admit your `billing.config.ts` file will get pretty crowded...
I will think on it and try to come up with a more user-friendly UX for this use case.
Hey this is cool!