#marketen_api
serene condorBOT
👋 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/1417518312450953266
📝 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.
- marketen_api, 12 minutes ago, 8 messages
- marketen_api, 4 days ago, 32 messages
merry oriole
hi there, just to make sure I understand, you're trying to avoid having a $0 invoice for a free trial, is that correct?
torpid quartz
hey. sorry for the mess.
yes, or removing the free trial entirely and invoicing the user 15 days after purchasing the product. So effectively the same
merry oriole
ok, one thing you could test out is using a subscription schedule to start the subscription at a later date https://docs.stripe.com/billing/subscriptions/subscription-schedules#start-subscription-future.
you can use Stripe's test clocks feature to simulate subscription behavior over time and make sure you're getting the outcome you want https://docs.stripe.com/billing/testing/test-clocks
alternatively you could handle it completely on your backend. have some kind of time-based job on your server that kicks off the subscription creation at the appropriate date and time
torpid quartz
but by creating a subscription in the future, I wont have a subscription active until that time comes right?
merry oriole
correct, not on Stripe. you would track the user's subscription status on your backend until then
torpid quartz
That wouldnt work. What about this? #1416011977255555102 message
no invoice will be generated, and I will have the subscription created on stripe since the beginning.
Also, since no invoice will be generated, should I listen for customer.subscription.created or checkout.session.completed events? Which one is better?
merry oriole
either one should work, you would just make sure the checkout.session.completed events you're looking at are for subscriptions
the data in checkout.session.completed will be a Checkout Session object, whereas customer.subscription.created will be a Subscription object. so it depends on what data you need access to at the time of catching the event
torpid quartz
That wouldnt work. What about this? https://discord.com/channels/841573134531821...
okay. Right now im using stripe links for the user checkout.
With this approach I will have to generate my custom checkout URLs every time an user wants to purchase my product, so 1 api call to stripe each time. Do I have to care about these API limits?
https://docs.stripe.com/rate-limits#api-read-request-allocations
merry oriole
these rate limits in particular would apply https://docs.stripe.com/rate-limits#rate-limiter you shouldn't get anywhere near that limit though unless your business is massively successsful 🙂