Fraud API connection

ID verification session data can be linked to transactions and customers. This allows analysts to create custom rules or alert triggers based on most IDV data points as well as filter and search transaction and customer lists based on certain fields.

To link data from a session to a transaction, the session’s unique reference ID must be provided in the Fraud API request payload in which the transaction is recorded. See the following example request made to /SeonRestService/fraud-api/v2 (POST):

{
"user_id": "example-user-id",
"idv_reference_id": "6ba42e3f-c9e7-4015-baf1-443a8f4c76ac"
}

This will result in a similar response:

{
"success": true,
"error": {},
"data": {
  "id": "2bd431db0ceb",
  "state": "APPROVE",
  ...
}
}

Indicating that the data from the session with reference_id: 6ba42e3f-c9e7-4015-baf1-443a8f4c76ac was successfully stored in the newly created transaction entity with id: 2bd431db0ceb. All rules and alert triggers based on IDV parameters were evaluated with the session’s data, applying the configured behaviours (eg. black-/whitelisting selected datapoints, modifying transaction fraud score, affecting transaction state, etc.).

Such rules only take effect for transactions for which idv_reference_id was specified, meaning subsequent transactions with the same user_id but no idv_reference_id will not trigger IDV specific rules based on historical data.

The session must take place before creating the transaction (or at least has to be initialised in the IDV service) so that the provided idv_reference_id points to an existing session.

Currently, only a single IDV session can be linked to a transaction. This connection is also one-way, meaning IDV data can affect transaction scoring and outcome via rules, but transaction data has no effect on the evaluation and final result of the IDV session.

Rules & alert triggers

Basis session information

• Session status
• Document verification result
• Selfie verification result
• Proof of Address result
• Session finish date
• Session start date
• Session ID
• Session reference ID
• Session template ID
• Platform of IDV session
• Platform ID
• Duplicates found
• Email in IDV session
• Phone number in IDV session
• User ID in IDV session
• Name in IDV session

Data extraction results

• Date of birth on document
• Document number
• Full name on document
• Age based on document
• Gender on document
• Document type
• Document issue date
• Document expiration date
• Document issuing country
• Personal ID number
• Postal code on document

Individual check results

• Selfie / liveness component
• Selfie / face matching component
• Document / image quality check
• Document / validity check
• Document / age verification
• Document / name match
• Document / data validity check
• Document / authenticity check
• Document / image liveness check
• Proof of Address / document type check
• Proof of Address / document validity check
• Proof of Address / address validity check
• Proof of Address / full address check
• Proof of Address / name match

Session timeline

• Document verification started
• Document verification finished
• Selfie verification started
• Selfie verification finished
• Proof of Address check started
• Proof of Address check finished

Filtering transaction & customer lists

Filterable fields

• Session status
• Session finish date
• Document verification result
• Selfie verification result
• Proof of Address result
• Document number
• Full name on document
• Date of birth on document