Skip to main content
The Data Verification module verifies a subject’s identity by cross-referencing submitted personal information, such as name, date of birth, address, and national ID numbers against trusted consumer, government, and credit bureau databases. It counts how many independent data sources confirm different combinations of identity elements, allowing organisations to assess the strength and confidence of an identity match. This module is commonly used for KYC (Know Your Customer), AML (Anti-Money Laundering), and general identity verification across multiple countries. This page contains documentation for the Data Verification - Single Match (All Sources) module, including its variants, capabilities, and the specific result codes it returns.
This variant performs a single-source identity verification check for Argentinian subjects. It cross-references the subject’s name, date of birth, and DNI (Documento Nacional de Identidad) number against trusted Argentinian data sources.

Capabilities

The module returns source-count capabilities that indicate how many independent data sources confirmed each combination of identity elements, plus an age flag and an overall GBG score. This capability structure is shared across most Data Verification variants. Differences between variants are in input requirements and default outcome logic.

Number of matching sources

The total number of independent data sources that returned any type of match for the subject’s submitted information.A value of 0 means no data sources matched any combination of the subject’s identity elements. Higher values indicate stronger verification confidence because the identity was confirmed independently across multiple sources.

Name + Address matches

The number of data sources where the subject’s name and address both matched.

Name + DOB matches

The number of data sources where the subject’s name and date of birth both matched.

Name + DOB + Address matches

The number of data sources where the subject’s name, date of birth, and address all matched. This is the strongest match combination without an ID number and is typically used as the threshold for a full “Match” outcome.

ID + Name + Address matches

The number of data sources where the subject’s national ID number, name, and address all matched.

ID + Name + DOB matches

The number of data sources where the subject’s national ID number, name, and date of birth all matched.

ID + Name + DOB + Address matches

The number of data sources where the subject’s national ID number, name, date of birth, and address all matched. This is the highest-confidence match combination available.

Is under 18

Indicates whether the subject is under 18 years of age based on the submitted or verified date of birth.

GBG score

An overall identity verification score calculated by GBG based on the strength and breadth of matches across data sources.Higher scores indicate stronger identity verification confidence. A score of 0 indicates that no meaningful verification data was returned. This score can be used in custom evaluation rules for more granular decisioning beyond the default outcomes.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response showing a successful identity match.
In this example:
  • One source matched the full ID + Name + Address + DOB combination (idNameAddressDob: 1), which is the strongest match available.
  • The GBG score is 500, indicating moderate verification confidence.
  • The subject is 18 or older (isUnder18: false).
  • The outcome resolves to Match.
This variant verifies Australian subjects against trusted credit data sources. It uses the supplier decision capability with support for partial matches.

Capabilities

The table below lists the capabilities returned by this variant.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response for a successful identity match.
JSON
This variant verifies Australian subjects against trusted directors register data sources.

Capabilities

The table below lists the capabilities returned by this variant.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response for a successful identity match.
JSON
This variant verifies Australian subjects against historical electoral roll data (pre-2004). It has the most complex partial match logic of any variant, with seven distinct conditions that qualify as a partial match.

Capabilities

The table below lists the capabilities returned by this variant.

Default outcomes

The table below lists the default outcomes for this variant.The Partial Identity Match outcome is triggered by any of the following six conditions. Any condition listed as any accepts every possible match result for that field.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
Replace your-journey-resourceID@latest with your journey’s resource ID. You can find this in the Journey Builder after publishing your journey.
JSON

Sample response

The following is a sample response for a successful identity match.
JSON

Input payload

The following is a sample payload used to submit data to the Australia - Historical Electoral Roll module for processing.
JSON
This variant verifies Australian subjects against trusted population data sources.

Capabilities

The table below lists the capabilities returned by this variant.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
Replace your-journey-resourceID@latest with your journey’s resource ID. You can find this in the Journey Builder after publishing your journey.
JSON

Sample response

The following is a sample response for a successful identity match.
JSON

Input payload

The following is a sample payload used to submit data to the Australia - Population module for processing.
JSON
This variant orchestrates identity verification across multiple Australian government ID sources.

