#rodricardona
mystic plank
Hi 👋 we usually don't have much insight into that. The issuer of the card that the customer is using is the party that decides whether or not the customer completed authentication successfully, that's not a decision that is made by Stripe.
Do you have an example handy where you saw this behavior that you can share?
ember vapor
what do you mean with an example any format is preferred? API logs?
Basically my app is for a tennis community where users pay for making reservations for tennis courses. We have several types of payments but the only one with a huge incomplete rate is the courses reservations:
- Payments to be a member seem fine
- Events seem fine
- Reservations huge error rate.
I was wondering if this could be related with the bank or the card provider tagging us as not trustworthy or because the Charge description or something like that
mystic plank
The ID of a Payment Intent (pi_) or Setup Intent (si_) where you saw that would be the most helpful.
ember vapor
sure let me share some in the last couple hours:
- pi_3OMuIdDMlRNnsRlu2XAkyh1C
- pi_3OMuL4DMlRNnsRlu0fecLtfI
- pi_3OMt6xDMlRNnsRlu19TFaGaC
- pi_3OMt8SDMlRNnsRlu1a1TCAih
mystic plank
pi_3OMuIdDMlRNnsRlu2XAkyh1C
Hm, initially it looks like 3DS wasn't attempted for this payment (though required), let me look at this from a different angle.
Alright, I see, looks like 3DS was attempted, but the issuer told us the customer didn't successfully complete the authentication challenge. There isn't more insight that we have to offer there, and for scenarios like that it's typically best to the have your customer reach out to their bank for clarity on why they couldn't authenticate successfully.
ember vapor
ok so it doesnt seem to be a problem on our side, is that correct?
mystic plank
Correct, it looks like the 3DS flow was triggered as expected, which is an indication your integration is behaving as it should.
ember vapor
ok and second related question, would it makes thing easier if I setup intent to get the card preapproved and then directly charge all payments against that saved card? or I would be seeing the same issue?
mystic plank
I honestly don't think it would make much of a difference. Payment Intents can handle the authentication flow when working with Elements, so switching to a Setup Intent + Payment Intent would just sort of separate the steps of the flow. The Setup Intent will still use Elements to trigger the same 3DS flow that the Payment Intents are using.
ember vapor
yes, my point is if for a user I only do a setup intent to save the payment method and then all future payment intents go against that without payment element involved (kind of one-click checkout) would that be a good solution for 3D Secure issues?
mystic plank
No, issuers are the ones who ultimately decide whether 3DS must be completed for them to approve a transaction, so it's possible that even previously set up Payment Methods will trigger a 3DS challenge that the customer must complete. So, while uncommon, it is possible to see a flow where a Setup Intent triggers 3DS, then a future Payment Intent using that same Payment Method does the same. So your Payment Intent flows will always need to be prepared to handle 3DS challenges.
ember vapor
clear thanks!
unborn loomBOT