#bennn
1 messages · Page 1 of 1 (latest)
Do you mean when onboarding a Connect Account? Is there a Doc you are following?
These are the create SetupIntent docs I'm looking at: https://stripe.com/docs/api/setup_intents/create and these are the create account link docs I'm looking at: https://stripe.com/docs/api/account_links/create
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Specifically, in the create SetupIntent docs, it states: If you’d prefer to redirect to a mobile application, you can alternatively supply an application URI scheme. We need support for this when creating an account link
Have you tried setting it as a deeplink or an unniversal link/app link?
We're using Capacitor (https://capacitorjs.com/) which means the app has a default URI scheme of capacitor://localhost. The redirect works when creating a SetupIntent but returns a Not a valid URL message when linking an account.
I see, and yes it's expected since Account Link only works with Https urls
You would want to setup any configuration which results in Universal link in iOS and App Link in Android, which allow receiving HTTPS url and resolve to the url schemes above
Cool, thank you I'll take a look at that. Is there any plan to allow it to work with non-https links? I'm curious why the SetupIntent allows for non-https links but the AccountLink doesn't?
Not that a timeline I would be able to share at this time, sorry. I know that SetupIntent and PaymentIntent are designed to work broadly with payment integration, while Account Link is designed to work as an URL on browser in the first place