#Dragos-3ds
steel coral
hi! do you have example PaymentIntent pi_xx or SetupIntents seti_xxx that have that issue?
but in general 3D Secure can fail sometimes, the customer's bank might be down or having an issue, it's normal enough to run into it sometimes.
plucky zenith
sure, I can give you some details, just a second
we've tried multiple times with several cards from the same bank, 3DS works for them on other apps, so we are thinking its an issue on our end
pi_3KUXwSKZ3arTVa2l0ozPSkBl
we've discovered that if we disable "Save this card for future payements" in the paymnetsheet the payment goes trough
steel coral
yeah that example is just what I said, there was a generic error from the customer's bank during the 3D Secure protocol.
they should ask their bank why it failed, we don't actually have any information beyond the fact it failed.
plucky zenith
but why does it work when we are not saving the card?
steel coral
we've discovered that if we disable "Save this card for future payements" in the...
maybe in that case we don't ask for 3D Secure(we generally ask for it when saving the card so your future payments get exemptions), so it sidesteps the issue?
plucky zenith
also, is there a way of hiding this option from the paymentsheet (Save this card..)?
steel coral
also, is there a way of hiding this option from the paymentsheet (Save this card...
I think not, if you initialise the PaymentSheet with a customer ID it will present that option
plucky zenith
okey, so basically the issue is with the bank?
steel coral
I would say so!
might also be because it's a RON bank seeing an attempt from a GB merchant in GBP, but really only they know why.
if you're the customer you can ask the bank to look into what happened in their "ACS" (3D Secure server) for the transaction "32063818-7f58-4ce6-b022-03dec3fe8687" (or give them timestamp of exact times you saw the problems).