Saved cards appearing without vaulting enabled and SetupIntent missing for subs

Hi @pixdata2,

The Saved Cards functionality/option appears on the checkout page but we didn’t have vaulting allowed in the payment settings:

Anytime a subscription is purchased, the payment method is vaulted because it must exist in Stripe in order to process a recurring payment. The option you’re referring to makes sure the Save card checkbox isn’t available on the checkout page for non subscription product. So to reiterate, anytime an order requires a saved payment method, the plugin will save it automatically. As is the case for a subscription.

As it’s a subscription product, we’re missing the SetupIntent on Stripe.

A SetupIntent is not created or used when a saved payment method is selected to process an order. It’s redundant since the SetupIntnet is only needed the first time a payment method is being saved and there is no payment being take. An example is a subscription that has a trial period.

If the customer uses a saved card, they get a blank error:

Check your WooCommerce > Status > Logs and see if there are any failure log entries. Also check your stripe.com account logs under the developer tab. See if there are any clues there as to what that blank error message is about.

Kind Regards,

Hi, thanks for your help.
We already checked with Stripe support that redirected us to WooCommerce support that sent us here.

I’ve also checked the “wc-stripe” log and I noticed that those payment intents using a saved card don’t get into it.

Instead I found several of this error (which are related with the time of the failures) in the “fatal-error” log:

2021-11-21T08:43:48+00:00 CRITICAL Uncaught Error: Call to a member function get_payment_method_title() on null in /home/519969.cloudwaysapps.com/quzqzrfwaj/public_html/wp-content/plugins/woo-stripe-payment/includes/abstract/abstract-wc-payment-gateway-stripe.php:1213
Stack trace:
#0 /home/519969.cloudwaysapps.com/quzqzrfwaj/public_html/wp-content/plugins/woo-stripe-payment/includes/abstract/abstract-wc-stripe-payment.php(169): WC_Payment_Gateway_Stripe->save_zero_total_meta()
#1 /home/519969.cloudwaysapps.com/quzqzrfwaj/public_html/wp-content/plugins/woo-stripe-payment/includes/gateways/class-wc-payment-gateway-stripe-cc.php(288): WC_Stripe_Payment->process_zero_total_order()
#2 /home/519969.cloudwaysapps.com/quzqzrfwaj/public_html/wp-content/plugins/woo-stripe-payment/includes/abstract/abstract-wc-payment-gateway-stripe.php(366): WC_Payment_Gateway_Stripe_CC->process_zero_total_order()
#3 /home/519969.cloudwaysapps.com/quzqzrfwaj/public_html/wp-content/plugins/woocommerce/includes/class-wc-checkout.php(980): WC_Payment_Gateway_Stripe->proces in /home/519969.cloudwaysapps.com/quzqzrfwaj/public_html/wp-content/plugins/woo-stripe-payment/includes/abstract/abstract-wc-payment-gateway-stripe.php alla riga 1213

• This reply was modified 3 years, 3 months ago by pixdata2.

Hi @pixdata2,

Thank you for those log entries. I will do some testing on our end and get back to you ASAP on any findings.

Do you have a staging site where this error can be re-created?

Kind Regards,

Hi @pixdata2,

After testing we did find a scenario where this error occurs. We will include a fix for this in the next release coming out later today.

So you don’t have to wait, please reach out to us via the Help button in the plugin settings.

We sincerely apologize for any inconvenience this issue has caused.

Kind Regards,

Version 3.3.13 released.