SLA credits
Every credit we’ve issued, in one ledger
A published service level is only worth as much as the credits paid against it. This is the full register since GA. No customer names, no waivers, no exceptions. Numbers are independently reviewed annually.
Credits issued (LTM)
€96,450
7 discrete incidents
Auto-issued share
100%
No customer ticket required
Median time to credit
38h
From incident close to invoice line
Independent review
BDO
Annual, included in integrity report
Register
| Quarter | Metric | Credit % | Issued |
|---|---|---|---|
| Q2 2026 | API latency p95 | 5% | €6,420 |
| Q2 2026 | Reconciliation freshness | 5% | €14,380 |
| Q1 2026 | Uptime | 10% | €41,200 |
| Q1 2026 | Payout cut-off | 5% | €3,940 |
| Q4 2025 | API latency p95 | 5% | €2,180 |
| Q4 2025 | Reconciliation freshness | 5% | €8,910 |
| Q3 2025 | Uptime | 5% | €19,420 |
How credits work
- Breach detection is automated against the same measurements we publish on the status page.
- Credits post as a negative line on the next monthly invoice — no claims process, no waivers, no cap below the published table.
- Material breaches trigger a public incident report in /transparency within five business days.
- Customers may opt to receive credits as a wire-back instead of an invoice offset; we honour the request the same cycle.