#renlaer057
1 messages · Page 1 of 1 (latest)
Hello renlaer057, we'll be with you shortly! 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.
• renlaer057, 2 hours ago, 9 messages
• renlaer057, 1 day ago, 80 messages
• renlaer057, 2 days ago, 38 messages
• renlaer057, 5 days ago, 9 messages
• renlaer057, 5 days ago, 9 messages
• renlaer057, 5 days ago, 46 messages
Not sure why you want to do that, but for example you can expire a Checkout Session by calling the Expire Checkout Session API
I want to get the checkout.session.expired event in test mode. How should I do it?
As i mentioned above, call this API: https://stripe.com/docs/api/checkout/sessions/expire
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
OK
I want to upgrade webhook to the latest version now. Should I click upgrade directly in the console?
Is there anything else that needs to be done? For example, what key should be replaced?
Do you want to recreate the public endpoint?
You would need to recreate the endpoint with newer API version
When I click Upgrade on the dashboard, the API endpoint seems to have been automatically upgraded. Is this OK? Do I still need to recreate the endpoint?
Ah it's ok by then. Just double check can you provide that endpoint Id? we_xxxx
we_1NVxr0ILBklWVE7iQxct4gum
Okay looks good
Sorry for the confusion before. It was for only endpoint created via API
So actually I don’t need to do anything now, it can be used normally, right?
req_9g2gje4gaa9rp4Why can’t I cancel this order?
This order was created at UTC 2023-10-18 07:49:55 and I cannot cancel it after 12 hours
req_V1AYvw47GIu1BE The ID just now is wrong, it is this ID
Please help me find out why this checkout session cannot be canceled
it is already expired
you don't have to manually expire the Checkout Sessions after 12hours
It takes 24 hours to expire, right?
It hasn't arrived yet, so why does it expire on its own?
taking a look
due to what I was mentioning the other day, there was an excessive number of attempts(probably fraud attempts) so we cancelled the underlying PaymentIntent , see https://dashboard.stripe.com/payments/pi_3O2VAFILBklWVE7i00VgQH3X
it seems that essentially expires the Session but I agree it's a bit confusing since we don't seem to send a webhook event for it until the 24 hours later
That's not right. When you canceled this PaymentIntent, you didn't notify me?
well we did generate a payment_intent.canceled event at least : https://dashboard.stripe.com/events/evt_3O2VAFILBklWVE7i0amT04jR
I am not listening to this event now
yep, I know
but I agree it's a bit weird how this is implemented, it's a bit of a rough edge case with multiple products involved here with Checkout and Radar and new protections from excessive retries ,so things are not perfect. You can raise feedback to https://support.stripe.com/?contact=true
So this will cause me an error, I need to listen for this event, right?
I suppose so! personally I'd just ignore the error. You tried to expire the Session, and it was already expired, so fundamentally there isn't a problem and the outcome is the same(customer can't pay).
No, there will be a BUG in our system. When it expires, because I did not listen to this event, it is still pending payment in our system.
So what I need to do is, listen to this event, and when my developer receives it, I need to update this checkout session to: Expired
Is it right?
Please point out the error for me
fair enough, then I suggest raising feedback with the product team via a support ticket so that we consistently send an .expired event when this happens
sure that could work too