#meryem-3DS
1 messages · Page 1 of 1 (latest)
we don't have such observation. do you have your account ID or failed declined payments that I can check?
payment id like pi_xxxxx or ch_xxxxx
I'd love to thanks ! For instance this payment_id : pi_3JZ0DwH1dThqjrnZ1ldKR6C8.
I was checking and over the last couple days it's already 700€...
Here is our account id : acct_1DdEc6H1dThqjrnZ
pi_3JZ0DwH1dThqjrnZ1ldKR6C8 was a successful payment with 3DS
The 3DS failure looks very low; once in September, 3 times in August. Nothing out of ordinary as I can see
it is entirely possible user just entered the wrong OTP
Sorry.. Indeed this one passed.
But if you check this event : evt_3JZHRaH1dThqjrnZ1btMpXnd
the client had to test with her card, her husbands one and I had to have her on the phone to give her my details for the paiement to pass through.
I think that the Stripe API that Webflow uses cannot trigger OTP.
I don't know exactly how it works but its this payment (pi_3JZHRaH1dThqjrnZ1JpyGlTE), the client had to update their payment details 3 times.
A maybe. So when payment_intent goes to the requires_action status, the integration needs to handle the action by either
- using Stripe SDK stripe.confirmCardPayment to present a 3DS page for the user to complete
- manually redirect the merchant to a 3DS page
so it seems that Webflow does not handle the 3DS flow properly
Ok more clear 🙂 So I understand it's most probably an integration issue rather than related to the Stripe API they're using that might be outdated, right ?
I believe so. I would recommend reaching out to Webflow ecommerce and ask them to fix this
because due to SCA, is will be very common that the transaction will require authentication
Thank you very much for your help.