Stripe failure with payment_intent : requires_confirmation

OK Thanks
I did the migration and will ask Stripe if they can trigger again the past three weeks payments in stand by
Unless there is a solution using CBSubs ? can I trigger something from there ?

There's nothing within CBSubs Stripe to manually trigger recurring payments. Those are entirely managed by Stripe. You might be able to trigger paying of the invoice manually within Stripe > Subscriptions (Stripe > Billing > Subscriptions if your account doesn't have the shortcut) management page though. If nothing there try checking Stripe > Billing > Invoices as well.

After the migration code I get the warning :

Si votre intégration s'appuie sur l'instrument de paiement par défaut de Stripe, veuillez mettre à jour votre intégration de manière à utiliser plutôt que , plutôt que , et plutôt que .

Is this change implemented in CBSubs ?

We've already completely removed sources from our integration long ago and are already using payment_method throughout. So new SEPA subscriptions are already using the newer implementations.

We have migrated everything but need to manually reactivate 100 monthly subscriptions with SEPA payment due to this change.
Hopefully we can trigger the payment again from Stripe but I guess that there is no way to reactivate the subscription with this ? correct ?
Which brings me to ask what setting you recommend for dealing with this kind of failures on Stripe side ?

Hopefully we can trigger the payment again from Stripe but I guess that there is no way to reactivate the subscription with this ? correct ?

If Stripe triggers the payment it should reactivate fine in CBSubs otherwise the user would need to resubscribe as their documentation suggests. I would check if their subscription is still active in Stripe > Billing > Subscriptions though as you can force an invoice payment there. If their Stripe subscription is not active anymore and has went into a cancelled state you'll need to re-collect.

Which brings me to ask what setting you recommend for dealing with this kind of failures on Stripe side ?

This was caused by the way Stripe stores payment methods. They completely removed their old way of storing them. I doubt this will happen again to be honest. Regardless there's nothing we or you can do about it as it was an internal change at Stripe.