Capabilities

The table below lists the capabilities returned by this variant.

DVS sources

Government ID sources that have not yet been checked. Informational only. Not used in default outcome logic.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response showing verification still in progress.
JSON
This variant verifies Australian subjects against standard sources for AML-regulated customers. It adds a credit bureau check capability alongside the overall verification status.

Capabilities

The table below lists the capabilities returned by this variant.

illion credit bureau check

illion Credit Bureau Check

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response for a successful identity verification.
JSON
This variant verifies Australian subjects against standard sources for non-AML customers. It provides only the overall verification status capability without a credit bureau check.The capabilities include only the overall verification result (VERIFIED, IN_PROGRESS). Default outcomes are: Pass (verified) / Refer (in progress) / Error (default).

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response for a successful identity verification.
JSON
This variant extends the AML standard sources variant with additional data sources.The capabilities and default outcomes are the same as Australia: Single match standard sources (AML).

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response showing verification still in progress.
JSON

Experian credit bureau check

Experian Credit Bureau Check
This variant provides the same standard-plus-additional-sources verification for non-AML customers. It does not include a credit bureau check capability.The capabilities include only the overall verification result (VERIFIED, IN_PROGRESS). Default outcomes are the same: Pass / Refer / Error.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response for a successful identity verification.
JSON
This variant verifies Australian subjects against trusted tenancy data sources.

Capabilities

The table below lists the capabilities returned by this variant.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
Replace your-journey-resourceID@latest with your journey’s resource ID. You can find this in the Journey Builder after publishing your journey.
JSON

Sample response

The following is a sample response for a successful identity match.
JSON

Input payload

The following is a sample payload used to submit data to the Australia - Tenancy module for processing.
JSON
This variant performs a single-source identity verification check for Brazilian subjects with a required CPF (Cadastro de Pessoas Físicas) number, the Brazilian individual taxpayer registration number issued by the Federal Revenue Service.The capabilities are the same as Argentina: Single match.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response showing a successful identity match.
JSON
This variant performs a single-source check without requiring a CPF number. It is suited for situations where a CPF is not available or required.The capabilities are the same as Argentina: Single match.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response showing a successful identity match.
JSON
This variant performs a standard identity verification check for Canadian subjects without FINTRAC-specific compliance requirements. It uses the simpler source-count capability structure rather than the field-level match flags used by the Fintrac Single Bureau variants. It does not include the under-18 flag.The capabilities are the same as Argentina: Single match, excluding the Is under 18 flag.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response for a successful identity match.
JSON
For a full explanation of match flag values, see match flags in the glossary.
This variant performs a single-source identity verification check for Chilean subjects using their identity card number (Cédula de Identidad / RUN).The capabilities are the same as Argentina: Single match.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response for a successful identity match.
JSON
This variant performs a single-source identity verification check for Colombian subjects using their identity card number (Cédula de Ciudadanía).The capabilities are the same as Argentina: Single match.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response for a partial identity match.
JSON
This variant performs a single-source identity verification check for Danish subjects.The capabilities are the same as Argentina: Single match.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit data to the Denmark: Single match module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source identity verification check for French subjects. Notably, a landline phone number is a required input. This is unique among Data Verification variants and reflects the data sources available for French identity verification.The capabilities are the same as Argentina: Single match.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit data to the France: Single match module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies German subjects against Schufa, Germany’s leading credit bureau that holds credit and identity data on the majority of German adults. Unlike the other German variants, this one uses field-level match flags rather than source counts, providing granular detail on which identity elements matched.

Capabilities

The capabilities returned by this variant are grouped into name, address, and other match flags.

Name match flags

Match results for the subject’s first and last names against the Schufa record.

Address match flags

Match results for the subject’s address, both overall and at the component level.

Other match flags

Date of birth and the Schufa QBit (quality indicator) flag.

Default outcomes

The table below lists the default outcomes for this variant.For a full explanation of match flag values, see match flags in the glossary.

Input payload

