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 lets the Onboarding Platform, the Fraud Prevention Platform, and the Case Management Platform operate in an integrated way, sharing decision engine, authentication, lists, audit, and messaging.
When the institution contracts more than one module, the Core ensures information flows between them. The score calculated during onboarding follows the customer through transaction monitoring. An alert generated in the FPP becomes a case in the CMP with the customer dossier. The restrictive list updated in the Core is reflected across every module 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 use |
|---|---|
| Onboarding Platform (ONP) | Onboarding risk scoring, automatic approval decisions |
| Fraud Prevention Platform (FPP) | Real-time transaction evaluation, fraud and AML rules |
| Case Management Platform (CMP) | Risk calculation for queue prioritization and decision authorities |
The engine can run in different configurations per module. An institution that contracts only the ONP receives the engine sized for onboarding scoring. When it adds the FPP, the same engine expands its scope 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 on 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 every module:
- 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, including every analyzed case
- Records are immutable
The institution has direct access to the audit trail and can export it to respond to auditor and regulator requests, with no intermediary required.
List management
Section titled “List management”The Core centralizes the management of restrictive lists used across every module:
- Blocklist, watchlist, and greylist: managed in one place and automatically reflected in the ONP (onboarding validation), the FPP (transaction evaluation), and the CMP (case context)
- External lists: PEP, international sanctions (OFAC, UN, EU), BACEN/BCRA lists, updated in real time
- Institution lists: import and maintenance of the institution's own lists
- Change history: every addition, removal, or edit is tracked
An entity added to the blocklist in the Core is considered across every decision point of the suite from the next query onward.
Notifications and messaging
Section titled “Notifications and messaging”The Core provides a cross-cutting notification service:
- Internal alerts for analysts, supervisors, and managers (via interface and email)
- Notifications for SLAs about to expire or already breached
- Escalation and case assignment notices
- Channels configurable per alert type
Scoring
Section titled “Scoring”The Core manages the lifecycle of the customer risk score, in the 0-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: score evolution over time, with every change recorded
- Configurable thresholds: the institution defines risk bands (low, medium, high, critical) according to its policy
- Transparent breakdown: the institution can see which variables contributed to the score at any given moment
The score is created at onboarding and evolves with every customer interaction. This persistence ensures decisions at any point in the lifecycle take the accumulated history into account.
Integration architecture
Section titled “Integration architecture”The diagram below illustrates how the Core connects the modules:
Each module consumes Core services as needed. Integration between modules takes place through this shared layer: there is no direct communication between ONP, FPP, and CMP. All information exchange flows through the Core, ensuring data consistency.