Understanding CheckSummary Results

🚧

NOTE: This method is being phased out

The following section details how to interpret the results of a /verify check on an entity when you specify the checkType details in full (rather than just use the “profile” option).

Unless you have a specific reason to not do so, please move to using Entity Profiles, rather than running individual checks.

Whenever a check is performed upon an entity, a summary record is returned as part of the response data. This is found in the checkSummary object, and represents the sum total of information about this entity and all previous relevant checks.

(Note: If you’re just after the results of the latest check, look for the most recent summary record in the checkSummaries list.)

As part of the primary summary object, there is an array of typed Key-Value Pairs called CheckResults.

In there, we will return any specific flags or data that we think might be useful for the developer to take immediate action on, rather than having to dig through the individual results.

The KvpKey is generally made up of 2 parts: .

is designed to indicate the level of importance of the flag. Valid values are:

  • Info - Flag is purely informational
  • Issue - Flag is highlighting something that is a potential issue
  • Important - Flag is indicating something we feel is Important and requires potential intervention
  • Action - Flag indicates a recommended action
  • Fail.Reason - Why the entity is currently in a failed state
  • Review.Reason - Why the entity is currently marked as REFER

<Flag> is the name of the flag and is generally self explanatory (see notes below).

The KvpType is one of the enumerated KVP types found in our OpenAPI specification. We’ve translated that to a more readable form here.

KvpKey

KvpType

KvpValues

Notes

Recommended Disposition

Action.Recommended

String

One of:

PASS

PASS_MANUAL

REFER

FAIL

FAIL_MANUAL

UNCHECKED

Recommended action to take, based on risk, confidence, and all other data.

The _MANUAL suffix on pass/fail indicate that manual intervention was required to make the entity pass/fail.

UNCHECKED means that no checks have been attempted against this entity as yet.

Failure / Refer Reason Indicators

Fail.Reason.*

String

The * can include:

Risk

NoMatch

Duplicate

Blacklist

Partial

Sanction

PEP

The * in the KvpKey will give a single word indicator of the primary failure reason.

The KvpValue will give a short note on why.

Review.Reason.*

 

The * can include:

PEP

Media

Risk



The * in the KvpKey will give a single word indicator of the primary referral reason.

The KvpValue will give a short note on why.

Info.ManualChanges

Integer

1+

If there have been manual interventions on this account, indicate how many

portal.issue.summary

String

Comma separated list of issues

Issue codes are:

404: No match

500: Service error

PTL: Partial match only

PEP: PEP match

S: Sanctions match

WL: AML Watchlist match

M: Adverse Media match

DUP: Duplicate

BL: Blacklist

ATT: No IDV data 

ATT-IDV: ID Validation failed

ATT-PHT: Photo comparison failed

ATT-OCR: OCR scanned document was modified

PEP/Sanctions Related Notes

Issue.HasAdverseMedia

Boolean

True / false

Adverse media was picked up during the check. Only included if true

Issue.IsPEP

Boolean

True / false

Entity appears on at least one PEP list

Only included if true

Important.HasSanctions

Boolean

True / false

Entity appears on at least one sanctions list

Only included if true

Issue.OnWatchlist

Boolean

True / false

Entity appears on at least one watchlist

Only included if true

Confidence Score Related Notes

Important.VERY_LOW_CONFIDENCE

Boolean

True / false

The confidence score is considered to be very low

Only included if true

Issue.LOW_CONFIDENCE

Boolean

True / false

Confidence levels in the result are considered low

Only included if true

Matching Statistics

Info.MissingChecks

String

Comma separated list of checkTypes that have not yet completed.

This will indicate which of the checks you requested have not completed successfully.

Inclusion of “two_plus” or “one_plus” indicates that name/DoB/address checks have not passed.

“id” indicates that no ID checks have passed. “pep” or “pep_media” indicate that you requested AML check has not been run.

Info.NameMatchCount

Integer

0 or more

The number of times we matched the name provided

Info.AddressMatchCount

Integer

0 or more

The number of times we matched the address provided

Info.DoBMatchCount

Integer

0 or more

The number of times we matched the date of birth provided

Info.GovIDMatchCount

Integer

0 or more

The number of supplied documents we succeeded in verifying

Info.OtherIDMatchCount

Integer

0 or more

If Other IDs were matched (e.g. email, mobile, etc) then that count appears here.

Info.ManualMatchCount

Integer

1 or more

Only included if Manual KYC process used. Provides the number of documents used to pass KYC

Info.ManualKYCMessage

string

Manual KYC details

Lists the matching documents used to pass a manually verified KYC check

Important.Blacklisted

Boolean

True / false

Indicates if the entity in question was found on the internal Blacklist.

Only included if true

Important.Whitelisted

Boolean

True / false

Indicates if the entity in question was found on the internal Whitelist. 

Only included if true

Important.Duplicate

Boolean

True / False

Indicates if the entity in question is potentially a duplicate.

Important.CreditBureauMatch.XXX

Boolean

True / False

Indicates a match/fail with a credit header source that may require notification be sent to the customer.


If set to true, the match was successful


If set to false, the match failed and the customer may need to be notified of this fact.


The XXX would be replaced with the reporting bureau. Valid values are:

  • Equifax
  • Experian

It is possible for there to be more than one of these, depending on how your failover/cascade works.

Risk Score Related Notes

Risk.Level

String

One of:
LOW

MEDIUM

HIGH

UNACCEPTABLE

Gives the risk rating for the entity at this time

Risk.Policy

String

Customer specific, but defaults nclude

SDD

EDD

Fail

The configured risk checking policy that was applied

Important.VERY_HIGH_RISK

Boolean

True / false

Risk score is considered very high (over 75)

Only included if true

Issue.HIGH_RISK

Boolean

True / false

Risk score is considered High (over 50)

Only included if true

Issue.MEDIUM_RISK

Boolean

True / false

Risk Score is considered Medium (over 30)

Only included if true


Did this page help you?