WIP, Shared, Published and Archived, with controlled gates
to launch a hosted capture session
guided capture: front, hologram, back, selfie, liveness
document, face and liveness checks together
The applicant photographs their ID in the hosted session and iVerifier reads the identity fields for you, while the front, security hologram and back of the card are captured for document checks.
The selfie taken in the session is compared with the portrait on the ID and scored, so holding someone else’s card is not enough to pass.
Liveness is checked from the selfie capture itself. Applicants are not asked to blink, nod or turn their head, so the journey stays quick while you confirm a real, present person is in front of the camera.
Each check is scored on its own and compared against decision thresholds. The verdict, the scores and any reason codes are signed and pushed to your system, so nothing about the decision is a black box.
Operations, compliance and fraud teams can open any session by its transaction ID and see exactly what was captured and how it was scored.
Scores shown are from a sample session; thresholds are illustrative and set per deployment.
iVerifier owns the camera, prompts and capture experience. Your app opens one secure URL and the applicant is guided step by step, so every channel captures the same quality of evidence without you building a capture interface.
The hosted capture handles the camera, framing and prompts, so there is nothing to build or maintain on your side.
Open the one hosted URL from a mobile app, a web journey, an agent’s tablet or a branch kiosk.
Every capture belongs to one session, traceable by its transaction ID from first photo to final verdict.
Your channels open the hosted session. iVerifier authenticates it, orchestrates every check, decides against your thresholds and signs the result, then delivers it to the systems that need it.
Authenticate, initialise a flow for the document type you need, and hand the applicant a single URL. That is the whole integration surface.
POST /api-kyc/token
Get an access token for your organisation.
POST /api/v1/realid/initialize
Choose the document type and flow; receive a transaction ID.
h5Url
Send the applicant to the returned URL in any channel.
Three REST calls start a hosted capture session.
# 1 Authenticate
POST /api-kyc/token
200 OK { "access_token": "eyJhbGci..." }
# 2 Initialise a MyKad H5 flow
POST /api/v1/realid/initialize
{ "docType": "mykad",
"flowType": "H5_REALIDLITE_KYC" }
# 3 Open the returned h5Url for the applicant
"transactionId": "sess_374c..."
"h5Url": "https://..."An HMAC-SHA256 signed webhook delivers each result.
{
"session_id": "sess_30ed93412ab448af8ffe",
"decision": "approved",
"ocr_fields": {
"name": "SAMPLE APPLICANT",
"doc_number": "XXXXXX-XX-1234"
},
"scores": {
"ocr": 0.928,
"face": 1.0,
"liveness": 0.942
},
"reason_codes": []
}Plain HTTPS and JSON, so any stack, low-code platform or integration layer can call it.
Check the HMAC-SHA256 signature before you act on a result, so only iVerifier verdicts are trusted.
Results are pushed as they are ready, and a missed callback never means a lost result.
iVerifier is not tied to one industry. The same hosted capture, checks and signed verdict serve onboarding, registration, payouts and re-verification wherever you need to know the person is real.
| Use case | Banking & finance | Insurance & takaful | Telecommunications | Retail & e-commerce | Public sector | Other industries |
|---|---|---|---|---|---|---|
| Customer onboardingOpen an account, policy or service remotely | ||||||
| Subscriber and service registrationPostpaid plans, utilities and digital service sign-ups | ||||||
| Financing and instalment applicationsLoans, cards, buy-now-pay-later and device financing | ||||||
| Claims, payouts and benefitsVerify the payee before money leaves | ||||||
| Re-verification and account recoveryPeriodic re-KYC, SIM replacement, device or password reset | ||||||
| High-risk changes and transactionsStep up before a sensitive change or large transaction | ||||||
| Agent, seller and workforce onboardingAgents, dealers, marketplace sellers and gig workers | ||||||
| Age and eligibility checksAge-restricted products and eligibility rules |
Other industries include property, mobility and gig platforms, healthcare, education and utilities.
Doing eKYC well usually means a capture app, three verification vendors, decision logic and review tooling. iVerifier delivers all of it as one hosted service.
Show regulators and auditors how each customer was verified, which checks were run and how the decision was reached, including the scored evidence behind false acceptance rate (FAR) audits.
Results are signed with HMAC-SHA256, so your systems can confirm they came from iVerifier and were not altered.
Every session starts with token authentication at the API gateway and stays scoped to one transaction ID.
Scores and reason codes travel with every verdict, so a decision can always be explained.
The portal keeps each session’s overview, media and scores together for operations, fraud and audit teams.
Crest confirms the hosting model and data residency with you, to match your regulatory boundary.
Evidence that supports Bank Negara Malaysia’s e-KYC policy document, AML/CFT customer due diligence and the PDPA, which has treated biometric data as sensitive personal data since April 2025.
Compliance depends on your policies, configuration, operating procedures and audits. iVerifier provides controls and evidence that support your compliance programme.
iVerifier is API-first, so verification is one step in a larger digital journey that Crest designs and delivers with the platforms you may already use.
Confirm the customer is real and matches their ID.
Check payslips, statements and bills for signs of editing.
Run onboarding as a case and file the evidence as governed records.
Publish and secure every onboarding API behind one gateway.
Practical answers for teams evaluating eKYC for any onboarding journey.
eKYC (electronic Know Your Customer) is the remote, digital way to confirm a customer’s identity without a branch visit or paper copies. A typical eKYC check reads the government-issued ID, compares the applicant’s selfie with the ID photo, and confirms the applicant is a live person, then records the evidence for compliance.
BNM’s e-KYC policy document (BNM/RH/PD 030-16, effective 15 April 2024) describes document verification, biometric matching against a government-issued ID and liveness detection as e-KYC measures, and requires all three for higher-risk products such as current and savings accounts. iVerifier performs these checks in one session and records the scores and evidence for each one, which supports the false acceptance rate (FAR) audits and monthly performance records the policy document asks for. Your institution remains responsible for its own risk assessment, thresholds and reporting.
iVerifier is an end-to-end eKYC platform from Crest Infosolutions. It combines document OCR, face match and passive liveness on one platform: one API launches a hosted capture session, the applicant scans their ID and takes a selfie, and your system receives a signed verdict with a score for each check.
Seconds, from capture to signed verdict. The applicant follows five guided steps in the hosted session, and the result is pushed to your webhook as soon as the decision is made.
Each hosted flow is initialised for a document type, starting with Malaysia’s MyKad: front of the card, security hologram, back of the card, selfie and liveness. Crest confirms the document types and flows available for your markets during scoping.
Passive liveness checks that a real, present person is in front of the camera from the selfie capture itself, without asking the applicant to blink, nod or turn their head. Together with face match, it is designed to stop someone presenting a photo or recording of another person.
With three API calls: authenticate to get an access token, initialise a flow for the document type you need, then open the returned h5Url for the applicant. iVerifier hosts the camera, prompts and capture, so there is minimal UI work on your side.
Each result is pushed to your endpoint as an HMAC-SHA256 signed webhook with the decision, the OCR fields, the scores and any reason codes. Results can also be retrieved at any time by polling with the session’s transaction ID.
Yes. The iVerifier portal shows every session by transaction ID, with an overview of the decision and identity fields, the captured media, and the OCR, face match and liveness scores.
Any journey that starts with an ID: customer onboarding, subscriber and service registration, financing applications, claims and payouts, re-verification and account recovery, step-up checks before high-risk changes, agent and seller onboarding, and age or eligibility checks. It is used across banking and finance, insurance and takaful, telecommunications, retail and e-commerce, the public sector, and industries such as property, mobility, healthcare and education.
iVerifier is API-first, so a verification can be a step in an Alfresco onboarding case, the verified customer can sign with SignDex in the same journey, and the onboarding APIs can be published and secured through Kong. Crest designs and delivers the end-to-end journey.
Bring one onboarding journey and we’ll show it running in iVerifier, from hosted capture to signed verdict, in a 30-minute walkthrough.
Document · selfie · liveness
Scores · reason codes · webhook
Opens your email application with a draft to review and send. Use the online contact form if you prefer.
Request for information or schedule a solution demo.