Skip to content

The Snapshot Problem

A fresh selfie is a moment. The next action still needs a binding.

An identity check can establish who is present when the check runs. It does not, by itself, establish who controls the session afterward—or what that person is approving.

A key returning is not a person returning. And a person returning is not proof that they approved this transfer, this account change, or this caller’s request.

Reverification is not session binding. Kenshiki Pulse is built to connect the identity evidence, the device’s history, and the person’s approval of the action that matters.

Identity proofing, authentication and continuous proof

Identity proofing checks the claimed identity and its relationship to the applicant. Authentication checks control of the means of access associated with an account. Neither check, by itself, establishes approval of the next action.

Continuous proof is the connection Pulse aims to build between that starting identity evidence, later device history, and approval of a specific action. The service must verify those bindings; a signed history alone does not establish identity. Compare the controls and their boundaries.

What returning-user checks establish

A common flow starts with enrollment, then asks a returning user for a fresh face check against the earlier record. Products can add liveness, device signals, risk analysis, and checks at sensitive actions. Those controls matter.

The question for the service is what happens next: how does the result bind to the session and the exact action being authorized? A successful match alone does not answer it.

These are examples from the vendors’ own product descriptions, not a claim that each example describes their entire platform.

CLEAR

Its Docusign integration lets existing CLEAR members verify with a selfie. New members can create an account within the signing flow. CLEAR announcement.

Jumio

selfie.DONE reverifies returning users with a selfie against an existing identity record. Its announcement also describes liveness and fraud-risk checks. Jumio announcement.

Socure

Selfie Reverification compares a fresh selfie with a previously accepted document-verification headshot, adding liveness, injection protection, device and behavioral signals. Socure documentation.

Persona

Reverify checks a returning person against their existing account. Persona describes checks for sensitive actions, including large transfers, and retains verification inquiries. Persona product explanation.

Incode

Its Auth0 integration supports enrollment, returning-user face authentication, configurable reverification, and login blocking. Results populate account metadata and an identity-token claim. Incode integration explanation.

Veriff

Biometric Authentication checks a returning user against an enrolled face template. Veriff also describes device, network, and behavioral risk signals and checks at high-value actions. Veriff product description.

iProov

Face Verifier compares a face scan with a pre-enrolled biometric template and applies Dynamic Liveness. It supports primary, multifactor, and step-up authentication. iProov product description.

The gap is between the check and the decision

For a web session: bind the approval to the intended service, session, and request. An identity claim inside a token is evidence the application must use; it is not the application’s entire authorization policy.

For a call: establish whose request is being presented and what the person is authorizing. Completing a check through a separate channel does not, by itself, establish the caller’s authority.

For coached fraud: recognizing the real person is not enough. A real person can be manipulated into approving a harmful action. Show the institution’s authenticated request and the exact action before approval. No identity match alone proves informed intent.

For later scrutiny: retain evidence linking enrollment, subsequent activity, and the decision. A match result can be part of that record. It is not, by itself, the whole chain.

What Pulse connects

Pulse starts with identity evidence bound to a key on the person’s device. It records signed device activity between checks. When an action needs approval, the person uses the device’s face or fingerprint check to authorize that key.

Capture, storage, signing, and continuity are available for SDK evaluation. The verifier and user-held presentation are planned components. Web and call integrations must enforce the session and request bindings described below.

What the service must establish at decision time

On narrow screens, scroll the comparison sideways.

DecisionWhat a fresh identity check contributesWhat the integration still must establish
Who is present?A current match to the enrolled identity, with the check’s supporting signals.The relationship between that identity, the device key, and the current approval.
What happened between checks?Evidence from the checks and any additional monitoring the product supplies.The signed activity history, its continuity, and any gaps relevant to this decision.
What is being approved?A verification result the application can use in its decision.The intended service, current session, exact action, and request-bound approval.
Can the decision be examined?The retained verification results and supporting records.A verifiable record connecting identity, history, request, and approval.

A verdict is an input. The chain is what connects it to the decision.

There is also a supply chain behind the check

The brand on the screen may use other companies for document analysis, face checks, manual review, or data extraction. Published supplier registries and partnership reports make some of those relationships visible.

A company can sell its own verification service and supply technology to other brands. Regula, for example, supplies the document-checking component described in Daon TrustX documentation and in Regula’s customer stories for Luciditi and REACT. SDKs can run inside a customer’s application or infrastructure, so supplier registries alone do not reveal the whole stack.

Explore in either direction: what a brand uses, or which brands use a component. Select a company name to follow the connection. Each card identifies its source and scope; optional services, backup suppliers, historical evidence, and corporate ownership are distinguished. These are documented examples, not a complete market inventory or a statement about every customer’s deployment.

The visual shows technology and data together. Start with ID.me or Login.gov to inspect their suppliers, or follow LexisNexis and Socure upstream. The data branches follow a different dependency: the records and intermediaries behind a service. The LexisNexis examples are scoped to its UK Business Services notice. Socure’s examples distinguish named product integrations, reseller services, customer-credential connectors, and unnamed data-provider categories. Each hop is sourced; a multi-hop path does not establish that every underlying field reaches the final service.

Behind the brand

Behind the check: technology and data.

Follow the suppliers behind the service, then the sources behind those suppliers. Every connection carries its own evidence and scope.

31 technology links 47 data-source links

Kenshiki Pulse

United States

Component-use coverage not yet collected customer coverage not yet collected

3 source / integration links · 0 downstream data users in this collection

Kenshiki’s declared verification chain: ICAO for passports; AAMVA for state ID; TransUnion for SSN; Aduna for phone checks. Face matching and state-ID processing use Kenshiki’s own code. AAMVA remains the state-ID record check.

Passport standards & trust

ICAO · passport standards and trust framework ↗
Passport verification follows ICAO standards. ICAO is the standards authority, not a verification vendor.

The supply chain on the mapOrganizations expanded · country flags retained
Kenshiki Pulse: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Kenshiki Pulse → AAMVA: State-ID record verificationKenshiki Pulse → TransUnion (US verification source): SSN verificationKenshiki Pulse → Aduna: Phone verification 🇺🇸 United States Kenshiki PulseSelected service · follow its suppliers → 🌐 Country not asserted AdunaPhone verificationDocumented 🇺🇸 United States AAMVAState-ID record verificationDocumented 🇺🇸 United States TransUnion (US verification source)SSN verificationDocumented Kenshiki Pulse: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Kenshiki Pulse → AAMVA: State-ID record verificationKenshiki Pulse → TransUnion (US verification source): SSN verificationKenshiki Pulse → Aduna: Phone verification 🇺🇸 United States Kenshiki PulseSelected service · follow its suppliers → 🌐 Country not asserted AdunaPhone verificationDocumented 🇺🇸 United States AAMVAState-ID record verificationDocumented 🇺🇸 United States TransUnion (US verification source)SSN verificationDocumented

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Kenshiki Pulseuses suppliers & sources below ↓
Country not asserted
1 entry
United States
2 entries

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Data sources and integrations for Kenshiki Pulse
  • AAMVA United States State-ID record verification Pulse state-ID verification · Supported service coverageDeclared data source Documented · 2026-10-17

    State-ID records are checked through AAMVA. State-ID processing uses Kenshiki’s own code.

    Operator declaration
  • TransUnion (US verification source) United States SSN verification Pulse SSN verification · Supported service coverageDeclared data source Documented · 2026-10-17

    TransUnion provides the SSN check.

    Operator declaration
  • Aduna 🌐 Country not asserted Phone verification Pulse phone verification · Supported service coverageDeclared data source Documented · 2026-10-17

    Aduna provides the phone check.

    Operator declaration
Who uses Kenshiki Pulse?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Kenshiki Pulse use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Kenshiki Pulse?

No downstream data users documented in this collection. This does not establish that there are none.

Kenshiki Pulse’s own products · in-house code

Ontic Labs, Inc., doing business as Kenshiki Labs, is based in Tacoma, Washington, United States. Location source ↗

LexisNexis Risk Solutions

United States

7 component links documented supplies 1 brands in this collection

9 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
LexisNexis Risk Solutions: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Acuant Inc.: Image processingLexisNexis Risk Solutions → IDVerse: Document verificationLexisNexis Risk Solutions → Veridas: Image processingLexisNexis Risk Solutions → Veriff: Image processingLexisNexis Risk Solutions → Au10tix: Document verificationLexisNexis Risk Solutions → TrustID: Document verificationLexisNexis Risk Solutions → Resistant AI: Document verificationLogin.gov → LexisNexis Risk Solutions: TrueID document authenticationLexisNexis Risk Solutions → Experian Limited: Identity and credit-reference dataLexisNexis Risk Solutions → Equifax Limited: Identity and credit-reference dataLexisNexis Risk Solutions → Crediva Limited: Identity and credit-reference dataLexisNexis Risk Solutions → Registry Trust: Judgment recordsLexisNexis Risk Solutions → Companies House: Directorship recordsLexisNexis Risk Solutions → General Register Office: Civil-registration recordsLexisNexis Risk Solutions → HM Land Registry: Property recordsLexisNexis Risk Solutions → Royal Mail plc: Commercial dataLexisNexis Risk Solutions → Vocalink Ltd: Commercial dataLogin.gov → LexisNexis Risk Solutions: Instant Verify identity resolutionLogin.gov → LexisNexis Risk Solutions: Phone Finder identity correlationLogin.gov → LexisNexis Risk Solutions: ThreatMetrix device-risk assessmentEquifax Limited → UK financial-account providers: Account-performance informationEquifax Limited → Registry Trust: Judgment-register informationExperian Limited → UK financial-account providers: Account-performance informationExperian Limited → Registry Trust: Judgment-register information 🇺🇸 United States LexisNexis Risk SolutionsSelected service · follow its suppliers → 🇨🇿 Czech Republic Resistant AIDocument verificationDocumented 🇪🇪 Estonia VeriffImage processingBackup supplier 🇮🇱 Israel Au10tixDocument verificationDocumented 🇪🇸 Spain VeridasImage processingBackup supplier 🇬🇧 United Kingdom Companies HouseDirectorship recordsDocumented 🇬🇧 United Kingdom Crediva LimitedIdentity and credit-reference dataDocumented 🇬🇧 United Kingdom Equifax LimitedIdentity and credit-reference dataDocumented 🇬🇧 United Kingdom Experian LimitedIdentity and credit-reference dataDocumented 🇬🇧 United Kingdom General Register OfficeCivil-registration recordsDocumented 🇬🇧 United Kingdom HM Land RegistryProperty recordsDocumented 🇬🇧 United Kingdom IDVerseDocument verificationDocumented 🇬🇧 United Kingdom Registry TrustJudgment records · Judgment-register informationDocumented 🇬🇧 United Kingdom Royal Mail plcCommercial dataDocumented 🇬🇧 United Kingdom TrustIDDocument verificationDocumented 🇬🇧 United Kingdom · Source category UK financial-account providersAccount-performance informationDocumented 🇬🇧 United Kingdom Vocalink LtdCommercial dataDocumented 🇺🇸 United States Acuant Inc.Image processingDocumented 🇺🇸 United States Login.govDocumented customer / upstream source LexisNexis Risk Solutions: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Acuant Inc.: Image processingLexisNexis Risk Solutions → IDVerse: Document verificationLexisNexis Risk Solutions → Veridas: Image processingLexisNexis Risk Solutions → Veriff: Image processingLexisNexis Risk Solutions → Au10tix: Document verificationLexisNexis Risk Solutions → TrustID: Document verificationLexisNexis Risk Solutions → Resistant AI: Document verificationLogin.gov → LexisNexis Risk Solutions: TrueID document authenticationLexisNexis Risk Solutions → Experian Limited: Identity and credit-reference dataLexisNexis Risk Solutions → Equifax Limited: Identity and credit-reference dataLexisNexis Risk Solutions → Crediva Limited: Identity and credit-reference dataLexisNexis Risk Solutions → Registry Trust: Judgment recordsLexisNexis Risk Solutions → Companies House: Directorship recordsLexisNexis Risk Solutions → General Register Office: Civil-registration recordsLexisNexis Risk Solutions → HM Land Registry: Property recordsLexisNexis Risk Solutions → Royal Mail plc: Commercial dataLexisNexis Risk Solutions → Vocalink Ltd: Commercial dataLogin.gov → LexisNexis Risk Solutions: Instant Verify identity resolutionLogin.gov → LexisNexis Risk Solutions: Phone Finder identity correlationLogin.gov → LexisNexis Risk Solutions: ThreatMetrix device-risk assessmentEquifax Limited → UK financial-account providers: Account-performance informationEquifax Limited → Registry Trust: Judgment-register informationExperian Limited → UK financial-account providers: Account-performance informationExperian Limited → Registry Trust: Judgment-register information 🇺🇸 United States LexisNexis Risk SolutionsSelected service · follow its suppliers → 🇨🇿 Czech Republic Resistant AIDocument verificationDocumented 🇪🇪 Estonia VeriffImage processingBackup supplier 🇮🇱 Israel Au10tixDocument verificationDocumented 🇪🇸 Spain VeridasImage processingBackup supplier 🇬🇧 United Kingdom Companies HouseDirectorship recordsDocumented 🇬🇧 United Kingdom Crediva LimitedIdentity and credit-reference dataDocumented 🇬🇧 United Kingdom Equifax LimitedIdentity and credit-reference dataDocumented 🇬🇧 United Kingdom Experian LimitedIdentity and credit-reference dataDocumented 🇬🇧 United Kingdom General Register OfficeCivil-registration recordsDocumented 🇬🇧 United Kingdom HM Land RegistryProperty recordsDocumented 🇬🇧 United Kingdom IDVerseDocument verificationDocumented 🇬🇧 United Kingdom Registry TrustJudgment records · Judgment-register informationDocumented 🇬🇧 United Kingdom Royal Mail plcCommercial dataDocumented 🇬🇧 United Kingdom TrustIDDocument verificationDocumented 🇬🇧 United Kingdom · Source category UK financial-account providersAccount-performance informationDocumented 🇬🇧 United Kingdom Vocalink LtdCommercial dataDocumented 🇺🇸 United States Acuant Inc.Image processingDocumented 🇺🇸 United States Login.govDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

LexisNexis Risk Solutionsuses suppliers & sources below ↓
Czech Republic
1 entry
Estonia
1 entry
Israel
1 entry
Spain
1 entry
United Kingdom
11 entries
United States
1 entry
Who uses LexisNexis Risk Solutions?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses LexisNexis Risk Solutions?
  • Login.gov United States TrueID document authentication Conditional · 2026-10-16

    Public implementation submits document images and, when the configured flow requires it, a selfie to TrueID. Commit date identifies source revision, not production activation or allocation. The permitted Acuant upstream hop is specific to TrueID; UK Business Services data sources are not composed into this path.

    Integration documentation
What does LexisNexis Risk Solutions use?
Who uses data from LexisNexis Risk Solutions?
  • Login.gov United States Instant Verify identity resolution Login.gov Instant Verify integration · United StatesProduct-specific integration Conditional · 2026-10-16

    Public implementation builds US identity-resolution requests. Production enablement and customer-specific data sources are not established by this code. No UK CRA-source path is inferred.

    Integration documentation
  • Login.gov United States Phone Finder identity correlation Login.gov Phone Finder integration · United StatesProduct-specific integration Conditional · 2026-10-16

    Public implementation sends identity attributes and a phone number to a configured Phone Finder workflow. This records an implemented interface, not current production allocation or underlying carrier suppliers.

    Integration documentation
  • Login.gov United States ThreatMetrix device-risk assessment Login.gov ThreatMetrix DDP integration · United StatesProduct-specific integration Conditional · 2026-10-16

    Public DDP implementation builds device-risk requests linked to a ThreatMetrix session identifier. Presence of this implementation does not establish which production transactions invoke it or an individual data-transfer route.

    Integration documentation
