We are experiencing repeated Stripe checkout failures affecting multiple customers attempting to purchase annual memberships through s2Member Pro.
Our website is running s2Member Framework and Pro v261110.
Three different credit cards have failed with card_declined / generic_decline errors. Stripe has also recorded several authentication_required errors.
Following an investigation with Stripe Support, they have identified a likely issue with how payment methods are attached to customers during subscription checkout.
Our s2Member logs show that the failure occurs at:
stripe-utilities.inc.php, line 961, within create_customer_subscription().
The failing API request is:
POST /v1/payment_methods/{id}/attach
Stripe Support advises that directly attaching a PaymentMethod to a Customer does not initiate 3D Secure authentication. Where the issuing bank requires authentication, the attachment can therefore fail before a subscription or PaymentIntent is created.
Stripe recommends using a SetupIntent, or a PaymentIntent configured for future usage, to authenticate the payment method before saving it.
Our questions are:
- Does s2Member Pro’s current Stripe subscription checkout support this authentication process?
- If so, why might our checkout be attempting to attach payment methods without completing the required authentication?
- Is there a configuration setting we need to enable, or is this a bug requiring a fix?
- Is there a recommended workaround that would allow us to continue accepting recurring subscriptions while the issue is investigated?
Our last successful subscription was created on 21 October 2026. However, we recognise that this problem may have existed previously and only affected transactions where the issuing bank required additional authentication.
Stripe request ID: req_I0nqbLBIK9C9Ik
This is now affecting genuine membership applications, so we would appreciate an urgent response.