> This is Payabli documentation. For a complete page index, fetch https://docs.payabli.com/llms.txt — append .md to any page URL for lightweight markdown. For section-level indexes, query parameters, and other AI-optimized access methods, see https://docs.payabli.com/ai-agents.md # Boarding application statuses > Learn about the statuses a boarding application moves through and what moves it from one status to the next > **Note** > > Intelligent boarding is in beta. To opt in, reach out to your Payabli contact. A boarding application moves through a series of statuses, from the moment it's created until its requested services are live. Application responses return the status as a lowercase name in `applicationStatus` and as a number in `applicationStatusCode`. Responses from lifecycle actions, such as submitting or withdrawing an application, return the new `applicationStatus`. For how applications relate to businesses, people, templates, and paypoints, see the [Intelligent boarding overview](/guides/pay-ops-boarding-object-model-overview). ## Application statuses The Status column contains the value of `applicationStatus`, and the Code column contains the value of `applicationStatusCode`. | Status | Code | Meaning | | ------------------ | ---- | --------------------------------------------------------------------------------------------------------------------------- | | `draft` | 1 | Created but not yet submitted. This is the only status where you can update the application. | | `submitted` | 2 | Submitted with the signature of record. Verification starts automatically. | | `verifying` | 3 | Automated verification is running. | | `pendingreview` | 4 | Waiting for underwriting review. | | `escalatedreview` | 5 | Escalated to a higher underwriting review tier. | | `pendingdocuments` | 6 | Underwriting requested documents. The application waits for the applicant to provide them, then returns to `pendingreview`. | | `pendingresponse` | 7 | Underwriting asked a question. The application waits for the applicant to answer, then returns to `pendingreview`. | | `approved` | 8 | Approved. The requested services are being enabled. | | `autoapproved` | 9 | Approved automatically, without manual review. | | `denied` | 10 | Denied. This is a final status. | | `withdrawn` | 11 | Withdrawn. This is a final status. | | `abandoned` | 12 | Reserved. No action moves an application to this status. | | `error` | 13 | Processing hit an error. Payabli can recover the application, which returns it to the status it had before the error. | | `activated` | 14 | The requested services are provisioned and live. This is a final status. | ## How an application moves between statuses Three kinds of actors move an application from one status to the next: * **You**: your integration calls a lifecycle endpoint. * **Payabli or Enterprise Partner**: Payabli's underwriting team, or an Enterprise Partner's, acts on the application. * **Automatic**: Payabli's systems move the application without anyone acting on it. | From | To | What moves it | Who acts | | ----------------------------------------------------------------------------------------------------- | --------------------------- | ------------------------------------------------------------ | ----------------------------- | | `none` | `draft` | The application is created. | You | | `draft` | `submitted` | The application is submitted. | You | | `submitted` | `verifying` | Automated verification starts. | Automatic | | `verifying` | `pendingreview` | Verification routes the application to manual review. | Automatic | | `verifying` | `autoapproved` | Verification approves the application without manual review. | Automatic | | `pendingreview` | `escalatedreview` | The application is escalated to a higher review tier. | Payabli or Enterprise Partner | | `pendingreview` or `escalatedreview` | `pendingdocuments` | Underwriting requests documents. | Payabli or Enterprise Partner | | `pendingreview` or `escalatedreview` | `pendingresponse` | Underwriting asks a question. | Payabli or Enterprise Partner | | `pendingdocuments` | `pendingreview` | The requested documents are provided. | You | | `pendingresponse` | `pendingreview` | The requested information is provided. | You | | `pendingreview` or `escalatedreview` | `approved` | Underwriting approves the application. | Payabli or Enterprise Partner | | `pendingreview` or `escalatedreview` | `denied` | Underwriting denies the application. | Payabli or Enterprise Partner | | `approved` or `autoapproved` | `activated` | All the requested services are boarded. | Automatic | | `draft`, `submitted`, `pendingdocuments`, or `pendingresponse` | `withdrawn` | The application is withdrawn. | You | | `submitted`, `pendingreview`, `escalatedreview`, `pendingdocuments`, `pendingresponse`, or `approved` | `error` | Processing fails. | Automatic | | `error` | The status before the error | Payabli recovers the application. | Payabli | An application in `denied`, `withdrawn`, or `activated` doesn't change status again. ## Check which actions are allowed Application responses and lifecycle action responses include an `allowedActions` array that lists the actions available in the application's current status. The array can include actions that Payabli or its systems perform, which you can't call through the API. These are actions, not statuses. For example, `provideDocuments` is how you respond when an application is in `pendingdocuments`. Check for one of these values before you call the matching endpoint: | Allowed action | Allowed in | What it does | | ------------------ | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | `submit` | `draft` | Submits the application for review. | | `withdraw` | `draft`, `submitted`, `pendingdocuments`, `pendingresponse` | Withdraws the application. See [Withdraw an application](/developers/api-reference/applications/withdraw-an-application). | | `provideDocuments` | `pendingdocuments` | Provides the documents that underwriting requested. The application returns to `pendingreview`. | | `provideResponse` | `pendingresponse` | Provides the information that underwriting requested. The application returns to `pendingreview`. | ## Track status changes To see how an application reached its current status, use [Get application status history](/developers/api-reference/applications/get-application-status-history). The response lists every transition, oldest first, with the `fromStatus`, `toStatus`, what triggered the change, and any reason recorded with it. The transition that creates the application has a `fromStatus` of `none`. ## Related resources See these related resources to help you get the most out of Payabli. #### Related topics * **[Intelligent boarding overview](/guides/pay-ops-boarding-object-model-overview)** - Understand the objects and application lifecycle behind intelligent boarding paypoints on Payabli * **[Manage boarding templates with the API](/guides/pay-ops-developer-templates-manage)** - Learn how to list, read, update, and archive boarding templates with the Payabli API * **[Manage applications with the API](/guides/pay-ops-developer-applications-manage)** - Learn how to create, submit, and track boarding applications with the Payabli API