Google Search Due Diligence Provider

Latest

🎯 Functional documentation

The Google Search due diligence provider allows screening Google for the occurrence of the party. A due diligence pdf is generated to check on which articles returned based on the party information provided.

:::info No configuration changes No mandatory configuration changes have been made in this version, no migration of the existing V5 configuration is needed. :::

What's new in this version

This version improves the generated due diligence PDF by applying yellow background highlighting to key terms, making it easier to spot relevant matches when reviewing the report.

Highlighting behavior

The following terms are always highlighted (no configuration needed):

• The individual's first name and last name (for individual checks)
• The company name (for company checks)

These standard terms are highlighted both in the Key Data section and across the match result fields.

Additional highlight keywords (keywords_to_highlight)

You can optionally configure extra terms to highlight via the keywords_to_highlight setting (comma-separated). For example, setting "fraud,corruption" will additionally highlight every occurrence of "fraud" and "corruption" in the PDF.

tip

keywords_to_highlight is independent from the keywords setting. The keywords setting controls which search terms are sent to the Google API for filtering results. The keywords_to_highlight setting controls which terms are visually highlighted in the generated PDF.

Input data points

• Individual
  • First name
  • Last name
• Company
  • Name
  • Country of address

DD parameters

This provider supports results for the following parameters:

• Individual & Company
  • GOOGLE_HIT

The provider returns a HIT if the response from the provider is not empty.

⚙️ Configuration

• Implementation class: GoogleSearchV6DueDiligenceProvider
• Resource URI: https://negnews.uat.myharmoney.eu

Settings

• authentication (required): Authentication details for accessing the APPC Google API. This should include:
  • clientId (required)
  • clientSecret (required)
  • tokenUri (required): https://negnews.uat.myharmoney.eu/token
• DUE_DILIGENCE_DOCUMENT_FETCH (optional, boolean): If true, fetches and stores a due diligence document (default: false).
• keywords (optional): Specifies keywords (e.g., fraud, corruption, terrorist) for custom search filtering. Matched keywords are highlighted in yellow in the generated PDF.
• client (optional): Specifies the client used to determine which default keyword list should be applied if no custom keywords are provided.
• num_results (optional): To limit the number of search results. Allowed values: 10 or 20 (default: 10).
• max_results_pdf (optional): To limit the number of search results included in the PDF.
• keywords_to_highlight (optional): Comma-separated keywords to highlight in the generated PDF (in addition to the standard first name, last name, and company name which are always highlighted). Example: "fraud,corruption".

Settings Configuration

Examples

Version 5

🎯 Functional documentation

The APPC Google due diligence provider allows screening Google for the occurrence of the party. A due diligence pdf is generated to check on which articles returned based on the party information provided. This version is created due to technical changes in v15.

Input data points

• Individual
  • First name
  • Last name
• Company
  • Name
  • Country of address

DD parameters

This provider supports results for the following parameters:

• Individual & Company
  • GOOGLE_HIT

The provider returns a HIT if the response from the provider is not empty.

⚙️ Configuration

• Implementation class: AppcGoogleV5DueDiligenceProvider
• Resource URI: https://negnews.uat.myharmoney.eu

Settings

• authentication (required): Authentication details for accessing the APPC Panama API. This should include:
  • clientId (required)
  • clientSecret (required)
  • tokenUri (required): https://negnews.uat.myharmoney.eu/token
• DUE_DILIGENCE_DOCUMENT_FETCH (optional, boolean): If true, fetches and stores a due diligence document (default: false).
• keywords (optional): Specifies keywords (e.g., fraud, corruption, terrorist) for custom search filtering.
• client (optional): Specifies the client used to determine which default keyword list should be applied if no custom keywords are provided.
• num_results (optional): To limit the number of search results.Allowed values: 10 or 20.(default: 10).
• max_results_pdf (optional): To limit the number of search results included in the PDF.

Example

