X2, K14 and K5
Onboarding and Verification
From a form to a funded account, without anybody re-keying a field. The whole sequence runs today. What makes it defensible afterwards is not that it completed, but that every stage left a record saying what was asked, what was answered, and who answered it.
Six stages, and what each one wrote.
An acceptance is defended with the records behind it rather than with the decision itself. The right-hand column is the point of the left-hand one.
- 1Application submittedX2, client portal
- 2Identity verifiedK5, idv.verify
- 3Ownership resolvedC3, through every layer
- 4Screening clearedK2, sanctions.screen
- 5Accepted by officerX3, named decision
- 6Account openedC2, wallet per currency
Standing is derived, not stored.
Identity events append. The standing is what they currently add up to, which is why the system can answer when, to what standard, by what method and until when rather than only whether a box is ticked.
Three levels and five methods. A simplified check and an enhanced one are not the same fact, and a system that records both as “verified” cannot tell you which customers need redoing when a policy tightens.
Events, append only
Standing, derived
pending_since records when the oldest in-flight check began. The rules allow verification to finish after a relationship starts, but only as soon as practicable, so how long it has been outstanding is a compliance fact rather than a progress indicator.
Seven states an identity can be in.
Three of these are frequently collapsed into failure by systems that treat verification as a boolean. They are different problems with different remedies.
Questionnaires, versioned and gated.
A question set is published as an immutable issue. An answer is bound to the version it was asked under, so a question that changes next quarter does not retroactively change what someone was asked.
Who said it matters as much as what was said.
An answer carries whether the applicant declared it or an officer wrote it down. A customer’s claim about their own source of funds and an officer’s finding about it are different evidence, and a file that records them identically cannot be reviewed properly.
Answers are superseded rather than overwritten, so the first answer is still there when somebody asks why it changed.
- A single-choice question may name the manual risk factor it answers, so a judgement is asked once on the form rather than again inside the risk card.
- Field composition is a closed registry: a versioned layout per party type says which fields are collected, under which heading, in what order.
- Both portals draw their forms from that layout, so the applicant’s form and the reviewer’s panel cannot drift apart.
What it guarantees.
Each of these is enforced rather than intended, and each is something you can sit down and try to break on a call. We would rather you did.
- An answer is bound to the questionnaire version it was asked under. Changing a question next quarter does not retroactively change what somebody was asked.
- Answers supersede rather than overwrite, so the first answer is still there when somebody asks why it changed.
- Identity standing is projected from events, so the system can always say when, to what standard, by what method and until when, not merely that a box is ticked.
- Both portals draw their forms from one versioned layout, so what the applicant is asked and what the reviewer sees cannot drift apart.
Walk your own application form through it.
Bring the questions you are required to ask and we will build the set, gate it and answer it on the call.