eKYC
Introduction
Unlike traditional document-based identity verification, eKYC validates personal information directly against authoritative databases such as government registries and credit bureaus, enabling a faster, lower-friction onboarding experience.
eKYC is ideal when you want to verify identity attributes (name, date of birth, address, national identifiers) without requiring the individual to upload identity documents. This is particularly useful in markets where database-driven KYC verification is recognized by regulators and widely adopted by financial institutions.
Dotfile is partnering with GBG for eKYC verification. GBG is a global identity verification provider that validates personal information against government registries, credit bureaus, and other authoritative data sources across 45+ countries.
The verification profile for each country is pre-configured by GBG’s professional services team. Each profile defines which data sources are queried and which codes determine the outcome of the check.
eKYC vs. ID Verification
Dotfile offers two approaches to identity verification. Choosing the right one depends on your regulatory requirements and the user experience you want to provide:
| eKYC Check | ID Verification Check | |
|---|---|---|
| Method | Database verification against government and credit bureau records | Document capture and biometric comparison |
| User interaction | None - fully internal check, no end-user action required | End-user uploads ID document and takes a selfie |
| Friction | Low - instant, no document upload needed | Higher - requires the user to provide documents |
| Speed | Instant (synchronous result) | May take a few seconds to minutes |
| Best for | Markets where database KYC is accepted; pre-screening; low-friction onboarding | Regulatory requirements mandating document-level verification; high-risk onboarding |
Both check types can be used together in a verification template. For example, you might run an eKYC check first for quick validation, and escalate to ID Verification only when needed.
How It Works
The eKYC check is an internal check: it does not require any end-user interaction. When you launch an eKYC check, Dotfile sends the individual’s information to the verification provider, who validates it against national databases in real time. The result is returned instantly, typically in under a second.
Key Concepts
• Database verification: Identity attributes are validated against trusted third-party data sources (government records, credit bureaus) rather than by reviewing an uploaded document.
• Country-specific profiles: Each country has a dedicated verification profile that determines which data sources are queried and which identifiers are required or optional. These profiles can be adjusted upon request.
• Field-level results: Each piece of information (first name, last name, date of birth, address) is individually verified and returns a match status.
• Multi-source verification: Dotfile’s default configuration uses 2-source matching whenever available. The provider query at least two data sources (e.g. credit bureaus, government registries) before validating the identity. When a mismatch occurs, source-level details are displayed so you can understand which database returned the discrepancy. Depending on your regulatory requirements, you can opt for a verification against a single source.
• Matching: A data source counts as a match when it successfully verifies a combination of identity fields. The standard matching logic is:
-
Name + Address = 1 match
-
Name + Date of Birth = 1 match
-
Name + Address + Date of Birth = stronger match (higher confidence score)
For a 2-source matching (Dotifle’s default configuration), the individual’s data must match on at least two independent sources. For example, if Source A matches on name + address and Source B matches on name + date of birth, this counts as a 2-source match and identity is validated.
All countries support partial (fuzzy) matching by default. This means that minor variations in names such as nicknames, abbreviations, or small typos (e.g. “Rob” matching “Robert”) are accepted. This significantly improves pass rates without compromising accuracy.
Launching an eKYC Check
You can launch an eKYC check from any individual profile page by adding a new check and selecting eKYC. The check is a one-click action - no additional form or configuration is needed at launch time.
The system automatically detects the country from the individual’s residence address and selects the appropriate verification profile. If the country is not in your workspace’s allowed countries list, the check cannot be created.
Prerequisites
Before launching an eKYC check, ensure the individual has the following information filled in:
• Required: First name, Last name, Address, Date of birth
• Country-specific: National identifier (e.g. SSN for the US, CPF for Brazil)
The more information you provide, the more accurate and reliable the verification result will be. Even if optional fields are missing, the check can still be launched - the provider will return partial results based on the available data. We can provide you with the full list of required / recommended information by country - please ask to [email protected].
Using Templates
You can also use a Template to automatically launch an eKYC check on all the individuals in a case that require it (e.g. Beneficial Owner, Legal Representative).
Check Results
After launching an eKYC check, the result is determined based on how well the individual’s information matches the data found in national databases. There are three possible outcomes:
| Result | Description |
| Approved | The individual’s identity has been verified successfully. Key attributes match the reference data. The check is automatically approved. |
| Need Review | Some attributes match, but others could not be fully verified or returned warnings. A compliance officer must manually review the results and decide to approve or reject. |
| Rejected | Critical identity attributes do not match. The individual’s identity could not be verified. The check is automatically rejected. |
Field-Level Verification
Each field submitted for verification is individually assessed and returns one of the following statuses:
| Status | Indicator | Description |
| Match | ✓ | The field value matches the reference data from the database. |
| Mismatch | ✗ | The field value does not match the reference data. This may indicate an error or a potential identity inconsistency. |
| Warning | ⚠ | A partial match or the data requires attention. For example, the year of birth matches but the day could not be verified. |
| No Match | — | No data was found for this field in the reference database. The field could not be verified. |
The main fields verified by the eKYC check are: First Name, Last Name, Date of Birth, and Address. Other fields can be verified when provided (SSN number for instance). When a mismatch is detected and multiple data sources were queried, a tooltip will indicate which source returned the discrepancy.
Decision Logic
The eKYC check result is determined in two steps: first, the verification provider scores the individual’s data against available databases and returns a provider-level decision; then, Dotfile maps that decision to one of three check statuses.
Provider Scoring
The provider compares the individual’s data against one or more data sources. Each source that finds a match contributes to a score based on the fields that were verified (name, address, date of birth, national identifier). The total score determines one of four provider-level decisions:
-
Alert: Negative information was found (e.g. deceased record, fraud flag).
-
Refer: The data could not be sufficiently matched against any source.
-
1 Source Pass: The data was verified against one data source.
-
2 Source Pass: The data was verified against two independent data sources (strongest level of verification).
The exact screening criteria vary by country:
USA:
-
2× name & address only = Refer (not sufficient)
-
2× name & date of birth = Pass
-
1× name, address & DOB + 1× name & SSN = Pass
-
1× name & DOB + 1× name & address = Pass
United Kingdom:
-
1× name, address & DOB = 1 Source Pass
-
1× name, address & DOB + 1× name & address = 2 Source Pass
All other countries (standard scoring):
-
1× name, address & DOB = 1 Source Pass
-
1× name, address & DOB + 1× name & address (minimum) = 2 Source Pass
Where only 1-source matching is available: forename, surname, DOB & address = Pass
Dotfile Decision Mapping
Dotfile maps the provider-level decision to one of three check statuses:
| Provider Decision | Dotfile Status | Action |
| Alert | Rejected | Automatically rejected - if auto reject was selected |
| Refer | Need Review | Requires manual review by a compliance officer |
| 1 Source Pass | Need Review | Requires manual review by a compliance officer |
| 2 Source Pass | Approved | Automatically approved - if auto approve was selected |
In summary: only a 2 Source Pass triggers automatic approval (if auto approve was selected). An Alert triggers automatic rejection (if auto reject was selected). All other outcomes (Refer, 1 Source Pass) require manual review by your compliance team.
Common Reasons for a Failed Check
If a check returns a “Need Review” or “Rejected” result, the most common causes are:
-
Poor input data quality (misspelled name, incorrect address format, missing fields)
-
The individual is not present in the available data sources (e.g. young person, recent immigrant, rural address)
-
Diacritics or character encoding issues (e.g. é vs e, common in French names)
-
Address standardisation mismatches (abbreviations, missing postal code)
To improve pass rates, ensure you collect as many fields as possible (especially national identifiers and phone numbers), and enforce proper address formatting in your data collection forms.
Workspace Settings
eKYC settings are configured at the workspace level in the Settings section. You can configure:
• Automatic approval: When enabled, checks that return a PASS decision are automatically approved without manual review.
• Automatic rejection: When enabled, checks that return a FAIL decision are automatically rejected without manual review.
API
eKYC checks can be created and retrieved via the Dotfile REST API.
Webhook events are also available to notify your systems when an eKYC check is completed or reviewed. You can learn more in our API documentation.
Updated 4 days ago
