# Boarding statuses reference

> Track merchant boarding progress with complete status and substatus reference. Understand application review, underwriting, approval, and decline stages with API status codes

## Statuses

These are the available boarding status values. The Key column contains the status code returned by the API.

<div id="boarding-status">
  <table>
    <thead>
      <tr>
        <th>
          Value
        </th>

        <th>
          Key
        </th>

        <th>
          Description
        </th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>
          Not Submitted
        </td>

        <td>
          -99
        </td>

        <td>
          The application is incomplete or hasn't been submitted yet.
        </td>
      </tr>

      <tr>
        <td>
          Declined
        </td>

        <td>
          0
        </td>

        <td>
          The application has been declined.
        </td>
      </tr>

      <tr>
        <td>
          Pending Signature
        </td>

        <td>
          2
        </td>

        <td>
          The application is waiting on the applicant's signature.
        </td>
      </tr>

      <tr>
        <td>
          Underwriting
        </td>

        <td>
          3
        </td>

        <td>
          The application is in underwriting.
        </td>
      </tr>

      <tr>
        <td>
          Submitted
        </td>

        <td>
          4
        </td>

        <td>
          The application is complete and submitted, but hasn't moved to underwriting yet.
        </td>
      </tr>

      <tr>
        <td>
          Manual Review
        </td>

        <td>
          6
        </td>

        <td>
          The application is in underwriting and requires further review.
        </td>
      </tr>

      <tr>
        <td>
          Approved
        </td>

        <td>
          7
        </td>

        <td>
          The application has been approved and is queued for boarding.
        </td>
      </tr>

      <tr>
        <td>
          Withdrawn
        </td>

        <td>
          8
        </td>

        <td>
          The applicant has voluntarily withdrawn their application.
        </td>
      </tr>

      <tr>
        <td>
          Boarding
        </td>

        <td>
          10
        </td>

        <td>
          The application is boarding with our service providers, banks, and Payabli.
        </td>
      </tr>

      <tr>
        <td>
          Activated
        </td>

        <td>
          99
        </td>

        <td>
          The paypoint has been created, and all configurations have been completed, but the paypoint hasn't processed a transaction yet.
        </td>
      </tr>

      <tr>
        <td>
          Live
        </td>

        <td>
          100
        </td>

        <td>
          The paypoint has successfully processed a pay in or pay out transaction.
        </td>
      </tr>

      <tr>
        <td>
          Exception Error
        </td>

        <td>
          -1
        </td>

        <td>
          An unidentified error has occurred with this application. Contact support to review.
        </td>
      </tr>
    </tbody>
  </table>
</div>

## Substatuses

Some statuses have substatuses to give you more information about where an application is in the process.

### Manual Review substatus

These statuses may appear when an application is in the Manual Review (6) status. The Key column contains the status code returned by the API.

<div id="manual-review-substatus">
  <table>
    <thead>
      <tr>
        <th>
          Value
        </th>

        <th>
          Key
        </th>

        <th>
          Description
        </th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>
          Pending Review
        </td>

        <td>
          1
        </td>

        <td>
          The application was flagged during underwriting and is waiting on manual review.
        </td>
      </tr>

      <tr>
        <td>
          Pending Documentation
        </td>

        <td>
          2
        </td>

        <td>
          The reviewer has requested additional documents from the applicant or org.
        </td>
      </tr>

      <tr>
        <td>
          Pending Action
        </td>

        <td>
          3
        </td>

        <td>
          An additional task has been requested from the applicant or org.
        </td>
      </tr>

      <tr>
        <td>
          Missing Data
        </td>

        <td>
          4
        </td>

        <td>
          The application needs additional data to complete underwriting.
        </td>
      </tr>
    </tbody>
  </table>
</div>

### Boarding substatus

These statuses may appear when a merchant is in the Boarding (10) status. The Key column contains the status code returned by the API.

<div id="boarding-enablement-substatus">
  <table>
    <thead>
      <tr>
        <th>
          Value
        </th>

        <th>
          Key
        </th>

        <th>
          Description
        </th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>
          ServiceProvider Review
        </td>

        <td>
          5
        </td>

        <td>
          The application was submitted to service provider for review, validation, and boarding.
        </td>
      </tr>

      <tr>
        <td>
          ServiceProvider Processing
        </td>

        <td>
          6
        </td>

        <td>
          The application is processing and waiting on final results.
        </td>
      </tr>

      <tr>
        <td>
          ServiceProvider Hold
        </td>

        <td>
          7
        </td>

        <td>
          The service provider requires additional information or a correction from the applicant, org, or Payabli.
        </td>
      </tr>

      <tr>
        <td>
          Pending Configuration
        </td>

        <td>
          8
        </td>

        <td>
          The paypoint has been created and is waiting on configuration and activation.
        </td>
      </tr>
    </tbody>
  </table>
</div>

### Declined substatus

These substatuses may appear when an application has a Declined status (0). The Key column contains the status code returned by the API.

<div id="boarding-declined-substatus">
  <table>
    <thead>
      <tr>
        <th>
          Value
        </th>

        <th>
          Key
        </th>

        <th>
          Description
        </th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>
          Standard Decline
        </td>

        <td>
          9
        </td>

        <td>
          The application has been declined for a reason. The reason is provided in the status text.
        </td>
      </tr>

      <tr>
        <td>
          Credit Decline
        </td>

        <td>
          10
        </td>

        <td>
          The application has been declined for a reason. The reason is provided in the status text.
        </td>
      </tr>
    </tbody>
  </table>
</div>

## Related resources

See these related resources to help you get the most out of Payabli.

<AccordionGroup>
  <Accordion title="References">
    * **[Paypoint statuses](/guides/pay-ops-paypoint-status-reference)** - Learn about the different statuses of paypoints
    * **[Pay In TransEvent reference](/guides/pay-in-transevents-reference)** - Learn about TransEvent values for pay in transactions
  </Accordion>

  <Accordion title="Related topics">
    * **[Board merchants](/guides/pay-ops-boarding-overview)** - Learn how boarding merchants works
    * **[Manage boarding in the UI](/guides/pay-ops-portal-boarding-manage)** - Learn how to manage the boarding process for paypoints in the Payabli UI
  </Accordion>
</AccordionGroup>