#codepapa-3ds
1 messages · Page 1 of 1 (latest)
Hello! Yep, generally you'll need to bring each customer/user on-session to provide payment details and handle any requested 3DS/auth by the issuer/bank
What about subscription services with hundreds of thousands of customers?
Why would that be any different in this instance?
There are instances where you can get an exception due to prior auth agreements: https://stripe.com/docs/strong-customer-authentication/previous-authorization-agreements
I just don't see how a company with say 50,000 subscribers is going to get each one manually to create a new subscription to go through 3DS2
You won't need to create a new subscription per se. You'd just be capturing new payment details, carrying out requested auth, and then attaching that new payment 'method' to the existing subscription
We have APIs and flows to facilitate this, but it's all hypothetical if your client isn't actually using Stripe
I will be moving them to Stripe, they only use it for the US site at the moment.
It's a frustrating process yes, but one that has been outlined for many years and been slowly rolling out for the past few
Appreciate your help.
So the client has subscriptions setup in WooCommerce, I am aiming to push subscriptions into Stripe in the new build.
Is it a complex process to shift the subscriptions in Stripe?
Well, 'it depends': what exactly you have currently, what you need from Stripe
There's details on migrating here: https://stripe.com/docs/security/data-migrations/imports
We can help facilitate moving payment data across so that you remain PCI compliant
But the subscriptions themselves would likely need to be re-created in Stripe using our APIs
Thanks appreciate it