Skip to main content

Risk Fraud Classification

While Identity Verification asks "is this the right person?", Risk Fraud Classification addresses the probabilistic variable: what is the real risk of this transaction turning into a financial loss for your business?

What it does

The engine cross-references the face and the identifier (code) with additional metadata to identify data inconsistencies, history of third-party document use, behavioral anomalies, and multi-account activity.

Adoption advantage: can be consumed through our SDKs or via API only.

Inputs

A process created via Create Process (Web & Native) or Create Process (API).

Required:

  • Person's selfie (imageBase64)
  • Primary identifier in subject.code (government ID, email, phone number, etc.)

Optional (Highly Recommended):

  • clientReference
  • Extra metadata: email, phone, demographic data (name, date of birth, gender, etc.) — these are the essential inputs for a complete behavioral model analysis.

Possible responses

ResponseMeaning
YESSigns of fraud associated with this face.
INCONCLUSIVENo signs of fraud associated with this face.
There is no NO response

Risk Fraud Classification does not return NO — the absence of evidence is represented as INCONCLUSIVE, not as a confirmation that there is no risk.

Availability

SurfaceSupported
SDK (Android, iOS, Flutter)
Web (iFrame, Redirect)
API (headless, no SDK)

Valid combinations

Risk Fraud Classification appears in flows that include the trust suffix:

idlivetrust, idtrust, idchecktrust, idchecktrustdocs, idchecktrustsign, idchecktrustdocssign, idtrustdocs, idtrustsign, idtrustdocssign, idtokentrust.

For the full matrix, see Available flows.

Use cases that use this capability