Where this physician's payouts stand, read live from Stripe.

payouts_enabled is fetched at the moment of the question and thrown away, never cached. A stored copy of compliance state is stale the instant Stripe updates it, and the version of that bug that matters is the one where we tell a physician they are good to be paid after Stripe has decided otherwise.

A Stripe read that fails degrades to the stored status rather than 500ing: the physician's own earnings page should not go blank because an upstream API is slow. A MISCONFIGURED rail still raises, because that is an operator problem and hiding it is how a dark rail stays dark unnoticed.