Checkout & API
Pre-launch standby mode. Services wake on real application traffic.
Operational
RecurCrypto service status
Live, sanitized health for the customer-facing payment rail. Internal counters, wallet data, job diagnostics, and secrets are never exposed here.
Last evaluated: 13/10/2026, 15:41:56 UTC
Operational
Polygon connectivity
Idle RPC health checks are paused to minimize pre-launch infrastructure cost.
Indexer & reconciliation
Background synchronization is paused while there are no live users.
Renewal engine
No live renewal workload is scheduled in pre-launch standby mode.
Webhooks
No live webhook retry workload is scheduled in pre-launch standby mode.
What this page measures
The public status model summarizes checkout/API availability, Polygon connectivity, indexer and reconciliation freshness, renewal processing, and webhook delivery. Merchant-specific payment failures are not exposed as public incidents.
A healthy public status does not replace merchant-side verification. Applications should keep webhook handling idempotent, preserve subscription and transaction identifiers, and use API reads or on-chain reconciliation when a customer state needs to be confirmed.
If one service is degraded, separate customer-facing checkout availability from background synchronization before changing access. A delayed webhook or indexer update can require verification without meaning the underlying subscription payment failed.
This public view is cached briefly so health checks do not add unnecessary load to the same services they measure. Operational state can therefore lag the underlying systems by up to about one minute.