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

# Application states

> Reference for all application statuses and their transitions

## Application statuses

| Status                         | Description                                                                  |
| ------------------------------ | ---------------------------------------------------------------------------- |
| `DRAFT`                        | Created but not yet submitted. Data can be added, updated, or deleted.       |
| `SUBMITTED`                    | Submitted for review. No modifications allowed.                              |
| `IN_REVIEW`                    | Compliance review in progress (automated and manual checks).                 |
| `PENDING_CUSTOMER_INFORMATION` | One or more RFIs issued. Partner must update data or documents and resubmit. |
| `APPROVED`                     | Approved. Terminal state.                                                    |
| `DENIED`                       | Denied. Terminal state.                                                      |
| `CANCELLED`                    | Canceled by the partner. Terminal state. Only reachable from `DRAFT`.        |

## Status transitions

```mermaid theme={null}
flowchart LR
    DRAFT --> SUBMITTED
    DRAFT --> CANCELLED
    SUBMITTED --> IN_REVIEW
    IN_REVIEW --> PENDING_CUSTOMER_INFORMATION
    PENDING_CUSTOMER_INFORMATION --> SUBMITTED
    IN_REVIEW --> APPROVED
    IN_REVIEW --> DENIED
```

See
[Submit and track applications](/cpn/managed-payments/end-user-onboarding/howtos/submit-and-track-applications)
for the submission and RFI workflow.

## Mutable vs. immutable states

Partners can only modify application data (sections, documents) in these states:

* **`DRAFT`**: Initial state after creation. Full read/write access.
* **`PENDING_CUSTOMER_INFORMATION`**: RFIs issued. Partners can update the
  sections and documents referenced by the RFIs, then resubmit.

All other states are immutable. API calls that attempt to modify data return a
`409 Conflict` error.

Saving section data in mutable states may trigger conditional changes. See
[Conditional logic](/cpn/managed-payments/end-user-onboarding/concepts/conditional-logic)
for details.

## Section statuses

Each section in an application has its own status that tracks data completeness:

| Status            | Description                                           |
| ----------------- | ----------------------------------------------------- |
| `not_started`     | No data saved for this section                        |
| `incomplete`      | Some data saved but required fields are missing       |
| `complete`        | All required fields are populated and valid           |
| `action_required` | An RFI targets a field in this section; update needed |

<Note>
  Terminal states (`APPROVED`, `DENIED`, `CANCELLED`) are final. Applications
  cannot transition out of these states.
</Note>