Status
The live status page lives at oid4pay.statuspage.io.
It embeds SLO-level uptime and the active incident timeline. The page below
is the static fallback.
Components and SLOs
| Component | Host | Availability SLO (monthly) |
|---|---|---|
| Authorization Server | as.oid4pay.com | 99.9% |
| Wallet Portal | wallet.oid4pay.com | 99.9% |
| Discovery Directory | discover.oid4pay.com | 99.5% |
| Billing engine | as.oid4pay.com/billing | 99.5% |
Latency SLOs
| Endpoint | p95 | p99 |
|---|---|---|
POST /oauth/par | 120 ms | 250 ms |
POST /oauth/token | 180 ms | 350 ms |
POST /merchant_test/verify-mandate | 40 ms | 120 ms |
GET /oauth/status-list | 30 ms | 80 ms |
POST /merchant_test/charge | 800 ms (Stripe-bound) | 1500 ms |
Incident communication
Subscribe on the Statuspage tenant for email and RSS notifications. Critical incidents also publish a postmortem entry on the incident history page within 5 working days of resolution.
Test mode
There is no separate sandbox. The developer preview runs in test mode on the hosts above and no real money moves (see test mode).
SLO error budget
The 99.9% availability target for the authorization server allows 43.2 minutes of downtime per 30 days. Our error-budget policy follows the standard approach: while we are under budget, feature work continues; once we are over budget, reliability work takes priority until the budget recovers.