OTP-verified intake, multi-step KYC capture, document upload, PEP and third-party checks, and a back-office case manager — all on the same audit ledger your regulator will read.
A real walk-through of the customer journey — from intake to KYC capture to the back-office case file.
The customer never visits a branch. Each form field, OTP, document and consent lands in the same case file your reviewer opens minutes later.
Pick the ID type, capture front and back with the on-device camera, then a selfie for liveness. Every image is stored alongside the case — screens below are from the live product.
Customer chooses the ID type (passport, national ID, driver's licence, residence card) and captures the front with the on-device camera. Auto-frame and glare detection happen before upload.
Same flow for the back of the document. Legibility is checked before the customer can advance — no blurry captures end up in the case file.
A guided selfie capture with face-frame alignment. Liveness check compares against the ID photo and screens for deepfake / injection attacks before the case is created.
Every screen of the LiveEx-Shield non-face-to-face onboarding module — the customer's mobile flow on top, the reviewer's back-office below. 22 screens, end to end.
Phone-first. The customer never visits a branch. Every keystroke, OTP, photo and consent lands in the same case file your reviewer opens minutes later.
Customer picks a title (Mr / Ms / Mrs) and enters first, middle, last name and DOB. The 4-step progress bar is anchored at the top so they always know what's next.
Country-flag mobile picker, email entered twice for confirmation, then a 4-digit OTP delivered to that email. A visible resend timer prevents OTP spam.
A geolocation button to capture current location, then structured fields: country, nationality, country of residence, residential address, home address, city, province, postal code, PO box. Clean data, not free text.
Profession, business activity, account purpose. Self-declared PEP and third-party flags. Source of funds and employer name. Submit closes the registration phase.
Three-step KYC sub-flow begins. The customer picks the ID type they have — passport, national ID, driver's licence, residence card — before camera capture starts.
On-device camera with auto-frame alignment. Anti-glare and blur detection block submission of unreadable images before they ever land in the case file.
Same flow for the back side. Legibility is checked before the customer can advance — no blurry captures, no missing fields.
A guided selfie capture with face-frame alignment. Liveness check compares against the ID photo and screens for deepfake / injection attacks before the record is finalised.
Optional supporting documents — proof of address, bank statement, employment letter, anything required by jurisdiction. Customer can also skip and let the reviewer request later.
On submit, the customer sees a clean confirmation card and the journey ends. From their side, onboarding is done; from yours, the case has just begun.
Automatically generated email — "Confirmation of Successful Registration and Due Diligence Process". Sender, timestamp and body are written to the audit log.
Same database, same audit ledger, different surface. Status pills, side-by-side review, RBA + sanction findings, modal confirmations — nothing happens silently.
Submission lands in the Profile Pending queue. Clicking Edit opens the full Customer Definition record — PIN, citizenship, ID details, address, profession — for line-by-line review.
Every save triggers a Lex AML confirmation modal — username, timestamp, and support contact (admin@liveexshield.com) all surfaced. Nothing changes silently.
Once a reviewer flags a profile, it transitions to Pending Compliance and is routed to the compliance team's queue. The modal stamps the user who initiated the routing.
KYC Process view shows every customer's KYC status at a glance. Incomplete pills tell the reviewer who still owes documents; the Non Face-To-Face shortcut on the left rail jumps to fresh submissions.
Reviewer opens a case to see the Risk-Based Assessment breakdown (customer type, place of birth, geography, profession scores) plus KYC Details — Google search, adverse-media, beneficial-owner screening — captured per question.
Decision is committed and the KYC Saved Successfully modal confirms. Both the prior and the new state stay in the audit ledger with timestamps and reviewer ID — nothing is overwritten.
Same KYC Process list, refreshed. The customer's status has flipped to Complete and the case is now eligible for downstream processes.
Case-level actions: trigger a fresh KYC request, send the audit PDF to the customer, or re-screen against sanctions. API usage and licence expiry pinned to the header so operators always know where they stand.
AML — Customer Profile Findings: sanctions screening results, RBA breakdown, KYC due-diligence answers and the scenario rules that fired. Reviewer types remarks and clicks Accept or Reject — both routes are logged.
Once accepted, the customer record becomes available for transaction monitoring, periodic review and SAR / STR workflows downstream. Lex AML modal stamps the user and offers the support email for any post-decision query.
Filtered Case Management view showing the same customer fully through the pipeline — Case Status Completed, KYC Status Completed. The record now flows into TMS and periodic-review surfaces.
The customer never sees the compliance machinery. The reviewer never sees a draft form. Both portals share the same database, the same audit log, the same case ID.
Phone-first journey customers complete on their own. OTP-verified intake, smart address capture, and the KYC document flow shown above.
Where your KYC team lives. Each submission lands as a case with status, evidence, risk band and analyst notes.
Form, verification, review, compliance exceptions, notifications, audit trail, regulator inspection — out of the box.
Every submission becomes a case with a status, an SLA timer, and an evidence packet ready to read.
Every field, every consent, every audit entry maps to a published expectation.
Sandbox tenant with your branding, your jurisdiction's risk-band rules, and your document templates. Onboard a fake customer end-to-end in under twenty minutes.
