This error has popped up for my users occasionally in the past, but now it’s becoming more frequent and becoming a serious problem.
A payment method of type card was expected to be present, but this PaymentIntent does not have a payment method and none was provided. Try again providing either the payment_method or payment_method_data parameters.
This error sometimes appears when a user currently on a subscription attempts to pay for a different subscription. In the current case, it’s because we changed the membership price, so we had to create a new subscription and make everyone “renew” under that one. Not everyone gets the error, and I can find no reason for it.
Searching here has led me to a single post that implies this error is understood, but did not describe the solution. It probably doesn’t help that I am a total novice when it comes to Stripe, so I may not even be asking the right questions. Hopefully somebody can give me some direction, thanks!
Wow… this got zero response. Is this subscription module unsupported now?
FYI my users are having the same issue…
Love this site, been here a long time. I had been a “supporter” before, but need to change my card. When I try to set this up, I get the following message:
“A payment method of type card was expected to be present, but this PaymentIntent does not have a payment method and none was provided. Try again providing either the payment_method or payment_method_data parameters.”
Not sure if anyone else has this trouble.
I tried via impersonation and got the same message. Card type IS present on the form page, etc. This user was a past Patreon supporter as well but is now in ‘free mode’. Their Stripe account is listed as ‘Cancelled’ in the plugin admin. Again… if these past data points are causing issues with Stripe why not have a way to simply purge this data from the user as them having a defunct Stripe and Patreon account are no longer relevant if it’s going to cause the transaction to fail.
By way of follow-up, to this day nobody has been able to identify the cause of this error, not even the professional consultant we paid to take a look. We are instructing our members who encounter this error to pay via Venmo or (of all things) a personal check, and then we update their membership information manually. This is not sustainable long-term, so we’ve already been looking at other membership management options, and depending on what our leadership decides, this may end with our organization dropping Discourse entirely. Which is a shame.
If there continues to be silence from the Discourse team here, then I would say it’s best to avoid this problematic plugin and look for other solutions.