KYCFeature GuidesAnti-Money Laundering (AML)

Ongoing Monitoring

Learn how to use the FrankieOne API to enable continuous AML monitoring and automatically receive alerts on changes to a customer's risk profile.

What is Ongoing Monitoring?

Meeting your Anti-Money Laundering (AML) obligations doesn’t end after a customer’s initial onboarding. Regulators require businesses to perform ongoing due diligence to ensure that a customer’s risk profile has not changed over time.

FrankieOne’s Ongoing Monitoring feature automates this entire process. Once enabled for an individual, our platform will continuously screen them against global watchlists and automatically alert you if any changes are detected, such as:

  • A customer being added to a Sanctions list
  • A customer becoming a Politically Exposed Person (PEP)
  • New Adverse Media being published about the customer

How Ongoing Monitoring Works

Our solution is designed as a simple “set and forget” lifecycle that is managed via the API and integrated directly into your workflow system.

1

1. Enable Monitoring

After a successful onboarding, you make a single API call to enable ongoing monitoring for an individual. This creates a “subscription” for that entity in our system.

2

2. Continuous Screening

Our platform takes over and perpetually monitors the entity against our global data sources. There is no further action required from you.

3

3. Real-Time Alerts

If a change is detected (e.g., a new PEP match is found), FrankieOne will automatically trigger a pre-configured “monitoring workflow”.

4

4. Action & Review

The monitoring workflow runs, generating a new workflowResult with a HIT. This result can be sent to you via a webhook, allowing you to create a case in your system for your compliance team to review and action the new alert.

Onboarding vs. Monitoring Workflows

Workflows in FrankieOne have a lifecyclePhase.

  • Workflows used for initial checks are ONBOARDING workflows.
  • Workflows triggered automatically by our monitoring service have a lifecyclePhase of MONITORING.
    This allows you to create distinct logic for handling new alerts.

API Integration: Managing Monitoring

You can manage an entity’s monitoring status using a dedicated set of API endpoints.

Enable or Disable Monitoring

To turn monitoring on or off for an individual, use the PATCH endpoint. This is a single endpoint that accepts query parameters to set the desired state.

Endpoint:
PATCH /v2/individuals/{entityId}/monitor

Query Parameters:

ParameterTypeRequiredDescription
enabledbooleanYesSet to true to enable monitoring or false to disable it.
monitoringTypestringYesSpecifies which type of monitoring to control. For AML, use AML.

Example: Enabling AML Monitoring

$curl --location --request PATCH 'https://api.frankieone.com/v2/individuals/{{entityId}}/monitor?enabled=true&monitoringType=AML' \
>--header 'api_key: {{your_api_key}}' \
>--header 'X-Frankie-CustomerID: {{your_customer_id}}'
Alternative Method: Enable via Workflow

You can also enable or disable ongoing monitoring as a step within your workflows. This allows you to automatically enroll customers into monitoring at the end of a successful onboarding workflow.

Automatic Disabling of Monitoring

To ensure you are only monitoring active customers and to prevent unnecessary costs, the FrankieOne platform will automatically disable ongoing monitoring for an entity in the following scenarios:

  • The entity is deleted.
  • All of the entity’s active Service Profiles are archived, deleted, or blocklisted.