title: How to handle incomplete stripe connected account onboarding?
body: <p>I am after the best practice for handling incomplete stripe connected account onboarding.</p>
  <p>When onboarding goes smoothly, everything is simple. But there are fiddly edgecases everywhere, which results in a lot of permutations of values for account <a href="https://stripe.com/docs/api/accounts/object#account_object-requirements" rel="nofollow noreferrer"><code>requirements</code></a></p>
  <p>These include</p>
  <ul>
  <li><code>current_deadline</code></li>
  <li><code>currently_due</code></li>
  <li><code>disabled_reason</code></li>
  <li><code>errors</code></li>
  <li><code>eventually_due</code></li>
  <li><code>past_due</code></li>
  <li><code>pending_verification</code></li>
  </ul>
  <p>This creates a lot of complexity.</p>
  <p>I need a simple way to:</p>
  <ol>
  <li>figure out if the connected user needs to be notified of something (i.e. that they need to give more info), and</li>
  <li>what to tell them.</li>
  </ol>
  <p>My current strategy is to check if <code>errors</code> is empty, and if not, simply display them along with a link to manage the user's stripe account so they can address the errors.</p>
  <p>But I'm worried this strategy will miss things (perhaps minor things that could be addressed <em>before</em> they become errors).</p>
  <p><strong>TL;DR</strong> I suspect most users will onboard without any problem, but for the few who do have issues, I want to ensure the app notifies them that they need to address them. What is the best way to do this? (using the information in <code>requirements</code> or other info)</p>