What IDME does
IDME is a B2B digital identity verification platform: organizations and government agencies use it to confirm online that a person or a company is really who they claim to be. Its main scenario is B2B contract signing, where a merchant completes six categories of document verification to earn a merchant ID before trading can start. I owned the UIUX with a React web frontend. Because the content is highly confidential, the screenshots here are deliberately ultra low resolution and fully blurred, showing only the shape and scale of the flows; the text carries the requirements, constraints and decisions.
KYB in six categories
The hard part of KYB (Know Your Business) is document volume: legal representative ID, proof of address, other shareholders, point of sale, bank account and contract signing, six categories with none optional. The design turns them into a six card checklist, one tick per completed category, so users always know where they stand and what is missing. Proof of address accepts utility bills, telecom invoices, leases and similar documents, by file upload or straight from the camera. For the bank account, a lookup finds the IBAN first and asks for confirmation, falling back to manual entry only when the lookup fails, cutting typo risk to nearly zero.
Designing the wait
The real UX battleground of identity verification is time. After submission, review can take one to seven days, and an undesigned gap just breeds anxious resubmissions. So every document category carries its own state (missing, in review, approved, returned), and the hub states the expected day range and what happens next: an approval email arrives first, access follows. When something is returned, the message names the document, the reason and the fix. The lesson: trust in a verification product does not come from speed, it comes from the user always knowing what is happening while they wait.