All categories ​ > ​ ​Configuration ​ > ​ ​Checks and data providers ​ > ​   Configuring RDC

Configuring RDC

Updated 4 months ago by Ainsley

Regulatory DataCorp (RDC) is a data provider you can use to run these checks:

  • PEPs and sanctions screening (individuals)
  • Sanctions and adverse media screening (companies)

PEPs and sanctions screening (individuals)

How it works

This is the default behaviour for a variant of the PEPs and sanctions screening check with RDC as the data provider.

The check is performed by screening an individual’s name and, when available, date of birth and address through RDC’s sources to provide a list of the individual’s potential matches to sanctions, politically exposed persons (PEPs), and (if you have access to RDC's adverse media results) instances of adverse media.

Instances of adverse media are only displayed when this check is used on the Assess PEPs, sanctions, and adverse media task.

If no potential matches are found for the individual (and the individual doesn't have potential matches returned from earlier screening checks), the check is marked Completed.

If any potential matches are found, the check returns Unresolved events and the matches are displayed in the check results. By default, all matches are displayed in the Potential matches list.

For every match that’s discovered, a detailed portfolio is displayed. This portfolio provides all available information from RDC about the match’s biography, associates, political exposure, events, sources, and (if available) adverse media.

This check variant is supported for all countries.

Any false positives filtered out by RDC aren’t displayed at all in PassFort. Contact RDC for more information about how they determine false positives and where you can see them.
A maximum of 200 potential matches can be processed. If there are more than 200 potential matches, they will not be displayed in PassFort. Please refine your search or view the matches through your data provider's portal.
To reduce false positives, provide the individual’s date of birth where possible.

Configuration options

You have the following configuration options:

  • Ignore historical matches (optional): When this option is selected, PassFort removes any matches that RDC previously listed as politically exposed or sanctioned but are not on any current lists.
  • Enable ongoing monitoring (optional): When this option is selected, any time a new match is discovered by RDC, the check’s task is marked incomplete, and, if the profile’s application is approved, it’s put into review. When this option is deselected, new matches are only returned from RDC when a user runs the check manually or, if your policy specifies, when a new task version is added to the application. Learn more about monitored applications.
When ongoing monitoring is enabled, any new matches are updated and displayed in PassFort as soon as RDC sends them.
  • Name settings for PassFort false positives reduction (required): This is one of three options contributing to PassFort’s false positive reduction service. It determines how PassFort treats results returned by RDC when a result’s name does not match the name on the profile. The value for the option must be one of the following: Allow any matches, Allow close or exact matches, or Allow exact matches.
  • Date of birth settings for PassFort false positives reduction (required): This is one of three options contributing to PassFort’s false positive reduction service. It determines how PassFort treats results returned by RDC when a result’s date of birth does not match the profile’s date of birth. The value for the option must be one of the following: Allow any matches, Allow close or exact matches, or Allow exact matches.
If the profile doesn’t have a date of birth (e.g. the field was left blank), date of birth is not used as a factor in identifying false positives.
  • Send Nationality as Country of Address when no address is available (optional): When the individual does not have an address, the country of nationality is sent as the country of address.
RDC does not return nationality, so the Country settings for false positive reduction configuration option cannot be used for the false positive reduction service.
To turn off PassFort’s false positive reduction service, set the Name settings for false positive reduction, Date of birth settings for false positive reduction, and Country settings for false positive reduction options to Allow any matches.

What we’ll need

Let us know that you’d like to add a variant of the PEPs and sanctions screening check with RDC and which configuration options you’d like to use. We’ll set it up for you.

We’ll also need:

  • Your RDC username and password: These are the same credentials you use to log into the RDC portal. We recommend you create an account specifically for PassFort and send us those credentials. If you choose to do this, please send us the credentials before you log in to the RDC portal for the first time because when you log in, you’ll be asked to reset your password.
  • Your webhook username and password: You choose what these will be. There are no restrictions on the length or characters in your username and password. For example, you might choose rdc@[yourdomain].com for your username.
  • Global location: The location of your RDC account servers. Can be United Kingdom or United States.

For help getting any of the information above, please speak to your RDC account manager.

To enable ongoing monitoring: Please also contact RDC Support and request that your account sends portfolio results and your username and password to this PassFort webhook URL: https://api.passfort.com/callback/rdc

Ongoing monitoring will not work otherwise.

If you’re using RDC for the PEPs and sanctions screening check (individuals) and the Sanctions and adverse media screening check (companies), the same webhook username and password are used for both checks. You only need to send one request to RDC Support to send portfolio results to the URL above.

Testing your configuration

Once the check variant is configured, follow these steps in your demo environment to test whether it's working as expected.

  1. Does the check complete when no matches are returned from RDC? To run the test, create an individual profile (with no other potential matches returned from previous screening checks) and run the check variant. If the check is marked Completed and no new matches are displayed in the check results, it’s working as expected.
  2. Does the check display PEPs matches returned from RDC? To run the test, create an individual profile with "PEP" as part of the profile’s first name or surname (e.g. "Alex PEP Wheeler"), and run the check variant. If the check status is Unresolved events and there are PEPs matches for David Cameron displayed in the check results, it’s working as expected.
  3. Does the check display sanctions matches returned from RDC? To run the test, create an individual profile with "sanction" as part of the profile’s first name or surname (e.g. "Alex sanction Wheeler"), and run the check variant. If the check status is Unresolved events and there are sanctions matches for Bahsar Al-Assad displayed in the check results, it’s working as expected.
  4. Does the check display adverse media matches returned from RDC? To run the test, create an individual profile with "media" as part of the profile's first name or surname (e.g. "Alex media Wheeler"), and run the check variant on the Assess PEPs, sanctions, and adverse media task. If the check status is Unresolved events and there are adverse media matches for David Cameron displayed in the check results, it's working as expected.
  5. What happens when new results are returned during ongoing monitoring? To run this test using your API, follow the steps in Test ongoing monitoring.

Required and optional profile fields

These are the profile details searched in RDC’s sources:

Name

Description

First name(s) (personal_details.name.given_names)

Required

The individual’s first and, if applicable, middle names.

Surname (personal_details.name.family_name)

Required

The individual’s last name.

Date of birth (personal_details.dob)

Optional

The individual’s date of birth.

Addresses (address_history.address)

Optional

The most recent address in the individual’s address history.

Sanctions and adverse media screening (companies)

How it works

This is the default behaviour for a variant of the Sanctions and adverse media screening check with RDC as the data provider.

The check is performed by screening a company’s name and country of incorporation through RDC’s sources to provide a list of the company’s potential sanctions matches and (if you have access to RDC’s PEPs results and adverse media results) PEPs matches and adverse media matches.

Instances of adverse media are only displayed when this check is used on the Assess sanctions and adverse media task.
Individuals who are company associates (e.g. shareholders and officers) are not screened as part of this check. To screen individuals automatically, create an associate smart policy for the task with a screening check for individuals. Learn how company associates are approved/rejected using associate smart policies.

If no potential matches are found for the company (and the company doesn't have potential matches returned from earlier screening checks), the check is marked Completed.

If any potential matches are found, the check returns Unresolved events and the matches are displayed in the check results. By default, all matches are displayed in the Potential matches list.

For every match that’s discovered, a detailed portfolio is displayed. This portfolio provides all available information from RDC about the match’s biography, associates, political exposure, events, sources, and (if available) adverse media.

This check variant is supported for all countries.

Any false positives filtered out by RDC aren’t displayed at all in PassFort. Contact RDC for more information about how they determine false positives and where you can see them.
A maximum of 200 potential matches can be processed. If there are more than 200 potential matches, they will not be displayed in PassFort. Please refine your search or view the matches through your data provider's portal.

Configuration options

You have the following configuration options:

  • Ignore historical matches (optional): When this option is selected, PassFort removes any matches that RDC previously listed as politically exposed or sanctioned but are not on any current lists.
  • Enable ongoing monitoring (optional): When this option is selected, any time a new match is discovered by RDC, the check’s task is marked incomplete, and, if the profile’s application is approved, it’s put into review. When this option is deselected, new matches are only returned from RDC when a user runs the check manually or, if your policy specifies, when a new task version is added to the application. Learn more about monitored applications.
When ongoing monitoring is enabled, any new matches are updated and displayed in PassFort as soon as RDC sends them.
  • Include adverse media matches (optional): When this option is selected, PassFort displays instances of adverse media returned from RDC.
This option should only be selected if you have adverse media configured on your RDC account. If you select this option and adverse media is not configured on your RDC account, this check cannot run successfully and error messages are displayed.
  • Name settings for PassFort false positive reduction (required): This is one of three options contributing to PassFort’s false positive reduction service. It determines how PassFort treats results returned by RDC when a result’s name does not match the name of the profile. The value for the option must be one of the following: Allow any matches, Allow close or exact matches, or Allow exact matches.
  • Date of birth settings for PassFort false positive reduction (required): This is one of three options contributing to PassFort’s false positive reduction service. It determines how PassFort treats results returned by RDC when a result’s date of incorporation does not match the profile’s date of incorporation. The value for the option must be one of the following: Allow any matches, Allow close or exact matches, or Allow exact matches.
If the profile doesn’t have a date of incorporation (e.g. the field was left blank), date of incorporation is not used as a factor in identifying false positives.
  • Country settings for PassFort false positive reduction (required): This is one of three options contributing to PassFort’s false positive reduction service. It determines how PassFort treats results returned by RDC when a result’s country of incorporation does not match the profile’s country of incorporation. The value for the option must be one of the following: Allow any matches, Allow close or exact matches, or Allow exact matches.
To turn off PassFort’s false positive reduction service, set the Name settings for false positive reduction, Date of birth settings for false positive reduction, and Country settings for false positive reduction options to Allow any matches.

What we’ll need

Let us know that you’d like to add a variant of the Sanctions and adverse media screening check with RDC and which configuration options you’d like to use. We’ll set it up for you.

We’ll also need:

  • Your RDC username and password: These are the same credentials you use to log into the RDC portal. We recommend you create an account specifically for PassFort and send us those credentials. If you choose to do this, please send us the credentials before you log in to the RDC portal for the first time because when you log in, you’ll be asked to reset your password.
  • Your webhook username and password: You choose what these will be. There are no restrictions on the length or characters in your username and password. For example, you might choose rdc@[yourdomain].com for your username.
  • Global location: The location of your RDC account servers. Can be United Kingdom or United States.

For help getting any of the information above, please speak to your RDC account manager.

If you’re using ongoing monitoring, please also contact RDC Support and request that your account sends portfolio results and your username and password to this PassFort webhook URL: https://api.passfort.com/callback/rdc

Ongoing monitoring will not work otherwise.

If you’re using RDC for the PEPs and sanctions screening check (individuals) and the Sanctions and adverse media screening check (companies), the same webhook username and password are used for both checks. You only need to send one request to RDC Support to send portfolio results to the URL above.

Testing your configuration

Once the check variant is configured, follow these steps in your demo environment to test whether it's working as expected.

  1. Does the check complete when no matches are returned from RDC? To run the test, create a company profile (with no other potential matches returned from previous screening checks) and run the check variant. If the check is marked Completed and no new matches are displayed in the check results, it’s working as expected.
  2. Does the check display PEPs and sanctions matches returned from RDC? To run the test, create a company profile with "sanctions" as part of the profile’s name and run the check variant. If the check status is Unresolved events and there are PEPs and sanctions matches for Rosneft displayed in the check results, it’s working as expected.
  3. Does the check display adverse media matches returned from RDC? To run the test, create a company profile with "media" as part of the profile's name and run the check variant on the Assess sanctions and adverse media task. If the check status is Unresolved events and there are adverse media matches for Roseneft displayed in the check results, it's working as expected.
  4. What happens when new results are returned during ongoing monitoring? To run this test using your API, follow the steps in Test ongoing monitoring.

Required and optional profile fields

These are the profile details searched in RDC’s sources:

Name

Description

Company name (metadata.name)

Required

The company’s name.

Country of incorporation (metadata.country_of_incorporation)

Required

The country in which the company is incorporated.

Addresses (metadata.addresses.address)

Optional

The company's address. If the company has multiple address types, the first one in the order below is sent:

  • Head office
  • Registered
  • Trading
  • Unspecified

How did we do?

Powered by HelpDocs (opens in a new tab)