# Checkout service – status report

**Week of 20–24 July 2026** · Owner: Priya N. · Status: **On track**

> **TL;DR:** Payment-retry rollout reached 100% of traffic on Tuesday with no
> error-rate movement. Refund latency work slipped one week – blocked on the
> ledger migration. Nothing needs a decision this week.

## Progress this week

- Payment-retry rollout completed: 25% → 100% of traffic, error rate flat at
  0.04% (was 0.05% before rollout).
- Idempotency-key handling shipped for the `POST /charges` path; duplicate
  charge reports dropped to zero since Wednesday.
- Load test at 2× peak traffic passed – p99 held at 180 ms.

## Slipped or blocked

- **Refund latency (was: due 24 Jul, now: 31 Jul).** The fix depends on the
  ledger migration, which is still replaying historical events. No customer
  impact meanwhile – refunds complete, just in 4–6 h instead of the 1 h
  target.

## Numbers that matter

| Metric | Last week | This week | Target |
|---|---|---|---|
| Charge error rate | 0.05% | 0.04% | Below 0.1% |
| p99 charge latency | 210 ms | 180 ms | Below 250 ms |
| Duplicate-charge reports | 3 | 0 | 0 |
| Refund completion time | 4–6 h | 4–6 h | Under 1 h |

## Next week

- Land the ledger migration and unblock refund latency.
- Start the chargeback-webhook spike (2-day timebox, decision doc to follow).

## Risks

- Ledger replay is single-threaded; if it runs past Tuesday, refund work
  slips a second week. Mitigation: replay is resumable, and we can shard it
  by account range if Monday's checkpoint looks slow.