Support (and require) API version 2023-08-16
-
Hi @mattwire.
Looks like 3d secure card fails with
unknwon error
after this change.Test Card Number -
4000002760003184
IntegrationError: handleCardAction: The PaymentIntent supplied does not require manual server-side confirmation. Please use confirmCardPayment instead to complete the payment.
Fixed by reverting the above change and specifying the payment method_types param to
card
by default on Line 421.$intentParams['payment_method_types'] = ['card'];
-
Hmm - I'm not sure if my issue is the same as Jitendra's now.
I've tested 6.9.4, master branch, and master branch plus Jitendra's patch. All three give the same result - an "unknown error" message when using the test card number Jitendra mentions.
Here is the JSON returned from a 6.9.4 submission using that card (on a contribution page, not Webform):
{ "id": "pm_1Nw55HEnauyF0tfyKDZJIV7R", "object": "payment_method", "billing_details": { "address": { "city": null, "country": null, "line1": null, "line2": null, "postal_code": "44444", "state": null }, "email": null, "name": null, "phone": null }, "card": { "brand": "visa", "checks": { "address_line1_check": null, "address_postal_code_check": null, "cvc_check": null }, "country": "DE", "exp_month": 4, "exp_year": 2044, "funding": "credit", "generated_from": null, "last4": "3184", "networks": { "available": [ "visa" ], "preferred": null }, "three_d_secure_usage": { "supported": true }, "wallet": null }, "created": 1696087679, "customer": null, "livemode": false, "type": "card" }
-
Just to confirm, this is the full patch we have on the master branch of stripe extension - https://gist.githubusercontent.com/jitendrapurohit/03a851d0c7e1c54ec7a68c746cabeffc/raw/0ca871c256a228ae2df78959c97a8f93d3915c33/stripe_unknown_error.patch
It works for us on both webform and contribution pages with 3d secure enabled card
4000002760003184
. -
Thank you @jitendra.
I don't know why my dev site was giving an "unknown error" - but since it was doing so even on 6.9.4, and my client confirmed that 3D Secure was working before I pushed the 6.10-dev branch, we rolled back to 6.9.4 and this issue resolved.
So I do think we're seeing the same issue after all. We rolled back because we moved to dev to support a newer Stripe account (they have several) and if we can't use 2023-08-16 API there's no reason to run dev.
-
mentioned in commit 3d66892c
-
mentioned in issue #446 (closed)