Guardline Core
What it is
Section titled “What it is”The Guardline Core is the shared services layer that connects the modules of the Guardline Suite. It provides the common infrastructure that allows the Onboarding Platform, the Fraud Prevention Platform and the Case Management Platform to operate in an integrated way, sharing the decision engine, authentication, lists, audit and messaging.
When the institution contracts more than one module, the Core ensures that information flows between them. The score calculated during onboarding follows the customer into transaction monitoring. The alert generated in FPP becomes a case in CMP with the customer case file. The restrictive list updated in the Core is reflected in all modules simultaneously.
The Core is not a module accessed directly by the end user. It operates behind the scenes, providing services to the modules.
Core services
Section titled “Core services”Shared decision engine
Section titled “Shared decision engine”The decision engine is a Core service, available to all modules. Each module uses it according to its needs:
| Module | Engine usage |
|---|---|
| Onboarding Platform (ONP) | Risk scoring during onboarding, automatic approval decision |
| Fraud Prevention Platform (FPP) | Real-time transaction evaluation, fraud and AML rules |
| Case Management Platform (CMP) | Risk calculation for queue prioritization and authority levels |
The engine can operate in different configurations per module. An institution that contracts only ONP receives the engine sized for onboarding scoring. When FPP is added, the same engine extends its reach to continuous transaction monitoring.
Central authentication
Section titled “Central authentication”All modules share a single authentication and identity management service:
- Single login for the entire suite
- SSO supported via SAML and OpenID Connect
- Centralized management of users, roles and permissions
- Access control by module, feature and profile
- Configurable session and password policies (expiration, complexity, lockout after failed attempts)
The administrator manages access for the entire operation in a single place, regardless of how many modules are active.
Unified audit trail
Section titled “Unified audit trail”The Core records an audit trail that spans all modules:
- Every action by every user in every module is recorded with a timestamp
- The customer history is continuous: from onboarding to the last evaluated transaction, through every case analyzed
- Records are immutable
The institution has direct access to the audit trail and can export it to meet requests from auditors and regulators, without depending on intermediaries.
List management
Section titled “List management”The Core centralizes the management of restrictive lists used by all modules:
- Blocklist, watchlist and greylist: managed at a single point and automatically reflected in ONP (registration validation), FPP (transaction evaluation) and CMP (case context)
- Institution lists: import and maintenance of the institution’s own lists, through the panel or through the API
- PEP and sanctions: screened by the ONP during onboarding with the contracted providers and delivered to the other modules as a customer attribute, with provenance
- Change history: every addition, removal or edit is tracked
An entity added to the blocklist in the Core is taken into account at every decision point in the suite at the next lookup.
Notifications and messaging
Section titled “Notifications and messaging”The Core offers a cross-module notification service:
- Internal alerts for analysts, supervisors and managers (via the interface and email)
- Notifications when an SLA is about to expire or has been breached
- Case escalation and assignment notices
- Configurable channels per alert type
Scoring
Section titled “Scoring”The Core manages the life cycle of the customer risk score, in the 0 to 1000 range:
- Origin: initial score calculated during onboarding (ONP)
- Evolution: score updated in real time by transaction monitoring (FPP)
- Operational use: score available as a prioritization criterion in the Decision Desk (CMP)
- History: evolution of the score over time, with a record of every change
- Configurable thresholds: the institution defines the risk bands (low, medium, high, critical) according to its policy
- Transparent breakdown: the institution sees which variables contributed to the score at each point in time
The score is created during onboarding and evolves with every customer interaction. This persistence allows decisions at any point in the life cycle to take the accumulated history into account.
Integration architecture
Section titled “Integration architecture”The diagram below shows how the Core connects the modules:
Each module consumes the Core services according to its needs. Integration between modules happens through this shared layer: there is no direct communication between ONP, FPP and CMP. Every exchange of information goes through the Core, ensuring data consistency.
Version 18, updated on