The Background Check Result Object (BCRO) is a generic container used to capture AML results.
It contains the following fields:
This is the single identifier use to group results across all check types for a single check pass.
Indicator of what sort of results are in this BCRO. Will be one of:
RFC3399 formatted date-timestamp that the check was first verified.
RFC3399 formatted date-timestamp when this record was last checked/verified at the source.
Current state, based on the most recent check.
CLEAR: The no checks have ever turned up results
PAST_HITS: Past checks have returned hits, but now they're clear. Only really relevant if we have a history of these checks.
POSSIBLE_HIT: The most recent checks turned up some results that may be relevant (confidence <80)
ACTIVE_HITS: The current checks are returning definitive hits (confidence >= 80)
How often these checks run. By default, you’ll probably only run these once, then move on.
However, if the entity_flag “ongoing_pep” is set, then you’ll need to add this user to the ongoing check register (service provider dependent).
Return the result to whatever list the connector is configured for.
Service provider that performed the check.
Where available, the source name of the data. This might be something like “pep-class-1” or “dfat_consolidated_list” or other list source.
Usually, the service provider will give us a receipt, transaction id, check number, or some such that gives us a unique id on their side that we can reconcile with. This value will be returned unless there is an error.
Loosely typed Key-Value-Pairs (KVP) to store notes and details around the result.
See Key Value Pairs documentation for more information.
This is where the bulk of the result data will be found. We'll describe these in more detail in the AML Result Set Elements page.
kvpType should generally be set to “general.string”
Updated 8 months ago