#nuven_docs
alpine folioBOT
👋 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/1225116894609150073
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
trim cliffBOT
novel cradle
Hello! The Your platform can no longer access the account condition happens when the connected account is disconnected from your platform. The account has been rejected happens when the account is rejected by Stripe, usually because it's violating our terms of service in some way.
You can listen for account.application.deauthorized Events to know when a connected account is disconnected from your platform: https://docs.stripe.com/api/events/types#event_types-account.application.deauthorized
And account.updated to see when things on the Account itself change, like capabilities and whatnot: https://docs.stripe.com/api/events/types#event_types-account.updated
devout gale
Ok, that is good to know. I guess I am trying to figure out is it possible to have these cases occur before the user finishes the connected account setup? The way we are displaying the stripe hosted page in our mobile app, there is no way for the user to refresh the page, as we do not want them to. I am trying to figure out if we can avoid using the refresh url, and still know all of these cases have happened
Every time they will be redirected to the stripe hosted page from within our mobile app, a new account link url will be created
novel cradle
Hm. I think it's technically possible for someone to go through part of onboarding, drop off, then get rejected based on the info they provided, but I don't know for certain. That's a better question for Stripe support than here.
devout gale
hmm i see, yes that does make sense. So what happens when the account is rejected while they are within the stripe hosted page, will stripe bring them to a page telling them their account has been rejected?
I am just trying to understand what the user experience will be
novel cradle
I don't think you'd be able to create an Account Link for them at that point, the attempt would likely fail with an error about the Account no longer being valid.
devout gale
ahhh ok. I know this is a big what if scenario, but what is they go through part of the onboarding, drop off, then come back, and while they come back, stripe rejects their info and account while they are currently viewing the onboarding pages. Is that something that can happen, and if so, how do I handle that
novel cradle
I don't know what would happen in that scenario. I think they would start to see errors while they were interacting with the onboarding process, and you would get one of the Events I mentioned above.
If you've successfully created an Account Link for them and sent them to it you don't generally need to worry about what happens during onboarding itself as Stripe handles that part.
devout gale
Ok, as long as the account link generation process can give me an error message or status like you mentioned, that will probably be good enough
since we are generating the account link url every time we want to onboarding them, even if they haven't finished onboarding
novel cradle
Yep, that sounds like the right approach.
devout gale
Ok great. My last question is this. Is there a way to ignore the refresh url, or make it not required somehow?
because we won't be using it
novel cradle
It's not optional, no, and it's not up to you if it gets used or not. It's for Stripe to use in various scenarios. You should create a URL that behaves as outlined here: https://docs.stripe.com/api/account_links/create#create_account_link-refresh_url
devout gale
I understand what's mentioned in the documentation, i was just trying to avoid having to create an end point for the refresh url since we are not handling that information. Seems regardless we need to give stripe a url for it to go too.
novel cradle
Yep, it's a required fallback.
devout gale
Ok, I have some things to think about. I appreciate your help and answering my questions. Thanks 🙂