View source for Restricted Value List

{{NATS4 Manual
| show_members_admin_section = true
}}

NATS allows you to create a restricted value list for member details to help better detect and find fraudulent members.  You can manage your restricted value list on the members admin -> restricted value list page.  You can add, deactivate and activate values to/from/on this list.  When you add a new value, it is activated automatically.  For each value you can search for members with fields containing that specific restricted value.  You can use mass actions to deactivate and activate multiple values at once as well as perform searches for matching members.  You can search for matching members using both active and de-active values.  However, only active values will be used when matching members during live transaction processing.  


To enable matching during live transaction processing, please go to the Configuration Admin -> Surfer section.  In the "Restricted Value List" section on that page, you can enable admin notifications by turning on the RESTRICTED_VALUE_LIST_MATCH_NOTIFICATION option.  You can also provide an email address (or multiple comma separated email addresses) in the RESTRICTED_VALUE_LIST_MATCH_EMAIL field to receive emails when matches occur.  You will also need to enable one of the match options.  For example, you can enable the RESTRICTED_VALUE_LIST_MATCH_FIRSTNAME_REBILL option to receive notifications and/or emails when a match occurs on the first name value for rebill transactions.  Or you can enable the RESTRICTED_VALUE_LIST_MATCH_USERNAME_INITIAL option to receive notifications and/or emails when a match occurs on the username value for initial transactions.

You can enable matching during live transaction processing on combinations of member details and transaction types

The following details can be used as part of the combination (<detail> in the configuration example below):
* username
* first name
* last name
The following transaction type groups and events can be used as part of the combination (<trans_type> in the configuration example below):
* initial (full and trial joins)
* rebill (including conversions)
* no cost registration (ncr)
* third party
* manual
* member info change detail events (change_details)

The format of the configuration name is:
RESTRICTED_VALUE_LIST_MATCH_<detail>_<trans_type>

All of the available combinations are available on the same section in the Configuration Admin -> Surfer section.