> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/chord-oms-overview/subscriptions/subscription-states.md).

# Subscription States

## Subscription States

## Overview

This section of documentation outlines the different statuses a subscription can have throughout its lifecycle and explains what causes a subscription to move into each one.

A subscription's status is described by more than a single label:

* **State** captures where the subscription sits in its lifecycle (for example, active, paused, canceled, or ended)
* **Processing state** reflects the health of the most recent order and payment attempt

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-d759dbbc63e21fb0ef1ba8f099c0c588831cb390%2Fsubscription-states-1.png?alt=media)

These run independently of one another — so a subscription can be active while its latest charge shows as failed, for instance. The specific statuses available, and the events that trigger them, also vary by subscription type.

The sections that follow break this down for each type:

* **Standard/Recurring**
* **Prepaid**
* **Gift Prepaid**

{% hint style="info" %}
\***NOTE:** \*A subscription's **lifecycle status** and its **paused/on-hold indicator** share a single status badge in the OMS admin UI — when an active subscription is put on hold, that badge simply reads "Paused."

In other words, being paused isn't a separate stage in the subscription's lifecycle — a paused subscription is still **Active**, just with its upcoming orders temporarily suspended.

The **most recent order's processing status** is shown separately and updates independently, reflecting the latest payment attempt regardless of where the subscription sits in its lifecycle.
{% endhint %}

#### Example

*This example happens to be a converted prepaid subscription — covered in the Prepaid section. Note that in the `Active` screenshot the action button reads **Pause**; in the `Paused`screenshot it reads*\* Resume\*\*.\*

![State: Active — orders are processing on schedule.](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-eb6a1d43bdc4e42d678eef86814d3290a53edda6%2Fsubscription-states-2.png?alt=media)

![State: Paused — the same subscription with orders on hold.](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-b20cba5dc1adccefbc78245e24ecbc49cf8fac08%2Fsubscription-states-3.png?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/chord-oms/chord-oms-overview/subscriptions/subscription-states.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.