The following is a sample payload used to submit data to the Germany: Schufa module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source identity verification check for German subjects using non-Schufa data sources (consumer and public record databases).The capabilities are the same as Argentina: Single match.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit data to the Germany: Single match without Schufa module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies Italian subjects against trusted citizen data sources. It shares the same capability structure and default outcome logic as Spain: Citizen Source.

Generic email match result

Indicates if the email has matched

Generic phone match result

Indicates if the phone number has matched

Input payload

The following is a sample payload used to submit data to the Italy - Citizen source module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source check for Italian subjects without requiring a Codice Fiscale.The capabilities are the same as Argentina: Single match.

Input payload

The following is a sample payload used to submit data to the Italy: Single match - no Codice Fiscale module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source identity verification check for Italian subjects using their Codice Fiscale (Italian tax identification code). The Codice Fiscale is a unique alphanumeric code assigned to every Italian citizen and resident, derived from their name, date of birth, gender, and birthplace.The capabilities are the same as Argentina: Single match.

Input payload

The following is a sample payload used to submit data to the Italy: Single match - with Codice Fiscale module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source identity verification check for Mexican subjects using their CURP (Clave Única de Registro de Población) via the tax identification number and identity card inputs.The capabilities are the same as Argentina: Single match.

Input payload

The following is a sample payload used to submit data to the Mexico: Single match module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies Dutch subjects against trusted citizen data sources. It shares the same capability structure and default outcome logic as Spain: Citizen Source.

Input payload

The following is a sample payload used to submit data to the Netherlands - Citizen Source module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source identity verification check for Dutch subjects against consumer data sources. It extends the standard source-count capabilities with phone and email match indicators.

Capabilities

This variant returns all the same source-count capabilities as Argentina: Single match, plus two additional boolean capabilities:

Phone match

Indicates whether one or more of the subject’s submitted phone numbers matched a phone number on file in the data source.

Email match

Indicates whether one or more of the subject’s submitted email addresses matched an email address on file in the data source.

Default outcomes

The table below lists the default outcomes for this variant.
This variant performs a single-source identity verification check for Dutch subjects against identity-specific data sources. It extends the standard capabilities with a phone match indicator (but not email match, unlike the consumer variant).The capabilities are the same as Argentina: Single match, plus the Phone match capability documented under the Netherlands consumer variant. The default outcomes are the same as Netherlands: Single match consumer.
This variant verifies New Zealand subjects against trusted birth certificate data sources with mandatory GovID inclusion. It returns only the supplier decision, with no individual field match flags. Capabilities and default outcomes are the same as New Zealand: Citizenship Certificate (mandatory GovID).

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response for a successful identity match.
JSON
For a full explanation of match flag values, see match flags in the glossary.
This variant verifies New Zealand subjects against trusted birth certificate data sources. This variant does not include GovID in the matching process.

Capabilities

The table below lists the capabilities returned by this variant.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit data to the New Zealand - Birth Certificate - without GovID module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies New Zealand subjects against trusted citizenship certificate data sources with mandatory GovID inclusion in the matching process. It is the most streamlined NZ variant. It returns only the supplier decision, with no individual field match flags.

Capabilities

The table below lists the capabilities returned by this variant.

Default outcomes

The table below lists the default outcomes for this variant.For a full explanation of match flag values, see match flags in the glossary.

Input payload

The following is a sample payload used to submit data to the New Zealand - Citizenship Certificate - mandatory GovID module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies New Zealand subjects against trusted citizenship certificate data sources. This variant does not include GovID in the matching process.Capabilities and default outcomes are the same as New Zealand: Birth Certificate (without GovID).

Input payload

The following is a sample payload used to submit data to the New Zealand - Citizenship Certificate - without GovID module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies New Zealand subjects against credit header data. Unlike Credit Header 2 (which uses a supplier decision with partial match support), Credit Header 1 uses individual field-level match flags and constructs the outcome logic from those flags directly. It matches on full name (as a single field), date of birth, and address.

Capabilities

The table below lists the capabilities returned by this variant.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit data to the New Zealand - Credit Header 1 module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies New Zealand subjects against trusted credit data sources. Unlike most other NZ variants, this one supports a Partial Identity Match outcome when the supplier returns a partial match.

Capabilities