Data sources and integrations for LexisNexis Risk Solutions
  • Experian Limited United Kingdom Identity and credit-reference data Business Services · United KingdomDeclared data source Documented · 2025-12-17

    Named CRA source; supplied fields depend on the service.

    Processing notice
  • Equifax Limited United Kingdom Identity and credit-reference data Business Services · United KingdomDeclared data source Documented · 2025-12-17

    Named CRA source; supplied fields depend on the service.

    Processing notice
  • Crediva Limited United Kingdom Identity and credit-reference data Business Services · United KingdomDeclared data source Documented · 2025-12-17

    Named CRA source. Crediva is an LNRS affiliate.

    Processing notice
  • Registry Trust United Kingdom Judgment records Business Services · United KingdomSource example named in notice Documented · 2025-12-17

    Named source example in the notice; no specific contract or universal use established.

    Processing notice
  • Companies House United Kingdom Directorship records Business Services · United KingdomSource example named in notice Documented · 2025-12-17

    Named source example in the notice; no specific contract or universal use established.

    Processing notice
  • General Register Office United Kingdom Civil-registration records Business Services · United KingdomSource example named in notice Documented · 2025-12-17

    Named source example in the notice; no specific contract or universal use established.

    Processing notice
  • HM Land Registry United Kingdom Property records Business Services · United KingdomSource example named in notice Documented · 2025-12-17

    Named source example in the notice; no specific contract or universal use established.

    Processing notice
  • Royal Mail plc United Kingdom Commercial data Business Services · United KingdomSource example named in notice Documented · 2025-12-17

    Named source example in the notice; no specific contract or universal use established.

    Processing notice
  • Vocalink Ltd United Kingdom Commercial data Business Services · United KingdomSource example named in notice Documented · 2025-12-17

    Named source example in the notice; no specific contract or universal use established.

    Processing notice
Corporate ownership · separate from component use
  • RELX United Kingdom Netherlands Parent company Documented

    Corporate ownership; not a verification component.

    Ownership source
  • IDVerse United Kingdom Acquisition Documented · 2025-02-19

    LexisNexis announced completion of the IDVerse acquisition in February 2025.

    Ownership source

Company country for geographic context; not a processing or data-transfer route.

Entrust IDV

formerly Onfido United States

5 component links documented customer coverage not yet collected

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Entrust IDV: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Entrust IDV → Teleperformance: Human reviewEntrust IDV → Mas Callnet: Human reviewEntrust IDV → Concentrix: Human reviewEntrust IDV → TrustID: Fraud detectionEntrust IDV → FaceTec: Liveness / authentication 🇺🇸 United States Entrust IDVSelected service · follow its suppliers → 🇮🇳 India Mas CallnetHuman reviewOptional 🇮🇳 India TeleperformanceHuman reviewOptional 🇮🇳 India · 🇧🇬 Bulgaria · 🇻🇳 Vietnam ConcentrixHuman reviewDocumented 🇬🇧 United Kingdom TrustIDFraud detectionOptional 🇺🇸 United States FaceTecLiveness / authenticationHistorical evidence Entrust IDV: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Entrust IDV → Teleperformance: Human reviewEntrust IDV → Mas Callnet: Human reviewEntrust IDV → Concentrix: Human reviewEntrust IDV → TrustID: Fraud detectionEntrust IDV → FaceTec: Liveness / authentication 🇺🇸 United States Entrust IDVSelected service · follow its suppliers → 🇮🇳 India Mas CallnetHuman reviewOptional 🇮🇳 India TeleperformanceHuman reviewOptional 🇮🇳 India · 🇧🇬 Bulgaria · 🇻🇳 Vietnam ConcentrixHuman reviewDocumented 🇬🇧 United Kingdom TrustIDFraud detectionOptional 🇺🇸 United States FaceTecLiveness / authenticationHistorical evidence

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Entrust IDVuses suppliers & sources below ↓
Bulgaria
1 entry
India
3 entries
United Kingdom
1 entry
United States
1 entry
Vietnam
1 entry

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
What does Entrust IDV use?
Who uses Entrust IDV?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

Who uses data from Entrust IDV?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Entrust IDV

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

Persona

United States

4 component links documented customer coverage not yet collected

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Persona: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Persona → Anthropic: Data extraction & analysisPersona → OpenAI: Data extraction & analysisPersona → Groq: Data extraction & analysisPersona → Resistant AI: Document analysis 🇺🇸 United States PersonaSelected service · follow its suppliers → 🇨🇿 Czech Republic Resistant AIDocument analysisConditional 🇺🇸 United States AnthropicData extraction & analysisConditional 🇺🇸 United States GroqData extraction & analysisConditional 🇺🇸 United States OpenAIData extraction & analysisConditional Persona: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Persona → Anthropic: Data extraction & analysisPersona → OpenAI: Data extraction & analysisPersona → Groq: Data extraction & analysisPersona → Resistant AI: Document analysis 🇺🇸 United States PersonaSelected service · follow its suppliers → 🇨🇿 Czech Republic Resistant AIDocument analysisConditional 🇺🇸 United States AnthropicData extraction & analysisConditional 🇺🇸 United States GroqData extraction & analysisConditional 🇺🇸 United States OpenAIData extraction & analysisConditional

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Personauses suppliers & sources below ↓
Czech Republic
1 entry
United States
3 entries

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
What does Persona use?
  • Anthropic United States Data extraction & analysis Conditional · 2026-08-22

    Conditional service; registry listing does not mean every Persona check uses it.

    Supplier registry
  • OpenAI United States Data extraction & analysis Conditional · 2026-08-22

    Conditional service; registry listing does not mean every Persona check uses it.

    Supplier registry
  • Groq United States Data extraction & analysis Conditional · 2026-08-22

    Conditional service; registry listing does not mean every Persona check uses it.

    Supplier registry
  • Resistant AI Czech Republic Document analysis Conditional · 2026-08-22

    Conditional service in Persona’s registry; service country is the United States, distinct from Resistant AI’s Czech corporate location.

    Supplier registry
Who uses Persona?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

Who uses data from Persona?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Persona

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

ID.me

United States

5 component links documented customer coverage not yet collected

14 source / integration links · 0 downstream data users in this collection

This view combines different products and dates. Suppliers disclosed in 2022 are historical evidence; community-status checks, optional in-person verification and the announced Plaid integration have separate scopes. They are not all part of every identity check.

The supply chain on the mapOrganizations expanded · country flags retained
ID.me: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → iProov: Liveness detectionID.me → Paravision: Face recognitionID.me → Amazon Rekognition: Face recognitionID.me → AuthenticID: Document and biometric verificationID.me → Sterling: In-person retail-kiosk verification channelID.me → Experian (US verification source): Authoritative identity-record comparisonID.me → TeleSign: Authoritative identity-record comparisonID.me → Prove: Authoritative identity-record comparisonID.me → National Plan & Provider Enumeration System (NPPES): Authoritative identity-record comparisonID.me → TransUnion (US verification source): Authoritative identity-record comparisonID.me → Prove: Mobile-device digital riskID.me → TeleSign: Mobile-device digital riskID.me → FingerprintJS: Mobile-device digital riskID.me → Fraud.net: Behavior analysisID.me → National Student Clearinghouse: Student and alumni status checksID.me → USAA: Military and veteran status checksID.me → SCRA military-status service: Military and veteran status checksID.me → US Department of Veterans Affairs: Military and veteran status checksID.me → Plaid: Benefit-payment bank-account verificationNational Student Clearinghouse → Participating US colleges and universities: Institution-reported enrollment records 🇺🇸 United States ID.meSelected service · follow its suppliers → 🇬🇧 United Kingdom iProovLiveness detectionHistorical evidence 🇺🇸 United States Amazon RekognitionFace recognitionHistorical evidence 🇺🇸 United States AuthenticIDDocument and biometric verificationHistorical evidence 🇺🇸 United States Experian (US verification source)Authoritative identity-record comparisonHistorical evidence 🇺🇸 United States FingerprintJSMobile-device digital riskHistorical evidence 🇺🇸 United States Fraud.netBehavior analysisHistorical evidence 🇺🇸 United States National Plan & Provider Enumeration System (NPPES)Authoritative identity-record comparisonHistorical evidence 🇺🇸 United States National Student ClearinghouseStudent and alumni status checksOptional 🇺🇸 United States ParavisionFace recognitionDocumented 🇺🇸 United States · Source category Participating US colleges and universitiesInstitution-reported enrollment recordsDocumented 🇺🇸 United States PlaidBenefit-payment bank-account verificationConditional 🇺🇸 United States ProveAuthoritative identity-record comparison · Mobile-device digital riskHistorical evidence 🇺🇸 United States · Source category SCRA military-status serviceMilitary and veteran status checksOptional 🇺🇸 United States SterlingIn-person retail-kiosk verification channelOptional 🇺🇸 United States TeleSignAuthoritative identity-record comparison · Mobile-device digital riskHistorical evidence 🇺🇸 United States TransUnion (US verification source)Authoritative identity-record comparisonHistorical evidence 🇺🇸 United States US Department of Veterans AffairsMilitary and veteran status checksOptional 🇺🇸 United States USAAMilitary and veteran status checksOptional ID.me: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → iProov: Liveness detectionID.me → Paravision: Face recognitionID.me → Amazon Rekognition: Face recognitionID.me → AuthenticID: Document and biometric verificationID.me → Sterling: In-person retail-kiosk verification channelID.me → Experian (US verification source): Authoritative identity-record comparisonID.me → TeleSign: Authoritative identity-record comparisonID.me → Prove: Authoritative identity-record comparisonID.me → National Plan & Provider Enumeration System (NPPES): Authoritative identity-record comparisonID.me → TransUnion (US verification source): Authoritative identity-record comparisonID.me → Prove: Mobile-device digital riskID.me → TeleSign: Mobile-device digital riskID.me → FingerprintJS: Mobile-device digital riskID.me → Fraud.net: Behavior analysisID.me → National Student Clearinghouse: Student and alumni status checksID.me → USAA: Military and veteran status checksID.me → SCRA military-status service: Military and veteran status checksID.me → US Department of Veterans Affairs: Military and veteran status checksID.me → Plaid: Benefit-payment bank-account verificationNational Student Clearinghouse → Participating US colleges and universities: Institution-reported enrollment records 🇺🇸 United States ID.meSelected service · follow its suppliers → 🇬🇧 United Kingdom iProovLiveness detectionHistorical evidence 🇺🇸 United States Amazon RekognitionFace recognitionHistorical evidence 🇺🇸 United States AuthenticIDDocument and biometric verificationHistorical evidence 🇺🇸 United States Experian (US verification source)Authoritative identity-record comparisonHistorical evidence 🇺🇸 United States FingerprintJSMobile-device digital riskHistorical evidence 🇺🇸 United States Fraud.netBehavior analysisHistorical evidence 🇺🇸 United States National Plan & Provider Enumeration System (NPPES)Authoritative identity-record comparisonHistorical evidence 🇺🇸 United States National Student ClearinghouseStudent and alumni status checksOptional 🇺🇸 United States ParavisionFace recognitionDocumented 🇺🇸 United States · Source category Participating US colleges and universitiesInstitution-reported enrollment recordsDocumented 🇺🇸 United States PlaidBenefit-payment bank-account verificationConditional 🇺🇸 United States ProveAuthoritative identity-record comparison · Mobile-device digital riskHistorical evidence 🇺🇸 United States · Source category SCRA military-status serviceMilitary and veteran status checksOptional 🇺🇸 United States SterlingIn-person retail-kiosk verification channelOptional 🇺🇸 United States TeleSignAuthoritative identity-record comparison · Mobile-device digital riskHistorical evidence 🇺🇸 United States TransUnion (US verification source)Authoritative identity-record comparisonHistorical evidence 🇺🇸 United States US Department of Veterans AffairsMilitary and veteran status checksOptional 🇺🇸 United States USAAMilitary and veteran status checksOptional

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

ID.meuses suppliers & sources below ↓
United Kingdom
1 entry
  • iProov →
    Verification technology

    Liveness detection

    Historical evidence · 2022
    Scope & evidence

    ID.me’s 2022 white paper names iProov for presentation attack detection; current deployment not established here.

    ID.me: Anti-Bias White Paper, page 12 ↗
United States
16 entries

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
What does ID.me use?
  • iProov United Kingdom Liveness detection Historical evidence · 2022

    ID.me’s 2022 white paper names iProov for presentation attack detection; current deployment not established here.

    Integration documentation
  • Paravision United States Face recognition Documented · 2025-07-17

    Paravision’s July 2025 announcement names ID.me’s deployment of Identity AI.

    Company announcement
  • Amazon Rekognition United States Face recognition Historical evidence · 2022

    Reported use in January 2022; current deployment not established here.

    Press report
  • AuthenticID United States Document and biometric verification Historical evidence · 2022-03-25

    ID.me’s March 2022 response groups AuthenticID with document authenticity and credential-photo/selfie comparison partners. It does not assign individual subfunctions; current deployment not established.

    Integration documentation
  • Sterling United States In-person retail-kiosk verification channel Optional

    ID.me offers an optional in-person pathway through Sterling; this edge represents retail-channel infrastructure, not a data feed or every online verification.

    Integration documentation
Data sources and integrations for ID.me
  • Experian (US verification source) United States Authoritative identity-record comparison Identity-record checks disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    Integration documentation
  • TeleSign United States Authoritative identity-record comparison Identity-record checks disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    Integration documentation
  • Prove United States Authoritative identity-record comparison Identity-record checks disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    Integration documentation
  • National Plan & Provider Enumeration System (NPPES) United States Authoritative identity-record comparison Identity-record checks disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    Integration documentation
  • TransUnion (US verification source) United States Authoritative identity-record comparison Identity-record checks disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    Integration documentation
  • Prove United States Mobile-device digital risk Mobile-device risk disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    ID.me named this mobile-risk partner in March 2022; current deployment, underlying carriers and exact data fields not established.

    Integration documentation
  • TeleSign United States Mobile-device digital risk Mobile-device risk disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    ID.me named this mobile-risk partner in March 2022; current deployment, underlying carriers and exact data fields not established.

    Integration documentation
  • FingerprintJS United States Mobile-device digital risk Mobile-device risk disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    ID.me named this mobile-risk partner in March 2022; current deployment, underlying carriers and exact data fields not established.

    Integration documentation
  • Fraud.net United States Behavior analysis Behavior analysis disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    Named by ID.me in March 2022; current deployment and exact inputs not established.

    Integration documentation
  • National Student Clearinghouse United States Student and alumni status checks Attribute exchange: students and alumni · United StatesProduct-specific integration Optional

    Current ID.me developer documentation names NSC as an authoritative source option for student/alumni community verification. Document review is an alternative; this is not every legal-identity check.

    Integration documentation
  • USAA United States Military and veteran status checks Attribute exchange: military and veterans · United StatesProduct-specific integration Optional

    Current ID.me documentation lists USAA, SCRA or VA as example authoritative sources for military/veteran community status; official email or document review are alternatives. No universal use or commercial subcontract inferred.

    Integration documentation
  • SCRA military-status service United States Source category · individual suppliers not identified Military and veteran status checks Attribute exchange: military and veterans · United StatesProduct-specific integration Optional

    Current ID.me documentation lists USAA, SCRA or VA as example authoritative sources for military/veteran community status; official email or document review are alternatives. No universal use or commercial subcontract inferred.

    Integration documentation
  • US Department of Veterans Affairs United States Military and veteran status checks Attribute exchange: military and veterans · United StatesProduct-specific integration Optional

    Current ID.me documentation lists USAA, SCRA or VA as example authoritative sources for military/veteran community status; official email or document review are alternatives. No universal use or commercial subcontract inferred.

    Integration documentation
  • Plaid United States Benefit-payment bank-account verification Announced government benefit-payment integration · United StatesProduct-specific integration Conditional · 2026-09-15

    September 2026 announced partnership combines ID.me person verification with Plaid financial-account verification for government benefit payments. Not proof of deployment at every agency or use in every ID.me check.

    Company announcement
Who uses ID.me?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

Who uses data from ID.me?

No downstream data users documented in this collection. This does not establish that there are none.

Company country for geographic context; not a processing or data-transfer route.

Jumio

United States

1 component links documented customer coverage not yet collected

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Jumio: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Jumio → FaceTec: 3D liveness detection 🇺🇸 United States JumioSelected service · follow its suppliers → 🇺🇸 United States FaceTec3D liveness detectionHistorical evidence Jumio: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Jumio → FaceTec: 3D liveness detection 🇺🇸 United States JumioSelected service · follow its suppliers → 🇺🇸 United States FaceTec3D liveness detectionHistorical evidence

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Jumiouses suppliers & sources below ↓
United States
1 entry

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
What does Jumio use?
  • FaceTec United States 3D liveness detection Historical evidence

    Reported integration in 2018; current deployment not established here.

    Press report
Who uses Jumio?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

Who uses data from Jumio?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Jumio

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

Veriff

Estonia

