11+
|Auto Reject
| > **Note** > Thresholds can be configured using **multiple ranges** , each mapped to a specific evaluation outcome. > > * **Range 1** can be configured as **PASSED** or **FLAGGED** > * **Range 2** can be configured as **FLAGGED** or **REJECTED** > * _Optionally_ , a **third range** can be defined to introduce **three-stage enforcement** , where: > > * Range 1 → **PASSED** > * Range 2 → **FLAGGED** > * Range 3 → **REJECTED** (applied automatically for values exceeding the previous ranges) > > This flexible range-based setup allows gradual risk escalation from allowing transactions, to flagging suspicious activity, and finally rejecting high-risk behavior. --- ### 5. Reset Window and Reset Period Reset settings determine **how long counter values remain relevant** . You can choose different reset periods based on the types of reset windows you select to set up the counter's validity.  *Reset Window/ Reset Period* ### 5.1 Reset Window Types ## Dynamic Window The counter resets after a fixed duration **relative to the time the counter is created or first triggered** .The reset cycle is independent of calendar boundaries. * **Daily:** Resets every 24 hours from first hit * **Weekly:** Resets every 7 days from first hit * **Monthly:** Resets after the configured monthly duration from first hit **Example:** If a counter is created or first incremented at **10:15 AM** , a daily dynamic window resets at **10:15 AM the next day** , not at midnight. ## Static Window The counter resets at **fixed calendar boundaries** , regardless of when the counter was created or first used. * **Daily:** Resets at midnight (UTC +05:30) * **Weekly:** Resets at the start of the configured week (UTC +05:30) * **Monthly:** Resets at the start of the calendar month (UTC +05:30) **Example:** A daily static window always resets at **12:00 AM** , even if the counter was first incremented later in the day. ## Rolling Window The counter continuously evaluates activity within a **moving time window** . Only events within the most recent time interval are considered. **Example:** At 3:00 PM, a 24-hour rolling window evaluates transactions that occurred after 3:00 PM the previous day. > **Note** > Rolling windows are only supported when a Customer level with an ID attribute is configured. **The maximum duration for which a rolling window can be set is 23:59:59.** ### 5.2 Reset Period The reset period is a customizable cycle that can be set to daily, weekly, monthly, or a specific duration measured in seconds. * Daily, weekly, monthly, or custom duration (in seconds) --- ### 6. Customer Blacklisting (Optional) Customer blacklisting can be enabled for both pre-transaction and explicit counters. When enabled: * Breaching a threshold results in the customer being blocked from further transactions * The block remains until the counter is manually removed #### 6.1 Managing Blacklisted Customer * **Viewing Blacklisted Customers** Blacklisted customers can be viewed in the Dashboard at:**FRM Module → Search Program → Custom Blacklist Program** * **Manual Removal** Customers can be manually removed from the blacklist from the Customer Blacklist screen. Once removed, the customer is immediately allowed to transact, subject to active FRM rules. [Video](https://dth95m2xtyv8v.cloudfront.net/tesseract/assets/juspay-frm/Filter%20Check%20(13).mp4) --- --- ## See Also - [Counter Types](https://juspay.io/in/docs/juspay-frm/docs/program-management/counter-types) - [Configuration Counters](https://juspay.io/in/docs/juspay-frm/docs/program-management/configuration-counters)