Stripe failure with payment_intent : requires_confirmation

How can we do to force confirmation ? What is the difference between checkout and Elements now ? and what do you recommend ?

Most of our transactions are automated SEPA recurring payments without the client to intervene, so if there is a new setting somewhere most of our customers will dont confirm

As far as I understand you can manually force a confirmation within Stripe > Transactions. Edit a transaction that's in a state that requires confirmation and there should be a Verify button of sorts there to do so. This however is supposed to be entirely handled by Stripe automatically. You need to get ahold of their support as your recurring SEPA payments are failing for whatever reason. CBSubs Stripe doesn't handle recurring aspects either as that's again handled by Stripe and Stripe simply lets us know when that has succeeded.

Checkout is a hosted payment solution and should've reduced risk of something like this even happening. Elements is on-site and won't redirect away to Stripe.

OK I've asked Stripe support as this is a new issue that we never had.

Clicking on a transaction does not show a Verify button, it's only marked as incomplete with a pop up that the customer did not yet try to pay the invoice !
Very strange as it should have been recurring and automatic. Then the Paymentintent is still marked as requires_confirmation and the invoice is marked_uncollectible.
Can this also happen with Elements instead of Checkout ? Should I change ?

Edit
If I try to manually debit the customer I get :L'utilisation d'une source de débit SEPA dans le champ `payment_method` est obsolète et ne constitue plus un parcours d'intégration valide. Veuillez consulter l'article d'assistance suivant afin de savoir comment résoudre cette erreur : support.stripe.com/questions/i-received-an-error-when-trying-to-use-a-sepa-direct-debit-source-how-should-i-handle-itPour payer cette facture, mettez à jour le moyen de paiement et relancez le paiement.

Could there be an issue with your gateway update as we have a lot of recurring payments made with previous versions ? maybe something is lacking in the stored values in the DB ?

So the documentation basically confirms my worries.

support.stripe.com/questions/i-received-an-error-when-trying-to-use-a-sepa-direct-debit-source-how-should-i-handle-it

Their internal API change resulted in older recurring payment methods to no longer be functional. They however seam to have provided a tool to migrate those older payment methods.

support.stripe.com/questions/reusable-object-migration-from-sources-to-payment-intents

Give that a try. If that doesn't work unfortunately it seams like their last suggestion is to recollect the payment method. Just to be clear again this isn't something CBSubs Stripe (our implementation) caused or can do anything about it was a change at Stripe internally.

Ok I try the migration method
However they advise to update the DB, is it needed with CBSubs ?Mettez à jour votre base de données afin d'utiliser les nouveaux objets PaymentMethodAccédez à l'endroit où vous stockez les ID de Source dans votre base de données locale, puis ajoutez-y une nouvelle colonne contenant l'ID de PaymentMethod ou remplacez l'ID de Source par l'ID de PaymentMethod.

There's nothing to update in the database. We don't store payment methods internally.