#nn87-subscription-update
1 messages · Page 1 of 1 (latest)
Is this happening in test mode? Does the customer's default PM use a test card that requires 3DS on every transaction?
It also happens in production
3ds auth is not required on every transaction
in test mode I used the 4242 4242... Visa card... there it happened too
Do you have the Subscription ID (sub_xxx) or the request ID for the update that I can take a look at?
So for that particular subscription, authentication was needed on the update request which is why the Payment Intent was stuck in requires_action . It was waiting for authentication to be completed
Is this something to be handled by the client
?
4242.... is not a test card which requires 3ds on every transaction right?
then why it got stuck there
?
This is likely happening because your Stripe account is in India, which has a lot of regulations (see https://support.stripe.com/questions/rbi-regulations-affecting-payments-from-india-issued-cards) on when 3DS needs to be displayed to the customer.
If in dashboard I go to a particular invoice I see the option to charge the customer then the customer's card is charged then and there
As I mentioned this also happened in the production site where the customer is from USA and has been recurring payments for months but now he suddenly required 3ds
even in tests this is happening since 1 week only before that it was good
I believe RBI regulations also apply to Indian accounts/business in both INR and non-INR transactions, and these regulations are fairly new, which explains why it was working previously
I'd strong suggest reading through what I linked you since there are a number of changes that are required if you're affected by RBI