Capture
Selfie, document, data fields. Financial join is usually none — unless you bill per capture. Most teams over-sample this family because it photographs well.
Custom yard page
The control ledger for KYC applications
A ledger, here, is not your general ledger. It is a teaching book that lists identity events on one side and the financial movements they should have caused on the other. This page is the public spine of that book.
Five event families
Decision
Pass, fail, expire, override. This is where completeness of “we did not fund a fail” lives. Overrides are their own mini-population.
Screen
Hits, clears, escalations. Join to freezes and payout permissions, not to marketing “risk scores.”
Restrict
Blocks, unwraps, re-opens. Cut-off against cards, outbound payments, and account status in the ledger.
Refresh
Periodic triggers. Often missing from onboarding-shaped KYC apps. If the family is absent, say so.
How we use it in a live file (teaching, not consulting)
Pick one assertion. Map it to one family. Name the join key. List what unmatched means. Only then sample. Teams that start in the UI wander into Capture and never reach Restrict, which is usually where money is.
The ledger is deliberately unfinished. Your product will have extra verbs (“liveness waived,” “corporate structure approved”). Add rows. Do not delete the unmatched column; that column is the point.
What this page is not
It is not a regulatory checklist, not a vendor comparison, and not a substitute for your firm’s methodology. It is a shape for financially auditing KYC verification applications so that identity evidence and money evidence have to meet.