#paulc7053_webhooks
pearl basinBOT
celest relicBOT
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.
- paulc7053_code, 7 hours ago, 36 messages
- paul_ece-googlepay, 3 days ago, 58 messages
- paulc7053_code, 3 days ago, 99 messages
- paulc7053_code, 4 days ago, 51 messages
- paulc7053_api, 4 days ago, 79 messages
- paulc7053_code, 6 days ago, 114 messages
pearl basinBOT
👋 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/1219373233229402172
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
celest relicBOT
native elk
Hello!
languid rapids
Hello 👋
In our test mode environment you can create a test clock, which lets you simulate time passing for things like subscription renewals https://docs.stripe.com/billing/testing/test-clocks
So you can simulate months passing in a minute rather than waiting months
native elk
Yes, I already tried that
But there are no requests being made
Maybe I just set the time too soon? I usually do 1-2 min
languid rapids
Can you tell me more about what you mean by that? Did you advance time on the clock but nothing seemed to happen?
native elk
Yes
languid rapids
As in 1-2 minutes in the future?
native elk
Yes
languid rapids
To see a renewal, what I typically do is check the subscription's current_period_end and then advance the test clock to after that time
If you do at least 60 minutes after that time, the next invoice should be created and finalized
native elk
Okay, so that + one hour
Just to double check, in order to assess wether it's a subscription invoice, I check the event.data.object.invoice.billing_reason
And its value should be subscription_cycle in order to know it's a subsequent subscription payment ?
languid rapids
Exactly