#davidthorand
1 messages ยท Page 1 of 1 (latest)
Hello! 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.
- davidthorand, 1 day ago, 76 messages
- davidthorand, 2 days ago, 19 messages
- davidthorand, 5 days ago, 15 messages
You mean a webhook event?
Yes
You can only expire the Checkout Session, so there's a checkout.session.expire webhook event: https://stripe.com/docs/api/events/types#event_types-checkout.session.expired
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I see. My idea was to listen for a checkout cancel event and assign some sort of default price to those customers. But if there is no event for that I gotta do that differently then
Yeah, you don't cancel checkout sessions. You expire them. So you'd want to build your workflow around that instead
Won't work either since the issue is that nothing tells me that the customer canceled (= abandoned) their checkout
Ahhhhh, that's what you mean by "cancelled".
You might look into abandoned cart recovery in this case: https://stripe.com/docs/payments/checkout/abandoned-carts
Yeah, sorry. Though "canceled" was the right term since you also specify a cancelUrl when creating a checkout session. My bad ๐
Let me check that
I don't think this will work in my case. What I want to do is to assign a default (free) subscription to these users
Ahhhh, gotcha. Yeah, you would have to handle that via custom code and routing on your end then.
Likely by setting the cancel_url to a page with a form that allows customers to create a free subscription
Yeah, I'll probably redirect the user to something like /?checkout-session=cancel and send a request which does the rest.
Just hoped I can hook into a webhook event and prevent that extra step in the frontend ๐
Thanks anyway, always great talking to you guys here!
Maybe it's even better to have the frontend involed so the user can be informed about what happend. Might be kinda confusing to abandon the checkout and enter the application anyway
Yeahhh, that's fair. Best of luck all the same! Happy to help