2 component links documented supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Veriff: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Veriff → EXL: Human review supportVeriff → Resistant AI: Tampering & address-document checksLexisNexis Risk Solutions → Veriff: Image processing 🇪🇪 Estonia VeriffSelected service · follow its suppliers → 🇨🇿 Czech Republic Resistant AITampering & address-document checksDocumented 🇮🇳 India EXLHuman review supportDocumented 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source Veriff: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Veriff → EXL: Human review supportVeriff → Resistant AI: Tampering & address-document checksLexisNexis Risk Solutions → Veriff: Image processing 🇪🇪 Estonia VeriffSelected service · follow its suppliers → 🇨🇿 Czech Republic Resistant AITampering & address-document checksDocumented 🇮🇳 India EXLHuman review supportDocumented 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Veriffuses suppliers & sources below ↓
Czech Republic
1 entry
India
1 entry
Who uses Veriff?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Veriff?
What does Veriff use?
  • EXL India Human review support Documented

    Verification review support; registry lists India as the processing country.

    Supplier registry
  • Resistant AI Czech Republic Tampering & address-document checks Documented

    Registry specifies tampering and proof-of-address fraud checks.

    Supplier registry
Who uses data from Veriff?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Veriff

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

GBG plc

United Kingdom

1 component links documented customer coverage not yet collected

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
GBG plc: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. GBG plc → Innovolar (GBG registry name): Passport chip reading 🇬🇧 United Kingdom GBG plcSelected service · follow its suppliers → 🇳🇱 Netherlands Innovolar (GBG registry name)Passport chip readingDocumented GBG plc: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. GBG plc → Innovolar (GBG registry name): Passport chip reading 🇬🇧 United Kingdom GBG plcSelected service · follow its suppliers → 🇳🇱 Netherlands Innovolar (GBG registry name)Passport chip readingDocumented

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

GBG plcuses suppliers & sources below ↓
Netherlands
1 entry

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
What does GBG plc use?
Who uses GBG plc?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

Who uses data from GBG plc?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for GBG plc

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Corporate ownership · separate from component use
  • Acuant Inc. United States Acquisition Historical evidence · 2021

    GBG’s history records the 2021 acquisition and subsequent integration under the IDology brand.

    Ownership source

Company country for geographic context; not a processing or data-transfer route.

RELX

United KingdomNetherlands

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
RELX: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. 🇬🇧 United Kingdom · 🇳🇱 Netherlands RELXSelected service · follow its suppliers → RELX: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. 🇬🇧 United Kingdom · 🇳🇱 Netherlands RELXSelected service · follow its suppliers →

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

RELXuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses RELX?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does RELX use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from RELX?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for RELX

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Corporate ownership · separate from component use

Company country for geographic context; not a processing or data-transfer route.

Acuant Inc.

United States

Component-use coverage not yet collected supplies 2 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Acuant Inc.: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Acuant Inc.: Image processingLogin.gov → Acuant Inc.: Acuant browser capture SDK 🇺🇸 United States Acuant Inc.Selected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source 🇺🇸 United States Login.govDocumented customer / upstream source Acuant Inc.: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Acuant Inc.: Image processingLogin.gov → Acuant Inc.: Acuant browser capture SDK 🇺🇸 United States Acuant Inc.Selected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source 🇺🇸 United States Login.govDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Acuant Inc.uses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Acuant Inc.?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Acuant Inc.?
  • LexisNexis Risk Solutions United States Image processing Documented

    TrueID Document Authentication; registry describes biometric image processing.

    Supplier registry
  • Login.gov United States Acuant browser capture SDK Conditional · 2026-10-16

    Public integration selects Acuant SDK versions and configures the Acuant SDK connection. This is capture technology, distinct from the downstream document-authentication decision. A direct procurement contract or universal production use is not established.

    Integration documentation
What does Acuant Inc. use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Acuant Inc.?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Acuant Inc.

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Corporate ownership · separate from component use
  • GBG plc United Kingdom Acquisition Historical evidence · 2021

    GBG’s history records the 2021 acquisition and subsequent integration under the IDology brand.

    Ownership source

Company country for geographic context; not a processing or data-transfer route.

IDVerse

OCR Labs Global Ltd in the registry United Kingdom

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
IDVerse: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → IDVerse: Document verification 🇬🇧 United Kingdom IDVerseSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source IDVerse: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → IDVerse: Document verification 🇬🇧 United Kingdom IDVerseSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

IDVerseuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses IDVerse?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses IDVerse?
What does IDVerse use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from IDVerse?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for IDVerse

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Corporate ownership · separate from component use

Company country for geographic context; not a processing or data-transfer route.

TrustID

United Kingdom

Component-use coverage not yet collected supplies 2 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
TrustID: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → TrustID: Document verificationEntrust IDV → TrustID: Fraud detection 🇬🇧 United Kingdom TrustIDSelected service · follow its suppliers → 🇺🇸 United States Entrust IDVDocumented customer / upstream source 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source TrustID: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → TrustID: Document verificationEntrust IDV → TrustID: Fraud detection 🇬🇧 United Kingdom TrustIDSelected service · follow its suppliers → 🇺🇸 United States Entrust IDVDocumented customer / upstream source 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

TrustIDuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses TrustID?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses TrustID?
What does TrustID use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from TrustID?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for TrustID

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

iProov

United Kingdom

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
iProov: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → iProov: Liveness detection 🇬🇧 United Kingdom iProovSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source iProov: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → iProov: Liveness detection 🇬🇧 United Kingdom iProovSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

iProovuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses iProov?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses iProov?
  • ID.me United States Liveness detection Historical evidence · 2022

    ID.me’s 2022 white paper names iProov for presentation attack detection; current deployment not established here.

    Integration documentation
What does iProov use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from iProov?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for iProov

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

Veridas

Spain

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Veridas: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Veridas: Image processing 🇪🇸 Spain VeridasSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source Veridas: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Veridas: Image processing 🇪🇸 Spain VeridasSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Veridasuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Veridas?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Veridas?
What does Veridas use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Veridas?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Veridas

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

Au10tix

Israel

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Au10tix: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Au10tix: Document verification 🇮🇱 Israel Au10tixSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source Au10tix: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Au10tix: Document verification 🇮🇱 Israel Au10tixSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Au10tixuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Au10tix?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Au10tix?
What does Au10tix use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Au10tix?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Au10tix

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

Resistant AI

Czech Republic

Component-use coverage not yet collected supplies 3 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Resistant AI: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Resistant AI: Document verificationVeriff → Resistant AI: Tampering & address-document checksPersona → Resistant AI: Document analysis 🇨🇿 Czech Republic Resistant AISelected service · follow its suppliers → 🇪🇪 Estonia VeriffDocumented customer / upstream source 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source 🇺🇸 United States PersonaDocumented customer / upstream source Resistant AI: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Resistant AI: Document verificationVeriff → Resistant AI: Tampering & address-document checksPersona → Resistant AI: Document analysis 🇨🇿 Czech Republic Resistant AISelected service · follow its suppliers → 🇪🇪 Estonia VeriffDocumented customer / upstream source 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source 🇺🇸 United States PersonaDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Resistant AIuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Resistant AI?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Resistant AI?
  • LexisNexis Risk Solutions United States Document verification Documented

    RiskNarrative service listed in the supplier registry.

    Supplier registry
  • Veriff Estonia Tampering & address-document checks Documented

    Registry specifies tampering and proof-of-address fraud checks.

    Supplier registry
  • Persona United States Document analysis Conditional · 2026-08-22

    Conditional service in Persona’s registry; service country is the United States, distinct from Resistant AI’s Czech corporate location.

    Supplier registry
What does Resistant AI use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Resistant AI?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Resistant AI

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

Innovolar (GBG registry name)

Netherlands

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Innovolar (GBG registry name): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. GBG plc → Innovolar (GBG registry name): Passport chip reading 🇳🇱 Netherlands Innovolar (GBG registry name)Selected service · follow its suppliers → 🇬🇧 United Kingdom GBG plcDocumented customer / upstream source Innovolar (GBG registry name): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. GBG plc → Innovolar (GBG registry name): Passport chip reading 🇳🇱 Netherlands Innovolar (GBG registry name)Selected service · follow its suppliers → 🇬🇧 United Kingdom GBG plcDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Innovolar (GBG registry name)uses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Innovolar (GBG registry name)?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Innovolar (GBG registry name)?
  • GBG plc United Kingdom Passport chip reading Documented

    IDscan Enterprise (web); third-party NFC technology for chip details and images.

    Supplier registry
What does Innovolar (GBG registry name) use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Innovolar (GBG registry name)?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Innovolar (GBG registry name)

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

EXL

India

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
EXL: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Veriff → EXL: Human review support 🇮🇳 India EXLSelected service · follow its suppliers → 🇪🇪 Estonia VeriffDocumented customer / upstream source EXL: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Veriff → EXL: Human review support 🇮🇳 India EXLSelected service · follow its suppliers → 🇪🇪 Estonia VeriffDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

EXLuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses EXL?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses EXL?
  • Veriff Estonia Human review support Documented

    Verification review support; registry lists India as the processing country.

    Supplier registry
What does EXL use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from EXL?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for EXL

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Review service country listed by the customer registry, not headquarters. Location source ↗

Teleperformance

India

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Teleperformance: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Entrust IDV → Teleperformance: Human review 🇮🇳 India TeleperformanceSelected service · follow its suppliers → 🇺🇸 United States Entrust IDVDocumented customer / upstream source Teleperformance: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Entrust IDV → Teleperformance: Human review 🇮🇳 India TeleperformanceSelected service · follow its suppliers → 🇺🇸 United States Entrust IDVDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Teleperformanceuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Teleperformance?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Teleperformance?
What does Teleperformance use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Teleperformance?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Teleperformance

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Review service country listed by the customer registry, not headquarters. Location source ↗

Mas Callnet

India

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Mas Callnet: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Entrust IDV → Mas Callnet: Human review 🇮🇳 India Mas CallnetSelected service · follow its suppliers → 🇺🇸 United States Entrust IDVDocumented customer / upstream source Mas Callnet: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Entrust IDV → Mas Callnet: Human review 🇮🇳 India Mas CallnetSelected service · follow its suppliers → 🇺🇸 United States Entrust IDVDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Mas Callnetuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Mas Callnet?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Mas Callnet?
What does Mas Callnet use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Mas Callnet?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Mas Callnet

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Review service country listed by the customer registry, not headquarters. Location source ↗

Concentrix

IndiaBulgariaVietnam

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Concentrix: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Entrust IDV → Concentrix: Human review 🇮🇳 India · 🇧🇬 Bulgaria · 🇻🇳 Vietnam ConcentrixSelected service · follow its suppliers → 🇺🇸 United States Entrust IDVDocumented customer / upstream source Concentrix: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Entrust IDV → Concentrix: Human review 🇮🇳 India · 🇧🇬 Bulgaria · 🇻🇳 Vietnam ConcentrixSelected service · follow its suppliers → 🇺🇸 United States Entrust IDVDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Concentrixuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Concentrix?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Concentrix?
What does Concentrix use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Concentrix?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Concentrix

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Review service locations listed by Entrust, not headquarters. Location source ↗

Anthropic

United States

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Anthropic: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Persona → Anthropic: Data extraction & analysis 🇺🇸 United States AnthropicSelected service · follow its suppliers → 🇺🇸 United States PersonaDocumented customer / upstream source Anthropic: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Persona → Anthropic: Data extraction & analysis 🇺🇸 United States AnthropicSelected service · follow its suppliers → 🇺🇸 United States PersonaDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Anthropicuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Anthropic?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Anthropic?
  • Persona United States Data extraction & analysis Conditional · 2026-08-22

    Conditional service; registry listing does not mean every Persona check uses it.

    Supplier registry
What does Anthropic use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Anthropic?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Anthropic

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

OpenAI

United States

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
OpenAI: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Persona → OpenAI: Data extraction & analysis 🇺🇸 United States OpenAISelected service · follow its suppliers → 🇺🇸 United States PersonaDocumented customer / upstream source OpenAI: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Persona → OpenAI: Data extraction & analysis 🇺🇸 United States OpenAISelected service · follow its suppliers → 🇺🇸 United States PersonaDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

OpenAIuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses OpenAI?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses OpenAI?
  • Persona United States Data extraction & analysis Conditional · 2026-08-22

    Conditional service; registry listing does not mean every Persona check uses it.

    Supplier registry
What does OpenAI use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from OpenAI?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for OpenAI

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

Groq

United States

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Groq: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Persona → Groq: Data extraction & analysis 🇺🇸 United States GroqSelected service · follow its suppliers → 🇺🇸 United States PersonaDocumented customer / upstream source Groq: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Persona → Groq: Data extraction & analysis 🇺🇸 United States GroqSelected service · follow its suppliers → 🇺🇸 United States PersonaDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Groquses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Groq?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Groq?
  • Persona United States Data extraction & analysis Conditional · 2026-08-22

    Conditional service; registry listing does not mean every Persona check uses it.

    Supplier registry
What does Groq use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Groq?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Groq

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

Paravision

United States

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Paravision: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Paravision: Face recognition 🇺🇸 United States ParavisionSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source Paravision: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Paravision: Face recognition 🇺🇸 United States ParavisionSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Paravisionuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Paravision?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Paravision?
  • ID.me United States Face recognition Documented · 2025-07-17

    Paravision’s July 2025 announcement names ID.me’s deployment of Identity AI.

    Company announcement
What does Paravision use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Paravision?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Paravision

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

Amazon Rekognition

United States

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Amazon Rekognition: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Amazon Rekognition: Face recognition 🇺🇸 United States Amazon RekognitionSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source Amazon Rekognition: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Amazon Rekognition: Face recognition 🇺🇸 United States Amazon RekognitionSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Amazon Rekognitionuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Amazon Rekognition?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Amazon Rekognition?
  • ID.me United States Face recognition Historical evidence · 2022

    Reported use in January 2022; current deployment not established here.

    Press report
What does Amazon Rekognition use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Amazon Rekognition?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Amazon Rekognition

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

FaceTec

United States

Component-use coverage not yet collected supplies 2 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
FaceTec: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Jumio → FaceTec: 3D liveness detectionEntrust IDV → FaceTec: Liveness / authentication 🇺🇸 United States FaceTecSelected service · follow its suppliers → 🇺🇸 United States Entrust IDVDocumented customer / upstream source 🇺🇸 United States JumioDocumented customer / upstream source FaceTec: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Jumio → FaceTec: 3D liveness detectionEntrust IDV → FaceTec: Liveness / authentication 🇺🇸 United States FaceTecSelected service · follow its suppliers → 🇺🇸 United States Entrust IDVDocumented customer / upstream source 🇺🇸 United States JumioDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

FaceTecuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses FaceTec?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses FaceTec?
  • Jumio United States 3D liveness detection Historical evidence

    Reported integration in 2018; current deployment not established here.

    Press report
  • Entrust IDV United States Liveness / authentication Historical evidence

    Reported Onfido partnership in 2021, before the Entrust acquisition; current deployment not established here.

    Press report
What does FaceTec use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from FaceTec?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for FaceTec

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Company country for geographic context; not a processing or data-transfer route.

Regula

LatviaUnited States

Component-use coverage not yet collected supplies 3 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Regula: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Daon (TrustX) → Regula: Document processingLuciditi (Arissian) → Regula: Document Reader SDKREACT (ID Wallet) → Regula: Document Reader SDK 🇱🇻 Latvia · 🇺🇸 United States RegulaSelected service · follow its suppliers → 🇪🇸 Spain REACT (ID Wallet)Documented customer / upstream source 🇬🇧 United Kingdom Luciditi (Arissian)Documented customer / upstream source 🇺🇸 United States Daon (TrustX)Documented customer / upstream source Regula: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Daon (TrustX) → Regula: Document processingLuciditi (Arissian) → Regula: Document Reader SDKREACT (ID Wallet) → Regula: Document Reader SDK 🇱🇻 Latvia · 🇺🇸 United States RegulaSelected service · follow its suppliers → 🇪🇸 Spain REACT (ID Wallet)Documented customer / upstream source 🇬🇧 United Kingdom Luciditi (Arissian)Documented customer / upstream source 🇺🇸 United States Daon (TrustX)Documented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Regulauses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Regula?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Regula?
  • Daon (TrustX) United States Document processing Documented

    TrustX documents a configurable Regula document processor; not evidence that every Daon workflow selects it.

    Integration documentation
  • Luciditi (Arissian) United Kingdom Document Reader SDK Documented

    Regula’s customer story describes the SDK embedded in Luciditi’s mobile and web platforms; current deployment not independently verified.

    Supplier case study
  • REACT (ID Wallet) Spain Document Reader SDK Documented

    Regula’s customer story describes its SDK embedded in REACT’s ID Wallet, on mobile and web; current deployment not independently verified.

    Supplier case study
