Public status page

API availability, webhook delivery latency and maintenance notices must come from an approved status source before public launch.

Status source not connected

This production route does not claim live component health until an incident/status backend or human-approved publication process is connected.

Fail closed

No operational, degraded, incident or maintenance row is shown from static content.

Publication boundary

Future notices must explain impact, start, end, update cadence and request_id guidance without exposing provider names, merchant data or funding state.

No provider names or route internals.
No merchant-specific data.
No SLA or uptime claim without approval.