#greg - subscription payment authentication
1 messages · Page 1 of 1 (latest)
Yes ! I have subscriptions, and payment methods (using 3DS at setup intent) are attached to users. Now that some subscriptions have to be renewed, payments for invoices fail because 3DS is asked again
Do you have an example subscription / invoice id?
This is expected to happen sometimes, and you either need to have a recovery flow to handle this or use Stripe's support for automatic 3DS authentication emails:
I really thought I had done well, because 3DS was handled at user payment intent's registration :
I see that automatic 3DS authentication emails are going out but this asks my users to come back onsite, and I don't want this
Future payments can also require authentication, this is at the discretion of the bank
i think this doesn't happen when credit card is a "source" for stripe and not a "payment method"
greg - subscription payment authentication
hello! catching up here one sec
This invoice in_1KiJ9ZAW5uHSJypiUo0YTPwb
@glacial cobalt
i think this doesn't happen when credit card is a "source" for stripe and not a "payment method"
AFAIK that would be irrelevant here. Looking into the Invoice you shared
(I had a first problem : payment default was not set as invoice_settings.default_payment_method . I solved this for this user before the renewal invoice was generated, so he should be a proper example of my problem)
yeah ok had a look at the original Invoice / PaymentIntent, and then the follow up Invoice and its PaymentIntent
this isn't an integration issue, invoice_settings.default_payment_method or any other field is irrelevant here
the customer's bank just required authentication on the payment, basically what synthridr explained here:
#958024225870974996 message
For ALL my customers ? And for 1 euro invoices ?
I can't help but find it weird
Thing is
It happens systematically for certain users : all that have been created after a certain date
That corresponds to an important change on our side : we switched from source to payment method
Hum no ok I see this : sub_1K0op5AW5uHSJypiI4idTkP4 payment method, no problem
yeah it doesn't have to do with source vs payment_method
just diff API fields, internally they work the same when talking to a bank
but really, I don't have an answer as it all depends on the customers bank. It could be increased SCA enforcement in the customer's country region. Could be any number of other factors that cause authentication being required