What does Regula use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Regula?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Regula

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Regula’s own products · capabilities, not customer evidence
  • Document Reader SDK ↗

    Document data extraction and authenticity checks, including chip reading where supported.

  • Face SDK ↗

    Face matching, face detection, and liveness assessment.

  • IDV Platform ↗

    Document, biometric, and data-based verification in one workflow.

Selected published offices in Latvia and the United States; other offices omitted. Location source ↗

Daon (TrustX)

United States

1 component links documented customer coverage not yet collected

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Daon (TrustX): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Daon (TrustX) → Regula: Document processing 🇺🇸 United States Daon (TrustX)Selected service · follow its suppliers → 🇱🇻 Latvia · 🇺🇸 United States RegulaDocument processingDocumented Daon (TrustX): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Daon (TrustX) → Regula: Document processing 🇺🇸 United States Daon (TrustX)Selected service · follow its suppliers → 🇱🇻 Latvia · 🇺🇸 United States RegulaDocument processingDocumented

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Daon (TrustX)uses suppliers & sources below ↓
Latvia
1 entry
United States
1 entry

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
What does Daon (TrustX) use?
  • Regula Latvia United States Document processing Documented

    TrustX documents a configurable Regula document processor; not evidence that every Daon workflow selects it.

    Integration documentation
Who uses Daon (TrustX)?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

Who uses data from Daon (TrustX)?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Daon (TrustX)

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Selected published US office; other offices omitted. Location source ↗

Luciditi (Arissian)

United Kingdom

1 component links documented customer coverage not yet collected

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Luciditi (Arissian): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Luciditi (Arissian) → Regula: Document Reader SDK 🇬🇧 United Kingdom Luciditi (Arissian)Selected service · follow its suppliers → 🇱🇻 Latvia · 🇺🇸 United States RegulaDocument Reader SDKDocumented Luciditi (Arissian): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Luciditi (Arissian) → Regula: Document Reader SDK 🇬🇧 United Kingdom Luciditi (Arissian)Selected service · follow its suppliers → 🇱🇻 Latvia · 🇺🇸 United States RegulaDocument Reader SDKDocumented

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Luciditi (Arissian)uses suppliers & sources below ↓
Latvia
1 entry
United States
1 entry

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
What does Luciditi (Arissian) use?
  • Regula Latvia United States Document Reader SDK Documented

    Regula’s customer story describes the SDK embedded in Luciditi’s mobile and web platforms; current deployment not independently verified.

    Supplier case study
Who uses Luciditi (Arissian)?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

Who uses data from Luciditi (Arissian)?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Luciditi (Arissian)

Upstream sources are not identified here. No provider names or individual contributors are inferred.

United Kingdom, as identified in the Regula customer story; not a London address. Location source ↗

REACT (ID Wallet)

Spain

1 component links documented customer coverage not yet collected

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
REACT (ID Wallet): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. REACT (ID Wallet) → Regula: Document Reader SDK 🇪🇸 Spain REACT (ID Wallet)Selected service · follow its suppliers → 🇱🇻 Latvia · 🇺🇸 United States RegulaDocument Reader SDKDocumented REACT (ID Wallet): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. REACT (ID Wallet) → Regula: Document Reader SDK 🇪🇸 Spain REACT (ID Wallet)Selected service · follow its suppliers → 🇱🇻 Latvia · 🇺🇸 United States RegulaDocument Reader SDKDocumented

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

REACT (ID Wallet)uses suppliers & sources below ↓
Latvia
1 entry
United States
1 entry

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
What does REACT (ID Wallet) use?
  • Regula Latvia United States Document Reader SDK Documented

    Regula’s customer story describes its SDK embedded in REACT’s ID Wallet, on mobile and web; current deployment not independently verified.

    Supplier case study
Who uses REACT (ID Wallet)?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

Who uses data from REACT (ID Wallet)?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for REACT (ID Wallet)

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Spain, as identified in the Regula customer story; not a specific office address. Location source ↗

Socure

United States

Component-use coverage not yet collected supplies 1 brands in this collection

5 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Socure: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Login.gov → Socure: Socure DocV document workflowSocure → Early Warning Services: Account validation and ownershipSocure → Middesk: Business verificationSocure → Kyckr: Company profiles and registry documentsSocure → Thomson Reuters CLEAR: Business and person searchesSocure → Socure data vendors · names undisclosed: Verification-supporting dataLogin.gov → Socure: Socure ID+ KYCLogin.gov → Socure: Socure ID+ PhoneRiskEarly Warning Services → Participating US financial institutions: Bank-account activity dataMiddesk → US state business registrations: Business formation dataKyckr → Official company registries: Live company-register data 🇺🇸 United States SocureSelected service · follow its suppliers → 🌐 Country not asserted KyckrCompany profiles and registry documentsDocumented 🌐 Country not asserted · Source category Official company registriesLive company-register dataDocumented 🌐 Country not asserted · Source category Socure data vendors · names undisclosedVerification-supporting dataDocumented 🇺🇸 United States Early Warning ServicesAccount validation and ownershipDocumented 🇺🇸 United States Login.govDocumented customer / upstream source 🇺🇸 United States MiddeskBusiness verificationDocumented 🇺🇸 United States · Source category Participating US financial institutionsBank-account activity dataDocumented 🇺🇸 United States Thomson Reuters CLEARBusiness and person searchesDocumented 🇺🇸 United States · Source category US state business registrationsBusiness formation dataDocumented Socure: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Login.gov → Socure: Socure DocV document workflowSocure → Early Warning Services: Account validation and ownershipSocure → Middesk: Business verificationSocure → Kyckr: Company profiles and registry documentsSocure → Thomson Reuters CLEAR: Business and person searchesSocure → Socure data vendors · names undisclosed: Verification-supporting dataLogin.gov → Socure: Socure ID+ KYCLogin.gov → Socure: Socure ID+ PhoneRiskEarly Warning Services → Participating US financial institutions: Bank-account activity dataMiddesk → US state business registrations: Business formation dataKyckr → Official company registries: Live company-register data 🇺🇸 United States SocureSelected service · follow its suppliers → 🌐 Country not asserted KyckrCompany profiles and registry documentsDocumented 🌐 Country not asserted · Source category Official company registriesLive company-register dataDocumented 🌐 Country not asserted · Source category Socure data vendors · names undisclosedVerification-supporting dataDocumented 🇺🇸 United States Early Warning ServicesAccount validation and ownershipDocumented 🇺🇸 United States Login.govDocumented customer / upstream source 🇺🇸 United States MiddeskBusiness verificationDocumented 🇺🇸 United States · Source category Participating US financial institutionsBank-account activity dataDocumented 🇺🇸 United States Thomson Reuters CLEARBusiness and person searchesDocumented 🇺🇸 United States · Source category US state business registrationsBusiness formation dataDocumented

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Socureuses suppliers & sources below ↓
Country not asserted
2 entries
  • Kyckr →
    Data & authoritative sources

    Company profiles and registry documents

    Documented

    RiskOS Kyckr integration · Multiple jurisdictions
    Available reseller integration

    Scope & evidence

    Available through a RiskOS reseller integration; selected workflows, not every Socure verification.

    Socure: Kyckr partner documentation ↗
    ↓ Further upstream · separately sourced
  • Socure data vendors · names undisclosed →Source category
    Data & authoritative sources

    Verification-supporting data

    Documented · 2026-10-01

    Services covered by the notice · Global notice; product terms apply
    Declared data source

    Scope & evidence

    The service notice discloses a category, not a full named-provider list.

    Socure: Global Services Privacy Notice ↗
United States
3 entries
Who uses Socure?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Socure?
  • Login.gov United States Socure DocV document workflow Conditional · 2026-10-16

    Public implementation supports configured document-only and document-with-selfie use cases, including licence and passport requests. The official test plan also documents Socure staging tests; neither source establishes production allocation. No RiskOS or bank-data upstream integration is inferred.

    Integration documentation
Who uses data from Socure?
  • Login.gov United States Socure ID+ KYC Login.gov Socure ID+ KYC integration · United StatesProduct-specific integration Conditional · 2026-10-16

    Public implementation requests the US kyc module for identity resolution. Source code is not proof of production activation. Other Socure products, RiskOS connectors and bank-data feeds are not assumed in this path.

    Integration documentation
  • Login.gov United States Socure ID+ PhoneRisk Login.gov Socure ID+ PhoneRisk integration · United StatesProduct-specific integration Conditional · 2026-10-16

    Public implementation requests the US phonerisk module and correlation signals. Production activation, traffic allocation and particular upstream data vendors are not established.

    Integration documentation
Data sources and integrations for Socure
  • Early Warning Services United States Account validation and ownership Account Intelligence Premier · United StatesProduct-specific integration Documented

    Approved Premier integration. Does not establish use in every Socure identity check.

    Integration documentation
  • Middesk United States Business verification RiskOS Middesk integration · United StatesAvailable reseller integration Documented

    Available through a RiskOS reseller integration; selected workflows, not every Socure verification.

    Integration documentation
  • Kyckr 🌐 Country not asserted Company profiles and registry documents RiskOS Kyckr integration · Multiple jurisdictionsAvailable reseller integration Documented

    Available through a RiskOS reseller integration; selected workflows, not every Socure verification.

    Integration documentation
  • Thomson Reuters CLEAR United States Business and person searches RiskOS CLEAR connector · United StatesCustomer’s own provider account Documented

    Requires the customer’s own partner account; not a centrally licensed feed for every Socure customer.

    Integration documentation
  • Socure data vendors · names undisclosed 🌐 Country not asserted Source category · individual suppliers not identified Verification-supporting data Services covered by the notice · Global notice; product terms applyDeclared data source Documented · 2026-10-01

    The service notice discloses a category, not a full named-provider list.

    Processing notice
What does Socure use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

US product context for the integrations shown; not a headquarters marker. Location source ↗

Early Warning Services

United States

Component-use coverage not yet collected customer coverage not yet collected

1 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Early Warning Services: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Early Warning Services → Participating US financial institutions: Bank-account activity dataSocure → Early Warning Services: Account validation and ownership 🇺🇸 United States Early Warning ServicesSelected service · follow its suppliers → 🇺🇸 United States · Source category Participating US financial institutionsBank-account activity dataDocumented 🇺🇸 United States SocureDocumented customer / upstream source Early Warning Services: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Early Warning Services → Participating US financial institutions: Bank-account activity dataSocure → Early Warning Services: Account validation and ownership 🇺🇸 United States Early Warning ServicesSelected service · follow its suppliers → 🇺🇸 United States · Source category Participating US financial institutionsBank-account activity dataDocumented 🇺🇸 United States SocureDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Early Warning Servicesuses suppliers & sources below ↓
United States
1 entry
Who uses Early Warning Services?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Early Warning Services?
  • Socure United States Account validation and ownership Account Intelligence Premier · United StatesProduct-specific integration Documented

    Approved Premier integration. Does not establish use in every Socure identity check.

    Integration documentation
Data sources and integrations for Early Warning Services
Who uses Early Warning Services?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Early Warning Services use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

US financial-institution data context; not an office marker. Location source ↗

Equifax Limited

United Kingdom

Component-use coverage not yet collected customer coverage not yet collected

2 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Equifax Limited: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Equifax Limited → UK financial-account providers: Account-performance informationEquifax Limited → Registry Trust: Judgment-register informationLexisNexis Risk Solutions → Equifax Limited: Identity and credit-reference data 🇬🇧 United Kingdom Equifax LimitedSelected service · follow its suppliers → 🇬🇧 United Kingdom Registry TrustJudgment-register informationDocumented 🇬🇧 United Kingdom · Source category UK financial-account providersAccount-performance informationDocumented 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source Equifax Limited: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Equifax Limited → UK financial-account providers: Account-performance informationEquifax Limited → Registry Trust: Judgment-register informationLexisNexis Risk Solutions → Equifax Limited: Identity and credit-reference data 🇬🇧 United Kingdom Equifax LimitedSelected service · follow its suppliers → 🇬🇧 United Kingdom Registry TrustJudgment-register informationDocumented 🇬🇧 United Kingdom · Source category UK financial-account providersAccount-performance informationDocumented 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Equifax Limiteduses suppliers & sources below ↓
United Kingdom
2 entries
Who uses Equifax Limited?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Equifax Limited?
Data sources and integrations for Equifax Limited
  • UK financial-account providers United Kingdom Source category · individual suppliers not identified Account-performance information Core credit referencing · United KingdomDeclared data source Documented

    CRAIN describes this source category; it does not establish which underlying fields reach LexisNexis.

    Processing notice
  • Registry Trust United Kingdom Judgment-register information Core credit referencing · United KingdomDeclared data source Documented

    Documented CRA source; not proof of a particular person’s records traversing the whole chain.

    Processing notice
Who uses Equifax Limited?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Equifax Limited use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

UK entity and processing-notice context; not a London office assertion. Location source ↗

Experian Limited

United Kingdom

Component-use coverage not yet collected customer coverage not yet collected

2 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Experian Limited: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Experian Limited → UK financial-account providers: Account-performance informationExperian Limited → Registry Trust: Judgment-register informationLexisNexis Risk Solutions → Experian Limited: Identity and credit-reference data 🇬🇧 United Kingdom Experian LimitedSelected service · follow its suppliers → 🇬🇧 United Kingdom Registry TrustJudgment-register informationDocumented 🇬🇧 United Kingdom · Source category UK financial-account providersAccount-performance informationDocumented 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source Experian Limited: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Experian Limited → UK financial-account providers: Account-performance informationExperian Limited → Registry Trust: Judgment-register informationLexisNexis Risk Solutions → Experian Limited: Identity and credit-reference data 🇬🇧 United Kingdom Experian LimitedSelected service · follow its suppliers → 🇬🇧 United Kingdom Registry TrustJudgment-register informationDocumented 🇬🇧 United Kingdom · Source category UK financial-account providersAccount-performance informationDocumented 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Experian Limiteduses suppliers & sources below ↓
United Kingdom
2 entries
Who uses Experian Limited?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Experian Limited?
Data sources and integrations for Experian Limited
  • UK financial-account providers United Kingdom Source category · individual suppliers not identified Account-performance information Core credit referencing · United KingdomDeclared data source Documented

    CRAIN describes this source category; it does not establish which underlying fields reach LexisNexis.

    Processing notice
  • Registry Trust United Kingdom Judgment-register information Core credit referencing · United KingdomDeclared data source Documented

    Documented CRA source; not proof of a particular person’s records traversing the whole chain.

    Processing notice
Who uses Experian Limited?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Experian Limited use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

UK entity and processing-notice context; not a London office assertion. Location source ↗

Crediva Limited

United Kingdom

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Crediva Limited: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Crediva Limited: Identity and credit-reference data 🇬🇧 United Kingdom Crediva LimitedSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source Crediva Limited: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Crediva Limited: Identity and credit-reference data 🇬🇧 United Kingdom Crediva LimitedSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Crediva Limiteduses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Crediva Limited?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Crediva Limited?
Who uses Crediva Limited?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Crediva Limited use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Crediva Limited

Upstream sources are not identified here. No provider names or individual contributors are inferred.

UK credit-reference agency affiliated with LexisNexis Risk Solutions. Location source ↗

Registry Trust

United Kingdom

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 3 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Registry Trust: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Registry Trust: Judgment recordsEquifax Limited → Registry Trust: Judgment-register informationExperian Limited → Registry Trust: Judgment-register information 🇬🇧 United Kingdom Registry TrustSelected service · follow its suppliers → 🇬🇧 United Kingdom Equifax LimitedDocumented customer / upstream source 🇬🇧 United Kingdom Experian LimitedDocumented customer / upstream source 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source Registry Trust: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Registry Trust: Judgment recordsEquifax Limited → Registry Trust: Judgment-register informationExperian Limited → Registry Trust: Judgment-register information 🇬🇧 United Kingdom Registry TrustSelected service · follow its suppliers → 🇬🇧 United Kingdom Equifax LimitedDocumented customer / upstream source 🇬🇧 United Kingdom Experian LimitedDocumented customer / upstream source 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Registry Trustuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Registry Trust?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Registry Trust?
  • LexisNexis Risk Solutions United States Judgment records Business Services · United KingdomSource example named in notice Documented · 2025-12-17

    Named source example in the notice; no specific contract or universal use established.

    Processing notice
  • Equifax Limited United Kingdom Judgment-register information Core credit referencing · United KingdomDeclared data source Documented

    Documented CRA source; not proof of a particular person’s records traversing the whole chain.

    Processing notice
  • Experian Limited United Kingdom Judgment-register information Core credit referencing · United KingdomDeclared data source Documented

    Documented CRA source; not proof of a particular person’s records traversing the whole chain.

    Processing notice
Who uses Registry Trust?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Registry Trust use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Registry Trust

