> ## Documentation Index
> Fetch the complete documentation index at: https://docs.y.uno/llms.txt
> Use this file to discover all available pages before exploring further.

# Onboarding Statuses

Onboarding tracks the lifecycle of recipient (submerchant) registration with providers for split payments. Use the onboarding `status` to understand where a recipient is in the process and whether any action is required.

See also:

* [Create Onboarding](/reference/create-onboarding)
* [Continue Onboarding](/reference/continue-onboarding)

## Onboarding statuses

The onboarding flow can have the following statuses.

<table>
  <thead>
    <tr>
      <th>Status</th>
      <th>Description</th>
      <th>Required action</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td class="status"><code>CREATED</code></td>
      <td>Initial record created; validation hasn’t started (often transitions quickly to <code>PENDING</code>).</td>
      <td class="action">Ensure all required data and documents are provided; otherwise wait for review to start.</td>
    </tr>

    <tr>
      <td class="status"><code>PENDING</code></td>
      <td>Under review by Yuno and/or the provider.</td>
      <td class="action">No action required.</td>
    </tr>

    <tr>
      <td class="status"><code>PENDING\_ADDITIONAL\_DOCUMENTATION</code></td>
      <td>More documentation or clarifications required.</td>
      <td class="action">Upload the requested documents and resubmit.</td>
    </tr>

    <tr>
      <td class="status"><code>PENDING\_RECIPIENT\_ACTION</code></td>
      <td>Recipient must complete steps (e.g., accept terms, KYC, verification).</td>
      <td class="action">Complete the pending step(s) and continue.</td>
    </tr>

    <tr>
      <td class="status"><code>SUCCEEDED</code></td>
      <td>Onboarding completed successfully; recipient is ready for split payouts.</td>
      <td class="action">Start using the recipient in splits/payouts.</td>
    </tr>

    <tr>
      <td class="status"><code>FAILED</code></td>
      <td>Processing failed; the onboarding was not approved.</td>
      <td class="action">Review the reason and retry or create a new onboarding after fixing issues.</td>
    </tr>

    <tr>
      <td class="status"><code>DECLINED</code></td>
      <td>Provider reviewed and declined the onboarding.</td>
      <td class="action">Update information or documentation, then create a new onboarding.</td>
    </tr>

    <tr>
      <td class="status"><code>BLOCKED</code></td>
      <td>Temporarily blocked due to risk/compliance policy or review.</td>
      <td class="action">Unblock via the corresponding endpoint or contact support.</td>
    </tr>

    <tr>
      <td class="status"><code>REJECTED</code></td>
      <td>Pre-submission validation failed before reaching the provider.</td>
      <td class="action">Fix the issues and retry/submit again.</td>
    </tr>

    <tr>
      <td class="status"><code>ERROR</code></td>
      <td>Transient processing error (e.g., timeout or connectivity).</td>
      <td class="action">Retry the operation; contact support if it persists.</td>
    </tr>

    <tr>
      <td class="status"><code>CANCELLED</code></td>
      <td>Onboarding was cancelled by the merchant/recipient or automatically due to workflow.</td>
      <td class="action">Create a new onboarding when ready.</td>
    </tr>

    <tr>
      <td class="status"><code>EXPIRED</code></td>
      <td>Not completed in time; window expired.</td>
      <td class="action">Restart by creating a new onboarding.</td>
    </tr>
  </tbody>
</table>