#abd1hass

1 messages · Page 1 of 1 (latest)

limpid hatchBOT
acoustic frigate
#

Do you have more details? Like the PaymentIntent ID and any error codes/logs you're seeing on your end?

limpid hatchBOT
woven egret
#

this is the paymentId pi_3NvhetJW5eVJnn2s1fedTojI

#

Unfortunantly we dont have client side logs just yet

#

but maybe il put one in on that component

#

he made several attempts. here is another. pi_3Nvh6TJW5eVJnn2s1H23k1PO

daring vessel
#

Hi 👋

I"m stepping in for @acoustic frigate as they need to leave soon. Just to be clear, you are getting redirected but without any of the Stripe object ids?

woven egret
#

yes. this happens randomly. Some other users face the issue as well. Redirect just hits the url without the params

daring vessel
#

Hmm... looking at this first one I can see the Intent failed auth but that shouldn't interfere with the redirect

#

Both appear to have failed auth

woven egret
#

in my code, im mostly following what the docs say. So cant be that.

#

sorry made a mistake, it doesnt even redirect. it actually takes them back to the same page they came from but params and state are removed by then

daring vessel
#

It could be that these payments are all failing durign the auth step

woven egret
#

Whats the normal process i should be doing if auth fails? i would have thought users get sent back to the same page without a refresh with the same URL

#

i do catch the error in a .then() and display

daring vessel
#

Okay yes if auth fails we don't redirect. The API returns the error which will include the following message you can display to your user
"message": "We are unable to authenticate your payment method. Please choose a different payment method and try again.",

#

The idea being that you want them to try a different card (or other payment method) and not be directed away from the payment element

#

So this behavior is expected

#

Since it allows your customer to choose a different payment method and complete the payment

woven egret
#

This already does work

daring vessel
#

Okay, I just explained why you are not seeing the redirect behavior you expect but you are telling me "this already does work" so what does that mean?

woven egret
#

sorry i meant when auth fails, my application shows the error message that comes back from stripe

daring vessel
#

Okay. So at that point not redirecting the customer is the expected behavior since your customer has not completed the payment.

woven egret
#

sorry i got to go. but il get my customer to try again and this time il try catch the error on client side