Upstream sources are not identified here. No provider names or individual contributors are inferred.

UK judgment-register source context; not an office marker. Location source ↗

Companies House

United Kingdom

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Companies House: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Companies House: Directorship records 🇬🇧 United Kingdom Companies HouseSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source Companies House: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Companies House: Directorship records 🇬🇧 United Kingdom Companies HouseSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Companies Houseuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Companies House?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Companies House?
  • LexisNexis Risk Solutions United States Directorship records Business Services · United KingdomSource example named in notice Documented · 2025-12-17

    Named source example in the notice; no specific contract or universal use established.

    Processing notice
Who uses Companies House?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Companies House use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Companies House

Upstream sources are not identified here. No provider names or individual contributors are inferred.

UK company-register source context; not an office marker. Location source ↗

General Register Office

United Kingdom

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
General Register Office: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → General Register Office: Civil-registration records 🇬🇧 United Kingdom General Register OfficeSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source General Register Office: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → General Register Office: Civil-registration records 🇬🇧 United Kingdom General Register OfficeSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

General Register Officeuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses General Register Office?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from General Register Office?
  • LexisNexis Risk Solutions United States Civil-registration records Business Services · United KingdomSource example named in notice Documented · 2025-12-17

    Named source example in the notice; no specific contract or universal use established.

    Processing notice
Who uses General Register Office?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does General Register Office use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for General Register Office

Upstream sources are not identified here. No provider names or individual contributors are inferred.

UK civil-registration source context; not an office marker. Location source ↗

HM Land Registry

United Kingdom

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
HM Land Registry: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → HM Land Registry: Property records 🇬🇧 United Kingdom HM Land RegistrySelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source HM Land Registry: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → HM Land Registry: Property records 🇬🇧 United Kingdom HM Land RegistrySelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

HM Land Registryuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses HM Land Registry?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from HM Land Registry?
  • LexisNexis Risk Solutions United States Property records Business Services · United KingdomSource example named in notice Documented · 2025-12-17

    Named source example in the notice; no specific contract or universal use established.

    Processing notice
Who uses HM Land Registry?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does HM Land Registry use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for HM Land Registry

Upstream sources are not identified here. No provider names or individual contributors are inferred.

UK property-record source context; not an office marker. Location source ↗

Royal Mail plc

United Kingdom

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Royal Mail plc: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Royal Mail plc: Commercial data 🇬🇧 United Kingdom Royal Mail plcSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source Royal Mail plc: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. LexisNexis Risk Solutions → Royal Mail plc: Commercial data 🇬🇧 United Kingdom Royal Mail plcSelected service · follow its suppliers → 🇺🇸 United States LexisNexis Risk SolutionsDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Royal Mail plcuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Royal Mail plc?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Royal Mail plc?
  • LexisNexis Risk Solutions United States Commercial data Business Services · United KingdomSource example named in notice Documented · 2025-12-17

    Named source example in the notice; no specific contract or universal use established.

    Processing notice
Who uses Royal Mail plc?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Royal Mail plc use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Royal Mail plc

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Commercial source named in the UK Business Services notice. Location source ↗

Middesk

United States

Component-use coverage not yet collected customer coverage not yet collected

1 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Middesk: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Middesk → US state business registrations: Business formation dataSocure → Middesk: Business verification 🇺🇸 United States MiddeskSelected service · follow its suppliers → 🇺🇸 United States SocureDocumented customer / upstream source 🇺🇸 United States · Source category US state business registrationsBusiness formation dataDocumented Middesk: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Middesk → US state business registrations: Business formation dataSocure → Middesk: Business verification 🇺🇸 United States MiddeskSelected service · follow its suppliers → 🇺🇸 United States SocureDocumented customer / upstream source 🇺🇸 United States · Source category US state business registrationsBusiness formation dataDocumented

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Middeskuses suppliers & sources below ↓
United States
1 entry
Who uses Middesk?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Middesk?
  • Socure United States Business verification RiskOS Middesk integration · United StatesAvailable reseller integration Documented

    Available through a RiskOS reseller integration; selected workflows, not every Socure verification.

    Integration documentation
Data sources and integrations for Middesk
Who uses Middesk?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Middesk use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

US business-verification product context; not an office marker. Location source ↗

Kyckr

🌐 Country not asserted

Component-use coverage not yet collected customer coverage not yet collected

1 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Kyckr: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Kyckr → Official company registries: Live company-register dataSocure → Kyckr: Company profiles and registry documents 🌐 Country not asserted KyckrSelected service · follow its suppliers → 🌐 Country not asserted · Source category Official company registriesLive company-register dataDocumented 🇺🇸 United States SocureDocumented customer / upstream source Kyckr: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Kyckr → Official company registries: Live company-register dataSocure → Kyckr: Company profiles and registry documents 🌐 Country not asserted KyckrSelected service · follow its suppliers → 🌐 Country not asserted · Source category Official company registriesLive company-register dataDocumented 🇺🇸 United States SocureDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Kyckruses suppliers & sources below ↓
Country not asserted
1 entry
Who uses Kyckr?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Kyckr?
  • Socure United States Company profiles and registry documents RiskOS Kyckr integration · Multiple jurisdictionsAvailable reseller integration Documented

    Available through a RiskOS reseller integration; selected workflows, not every Socure verification.

    Integration documentation
Data sources and integrations for Kyckr
  • Official company registries 🌐 Country not asserted Source category · individual suppliers not identified Live company-register data Company registry services · Multiple jurisdictionsDeclared data source Documented

    Official registry retrieval; coverage varies by jurisdiction and request.

    Integration documentation
Who uses Kyckr?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Kyckr use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

International registry coverage; company country not asserted in this collection. Location source ↗

Thomson Reuters CLEAR

United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Thomson Reuters CLEAR: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Socure → Thomson Reuters CLEAR: Business and person searches 🇺🇸 United States Thomson Reuters CLEARSelected service · follow its suppliers → 🇺🇸 United States SocureDocumented customer / upstream source Thomson Reuters CLEAR: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Socure → Thomson Reuters CLEAR: Business and person searches 🇺🇸 United States Thomson Reuters CLEARSelected service · follow its suppliers → 🇺🇸 United States SocureDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Thomson Reuters CLEARuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Thomson Reuters CLEAR?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Thomson Reuters CLEAR?
  • Socure United States Business and person searches RiskOS CLEAR connector · United StatesCustomer’s own provider account Documented

    Requires the customer’s own partner account; not a centrally licensed feed for every Socure customer.

    Integration documentation
Who uses Thomson Reuters CLEAR?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Thomson Reuters CLEAR use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Thomson Reuters CLEAR

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US service context for the Socure connector; not a corporate headquarters marker. Location source ↗

UK financial-account providers

Source category · not a named company United Kingdom

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 2 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
UK financial-account providers: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Equifax Limited → UK financial-account providers: Account-performance informationExperian Limited → UK financial-account providers: Account-performance information 🇬🇧 United Kingdom · Source category UK financial-account providersSelected service · follow its suppliers → 🇬🇧 United Kingdom Equifax LimitedDocumented customer / upstream source 🇬🇧 United Kingdom Experian LimitedDocumented customer / upstream source UK financial-account providers: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Equifax Limited → UK financial-account providers: Account-performance informationExperian Limited → UK financial-account providers: Account-performance information 🇬🇧 United Kingdom · Source category UK financial-account providersSelected service · follow its suppliers → 🇬🇧 United Kingdom Equifax LimitedDocumented customer / upstream source 🇬🇧 United Kingdom Experian LimitedDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

UK financial-account providersuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses UK financial-account providers?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from UK financial-account providers?
  • Equifax Limited United Kingdom Account-performance information Core credit referencing · United KingdomDeclared data source Documented

    CRAIN describes this source category; it does not establish which underlying fields reach LexisNexis.

    Processing notice
  • Experian Limited United Kingdom Account-performance information Core credit referencing · United KingdomDeclared data source Documented

    CRAIN describes this source category; it does not establish which underlying fields reach LexisNexis.

    Processing notice
Who uses UK financial-account providers?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does UK financial-account providers use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for UK financial-account providers

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Source category: banks, lenders, utilities, and telecoms; no individual provider inferred. Location source ↗

Participating US financial institutions

Source category · not a named company United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Participating US financial institutions: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Early Warning Services → Participating US financial institutions: Bank-account activity data 🇺🇸 United States · Source category Participating US financial institutionsSelected service · follow its suppliers → 🇺🇸 United States Early Warning ServicesDocumented customer / upstream source Participating US financial institutions: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Early Warning Services → Participating US financial institutions: Bank-account activity data 🇺🇸 United States · Source category Participating US financial institutionsSelected service · follow its suppliers → 🇺🇸 United States Early Warning ServicesDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Participating US financial institutionsuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Participating US financial institutions?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Participating US financial institutions?
  • Early Warning Services United States Bank-account activity data Consumer information services · United StatesDeclared data source Documented

    Contributing institutions are a category; no bank or complete downstream dataset is inferred.

    Integration documentation
Who uses Participating US financial institutions?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Participating US financial institutions use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Participating US financial institutions

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Source category, not the names of Early Warning’s owners or a list of participating banks. Location source ↗

US state business registrations

Source category · not a named company United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
US state business registrations: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Middesk → US state business registrations: Business formation data 🇺🇸 United States · Source category US state business registrationsSelected service · follow its suppliers → 🇺🇸 United States MiddeskDocumented customer / upstream source US state business registrations: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Middesk → US state business registrations: Business formation data 🇺🇸 United States · Source category US state business registrationsSelected service · follow its suppliers → 🇺🇸 United States MiddeskDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

US state business registrationsuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses US state business registrations?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from US state business registrations?
  • Middesk United States Business formation data Formation data · United StatesDeclared data source Documented

    Formation-data source only; not a claim about every Middesk product.

    Integration documentation
Who uses US state business registrations?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does US state business registrations use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for US state business registrations

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Government source category for formation data; not a named commercial supplier. Location source ↗

Official company registries

Source category · not a named company 🌐 Country not asserted

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Official company registries: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Kyckr → Official company registries: Live company-register data 🌐 Country not asserted · Source category Official company registriesSelected service · follow its suppliers → 🌐 Country not asserted KyckrDocumented customer / upstream source Official company registries: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Kyckr → Official company registries: Live company-register data 🌐 Country not asserted · Source category Official company registriesSelected service · follow its suppliers → 🌐 Country not asserted KyckrDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Official company registriesuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Official company registries?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Official company registries?
  • Kyckr 🌐 Country not asserted Live company-register data Company registry services · Multiple jurisdictionsDeclared data source Documented

    Official registry retrieval; coverage varies by jurisdiction and request.

    Integration documentation
Who uses Official company registries?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Official company registries use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Official company registries

Upstream sources are not identified here. No provider names or individual contributors are inferred.

International government-source category; jurisdictions vary by request. Location source ↗

Socure data vendors · names undisclosed

Source category · not a named company 🌐 Country not asserted

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Socure data vendors · names undisclosed: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Socure → Socure data vendors · names undisclosed: Verification-supporting data 🌐 Country not asserted · Source category Socure data vendors · names undisclosedSelected service · follow its suppliers → 🇺🇸 United States SocureDocumented customer / upstream source Socure data vendors · names undisclosed: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Socure → Socure data vendors · names undisclosed: Verification-supporting data 🌐 Country not asserted · Source category Socure data vendors · names undisclosedSelected service · follow its suppliers → 🇺🇸 United States SocureDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Socure data vendors · names undiscloseduses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Socure data vendors · names undisclosed?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Socure data vendors · names undisclosed?
  • Socure United States Verification-supporting data Services covered by the notice · Global notice; product terms applyDeclared data source Documented · 2026-10-01

    The service notice discloses a category, not a full named-provider list.

    Processing notice
Who uses Socure data vendors · names undisclosed?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Socure data vendors · names undisclosed use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Socure data vendors · names undisclosed

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Disclosed provider category, not independently identified counterparties. Location source ↗

Experian (US verification source)

United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Experian (US verification source): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Experian (US verification source): Authoritative identity-record comparison 🇺🇸 United States Experian (US verification source)Selected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source Experian (US verification source): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Experian (US verification source): Authoritative identity-record comparison 🇺🇸 United States Experian (US verification source)Selected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Experian (US verification source)uses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Experian (US verification source)?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Experian (US verification source)?
  • ID.me United States Authoritative identity-record comparison Identity-record checks disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    Integration documentation
Who uses Experian (US verification source)?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Experian (US verification source) use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Experian (US verification source)

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US verification-source context; no headquarters or processing-location assertion. Location source ↗

TeleSign

United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
TeleSign: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → TeleSign: Authoritative identity-record comparisonID.me → TeleSign: Mobile-device digital risk 🇺🇸 United States TeleSignSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source TeleSign: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → TeleSign: Authoritative identity-record comparisonID.me → TeleSign: Mobile-device digital risk 🇺🇸 United States TeleSignSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

TeleSignuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses TeleSign?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from TeleSign?
  • ID.me United States Authoritative identity-record comparison Identity-record checks disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    Integration documentation
  • ID.me United States Mobile-device digital risk Mobile-device risk disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    ID.me named this mobile-risk partner in March 2022; current deployment, underlying carriers and exact data fields not established.

    Integration documentation
Who uses TeleSign?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does TeleSign use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for TeleSign

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US verification-source context; no headquarters or processing-location assertion. Location source ↗

Prove

United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Prove: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Prove: Authoritative identity-record comparisonID.me → Prove: Mobile-device digital risk 🇺🇸 United States ProveSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source Prove: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Prove: Authoritative identity-record comparisonID.me → Prove: Mobile-device digital risk 🇺🇸 United States ProveSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Proveuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Prove?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Prove?
  • ID.me United States Authoritative identity-record comparison Identity-record checks disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    Integration documentation
  • ID.me United States Mobile-device digital risk Mobile-device risk disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    ID.me named this mobile-risk partner in March 2022; current deployment, underlying carriers and exact data fields not established.

    Integration documentation
Who uses Prove?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Prove use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Prove

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US verification-source context; no headquarters or processing-location assertion. Location source ↗

National Plan & Provider Enumeration System (NPPES)

United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
National Plan & Provider Enumeration System (NPPES): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → National Plan & Provider Enumeration System (NPPES): Authoritative identity-record comparison 🇺🇸 United States National Plan & Provider Enumeration System (NPPES)Selected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source National Plan & Provider Enumeration System (NPPES): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → National Plan & Provider Enumeration System (NPPES): Authoritative identity-record comparison 🇺🇸 United States National Plan & Provider Enumeration System (NPPES)Selected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

National Plan & Provider Enumeration System (NPPES)uses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses National Plan & Provider Enumeration System (NPPES)?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from National Plan & Provider Enumeration System (NPPES)?
  • ID.me United States Authoritative identity-record comparison Identity-record checks disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    Integration documentation
Who uses National Plan & Provider Enumeration System (NPPES)?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does National Plan & Provider Enumeration System (NPPES) use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for National Plan & Provider Enumeration System (NPPES)

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US verification-source context; no headquarters or processing-location assertion. Location source ↗

TransUnion (US verification source)

United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 2 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
TransUnion (US verification source): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → TransUnion (US verification source): Authoritative identity-record comparisonKenshiki Pulse → TransUnion (US verification source): SSN verification 🇺🇸 United States TransUnion (US verification source)Selected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source 🇺🇸 United States Kenshiki PulseDocumented customer / upstream source TransUnion (US verification source): organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → TransUnion (US verification source): Authoritative identity-record comparisonKenshiki Pulse → TransUnion (US verification source): SSN verification 🇺🇸 United States TransUnion (US verification source)Selected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source 🇺🇸 United States Kenshiki PulseDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

TransUnion (US verification source)uses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses TransUnion (US verification source)?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from TransUnion (US verification source)?
  • ID.me United States Authoritative identity-record comparison Identity-record checks disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    Integration documentation
  • Kenshiki Pulse United States SSN verification Pulse SSN verification · Supported service coverageDeclared data source Documented · 2026-10-17

    TransUnion provides the SSN check.

    Operator declaration
Who uses TransUnion (US verification source)?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does TransUnion (US verification source) use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for TransUnion (US verification source)

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US verification-source context; no headquarters or processing-location assertion. Location source ↗

FingerprintJS

United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
FingerprintJS: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → FingerprintJS: Mobile-device digital risk 🇺🇸 United States FingerprintJSSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source FingerprintJS: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → FingerprintJS: Mobile-device digital risk 🇺🇸 United States FingerprintJSSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

FingerprintJSuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses FingerprintJS?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from FingerprintJS?
  • ID.me United States Mobile-device digital risk Mobile-device risk disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    ID.me named this mobile-risk partner in March 2022; current deployment, underlying carriers and exact data fields not established.

    Integration documentation
Who uses FingerprintJS?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does FingerprintJS use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for FingerprintJS

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US verification-source context; no headquarters or processing-location assertion. Location source ↗

Fraud.net

United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Fraud.net: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Fraud.net: Behavior analysis 🇺🇸 United States Fraud.netSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source Fraud.net: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Fraud.net: Behavior analysis 🇺🇸 United States Fraud.netSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Fraud.netuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Fraud.net?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Fraud.net?
  • ID.me United States Behavior analysis Behavior analysis disclosed in 2022 · United StatesDeclared data source Historical evidence · 2022-03-25

    Named by ID.me in March 2022; current deployment and exact inputs not established.

    Integration documentation
Who uses Fraud.net?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Fraud.net use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Fraud.net

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US verification-source context; no headquarters or processing-location assertion. Location source ↗

AuthenticID

United States

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
AuthenticID: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → AuthenticID: Document and biometric verification 🇺🇸 United States AuthenticIDSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source AuthenticID: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → AuthenticID: Document and biometric verification 🇺🇸 United States AuthenticIDSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

AuthenticIDuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses AuthenticID?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses AuthenticID?
  • ID.me United States Document and biometric verification Historical evidence · 2022-03-25

    ID.me’s March 2022 response groups AuthenticID with document authenticity and credential-photo/selfie comparison partners. It does not assign individual subfunctions; current deployment not established.

    Integration documentation
What does AuthenticID use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from AuthenticID?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for AuthenticID

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US verification-source context; no headquarters or processing-location assertion. Location source ↗

National Student Clearinghouse

United States

Component-use coverage not yet collected customer coverage not yet collected

1 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
National Student Clearinghouse: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. National Student Clearinghouse → Participating US colleges and universities: Institution-reported enrollment recordsID.me → National Student Clearinghouse: Student and alumni status checks 🇺🇸 United States National Student ClearinghouseSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source 🇺🇸 United States · Source category Participating US colleges and universitiesInstitution-reported enrollment recordsDocumented National Student Clearinghouse: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. National Student Clearinghouse → Participating US colleges and universities: Institution-reported enrollment recordsID.me → National Student Clearinghouse: Student and alumni status checks 🇺🇸 United States National Student ClearinghouseSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source 🇺🇸 United States · Source category Participating US colleges and universitiesInstitution-reported enrollment recordsDocumented

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

National Student Clearinghouseuses suppliers & sources below ↓
United States
1 entry
Who uses National Student Clearinghouse?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from National Student Clearinghouse?
  • ID.me United States Student and alumni status checks Attribute exchange: students and alumni · United StatesProduct-specific integration Optional

    Current ID.me developer documentation names NSC as an authoritative source option for student/alumni community verification. Document review is an alternative; this is not every legal-identity check.

    Integration documentation
Data sources and integrations for National Student Clearinghouse
  • Participating US colleges and universities United States Source category · individual suppliers not identified Institution-reported enrollment records EnrollmentVerify · United StatesDeclared data source Documented

    EnrollmentVerify uses records reported by participating colleges and universities. This source category does not identify an individual school or prove every field passes downstream.

    Integration documentation
Who uses National Student Clearinghouse?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does National Student Clearinghouse use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

US verification-source context; no headquarters or processing-location assertion. Location source ↗

Participating US colleges and universities

Source category · not a named company United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Participating US colleges and universities: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. National Student Clearinghouse → Participating US colleges and universities: Institution-reported enrollment records 🇺🇸 United States · Source category Participating US colleges and universitiesSelected service · follow its suppliers → 🇺🇸 United States National Student ClearinghouseDocumented customer / upstream source Participating US colleges and universities: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. National Student Clearinghouse → Participating US colleges and universities: Institution-reported enrollment records 🇺🇸 United States · Source category Participating US colleges and universitiesSelected service · follow its suppliers → 🇺🇸 United States National Student ClearinghouseDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Participating US colleges and universitiesuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Participating US colleges and universities?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Participating US colleges and universities?
  • National Student Clearinghouse United States Institution-reported enrollment records EnrollmentVerify · United StatesDeclared data source Documented

    EnrollmentVerify uses records reported by participating colleges and universities. This source category does not identify an individual school or prove every field passes downstream.

    Integration documentation
Who uses Participating US colleges and universities?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Participating US colleges and universities use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Participating US colleges and universities

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Institutional enrollment-record source category; no named school or processing location inferred. Location source ↗

USAA

United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
USAA: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → USAA: Military and veteran status checks 🇺🇸 United States USAASelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source USAA: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → USAA: Military and veteran status checks 🇺🇸 United States USAASelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

USAAuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses USAA?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from USAA?
  • ID.me United States Military and veteran status checks Attribute exchange: military and veterans · United StatesProduct-specific integration Optional

    Current ID.me documentation lists USAA, SCRA or VA as example authoritative sources for military/veteran community status; official email or document review are alternatives. No universal use or commercial subcontract inferred.

    Integration documentation
Who uses USAA?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does USAA use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for USAA

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US military-status authoritative-check context; no supplier contract or office location inferred. Location source ↗

SCRA military-status service

Source category · not a named company United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
SCRA military-status service: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → SCRA military-status service: Military and veteran status checks 🇺🇸 United States · Source category SCRA military-status serviceSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source SCRA military-status service: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → SCRA military-status service: Military and veteran status checks 🇺🇸 United States · Source category SCRA military-status serviceSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

SCRA military-status serviceuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses SCRA military-status service?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from SCRA military-status service?
  • ID.me United States Military and veteran status checks Attribute exchange: military and veterans · United StatesProduct-specific integration Optional

    Current ID.me documentation lists USAA, SCRA or VA as example authoritative sources for military/veteran community status; official email or document review are alternatives. No universal use or commercial subcontract inferred.

    Integration documentation
Who uses SCRA military-status service?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does SCRA military-status service use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for SCRA military-status service

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US military-status authoritative-check context; no supplier contract or office location inferred. Location source ↗

US Department of Veterans Affairs

United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
US Department of Veterans Affairs: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → US Department of Veterans Affairs: Military and veteran status checks 🇺🇸 United States US Department of Veterans AffairsSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source US Department of Veterans Affairs: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → US Department of Veterans Affairs: Military and veteran status checks 🇺🇸 United States US Department of Veterans AffairsSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

US Department of Veterans Affairsuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses US Department of Veterans Affairs?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from US Department of Veterans Affairs?
  • ID.me United States Military and veteran status checks Attribute exchange: military and veterans · United StatesProduct-specific integration Optional

    Current ID.me documentation lists USAA, SCRA or VA as example authoritative sources for military/veteran community status; official email or document review are alternatives. No universal use or commercial subcontract inferred.

    Integration documentation
Who uses US Department of Veterans Affairs?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does US Department of Veterans Affairs use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for US Department of Veterans Affairs

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US military-status authoritative-check context; no supplier contract or office location inferred. Location source ↗

Sterling

United States

Component-use coverage not yet collected supplies 1 brands in this collection

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Sterling: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Sterling: In-person retail-kiosk verification channel 🇺🇸 United States SterlingSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source Sterling: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Sterling: In-person retail-kiosk verification channel 🇺🇸 United States SterlingSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Sterlinguses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Sterling?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Sterling?
  • ID.me United States In-person retail-kiosk verification channel Optional

    ID.me offers an optional in-person pathway through Sterling; this edge represents retail-channel infrastructure, not a data feed or every online verification.

    Integration documentation
What does Sterling use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Sterling?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Sterling

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US verification-source context; no headquarters or processing-location assertion. Location source ↗

Plaid

United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Plaid: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Plaid: Benefit-payment bank-account verification 🇺🇸 United States PlaidSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source Plaid: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. ID.me → Plaid: Benefit-payment bank-account verification 🇺🇸 United States PlaidSelected service · follow its suppliers → 🇺🇸 United States ID.meDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Plaiduses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Plaid?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Plaid?
  • ID.me United States Benefit-payment bank-account verification Announced government benefit-payment integration · United StatesProduct-specific integration Conditional · 2026-09-15

    September 2026 announced partnership combines ID.me person verification with Plaid financial-account verification for government benefit payments. Not proof of deployment at every agency or use in every ID.me check.

    Company announcement
Who uses Plaid?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Plaid use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Plaid

Upstream sources are not identified here. No provider names or individual contributors are inferred.

US verification-source context; no headquarters or processing-location assertion. Location source ↗

Login.gov

United States

3 component links documented customer coverage not yet collected

7 source / integration links · 0 downstream data users in this collection

Public code and operational documentation identify these interfaces. They do not establish current production activation or traffic allocation. The LexisNexis UK data examples and Socure’s banking/KYB integrations are not attributed to Login.gov.

The supply chain on the mapOrganizations expanded · country flags retained
Login.gov: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Login.gov → LexisNexis Risk Solutions: TrueID document authenticationLogin.gov → Acuant Inc.: Acuant browser capture SDKLogin.gov → Socure: Socure DocV document workflowLogin.gov → LexisNexis Risk Solutions: Instant Verify identity resolutionLogin.gov → LexisNexis Risk Solutions: Phone Finder identity correlationLogin.gov → LexisNexis Risk Solutions: ThreatMetrix device-risk assessmentLogin.gov → Socure: Socure ID+ KYCLogin.gov → Socure: Socure ID+ PhoneRiskLogin.gov → AAMVA: AAMVA DLDV record verificationLogin.gov → US Department of State: Department of State Passport APILexisNexis Risk Solutions → Acuant Inc.: Image processingAAMVA → Participating US DL/ID issuing agencies: DL/ID issuing-record matching 🇺🇸 United States Login.govSelected service · follow its suppliers → 🇺🇸 United States AAMVAAAMVA DLDV record verificationDocumented 🇺🇸 United States Acuant Inc.Acuant browser capture SDK · Image processingConditional · Documented 🇺🇸 United States LexisNexis Risk SolutionsTrueID document authentication · Instant Verify identity resolution · Phone Finder identity correlation · ThreatMetrix device-risk assessmentConditional 🇺🇸 United States · Source category Participating US DL/ID issuing agenciesDL/ID issuing-record matchingDocumented 🇺🇸 United States SocureSocure DocV document workflow · Socure ID+ KYC · Socure ID+ PhoneRiskConditional 🇺🇸 United States US Department of StateDepartment of State Passport APIDocumented Login.gov: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Login.gov → LexisNexis Risk Solutions: TrueID document authenticationLogin.gov → Acuant Inc.: Acuant browser capture SDKLogin.gov → Socure: Socure DocV document workflowLogin.gov → LexisNexis Risk Solutions: Instant Verify identity resolutionLogin.gov → LexisNexis Risk Solutions: Phone Finder identity correlationLogin.gov → LexisNexis Risk Solutions: ThreatMetrix device-risk assessmentLogin.gov → Socure: Socure ID+ KYCLogin.gov → Socure: Socure ID+ PhoneRiskLogin.gov → AAMVA: AAMVA DLDV record verificationLogin.gov → US Department of State: Department of State Passport APILexisNexis Risk Solutions → Acuant Inc.: Image processingAAMVA → Participating US DL/ID issuing agencies: DL/ID issuing-record matching 🇺🇸 United States Login.govSelected service · follow its suppliers → 🇺🇸 United States AAMVAAAMVA DLDV record verificationDocumented 🇺🇸 United States Acuant Inc.Acuant browser capture SDK · Image processingConditional · Documented 🇺🇸 United States LexisNexis Risk SolutionsTrueID document authentication · Instant Verify identity resolution · Phone Finder identity correlation · ThreatMetrix device-risk assessmentConditional 🇺🇸 United States · Source category Participating US DL/ID issuing agenciesDL/ID issuing-record matchingDocumented 🇺🇸 United States SocureSocure DocV document workflow · Socure ID+ KYC · Socure ID+ PhoneRiskConditional 🇺🇸 United States US Department of StateDepartment of State Passport APIDocumented

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Login.govuses suppliers & sources below ↓
United States
5 entries
  • LexisNexis Risk Solutions →
    Verification technology

    TrueID document authentication

    Conditional · 2026-10-16
    Scope & evidence

    Public implementation submits document images and, when the configured flow requires it, a selfie to TrueID. Commit date identifies source revision, not production activation or allocation. The permitted Acuant upstream hop is specific to TrueID; UK Business Services data sources are not composed into this path.

    Login.gov: Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23 ↗
    ↓ Further upstream · separately sourced
    Data & authoritative sources

    Instant Verify identity resolution

    Conditional · 2026-10-16

    Login.gov Instant Verify integration · United States
    Product-specific integration

    Scope & evidence

    Public implementation builds US identity-resolution requests. Production enablement and customer-specific data sources are not established by this code. No UK CRA-source path is inferred.

    Login.gov: Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23 ↗
    Data & authoritative sources

    Phone Finder identity correlation

    Conditional · 2026-10-16

    Login.gov Phone Finder integration · United States
    Product-specific integration

    Scope & evidence

    Public implementation sends identity attributes and a phone number to a configured Phone Finder workflow. This records an implemented interface, not current production allocation or underlying carrier suppliers.

    Login.gov: Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23 ↗
    Data & authoritative sources

    ThreatMetrix device-risk assessment

    Conditional · 2026-10-16

    Login.gov ThreatMetrix DDP integration · United States
    Product-specific integration

    Scope & evidence

    Public DDP implementation builds device-risk requests linked to a ThreatMetrix session identifier. Presence of this implementation does not establish which production transactions invoke it or an individual data-transfer route.

    Login.gov: Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23 ↗
  • Acuant Inc. →
    Verification technology

    Acuant browser capture SDK

    Conditional · 2026-10-16
    Scope & evidence

    Public integration selects Acuant SDK versions and configures the Acuant SDK connection. This is capture technology, distinct from the downstream document-authentication decision. A direct procurement contract or universal production use is not established.

    Login.gov: Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23 ↗
  • Socure →
    Verification technology

    Socure DocV document workflow

    Conditional · 2026-10-16
    Scope & evidence

    Public implementation supports configured document-only and document-with-selfie use cases, including licence and passport requests. The official test plan also documents Socure staging tests; neither source establishes production allocation. No RiskOS or bank-data upstream integration is inferred.

    Login.gov: Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23 ↗
    Data & authoritative sources

    Socure ID+ KYC

    Conditional · 2026-10-16

    Login.gov Socure ID+ KYC integration · United States
    Product-specific integration

    Scope & evidence

    Public implementation requests the US kyc module for identity resolution. Source code is not proof of production activation. Other Socure products, RiskOS connectors and bank-data feeds are not assumed in this path.

    Login.gov: Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23 ↗
    Data & authoritative sources

    Socure ID+ PhoneRisk

    Conditional · 2026-10-16

    Login.gov Socure ID+ PhoneRisk integration · United States
    Product-specific integration

    Scope & evidence

    Public implementation requests the US phonerisk module and correlation signals. Production activation, traffic allocation and particular upstream data vendors are not established.

    Login.gov: Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23 ↗
  • AAMVA →
    Data & authoritative sources

    AAMVA DLDV record verification

    Documented

    Login.gov AAMVA DLDV integration · United States
    Product-specific integration

    Scope & evidence

    Official outage documentation names AAMVA DLDV as an identity-verification dependency. This is record verification against participating issuing jurisdictions, not document-image authentication, face matching or a claim that every jurisdiction participates. Current production routing is not established by the handbook.

    Login.gov: Vendor outage response process ↗
    ↓ Further upstream · separately sourced
    • 🇺🇸 Participating US DL/ID issuing agenciesSource category

      DL/ID issuing-record matching

      Evidence for this hop

      DLDV compares submitted identification attributes against participating issuing-jurisdiction records and returns match indicators. Issuing agencies are a source category; no specific state, full record disclosure or complete participating-state inventory is inferred.

      AAMVA ↗
  • US Department of State →
    Data & authoritative sources

    Department of State Passport API

    Documented

    Login.gov passport-verification integration · United States
    Product-specific integration

    Scope & evidence

    Official vendor-outage documentation lists the DoS Passport API. This establishes an operationally documented service dependency, not its current activation, exact returned fields, passport-chip authentication or a universal check for every user.

    Login.gov: Vendor outage response process ↗

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
What does Login.gov use?
  • LexisNexis Risk Solutions United States TrueID document authentication Conditional · 2026-10-16

    Public implementation submits document images and, when the configured flow requires it, a selfie to TrueID. Commit date identifies source revision, not production activation or allocation. The permitted Acuant upstream hop is specific to TrueID; UK Business Services data sources are not composed into this path.

    Integration documentation
  • Acuant Inc. United States Acuant browser capture SDK Conditional · 2026-10-16

    Public integration selects Acuant SDK versions and configures the Acuant SDK connection. This is capture technology, distinct from the downstream document-authentication decision. A direct procurement contract or universal production use is not established.

    Integration documentation
  • Socure United States Socure DocV document workflow Conditional · 2026-10-16

    Public implementation supports configured document-only and document-with-selfie use cases, including licence and passport requests. The official test plan also documents Socure staging tests; neither source establishes production allocation. No RiskOS or bank-data upstream integration is inferred.

    Integration documentation
