#WpgJetsFan13
quiet laurel
whole drift
Hello 👋
We've typically seen users either rely on the webhooks OR poll the API to retrieve the status of a subscription/checkout session.
cold matrix
Yes, that's what I've figured. I've already tried both, but it seems that by the time we get to the page that calls Stripe to fetch the subscription, it isn't there yet
whole drift
Aside from those, I don't think there are any alternatives. Depending on network infra it may have some delay but we've not heard of slowdown issues from other users.
cold matrix
so it's still not fast enough
There is a thread about it on github actually, so other users have definitely had trouble with this.
The thread is closed though
whole drift
Can you link the thread here?
cold matrix
sure, I think the original question on that thread is about the delivery order of the webhooks, but some comments mention what I'm talking about, more or less
It would be helpful if Stripe allowed you to attach some state data to the checkout session, and if Stripe would pass that data to the successURL as query params or something when checkout is complete. Just a suggestion. Right now, the front-end knows the checkout was successful based on the url being called, but that url could be called by just typing it in the browser. If it had some state data we could compare with our system, we could rely on that and immediately display to our user that they are subscribed. Other than that, I think we just have to retry fetch until we get a good response
I guess I'd probably have to make that suggestion on github though, not here
whole drift
Yeah I definitely understand your usecase. However, with Checkout alot of things are happening asynchronously. One thing you can do, is pass your checkout session ID to your client-side as shown here
https://stripe.com/docs/payments/checkout/custom-success-page
whole drift
Let me know if that helps ^