Collect only approved information
Define required fields, consent, purpose and secure channels instead of gathering sensitive data through open inquiries.
Risk Service
eKYC
Coordinate supported onboarding intake, verification handoffs, exception reviews and records for people, businesses and merchants.
For financial and digital businesses that need a controlled onboarding workflow across customer systems, verification services and human review.
Data intakeVerification handoffException reviewDecision record
Service outcomes
Keep onboarding checks, exceptions and decisions connected.
These are operating goals, not performance guarantees. Results depend on scope, participants, implementation and customer operations.
Route exceptions consistently
Send unsupported, mismatched, incomplete or higher-risk cases to the responsible reviewer.
Keep the decision trail clear
Relate verification responses, review notes, status and decision owner to the onboarding case.
Coverage & fit
Fit onboarding checks to the subject, jurisdiction and customer policy.
Documents, registries, biometrics, sanctions or other checks are not assumed. Each data source, vendor, subject type and legal basis must be confirmed.
Individuals
Approved identity and onboarding steps for supported person-level customer or user journeys.
Businesses
Supported organization, representative, ownership or control reviews where data and services are available.
Merchants
Coordinate business review with website, product and payment-risk evidence where separately scoped.
Ongoing review
Re-open or refresh approved checks after policy, expiry, event or risk triggers.
Verification is not automatic compliance
A verification response is one input. The customer retains its legal, onboarding, AML/CFT, sanctions, risk and customer-acceptance responsibilities.
Priority use cases
Use eKYC where onboarding needs explicit data and exception paths.
Fintech customer onboarding
Coordinate approved person-level data and verification status before the customer makes an account decision.
Business onboarding
Bring organization, representative and ownership checks into one controlled case workflow where supported.
Merchant due diligence
Relate business verification to website and payment-risk review without treating them as the same check.
Periodic refresh
Re-run approved checks and review changed or expired evidence under customer policy.
Core capabilities
Coordinate onboarding data, checks and human decisions.
The customer approves the subject types, data, vendors, thresholds, exception rules, retention and decision ownership.
Structured intake
Capture approved onboarding fields, consent and case references through the authorized channel.
Verification-service handoff
Send supported checks to approved providers or data sources where integrated.
Response normalization
Map supported provider responses to agreed case statuses without hiding source detail.
Exception queue
Route incomplete, mismatched, unavailable or policy-triggered cases to human review.
Decision record
Record the responsible decision, reason, evidence references and relevant timestamps.
Refresh and monitoring triggers
Open approved re-review activity after expiry, change or other customer-defined events.
Integration & deployment
Integrate eKYC through secure onboarding channels.
Technical design covers data minimization, consent, provider credentials, secure evidence access, status events, retention, deletion and reviewer permissions.
Request technical documentation →Customer journey
Embed or connect the approved intake step in the customer’s onboarding experience where supported.
Verification providers
Connect only confirmed services and data sources under the applicable commercial and data arrangements.
Case management
Return statuses, exceptions and evidence references to the responsible reviewer or customer system.
Secure operations
Keep sensitive documents and personal data out of public website and ordinary email channels.
How it works
Move an onboarding case from intake to customer decision.
Vellfi can coordinate the workflow; the customer or allocated responsible party makes the onboarding decision.
- 1
Collect. Receive approved data and consent through the authorized onboarding channel.
- 2
Check. Send supported verification requests to the agreed services or sources.
- 3
Normalize. Relate responses and evidence references to the onboarding case.
- 4
Review. Route exceptions or policy triggers to the responsible reviewer.
- 5
Decide and record. Record the customer’s approved outcome, reason and next action.
Illustrative scenario—not a customer case study
A fintech is combining several onboarding checks into one customer journey.
Context
Identity, business, sanctions and manual-review responses currently arrive in different systems with inconsistent statuses.
ChallengeReviewers spend time reconciling responses and cannot easily see why a case was escalated or decided.
Possible approach
Vellfi scopes approved intake fields, supported provider handoffs, normalized statuses, exception rules and reviewer records under the customer’s policy.
Potential operating effectThe fintech receives a defined case flow and decision trail. Acceptance, compliance and fraud outcomes remain its responsibility and are not guaranteed.
Responsibilities & availability
Allocate data, verification and decision responsibilities explicitly.
Customer
Owns lawful basis, notices, onboarding policy, risk appetite, regulatory duties and final customer decisions.
Vellfi
Provides only the supported workflow, provider integration, statuses and records included in scope.
Verification providers
Supply contracted checks, sources or evidence under their own coverage, terms and data roles.
Reviewer
Examines exceptions and makes the decision allocated by customer policy.
Sensitive data requires approved channels
Do not send identity documents, biometric data, sanctions files, credentials or live onboarding cases through the Vellfi public contact form or ordinary email.
Next step
Map your onboarding checks and exception paths.
Share subject types, jurisdictions, current providers, statuses and reviewer responsibilities without sending personal documents or live case data.
FAQ
eKYC: common questions
What does eKYC mean on this site?
It refers to supported digital onboarding workflows that coordinate approved data, verification services, exceptions and review records.
Does eKYC automatically satisfy KYC or AML rules?
No. Compliance depends on applicable law, customer policy, checks, evidence, implementation and responsible decisions.
Which documents or biometric checks are supported?
No universal list is claimed. Subject type, jurisdiction, provider, document and biometric availability must be confirmed.
Can businesses and merchants be reviewed?
Potentially, where organization, representative, ownership and merchant checks are supported and included in scope.
How are exceptions handled?
The customer defines which responses require more evidence, re-checking, manual review or rejection and who owns the decision.
Where is onboarding data stored?
Hosting, transfer, access, retention and deletion are agreed for each deployment and data role.
What should be shared in an initial discussion?
Subject types, markets, existing providers, case statuses, exception categories and process requirements are useful; sensitive personal data is not.