This operator surface makes KYC refresh explicit: which lanes are safe, which review packets are stale, and where payout, onboarding, treasury, or platform-risk teams still need to repair evidence before an account-safe decision is made.
Refresh-safe account posture
Escalate the marketplace payouts lane now: beneficial-owner refresh evidence, sanction-screen recency, and document expiry posture are still split across three systems and the next payout unlock should stay blocked until one canonical packet is rebuilt.
Ownership records were partially updated, but the controlling-person document trail is still stale in the canonical review packet.
Risk: Account-safe payout posture can break if stale ownership state clears ahead of the real review outcome.
Next: Merge refreshed beneficial-owner evidence, rerun sanctions screening, and regenerate the approval packet.
Document uploads are present, but two cases still lack adjudicated proof-of-address outcomes.
Risk: Stale refresh queues can leave customer state ambiguous across onboarding and fraud systems.
Next: Close the two unresolved address proofs and republish the queue snapshot.
Identity proofing, role review, and sanctions recency all converge on one reviewed packet.
Risk: Low. Current review lane is refresh-safe.
Next: Monitor only.
Sanctions recency is current, but passport expiration evidence drifted away from the main review packet.
Risk: Cross-border payout approvals can move on stale identity proof if the expiry anchor is missed.
Next: Restore document-expiry evidence to the canonical packet before the next release window.