#abcd_15536

1 messages · Page 1 of 1 (latest)

finite lavaBOT
tacit inlet
#

Hello! No the user needs to complete the onboarding/verifiation flow to be conncted to your platform

random tusk
#

Suppose a user has created a Stripe account through our Software/System. We want to restrict the user from enabling or disabling Stripe account settings so that our system is not affected. Onboarding should still be possible, but after onboarding, the user should be restricted from making any changes to Stripe.
Is it Possible ?

tacit inlet
#

What kind of accounts are you creating?

random tusk
#

Custom Account

tacit inlet
#

We want to restrict the user from enabling or disabling Stripe account settings so that our system is not affected
You need to elaborate on what you mean by this. If you're using custom accounts then you control the entire experience and can limit users in whatever way you want

random tusk
#

yes

tacit inlet
#

What does 'yes' mean? You need to help me by explainin what it is you want to control/limit

random tusk
#

Control user limit so that he cannot disable or enable account. Not able to change password.

tacit inlet
#

Not able to change password
You can't prevent that I'm afraid

Equally users can't manually enable/disable accounts, but accounts may become restricted/disabled depending on verification requirements. Your application needs to account for that and handle such scenarios: https://stripe.com/docs/connect/handling-api-verification

Learn how Connect platforms can use webhooks and the API to handle verification of connected accounts.