A service carries its own status as it is enabled, reviewed by underwriting, and later disabled. This page covers the service-level statuses only. For the business-level boarding flow (Saved → PENDING_REQUIREMENTS → PENDING_UNDERWRITING → ACTIVE → CLOSED), see Status lifecycle.

---

Service statuses

Once you enable a service, it moves through its own statuses: from PENDING_UNDERWRITING to ACTIVE on approval, then through PENDING_DISABLE to DISABLED if you turn it off.

stateDiagram-v2
    [*] --> PENDING_UNDERWRITING: service enabled
    PENDING_UNDERWRITING --> ACTIVE: approved
    ACTIVE --> PENDING_DISABLE: disable requested
    PENDING_DISABLE --> DISABLED: turned off
    DISABLED --> [*]

While a service sits in PENDING_UNDERWRITING, its missingFields, missingDocuments, and errors tell you what's still outstanding. See Underwriting exceptions.

🚧

PENDING-PUBLISH

Two status-vocabulary conflicts are unresolved in the source contract: an enabled service appears as both ENABLED and ACTIVE in different examples, and a pending-disable service as both PENDING and PENDING_DISABLE. This table uses the ACTIVE and PENDING_DISABLE forms. Confirm the authoritative enum against the boarding spec before publish.

---

Next steps

See also

• Supported services and features: the service and feature codes
• Underwriting exceptions: resolve what a service still needs