When we deprecate a specific condition or parameter, it means that we are going to retire or remove it from the system in the future. It is an advance warning that you should stop using it and transition to a newer or replacement option. Deprecated conditions or parameters still work until they are decommissioned.
We deprecate features to keep our fraud-fighting system modern, efficient, and powerful. There are a few common reasons:
-
Improved accuracy: We have developed a new, more effective condition that catches more fraud or has fewer false positives. The deprecated value is often less reliable than the new replacement.
-
Performance: The old value slows down the system, and the new one is faster.
-
Simplification: Sometimes, a value is no longer necessary because its function has been added into another, more powerful condition.
When you see a deprecated value in Kount 360 or receive a notification that a condition or parameter you are using is deprecated, you should take action as soon as conveniently possible:
-
Identify usage: Check your existing fraud policies and configurations to see where the deprecated condition or parameter is being used.
-
Find the replacement: We will always provide a recommended replacement condition or parameter. The replacement is the best way to achieve the same or an improved result.
-
Migrate your policies: Update your rules to use the new replacement condition/parameter.
-
Plan for removal: The deprecated value will continue to work for a defined transition period, after which it will be removed and stop working entirely.
Caution
Do not create new rules using the deprecated feature. Migrate your existing conditions to the recommended replacement before the official removal date.
Comments
0 comments
Article is closed for comments.