eKYB

The eKYBVerification module collects business identity information and validates it against official corporate registries and regulatory databases to confirm the legitimacy of a legal entity. It enables compliant, real-time business verification within onboarding and regulatory flows.

Designed to be structured and secure, the module manages logic, processing states, and verification outcomes with clear system feedback.

---

Where it fits in the flow

eKYB Verification is positioned after initial business representative data collection (such as email or phone verification) and before advanced verification modules, depending on the configured onboarding flow.

---

User Flow

The eKYB Verification experience guides users through structured data entry and backend validation.

---

Full Flow Map

This diagram outlines the end-to-end screen sequence of the eKYB Verification module, including data input, validation states, and the success outcome.

---

Happy Path (Light & Dark)

The ideal user journey occurs when business information is submitted and verified successfully against official records without interruptions. The happy path represents the smoothest version of the experience: the user completes all required business fields accurately (such as legal entity name, registration number, and jurisdiction), submits the form, and the system validates the information against corporate registries without mismatches or delays. The processing state resolves successfully on the first attempt, and the user reaches the confirmation screen without needing to retry or correct any data. Light and dark mode previews are included to allow teams to validate visual consistency, accessibility, and contrast across themes and platforms.

---

Best Practices

Recommended guidelines for designing and implementing the eKYB Verification experience.

✅ Do

• Keep the form structured, clean, and easy to scan.
• Use inline validation to prevent submission errors.
• Clearly indicate required fields and input formats.
• Preserve user-entered data if verification fails.
• Provide clear feedback during the processing state.

❌ Don’t

• Don’t delay validation until after submission.
• Don’t erase completed fields after backend errors.
• Don’t allow duplicate submissions while processing.