Fraud Management
Rules existed. But creating them required developers.
That worked early on. It didn’t work as the system grew.
A shift was needed from developer-controlled logic to user-controlled configuration.
What was happening
Rule creation and testing depended on engineering.
Even small changes required developer involvement.
Risk profiling, rules, and merchant mapping were not clearly connected.
The system existed. But it was difficult to operate.
What we changed
Shift control to users
Rule creation was restructured so admins can define rules directly.
Without relying on developers for every change.
This made the system usable for day-to-day decision-making.
Connect the system
Relationships between rules, risk profiles, and merchants were clarified.
Rules feed into risk profiles
Risk profiles apply to merchants
This made the system easier to understand and manage.
Make logic easier to work with
Rule creation and management were simplified.
Not by reducing capability.
By organizing how rules are created, tested, and applied.
Less dependency. More control.
What this enables
Teams can create and update rules without engineering support.
Risk logic becomes easier to manage and evolve.
The system can adapt faster as needs change.