---
title: Account Protection Decision Testing
slug: extensions/account-protection-decision-testing
docTags: 
createdAt: 2026-09-22T18:20:22.602Z
---

Use `forterForceForterDecision` to trigger deterministic outcomes for Account Protection events (login, registration, profile updates). Skip this page if you haven't enabled Account Protection.

It has no effect on order decisions. See [Order Decision Testing](https://docs.forter.com/extensions/order-decision-testing) to force those instead.

| Setting                 | IP sent   | Forter returns          |
| ----------------------- | --------- | ----------------------- |
| `DISABLED`              | Real IP   | Real decision           |
| `APPROVED`              | `0.0.0.1` | `APPROVED`              |
| `DECLINED`              | `0.0.0.2` | `DECLINED`              |
| `NOT_REVIEWED`          | `0.0.0.3` | `NOT_REVIEWED`          |
| `VERIFICATION_REQUIRED` | `0.0.0.4` | `VERIFICATION_REQUIRED` |

:::BlockQuote
**Note:** Set this back to `DISABLED` before production. It overrides the customer's real IP.
:::

## Forced approve on login

1. Set `forterForceForterDecision` to `APPROVED`.
2. Log in.
3. Verify: login succeeds normally.

## Forced decline on login

1. Set `forterForceForterDecision` to `DECLINED`.
2. Attempt to log in.
3. Verify: login is blocked. The customer isn't authenticated, and is redirected back to the login page instead of the account dashboard.

`NOT_REVIEWED` and `VERIFICATION_REQUIRED` follow the same pattern: set `forterForceForterDecision`, trigger the event you want to test (login, registration, or profile update), then verify the configured response action for that decision. See [Account Protection](https://docs.forter.com/extensions/accounts-configuration) for the available actions per event.