#50an6xy06r6n_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1237117731204235274
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
As far as I am aware that shouldn't be an issue. Will test this myself. Did they describe exactly what error they are getting?
they're not being the most coherent tbh. We're asking for screenshots but we don't have anything yet
That screenshot is of the account dropdown for when multiple standard connect accounts are under the same email. Not strictly relevant for Standard+Custom on the same email I guess
yeah this is specifically for standard + custom
Sounds good, will see what I can find when testing
they seem to be saying that they can't even onboard
but it's very hard for us to test or verify that, since we don't have a separate custom platform
If it helps, here are the repro steps (as far as I can tell)
- Create a Custom account using address@email.com (and onboard/set up everything)
- Create a Standard account on a different platform, with address@email.com pre-filled
- Attempt to onboard to the Standard account
- ???
Lucky for you I have far to many platform test accounts. Still testing at the moment but will let you know what I can find
thanks!
Was just able to connect a custom, then standard account to two separate platforms in test mode
So this should be possible, I think we'd need to know more info on exactly what the user is running in to to troubleshoot further.
hmm ok. Let me know if you need anything from me. As I said, the customer hasn't been entirely clear about when they're having issues
I think I've tested as much as I can with the info at hand. You can ask the user to reach out to our support team if you think they'd have better luck talking to us directly. https://support.stripe.com/?contact=true
Though that only works if they have some type of standard connect account already. Otherwise they can start an email with our support team at
https://support.stripe.com/contact/email
Hmmm ok so it works as far as you can tell?
I guess as a follow up, is there any way for us to change the email on a connect standard account after it's been created?
Correct, as far as I can tell there is no restriction on this. Yep, you can update via the API https://docs.stripe.com/api/accounts/update#update_account-email
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Thanks! As a follow-up question, can you explain how much information is shared between Connect accounts that share an email address? Is it just the login credentials? Or are there any business/account details shared? As I said, I haven't really been able to find Connect documentation addressing this, but customers frequently get confused when they're asked to log into an existing account during the onboarding flow
Good question. I am not immediately sure but will ask my colleagues. Basically we used to let accounts connect to multiple platforms but that is not possible anymore (at least by default), so when a user signs up for a Standard Connect platform with an email associated with and existing Standard account, we create a new account that then connects to the platform instead. Finding out with my colleagues exactly what info is copied over to the new account.
It looks like it is only the login credentials, the user will still need to supply their info again
Thanks, that makes sense