Ayzal AIAYZAL .AI
Back to Knowledge Base
Rule Building

Rule Type Reference & Configuration Guide — Ayzal AI FRM

A complete guide to every rule type in Ayzal AI FRM, with configuration examples, use cases, and best practices for building composite detection logic.

Updated 2026-10-27

Rule Type Reference & Configuration Guide

This guide explains every rule type available in Ayzal AI FRM, how it works in the backend, and how to configure it for real-world fraud detection.

1. Single Row Checks

These rules evaluate each transaction on its own. No history or cross-entity lookups are required.

field_compare

Compares a field in the transaction to a constant value.

field_in_range

Checks if a field falls between two values.

field_in_list

Checks if a field matches any entry in a Fraud List.

time_of_day

Checks if the transaction occurred within a specific hour range.

2. Two-Column Checks

These rules compare two fields within the same transaction.

field_equals

Checks if Field A equals Field B.

field_mismatch

Checks if Field A does not equal Field B.

name_email_match

Uses fuzzy matching to see if a customer's name matches their email address.

fuzzy_match

Generic string similarity between two fields (same as name_email_match but for any fields).

3. Entity Counts

These rules require looking at historical data and grouping by an entity (e.g., customer_id, card_fingerprint).

count_total

Counts the total number of transactions for an entity within a time window.

count_events

Counts the number of transactions matching a specific status for an entity.

count_distinct

Counts the number of distinct values for a target entity, grouped by a source entity.

4. Relationships

These rules traverse the Entity Graph to find relationships between entities.

shared_entity

Checks if an entity (e.g., a card) is used by multiple subjects (e.g., customers).

entity_chain

Traverses a multi-hop path between entities (A -> B -> C) and counts distinct endpoints.

5. Aggregations

These rules aggregate numeric values across transactions for an entity.

sum_amount

Sums a numeric field for an entity within a time window.

average

Averages a numeric field for an entity.

ratio

Calculates the ratio between two event counts.

amount_spike

Compares the current transaction amount to the customer's historical average.