#nguyenxuanloc
1 messages · Page 1 of 1 (latest)
The banks could request 3DS/auth on subsequent recurring payments, yes. Our integrations/APIs do make the necessary steps to try and prevent that but it can still happen
so we need to handle this case, right. I'm following this document: https://stripe.com/docs/billing/migration/strong-customer-authentication#scenario-3
Can you share more docs about your pre-built-tools
What specifically?
You can configure emails to be sent to customers if/when recurring payments require 3DS: https://stripe.com/docs/billing/revenue-recovery/customer-emails#secure-payments
That will facilitate collecting authentication on that payment. Alternatively, you can build that flow yourself by bringing the user back on-session to re-confirm the payment
Looks about right, yep
Thank you, sir