#dcx86-future-payments
1 messages ยท Page 1 of 1 (latest)
Hi ๐ can you elaborate what you're referring to when you reference requiring permission?
That what I asked myself when I read the documentation attached to the link. It does not specify what permission means. ๐
btw, we are not doing off-session payments
but still have to go through no-payment-authentication
Ah, apologies, I didn't realize your link was directly to the referenced text. Thank you for that!
So this is referring to putting a section of text on your site notifying customers that you intend to charge their payment methods without action from them, to collect their permission to do so, and to set expectations around frequency.
It ends with "...when theyโre not actively using your website or app", and if you're doing on-session payments then the customer should be on your site/app and this might not be necessary. However, I'm not a legal expert and you should confirm whether a warning/agreement is necessary with your legal advisor.
Thank you @pastel bolt
Got another quick question:
What happens if i disable the rule: "Request 3DS if 3DS is required for the card"?
Your integrations will stop prompting for 3DS authentication when it's required for a card, and those payments will fail to process.
I would recommend that you don't disable that.
Any time! I hope you do the same ๐
Sorry got one last question.
"If 3D Secure requests are disabled for all cards, does the payment still go through? "
If the issuing bank requires 3DS be completed for a particular transaction and 3DS has been disabled, then that payment will be rejected and fail to process.
Awesome. Thanks a lot!