The table below lists the capabilities returned by this variant.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit data to the New Zealand - Credit Header 2 module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies New Zealand subjects against a third NZ credit reporting agency. It provides the most granular capability set of any NZ credit header variant, with individual name component match flags, address component match flags, and a deceased flag.

Capabilities

The capabilities returned by this variant are grouped into name, address, and other match flags.

Name match flags

Match results for the subject’s first, middle, and last names.

Address match flags

Match results for the subject’s address, both overall and at the component level.

Other match flags

Date of birth, deceased flag, and address quality.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit data to the New Zealand - Credit Header 3 module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies New Zealand subjects against trusted directors and shareholders data sources. It matches name and address at the individual component level (premise, thoroughfare, locality, postal code), providing more granular address verification than other NZ variants.

Capabilities

The capabilities returned by this variant are grouped into name and address component match flags.

Name match flags

Match results for the subject’s first, middle, and last names.

Address component match flags

Granular match results for individual address components.

Default outcomes

The table below lists the default outcomes for this variant.For a full explanation of match flag values, see match flags in the glossary.

Input payload

The following is a sample payload used to submit data to the New Zealand - Directors and Shareholders module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies New Zealand subjects against trusted driver licence data sources in real time. It verifies the licence number, version number, name, and date of birth.

Capabilities

This variant returns the same name match flags as New Zealand: Land Titles, plus:

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON
The table below describes each field in the payload, including validation rules for driver licence document fields.

Sample response

The following is a sample response returned by the module.
JSON

Sample response

The following is a sample response for a successful identity match.
JSON
For a full explanation of match flag values, see match flags in the glossary.
This variant verifies New Zealand subjects against trusted land ownership data sources. It uses field-level match flags with a supplier decision capability that provides the data source’s overall match assessment.

Capabilities

The capabilities returned by this variant are grouped into name match flags, an address match flag, address quality, and supplier decision.

Name match flags

Match results for the subject’s first, middle, and last names against the Land Titles record.

Address match flag

Overall address match result.

Address quality

Indicator of how well the submitted address could be validated.

Supplier decision

Overall match decision returned by the data source. This is the primary capability used in the default outcome logic.

Default outcomes

The table below lists the default outcomes for this variant.For a full explanation of match flag values, see match flags in the glossary.

Input payload

The following is a sample payload used to submit data to the New Zealand - Land Titles module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies New Zealand subjects against trusted passport data sources. It verifies the passport number, expiry date, name, and date of birth.

Capabilities

This variant returns the same name and DOB match flags as New Zealand: Birth Certificate (without GovID), plus:

Data source result

The data source check result

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON
The table below describes each field in the payload, including validation rules for passport document fields.

Sample response

The following is a sample response returned by the module.
JSON

Sample response

The following is a sample response for a successful identity match.
JSON
For a full explanation of match flag values, see match flags in the glossary.
This variant orchestrates identity verification across multiple New Zealand government ID sources (driver licence, passport, citizenship certificate, and birth certificate). It manages the verification workflow across sources and reports an overall verification status.

Capabilities

The table below lists the capabilities returned by this variant.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit data to the New Zealand: Single match gov ID source module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies identity against any standard New Zealand source (not limited to government sources). It provides a simpler capability set with only the overall verification status without a sources-remaining tracker.

Capabilities

The table below lists the capabilities returned by this variant.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit data to the New Zealand: Single match standard sources module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies New Zealand subjects against trusted tenancy data sources. Unlike the Australian Tenancy variant (which uses a simple supplier decision), this variant provides individual field-level match flags with a partial match outcome.

Capabilities

The table below lists the capabilities returned by this variant.

Default outcomes

The table below lists the default outcomes for this variant.For a full explanation of match flag values, see match flags in the glossary.

Input payload

The following is a sample payload used to submit data to the New Zealand - Tenancy module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source identity verification check for Peruvian subjects. It extends the standard source-count capabilities with an ID + Name match counter (without requiring address or DOB alongside the ID) and a phone match indicator.

Capabilities

This variant returns all the same source-count capabilities as Argentina: Single match, plus:

