1. Introduction to Processes

Processes allow users to define and manage distinct operational flows within the system. By creating processes, users can structure and control how different rules apply to specific customer interactions, ensuring that compliance and monitoring mechanisms are tailored to different business activities.

1.1 Purpose of Processes

Processes are used to:

• Apply Different Rules to Different Customer Moments: Assign relevant rules to various business or customer journey stages.

• Enhance Compliance Monitoring: Define structured processes to ensure that regulatory requirements are met consistently.

• Enable Activity-Based Rule Execution: Implement distinct rules for the same entities depending on the nature of their engagement.

2. Defining Processes in the System

Users can create and manage processes within the system by specifying key parameters.

2.1 Process Parameters

• Name: Each process must have a unique name for easy identification.

• Process Type: Defines the category of the process, determining the required content and structure of API requests.

• Process ID: Each process is assigned a unique identifier (processId), which is necessary for API interactions and must be referenced in request payloads when triggering a process.

• Active Status: Defines whether the process is currently enabled or disabled.

Example Process Configurations:

Process Name: "KYC Verification"
Process Type: "individualKyc"
Process ID: "123456abcde"
Active: True

Other process types include:

• Transaction Process

• Car KYC Process

• Car Purchase Process

• Business KYC Process

3. Process Management Features

3.1 Creating a Process

To create a new process, users must provide:

• Name (String, must be unique)

• Process Type (Enum: transaction, carKyc, carPurchase, individualKyc, businessKyc)

• Active Status (Boolean, True/False)

Upon creation, the system assigns a unique identifier to the process.

3.2 Retrieving Processes

Users can fetch details of a specific process by querying its Process ID.

• Response Data Includes:

  • id: Unique identifier for the process.

  • name: Process name.

  • requestType: Type of process.

  • processId: Identifier used in API requests.

  • createdAt: Timestamp when the process was created.

  • updatedAt: Timestamp of the last update.

  • active: Process activation status.

3.3 Updating a Process

Users can modify existing processes to:

• Change the name for better clarity.

• Update the process type to align with business needs.

• Activate or deactivate processes as required.

3.4 Deleting a Process

Processes that are no longer needed can be removed. Deleting a process will affect rules and monitoring, so careful review is recommended before deletion.

3.5 Updating Process Activation Status

Users can enable or disable a process without deleting it, allowing for better control over rule execution.

• Set active to true or false to manage process availability.

4. Process ID Usage in API Requests

Each process has a Process ID that must be referenced when triggering processes via API requests.

• The processId field in the API request payload ensures that the correct process is initiated.

• The system validates the Process ID against the stored processes to ensure proper rule execution.

Example API Request Using Process ID

{
  "processId": "123456abcde",
  "customerId": "987654xyz",
  "transactionAmount": 5000,
  "transactionType": "cross-border"
}

The above request ensures that the correct process is executed based on the rules and monitoring configurations assigned to it.

5. Recommended Use Cases

Processes are highly flexible and can be tailored to various business scenarios:

5.1 Customer Journey & Business Flow Management

• Define processes to apply different rules at various points in a customer's journey.

• Example:

  • Onboarding Process → Run KYC verification rules.

  • Payment Processing → Apply transaction monitoring rules.

  • High-Risk Transactions → Trigger enhanced due diligence (EDD) rules.

5.2 Activity-Based Rule Execution

• Run different rules for the same entity based on their activity type.

• Example:

  • A customer making a domestic payment might undergo minimal checks.

  • The same customer making a cross-border transaction might trigger a higher level of scrutiny.

6. Summary

Processes allow users to create structured workflows that control how rules are applied in different contexts. By defining process names, types, and activation statuses, organizations can ensure that compliance and risk assessment mechanisms are dynamically aligned with business operations. The Process ID is a critical component, as it must be referenced in request payloads to initiate the correct processes. The ability to retrieve, update, and deactivate processes provides flexibility in managing evolving business needs and regulatory requirements.