#nash - hooks.stripe.com error
1 messages ยท Page 1 of 1 (latest)
Hello, is this happening after you make a certain call in your javascript code?
Do you have more info on what this error looks like or where it comes from otherwise?
The QA person, got a 3ds dialogue and clicked through it. At the end this popped up.
Our JS just got to call the call the invoked the 3ds (need to look at code for detail).
The transaction shows as success on stripe dashboard.
But this error broke our JS flow, the account never got created on our side.
Could you look into your internal logs if I give you the transaction id?
Maybe there's something there? We don't call hooks.stripe.com at all. So seems internal to stripe.
Do you have the ID of the payment intent associated with this error? (pi_12345)
Just pasting the image here so I have it for reference when only looking at the thread
Is that error entirely within the modal that 3DS was in?
One sec
Checking to see if I have the pi id.
It's taking me a second. Looking still...
pi_3LewSaJ48AZtLH6B1YPPl1VV
There you go.
Is that error entirely within the modal that 3DS was in?
yup
Gotcha thank you. Logs on our side look fine, if that issue is entirely within the modal I think this seems like it is client side but it may be within our code.
Have you only seen it once or have you been able to reproduce this more?
Only once. We tried same card again, and it didn't happen. What leads me to believe it may be within your code is because we don't explicitly call hooks.stripe.com in our code. So can't think of anything else.
Yeah, can you DM me your email so I can grab the ticket? I feel that this may need to be escalated on our side.
๐โโ๏ธ
Did you happen to take a screenshot of the developer console or anything that might show more error info?
๐ฆ nope. It was QA side. I asked them to do so if it happens again.
discord noob here, can't figure out how to dm ๐
Do I need to add you as friend first?
Just sent you one if that helps
Shouldn't need to. If you click on my name a dialogue should show up that allows you to send one
Oh also I am guessing they tried clicking "Try again" and that didn't help?
There is a decent chance that this was a one-off networking issue if the page works otherwise but I will see if there is more we can do here.