#zaddler_api
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/1219361315248930919
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- zaddler_api, 3 hours ago, 41 messages
- zaddler_unexpected, 8 hours ago, 51 messages
- zaddler_code, 4 days ago, 26 messages
hI
Hello ๐ , can you tell me more about how you are creating these subscriptions and what specifically you are seeing where we tell you the limit is 3 years?
I want a subscription with an infinite billing cycle, is it possible?
That is to say, it never ends, since it is a free subscription, it is to avoid registering many records per webhook database.
Ah, so that setting is how often the subscription cycles. So like if you have a monthly subscription, it will cycle and charge the user every month, but it will cycle indefinitely until the subscription is cancelled
Correct
Are you saying you want an infinite cycle? We do not support those at the moment.
Can you tell me more about what you are trying to do overall with these subscriptions?
What happens is that, every month, I add the user billing to the database, but if it is a free plan, and a user never uses paid plans, there will be many records, so to avoid this, it is to make a plan free has an indefinite duration (it is to save records in the database).
At that point is there a specific reason to create a Subscription object with us? I feel like it may be easier to have some flag in your DB that they are on a free plan and provision access based on that.
Indicate that they are on a free plan, but without the need to add it to my database, is that what you mean?
Honestly it's to let my system know it's on a free plan.
Without creating the Stripe object is more what I was getting at. Sometimes it can just be easier to provision things without creating a Stripe object and just recording things in your own system.
Otherwise, to actually use subscriptions here 3 years would be the closest you can get
I understand, well I still think that every 3 years is also useful, for the moment, I hope that in the future Stripe can take into account indefinite subscriptions.