CADi · Customer onboarding
Why did we reject that customer?
Explain accept, reject and escalation decisions, the evidence behind them and the alternatives considered alongside your existing identity checks.
Bring us a problem, a suspected opportunity or a result that does not add up. We can explore how CADi KYC could help, starting with your question and the evidence available.
Get in touchOnboarding decisions reject real people. An accept, reject or escalate call at the door carries a fair-treatment and non-discrimination weight that a pass/fail from a KYC stack does not capture or defend.
When a rejection is challenged - as unfair, as discriminatory - the firm needs to show why the door did not open, under what policy, on what basis. That reasoning is rarely recorded in a form that answers the challenge without a manual reconstruction.
CADi KYC evidences how an onboarding decision was made - accept, reject or escalate - running alongside the firm's own KYC stack. It is built to govern the how; it does not make the call or replace that stack.
It produces an identity-decision record with the policy, the rationale and the trace, load-bearing on fair treatment and non-discrimination - never a way to reject more applicants or tighten the gate silently. It enters as evidence and is designed to graduate toward governing the onboarding decision.
An identity-decision record - accept, reject or escalate - with the policy and the rationale, not a bare pass/fail.
Built around non-discrimination and fair treatment, so a rejection can be defended as warranted rather than reconstructed after a challenge.
Explicitly not a way to reject more applicants or narrow the gate quietly - the evidence cuts against silent, undocumented drift.
Runs alongside the firm's KYC stack first, attesting how the call was governed; graduates toward governing the onboarding decision as trust builds.
Banks, fintechs and regulated firms onboarding at scale, who reject real people and must defend how those calls were made.
The teams accountable for non-discrimination and fair customer treatment at onboarding, who need the reasoning on the record.
CADi KYC is one product in the CADi range: the same deterministic causal engine - nine layers, a do-calculus core and a hash-chained audit trail - pointed at the onboarding decision.
It belongs to the reporting layer: it runs alongside the firm's own KYC stack, evidencing how a decision was governed rather than making it, and is built to graduate into the decision itself once the evidence loop is trusted - enter on evidence, earn the decision.
CADi is in production - its engines are live in the cloud - with nine UK patent applications pending. CADi KYC evidences how an onboarding decision was governed; it does not make the accept/reject call, replace the firm's KYC stack, or guarantee a regulatory outcome.
Causal analysis runs on a declared model of the decision environment. Its conclusions depend on that model, the available evidence and explicit assumptions; estimates are analytical approximations. The engine has been tested against injected, synthetic and real ingested data. Live-outcome validation is completed against each client's own outcomes during deployment.