#vdtn-PaymentMethod
obtuse dust
Hi! Can you share the request ID (req_xxx)? Here's how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request
prisma knoll
yes, req_pIbsSiKX7r4GcF
let me know if you need any other information
it was a
POST /v1/payment_methods/pm_1LDzioFHjEtCWkTs4zTU93L7/attach
thanks, let me take a look
So you collected the PaymentMethod in frontend (e.g., stripe.createPaymentMethod), and then attach this PaymentMethod to the customer at your backend? am I right?
prisma knoll
yes, that's correct
obtuse dust
OK. Stripe will validate the card paymentmethod when attaching it to a customer, and for some issuers, card validation requires 3DS and your current integration doesn't support 3DS.
I'll suggest you to use SetupIntent to collect the payment method instead, you can find details in this doc https://stripe.com/docs/payments/save-and-reuse
prisma knoll
Thanks, we did consider setup intent. The problem with it is the customer needs to go through double authorization. Once when attaching the payment method and once when making the payment. Since it is a pay now transaction, it's not a good user experience
obtuse dust
Your customer is unlikely to be asked for 3DS again during payment if the paymentMethod was collected via SetupIntent. However, the bank issuer have the final decision whether to trigger 3DS flow or not.
prisma knoll
thanks, I've tried with a few test 3ds cards and they did trigger double authorization
@obtuse dust : is there a good test card that we can use to simulate these kinds of errors in testing mode?
obtuse dust
https://stripe.com/docs/testing#regulatory-cards you can use these cards to trigger 3DS flow
prisma knoll
we could successfully attach cards to the customer for all provided test cards. We couldn't really reproduce that card_error_authentication_required error at all
obtuse dust
OK, another possibility is that the customer might enter the card number wrongly, and that's why it fails in authentication when it's being attached to a customer.
prisma knoll
we are consistently getting 2000 of these errors per day so I don't think that's the case
obtuse dust
Sorry, I read the response of req_pIbsSiKX7r4GcF again. card_error_authentication_required means the transaction requires authentication (most likely 3DS). So the solution I'd recommend is to use SetupIntent API to collect the payment method so that your customer will be able to complete the 3DS flow during this process.
prisma knoll
yes, but is there a test card that could trigger the same error code when being attached to the customer? I've tried all of the test cards including 3ds ones but couldn't get the same error code
obtuse dust
Did you try this one? 4000002760003184
prisma knoll
yes, I did. It can be attached without any issue
obtuse dust
Can you try this one 4000008400001629 ?
prisma knoll
yes, it failed to attach but we're getting a different error code: card_declined, not card_error_authentication_required
obtuse dust
Yes, there's no test card to reproduce the exact error code.
But I'm confident that you are able to attach the payment method with SetupIntent API.
prisma knoll
thanks, would it be easy to introduce a new test card with the exact error code?
obtuse dust
You are right, can you write in to Stripe support about your feedback? https://support.stripe.com/contact
prisma knoll
will do thanks