The check that made the decision is the check on file.
Verification reports, screening snapshots and consent trails are sealed the moment a decision is made. When a bank or regulator asks years later, the provider proves the report existed unaltered at decision time, while the person's data never left the provider.
What gets sealed
Document forensics, liveness and face-match results sealed as the report is finalized, fixing exactly what cleared the customer.
AML, PEP and sanctions results sealed as run, so what the lists said on that day is provable on any later day.
Who consented to what, and every re-screening outcome, sealed as events occur, building a trail nobody can restate.
How it runs day to day
The verification platform calls POST /v1/seal the moment a report is finalized.
Only a salted digest leaves the provider; the identity data itself never does.
The proof is filed with the case and handed to the relying bank with the report.
In any audit or dispute, the report verifies against its decision-day anchor.
An account goes bad and the regulator asks whether the onboarding report was rewritten after the fact. The sealed report verifies against its anchor from the day of the decision: the screening result on file is the one that cleared the customer. The question is answered with mathematics, not with log files.
Without an independent seal, the provider's defense rests on its own database timestamps, the very records under suspicion, and every relying bank inherits that doubt.