#paul_payment-nextaction
sterile fogBOT
đ 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/1273397252433514680
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
sage quest
Have you been able to consistently reproduce the behavior yet?
nova hazel
Unfortunately this is a production error and we can't replicate it easily
This might help as well:
"next_source_action": {
"type": "use_stripe_sdk",
Here is the payment intent link:
https://dashboard.stripe.com/payments/pi_3PnkczFfzadd3IOM1cCt6Kxx
anything you can provide in terms of the cause? thanks for the help on this!
sage quest
As far as we can tell on our end, it looks like this confirmation was handled as expected. That being said, your API version is ancient 2015-10-16 so there could be something going wrong that I'm not aware of. I think we would need screenshots of the console errors and network requests that led up to the issue, in order to troubleshoot further
nova hazel
So this is all the info we have access to, BUT we can definitely look into upgrading our API
sage quest
It might be worth it. next_source_action is deprecated in favor of next_action, but other than that, the payment flow shouldn't require too much refactoring
sterile fogBOT