notary.mu
Customer profile · identification & screening
SAMPLE DATA

Customer onboarding

The customer is whoever instructs the étude — not necessarily a party to the deed. Profile first, then identify; checks run automatically as the profile completes.

Searches the party registry and the customer file history in one call.
Identity
Name history — declaration
Contact & residence
ID document upload
JPG, PNG or PDF, max 8 MB per file. Each upload is fingerprinted (SHA-256) into the audit trail. Uploading a copy does not replace sighting the original — the "original sighted" confirmation below remains required before execution.
Biometric verification
Capture a selfie and upload the photo side of the ID, then run the face match.
Face matching in this prototype is simulated. In production, an on-device or server-side face-match SDK compares the selfie to the ID photo with liveness detection; a passed match lifts the remote-onboarding risk factor. Biometric data is special-category data under the DPA — explicit consent, no retention beyond verification unless consented.
Engagement context

Database checks Awaiting identity

Every check result is timestamped into the customer's audit trail — the étude's evidence of diligence.

Risk rating appears once identity is captured.
Screening lists in this prototype are mock data. In production: internal registry + customer DB via the identity service; sanctions/PEP via a screening provider or the UN & EU consolidated lists, re-screened on every new file. Profiles are personal data under the Mauritian Data Protection Act — access is logged, retention scheduled.