The status page should show operational, degraded, partial outage, major outage or maintenance for each component, with incident start, updates and resolution. It must not invent historical uptime or hide the manual nature of fulfillment.
A general incident does not determine one order’s payment state. The verified order page remains the source for individual confirmation and delivery; if an incident blocks access, contact support with the USV- reference after service recovers.
The status page separates storefront and catalog, guest checkout, OxaPay payment creation, payment-webhook processing, email delivery, passwordless access, order tracking and manual fulfillment. Each incident should identify affected components, start time, current impact, mitigation and resolved time without publishing customer data. Planned maintenance is labeled separately. A history can be shown only from recorded events; no uptime percentage or past reliability claim is invented.
A green component state cannot confirm an individual order, and a provider outage may be narrower or broader than the visible summary. Customers should rely on their secure order page for payment and fulfillment state, then report a mismatch with the USV reference and time. During an incident, updates should be factual and time-stamped; estimated recovery is labeled as an estimate. The final public incident contact and maintenance-notice policy remain [STATUS_CONTACT_TO_VERIFY] and [MAINTENANCE_NOTICE_POLICY_TO_VERIFY].