Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

alert-icon-red-11.pngImage Added

 

ATTENTION:

This page has been migrated to the Tazama GitHub repository and is now located at:

https://github.com/frmscoe/docs/blob/main/Product/06-Channel-Aggregation-And-Decisioning-Processor-Cadproc.md

This page will no longer be maintained in Confluence.

Table of Contents
minLevel1
maxLevel7

Introduction

The foundation of the Actio Transaction Monitoring service is its ability to evaluate incoming transactions for financial crime risk through the execution of a number of conditional statements (rules) that are then combined into typologies that describe the nature of the financial crime that the system is trying to detect.

...

It is conceivable that the GO-list may contain different typologies that the NO-GO-list. In other words, we may find that a specific set of typologies, when evaluated together, provide enough information to allow a system to proceed with a transaction even if other typologies point out an interdiction. Actio may then issue conflicting triggers where one typology indicates interdiction and a set of different typologies may indicate an immediate proceed. The execution priority of the conflicting triggers must be determined by the client system operator during Actio implementation and may be:

  1. First come, first served: If the interdiction trigger occurs before the proceed trigger, Actio will instruct the client system to interdict the transaction. If the converse occurs, the client system will be instructed to proceed with the transaction.

  2. Interdiction Priority: All typologies in the list of interdicting typologies in the CADProc config must be received and evaluated before the set of GO typologies can be evaluated. If any typology indicates interdiction, the CADProc will immediately trigger an interdiction notification to the client system. Only once all interdictable typologies have been evaluated (and passed), only then will the list of “proceed” typologies be evaluated.

  3. Proceed Priority: All typologies in the list of “proceed” typologies in the CADProc config must be received and evaluated before any interdicting typologies can be triggered. If a proceed notification is then issued, any subsequent interdicting notifications from subsequent typologies must be ignored, though an alert must still be issued to the Case Management System for investigation.

“Proceed Priority” is the recommended approach. Proceed priority will be required in situations where a temporary allow list can be used to over-ride an interdiction outcome.

...