#tgiv014-setup-intents
warped oyster
Sure thing! Here's the ID of one of the setup intents in question: seti_1K6j0xHto8tsBwHr8ykDv5VC
Some more details: We're creating setup intents on connected accounts via the Stripe Go library. Customers enter payment info on a root Stripe account and payment methods are cloned to connected accounts for billing
covert apex
Is there a reason you have them go through a Setup Intent again after being cloned? It looks like you already create the Payment Method through a Setup Intent when you initially collect the information on the platform
warped oyster
That's correct. No reason for going through a secondary setup intent after cloning. I'm currently testing transitioning to adding mandate_data when cloning payment methods and want to confirm that mandates are generated as expected
My main concern is with ensuring that transactions which fall under SCA are correctly marked as Merchant-Initiated
covert apex
Give ma bit to dig in to some things - I need to refresh on mandates + cloning payment methods
warped oyster
Sounds good. Thanks for looking into it!
covert apex
So I think you're not seeing any mandate return because we don't populate mandate on the Setup Intent if it's for a card Payment Method. I can confirm that I do see a mandate for that Setup Intent on our end, it's just not being surfaced back to you
warped oyster
Ah okay that makes sense. Is it still advantageous to provide mandate_data when creating&confirming a setup intent? My suspicion based on https://stripe.com/guides/strong-customer-authentication#merchant-initiated-transactions-including-variable-subscriptions is yes, but I want to confirm
covert apex
I don't think it's necessary since it should be sharing the mandate that was collected before the cloning, but let me check
covert apex
Sorry for coming back to this so late! From what I can see on my end, when you clone the Payment Method to the connect account it should also clone the mandate, so you shouldn't need to create a new one.
warped oyster
No worries! I've been digging around a bit too. SCA led me down the 3DS rabbit hole - I noticed some wording on https://stripe.com/docs/strong-customer-authentication/connect-platforms#saving that indicates that permission (I'm assuming that's the mandate?) is cloned alongside the payment method. Does that include 3DS authentication for SCA? We don't currently have 3DS enabled on the root platform account and I'm wondering if that would be valuable for connected accounts in Europe that have to comply with SCA
covert apex
Yes, it would clone over the 3DS authentication as well if it was requested for the platform.
warped oyster
Great! I’ll look into enabling 3DS for our customer portal users