{
    "authentication": {
        "tokenUri": "$vault{CLIENT_DUEDILIGENCE_APPC_GOOGLE_tokenUri}",
        "clientId": "$vault{CLIENT_DUEDILIGENCE_APPC_GOOGLE_clientId}",
        "clientSecret": "$vault{CLIENT_DUEDILIGENCE_APPC_GOOGLE_clientSecret}"
    },
    "DUE_DILIGENCE_DOCUMENT_FETCH": true,
    "PROVIDER_DISPLAY_NAME": "Negative news agent",
    "keywords": "fraud",
    "client": "client_2",
    "max_results_pdf": 3,
    "num_results": 10
}

Version 3

🎯 Functional documentation

The APPC Google due diligence provider allows screening Google for the occurrence of the party. A due diligence pdf is generated to check on which articles returned based on the party information provided. This version provides a small summary of the Google page in the pdf, if available.

Input data points

• Individual
  • First name
  • Last name
• Company
  • Name
  • Country of address

DD parameters

The provider returns a HIT if the response from the provider is not empty.

This provider supports results for the following parameters:

• Individual
  • GOOGLE_HIT
• Company
  • GOOGLE_HIT

⚙️ Configuration

• Implementation class: AppcGoogleV3DueDiligenceProvider
• Resource URI: https://negnews.uat.myharmoney.eu

Settings

• authentication (required): Authentication details for accessing the APPC Panama API. This should include:
  • clientId (required)
  • clientSecret (required)
  • tokenUri (required): https://negnews.uat.myharmoney.eu/token
• DUE_DILIGENCE_DOCUMENT_FETCH (optional, boolean): If true, fetches and stores a due diligence document (default: false).
• customSearch (optional, boolean): If true, uses the search keyword as client_name in the search request (default: false).
• keywords (optional): Specifies keywords (e.g., fraud, corruption, terrorist) for custom search filtering.
• numResults (optional): Limits the number of search results (default: 10).

Example

{
  "authentication": {
    "tokenUri": "$vault{CLIENT_DUEDILIGENCE_APPC_GOOGLE_tokenUri}",
    "clientId": "$vault{CLIENT_DUEDILIGENCE_APPC_GOOGLE_clientId}",
    "clientSecret": "$vault{CLIENT_DUEDILIGENCE_APPC_GOOGLE_clientSecret}"
  },
  "DUE_DILIGENCE_DOCUMENT_FETCH": true,
  "PROVIDER_DISPLAY_NAME": "Negative news agent",
  "custom_search": true,
  "keywords": "fraud",
  "num_results": 10
}

Version 2

🎯 Functional documentation

The APPC Google due diligence provider allows screening Google for the occurrence of the party. A due diligence pdf is generated to check on which articles returned based on the party information provided.

Input data points

• Individual
  • First name
  • Last name
• Company
  • Name
  • Country of address

DD parameters

The provider returns a HIT if the response from the provider is not empty.

This provider supports results for the following parameters:

• Individual
  • GOOGLE_HIT
• Company
  • GOOGLE_HIT

⚙️ Configuration

• Implementation class: AppcGoogleV2DueDiligenceProvider
• Resource URI: https://negnews.uat.myharmoney.eu

Settings

• authentication (required):
  • clientId (required)
  • clientSecret (required)
  • tokenUri (required): https://negnews.uat.myharmoney.eu/token
• DUE_DILIGENCE_DOCUMENT_FETCH (optional, boolean): If true, fetches and stores a due diligence document (default: false).

Example

{
  "authentication": {
    "tokenUri": "$vault{CLIENT_DUEDILIGENCE_APPC_GOOGLE_tokenUri}",
    "clientId": "$vault{CLIENT_DUEDILIGENCE_APPC_GOOGLE_clientId}",
    "clientSecret": "$vault{CLIENT_DUEDILIGENCE_APPC_GOOGLE_clientSecret}"
  },
  "PROVIDER_DISPLAY_NAME": "Negative news agent"
}