ID + Name matches

The number of data sources where the subject’s national ID number and name matched, without requiring address or DOB.This is a lower-confidence match than ID + Name + Address or ID + Name + DOB, but it confirms that the ID number is associated with the submitted name.

Phone match

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit data to the Peru: Single match module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source check for Polish subjects.The capabilities are the same as Argentina: Single match.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit data to the Poland: Single match module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source check for Polish subjects against population register data sources. Capabilities and default outcomes are the same as Poland: Single match.

Input payload

The following is a sample payload used to submit data to the Poland: Single match Population module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source identity verification check for South African subjects using their identity card number (South African ID number), a 13-digit number that encodes the subject’s date of birth, gender, and citizenship status).The capabilities are the same as Argentina: Single match.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response showing a successful identity match.
In this example:
  • Two sources matched the full ID + Name + Address + DOB combination, shown by idNameAddressDob: 2, which is the strongest match available.
  • The GBG score is 745, indicating high verification confidence.
  • The subject is 18 or older, shown by isUnder18: false.
  • The outcome resolves to Match.
This variant verifies Spanish subjects against trusted citizen data sources. It provides the most granular field-level matching of any Spain variant, including individual address component matches, phone number matching, email matching, and a “Could Not Locate” outcome.

Capabilities

The capabilities returned by this variant are grouped into name, address, and other match flags.

Name match flags

Match results for the subject’s first name, last name, and initial.

Address match flags

Match results for the subject’s address, both overall and at the component level.

Other match flags

Date of birth, phone, email, and address quality.

Default outcomes

The table below lists the default outcomes for this variant.For a full explanation of match flag values, see match flags in the glossary.

Input payload

The following is a sample payload used to submit data to the Spain - Citizen Source module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source identity verification check for Spanish subjects.The capabilities are the same as Argentina: Single match.

Input payload

The following is a sample payload used to submit data to the Spain: Single match module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source identity verification check for Swedish subjects using their personnummer (personal identity number).The capabilities are the same as Argentina: Single match.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit data to the Sweden: Single Match Personal ID module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source check for Swedish subjects against population register data sources. Capabilities and default outcomes are the same as Sweden: Single match personal ID.

Input payload

The following is a sample payload used to submit data to the Sweden: Single Match Population module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies UK subjects against Electoral Register and credit database information held by a specific credit bureau partner. It uses a different capability structure from the standard source-count pattern, counting matches at two levels of granularity (specific element combinations and broader “any match” totals) rather than the ID-based combinations used by other countries.

Capabilities

This variant returns several count-based capabilities and an under-18 flag, described below.

Count of matches against name and address

The number of data sources where the subject’s name and address matched.

Count of matches against name and date of birth

The number of data sources where the subject’s name and date of birth matched.

Count of matches against name, address and date of birth

The number of data sources where all three elements (name, address, and date of birth) matched. This is the strongest match combination for this variant and is the threshold for the Identity Match outcome.

Total sources with more than one field match

The total number of data sources that matched on more than one field (any combination). This serves as the threshold for the Partial Identity Match outcome. It captures cases where some elements matched but not the full name + address + DOB combination.

Total sources where name and address match

An aggregate count of sources confirming the name and address combination.

Total sources where name and date of birth match

An aggregate count of sources confirming the name and date of birth combination.

Is under 18

Activity history

Bucketed age of the oldest known credit account (GPG45 Activity History)

Default outcomes

The table below lists the default outcomes for this variant.
Outcome thresholds are configurable. Your organisation may have different thresholds configured based on your verification requirements.

Configuration

You can configure how matches are counted for this variant in the module settings. These settings control which match types are included in the count totals.

Understanding specific counts vs. total counts

The capability counters operate at two levels:
  • Specific counts (e.g. nameAddressMatchCount) only increment when exactly the listed fields matched, with no additional fields.
  • Total counts (e.g. totalNameAndAddressMatchCount) increment when those fields matched, regardless of whether additional fields also matched.