Data sources and integrations for Login.gov
  • LexisNexis Risk Solutions United States Instant Verify identity resolution Login.gov Instant Verify integration · United StatesProduct-specific integration Conditional · 2026-10-16

    Public implementation builds US identity-resolution requests. Production enablement and customer-specific data sources are not established by this code. No UK CRA-source path is inferred.

    Integration documentation
  • LexisNexis Risk Solutions United States Phone Finder identity correlation Login.gov Phone Finder integration · United StatesProduct-specific integration Conditional · 2026-10-16

    Public implementation sends identity attributes and a phone number to a configured Phone Finder workflow. This records an implemented interface, not current production allocation or underlying carrier suppliers.

    Integration documentation
  • LexisNexis Risk Solutions United States ThreatMetrix device-risk assessment Login.gov ThreatMetrix DDP integration · United StatesProduct-specific integration Conditional · 2026-10-16

    Public DDP implementation builds device-risk requests linked to a ThreatMetrix session identifier. Presence of this implementation does not establish which production transactions invoke it or an individual data-transfer route.

    Integration documentation
  • Socure United States Socure ID+ KYC Login.gov Socure ID+ KYC integration · United StatesProduct-specific integration Conditional · 2026-10-16

    Public implementation requests the US kyc module for identity resolution. Source code is not proof of production activation. Other Socure products, RiskOS connectors and bank-data feeds are not assumed in this path.

    Integration documentation
  • Socure United States Socure ID+ PhoneRisk Login.gov Socure ID+ PhoneRisk integration · United StatesProduct-specific integration Conditional · 2026-10-16

    Public implementation requests the US phonerisk module and correlation signals. Production activation, traffic allocation and particular upstream data vendors are not established.

    Integration documentation
  • AAMVA United States AAMVA DLDV record verification Login.gov AAMVA DLDV integration · United StatesProduct-specific integration Documented

    Official outage documentation names AAMVA DLDV as an identity-verification dependency. This is record verification against participating issuing jurisdictions, not document-image authentication, face matching or a claim that every jurisdiction participates. Current production routing is not established by the handbook.

    Integration documentation
  • US Department of State United States Department of State Passport API Login.gov passport-verification integration · United StatesProduct-specific integration Documented

    Official vendor-outage documentation lists the DoS Passport API. This establishes an operationally documented service dependency, not its current activation, exact returned fields, passport-chip authentication or a universal check for every user.

    Integration documentation
Who uses Login.gov?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

Who uses data from Login.gov?

No downstream data users documented in this collection. This does not establish that there are none.

United States federal identity service; country context, not a processing location. Location source ↗

AAMVA

United States

Component-use coverage not yet collected customer coverage not yet collected

1 source / integration links · 2 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
AAMVA: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. AAMVA → Participating US DL/ID issuing agencies: DL/ID issuing-record matchingLogin.gov → AAMVA: AAMVA DLDV record verificationKenshiki Pulse → AAMVA: State-ID record verification 🇺🇸 United States AAMVASelected service · follow its suppliers → 🇺🇸 United States Kenshiki PulseDocumented customer / upstream source 🇺🇸 United States Login.govDocumented customer / upstream source 🇺🇸 United States · Source category Participating US DL/ID issuing agenciesDL/ID issuing-record matchingDocumented AAMVA: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. AAMVA → Participating US DL/ID issuing agencies: DL/ID issuing-record matchingLogin.gov → AAMVA: AAMVA DLDV record verificationKenshiki Pulse → AAMVA: State-ID record verification 🇺🇸 United States AAMVASelected service · follow its suppliers → 🇺🇸 United States Kenshiki PulseDocumented customer / upstream source 🇺🇸 United States Login.govDocumented customer / upstream source 🇺🇸 United States · Source category Participating US DL/ID issuing agenciesDL/ID issuing-record matchingDocumented

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

AAMVAuses suppliers & sources below ↓
United States
1 entry
  • Participating US DL/ID issuing agencies →Source category
    Data & authoritative sources

    DL/ID issuing-record matching

    Documented

    Driver’s License Data Verification (DLDV) · United States
    Declared data source

    Scope & evidence

    DLDV compares submitted identification attributes against participating issuing-jurisdiction records and returns match indicators. Issuing agencies are a source category; no specific state, full record disclosure or complete participating-state inventory is inferred.

    AAMVA: Driver’s License Data Verification (DLDV) Service ↗
Who uses AAMVA?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from AAMVA?
  • Login.gov United States AAMVA DLDV record verification Login.gov AAMVA DLDV integration · United StatesProduct-specific integration Documented

    Official outage documentation names AAMVA DLDV as an identity-verification dependency. This is record verification against participating issuing jurisdictions, not document-image authentication, face matching or a claim that every jurisdiction participates. Current production routing is not established by the handbook.

    Integration documentation
  • Kenshiki Pulse United States State-ID record verification Pulse state-ID verification · Supported service coverageDeclared data source Documented · 2026-10-17

    State-ID records are checked through AAMVA. State-ID processing uses Kenshiki’s own code.

    Operator declaration
Data sources and integrations for AAMVA
  • Participating US DL/ID issuing agencies United States Source category · individual suppliers not identified DL/ID issuing-record matching Driver’s License Data Verification (DLDV) · United StatesDeclared data source Documented

    DLDV compares submitted identification attributes against participating issuing-jurisdiction records and returns match indicators. Issuing agencies are a source category; no specific state, full record disclosure or complete participating-state inventory is inferred.

    Integration documentation
Who uses AAMVA?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does AAMVA use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

United States DLDV service context; country marker does not identify a hosting location. Location source ↗

Participating US DL/ID issuing agencies

Source category · not a named company United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Participating US DL/ID issuing agencies: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. AAMVA → Participating US DL/ID issuing agencies: DL/ID issuing-record matching 🇺🇸 United States · Source category Participating US DL/ID issuing agenciesSelected service · follow its suppliers → 🇺🇸 United States AAMVADocumented customer / upstream source Participating US DL/ID issuing agencies: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. AAMVA → Participating US DL/ID issuing agencies: DL/ID issuing-record matching 🇺🇸 United States · Source category Participating US DL/ID issuing agenciesSelected service · follow its suppliers → 🇺🇸 United States AAMVADocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Participating US DL/ID issuing agenciesuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Participating US DL/ID issuing agencies?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Participating US DL/ID issuing agencies?
  • AAMVA United States DL/ID issuing-record matching Driver’s License Data Verification (DLDV) · United StatesDeclared data source Documented

    DLDV compares submitted identification attributes against participating issuing-jurisdiction records and returns match indicators. Issuing agencies are a source category; no specific state, full record disclosure or complete participating-state inventory is inferred.

    Integration documentation
Who uses Participating US DL/ID issuing agencies?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Participating US DL/ID issuing agencies use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Participating US DL/ID issuing agencies

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Source category: participating US issuing jurisdictions, not a named supplier or universal state coverage. Location source ↗

US Department of State

United States

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
US Department of State: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Login.gov → US Department of State: Department of State Passport API 🇺🇸 United States US Department of StateSelected service · follow its suppliers → 🇺🇸 United States Login.govDocumented customer / upstream source US Department of State: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Login.gov → US Department of State: Department of State Passport API 🇺🇸 United States US Department of StateSelected service · follow its suppliers → 🇺🇸 United States Login.govDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

US Department of Stateuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses US Department of State?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from US Department of State?
  • Login.gov United States Department of State Passport API Login.gov passport-verification integration · United StatesProduct-specific integration Documented

    Official vendor-outage documentation lists the DoS Passport API. This establishes an operationally documented service dependency, not its current activation, exact returned fields, passport-chip authentication or a universal check for every user.

    Integration documentation
Who uses US Department of State?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does US Department of State use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for US Department of State

Upstream sources are not identified here. No provider names or individual contributors are inferred.

United States federal passport-service context; not an API hosting location. Location source ↗

Aduna

🌐 Country not asserted

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 1 downstream data users in this collection

Aduna is a joint venture: Ericsson owns 50%; twelve telecom operators jointly own the other 50%.

The supply chain on the mapOrganizations expanded · country flags retained
Aduna: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Kenshiki Pulse → Aduna: Phone verification 🌐 Country not asserted AdunaSelected service · follow its suppliers → 🇺🇸 United States Kenshiki PulseDocumented customer / upstream source Aduna: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. Kenshiki Pulse → Aduna: Phone verification 🌐 Country not asserted AdunaSelected service · follow its suppliers → 🇺🇸 United States Kenshiki PulseDocumented customer / upstream source

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Adunauses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

Who uses Aduna?

Explore the services this supplier feeds.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses data from Aduna?
  • Kenshiki Pulse United States Phone verification Pulse phone verification · Supported service coverageDeclared data source Documented · 2026-10-17

    Aduna provides the phone check.

    Operator declaration
Who uses Aduna?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Aduna use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Data sources and integrations for Aduna

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Corporate ownership · separate from component use
  • Ericsson Sweden 50% equity ownership Documented · 2025-07-29

    Ericsson owns 50% of Aduna; twelve telecom operators jointly own the remaining 50%. Corporate ownership is separate from Pulse’s phone-check relationship.

    Ownership source

Country context has not been sourced in this collection.

Ericsson

Sweden

Component-use coverage not yet collected customer coverage not yet collected

0 source / integration links · 0 downstream data users in this collection

The supply chain on the mapOrganizations expanded · country flags retained
Ericsson: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. 🇸🇪 Sweden EricssonSelected service · follow its suppliers → Ericsson: organizations and their supplier connections Each box is a separate organization or explicitly labelled source category. Arrows run from customer to supplier. Nodes are expanded for readability, grouped in country order rather than plotted at office addresses. Amber dashed lines are data relationships; teal lines are technology relationships. Click an organization to explore it. 🇸🇪 Sweden EricssonSelected service · follow its suppliers →

— Technology supplier┄ Data source / integration

One box per organization. Dense regions are expanded so companies remain separate; flags identify country context. Arrows show documented relationships, not personal-data routes.

Ericssonuses suppliers & sources below ↓

Upstream suppliers and sources have not been identified in this collection.

A connection identifies a documented supplier, source or integration—not every verification’s route. Further hops appear only where the product scopes are compatible. Missing hops remain unknown; ownership is shown separately.

All relationship details · suppliers and customers
Who uses Ericsson?

No customer integrations documented in this collection. That is a coverage gap, not a claim that this company has no customers.

What does Ericsson use?

No third-party components documented in this collection. That does not establish that the company builds everything itself.

Who uses data from Ericsson?

No downstream data users documented in this collection. This does not establish that there are none.

Data sources and integrations for Ericsson

Upstream sources are not identified here. No provider names or individual contributors are inferred.

Corporate ownership · separate from component use
  • Aduna 🌐 Country not asserted 50% equity ownership Documented · 2025-07-29

    Ericsson owns 50% of Aduna; twelve telecom operators jointly own the remaining 50%. Corporate ownership is separate from Pulse’s phone-check relationship.

    Ownership source

Ericsson headquarters in Stockholm, Sweden. Location source ↗

The data layer distinguishes declared sources, source examples, reseller integrations, and connectors using the customer’s own provider account. Product and jurisdiction are shown per link; paths do not establish that every field reaches the final service. Selected public evidence, checked 2026-10-17; not a complete industry inventory. Registry entries, integration documentation, supplier case studies, press reports, and ownership are labelled separately. Optional, conditional, backup, and historical relationships retain their scope. A source documents a relationship, not every customer’s deployment. Geography is shown at country level; lines do not represent personal-data routes. Download the sourced relationship data (JSON) ↗
Read the map’s sources and relationship details

The sources, in their own words

Retrieved 2026-10-17.

LexisNexis Risk Solutions

Veriff

  • EXL — Human review support

    Full source read. Documented · Supplier registry. Verification review support; registry lists India as the processing country.

    “EXLService (Ireland) Limited … What does the sub-processor do? Provides review support for verification services. What is the primary processing location? India.”
    Veriff, Sub-processors used by Veriff (Oct 16, 2026)
  • Resistant AI — Tampering & address-document checks

    Full source read. Documented · Supplier registry. Registry specifies tampering and proof-of-address fraud checks.

    “Resistant AI, s.r.o., a company registered in the Czech Republic … What does the sub-processor do? Tampering Check & Proof of Address Fraud Check”
    Veriff, Sub-processors used by Veriff (Oct 16, 2026)

Entrust IDV

GBG plc

  • Innovolar (GBG registry name) — Passport chip reading

    Full source read. Documented · Supplier registry. IDscan Enterprise (web); third-party NFC technology for chip details and images.

    “Innovolar — Netherlands — Technology provider: Near Field Communication reads details and images from biometric chips”
    GBG plc, Identity Authorised Sub processor List, IDscan Enterprise (web)
  • Acuant Inc. — Acquisition

    Full source read. Historical evidence · Ownership source · 2021. GBG’s history records the 2021 acquisition and subsequent integration under the IDology brand.

    “Acuant, the leading US specialist in AI-powered digital identity verification joins GBG”
    GBG, Our history

Persona

  • Anthropic — Data extraction & analysis

    Full source read. Conditional · Supplier registry · 2026-08-22. Conditional service; registry listing does not mean every Persona check uses it.

    “Anthropic — United States of America (US) — Data Extraction and Analysis — Conditional”
    Persona, Subprocessors (Last updated: August 22, 2026)
  • OpenAI — Data extraction & analysis

    Full source read. Conditional · Supplier registry · 2026-08-22. Conditional service; registry listing does not mean every Persona check uses it.

    “OpenAI — United States of America (US) — Data Extraction and Analysis — Conditional”
    Persona, Subprocessors (Last updated: August 22, 2026)
  • Groq — Data extraction & analysis

    Full source read. Conditional · Supplier registry · 2026-08-22. Conditional service; registry listing does not mean every Persona check uses it.

    “Groqcloud — United States of America (US) — Data Extraction and Analysis — Conditional”
    Persona, Subprocessors (Last updated: August 22, 2026)
  • Resistant AI — Document analysis

    Full source read. Conditional · Supplier registry · 2026-08-22. Conditional service in Persona’s registry; service country is the United States, distinct from Resistant AI’s Czech corporate location.

    “Resistant AI”
    Persona, Subprocessors, updated August 22, 2026

