#nishabkumari
1 messages · Page 1 of 1 (latest)
Hi there 👋 no, you cannot automatically approve transactions that require 3DS. The 3DS challenge must be completed by the customer when required.
How is your flow currently handling the process of collecting payment method details from your customers?
We take payment method while creating subscriptions and one time payment is done my customer while subscriptionsa re created.
the problem somes at time of renewal or when we modify quntity of the subscription via API
CAn you help me understadn if e-mandate will help in this case? and if yes, how to activate e-mandate flow ?
Can you elaborate on this? Is it the one-time payment that is creating the Payment Method you're later trying to reuse? Can you share an example of a Subscription running into this concern?
subscription - sub_1Nj1YLDvzL5KbtwGEgtY5sEo, i tried to make a off season payment on this - in_1NmxmDDvzL5KbtwGhOXeDV73 , pi_3NmxmDDvzL5KbtwG0Uyl232y
you can check this subscription.. while creation of subscription, Credit card information was added. later for renewal and also for off season the payment is not done as waitign for user to take an action
Was 3DS ever completed for that card? I looked at the first intent where it was used, but it doesn't look like it moved to a succeeded state.
If the customer never completed a 3DS challenge, then their payments are likely going to keep running into this behavior. The Payment Intent initially used for that Payment Method is using setup_future_usage: off_session (because it's coming from a Subscription's Invoice), so the need for 3DS should be reduced if that Invoice were successful, but it seems the customer did not complete the authentication process.
we do have examples where the initial payment was success, still the renewal needed user to confimr the payment via email link
i need to search for the example
Is there any chance that Subscription involves India? They have more strict requirements around completing 2FA for recurring payments, so it may be expected that your customer needs to complete additional authentication each time. That is talked about in more detail here:
https://stripe.com/docs/india-recurring-payments
can u check once sub_1NgME4DvzL5KbtwG5LMm6cV1
yes m checking indian card transaction
It looks like the authentication challenge was completed for a previous payment for that Payment Method.
Choosing when a customer must complete additional authentication is not something Stripe controls, it is up to the issuing bank that provides the card to decide when they require the customer to complete an authentication challenge.
then what we should do in this case ?
how t ensure that customer doesnt have to confirm payment every month ? as this can be hassle for customers
They might have to if that is what their bank decides to do.
i am also from India and i am using my wallet for many indian subscription .. but i dont need to confirm payment every month
i use products like Amazon, NetFlix, Google etc
Hm, I don't have firsthnad experience with those restrictions. Are all of your customers experiencing the behavior you're describing, or only a subset of them?
all users received an email and had to confirm the payment
is there any setting we are misisng while subscription creation ? or any other thing we can do to make it enable ?
Not that I've noticed so far.
As far as I can tell, everything is being done the way we recommend. At this point I would recommend having your customers reach out to their banks to confirm whether their banks are intending to request authentication with each purchase. If this it is a requirement of the issuing bank to complete authentication more frequently, then we don't have the ability to avoid that.