#bin_subscription-datamodel
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1238161620497076345
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
bin_subscription-datamodel
For #1: that's up to you really, I would say yes personally I'd have my own model(s) that would have a pointer to the Stripe objects with the relevant ids
For #2: The Subscription object https://docs.stripe.com/api/subscriptions/object has items as a property which is a list of SubscriptionItems and each of those is associated with a given Price price_123 that itself is tied with a Product prod_123 https://docs.stripe.com/api/subscriptions/object#subscription_object-items-data-price-product
We don't show the Product name there unfortunately so the easiest is to cache that data in your own Stripe account I would say.
For #3: Trial periods are documented at https://stripe.com/docs/subscriptions/trials but you can't do an "infinite trial" as those are limited to 2 years I think. In the flow you describe, the best approach is to put them on a $0/month or $0/year Price instead
thank you for your quick response ใ
happy to help ๐
@left stump hello again, could you please provide me an example or show me documentation (or facilitate a link to some examples you may have at Stripe's public GitHub) on how (1) would typically look?
We don't have anything like this sorry. We don't really show you how to model things in your own systems
oh, okay thank you