> ## Documentation Index > Fetch the complete documentation index at: https://docs.anyway.sh/llms.txt > Use this file to discover all available pages before exploring further. # Customers & Subscriptions > Inspect customer purchase history and manage recurring customer subscriptions. The **Customers** and **Subscriptions** pages under **Payment** describe commerce sold by your organization. ## Customers The Customers page lists the stable Anyway customer ID and normalized email for customers derived from your organization's orders. Open a customer to review related orders and subscriptions, then follow an item to its full detail view. Customer records are created from commerce activity; this page is not a general-purpose contact database and does not edit customer identity. ## Subscriptions The Subscriptions page lists recurring customer subscriptions and supports status filtering. Open a subscription to inspect: * status, customer, product, amount, currency, and billing interval; * the current period end and whether cancellation is scheduled; and * the initial payment plus later renewal orders. Supported lifecycle statuses are `PENDING`, `ACTIVE`, `PAUSED`, `CANCELED`, `EXPIRED`, and `ENDED`. Billing intervals can be daily, monthly, or yearly. Recurring checkout is available for supported Card / USD pricing; Crypto payment links remain one-time. ## Order relationships | Order kind | `subscriptionId` | `originalOrderId` | | ---------------------------- | ---------------- | --------------------------- | | One-time purchase | Not present | Not present | | Initial subscription payment | Present | Not present | | Subscription renewal | Present | Points to the initial order | Use these relationships to distinguish one-time orders from initial and renewal charges without relying on a payment-provider identifier. ## Schedule cancellation Canceling from the Subscriptions page schedules cancellation at the end of the current billing period. The subscription can remain active until `currentPeriodEnd`; the detail shows that state through `cancelAtPeriodEnd`. Refreshes and Webhook updates reconcile the record with the payment provider. Read subscription lifecycle and order relationship fields from your backend. Read customer identities and use `customer_id` to filter related records.