#xaositect_connect-risk-management

1 messages · Page 1 of 1 (latest)

wind mulchBOT
#

👋 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/1343627337496920066

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

vivid sinew
#

Hi 👋

We focus on coding integrations with Stripe APIs and are not as expert on Stripe policies and how they impact Connect Platform risk. However, I recommend you review this doc (and the sub-pages) to get a better undersanding: https://docs.stripe.com/connect/risk-management

#

You can also reach out to Support but I think it would be best to first review our public docs so you can get a better understanding of the larger picture of Platform risk.

ruby radish
#

Thanks, I'd never seen that document before

#

I regret that Support is so generally difficult to get useful information from, but I'll pursue that avenue.

vivid sinew
#

Yes I understand it can be difficult.

#

One way to try and improve the support experience is to include as much pertinent details as possible.

#

Include the public docs/support articles you have already reviewed, describe the steps you have already taken in your own research, and mention specific options like the settings in the controller hash. Include formatted snippets of code, if applicable.

#

this will help route your request to right team(s) more quickly