ID.me

  • iProov — Liveness detection

    Full source read. Historical evidence · Integration documentation · 2022. ID.me’s 2022 white paper names iProov for presentation attack detection; current deployment not established here.

    “For PAD, to ensure the selfie submitted is actually that user’s face, ID.me partners with iProov”
    ID.me, Anti-Bias White Paper, page 12
  • Paravision — Face recognition

    Full source read. Documented · Company announcement · 2025-07-17. Paravision’s July 2025 announcement names ID.me’s deployment of Identity AI.

    “ID.me’s deployment of Identity AI for seamless, secure access to digital services.”
    Paravision, Paravision Unveils Converge 4
  • Amazon Rekognition — Face recognition

    Search excerpt checked. Historical evidence · Press report · 2022. Reported use in January 2022; current deployment not established here.

    “ID.me confirmed Thursday in an email to CyberScoop that the company uses Amazon's Rekognition facial recognition product.”
    CyberScoop, ID.me CEO backtracks on claims company doesn't use powerful facial recognition tech
  • Experian (US verification source) — Authoritative identity-record comparison — Identity-record checks disclosed in 2022, United States

    Full source read. Historical evidence · Integration documentation · 2022-03-25. Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    “Experian”
    ID.me, Montana Economic Affairs Interim Committee response, page 5
  • TeleSign — Authoritative identity-record comparison — Identity-record checks disclosed in 2022, United States

    Full source read. Historical evidence · Integration documentation · 2022-03-25. Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    “TeleSign”
    ID.me, Montana Economic Affairs Interim Committee response, page 5
  • Prove — Authoritative identity-record comparison — Identity-record checks disclosed in 2022, United States

    Full source read. Historical evidence · Integration documentation · 2022-03-25. Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    “Prove”
    ID.me, Montana Economic Affairs Interim Committee response, page 5
  • National Plan & Provider Enumeration System (NPPES) — Authoritative identity-record comparison — Identity-record checks disclosed in 2022, United States

    Full source read. Historical evidence · Integration documentation · 2022-03-25. Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    “(NPPES)”
    ID.me, Montana Economic Affairs Interim Committee response, page 5
  • TransUnion (US verification source) — Authoritative identity-record comparison — Identity-record checks disclosed in 2022, United States

    Full source read. Historical evidence · Integration documentation · 2022-03-25. Named in ID.me’s March 2022 response to Montana legislators. Historical supplier disclosure; current deployment and per-product use not established.

    “TransUnion”
    ID.me, Montana Economic Affairs Interim Committee response, page 5
  • Prove — Mobile-device digital risk — Mobile-device risk disclosed in 2022, United States

    Full source read. Historical evidence · Integration documentation · 2022-03-25. ID.me named this mobile-risk partner in March 2022; current deployment, underlying carriers and exact data fields not established.

    “Prove”
    ID.me, Montana Economic Affairs Interim Committee response, page 5
  • TeleSign — Mobile-device digital risk — Mobile-device risk disclosed in 2022, United States

    Full source read. Historical evidence · Integration documentation · 2022-03-25. ID.me named this mobile-risk partner in March 2022; current deployment, underlying carriers and exact data fields not established.

    “TeleSign”
    ID.me, Montana Economic Affairs Interim Committee response, page 5
  • FingerprintJS — Mobile-device digital risk — Mobile-device risk disclosed in 2022, United States

    Full source read. Historical evidence · Integration documentation · 2022-03-25. ID.me named this mobile-risk partner in March 2022; current deployment, underlying carriers and exact data fields not established.

    “FingerprintJS”
    ID.me, Montana Economic Affairs Interim Committee response, page 5
  • Fraud.net — Behavior analysis — Behavior analysis disclosed in 2022, United States

    Full source read. Historical evidence · Integration documentation · 2022-03-25. Named by ID.me in March 2022; current deployment and exact inputs not established.

    “Fraud.net”
    ID.me, Montana Economic Affairs Interim Committee response, page 5
  • AuthenticID — Document and biometric verification

    Full source read. Historical evidence · Integration documentation · 2022-03-25. ID.me’s March 2022 response groups AuthenticID with document authenticity and credential-photo/selfie comparison partners. It does not assign individual subfunctions; current deployment not established.

    “AuthenticID”
    ID.me, Montana Economic Affairs Interim Committee response, page 5
  • National Student Clearinghouse — Student and alumni status checks — Attribute exchange: students and alumni, United States

    Full source read. Optional · Integration documentation. Current ID.me developer documentation names NSC as an authoritative source option for student/alumni community verification. Document review is an alternative; this is not every legal-identity check.

    “National Student Clearinghouse”
    ID.me, Attribute exchange overview
  • USAA — Military and veteran status checks — Attribute exchange: military and veterans, United States

    Full source read. Optional · Integration documentation. Current ID.me documentation lists USAA, SCRA or VA as example authoritative sources for military/veteran community status; official email or document review are alternatives. No universal use or commercial subcontract inferred.

    “USAA”
    ID.me, Attribute exchange overview
  • SCRA military-status service — Military and veteran status checks — Attribute exchange: military and veterans, United States

    Full source read. Optional · Integration documentation. Current ID.me documentation lists USAA, SCRA or VA as example authoritative sources for military/veteran community status; official email or document review are alternatives. No universal use or commercial subcontract inferred.

    “SCRA”
    ID.me, Attribute exchange overview
  • US Department of Veterans Affairs — Military and veteran status checks — Attribute exchange: military and veterans, United States

    Full source read. Optional · Integration documentation. Current ID.me documentation lists USAA, SCRA or VA as example authoritative sources for military/veteran community status; official email or document review are alternatives. No universal use or commercial subcontract inferred.

    “VA”
    ID.me, Attribute exchange overview
  • Sterling — In-person retail-kiosk verification channel

    Full source read. Optional · Integration documentation. ID.me offers an optional in-person pathway through Sterling; this edge represents retail-channel infrastructure, not a data feed or every online verification.

    “ID.me offers In-Person Verification services through a partnership with Sterling.”
    ID.me, Identity Verification
  • Plaid — Benefit-payment bank-account verification — Announced government benefit-payment integration, United States

    Full source read. Conditional · Company announcement · 2026-09-15. September 2026 announced partnership combines ID.me person verification with Plaid financial-account verification for government benefit payments. Not proof of deployment at every agency or use in every ID.me check.

    “with ID.me verifying the person and Plaid verifying the bank account.”
    ID.me, ID.me and Plaid partnership for government benefit payments

Jumio

  • FaceTec — 3D liveness detection

    Search excerpt checked. Historical evidence · Press report. Reported integration in 2018; current deployment not established here.

    “Jumio added FaceTec's 3D liveness detection to its verification suite in 2018”
    Biometric Update, FaceTec company news

RELX

Daon (TrustX)

  • Regula — Document processing

    Full source read. Documented · Integration documentation. TrustX documents a configurable Regula document processor; not evidence that every Daon workflow selects it.

    “The image profile will determine whether a cropped or uncropped image is sent to Regula for processing.”
    Daon, TrustX Document Processing

Luciditi (Arissian)

  • Regula — Document Reader SDK

    Full source read. Documented · Supplier case study. Regula’s customer story describes the SDK embedded in Luciditi’s mobile and web platforms; current deployment not independently verified.

    “For the purposes of automatic document recognition and verification and accurate data extraction, Luciditi platform employed Regula Document Reader SDK.”
    Regula, Arissian Ltd., the company behind Luciditi

REACT (ID Wallet)

  • Regula — Document Reader SDK

    Full source read. Documented · Supplier case study. Regula’s customer story describes its SDK embedded in REACT’s ID Wallet, on mobile and web; current deployment not independently verified.

    “Regula Document Reader SDK was embedded into REACT’s ID Wallet solution”
    Regula, Digital Identification Provider REACT Partnered with Regula

Equifax Limited

  • UK financial-account providers — Account-performance information — Core credit referencing, United Kingdom

    Full source read. Documented · Processing notice. CRAIN describes this source category; it does not establish which underlying fields reach LexisNexis.

    “This data is provided from banks, building societies and other financial services providers”
    Experian, Equifax and TransUnion, Credit Reference Agency Information Notice
  • Registry Trust — Judgment-register information — Core credit referencing, United Kingdom

    Full source read. Documented · Processing notice. Documented CRA source; not proof of a particular person’s records traversing the whole chain.

    “Registry Trust Limited, which supplies the data on the registers to us.”
    Experian, Equifax and TransUnion, Credit Reference Agency Information Notice

Experian Limited

  • UK financial-account providers — Account-performance information — Core credit referencing, United Kingdom

    Full source read. Documented · Processing notice. CRAIN describes this source category; it does not establish which underlying fields reach LexisNexis.

    “This data is provided from banks, building societies and other financial services providers”
    Experian, Equifax and TransUnion, Credit Reference Agency Information Notice
  • Registry Trust — Judgment-register information — Core credit referencing, United Kingdom

    Full source read. Documented · Processing notice. Documented CRA source; not proof of a particular person’s records traversing the whole chain.

    “Registry Trust Limited, which supplies the data on the registers to us.”
    Experian, Equifax and TransUnion, Credit Reference Agency Information Notice

Socure

  • Early Warning Services — Account validation and ownership — Account Intelligence Premier, United States

    Full source read. Documented · Integration documentation. Approved Premier integration. Does not establish use in every Socure identity check.

    “Socure is proud to partner with Early Warning Services”
    Socure, Account Intelligence Premier Services
  • Middesk — Business verification — RiskOS Middesk integration, United States

    Full source read. Documented · Integration documentation. Available through a RiskOS reseller integration; selected workflows, not every Socure verification.

    “Middesk”
    Socure, Middesk partner documentation
  • Kyckr — Company profiles and registry documents — RiskOS Kyckr integration, Multiple jurisdictions

    Full source read. Documented · Integration documentation. Available through a RiskOS reseller integration; selected workflows, not every Socure verification.

    “Kyckr”
    Socure, Kyckr partner documentation
  • Thomson Reuters CLEAR — Business and person searches — RiskOS CLEAR connector, United States

    Full source read. Documented · Integration documentation. Requires the customer’s own partner account; not a centrally licensed feed for every Socure customer.

    “Thomson Reuters CLEAR”
    Socure, Thomson Reuters CLEAR partner documentation
  • Socure data vendors · names undisclosed — Verification-supporting data — Services covered by the notice, Global notice; product terms apply

    Full source read. Documented · Processing notice · 2026-10-01. The service notice discloses a category, not a full named-provider list.

    “from companies that supply us with data to support verification”
    Socure, Global Services Privacy Notice

Early Warning Services

  • Participating US financial institutions — Bank-account activity data — Consumer information services, United States

    Full source read. Documented · Integration documentation. Contributing institutions are a category; no bank or complete downstream dataset is inferred.

    “data provided to us by thousands of financial institutions”
    Early Warning Services, Consumer Information

Middesk

  • US state business registrations — Business formation data — Formation data, United States

    Full source read. Documented · Integration documentation. Formation-data source only; not a claim about every Middesk product.

    “Middesk sources formation data from Secretary of State registrations”
    Middesk, Formation data

Kyckr

  • Official company registries — Live company-register data — Company registry services, Multiple jurisdictions

    Full source read. Documented · Integration documentation. Official registry retrieval; coverage varies by jurisdiction and request.

    “Kyckr retrieves live data directly from official government sources at the time of your request.”
    Kyckr, Frequently asked questions

National Student Clearinghouse

  • Participating US colleges and universities — Institution-reported enrollment records — EnrollmentVerify, United States

    Full source read. Documented · Integration documentation. EnrollmentVerify uses records reported by participating colleges and universities. This source category does not identify an individual school or prove every field passes downstream.

    “By using the enrollment data that you already report to the Clearinghouse”
    National Student Clearinghouse, Education Verifications

Login.gov

  • LexisNexis Risk Solutions — TrueID document authentication

    Full source read. Conditional · Integration documentation · 2026-10-16. Public implementation submits document images and, when the configured flow requires it, a selfie to TrueID. Commit date identifies source revision, not production activation or allocation. The permitted Acuant upstream hop is specific to TrueID; UK Business Services data sources are not composed into this path.

    “class TrueIdRequest”
    Login.gov, Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23
  • LexisNexis Risk Solutions — Instant Verify identity resolution — Login.gov Instant Verify integration, United States

    Full source read. Conditional · Integration documentation · 2026-10-16. Public implementation builds US identity-resolution requests. Production enablement and customer-specific data sources are not established by this code. No UK CRA-source path is inferred.

    “module InstantVerify”
    Login.gov, Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23
  • LexisNexis Risk Solutions — Phone Finder identity correlation — Login.gov Phone Finder integration, United States

    Full source read. Conditional · Integration documentation · 2026-10-16. Public implementation sends identity attributes and a phone number to a configured Phone Finder workflow. This records an implemented interface, not current production allocation or underlying carrier suppliers.

    “module PhoneFinder”
    Login.gov, Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23
  • LexisNexis Risk Solutions — ThreatMetrix device-risk assessment — Login.gov ThreatMetrix DDP integration, United States

    Full source read. Conditional · Integration documentation · 2026-10-16. Public DDP implementation builds device-risk requests linked to a ThreatMetrix session identifier. Presence of this implementation does not establish which production transactions invoke it or an individual data-transfer route.

    “class ThreatMetrixRequest”
    Login.gov, Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23
  • Acuant Inc. — Acuant browser capture SDK

    Full source read. Conditional · Integration documentation · 2026-10-16. Public integration selects Acuant SDK versions and configures the Acuant SDK connection. This is capture technology, distinct from the downstream document-authentication decision. A direct procurement contract or universal production use is not established.

    “us.acas.acuant.net”
    Login.gov, Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23
  • Socure — Socure DocV document workflow

    Full source read. Conditional · Integration documentation · 2026-10-16. Public implementation supports configured document-only and document-with-selfie use cases, including licence and passport requests. The official test plan also documents Socure staging tests; neither source establishes production allocation. No RiskOS or bank-data upstream integration is inferred.

    “socure_docv_document_request_endpoint”
    Login.gov, Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23
  • Socure — Socure ID+ KYC — Login.gov Socure ID+ KYC integration, United States

    Full source read. Conditional · Integration documentation · 2026-10-16. Public implementation requests the US kyc module for identity resolution. Source code is not proof of production activation. Other Socure products, RiskOS connectors and bank-data feeds are not assumed in this path.

    “modules: ['kyc']”
    Login.gov, Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23
  • Socure — Socure ID+ PhoneRisk — Login.gov Socure ID+ PhoneRisk integration, United States

    Full source read. Conditional · Integration documentation · 2026-10-16. Public implementation requests the US phonerisk module and correlation signals. Production activation, traffic allocation and particular upstream data vendors are not established.

    “modules: ['phonerisk']”
    Login.gov, Public identity-idp implementation at commit 9097702c0eb63d9e4ad2b371b5e48ddee519ed23
  • AAMVA — AAMVA DLDV record verification — Login.gov AAMVA DLDV integration, United States

    Full source read. Documented · Integration documentation. Official outage documentation names AAMVA DLDV as an identity-verification dependency. This is record verification against participating issuing jurisdictions, not document-image authentication, face matching or a claim that every jurisdiction participates. Current production routing is not established by the handbook.

    “AAMVA DLDV”
    Login.gov, Vendor outage response process
  • US Department of State — Department of State Passport API — Login.gov passport-verification integration, United States

    Full source read. Documented · Integration documentation. Official vendor-outage documentation lists the DoS Passport API. This establishes an operationally documented service dependency, not its current activation, exact returned fields, passport-chip authentication or a universal check for every user.

    “DoS Passport API”
    Login.gov, Vendor outage response process

AAMVA

  • Participating US DL/ID issuing agencies — DL/ID issuing-record matching — Driver’s License Data Verification (DLDV), United States

    Full source read. Documented · Integration documentation. DLDV compares submitted identification attributes against participating issuing-jurisdiction records and returns match indicators. Issuing agencies are a source category; no specific state, full record disclosure or complete participating-state inventory is inferred.

    “verify DL/ID information against data from the issuing agency”
    AAMVA, Driver’s License Data Verification (DLDV) Service

Kenshiki Pulse

  • AAMVA — State-ID record verification — Pulse state-ID verification, Supported service coverage

    Full source read. Documented · Operator declaration · 2026-10-17. State-ID records are checked through AAMVA. State-ID processing uses Kenshiki’s own code.

    “Kenshiki’s declared verification chain: ICAO for passports; AAMVA for state ID; TransUnion for SSN; Aduna for phone checks. Face matching and state-ID processing use Kenshiki’s own code. AAMVA remains the state-ID record check.”
    Kenshiki Labs, Pulse verification chain · operator declaration
  • TransUnion (US verification source) — SSN verification — Pulse SSN verification, Supported service coverage

    Full source read. Documented · Operator declaration · 2026-10-17. TransUnion provides the SSN check.

    “Kenshiki’s declared verification chain: ICAO for passports; AAMVA for state ID; TransUnion for SSN; Aduna for phone checks. Face matching and state-ID processing use Kenshiki’s own code. AAMVA remains the state-ID record check.”
    Kenshiki Labs, Pulse verification chain · operator declaration
  • Aduna — Phone verification — Pulse phone verification, Supported service coverage

    Full source read. Documented · Operator declaration · 2026-10-17. Aduna provides the phone check.

    “Kenshiki’s declared verification chain: ICAO for passports; AAMVA for state ID; TransUnion for SSN; Aduna for phone checks. Face matching and state-ID processing use Kenshiki’s own code. AAMVA remains the state-ID record check.”
    Kenshiki Labs, Pulse verification chain · operator declaration

Ericsson

  • Aduna — 50% equity ownership

    Full source read. Documented · Ownership source · 2025-07-29. Ericsson owns 50% of Aduna; twelve telecom operators jointly own the remaining 50%. Corporate ownership is separate from Pulse’s phone-check relationship.

    “Ericsson holds 50 percent of the venture equity”
    Ericsson, Ericsson announces completion of Aduna transaction

Follow the chain

Notes on this comparison

The product examples above link to primary vendor material. The map separately identifies registry entries, reported partnerships, and ownership sources. These sources describe particular products and relationships; they do not establish that a vendor lacks other capabilities.

Product descriptions change. Send a correction if a cited description is out of date.

By Kenshiki Labs.