#cerebraldad

1 messages · Page 1 of 1 (latest)

marble loomBOT
austere delta
#

say... would it be more beneficial to use stripe to keep track of the credits or should i just do that on my backend

bold pivot
#

hey..

austere delta
#

Hello 👋

#

If you are giving your users a set amount of credits per payment, that would be a standard price. Metered billing would be more for if you tracked how many credits they used and then billed them for it at the end of the month

#

And typically credits would be best to track in your DB. You can do something like store them on the Customer object's metadata but that would be slower to look up and update than your own DB

#

And it would constrain your API rate limit for doing other things on Stripe, so it would be harder to scale

bold pivot
#

so the issue im facing is not to be a pain in the butt with the finances. I want them to use the app and not worry about usage...but the fact is getting the information in the app is expensive - I want to make sure that im covered

#

so charging the user $10 per month might not be worth it for some if they are low usage - but ... anyway see where im going? Not sure how to structure this

#

im using the firebase extension btw

#

@here

#

with metered billing can people add an initial balance?

austere delta
#

Can you tell me what you would like to do for the users that aren't active enough to charge $10 a month? Do you want to charge them less frequently or only after a certain amount of usage across months or something?

austere delta
bold pivot
#

yeah

#

i might have to go with a price product and move on from there once i know usage.

austere delta
#

Still not clear on your use case unfortunately. Can you give me a specific example of what you would like this to look like?