#gadbit-connect-rejection
1 messages · Page 1 of 1 (latest)
how can i help?
When a Standard Account tries to connect with my platform in order to receive payments online, how many days it last to get an answer from Stripe to know if its enabled to receive payments through my app?
I recommend checking in with our support team about this: https://support.stripe.com/?contact=true
OK, so at programming level, i have another question, can i have a listener when a connected account is rejected or its only available for status change?
https://stripe.com/docs/connect/webhooks explains how Events and Webhooks work with Connect, so yes you can listen to account.updated for this
gadbit-connect-rejection
OK, so i have another question, since it's possible that a connected account was already registered on Stripe (so it's enabled to receive payments), but also it's possible that a connected account is not registed on Stripe yet. So, the second one needs to create an account filling the form, but its info need to be reviewed
So, what's the default state for those accounts?
First case (already registered account), Second case (not registered account).
Sorry I don't really understand what you're getting after. What you should do is look at charges_enabled, payouts_enabled and requirements
But... All the accounts has charges_enabled and payouts_enabled false by default even when the account was already registered in Stripe before and has charges_enabled true with another Connected Account?
I ask that question since i need to know that charges_enabled field will be updated at least once for every new connected account, since i will be listening the account.updated event, to change a field in my database.