#Cédric Morelle
1 messages · Page 1 of 1 (latest)
Hi
Can you share the Subscription Id or the event Id ?
evt_1NAUJhAslfugMFd95YzPVokV
it's in test mode
In fact I have been using the card test 4242 xxxx xxxx 4242
but why did it set as failed here ?
this isn't the event id you are showing in the screenshot
can you please copy past that eventId here ?
evt_1NAUJhAslfugMFd95YzPVokV
This event is customer.updated and not invoice.payment_failed
evt_1NAUJdAslfugMFd9xOe3gWjX
The confirm request (req_GwFKejcphKOtaO) of the PaymentIntent, returned a 3DS authentication action. Your frontend need to handle these actions.
You need to follow this guide, step by step, in order to cover this use case (if you are using Stripe Elements)
https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements
what do you mean my frontend need to handle these actions? Of course I have been following carefully this guide
go there and click on "go Premium"
then make sure to select the first option
There wasn't a 3ds action when confirming the payment? in this step:
https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements#complete-payment
the anchor #complete-payment does not refer to anything in your link 😦
this is my file may be you could tell me what I have done wrong for checking 3DS ?
https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements
Can you scroll down to "Complete payment" section please ?
which number section is it ?
it shoul dbe 6
is there much modification needed in my file there #1110115127992254544 message ?
Hi! I'm taking over this thread.
ok
I see the subscription is active with all invoices paid. So can you clarify what exactly is the issue? sub_1NAUIkAslfugMFd92mTsQH46
it seems the way I handled this file #1110115127992254544 message is not correct for 3DS. and even when I'm using the test card 4242 4242 4242 4242 it creates an event
invoice.payment_failed (and it trigger our webhook for such case)
Can you share the event Id (evt_xxx) for the invoice.payment_failed?
evt_1NAUJdAslfugMFd9xOe3gWjX
Thanks! Give me a few minutes to look into this.
This event was not triggered when you created the subscription, but when you tried to confirm the PaymentIntent here: https://dashboard.stripe.com/test/logs/req_GwFKejcphKOtaO
Which to me looks expected, since the PaymentIntent then moved in a succeeded status after 3DS was requested.
Sorry I'm totally lost now
Is there something missing in my file #1110115127992254544 message to handle 3DS ?
I tried and it ended to tell me the payment was confirmed
Why do you think something is missing? I don't really understand the issue.
with my current configuration I set here, do I handle properly the 3DS scenario or did I forgot something ?
It looks correct to me!
If you have an example of a PaymentIntent ID that had an issue, please share it here.
I need to perform more tests. Thanks for your help will open a new request if I have to handle issue with 3DS
thanks a lot
for your patience
Note that if your question was "why the 4242 card triggered 3DS", the answer is because you have a radar rule "Request 3Ds if 3DS is supported".