#alok_kumar71
winter oxideBOT
Hello! We'll be with you shortly. 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.
- alok_kumar71, 1 day ago, 3 messages
- alok_kumar71, 3 days ago, 7 messages
fossil geode
How are you migrating exactly? Can you link the doc you're referencing?
warm forge
First creating a payment method on the connected account using the setup intent customer object and setup intent payment method.
Then, using the payment method of connected account I'm creating a customer on connected account
fossil geode
The auth would be carried over. However, some banks might still require 3ds in the future for that payment method. This would be true even if you didn't clone the payment method
Sometimes banks will require 3ds auth for recurring transactions later on. We have no way of knowing when/if it'll happen
warm forge
Actually I'm creating setup intent and then creating payment intent on multiple connected account, I don't want user to perform 3ds2 auth again n again, since user would have already performed 3ds2 auth during setup intent. So is there efficient solutions to achieve this?
fossil geode
You're creating setup intent on platform then cloning the customer and payment method to the connect account? If so that's the most efficient
warm forge
Right, but while confirming the payment intent it's either returning require_action or authentication_required.
Even though user already performed 3ds2 auth during setup intent confirmation
fossil geode
Ah yeah that should carry authentication over
Can you share the setupintent id on the platform, the payment method id on the connect account, and the payment intent id on the connect account where you're still getting authentication required?
Also how often is 3ds required after cloning?
Do you see this in every case?
warm forge
Platform Customer ID: cus_P6lZK4bIzYLthH
Platform SetupIntent ID: seti_1OIY2qLsRZKIA2Z6E3tje4ge
Connected Account Customer ID: cus_P6lbRij107juhO
Connected Account PaymentIntent ID: pi_3OIY4fGk7t9ea3NQ1zVYoMRv
I'm using this test card: 4000000000003220
Yes I see this 3ds2 auth everytime when I confirm the intent
Either at starting on setup intent confirmation or later payment intent confirmation
@fossil geode
fossil geode
In many threads
Please be patient
Oh you're in test mode
The 3220 card will always require 3ds no matter what
Even if set up with a setupintent
You want this card: 4000002500003155
But, can the scenario happen in real time which is happening with a 3220 card? Is it a legit scenario?
fossil geode
Yep it's possible
And there's no way to avoid it
Sometimes a bank will require 3ds even if you used a setupintnt
That's up to the bank
warm forge
Ohh! Ok.
Thanks for responding. That was helpful