Platform lifecycles
A lifecycle page describes a domain resource's journey over time — its states, transitions, and the end-to-end process you drive as a caller — as state + sequence diagrams. Each links to endpoints for how to call each step.
Only resources with a genuine multi-step journey appear here. One-shot stateless lookups/reads do not have a lifecycle: statements (read/download), address, banking products, and payees (thin create→read→delete).
| Resource | Page | Journey |
|---|---|---|
| Parties | Parties | Status machine PROSPECT → ACTIVE → TERMINATED, with per-entity-type onboarding (individual, company, sole-trader). |
| Identity verification (KYX) | kyx | A verification session — initiate → upload → verified/declined/failed, keyed by arkVerificationId. Tracked separately from a party; see the page. |
| Card | card | Issue → provision → ACTIVE ↔ LOCKED → CANCELED. |
| Payment | payment | Immediate (validate → initiate) and scheduled (create → list → cancel) journeys. |
| Account | account | Open → manage signatories / alias → view transactions. |
| Notification | notification | NEW → DELIVERED (scheduled sends show SCHEDULED_DELIVERY); can be CANCELLED or purged. |