aj_api | Stripe Developers | Page 1

sharp oarBOT Mar 7, 2025, 1:40 AM

#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1347383475455529032

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

aj_3ds-cloned-payment-methods, 7 hours ago, 52 messages

#

tiny sleet Mar 7, 2025, 1:48 AM

#

Hi, I see you had a conversation today and my colleague suggested the use of 3DS Radar rule. Did that help? Is this a different issue?

potent linden Mar 7, 2025, 1:51 AM

#

this is a different issue

#

that was for a different workflow..this is for migrating existing subscriptions

#

we are currently in the process of moving our European customers from our platform to connect account. One part is new subscriptions and the other part is moving existing subscriptions

#

we are now running into issues with the second part. That is, we already have active subscriptions in our platform account and we clone the payment method to connect account, create a customer and attach it to them and create a new subscription to mirror the existing one and if successful the platform one would be marked as canceled. The same payment method seems to be working as expected in platform but when cloned into our connect account its requesting extra auth

tiny sleet Mar 7, 2025, 2:04 AM

#

Which country is your Platform and your Connected Account which you cloned to?

potent linden Mar 7, 2025, 2:05 AM

#

Platform account is US and connected account is UK

#

the payment methods we are shifting should be in UK or EU

tiny sleet Mar 7, 2025, 2:07 AM

#

Yes so that's the point. UK and Europe has SCA, which is not required on US. So the original PM might be successful on US account and the cloned PM inherit that setup, it's still not enough to fulfill SCA, and will need to be authenticated once again

potent linden Mar 7, 2025, 2:08 AM

#

will it be the same case if Stripe migrates these customers for us from platform to connect?

tiny sleet Mar 7, 2025, 2:08 AM

#

There could be other similar scenarios as well, and I recommend to be ready to re-authenticate anyway, when you received an authenticate error on the cloned PM

#

Yep

#

It needs the customer consensus

potent linden Mar 7, 2025, 2:09 AM

#

the problem with re authenticating is that we do not have a workflow to support it and these are very old customers 😦

#

is this the case for all payments or is it decided by the issuing bank/card?

#

also will this be the case for new charges since we tokenize in platform and then transfer to connect?

tiny sleet Mar 7, 2025, 2:11 AM

#

It's common for all payment cloned from non-Europe account to Europe account, and then after that, the issuing bank still hold the decision to further request 3DS if they need/want to

#

By "transfer to connect" do you mean cloning?

potent linden Mar 7, 2025, 2:14 AM

#

yep

#

one thing I'm trying to confirm is in the platform account the same cards issued by European banks don't have issues whereas when cloned and trying to create a charge in connect we run into extra auth issue

tiny sleet Mar 7, 2025, 2:30 AM

#

Yes, because the merchant country matter, that you should be regulated if you are an Europe entity

#

That's expected

#

And in the end, it's not extra auth "issue", it's the regulation enforcement required in different country. It could be even stricter in India or Brazil for example. We are living in a changing world.

#

As a merchant, you want to make sure your integration can handle such cases, not to reduce such cases. Those are not in your control, or Stripe control anyway

#

Hope that makes sense!

potent linden Mar 7, 2025, 2:33 AM

#

ok got it. Thanks a lot for the clarification

#aj_api