#phpeixoto-3ds
hollow glen
Typically when you create PaymentMethod tokens from the Sources objects, it carries over the SCA/3DS auth exemption
Issuers however can request 3DS anytime
short shadow
I didn't create new PaymentMethods, I simply retrieve them as so
pm = stripe.PaymentMethod.retrieve('card_12345')
hollow glen
Umm, can you share example objects for this scenario so that I'm on the same page?
like pm_xxx ID, card_xx ID as well as the payment intent ID (pi_xx) where you saw 3DS requested?
meager tokenBOT
short shadow
I cant because it's production data
let me see if I can reproduce that in test mode
short shadow
pi_3OLbP0EA31HiYedh06WlFlX8
card_1NroPZEA31HiYedh0xvnoceO
grizzled venture
Yeah so sometimes banks will require 3ds auth on transactions. You'd need the customer to come back online to auth it
No way to handle it on the backend
Customer needs to be present for that
Going forward, when you collect payment details, you should use a setupintent or payment intent with setup_future_usage to prevent this from happening often
But it's still possible
Really it's up to the bank
meager tokenBOT
phpeixoto-3ds
short shadow
=/
That's a bummer. I'm already using setup intents for new customers, but all of my customer base is already built with those old card Sources...
grizzled venture
Let me check with a colleague to make sure I'm not missing something here
These cards used to work OK with the old Charges API.
Can you share some charge id's where charging that above card_ succeeded off session? Just for comparison
How frequent is this issue?