#alex-from-fuxam_api
finite widgetBOT
đ 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/1282618480771993641
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
robust idol
I see that the full url is used in the success_url
Stripe Checkout uses the same feature to return you the Checkout Session Id:
https://docs.stripe.com/checkout/fulfillment#configure-landing-page-url
cedar tiger
Is this new ? We used to be able to return information from the checkout like this. Is there any way to still specify query parameters on the success_url?
robust idol
Sorry, maybe I wasn't enough clear. What I wanted to say is that you can specify query params in your return url
cedar tiger
i tried specifying the return_url but i got this "The return_url parameter can only be used with ui_mode: embedded". We are not embedding the checkout session though
robust idol
yes you need to use success_url for the hosted mode.
finite widgetBOT
cedar tiger
If you check the request I sent, it can be seen that i used that and added query parameters that never showed up after the checkout session
We used to use this exact way of redirecting the user to the correct page after checkout and it always worked until now
nocturne ginkgo
hmm interesitng, always possible we changed something, I'd suggest opening a support ticket; if I get time in the next hour I'll look for recent changes if I can(sorry, this morning is extremely busy and my team has a lot of OOO)
cedar tiger
Yes please! I'll keep this thread open in a tab
nocturne ginkgo
so I just quickly tried this on my end and using https://example.com/success?customer=1234 works for me and I'm redirected to that exact URL after the payment
if it's not working for you can you replicate the problem in test mode first, and then create a new CheckoutSession and give me the ID cs_test_xxx so I can visit it?
cedar tiger
yes for sure
one sec
cs_test_b1fxOaGeHFbGv9gbJbTBvpitQvis0iReWVcc0V5XaFPwpfDCC8JK7qFbc9#fid2cGd2ZndsdXFsamtQa2x0cGBrYHZ2QGtkZ2lgYSc%2FY2RpdmApJ2R1bE5gfCc%2FJ3VuWnFgdnFaMDRISkpqTkByTXVRUGA9UjJ3azZuVTRJPURHNFR%2FbU52NGRRdmdjT0NvUn8zTV9vaX93ZlFNTUJxXGRAQmJ9UFZJdVZzUXFoUX0xR0lEYmBCdUNkR1w3bTQ1NVREUVdxc2JwJyknY3dqaFZgd3Ngdyc%2FcXdwYCknaWR8anBxUXx1YCc%2FJ2hwaXFsWmxxYGgnKSdga2RnaWBVaWRmYG1qaWFgd3YnP3F3cGB4JSUl
nocturne ginkgo
ah you paid that one
I mean ,create one, then just give me the ID so I can pay it in testmode in my browser and see what the redirect does.
nocturne ginkgo
to be clear in the API request it says you passed "http://localhost:3000/onboarding/complete/cm0utmn3d0001mikvyg8j33di" , is that what you expect?
after paying I do get redirected to that URL as expected. But your question seemed to be about URL query params? I'm not sure if you're saying the problem is they don't get passed properly when calling the API(in which case I'd want to see your code, maybe it's an encoding issue), or if you're saying the Checkout page strips the params when redirecting, which so far I can not reproduce.
cedar tiger
That url was wrong, sorry. That was me trying to do a workaround. THis one should have the right format https://checkout.stripe.com/c/pay/cs_test_b158KD0rurmJJevUDF80tHzCpB2C66Z9DtyqW5J0BGHNIEMNm3sZUGCXkP#fid2cGd2ZndsdXFsamtQa2x0cGBrYHZ2QGtkZ2lgYSc%2FY2RpdmApJ2R1bE5gfCc%2FJ3VuWnFgdnFaMDRISkpqTkByTXVRUGA9UjJ3azZuVTRJPURHNFR%2FbU52NGRRdmdjT0NvUn8zTV9vaX93ZlFNTUJxXGRAQmJ9UFZJdVZzUXFoUX0xR0lEYmBCdUNkR1w3bTQ1NVREUVdxc2JwJyknY3dqaFZgd3Ngdyc%2FcXdwYCknaWR8anBxUXx1YCc%2FJ2hwaXFsWmxxYGgnKSdga2RnaWBVaWRmYG1qaWFgd3YnP3F3cGB4JSUl
nocturne ginkgo
seemed to redirect for me
nocturne ginkgo
it's probably worth checking the Network tab and logs, maybe we redirect correctly to the endpoint but your service running on localhost is 3xx redirecting to a version without the params.
cedar tiger
Hmm this is super weird. I will and find the issue now, but I thought i would've noticed if it redirected
robust idol
Hey, taking over here. Let me know if there's any follow-up Qs I can answer!
cedar tiger
Hi, Thank you! Im trying to figure out if theres a redirect happening on our end now
robust idol
Have you checked your server logs if it redirects the website?
finite widgetBOT