#eckhartpark_api
ripe yewBOT
đ 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/1350172685958909952
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
azure shore
So probably my biggest fear here is that I'm sending people to a "success" page when they fail or incomplete their payment.
I don't think it is, but would like confirmation
daring zodiac
Hi, what does 'failed while the other was incomplete.' mean here? From looking at the requests, I can confirm that both statuses on both of the requests show status: "requires_action", . We document how PaymentIntents work here: https://docs.stripe.com/payments/paymentintents/lifecycle?intent=payment
In cases for requires_action, the issuing bank is asking for additional authentication. On this request, req_UXYXevSlGWeWPJ they were redirected to the issuing bank and the customer failed the authentication. For this reason, we're asking for another payment method.
On the other request, you did not redirect the customer to authenticate.
Can you add more context into what you mean by 'So probably my biggest fear here is that I'm sending people to a "success" page when they fail or incomplete their payment.'?
azure shore
Hi I can't find this one that you're referring to: req_yFeauQyMgSmLHl Where do I find it? They weren't the request ids i provided as related ?
daring zodiac
Sorry, I mean to share this: req_UXYXevSlGWeWPJ
azure shore
ok thanks checking
daring zodiac
Sure
ripe yewBOT
azure shore
oh I was mistaken, these both were part of the same flow on the same payment. One followed the other. I get that they are both requests to confirm a payment intent. So in req_UXYXevSlGWeWPJ they were redirected to the issuing bank. It failed, then it goes to req_pX0LFmh9EMsA4k. Why did the flow go to that second request? Did the user try again somehow?
wanton lodge
Yeah
It doesn't fully redirect them
It's the payment element so it handles it on the page in a popup
You should be able to use one of our 3ds test cards on your integration in test mode to see how this behaves: https://docs.stripe.com/testing#regulatory-cards
azure shore
would the appropriate test card be the 3ds DECLINED card to emulate this?
wanton lodge
They each test a different scenario
Depends on what you want to try
If you use 4000002760003184
You can select pass or fail
for 3ds
in the modal
azure shore
right, ok. Can you tell me why this one ended up as incomplete: req_Bii0doTbLdpDef. Is it basically they were sent to further authentication and they just closed out their browser or something?
wanton lodge
That's what it looks like, yeah
azure shore
oh ok, when you said "it doesn't fully redirect them", the user wasn't actually sent anywhere, they were just on the popup and it told them it failed?
wanton lodge
Yeah they're not redirected away from the checkout page
Again, recommend testing your integration in test mode
With some 3ds cards
azure shore
got it thanks
wanton lodge
You'll get a better sense for how this works