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

# Order States

> Order states explained. Order lifecycle state-machine diagram.

In the figure below, the order states are represented in a state-machine diagram, with the actions that trigger each state transition.

```mermaid theme={null}
stateDiagram-v2
    %% --- states declared explicitly so we can style them ---
    state Start
    state End
    state Created
    state Fulfilled
    state SentUnlock
    state ClaimedUnlock
    state OrderCancelled
    state SentOrderCancelled
    state ClaimedOrderCancel

    %% --- initial entry ---
    [*] --> Start

    %% --- transitions from Start / Created ---
    Start --> Created : Order Created on Source Chain
    Created --> Fulfilled : Order Fulfilled on Destination Chain
    Created --> OrderCancelled : Order Cancelled on Destination Chain

    %% --- fulfilled path ---
    Fulfilled --> SentUnlock : Cross-Chain Message Sent
    SentUnlock --> ClaimedUnlock : Order Claimed by Solver
    ClaimedUnlock --> End

    %% --- cancelled path ---
    OrderCancelled --> SentOrderCancelled : Cross-Chain Message Sent
    SentOrderCancelled --> ClaimedOrderCancel : Order Claimed on Source Chain
    ClaimedOrderCancel --> End

    %% --- styling for Start / End nodes ---
    style Start fill:#90EE90,stroke:#333,stroke-width:1px,color:#000
    style End   fill:#FF6347,stroke:#333,stroke-width:1px,color:#fff

```

According to the DLN API, an order must be in one of these states:

| State | Description |
| - | - |
| **Created** | An order placed by a user on the DLN is pending fulfillment. |
| **Fulfilled** | The order on the destination chain has been completed by a solver. The full amount of the requested assets has been successfully transferred to the `dstChainTokenOutRecipient`. |
| **SentUnlock** | After fulfilling the order, the solver initiates the unlock procedure on the destination chain. A cross-chain message is sent via DMP to unlock the input assets locked on the source chain. |
| **ClaimedUnlock** | The unlock process is finalized, and the solver receives the input assets. The affiliate fee is directed to the `affiliateFeeRecipient` on the source chain. |
| **OrderCancelled** | The `dstChainOrderAuthorityAddress` has started the cancellation process on the destination chain. |
| **SentOrderCancel** | A cross-chain message is sent via DMP from the destination to the source chain. It unlocks the input assets on the source chain to be claimed by the `srcAllowedCancelBeneficiary`. |
| **ClaimedOrderCancel** | The source chain input assets have been claimed by the `srcAllowedCancelBeneficiary`. The cancel procedure is finalized. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.