Remediation, fixing a book of customers that was onboarded badly
Solidus runs no remediation programmes and ships no case management. Remediation is not-built in our lexicon.
What it is
A backward-looking exercise: going through customers already onboarded and bringing their files up to a standard they did not meet at the time.
It is usually triggered by something unwelcome, a supervisory finding, an internal audit, a migration that exposed gaps, or a policy change that raised the bar retroactively. The work is rarely optional and rarely small: contacting customers who thought they were done, re-collecting information, and evidencing the whole thing to whoever asked for it.
Remediation differs from re-KYC in cause, not mechanics. Re-KYC is scheduled maintenance; remediation is a correction of the past. The customer experience is the same imposition, which is precisely why completion rates are the thing that decides whether a programme succeeds.
Where a portable credential genuinely helps, and it is a real point
The binding constraint in most remediation programmes is customer response, not internal process. Every contacted customer who does not complete the flow becomes an escalating problem: restricted, chased, or eventually offboarded.
Anything that lowers the effort asked of the customer moves that number, and a credential the customer already holds is exactly that: present it, rather than repeat the original onboarding.
That is a real argument, and it is the same structural point as re-KYC: the estate's strongest positive case, where repetition is guaranteed rather than hoped for. The argument is good; what is unverified is our implementation, not the shape of the idea.
The honest precondition: it only works for customers who already hold a credential. For a remediation programme running today against a book onboarded years ago, almost nobody does. So this is an argument about how a future book behaves, not a fix for a present problem, and if you are scoping remediation this quarter, we are not a candidate.