#fecabouffe
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- fecabouffe, 8 minutes ago, 6 messages
Hi again, sorry to hear those didn't allow you to reproduce the behavior. Can you share the ID of a request where you tried to update a Customer but encountered the error that you referenced?
I try to get it. I can get the ID is in the Exception I guess?
Yes, I believe our error messages now include the request ID, it should have an req_ prefix. Or you can find it in your Stripe dashboard:
https://support.stripe.com/questions/finding-the-id-for-an-api-request
req_kvewWWzQp1UN7w
👋
That request is a 3DS failure upon attaching the card to a Customer
You shouldn't be attaching the card directly.
As this does trigger a card validation and 3DS can be required
You either want to attach via a PaymentIntent or a SetupIntent
What integration flow are you using here?
Front-end:
- create payment method with
stripe.createPaymentMethod('card', this.cardElement)
Backend (PHP): - create/update customer with this PM as default
- create subscription -> if invoice has status open_3ds, I do a confirmCardPayment
- done
Yeah okay so you want to change that flow slightly to using payment_behavior: default_incomplete when you create the Subscription and then pass the latest_invoice.payment_intent.client_secret to your frontend to use with confirmCardPayment()
You shouldn't be using createPaymentMethod() here
Oh, ok. Thanks for the tip. I will check what I can do with that.
Is it something dependent of the user's bank? Because I have this issue only with one (or few) banks righ now. It's working well for everyone else