---
page_title: Overview
product: Juspay FRM
page_source: https://juspay.io/in/docs/juspay-frm/docs/program-management/overview
llms_txt: https://juspay.io/in/docs/llms.txt
product_llms_txt: https://juspay.io/in/docs/juspay-frm/llms.txt
---


# Understanding Counters



Counters are component of Fraud Risk Management (**FRM** ) systems, used to track the **frequency of specific activities** , such as transaction counts or failures. These counts are compared against predefined limits, and predefined actions (PASSED/ FLAGGED/ REJECT) are triggered when these limits are met or exceeded. 

![Image](https://dth95m2xtyv8v.cloudfront.net/tesseract/assets/juspay-frm/Understanding%20Counters%20-%20visual%20selection%20(2).png)



Counters are commonly used to **control risk, prevent misuse, and enforce operational limits** . They help systems answer critical questions like:

* Is the activity within acceptable limits?
* Has the behavior crossed a threshold that requires intervention?

![Image](https://dth95m2xtyv8v.cloudfront.net/tesseract/assets/juspay-frm/Screenshot%202026-01-19%20at%2012.51.43%E2%80%AFPM.png)
*FRM Counters Configuration Dashboard*




### 1.1 How Counters Work



* Counters **maintain and increment a count**  based on configured **[levels, attributes](https://juspay.io/in/docs/juspay-frm/docs/program-management/configuring-counters#5.-Configuring-Levels-and-Attributes)** **, and** **[conditions.](https://juspay.io/in/docs/juspay-frm/docs/program-management/configuring-counters#7.-Adding-Conditions)**
* Each transaction triggers a **risk check** , during which the counter value is evaluated
* The counter value is continuously compared against configured **threshold ranges**


### 1.2 How Decision is Made



* Transactions **within the configured limits**  are allowed to proceed
* When the counter value **exceeds a threshold** , the rule engine enforces the configured action:
  
  * **Flag**  the transaction, or
  * **Reject**  the transaction
* This configuration applies to all subsequent transactions **until a reset condition is met**


### 1.3 Reset Behaviour



* Counters are reset based on the configured:
  
  * **Reset window type**  (dynamic, static, or rolling)
  * **Reset period**  (for example, daily or custom duration)
* Once reset, the counter value is cleared and evaluation starts again


### 1.4 Optional Blacklisting



* Counters can optionally enable **customer blacklisting**
* When enabled, breaching a threshold results in the customer being blocked from further transactions
* Blacklisting remains active until the counter resets or the blacklist is manually removed

Counters are a **core enforcement mechanism**  in the FRM rule engine and are evaluated as part of the **pre-transaction risk check**  to ensure transactions comply with configured limits before reaching the payment gateway.


## Counter Rule Lifecycle



Transaction triggers risk check, counters are evaluated, and decision is returned based on the threshold defined.

![Image](https://dth95m2xtyv8v.cloudfront.net/tesseract/assets/juspay-frm/Counters%20Lifecycle%20-%20visual%20selection-aOb2B.png)




### Lifecycle Substep


1. Transaction triggers a **risk check**
2. Applicable counters are evaluated
3. If conditions match, counter value is **incremented**
4. Counter value is compared against configured thresholds
5. Decision is returned (`PASS`, `FLAG`, `REJECT`)



---

## See Also

- [Explicit Counters](https://juspay.io/in/docs/juspay-frm/docs/program-management/explicit-counters)
- [Counter Types](https://juspay.io/in/docs/juspay-frm/docs/program-management/counter-types)