ariandr_ios-migration | Stripe Developers | Page 1

dapper irisBOT Oct 28, 2024, 5:50 PM

#

👋 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/1300516944989917195

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

#

devout hedge Oct 28, 2024, 5:51 PM

#

@desert violet I'm fairly certain this flow is impossible with that newer integration sadly. You will have to basically split it into 2 separate flows

Collect card details on the platform with a SetupIntent
Once done, clone the card to the connected account and then use a PaymentIntent and confirm it with the saved card

#

ariandr_ios-migration

#

backend shares this payment method to a connected account and puts the shared one inside the payment intent
this flow is not possible because you are changing the accounts involved in that flow so you can't do that flow

desert violet Oct 28, 2024, 5:54 PM

#

@devout hedge
So, it's just the limitation of the new iOS SDK?
Because on the server side it works perfectly well and if there is no 3DSecure, the payment succeeds, just the iOS shows the error.

devout hedge Oct 28, 2024, 5:55 PM

#

yes the SDK doesn't support a flow like this because there's a mismatch between the info you configured (platform details) and the PaymentIntent being on the connected account

desert violet Oct 28, 2024, 5:57 PM

#

Okay, what would we need to do if we already have thousands of customers with saved payment methods on on the Main Platform account and we want to share the payment methods during the payment to the Connected accounts?

#

So that it works with iOS SDK

#

@devout hedge

devout hedge Oct 28, 2024, 5:58 PM

#

@desert violet I don't think there's any flow that can work that way unless you build your own UI to show the saved payment methods yourself first. We don't have this logic in our SDK that I know of.

desert violet Oct 28, 2024, 6:07 PM

#

@devout hedge
Well, PaymentSheet.FlowController already shows saved payment methods. When we select, it just provides a payment method id and we try to confirm the payment.

We select them, send to the server and if it succeeds without 3DSecure, it's already paid and done, just the app shows the error.

I believe it's a pretty common use case that you want to use the customer from the Main Platform, get their saved payment method and then the customer can pay for many different businesses (using connect). In our case it's booking in different sports clubs, like Pilates, Yoga.

If we don't save payment methods on our Main Platform, the user will have to enter the new cards every time for every new sports club. It's like Aorbnb or Booking type of thing.

devout hedge Oct 28, 2024, 6:09 PM

#

Well, PaymentSheet.FlowController already shows saved payment methods
sure, because you configure it with a Customer from the platform as if you are going to do something on the platform itself. But you don't, you clone that PaymentMethod and use a completely different object (that cloned version) on a different account (the connected account) which the iOS SDK doesn't really support today
I don't disagree it'd be a cool feature request but I'm fairly confident it doesn't work today. And it's not that common as a use-case

desert violet Oct 28, 2024, 6:13 PM

#

@devout hedge
Okay, thanks. Can you create a feature request for this on your side?

Also a question, if we don't migrate and stay on Basic Integration, what window of support can we expect?

Because now it would be impossible to break our business just to migrate.

devout hedge Oct 28, 2024, 6:14 PM

#

We won't turn off the old feature, but it will be removed from our newer versions of our SDKs so you'll basically be "stuck" until you upgrade

desert violet Oct 28, 2024, 6:16 PM

#

@devout hedge
I mean is it reasonable to expect that next year, when iOS 19 is released, if there is a crash in the old SDK that supports Basic Integration, the team will fix it and provide a release for the old SDK?

devout hedge Oct 28, 2024, 6:17 PM

#

That seems unlikely no. It's possible, we have made exceptions like this occasionally over the years but it's extremely rare and we expect all developers to migrate.

I think at this point, your best approach is to reach out to our support team to discuss this: https://support.stripe.com/contact and they can work with you on a path forward

#

But my take is that we wouldn't support this at all unfortunately. It'd be the same if you used Stripe.js and PaymentElement with saved PaymentMethods. We don't support your flow

#

So your best bet in my eyes is to build your own UI for showing saved PaymentMethods if you want to let the end customer pick the one(s) from the platform

desert violet Oct 28, 2024, 6:21 PM

#

Okay.

But if we build the UI to pick the PaymentMethods from our Main platform, how do we trigger the payment itself?

#

Now we use:
paymentSheetFlowController.confirm

#

@devout hedge

devout hedge Oct 28, 2024, 6:27 PM

#

looking

#

Okay someone on my team said this:

use https://stripe.dev/stripe-ios/stripepayments/documentation/stripepayments/stpapiclient/confirmpaymentintent(with:completion:)

You would have configured PaymentIntent params with the selected Payment Method ID from your UI - https://stripe.dev/stripe-ios/stripepayments/documentation/stripepayments/stppaymentintentparams

This all assumes that you initialized/configured the SDK with the right connected account information at that point

#ariandr_ios-migration