Stripe Payment Gateway failing for recurring subscriptions

Hi,
When a customer sets up a recurring subscription using Stripe, the initial payment goes through but the subsequent ones do not. From what I can tell, this is because the payment method is stored against the customer, however it is not set to be the 'default' payment method. Therefore it is not automatically used for subsequent payments.

I received this message from Stripe support when I queried why a specific customer's payment did not go through:

The Payment Method was attached to the customer during the PaymentIntent Confirmation request by setting 'save_payment_method: true':

This parameter — 'save_payment_method: true' — is from before we built the default behavior of 'setup_future_usage'[0], which will automatically make these Payment Methods the default for the customer. This is why you will no longer see 'save_payment_method' as a documented parameter in our API Reference.

Thanks

Stripe API is versioned with support for previous API versions.

Please make sure to set same API versions on both CBSubs Stripe gateway and on Stripe.com side.

Then the parameter will be accepted and works fine, we have several community members using auto-recurring Stripe payments.

I received this message from Stripe support when I queried why a specific customer's payment did not go through:

The Payment Method was attached to the customer during the PaymentIntent Confirmation request by setting 'save_payment_method: true':

This parameter — 'save_payment_method: true' — is from before we built the default behavior of 'setup_future_usage'[0], which will automatically make these Payment Methods the default for the customer. This is why you will no longer see 'save_payment_method' as a documented parameter in our API Reference.

Their API changelog makes no mention of this.

stripe.com/docs/upgrades#api-changelog

We're using handleCardPayment, which also appears to be deprecated and their API changelog again makes no note of this.

stripe.com/docs/js/deprecated/handle_card_payment

I thought Stripe was better than this. I don't understand how they expect me to remain informed of deprecation's if their changelog doesn't note them. Have added a feature ticket to review their API further as I will apparently have to dig for deprecation information.

forge.joomlapolis.com/issues/8095

Ok, looks like JS API deprecation's are only noted on the below page and not in the changelog.

stripe.com/docs/js/deprecated

The concerning issue is this deprecation was made in v3 of their JS API where this was previously working fine and suddenly now it does not. I hope this does not continue to be a problem in the future.

Thanks for the update.

Since our Stripe account is brand new, I didn't automatically see the option of the older APIs from my Stripe dashboard.

However when I contacted Stripe support and asked them to set my API to the older version, this was done very quickly and easily.

I can confirm that the CB Stripe plugin is working correctly once I had the correct API set.

Thanks