For example, if 3 sources matched on name + address + DOB and 1 source matched on name + address only:

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response showing a successful identity match against multiple sources.
In this example:
  • 2 tradeline sources matched on name, address, and DOB (nameAddressDobMatchCount: 2)
  • 1 electoral roll source matched on name and address only (nameAddressMatchCount: 1)
  • 0 sources matched on name and DOB exclusively (nameDobMatchCount: 0)
  • 3 total sources had more than one field match (totalAnyMatchCount: 3)
  • The inner array provides per-source detail with individual match flags for each source
For a full explanation of match flag values, see match flags in the glossary.
This variant queries a different UK credit bureau partner. Capabilities, configuration, and default outcomes are the same as UK: Credit Bureau 1.

Input payload

The following is a sample payload used to submit data to the UK: Credit Bureau 2 module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant queries a third UK credit bureau partner. Capabilities, configuration, and default outcomes are the same as UK: Credit Bureau 1.
This variant verifies UK subjects against electoral roll data. It uses field-level match flags rather than source counts, providing granular detail on which individual identity elements matched.

Capabilities

The capabilities returned by this variant are grouped into name and other match flags.

Name match flags

Match results for the subject’s first, middle, and last names.

Other match flags

Address, date of birth, and under-18 flag.

Default outcomes

The table below lists the default outcomes for this variant.For a full explanation of match flag values, see match flags in the glossary.

Input payload

The following is a sample payload used to submit data to the UK: Edited and Historical Electoral Roll module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant verifies UK subjects against the National ID Register. It uses field-level match flags similar to the Electoral Roll variant, but adds phone number matching capabilities (landline and mobile).

Capabilities

The name, address, date of birth, and under 18 match flags are the same as UK: Edited and Historical Electoral Roll, with one difference: first name matches also accepts alias match as a qualifying value for the Identity Match outcome (not just match and partial match).This variant adds two phone match flags.

Phone match flags

Match results for the subject’s landline and mobile phone numbers.

Default outcomes

The table below lists the default outcomes for this variant.For a full explanation of match flag values, see match flags in the glossary.

Input payload

The following is a sample payload used to submit data to the UK: National ID Register module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source check across all available UK data sources.The capabilities are the same as Argentina: Single match.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit data to the UK: Single match all sources module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant is deprecated. Use UK: Single match all sources or the non-legacy UK: Credit Bureau 1 variant instead.
This legacy variant performs a single-source check against a specific credit bureau. It uses the standard source-count capabilities (without GBG score) rather than the CRA-specific match count structure used by the non-legacy Credit Bureau variants.The capabilities are the same as Argentina: Single match, excluding the GBG score. The default outcomes follow the standard pattern: ALERT → Match (Name + DOB + Address ≥ 1) → Partial Match → No Match → Error.

Input payload

The following is a sample payload used to submit data to the UK: Single match Credit Bureau 1 [Legacy] module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant is deprecated.
This legacy variant queries a second credit bureau. Capabilities and default outcomes are the same as UK: Single match Credit Bureau 1 (legacy).

Input payload

The following is a sample payload used to submit data to the UK: Single match Credit Bureau 2 [Legacy] module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant is deprecated.
This legacy variant queries a third credit bureau. Capabilities and default outcomes are the same as UK: Single match Credit Bureau 1 (legacy).

Input payload

The following is a sample payload used to submit data to the UK: Single match Credit Bureau 3 [Legacy] module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a single-source check against the aggregated super bureau.

Input payload

The following is a sample payload used to submit data to the UK: Single match super bureau module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant checks whether a UK subject is recorded as deceased against mortality data source.

Capabilities

Default outcomes

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response showing that the subject is not recorded as deceased.
In this example:
  • The mortality data source returned deceasedFlag: "N", indicating the subject is not recorded as deceased.
  • The inner array shows the data source consulted: population.
  • The outcome resolves to Not Deceased.
This variant verifies US subjects against credit bureau data. It uses field-level match flags (including SSN and phone matching) rather than the enumset-based risk code structure used by the US Source 2 variants.

Capabilities

The table below lists the capabilities returned by this variant.

Default outcomes

The table below lists the default outcomes for this variant.

Input payload

The following is a sample payload used to submit identity data to the Data Verification module for processing.
JSON

