KYC onboarding

Customer Identity Verification

Verify a customer's identity against authoritative sources, block impersonation with biometric liveness, and receive a clear identity opinion that feeds the same screening record used across the business.

Last updated

What this covers

  • Government-issued document checks
  • Biometric face match and liveness
  • Four ways to reach the customer
  • Confidence-based identity opinions
  • Linked to AML screening
Marble office atrium with access-control turnstiles at the entrance

Screening in production for

  • Zappit
  • AMP
  • BancABC
  • BMG
  • BTC
  • CMC Markets
  • Coop
  • CSC
  • EFICA
  • EML
  • Groupama
  • MEO
  • Riskified
  • Securiport
  • Tanzania Commercial Bank
  • Tradeview Markets
How it works

From a photo of a passport to a decision you can defend.

  1. A person actsChoose deliveryVerify in-platform, send an SMS or email link, or embed a verification URL in your own system.
  2. A person actsCustomer submitsThe customer enters their details and photographs their identity document, on desktop or mobile.
  3. A person actsFaceMatchWhere requested, the customer takes a live selfie and liveness detection confirms they are physically present.
  4. AutomatedVerified against recordsName, date of birth and document details are checked against government and official sources for the document's country.
  5. AutomatedFraud checksDocument authenticity, facial recognition, liveness and device signals are assessed at the same time.
  6. A person actsIdentity opinionA clear outcome returns in seconds, stored with its evidence for audit, for your team to act on.
4 a person acts2 automated
Most of this sequence is the customer's two minutes on their own phone. The platform's part is the middle — routing the check, verifying against authoritative records and running fraud detection in parallel — and what reaches your team at the end is an opinion, not a data dump.
The real problem

A document that passes is not a person who exists.

Document authentication answers whether the credential is genuine. It does not answer whether the human holding it is real, whether the face was generated, or whether the same portrait has already been used on another identity. Synthetic and assembled identities are built to survive exactly the check most onboarding flows stop at, which is why verification here runs a set of fraud tests alongside the document check rather than trusting any one signal.

Biometric verification versus deepfakes, and which one is winning
  • Face liveness separates a present person from a photograph, a recording or a generated face
  • Deepfake and cheapfake detection tests the media itself for manipulation
  • Document liveness and print detection tell an original apart from a screen or a photocopy
  • Portrait overlay detection catches a genuine document wearing someone else's face
  • Duplicate portrait detection finds the same face submitted under mismatched identity details
  • Device and location signals show where verification was manipulated to get through
Capabilities

What you get.

Verify your way

Run verification inside MemberCheck, send the customer a link by SMS or email, or embed a verification URL in your own portal. Customers verify in a browser on any device, with no app to download.

Document verification

Authenticate passports, driving licences and national identity cards against government and official records, with each request routed automatically to the right source for the document's country of issue.

Biometric FaceMatch

Match a live selfie to the photo on the verified document, with liveness detection that confirms a real person is present rather than a photograph, a recording or a generated face.

Identity opinions, not raw data

Every check returns a confidence-based outcome — verified, not verified, review required, pending, incomplete or not requested — so a compliance officer reads a decision rather than interpreting match scores.

One scan, identity and risk

A verified identity flows straight into sanctions, PEP and adverse-media screening on the same record, so an onboarding decision uses identity and risk together instead of two systems.

API integration

Embed verification into your own onboarding flow through the MemberCheck REST API, so customers verify inside your product and results post back to the customer record automatically.

Scope

What you can screen.

  • New customers at onboarding
  • Individuals and sole traders
  • Directors and authorised signatories
  • Beneficial owners requiring proof of identity
  • Re-verification during the relationship
1,000+
Global watchlists screened
<1s
Average screening response
24h
Watchlist refresh cycle
195
Countries covered
Assurance

What your security review will ask for.

99.98%
System uptime
<24h
Average integration time
24–48h
Signed to production account
<1s
Average screening response
  • ISO/IEC 27001:2022 certifiedISO/IEC 27001:2022Information security management, independently audited.
  • ISO/IEC 27701:2019 certifiedISO/IEC 27701:2019Privacy information management, extending ISO 27001.
  • GDPR — EU General Data Protection RegulationGDPRPersonal data handled to EU standards, wherever you operate.
  • DORA — EU Digital Operational Resilience ActDORAOperational resilience for EU financial entities and their vendors.
Questions

Common questions.

How does the verification process work?

MemberCheck validates a government-issued identity document against trusted authoritative records. Each request is routed automatically to the most appropriate source for the customer's location and the type of check requested, and the result returns as a confidence-based identity opinion rather than raw match data.

How long does a check take?

Most identity verification checks complete in seconds, fast enough to run inside a live onboarding flow. Response times vary with the country and document type being verified.

What happens if a customer cannot be verified?

A check that cannot be completed, or that returns a low-confidence result, comes back as an identity opinion of review required rather than a silent decline. Your team decides whether to ask for more information or escalate, so a genuine customer is not lost to an automated refusal.

Do customers need to download an app?

No. Verification runs entirely in the customer's browser. A session started on a desktop can be handed to a phone with a QR code, because document capture and selfies are more reliable on a mobile camera.

Which documents and countries are supported?

MemberCheck verifies government-issued passports, driving licences and national identity cards, with document and data coverage across 60+ countries, expanding to 120+. Australian and New Zealand clients can choose which source handles Australian document checks, and no separate participation agreement is required.

Does verification connect to AML screening?

Yes. The verified identity feeds directly into sanctions, PEP and adverse-media screening on the same customer record, so onboarding decisions use identity and risk together instead of in separate systems.

See MemberCheck in action.

A short walkthrough of screening, verification and ongoing monitoring in one platform, set to the thresholds and jurisdictions your programme actually uses.