The operator onboarded to Stripe Connect 14 months ago, the timestamp was blank when I audited — a transient capability flap was wiping my milestone audit anchor

Marcus (39), Frankfurt fintech compliance auditor, three days into a quarterly review needs to prove a restaurant chain's Stripe Connect first-onboard date for a BaFin tax dispute. The thMenu super-admin panel shows the account active, payments flowing, but `stripe_connect_onboarded_at: NULL`. Forensic: across 14 months, three transient capability flaps (KYC re-docs, dispute review, Stripe Risk hold) had each fired the `connect/refresh` route, which overwrote the canonical timestamp with NULL every time `charges_enabled=false`. **PR #631 batch HHH F1** fix: `COALESCE`-style read-then-conditional-stamp. First-true wins, never overwrite. Mirror of TT-B F3 (verification flags time-bound, never sticky) in REVERSE — milestone audit timestamps sticky-first-true, never overwritten. Pattern: `grep -rn "_onboarded_at\|_verified_at\|_completed_at"` sweep + audit every UPDATE path for the write-on-true-overwrite-on-false anti-pattern.

Related articles