Guardline Suite
Overview
Section titled “Overview”The Guardline Suite is a compliance and fraud prevention platform that covers the customer lifecycle at financial institutions: registration, transaction monitoring, case analysis and regulatory reporting.
The platform consists of three modules and a shared services layer called Core. The modules can be contracted independently or in combination. When they operate together, they share the decision engine, authentication, restrictive lists, scoring and audit trail through the Core.
The three modules
Section titled “The three modules”How the modules connect
Section titled “How the modules connect”The Core is the layer that integrates the modules. The risk score calculated during onboarding (ONP) is persisted and used by FPP in transaction monitoring. AML alerts generated by FPP open cases in CMP, already including the customer’s case file, and the Desk’s verdict returns to FPP. Restrictive lists managed in the Core are queried by all modules simultaneously.
The diagram below illustrates this connection in an 11-step flow:
Step by step
Section titled “Step by step”1. Registration via Onboarding Platform. A new customer starts the onboarding journey. The institution has configured the flow with document validation, facial biometrics and background check, including PEP and sanctions. The customer goes through the steps in the institution’s white-label interface.
2. Risk scoring during onboarding. The decision engine calculates the customer’s risk based on the configured rules: history, location, document type, verification results. The score (0-1000 range) is recorded and follows the customer from then on.
3. Customer approved and active. With a score within the threshold configured by the institution, the registration is approved automatically. The customer starts transacting.
4. Transactions evaluated in real time. Each transaction is evaluated by FPP in the fraud domain, with the decision in the call itself, and in the AML domain, right after, against the behavioral baseline (UBA) and the scenarios of the jurisdiction’s catalog.
5. AML pattern detected. Weeks later, the customer starts receiving several structured operations from new counterparts. An AML rule triggers and an alert is born with the scenario code, the severity configured by Compliance and the transactions as evidence. Subsequent triggers of the same scenario consolidate into the same alert.
6. Case opened in the Decision Desk. Because it has medium or high severity, the alert is dispatched to CMP, which opens the case in the AML desk with amount, currency, scenario, severity and risk level filled in, or consolidates it into an already open case of the same customer.
7. Analyst triages and investigates. The analyst accesses the case file on a single screen: customer data, transaction history, onboarding result, previous alerts, behavioral baseline. The conclusion of the investigation is reviewed by another user.
8. Committee. With confirmed indications, the case opens a committee session, with quorum and voting recorded.
9. Communication to the regulator. In Brazil, CMP generates the XML of the communication to COAF, and the institution files it. The audit trail is preserved.
10. Verdict returns. The committee decision and the record of the communication return to FPP, update the alert and enter the customer history, visible in the 360 view.
11. Or no indications: case archived. If the operation is legitimate, the case is archived with a recorded justification. The history remains available for audit.
Modular contracting
Section titled “Modular contracting”Each module works autonomously. An institution that already has its own fraud engine can adopt only the Case Management Platform. Another that needs only digital onboarding can start with the Onboarding Platform. When modules are combined, integration through the Core is automatic.
| Module | Main function | Standalone use |
|---|---|---|
| Onboarding Platform (ONP) | Configurable digital onboarding | Yes |
| Fraud Prevention Platform (FPP) | FRAML: fraud and money laundering prevention | Yes |
| Case Management Platform (CMP) | Decision Desk and case management | Yes |
| Guardline Core | Shared services (engine, authentication, lists, audit) | Backbone of the suite |
Institutions served
Section titled “Institutions served”The Guardline Suite is used by financial and other regulated institutions whose operations involve compliance, fraud prevention and AML/CFT. This includes banks, fintechs, payment institutions, foreign exchange brokers and insurers.
Regulatory compliance
Section titled “Regulatory compliance”The suite was designed for adherence to the regulatory requirements of Brazil and Argentina:
- BACEN Circular 3.978: AML/CFT procedures, KYC, monitoring and communication to COAF
- BACEN Carta Circular 4.001/2020: typologies of suspicious operations, which give the codes of the Brazilian scenario catalog
- COAF resolutions: reporting deadlines and record retention
- UIF regulations (Argentina): monitoring scenarios, severity and deadlines of the Argentine catalog
- LGPD (Brazil’s data protection law): processing and protection of personal data
- FATF recommendations: international standards for money laundering prevention
The platform follows the controls of the ISO 27001 and SOC 2 standards, without holding formal certification in those standards.
Test environment
Section titled “Test environment”All modules have a sandbox environment available after the contract is signed. The institution can test onboarding journeys, simulate transactions in the decision engine and operate the case desk with synthetic data before going to production.
Version 18, updated on