# Chapter 7 — Configuration and Models

## Purpose

This chapter provides an overview of the model and configuration layer that powers the fraud platform.

## What this area covers

The configuration area is where administrators and rule authors define the behavior of the platform. It includes the core building blocks that drive scoring, decisioning, case creation, and related workflows.

## Common configuration topics

- Models: define the logic behind scoring and evaluation.
- Request XPath: extract values from incoming requests.
- Inline functions and scripts: add small logic units directly in configuration.
- Lists and dictionaries: maintain shared reference data.
- Gateway rules, abstraction rules, and activation rules: define how decisions and workflows are triggered.
- TTL counters and watcher settings: control lifecycle, suppression, and monitoring behavior.

## Example usage

Example: if a merchant is repeatedly creating high-risk transactions, create or update a rule so the platform flags the behavior and opens a case for review.

## Operational guidance

- Keep the configuration clear and well documented.
- Test changes before enabling them broadly.
- Review the effect on scores and cases after a change is published.

## Notes

Configuration is the heart of the fraud engine. Good configuration produces predictable decisions, better case quality, and more reliable operations.