#bubblegum-checkout-migration
1 messages · Page 1 of 1 (latest)
We recommend saving all of that information in your database really before redirecting
Any caveats with saving a temporary version of it before redirecting it, and then saving it permanently when the success page is hit before rendering the HTML?
no that seems fine
so effectively ignoring the checkout.session.completed and just trusting the success page with the CHECKOUT_SESSION_ID
I would always recommend doing both since someone could close their browser before hitting the success URL
I'm curious - isn't this a more common problem? Don't sites want to be able to immediately show the user the digital products that they ordered in their application's dashboard, instead of just showing a confirmation message that essentially says "Thanks for your order. Come back in a few minutes to see it show up in your dashboard."
But you can already totally do that?
That's exactly what I explained. Just it's possible for someone to close their browser before hitting your confirmation page so you want the webhook handler as a back up
OK - this solution just seemed like a workaround, and I was surprised a solution for it wasn't suggested in the docs, since my use-case seems like it'd be a common use-case.
Thanks for the help
sure thing!