#sl_stripejs-apiversion
1 messages ¡ Page 1 of 1 (latest)
đ 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/1228381944182734908
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there!
Hello
This shouldn't be an issue in this case. We always use the latest Stripe.js version loaded from https://js.stripe.com/v3/ . Just to be clear, you're looking at this request in the Dashboard and that's where you're seeing API version 2020-08-27?
yes in the dashboard the version is 2020-09-27
2020-08-27 (typo)
and I want to test the higher version before I update the version in the dashboard
Yep, I got it. The only version that's important here is what's passed in your backend code. There's no "versioning" for frontend calls
This is an issue with your return URL. It looks like it's not a valid URL
ah ok will look at that - thank you so much
I recommend looking at the value you're passing for confirmParams.return_url: https://docs.stripe.com/js/payment_intents/confirm_payment#confirm_payment_intent-options-confirmParams
@vagrant urchin ah, I was wrong! You can override your account's default API version client side: https://docs.stripe.com/js/initializing#init_stripe_js-options-apiVersion
While this usually never matters, it may be helpful if you're working with frontend code that looks like the status of an Intent. For example, you might be working with an API version that uses requires_action for the status and another version that uses the older requires_source_action