Status
Nothing is running yet.
MolnPay is in development. There is no production deployment, no API serving requests and no merchant depending on one, so there is no uptime to report and no incident history to show.
This page will be replaced by a real status page, fed by real monitoring, before the first merchant takes a live payment. It will never be decorative — a status page you cannot trust during an incident is worse than not having one.
What it will cover.
- Per-component state
- The API, the hosted checkout, the webhook deliverer, the signer and the dashboard, reported separately. An aggregate light that is green while webhooks are stuck tells a merchant nothing.
- Per-chain state
- Watcher lag, deposits being credited, sweeps and payouts broadcasting — for each of the fifteen chains individually. Chains fail one at a time, and an integrator settling on Tron does not care that Base is fine.
- Incidents, while they are happening
- Posted as they are understood rather than after they are resolved, with what is affected and what is not. A merchant deciding whether to switch off their checkout needs the update at minute five, not the post-mortem.
- Scheduled maintenance
- Announced ahead of time, with what will be unavailable and for how long.
- History
- Past incidents stay up. A status page that quietly deletes its bad days is a marketing page.