Sample response

The following is a sample response for a successful identity match.
JSON
For a full explanation of match flag values, see match flags in the glossary.
This variant performs a US identity verification check via a credit bureau. It uses a hybrid capability structure that combines individual field-level match flags with the full enumset-based risk code suite documented under US: Source 2 (Legacy). The bureau is selected through credential routing. Contact GBG for bureau selection guidance.

Capabilities

This variant returns field-level match flags grouped into name, address, and other categories, alongside the full enumset risk code suite.

Name match flags

Match results for the subject’s first and last names.

Address match flags

Match results for the subject’s address, both overall and at the component level.

Other match flags

Date of birth and Social Security Number.

Enumset risk code capabilities

This variant also returns all enumset risk code categories documented under US: Source 2 (Legacy): subject risk codes, address risk codes (including warm address alerts), DOB risk codes, SSN risk codes, acceptance result, match result, COPPA alert, alert list, Trust USA risk codes, and Trust USA result.

Last name matches

Last names match flag (single-source standard)

Year of birth matches

Year of birth match flag (single-source standard)

Month of birth matches

Month of birth match flag (single-source standard)

Day of birth matches

Day of birth match flag (single-source standard)

DOB capabilities

DOB matching alerts

SSN capabilities

SSN matching alerts, validation and issuance alerts

Acceptance capabilities

Summary Results or Score Card Results

Match capabilities

Individual Located or Not Located

Subject restricted

COPPA Alert

Alert list capabilities

Alerts.

Trust USA risk capabilities

Trust USA Risk Capabilities

Trust USA result capabilities

Trust USA Result Capabilities

Default outcomes

The outcome logic combines the match result and acceptance result capabilities. This is the same as US: Source 2 (Legacy). The individual field-match flags are not used in the default outcome logic. They are available for custom evaluation rules.

Input payload

The following is a sample payload used to submit data to the US: Credit Bureau 1 module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant queries a different credential-routed credit bureau. Capabilities and default outcomes are the same as US: Credit Bureau 1.

Input payload

The following is a sample payload used to submit data to the US: Credit Bureau 2 module for processing.
JSON

Sample response

The following is a sample response returned by the module.
JSON
This variant performs a comprehensive US identity verification check using name and address as required inputs, with optional DOB, SSN, phone, and email. It returns an extensive set of enumset-based risk code capabilities rather than simple match flags. This capability structure is unique to US variants and provides deep fraud and risk intelligence alongside identity matching.

Capabilities

All US Source 2 variants share the same capability set. The capabilities are enumset types. Each can contain zero or more result codes simultaneously.

Subject risk codes

Flags indicating issues with the subject record itself.

Name risk codes

Address risk codes

This is the largest capability category, covering match failures, deliverability issues, behavioural signals, and warm address alerts.

Match codes

Deliverability signals

Behaviour signals

Address type signals

Warm address alerts

These flag addresses associated with specific institutional locations. Each alert exists in two forms: one for the located address and one for the input address.

DOB risk codes

SSN risk codes

Codes for SSN matching, validation, and issuance anomalies. Includes both current and legacy code formats.

Acceptance result (score card)

Match result

COPPA alert

Alert list

Flags for subjects or elements that appear on configured alert lists.

Trust USA risk codes

An extensive set of element-pair risk codes that indicate which specific combinations of input (I-prefix) and located (L-prefix) identity elements were flagged. These codes use short identifiers (e.g. IADDR for input street address, LSSN9 for located SSN9). The full set includes combinations of name, address, SSN, phone, email, IP address, and document elements. Also includes overall pass, fail, and refer result codes.

Trust USA result

Default outcomes

The outcome logic combines the match result and acceptance result capabilities.For a full explanation of match flag values, see match flags in the glossary.
This variant requires both DOB and SSN, providing the strongest matching configuration. Capabilities and default outcomes are the same as US: Source 2.
This variant adds date of birth as a required input for stronger matching confidence. All other capabilities and default outcomes are the same as US: Source 2.
This variant adds SSN as a required input. All other capabilities and default outcomes are the same as US: Source 2.