FrankieOne Ongoing Monitoring

Learn how to dynamically manage AML monitoring for compliance and fraud prevention with FrankieOne’s Ongoing Monitoring API v2.

Introduction

FrankieOne’s Ongoing Monitoring API v2 empowers businesses to dynamically manage Anti-Money Laundering (AML) monitoring for entities. This solution ensures compliance with AML regulations and facilitates continuous fraud risk assessment. With the ability to enable or disable monitoring on demand, businesses can adapt to changing risk profiles efficiently.

Key Features

Dynamic AML Monitoring

Manage AML monitoring status for entities in real time, ensuring compliance and fraud prevention.

Subscription Management

Control monitoring subscriptions per service profile, tailoring your monitoring strategy.

Audit & Reporting

Maintain comprehensive audit logs and monitoring execution details for compliance reporting.

Workflow Integration

Leverage workflow processes to handle detected risk events transparently and effectively.

How It Works

  1. Monitoring Activation:

    • Use the API to enable or disable monitoring for an entity.
    • Endpoint: PATCH /v2/individuals/{entityId}/monitor

  2. Subscription Management:

    • Manage monitoring status for each service profile using the API.
    • Specify monitoring types like AML with query parameters.

  3. Audit & Compliance Tracking:

    • The API provides workflow execution details and audit history.

Integration Instructions

Prerequisites

  • API Key: Required for authentication.
  • Customer ID: Your unique identifier with FrankieOne.

Integration Steps

  1. Authentication:

    • Include your api_key and X-Frankie-CustomerID in the headers of each API request.

  2. Enable Monitoring:

    • Use the PATCH /v2/individuals/{entityId}/monitor endpoint to enable or disable monitoring for a specific entity.
    1{
    2  "comment": {
    3    "text": "Update after speaking to customer over phone directly"
    4  }
    5}

  3. Response Handling:

    • Monitor the status field in the API response for “ENABLED” or “DISABLED”.
    • Review workflows for triggered actions.

Troubleshooting

  • Error Code 400: Invalid entity ID. Ensure the entity exists in the system.
  • Error Code 403: Monitoring not enabled. Activate monitoring before checking status.
  • Error Code 429: Rate limit exceeded. Reduce API request frequency.
  • Error Code 500: Internal server error. Retry the request or contact support.

Additional Resources

Built with