#pro-pooja_webhooks
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/1230511539371638904
đ 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.
- pro-pooja_webhooks, 1 hour ago, 9 messages
- pro-pooja_webhooks, 7 hours ago, 3 messages
Hello
Easiest way to handle this is to simply mock the response instead of actually triggering the Event
Otherwise, you could use the CLI to trigger this Event and use the --edit flag to update the reason. See: https://docs.stripe.com/cli/trigger#trigger-edit
Instructions are not clear
What exact should be sent as parameter to edit the reason
Ah actually I'm incorrect -- that isn't a parameter you will be able to dictate in the fixture since it isn't set via an API request
So let's back up a second
Using a test clock and going through all of the retries using a failing payment method is the way to do this.
What are you trying right now?
Updating the subscription
- attaching this card - 4000000000000341 ,
- setting the subscription end date from forever to future date
- Update the Subscription
Then, simulating the clock to end date set for the subscription, but it is canceling the subscription directly with reason "cancellation_requested"
Well yeah... you don't want to set a cancellation date if you want the reason for cancellation to be payment_failed
That happens when the Subscription goes through all your set retries based on your Settings and then cancels
So, I need to simulate the clock to the next billing cycle date?
You need to check your retry settings at https://dashboard.stripe.com/settings/billing/automatic
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
And then move the clock past whatever the time period you have set for those retries is
It is set to retry 3 days after the previos attempt
And what do you have set for If all retries for a payment fail,?
Cancel the subscription
I am on a test mode, so the live mode's settings will be applied automatically , right?
Yes
Wait no
lol sorry
Yes, we changed this recently
Where testmode should use your livemode settings as well
If you try to change them in testmode you should see them greyed out (disabled for update)
Yes, its grayed out
Can you share a Subscription ID where you didn't set it to explicitly cancel and you advanced time past your retry settings?
sub_1P6urPGVCe8mF8QWU1Evw508
You set an explicit canellation date for that Subscription via the Subscription Schedule
You need to create one without an explicit cancellation as we discussed above
sub_1P6msLGVCe8mF8QW9bhtSXKC
Great now advance time
Advanced to May 18, 2024|5:47 AM GMT+1
Yeah that's not far enough... you need to generate the next Invoice so that payment fails for that Invoice and it goes through the retries
Then when all retries fail the Sub will cancel
How can I genearte Invoice manually?
Why?
You can update the Subscription to change quantity or Price and use proration_behavior: 'always_invoice' if you want to force an Invoice to be generated
There is a 15 GBP Invoice in draft