#Shadab-3DS
1 messages · Page 1 of 1 (latest)
Hi
It should triggered at the time of creation, when you collect customer's payment method
We follow this approach for payment
As per the this process, 3D secure will trigger if it's required or mandatory
We have tested it in test mode
and seems working fine
but when we try it in production environment
3D secure is not trigger at the time of subscription creation
but now it's asking for 3D secure at the time of renewal
let me share the subscriptionId
sub_1JyxLbFaGWhFAaijEHdPP9b5
My question is that If 3D secure is mandatory or required then it should be ask at the time of creation.
Can you please also check if we are missing anything in this integration?
Are you there @delicate ether
Hello, sorry I am in a MTG and will get back as soon as I can!
sure
Okie I just checked the PaymentIntent
This is the PaymentIntent pi_3JyxLbFaGWhFAaij133sf76L
it didn't require 3DS
I would say it's totally depends on the issuer bank
the bank decided they didn't need to require 3DS, but decided to require it again. The 3DS attempt is "automatic" in this case
but it should be ask at the time of creation not at the time of renewal
Can you please check our logs, Might be we are missing something
Yeah I am checking logs
it doesn't tell anything other than, the bank didn't require 3ds at the first time
it's all we received from card network
The Issuer bank simply responded "Ok go ahead"
But beside this case, your system should be able to handle any similar case, when the bank require 3DS on renewal timing regardless of whether they required it on creation timing or not. It could happen, depends on various banks out there
If your system can handle it, then it's not to be worried, right?
sure