Identity verification for customers in Japan
Verify a customer's identity at the time of transaction, apply a stricter method when the transaction is high risk, and keep verified details current after onboarding
- 60+countries checked against official data
- 240+countries and territories' ID documents recognised
- Webbrowser
- 30-dayvalidity
A sample identity check: an ID document being scanned, a face-match score and a verified result.
Screening in production for
What every identity check returns
Document checks
Passports, licences and IDs
FaceMatch
Live selfie matched to photo
Liveness tests
Deepfake and fraud checks
Three ways to reach
Platform, email or SMS
Identity opinions
Clear verified outcome
Linked to screening
Feeds sanctions checks
Verify the document against official records
Each request routes to the right source for the customer's country, returning a confidence-based opinion
- Passport, licence or national ID
- 60+ countries checked against official data
- Field-level match status
A sample identity verification card: an ID document being scanned, face-match confidence and a verified result.
Prove the document belongs to the person
A live selfie is matched to the document portrait, with liveness and manipulation tests
- Liveness and deepfake checks
- Duplicate portrait detection
- Print and screen detection
A sample FaceMatch result: a confidence ring filled to the match score with its checks.
One scan, identity and risk
The verified identity feeds straight into PEP and sanctions screening, so identity and risk are assessed in one record
- Verified identity linked
- Screening runs automatically
- One record for audit
A sample matching result: name variants scored against a threshold, with weak matches filtered out.
Document verification and FaceMatch for Japan
- 1,000+
- Global watchlists screened
- <1s
- Average screening response
- 24h
- Watchlist refresh cycle
- 195
- Countries covered
Assurance
ISO/IEC 27001:2022
ISO/IEC 27701:2019
GDPR
DORA
Three ways to verify
Web app
Interface in English and Japanese
Batch upload
CSV or XML with preview
REST API
Verification inside your systems
Common questions
Which transactions need stricter verification in Japan?
The Act names three categories: transactions where identity theft or falsified information is suspected, transactions with a customer in a designated country (Iran and North Korea are named), and transactions with a foreign PEP. These require a more stringent verification method than usual.
How long must verification records be kept?
Seven years under the Act on Prevention of Transfer of Criminal Proceeds, with the Foreign Exchange and Foreign Trade Act carrying its own seven-year retention rule for the firms it covers.
Which Japanese identity documents are supported?
MemberCheck verifies government-issued passports, driving licences and national identity cards. Coverage varies by country and document type, so talk to our team about the Japanese documents your customers present and we will confirm what is supported for your onboarding flow.
How is this different from the global identity verification page?
The product is the same. This page covers how it applies in Japan: verification at the time of transaction, the stricter method for high-risk transactions, and keeping details current. The global page describes the product for every market.
Further reading
More for Japan
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.