Identity in KYC Onboarding
When you run a KYC onboarding flow on the Lunixi platform, the identity risk snapshot that Identity Intelligence already built for the session is made available to the KYC decision as corroborating evidence. KYC pulls a compact riskSummary — device familiarity, network posture, related-session velocity and the reason codes behind them — and folds it into its own risk banding. Identity supplies the signals; KYC owns the verification decision.
Identity is an evidence provider here too. It tells KYC whether the device is known and stable, whether the session came in over an anonymising network, and how many related sessions it has seen — it never approves or rejects an applicant. That verdict belongs to KYC.
An in-platform bridge, not an endpoint
The link between the two services is internal to the platform. You do not call it from your integration — there is no merchant-facing request here. Inside the platform, the KYC service reads the snapshot through an internal gRPC bridge (getKycRiskSnapshot), authenticated with a platform-minted internalAuthToken scoped to identity:read. The only surfaces you integrate against remain the Identity SDK and the server-side API; this page describes what happens behind them.
The session is analysed by Identity
As the applicant moves through onboarding, the Identity SDK and backend build the usual risk snapshot — device fingerprint, continuity, network intelligence and related-session graph.
KYC requests a risk summary
At decision time, the KYC service asks Identity for the snapshot that matches the onboarding session (keyed by merchant, KYC session, session id, snapshot id or subject). The call is time-boxed with a short internal timeout.
The summary enters the KYC risk band
Identity returns a riskSummary. KYC's own evaluators read the network and session fields and adjust the applicant's risk band and enhanced-due-diligence requirement accordingly.
The reference is persisted
After the decision, KYC records that the session was identity-enriched and keeps a reference to the snapshot, so the enrichment is auditable and can feed ongoing monitoring.
What KYC reads — riskSummary
The bridge returns the identity snapshot plus a flattened riskSummary and the related-session view. The fields KYC consumes:
{
"riskSummary": {
"riskScore": 42,
"knownDevice": true,
"stableDevice": true,
"vpnDetected": false,
"proxyDetected": false,
"torDetected": false,
"networkPosture": "residential",
"networkRiskScore": 18,
"relatedSessionCount": 3,
"reasonCodes": ["KNOWN_DEVICE", "RESIDENTIAL_NETWORK"],
"tags": ["signal:identity_snapshot_linked"]
}
}| Field | What it tells KYC |
|---|---|
riskScore | Identity's top-line risk score for the session |
knownDevice | The device has been seen before for this merchant |
stableDevice | The fingerprint is stable across recent sessions |
vpnDetected / proxyDetected / torDetected | Whether the session arrived over an anonymising network |
networkPosture | The character of the network (e.g. residential vs hosting) |
networkRiskScore | Aggregate network risk for the session |
relatedSessionCount | How many related sessions the identity graph has linked |
reasonCodes | Explainable codes behind the summary |
tags | Machine tags carried on the snapshot |
The related-session graph is keyed by hashed account and actor identifiers, not raw personal data — see Onboarding Risk Signals. KYC never receives the raw PII behind a link, only the fact that a link exists.
Best-effort and fail-open
The snapshot is enrichment, not a gate. If Identity is turned off for the deployment (identityServiceEnabled is false), or the internal call times out or fails, KYC receives no snapshot and the onboarding decision continues without it — it does not stall or hard-fail on a missing summary. When the summary is present it strengthens the decision; when it is absent the flow degrades gracefully.
Treat identity enrichment as additive. A missing riskSummary is not a red flag — it means Identity had nothing to add for that session, or was unavailable. The KYC verification decision stands on its own evidence (documents, biometrics, sanctions) regardless.
The boundary
- Identity proves. It provides device, network and related-session evidence about how the session behaved.
- KYC decides. It weighs that evidence alongside document, biometric and sanctions checks and issues the verification outcome.
Nothing in the identity riskSummary blocks an applicant by itself. It shifts the risk band and can flag enhanced due diligence, but the accept/review/reject call is always KYC's.