Card Groups - Zendesk · Web view- the number of cards removed from the upload because the...

_________________________________________________________________________________________________

Card GroupsVersion 2015.01

3/13/2015

_________________________________________________________________________________________________

_________________________________________________________________________________________________

Property of Saylent Technologies, Inc. © 2015

Confidential and Proprietary Information. | All Rights Reserved. | Authorized Use only.

Alteration, Duplication or Distribution of, in any manner, is strictly prohibited.

www.saylent.com

_________________________________________________________________________________________________

Contents_________________________________________________________________________________________________

ContentsCard Groups................................................................................................................................... 1

The Basics.................................................................................................................................. 1

Who Can Use It?..................................................................................................................... 1

What It does?.......................................................................................................................... 1

How to Navigate?.................................................................................................................... 1

What Can I Do Here?..............................................................................................................2

Simplifying Dates on Card Groups..............................................................................................5

What do the Card Group Detail Screens Look Like?...................................................................7

General Tab............................................................................................................................. 7

Member Filter Tab................................................................................................................... 8

Marketing Tab........................................................................................................................ 10

Profitability Tab...................................................................................................................... 10

Audit History.......................................................................................................................... 10

The Basics of Creating Card Groups.........................................................................................10

Step-By-Step Card Group Creation...........................................................................................13

Step 1: Card Group and Auto Build Information....................................................................14

Step 2: Pick Existing Demographic-Based Filter(s)...............................................................15

Step 3: Create New Demographic-Based Filters...................................................................16

Step 4: Selection Page - Transaction Data Y? Or N?............................................................25

Step 5: Pick Existing Transaction-Based Filters....................................................................26

Step 6: Create New Transaction-Based Filters......................................................................27

Step 7: Verify the Summary...................................................................................................35

Step 8: Enter Membership Start Date & Finish......................................................................36

Create a Card Group without the Wizard..................................................................................36

Saving the Group................................................................................................................... 37

Build Dates............................................................................................................................ 37

Adding Filters to a Manual Group..........................................................................................37

Auto Build.............................................................................................................................. 37

Creating a Combo Filter in a Group without the Wizard.........................................................39

Manage Members & Upload Membership List..........................................................................39

The Member Management Tabs............................................................................................40

Apply Manual Members.........................................................................................................45

File Upload - File Requirements............................................................................................46_________________________________________________________________________________________________

Card Groups i

Contents_________________________________________________________________________________________________

Assigning the Card Group to Module Roles..............................................................................47

Editing an Existing Card Group.................................................................................................48

Sample Card Group – Data Breach...........................................................................................48

Sample Card Group – Low Activity............................................................................................50

Printable Cheat Sheets................................................................................................................. 52

Description of the Five Tabs under Each Card Group...............................................................53

The Nine Steps to Creating a Card Group................................................................................55

Demographic-Based Filter Fields..............................................................................................57

Compare Functions - Demographic Filters................................................................................59

Transaction-Based Filter Fields.................................................................................................61

Compare Functions - Transaction Filters..................................................................................64

Filter Codes............................................................................................................................... 67

Two Special Circumstances: And/Or and EXP..........................................................................68

Auto Build.................................................................................................................................. 69

Apply Manual Members.............................................................................................................71

File Upload - File Requirements................................................................................................72

Simplifying Dates on Card Groups............................................................................................73

Saylent Contact Information..........................................................................................................76

_________________________________________________________________________________________________

Card Groups ii

Contents_________________________________________________________________________________________________

Card GroupsThe Basics

Who Can Use It?

The Card Groups section is available to all users of the system. Basic users have the ability to use existing groups, power users and higher may create and manage groups. It is best to have a decent understanding of Transaction, Data Searches, and filters before learning “Card Groups”.

What It does?

This section contains one of the system’s key performance capabilities - the ability to segment cardholders into customizable groups. They can be used for analyzing transactions, demographics, card volumes by status, BINs, card profitability, and more. Users may create a “static” one time group that will never change, or you can create a group that is “auto-build”, and will change dynamically every day.

These groups are also designed for the “Top Card Groups” chart on the Overview page, and can be used to assist with fraud and operational analysis. The direct revenue side of card groups is their ability to be used in custom marketing campaigns designed to build loyalty, increase cardholder usage and drive interchange. Card Groups are typically created on user-defined filters that are based on customized transaction data (less than 5 signature transactions in a month, etc.), or demographic information (age, location, etc.).

With recent enhancements users are not limited to using filters for group creation. You can now upload a file to create a completely new custom group. Manage the cardholders in the group via the user interface, or via the upload. Include or exclude them as a member of the group easily. Use either the Card ID or the Card Number to create anything from a “compromised card group” for fraud, to a “do not mail” marketing suppression list.

How to Navigate?

Main Navigation Menu Bar

To access Card Groups, select Enhanced Reporting » Card Groups from the Main Navigation Menu Bar.

All Card Groups present in the system are displayed by page when this option is selected.

Card Groups can be created in two ways from this main screen (“New Group” or “New Group Wizard”). Most users should use the “New Group Wizard”. Only advanced users should use the manual “New Group” option.

Search and view a particular card group right at the top of the page. Click the particular Card Group hyperlink on the left side of the page to see the details of a particular Card Group, including the number of members, and the total breakdown by card status (if provided). This is also how you will edit, re-build, or manually manage every group.

While Filters take a main role in the creation of these groups, they do touch on many aspects of the system. Card Groups will allow you to create groups of highly focused cardholders. You may custom select a group based on age brackets, branch location, activity level, account type, card type, and many more as long as that data set is provided to the system.

_________________________________________________________________________________________________

Card Groups iii

Contents_________________________________________________________________________________________________

What Can I Do Here?

All column headers are sortable, and multiple clicks change from ascending to descending.

From the main screen you will see a:

Search bar for quickly finding a group

Once selected

Click view to go to the car group detail

Click Manage Members to go to the manually manage membership detail screens

The New Group creator (for advanced users)

Click to manually create a new group

The New Group Wizard (for most users)

Click to create a new group using the wizard

The pagination control

Click the page number desired

And a list of all the created groups present in the system

Columns are sortable by clicking on the headers

Click on the hyperlinked card group name to go to the detail screens

Click Manage Members to go to the manually manage membership detail screens

Note Any user with module access can view the card group details, but only power users or higher can create or edit them.

Each “Card Group” will provide multi-tab access to all group functions, including:

The dates used during the last build the group

The number of members currently present in the group based on date last built

The number of member cards by each status type as of the date it was built

The ability to download a detailed contact and mail list for all members of the group

The ability to make a group static, or “Auto-Build”

Access to the filter that the group may be built from

Functionality to determine when and how a member is added/removed from a group

Access to the manually manage members section of the group

The initial start date used the last time the group was built (determines when members join)

The ability to rebuild the group using a new initial start date for members

Indication on whether the group is used in a system marketing campaign and which one

Indication on whether the group is used in profitability analysis

_________________________________________________________________________________________________

Card Groups iv

Contents_________________________________________________________________________________________________

And an audit history for changes made to that group; including actual “Card Group Build” date

There will be five tabs under each “Card Group” for performing all tasks related to management of groups.

General

Group Name

Group Description

Role of the group – Reporting (searching & analysis), Marketing, or Profitability

Build start date - controls when system starts building the group in the nightly processes

Build end date - controls when system stops building the group in the nightly processes

Ability to refresh the members list based on recent manual member changes

The number of cards currently a member of the group; as of last build and manually applied cards

Ability to download a detailed list of all current members (unmask card # is avail with permissions)

Breakdown of all the members – number of cards respective of each card status

Member Filter

Auto Build Groups (check off for dynamic)

For a One Time Static Groups (Please leave unchecked – Most every group - Typical)

Build using “Filter” (will discuss in more detail later)

View Filter – the last used filter in creating the group

Create New Filter – design a new filter for this group built from

Associate Card (relevant for transaction searches) (not relevant in static/imported groups)

Daily – if you want members to be added to this group based on daily numbers

Monthly – if you want members added to this group based on monthly numbers

As of

Day Found – Adds the card as a member from the day it meets the group criteria

Start of Month – Adds from the beginning of the month it is found

Start of Quarter – Adds from the beginning of the calendar quarter it is found

Start of time – Adds from the beginning of the system time (default 01/1/2000)

Remove Association (relevant for transaction searches) (not relevant in static/imported groups)

Daily – if you want members to be removed from this group based on daily numbers

Monthly – if you want members removed from this group based on monthly numbers

As of

_________________________________________________________________________________________________

Card Groups v

Contents_________________________________________________________________________________________________

Day Prior – is actually the day found, but since the system is not updated in real time, it uses yesterday’s data, so the member technically will show as being removed from the group on the day prior.

o This is important because the cardholder may have transaction data on the last day of the month and you would want to make sure is included in any analysis.

End of Month – Removed the end of the calendar month being evaluated

End of Quarter – Removed the end of the calendar quarter being evaluated

Start of Time – Removed from the group the day it was added

o When removed membership end date will read 1/1/2000 (start of time) or the starting membership already listed this shows them as a member at some point.

Manage Members – (will discuss in more detail later) (must have permissions)

Select to be brought to the manually manage members section of the group: Use for:

o Details of group and the manual management history

o Searching the active membership list to view or delete

o Searching the manual membership list to view or delete

o Edit start and end dates for a member

o Add members to a group via a file upload using

Card ID

Card Number

o Upload history to the group

o Audit history on the group

Set initial start date – This is the date that the system will use during a manual card build as the membership start date of the members

This will show the last “initial date” used. (1/1/2000 is default start of time in system)

Transactions or data that occurred on or between this initial “start” date, up to and including the “end date”, will be returned in transaction searches

Anything outside of that range, will not be included in transaction search results

Group used for Marketing (Campaigns) Tab

Checkbox to associate a group with a campaign

If selected, please note that the card group will have limited edit functions

If campaign is still unlocked the membership can be managed manually still

Group used for Profitability

Checkbox to associate a group with the profitability engine

Historical Auditing by date range

Use to see a history of major changes to the group

Will show the last time the group was manually build through the User Interface (UI)_________________________________________________________________________________________________

Card Groups vi

Contents_________________________________________________________________________________________________

Will NOT show the last “auto build” date; go to the Group’s Manage Membership section

Simplifying Dates on Card GroupsThe dates can be confusing when discussing card groups, so before we get into detailed descriptions of everything card group related, let’s take a moment to try and simplify our thinking around card group dates.

Note

There are essentially only 3 (three) dates in card groups that have any bearing”

Actual Build Date

Membership Start Date

Membership End Date

Manual-Builds – I clicked the “build” button in the UI

Example :

If today is 01/01/2013 and I press “build” – then the actual build date is 01/01/2013

o You can’t control the date in any way, it is just today’s date

The actual build date is just the date in the system on the day the group builds or re-builds.

Auto-Builds – I told the system “start building the group on this date” and “don’t stop building until this future date”

Example :

Today is 2/1/2013, and you enter; “Build Start Date” of 2/15/2013, “Build End Date” of 2/28/2013

o The actual build date will show as “none” until 2/15/2013,

o The system will auto build the group that day, and the actual build date will now show 2/15/2013

o Every day after that, the actual build date will be updated after the auto build to show the next date

2/16, 2/17, 2/18, etc. until it hits 2/28/2013 and then the system will STOP auto building

o It will show 2/28/2013 forever, or until one of two things occurs

Auto build dates are changed or

A manual build is performed.

Actual build date is just the day that you told the system, to go look at all the records, and bring back the cards #’s

When the group is built, each member will receive a one line entry, or row, in the membership list. When they are added to the group, the system pulls in various details about each member like card ID, card number, name, address, city, state, etc.

_________________________________________________________________________________________________

Card Groups vii

Contents_________________________________________________________________________________________________

These are added as columns in the membership list. So each member has one row with all this data available to you.

Below is a modified sample, of a card group membership list.

Two of the columns in the membership list, will hold the dates that the each member was added / removed from the group.

These dates are critical to:

Getting results when you use the card group in a transaction search

Look at the first member listed (John Smith)

o If you did a transaction search for 3/1/2013 you would not get any results from this member because they are no longer a member of the group as of 1/1/2013

The total count of members currently in the group

This is a group of 1 (Jane Doe) because the first listing has been expired from the group

Note

Recurring Members

If John Smith re-joined the group at a later date, he would receive a brand new row in the membership list with a new start date and an empty end date. Dynamic groups will hold a running tally of members over time. Manual builds delete the list.

Membership Start and End Dates are determined by 3 (three) methods only.

By the Manual Build process


o Whatever you enter for the “initial start date”

Membership End Date

o Always empty; unless you manually manage in some form

By the Auto Build process


o “Associate Card” – are we adding cards to the group based on monthly or daily

o “As-of” – once system finds a new member this determines what date will be entered as the membership start date

_________________________________________________________________________________________________

Card Groups viii

Contents_________________________________________________________________________________________________

Membership End Date

o “Remove Association” – are we removing cards to the group based on monthly or daily

o “As-of” – once system determines a member should be removed, this determines what date will be entered for the membership end date

By the Manually Managing Membership via file upload or edit; dates are ignored when it is in campaign

Note You are responsible for telling the system how to determine the dates.

What do the Card Group Detail Screens Look Like?This section shows screen shots of the various card group screens, and explains the functions that are presented on each.

General Tab

The General tab indicates the group name, description, roles associated with the Card Group, and the number of cards in the group as of the date of the last card data import’ Additionally, statistics regarding the cards in the group are displayed by Card Status, Card Type, Card Program and number of Cards’ The current members list with contact information and other specifics may be downloaded into an Excel csv file by clicking on Download’ Users with the “unmasked” permission assigned to their User Id will have the option to download with sensitive data, either masked or unmasked.

The General tab of the card groups detail screens also displays the Build Start and End Dates. Build Dates only pertain to groups that are set up as “Auto Build” using a filter. Here is what to remember about Build Dates.

The Build Start Date will control the building of the Card Group with the daily import process; this means that every night, starting on _”X”_ date, the card group will be re-built following the import of the latest transaction file from the previous day. This must start on a date that is equal to today or a date in the future.

The Build End Date will tell the system when to stop this nightly process. Once the End Date is reached, the group will cease to build every night as part of the daily import process.

DO NOT confuse Build Dates with the Membership Start and End Dates. Build Dates will not affect the Membership Start and End Dates associated with each group member. It only refers to building the group during the nightly process.

Build Start and End dates are required fields on all groups; however if you are creating a static one-time group, it will never be built during the nightly process - the Build End Date can therefore be the same as the Build Start Date.

Note The system will automatically use today’s date for both fields if not provided.

If the group has a standalone “reporting” role, you may still change virtually all info and setup for the group, once it is created. You may change name and description, and select save to keep the changes. By selecting “Refresh Members” you can update the group counts from any recent _________________________________________________________________________________________________

Card Groups ix

Contents_________________________________________________________________________________________________

manual membership changes (recommended before downloading). This will NOT re-build the group in any way.

Download Group Contact & Marketing List

You can select download to get the group mail list details in a csv file. By checking the “Include unmasked card data in download” (if you have permissions) you will be able to see the unmasked card number as well.

The Excel csv file will show all of the contact information for every member record in the Card Group’ The excel file can then be used as the data source for a mail merge document, marketing campaign, or to use it to manually include or exclude this group from another group present in the system.

The Card Group ID and Card Group Name are part of the name of the file that is generated by the export. The naming convention of the download is: Card Group Mailing List [NAME - ID].CSV.

Users have the option to download an excel spreadsheet of the Cards in the Group (with/without sensitive data masked).

NoteThe group contact list has all the detail related to your group.

There are numerous fields that come in the downloadable .csv file and multiple potential uses.

Member Filter Tab

The Member Filter Tab access to the associated filter used in creating a particular Card Group. The user has the option to view/edit the existing filter attached to the group, or to create a new filter to associate with the Card Group.

Options regarding when to associate or remove cards from the group using the nightly import processes are also available to change as needed. It is from this screen that you will also re-build a Card Group using a new Membership Initial Start Date’

Note

The initial start date is not the actual build date.

The build date is the date it was manually built or built as part of the nightly process.

To find the actual build date, whether manual or auto build, please go to Manage Members.

The Member Filter Tab of the Card Group page displays the “Last card group initial date”. The screen shot above shows “NONE” as it is a system generated group and it is built automatically

In most groups:

“Last card group initial date”, is the exact same thing as the “set initial start date” field

This “last card group initial date” will be filled in with whatever “set initial start date” was previously used

It comes from the date entry field at the bottom of the “Card Group Membership Build” box (shown above)

This has absolutely NO bearing on the “auto build” process

_________________________________________________________________________________________________

Card Groups x

Contents_________________________________________________________________________________________________

During the “auto build” process, the system automatically assigns this “initial (membership) start date” based on how the user sets the “Associate/Remove” options that are configured at the top of this tab

NoteManually building a card group is the only time that the initial start date is a factor.

The initial start date used is very important because nothing before this date will be searchable.

Example:

If you perform a transaction search using a group, and enter “settlement dates” which are before the group’s “initial start date”, then no results will be returned from that search because there were no members at that time. The system sees the group as empty; the membership start date tells it to ignore anything before that date

If you rebuild a group using an initial date that’s later than the first build, you will potentially lose search results

On the flip side, if you use an initial date that is older than the first build, you will potentially add search results

The “initial start date” is the day they will join the group – you will NOT see any results BEFORE that date

Note The previous initial start date and the rebuild initial start date must be carefully considered to ensure your desired results.

Rebuilding membership of any group does have important side effects to remember:

By re-building the membership of a group, the current existing membership will be deleted’ Please proceed with caution. Once executed there is no recovering the previous group.

As a precaution, it is suggested that you download the current membership list before proceeding, unless you are absolutely sure.

o With the download available, you could at least upload the Card IDs or Card Numbers back into the system to re-create the previous group membership.

o This will need to be done with a completely empty group

The “initial start date” controls what date is added to each member record

It is the date they joined the Card Group membership

The system will allow initial dates in the past, present or future.

If the “Initial Start Date” is a date in the future, the system will not return search results until the day after the start date, IF there are transaction records for that member.

The “initial start date” will be used as the “membership start date” listed for all members of the group

This is critical to seeing results for that member’s transactions via the transaction search

Example :

_________________________________________________________________________________________________

Card Groups xi

Contents_________________________________________________________________________________________________

If you build a group based on a transaction filter that uses just the month of January, but you have set your “initial start date” to only January 15th, then

o You will miss every transaction record that exists from the 1st to 14th in your transaction search - EVEN IF you use the 1st to the 31st as the settlement date range in your search.

Manually Managing Membership (See - Manage Members & Upload Membership List)

The Manage Members hyperlink brings the user to the Member Management screens for that Card Group. This is where all manual changes to include or exclude members will be performed if the user has the appropriate permissions. We will discuss the details of this section in little later. This area also controls the upload capability to include or exclude members into card groups. It can be reach through this screen as well as the main card group screen.

Marketing Tab

The Marketing tab will inform the user if a specific card group is linked with a marketing Campaign through the Business Analytics section of the system. A card “group used for marketing” checkbox is automatically populated by the system when the Card Group is used in a Campaign’ From this tab, the user is also able to see the campaign that the group is attached too, and go to view the existing Campaign by selecting the hyperlinked campaign name.

The membership start and end dates do not apply for card groups attached to a campaign. The start date is defaulted to 01/01/2000, and there is no end date. If membership dates are attached to a group, they will be ignored the moment the group is associated with a campaign.

Profitability Tab

The Profitability tab will inform the user if a specific card group is linked with profitability analysis through the Business Analytics section of the system.

Audit History

The Audit History tab lists all audit entries for the specified date range.

Change the date range to search card groups with a larger number of entries. Click refresh when done updating to show the results from that range only.

The Basics of Creating Card Groups

Note Permissions Required

From the main “Card Groups” page there is a link for “New Group” (advanced users) and also “New Group Wizard” (most every user). The “New Group” option allows you to create a group in a manual process. The “New Group Wizard” walks the user through a step-by-step process to try and simplify the card group creation process. Both serve the same function, so for now we will just look at the wizard specifics. The wizard will assist virtually all users in creating a new group.

Groups are inherently complex to build and manage which is why the functionality is limited to power users or above, but once built they are highly valuable in understanding your portfolio by segments and like behaviors. Virtually all users will benefit from using card groups in various ways. Outside of importing a card group list directly into the system, which we will go over

_________________________________________________________________________________________________

Card Groups xii

Contents_________________________________________________________________________________________________

separately, the backbone of groups is filters, so this section will deal with creating a card group using filters.

Before we begin the step-by-step approach to building card groups, there are three crucial elements to pay special attention to so that you can understand and use card groups effectively. They are:

Dates – there are many involved in card groups and they all having a particular meaning. With the wrong dates, groups will not build correctly so it is crucial to understand their logic and purpose.

Association and Removal – For “auto-build” options; determines when a cardholder is added and removed from the group in question. With reference to dates, if you perform a search over a period of 3 days and a member was only a part of the group for 2 of those days, then you will miss their results for the last day potentially.

FILTERS – whether it points to a demographic item like “Card Status” or it points to a transaction element like “POS Signature” transactions, filters is the criteria on which these types of groups are built. Understanding Excel formulas, formula logic, and Boolean will strengthen your ability to use card groups in advanced ways, but it is not essential when creating more general groups.

There are 9 general steps to creating a new group whether using the “New Group” or the “New Group Wizard” feature. They are:

1. Card Group and Auto Build Information

2. Pick Existing Demographic-Based Filters for the group

3. Create New Demographic-Based Filters for the group

4. Selection Page – Are you using Transactions in your group? How?

5. Pick Existing Transaction-Based Filters for the group

6. Create New Transaction-Based Filters for the group

7. Verify the summary of how you set up the group

8. Enter Membership Initial Start Date & tell the system to “Finish” building the group

9. The system will build the group and make it available

Below please find a more detailed breakdown of each step, followed by a step-by-step approach with screen shots.

1. Card Group / Build Information – basic details about the group and auto build association/removal options

Name – to be used throughout the system

Description – to be shown on the main card groups section

Build Start Date – when system starts building group at night (Required on all – but an Auto Build item)

Build End Date – when system stops building group at night (Required on all – but an Auto Build item)

Auto Build Checkbox – for dynamic groups that you want to build every night or month (Rare)

_________________________________________________________________________________________________

Card Groups xiii

Contents_________________________________________________________________________________________________

o Leave unchecked for static groups - a typical group that never changes unless desired (Frequent)

When to Include (Associate Card) or exclude (Remove Association) from a card group membership

o Daily – if you want members to be Added/Removed from this group based on the previous day

o Monthly – if you want members Added/Removed from this group based on the previous month

2. Pick Existing Demographic-Based Filters – select pre-existing filters based on demographic elements

Any existing filter created for another card group or created under System » Setup » Filters will be available for use. You can also create filters on the next step to use in multiple groups based on cardholder, card, or account data elements (Demographics)

If you are NOT using an existing filter, move on to create a new one during the next step

3. Create New Demographic-Based Filters – to create a “New Filter” (only based on demographic elements)

If you don’t have an existing demographic filter to use then this is the step where you will create one.

If you do NOT need to create a new filter based on demographics, move on to the next step

4. Selecting To Use Transaction Data – decide to use or not use transactions to help define the group

First select if you want transactions to be a part of the group criteria or filters

o Such as more than “x” transactions in a month

Decide to have your transaction setup be the basis for including/excluding members from group

If the transaction option is selected then the proceed to step 5 and 6

o Note: Once selected, at least one item is required from step 5 or 6, but not both.

o Users may include both existing and new filters to a group setup

Caution: The more you add, the smaller the membership – The system could be looking for all criteria to be true. You can’t have something be “less than 4” and at the same time be “greater than 6”

If this option is not selected then the wizard proceeds to step 7

5. Pick Existing Transaction-Based Filters – select pre-existing filters based on transaction elements

Any existing filter created for another card group or created under System » Setup » Filters will be available for use. You can also create filters on the next step to use in multiple groups based on transaction data elements (Transactions) like Transaction Type, Merchant Name, and much more.

_________________________________________________________________________________________________

Card Groups xiv

Contents_________________________________________________________________________________________________


6. Create New Transaction-Based Filters – to create a “New Filter” based on transaction elements

If you don’t have an existing transaction filter to use, then this is the step where you will create one

If you do not need to create a new filter based on demographics, move on to the next step


In the wizard, the system will display a summary of all selections that will define this group

If manually creating, review the information and filters you have selected before building

8. Enter Start date for adding members to the group

Tell the system to build the group

o In the wizard select “Finish” after entering the “initial start date” for members start date

o When manually creating you must use the member filter tab to enter date and select “Build”


After telling the system to build the card group, please be patient. Depending on the size of the group and the various filters or transactions that are used to define the group, it may take several minutes to compile the complete group parameters by searching the database and adding the qualified members to the group membership list.

Note

When running transaction searches in Card360, it is important to remember that if you use a card group as part of the search, it will only look for transactions from the members of the group. The member start and end dates is what determines if they are a member.

Step-By-Step Card Group Creation

Note Card Group Wizard

To assist users with the New Group Wizard for creating custom card groups, this section will demonstrate a step-by-step approach.

Remember this system has many facets. The vast filter selections make it impossible to demonstrate all the potential uses, and each user’s job role is different. The possibilities for segmentation are only limited by the user’s imagination or by the data received. There are many ways to slice an overall card portfolio, and each slice can show different patterns of behavior. Understanding those behaviors could mean more revenue, and that is why card groups are a very important aspect of the system for all users of all departments; Board & Executive Level, Operations, Product Management, Marketing, and Fraud Management have all benefited from use of card groups and Card360 in general._________________________________________________________________________________________________

Card Groups xv

Contents_________________________________________________________________________________________________

If there is a specific group you are trying to create, or data you are trying to reach, it can probably accomplished in some form. If requested, a step-by-step document could be requested to assist you; contact your Saylent Relationship Manager. If it is not currently possible, we will be happy to consider it for future enhancements, if possible. We welcome your feedback in making Card360 best meet our customer’s needs’

Please consider this step-by-step as a baseline process. Merely adapt your date structures, as well as your filter criteria to achieve your desired segment.

The wizard will guide you through a series of up to nine (9) steps, gathering the information along the way that is necessary to create a collection of cards.

NoteClicking on the “Close” button in the lower right hand corner of the wizard, will close the wizard and nothing will be saved. If the system is timed out and you are logged out, all data is lost.

To begin, click the hyperlink “New Group Wizard” on the top of the main Card Groups page to activate the wizard.

Step 1: Card Group and Auto Build Information

The first step of the Card Group Wizard is where the user enters the basic group information. Enter the name of the Card Group being created (used throughout system), as well as a short description of the group purpose (shown on the main card groups screen).

Note The build dates and the Include/Remove drop-down on this screen only applies to dynamic groups with Auto Build checked off and enabled.

The user will indicate the Build Dates to be used by the system. On auto build groups, the system will build and re-build the group each and every night as one of the final steps in the nightly import process. The “Build Start Date” tells the system what night to begin building it, and the build process will re-occur for as many nights as it takes to reach the “Build End Date”.

Also critical on this page is “Include/remove card membership to this group”. The dropdown presents the option for daily or monthly. This is the same thing as the associate card/remove association that we saw in the Card Group Detail screens. This setting determines whether members are added or removed from the group, based on daily activity/data or monthly activity/data. It determines if cards begin or end their membership in this group on a daily, or a monthly basis.

To begin creating a Card Group enter the following information as needed:

1. Name Field - Enter the name that the group will be referred to

2. Description – Enter a user friendly description that will help users understand the contents of the group and what it is intended to be used for

3. Build Start Date – Enter a Start Date that is at least today’s date or a day in the future. This date will tell the system “start building my group automatically every night on this date” (Only applies to dynamic groups with auto build on).

The date cannot be a date in the past because the builds that occur through the imports can only start as of today.

_________________________________________________________________________________________________

Card Groups xvi

Contents_________________________________________________________________________________________________

Most users creating a group that will likely be built just once (Static), can either enter in today’s date or move on. The system will auto-enter today’s date after you go on to the next page of the wizard.

4. Build End Date – Enter an End Date that is at least todays date or a day in the future. This date will tell the system “stop building my group every night as of this date” (Only applies to dynamic groups with auto build on).

The date cannot be a date in the past because the builds that occur through the imports can only start as of today.

Once the End Date is reached, the group will cease to build with the daily import process’

The Build End Date also cannot be less than Build Start Date

Although rare, and for specific users, if you want a group to auto build every night for a long time select a date in a distant future (many years). Otherwise you may return to your group to discover it hasn’t re-built.

Most users creating a group that will likely be built just once (Static), can either enter in today’s date or move on. The system will auto-enter todays date after you go on to the next page of the wizard.

5. Auto Build Checkbox – Leave unchecked for a static group that will only be built once. Check the box if you want this group to be dynamic and constantly by built every night until it reaches the user entered Build End Date.

Once checked, the build dates are required elements to proceed to the next step

When the “Auto build groups” check box is not checked, the system will automatically populate the Build Dates with today’s date and create a static Card Group built based on today.

6. Daily or Monthly – Choose daily or monthly to set how the system determines the date that members will be added to the group or removed from the group

NoteBuild dates have no effect on the start and end dates of the members in a card group.

The card group initial start date is what determines the membership dates.

7. Click Next to proceed to Step 2 or Close to cancel out of the wizard function without saving.

Step 2: Pick Existing Demographic-Based Filter(s)

Note Skip this step if you are not using an existing demographic-based filter in the system.

The second step of the wizard is where users will be able to select any demographic filter that is already in the system. The third step will let you create a new demographic filter. If you have not previously created a filter to use, and you are not using one that another user set up, then please skip this step right now.

If you are still reading, then you have an existing filter to use in this group. In order to select the previous filter and attach it to this group, you need to locate the filter by name.

_________________________________________________________________________________________________

Card Groups xvii

Contents_________________________________________________________________________________________________

1. Place your cursor in the empty field located next to the link “Add Pre-Existing Filter”

2. Start typing the first letter in your filter name, and results will be returned that match you entry

The more you type the more the list is narrowed.

3. Once you have located your filter, select it, and it will be placed as a single entry in the search box

4. Now click on the “Add Pre-Existing Filter” link

After clicking, you will see a line item appear below the search box. This tells you, that filter is attached to this group. The “[X]“ that sits just to the left of the line item is how you remove it from the group. Click the “X” and the filter will be removed from the group and disappear from the screen.

Note To add more existing filters to this group, repeat the steps highlighted above.

5. Click Next to proceed to step 3.

Important Information Regarding System Logic

Once multiple filters are selected in this step, the system will present a “Card Must Match” checkbox. This is due to Card360’s default functionality to use the logical operator of “OR” between the multiple filters. As an example, Card360 would return cards that belong to Branch 100 “OR” Branch 200’

However, if the intent is to combine the multiple filter selections together, you must enable the “Card Must Match” option. This will effectively change the OR to an AND’ In that case, with the “Card Must Match” option checked, the Card Group would return only cards that where a part of Branch 100 “AND” a part of Branch 200. This scenario obviously, can’t exist, and hence it would not return any members to this group

Step 3: Create New Demographic-Based Filters

Note You can skip this step if you do not need to create a new demographic-based filter.

The third step of the wizard is where the user can create any new demographic-based filters that they desire to be used as one of the group criteria. Users can add an unlimited number of additional card, cardholder, or account-based demographic criteria. Please note that this is an optional step, and if you do not need to add a new demographic filter, you may skip this step now.

If you are still reading then you want to set up a new demographic-based filter to use in this group.

In the previous step users could attach an existing demographic filter which would have been created at some point, using the filters section of the system. In this step, the wizard will display the filter creation options from that section of the system. Setting up filters can be complex sometimes and does require some background information. If you need any assistance, please refer to the Filters section of this manual, or contact you Saylent Relationship Manager for assistance.

_________________________________________________________________________________________________

Card Groups xviii

Contents_________________________________________________________________________________________________

Filters are really the cornerstone of the system. They are very powerful and have numerous options based on the available fields. They are also completely dependent on the data being available via the import process and system setup. If a field is available, but there is no data, then the filter will not return results. It is recommended that you perform a search or view the detail screens for card, customer, or account to determine if the data is provided in the import feed, and available for use. If you need assistance, contact your Saylent Relationship Manager to request the data or determine if it is in the system and valid for use in filters.

This step will have greater detail around setting up a filter, but again please remember there are many options and this should be used as a base guide to creating your own unique filter based on the available options.

First step is to click on the “Add New Filter” hyperlink’

This will bring up the filter creation controls directly inside the Card Group Creation Wizard.

Drop Down Detail

In the screen shot above you will notice the long list of available fields to choose from. What you are seeing is all of the available demographic-based fields in the system, which may or may not contain data depending on each installation’s specific data import process. Demographic information is provided on varied schedules depending on the specific installation. Demographic information is not held historically. It is a snapshot in time, as of the last demographic import.

In the case of card groups you will be using these demographic elements to define, or contribute to defining, your group membership. Let’s take a moment to pull out a sample list of the available demographic filter items and how they might be used.

Demographic Filter Fields

There are 5 (Five) Demographic Types:

Account

Elements of each card numbers attached account. View “Accounts” under Data Search section

Card

Elements of each card number. View “Cards” under Data Search section

Card Group

For setting a system generated unique Card Group ID as a group criteria (use caution)

Cardholder

Elements of each cardholder. View “Customer” under Data Search section for most fields

Customer

Elements of each customer. View “Customer” under Data Search section

Below is a more detailed breakdown by type:

N.H. = No “Help” is available.

“Help” brings up options to select from. Certain fields require the system to look for set information or codes.

_________________________________________________________________________________________________

Card Groups xix

Contents_________________________________________________________________________________________________

U.D. = User-Defined

A free form field that the user must know the correct entry. The system only looks for the value(s) you enter.

Note Most demographic items have NO “Help”

Demographics typically require a specific response that is particular to 1(one) account, card, or customer

The manner of your data feed determines the correct responses – Descriptions below are not necessarily correct responses

Branch ID, BIN #’s, Card Status, Card Group ID, and Phone Type are the only demographic-based fields with “Help”

Account

Account: Account Number (N.H. - U.D.) - Enter a specific account number(s)

Account: Account Type (N.H. - U.D.) - Enter the specific account type; DDA, Checking, Etc.

Account: Address Type (N.H. - U.D.) - Enter a specific type; Home = H, Business = B, Etc.

Account: Branch ID - Branches are related to a Branch ID; pick code from list OR manually enter code

Account: City (N.H. - U.D.) - Looking for the city the account was opened in

Account: Open Date (N.H. - U.D.) - Looking for the date the account was opened ( mm/dd/yyyy)

Account: Primary Holder? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

Account: State (N.H. - U.D.) - The state code or spelt out; however system shows the data set

Account: Zip (N.H. - U.D.) – The 5 digit zip or with 4 additional dash or no dash; however the data shows

Card

Card: Accept International? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

Card: Activation Date (N.H. - U.D.) - Looking for the activation date of the card ( mm/dd/yyyy)

Card: Allow Overdrafts? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

Card: Annual Fee (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

Card: BIN – BIN numbers are related to a BIN ID; pick code from list OR manually enter correct code

Card: Card ID (N.H. - U.D.) – Looking for a specific Card ID that is unique to each card in system

Card: Card Number (N.H. - U.D.) - Looking for a specific Card number; typically no dashes

_________________________________________________________________________________________________

Card Groups xx

Contents_________________________________________________________________________________________________

Card: Card Status - Each system card status has a corresponding code ex. [CODE], [A] or [Active], etc.

Card: Expiration Date (N.H. - U.D.) - Looking for the expiration date of the card ( mm/dd/yyyy)

Card: Hot Date (N.H. - U.D.) - Looking for the hot card date of the card ( mm/dd/yyyy)

Card: Institution (N.H. - U.D.) – Looking for a specific Institution

Card: Issue Date (N.H. - U.D.) - Looking for the issue date of the card ( mm/dd/yyyy)

Card: Last Used (N.H. - U.D.) - Looking for the date the card was last used ( mm/dd/yyyy)

Card: Reward Status (N.H. - U.D.) – Looking for specific entry based on data feed value

Card Group

Card Group: Card Group - Card groups are related to a Card Group ID; pick code OR manually enter code

Cardholder

Cardholder: Address Type (N.H. - U.D.) - Enter a specific type; Home = H, Business = B, Etc.

Cardholder: Birthdate (N.H. - U.D.) - Looking for the cardholder’s birthdate ( mm/dd/yyyy)

Cardholder: Cardholder Type (N.H. - U.D.) - Enter a specific type; Consumer = C, Business = B, Etc.

Cardholder: City (N.H. - U.D.) - Looking for the city the cardholder lives in based on current system address

Cardholder: Gender (N.H. - U.D.) – Looking for Male [M], Female [F], or however the data is shown

Cardholder: State (N.H. - U.D.) - The state code or spelled out; however system shows the data set

Cardholder: Zip (N.H. - U.D.) - The 5 digit zip or with 4 additional dash or no dash; however the data shows

Customer

Customer: Phone Number (N.H. - U.D.) - Looking for customer phone # however shown; dash or no dash

Customer: Phone Type - Enter a specific type; Home = H, Business = B, Office = O, Etc.

NoteIf the demographic field you are working with is looking for a specific code (represented by the entry in-between [ ] shown as [A], then keep in mind that only that specific response will work in your filter.

Example:

An active card status may be represented as “Active [A]”, but the system is looking for just the A with no brackets. If you enter active or Active or ACTIVE, there will be no results. Only the A by itself will work.

_________________________________________________________________________________________________

Card Groups xxi

Contents_________________________________________________________________________________________________

If you enter something into a field that requires a code, you must first exit the “Help”, and delete the invalid response. Do this by clicking “Help” again (it will display as “Hide”). Then continue building

You should now have a solid understanding of the demographic-based fields, what they are used for, what section of the system data they refer to, and what responses are possible to make filters work.

Unfortunately we are not done with this step, but in order to complete, please see below regarding the compare function.

How do I use the Compare Ordinals?

Now that we have an understanding on the available demographic fields and responses, let’s quickly go over one of the other very crucial aspects of filters. It is called the OPERAND or the COMPARE. In the screen shot below you can see an example of the options under the Compare field dropdown box.

These settings make a world of difference in setting up a filter. These Compare functions allow the user to tell the system exactly what they want to find. Using these Compare features does require a logical thought process to ensure you achieve your desired results.

Simply put you can’t use the equals sign with two responses in the entry field. Example: You can’t have something be a POS SIG and a POS PIN transaction at the same time.

NoteThe most likely functions for 90% of users will be = or In.

The next most common functions will be <, >, <= and >=.

Below please find a description of the 16 compare functions for use in filters.

Compare Function Description

= (Equals)

Will look for one specific value or statement value

Cardholder State: = MA; or Cardholder State: = Massachusetts

Find me all the cardholders with their state equals to Massachusetts

>(Greater than)

Will look for a minimum number/date and find any number greater than that

Card: Issue Date > 01/01/2013

Find me all the cards that have an issue date later than January 1, 2013

<(Less than)

Will look for a maximum number/date and then find any number less than that

Card: Issue Date < 12/31/2010

Find me all the cards that have an issue date earlier than December 31, 2010

_________________________________________________________________________________________________

Card Groups xxii

Contents_________________________________________________________________________________________________


Is null(Is empty)

Will look for empty fields under whatever element you are looking at

Card: Activation Date Is null

Find me all cards that have no date in the activation date field

In(Is part of)

Will look for something to be in two or more things; equals multiple entries

Cardholder State: = MA,NH; or Cardholder State: = Massachusetts, New Hampshire

Find me all the cardholders in Massachusetts or New Hampshire

Starts with Will look for data that starts with whatever you enter into the field

Customer: Phone Number Starts with 617

Find me all the customers with phone numbers in the (617) area code

Ends with Will look for data that ends with whatever you enter into the field

Card: Card Number Ends with 5469

Find me the card number(s) that end in 5469

Contains Will look for data that contains whatever you enter into the field

Card: Reward Status Contains VIP

Find me all the cards that contain VIP in the reward status field

>=(Greater than or equal to)

Will look for and then find any number AND all those greater than that

Card: Expiration Date >= 12/31/2010

Find me all cards that have an expiration of at least Dec. 31, 2010 or later

<=(Less than or equal to)

Will look for and find any number AND all those less than that

Card: Hot Date <= 01/01/2013

Find me all cards with a hot date of Jan. 1, 2013 or earlier

Not equal Will look for all data items that DO NOT Equal whatever you enter into the field

Cardholder: Address Type Not equal to Business

Find me all the cardholders with an address not classified as a business address

_________________________________________________________________________________________________

Card Groups xxiii

Contents_________________________________________________________________________________________________


Is not null(Is not empty)

Will look for any value to be entered; as long as it has “some” entry it will be found

Card: Activation Date Is not null

Find me all cards that have at least some value entered in the activation date field

Is not in(Is not a part of)

Will look for all data items that are NOT IN whatever you enter into the field

Card: BIN Is not in 1111,2222,3333,4444

Find me all other cards that are NOT from the BINS of 1111, 2222, 3333, or 4444

Does not start with Will look for data entries that DO NOT Begin with whatever entry you provide

Account: Account Number Does not start with 0

Find me all accounts that do not start with the number 0 (zero)

Does not end with Will look for data entries that DO NOT End with whatever entry you provide

Account: Account Number Does not end with a 9

Find me all accounts that do not end with the number 9 (nine)

Does not contain Will look for data entries that DO NOT Contain whatever entry you provide

Card: Allow Overdrafts? Does not contain N

Find me all the cards that allow overdrafts; or have any other response except “N”

Summary Step 3 – Creating a New Demographic-Based Filter

Now that we have a background understanding of demographic filter fields, their compare functions, and what types of data the fields are looking for, let’s move ahead to complete this step. Below are the basic tasks to complete Step 3.

1. Add New Filter – Click on the hyperlink to begin defining your desired filter

2. Field – Use the drop down to view and select from your available demographic fields’

Defines the field you want to have the system look at

To select, highlight and single click it

3. Compare – Use the drop down to view and select from your available Compare Functions

Instruct the system how to measure against the “To” (described below)


4. To – Enter desired data or required [CODE] in this field _________________________________________________________________________________________________

Card Groups xxiv

Contents_________________________________________________________________________________________________

This is what the system will go looking for in whatever Compare function you select

For example if in the Compare field indicates “=” and your To field indicates 12345, the system will return all the data contained in that “Field” that equals 12345.(Likely only has 1 result because of the =)

5. Update – Save your criteria

6. Repeat – If you wish to add more criteria, repeat steps above

7. Next – When finished adding, click Next to move on to Step 4

To remove a demographic item, click on the X next to the item. You will be asked if you want to delete the item. Select Yes or Cancel.

NoteYou may add multiple filters, but be aware that the more criteria, the thicker the logic to think through. The system allows very complex scenarios. Most users, will use 1- 4 criteria for some standard scenarios.

Two Special Circumstances: And/Or and EXP

Creating multiple filter parts requires the user to select how the different parts will interact with each other. This drastically changes the ending filter and group. As soon as you add a second filter item, you will see a new drop down box appear. This is where users will select AND/OR. With more than 2 parts, it’s recommended to use AND for all parts, or vice-versa. Mixing the two types in the same filter should be avoided unless specifically trained.

And/Or

The default will be AND, and you must either keep it, or select OR.

AND

If your intent is to have the system find results that

o Fall into, or meet the criteria of one filter AND ALSO

o Fall into, or meet the criteria of the second filter

The results meet BOTH filter criteria, but results in one that are not in the other will be excluded

Essentially: Both must be true

OR


o Fall into, or meet the criteria of one filter OR

o They fall into, or meet the criteria of the second filter.

The results are in one OR the other, but are not necessarily in BOTH

Essentially: At least one must be true

In some situations, you may need to create a dynamic filter that uses a formula to define their logic, and get a result.

For example, if you wanted to make a filter to find somebody’s AGE, then the filter item must specify how to calculate that using the “Cardholder: Birthdate” demographic field. The way you enter it and the compare functions you select, can change results. _________________________________________________________________________________________________

Card Groups xxv

Contents_________________________________________________________________________________________________

EXP – Expression or Formula

Tells the system to calculate whatever has been entered into the “To” field.

These types of filters are typically set up once and reused.

Formula is [TODAY] - (365*14) for 14 Years of Age

Example 1

In the system to find all those age 14 it is entered like this:

Ordinal Field Compare To Exp

0 Cardholder : Birthdate <= [TODAY]-(365*14) Checked

1 Cardholder : Birthdate > [TODAY]-(365*15) Checked

Example 2

To find those that are between the ages of 18 and 24 is not much different



1 Cardholder : Birthdate > [TODAY]-(365*25) Checked

Example 3

To find those that are age 55 and older



Birthdate and Today’s date are converted to a system number value. In the above expressions, the easiest way to think of [TODAY] is as a large number that grows each day. If today was 10 and you were born today, your birthday would be 100. Born yesterday it is 9, and born tomorrow it is 11.

So if I was looking for somebody that was 2 days or older

I would be looking for their birthdate to be less than or equal to 8

Ages are one of the most challenging filter Expressions present in the system because the logic can twist your thinking. Once you learn the logic though, they are not challenging to replicate. Key aspects to remember with age filters are

That the Compare Functions are reversed from normal thinking

Confusing as it may be, trust the logic

Finding an age typically involves referencing “at least “x” age, but not yet “y” age

Just insert the date you want to work with in the formula [Today] - (365*18) or *19), or *20), etc.

EXP is typically around dates, and can involve the following system values or codes

_________________________________________________________________________________________________

Card Groups xxvi

Contents_________________________________________________________________________________________________

o Other filter codes shown below

Filter Codes

There are several codes that can be used for calculations within filters. These filters include:

[TODAY] - Returns today’s date

[TODAY_DATE] - Returns today’s date

[TODAY_DAYOFMONTH] - Returns the current day of the month (1-31)

[TODAY_DAYOFWEEK] - Returns the current day of the week (1-7)

[THISMONTH_DAYS] - Returns the number of days in the current month (28-31)

[THISMONTH_FIRSTDAY] - Returns the first day of the month (1)

[THISMONTH_LASTDAY] - Returns the last day of the month (28-31)

[LASTMONTH_DAYS] - Returns the number of days in the previous month (28-31)

[LASTMONTH_FIRSTDAY] - Returns the first day of the previous month (1)

[LASTMONTH_LASTDAY] - Returns the last day of the previous month (28-31)

[MAXSETTLE] - Returns the date of the most recent transaction settlement

[MAXSETTLE_DATE] - Returns the date of the most recent transaction settlement

Codes with “_DATE” are the same as those codes without (e.g. [TODAY] = [TODAY_DATE]).

While finding an age is more complex, many of these can be used in very simple equations. Expressions using simple addition and subtraction for example, can be very easy. It will move by date by whole days.

[Today] – 5 If today’s date is May 7th, 2007, the expression [TODAY]-5 would return a value of 5/2/2007

Note If using any of the codes listed above, the “Expression?” check box for that item in the filter must be selected or else the calculation will not run correctly.

Fields without the Help Option use Statements or Expressions.

Statements are fixed values that are the equivalent of field = 0.

Expressions are like formulas and they dictate a certain set of variables, such as add to membership where account open date is = today’s date-30 or = account open date-31. When using expressions, the Exp box must be checked.

Click next to proceed to Step 4. To go back to a previous page, click Previous.

Step 4: Selection Page - Transaction Data Y? Or N?

Note You can skip this step if you do not need to add any transaction-based filters.

Steps 1 to 3 the focus was on defining the demographic criteria for the Card Group, otherwise known as the “Demo” filter’ In some cases, this will be the only definition necessary in order to create the group’ In others though, users may want to define additional criteria that is related to

_________________________________________________________________________________________________

Card Groups xxvii

Contents_________________________________________________________________________________________________

transaction information as opposed to demographic information. This is otherwise known as the “Tran” filter. Examples of such transaction filters would be:

Cards with less than 5 POS Signature Transactions in a month

Cards that performed transactions at a certain merchant

Transaction count greater than or equal to 1

Step 5 only appears if the user denotes on step 4 that it is their intent to add transaction information as part of the criteria for the Card Group’ If the check box is not enabled, this step will be skipped and the user will be forwarded to Step 7.

If you are going to be using the Card Group as the basis for a transaction search within Card360, you do not need to add any transactional criteria via the wizard unless it is necessary to create the group; however the membership start date (aka Initial Start Date) makes a big difference. If you use initial date for 2/1, and add cards to the group for 2/1 to 2/28 you will get your group, and can search forward of 2/1, but you can’t look back further with that group till the initial date is set back further.

If you want to add transaction information as criteria for the group’s membership, this is the page to start. To include transactional information as part of the criteria for the Card Group, please follow these steps:

1. Check the box- √ Include transaction data with this Card Group

2. Select Include or Exclude - the cards from the resultant transaction information

Include - If you want the transaction items you select to be the basis for including them from the group

Exclude - If you want the items you select to be the basis for excluding them from the group

3. Click Next to proceed to step 5’

Step 5: Pick Existing Transaction-Based Filters

Note Skip this step if you are not using an existing transaction-based filter in the system.

The fifth step of the wizard is where users will be able to select any transaction filter that is already in the system. The sixth step will let you create a new transaction filter. If you have not previously created a filter to use and you are not using one that another user set up, then please skip this step right now.

If you are still reading, then you have an existing filter to use in this group. In order to select the previous filter and attach it to this group, you need to locate the filter by name.

1. Place your cursor in the empty field located next to the link “Add Pre-Existing Filter”

2. Start typing the first letter in your filter name, and results will be returned that match you entry

The more you type the more the list is narrowed.

3. Once you have located your filter, select it, and it will be placed as a single entry in the search box

4. Now click on the “Add Pre-Existing Filter” link._________________________________________________________________________________________________

Card Groups xxviii

Contents_________________________________________________________________________________________________

After clicking, you will see a line item appear below the search box. This tells you, that filter is attached to this group. The “[X]“ that sits just to the left of the line item is how you remove it from the group. Click the “X” and the filter will be removed from the group and disappear from the screen.

5. Click Next to proceed to step 6.

Note To add more existing filters to this group, repeat the steps highlighted above.

Important Information Regarding System Logic

Once multiple filters are selected in this step, the system will present a “Card Must Match” checkbox. This is due to Card360’s default functionality to use the logical operator of “OR” between the multiple filters As an example, Card360 would return cards that belong to Branch 100 “OR” Branch 200’

However, if the intent is to combine the multiple filter selections together, you must enable the “Card Must Match” option. This will effectively change the OR to an AND’ In that case, with the “Card Must Match” options checked, the Card Group would return only cards that where a part of Branch 100 “AND” a part of Branch 200. This scenario obviously, can’t exist, and hence it would not return any members to this group

Step 6: Create New Transaction-Based Filters

Note You can skip this step if you do not need to create a new transaction-based filter.

The sixth step of the wizard is where the user can create any new transaction-based filters that they desire to be used as one of the group criteria. Users can add an unlimited number of additional Card Group or Transaction-based criteria. Please note that this is an optional step, and if you do not need to add a new transaction filter, you may skip this step now.

If you are still reading, then you want to set up a new transaction-based filter to use in this group.

In the previous step users could attach an existing transaction filter which would have been created at some point, using the filters section of the system. In this step, the wizard will display the filter creation options from that section of the system. Setting up filters can be complex sometimes and does require some background information. If you need any assistance, please refer to the Filters section of this manual, or contact you Saylent Relationship Manager for assistance.

Filters are really the cornerstone of the system. They are very powerful and have numerous options based on the available fields. They are also completely dependent on the data being available via the import process and system setup. If a field is available, but there is no data, then the filter will not return results. It is recommended that you perform a search or view the transaction searches and detail screens to determine if the data is provided from the import feed. If you need assistance, contact your Saylent Relationship Manager to request the data or determine if it is in the system and valid for use in filters.

This step will have greater detail around setting up a filter, but again please remember there are many options and this should be used as a base guide to creating your own unique filter based on the available options

First step is to click on the “Add New Transaction Item” hyperlink’

This will bring up the filter creation controls directly inside the Card Group Creation Wizard.

_________________________________________________________________________________________________

Card Groups xxix

Contents_________________________________________________________________________________________________

Drop Down Detail

The Field drop-down list contains a long list of available fields to choose from. This is a list of all the available transaction-based fields in the system, which may or may not contain data depending on each installation’s data import process.

In the case of card groups you will be using these transaction elements to define, or contribute to defining, your group membership. Let’s take a moment to pull out a sample list of the available transaction filter items and how they might be used.

Note You must use dates inside transaction filters, otherwise the system searched every transaction record in the system.

Example

A Filter for Txn: Named Transaction = [19]POS Signature & Txn: Transaction Count <=5

Would search everything without Txn: Settlement Date>= 01/01/2013 & Txn: Settlement Date <= 01/31/2013

Transaction Filter Fields:

There are 2 (Two) Transaction Types:

Card Group

For setting a system generated unique Card Group ID as a group criteria (use caution)

Transaction

Elements of each transaction that comes through the system

Below is a more detailed breakdown by type:

N.H. = No “Help” is available.


U.D. = User-Defined


Note Most transaction items have No “Help”

Transactions typically require a specific response that is particular to 1(one) transaction or group of transactions

The manner of your data feed determines the correct responses – Descriptions below are not necessarily correct responses

Card Group


Transaction

Txn: Amount (by group) (N.H. - U.D.) – The total transaction amount from the group

_________________________________________________________________________________________________

Card Groups xxx

Contents_________________________________________________________________________________________________

Txn: Amount Completed (N.H. - U.D.) – The total settled transaction Amount/Spend/Purchases

Txn: Amount Requested (N.H. - U.D.) – The total requested transaction Amount/Spend/Purchases

Txn: Base Transaction? (N.H. - U.D.) - Looking for Base=Yes[Y] or No [N]= Custom; PIN, SIG are base

Txn: Card Entry Method – Select from the system defined methods of entry; present, swipe, phone, etc.

Txn: Card ID (N.H. - U.D.) - Looking for a specific Card ID that is unique to each card in system

Txn: Cash Back Amount (N.H. - U.D.) – The total amount of cash back associated with a transaction(s)

Txn: City (N.H. - U.D.) - Looking for the city the transaction took place in

Txn: Country (N.H. - U.D.) - Looking for the Country the transaction took place in

Txn: Exception Amount (N.H. - U.D.) – The total exception amount attached to a transaction

Txn: Exception Fee (N.H. - U.D.) – The total exception fee attached to a transaction

Txn: Fraud Score (N.H. - U.D.) – The fraud score or range that is attached to a transaction(s)

Txn: International? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically - The International Txn Flag

Txn: Issuer Network – Pick from a system defined issuer network list; the network attached to transaction

Txn: MCC Fraud Score (N.H. - U.D.) - The MCC Fraud Score or range that is attached to a transaction(s)

Txn: Merchant ID (N.H. - U.D.) - The Merchant ID or range that is attached to a transaction(s)

Txn: Merchant Name (N.H. - U.D.) - The Merchant Name that is attached to a transaction(s); BestBuy

Txn: Merchant Type - The associated merchant category code type that is attached to a transaction(s); Gas

Txn: Message Type - The message type that is attached to a transaction(s)

Txn: Month (N.H. - U.D.) - Looking for the Month that the transaction took place in

Txn: Named Transaction – Is where all of your “Base” transactions exist; POS PIN, POS SIG

Txn: Network - Looking for the Network that the transaction took place on

Txn: On Premise? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

Txn: Our Terminal? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

Txn: PIN Present? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

_________________________________________________________________________________________________

Card Groups xxxi

Contents_________________________________________________________________________________________________

Txn: POS Condition Code – Pick from the system POS Condition Codes that may be on a transaction(s)

Txn: Postal Code (N.H. - U.D.) - The 5 digit zip or with 4 additional dash or no dash; however the data shows

Txn: Processing Country (N.H. - U.D.) - Looking for the Country where the processing took place in

Txn: Quarter (N.H. - U.D.) - Looking for the calendar quarter that the transaction took place in

Txn: Response Code - Pick from the system Response Codes that may be on a transaction(s)

Txn: Response Reason- Pick from the system Response Reasons that may be on a transaction(s)

Txn: RTD Rule - Pick from the system RTD Rule Codes that may be on a transaction(s)

Txn: Settlement Date (N.H. - U.D.) - Looking for the settlement date that the transaction took place on

Txn: State/Province (N.H. - U.D.) - Looking for the State that the transaction took place in

Txn: Surcharge (N.H. - U.D.) - The total Surcharge amount attached to transaction(s)

Txn: Surcharge (by group) (N.H. - U.D.) - The total Surcharge amount by group attached to transaction(s)

Txn: Surcharge Count (N.H. - U.D.) - The total Surcharge count attached to transaction(s)

Txn: Switch Date/Time (N.H. - U.D.) – The date/time stamp that the transaction hit the processing switch

Txn: Terminal Date/Time (N.H. - U.D.) - The date/time stamp that the transaction was sent through terminal

Txn: Terminal ID (N.H. - U.D.) – The merchant terminal id or ATM terminal id that is attached to transaction(s)

Txn: Transaction Code – The associated transaction code on the transaction detail

Txn: Transaction Count (N.H. - U.D.) - The total count of all transactions; by type, by card, by group

Txn: VAA Condition Code - The VAA Condition Code or range that is attached to a transaction(s)

Txn: VAA Reason Code - The VAA Reason Code or range that is attached to a transaction(s)

Txn: VAA Risk Score (N.H. - U.D.) - The VAA Risk Score or range that is attached to a transaction(s)

Txn: Year (N.H. - U.D.) - Looking for the Year that the transaction took place in

NoteIf the transaction field you are working with is looking for a specific code (represented by the entry [ ] shown as [19]), then keep in mind that ONLY that specific response will work in your filter

Example _________________________________________________________________________________________________

Card Groups xxxii

Contents_________________________________________________________________________________________________

A POS Signature named transaction may be represented as “POS Signature [19]”, but the system is looking for just the 19 with no brackets. If you enter POS SIG or POS SIGNATURE, there will be no results. Only the 19 by itself will work.

If you enter something into a field that requires a code, you must first exit the “Help”, and delete the invalid response. Do this by clicking “Help” again (it will display as “Hide”). Then continue building

You should now have a solid understanding of the transaction-based fields, what they are used for, what section of the system data they refer to, and what responses are possible to make filters work.

Unfortunately we are not done with this step, but in order to complete, please see below regarding the compare function.

How do I use the Compare Ordinals?

Now that we have an understanding on the available transaction fields and responses, let’s quickly go over one of the other very crucial aspects of filters. It is called the OPERAND or the COMPARE. In the screen shot below you can see an example of the options under the Compare field dropdown box.

These settings make a world of difference in setting up a filter. These Compare functions allow the user to tell the system exactly what they want to find. Using these Compare features does require a logical thought process to ensure you achieve your desired results.

Simply put you can’t use the equals sign with two responses in the entry field.

Example

You can’t have something be a POS SIG and a POS PIN transaction at the same time.

NoteThe most likely functions for 90% of users will be = or In.

The next most common functions will be <, >, <= and >=.

Below please find a description of the 16 compare functions for use in filters.


= (Equals)


Txn: Merchant Name: = BestBuy, or Best Buy

Find me all the transactions from BestBuy or Best Buy or BB Store 29

>(Greater than)


Txn: Settlement Date > 01/01/2013

Find me all transactions that have a settlement date later than January 1, 2013

_________________________________________________________________________________________________

Card Groups xxxiii

Contents_________________________________________________________________________________________________


<(Less than)


Txn: Switch Date < 12/31/2010

Find me all the transactions that have a switch date earlier than December 31, 2010

Is null(Is empty)


Txn: Postal Code Is null

Find me all the transactions that have no zip code in the transaction

In(Is part of)


Txn: State/Province = MA,NH; or Txn: State/Province = Massachusetts, New Hampshire

Find me all the transactions in Massachusetts or New Hampshire


Txn: Merchant Name starts with Best

Find me all the transactions that have a merchant name beginning with “Best”.


Txn: Merchant Name ends with Buy

Find me all the transactions that have a merchant name ending with “Buy”


Txn: Merchant Name contains Bath

Find me all the transactions that have a merchant name containing “Bath”



Txn: Terminal Date >= 12/31/2010

Find me all the transactions with a terminal date of at least Dec. 31, 2010 or later



Txn: Terminal Date <= 01/01/2013

Find me all the transactions with a terminal date of Jan. 1, 2013 or earlier

_________________________________________________________________________________________________

Card Groups xxxiv

Contents_________________________________________________________________________________________________



Txn: Amount Completed Not equal to 100

Find me all the transactions with a completed transaction amount NOT equal to $100



Txn: Card Entry Method Is not null

Find me all the transactions where the card entry method field has at least some entry



Txn: State/Province Is not in Massachusetts

Find me all the transactions that did NOT occur in Massachusetts


Txn: Merchant Name Does not start with W

Find me all transactions with a merchant name that does not begin with a W


Txn: Merchant Name Does not end with a S

Find me all transactions with a merchant name that does not end with an S


Txn: Merchant Name Does not contain 0,1,2,3,4,5,6,7,8,9

Find me all transactions with a merchant name that does contain numbers

Summary Step 6 – Creating a New Transaction-Based Filter

Now that we have a background understanding of transaction filter fields, their compare functions, and what types of data the fields are looking for, let’s move ahead to complete this step. Below are the basic tasks to complete Step 6.

1. “Add New Filter” – Click on the hyperlink to begin defining your desired filter

2. Field – Use the drop down to view and select from your available transaction fields’

Defines the field you want to have the system look at_________________________________________________________________________________________________

Card Groups xxxv

Contents_________________________________________________________________________________________________


3. Compare – Use the drop down to view and select from your available Compare Functions

Instruct the system how to measure against the “To” (described below)


4. To – Enter desired data or required [CODE] in this field

This is what the system will go looking for in whatever Compare function you select

For example if in the Compare field indicates “=” and your To field indicates 12345, the system will return all the data contained in that “Field” that equals 12345.(Likely only has 1 result because of the =)

5. Update – Save your criteria

6. Repeat – If you wish to add more criteria, repeat steps above

7. Next – When finished adding, click Next to move on to Step 4

To remove a transaction item, click on the X next to the item. You will be asked if you want to delete the item. Select Yes or Cancel.

NoteYou may add multiple filters, but be aware that the more criteria, the thicker the logic to think through. The system allows very complex scenarios. Most users, will use 1- 4 criteria for some standard scenarios.


Creating multiple filter parts requires the user to select how the different parts will interact with each other. This drastically changes the ending filter and group. As soon as you add a second filter item, you will see a new drop down box appear. This is where users will select AND/OR. With more than 2 parts, it’s recommended to use AND for all parts, or vice-versa. Mixing the two types in the same filter should be avoided unless specifically trained.

And/Or

The default will be AND, and you must either keep it, or select OR’

AND






OR




_________________________________________________________________________________________________

Card Groups xxxvi

Contents_________________________________________________________________________________________________



In some situations, you may need to create a dynamic filter that uses a formula to define their logic, and get a result. For example, if you wanted to make a filter to find somebody’s AGE, then the filter item must specify how to calculate that using the “Cardholder: Birthdate” demographic field. The way you enter it and the compare functions you select, can change results. See below

EXP – Expression or Formula

Tells the system to calculate whatever has been entered into the “To” field

Example

[Today] – 5

If today’s date is May 7th, 2007, the expression [TODAY]-5 would return a value of 5/2/2007


Other filter codes shown below

Filter Codes

There are several codes that can be used for calculations within filters. These filters include:
















Click Next to proceed to step 7. To go back to a previous page, click Previous.

_________________________________________________________________________________________________

Card Groups xxxvii

Contents_________________________________________________________________________________________________

Step 7: Verify the Summary

Step 7 shows a summary of all of the entries made on the previous six steps’ It is important for the user to review this summary before proceeding on to the next step’ If there is anything that is inaccurate in the summary, the user should click on the “Previous” button to return to the previous steps and make the appropriate corrections.

Click Next to proceed to step 8. To go back to a previous page, click Previous until you reach the page you need.

Step 8: Enter Membership Start Date & Finish

The final step of the wizard is where the user tells the system to search, identify, and qualify cards to meet the demographic and transaction filter criteria that has been set up. The system will then build the Card Group Membership List. The system will first require the user to select a date.

This date will be used in the systems qualification, and will ultimately determine when you may be able to see it as an active member of the group. Card360 will use the criteria defined previously for the Card Group and look for cards that fit the parameters. It will do this from the date you entered going forward. It will add, edit, or remove cards as they fall in or out of the overall definition of the group. It does this by affecting the start and end dates for each member of the group.

“Begin membership on” (aka “Initial Start Date”) determines the start date of all the members in the group. It will not necessarily be that date, but the date does determine when a card may be in a group, and also all the times it has joined and left the group over time.

This Initial Date is very important. If you perform transaction searches before your initial start date, you will likely not find any results. Quite simply put, during the timeframe of your search, they weren’t a part of the group, so even if they had results, you won’t see them. That card was not even a part of the search.

Note Clicking Close at any time during card group creation up to this point will exit the Wizard and delete all information and the card group will not be created.

Click the “Finish” button to save the Card Group and its definition to the application, and to build the membership, if applicable.

You will receive confirmation that the card group has been created. This Card Group will now be included in the list of Card Groups found under menu items Enhanced Reporting l Card Groups.

Click Close now to finish the creation process.

Create a Card Group without the WizardThis section will perform a brief overview of creating a group manually, without the use of the “New Group Wizard.” As only advanced users will use this method, it is assumed that they understand the specifics of each step. If more detail is required, please refer back to the section on creating a new group via the wizard. You can also refer to the section of this manual dealing with Filters.

The overall steps in creating a group do not change when creating a group manually. Those steps are:

1. Card Group and Auto Build Information

_________________________________________________________________________________________________

Card Groups xxxviii

Contents_________________________________________________________________________________________________

2. Pick Existing Demographic-Based Filters for the group

3. Create New Demographic-Based Filters for the group

4. Selection Page – Are you using Transactions in your group? How?

5. Pick Existing Transaction-Based Filters for the group

6. Create New Transaction-Based Filters for the group


8. Enter Membership Initial Start Date & tell the system to “Finish” building the group


The user can access manual group creation through the “New Group” link on the main Card Groups page at the Enhanced Reporting l Card Groups menu item’ Click the hyperlink “New Group” on the top of the page’

After selecting, users will see an empty version of the Card Group Details screen. The creation process starts on the General Tab. Here you can enter the Group Name and a common description.

Saving the Group

The “Save” link acts like an insert function. Until you select “Save”, no information will be saved and the group will not be created. If you plan on using the manually manage membership features to upload a list of cards, then simply add the name and description, click save, and then go to the manual management section of that group which we will discuss in a little bit.

If you will be using filters to define your group, then you may save your group now, and then continue adding information to finalize the group. If you create the group without adding a filter, the system will inform you that there is no filter attached to the group.

If you make a mistake, or DO NOT want to add the group to the system, simply navigate away from this page. All changes will be lost. It is recommended that you enter all group information before saving, so that unnecessary groups do not burden the system

Build Dates

Before saving, you may add build dates to your group. Remember these only apply to groups with the “Auto Build” checkbox enabled. If you have specific dates to use, you may enter them at any time. If you are creating a static group, then you may either enter in today’s date for both the start and end dates, or let the system do it for you. If the Build Start and End Dates are not filled in, when you select “Save” the system will automatically add today’s date to both fields.

Adding Filters to a Manual Group

Every other aspect of manually creating a group will be performed on the Member Filter Tab of your new group detail screens. Please note that “Card Group Membership Build” section on the bottom of this tab, is not available UNTIL you save new group. Attach your existing filter through the open field “Build using filter”, or “Create New Filter”.

Auto Build

In the top left corner of the Member Filter tab there is the checkbox for Auto Build. This is defaulted to be off as the system standard practice is build one-time static groups. Dynamic _________________________________________________________________________________________________

Card Groups xxxix

Contents_________________________________________________________________________________________________

groups that build as part of the nightly import process, are used in specific situations, are rarer, and are typically for only advanced users.

Please be cautious to only use auto build if you are absolutely sure it is needed. Unwanted or unused groups that are accidentally set with auto build enabled, creates an unnecessary drain on the system’s resources; via nightly imports

Remember, once you enable auto build, you must manage all the settings for auto build. These settings are:

Your Build Start and End Dates (on the General Tab)

This is where you essentially schedule (Start Date) a task in the system, to have the group be built every night as part of the nightly import process. This is a recurring event until it reaches the End Date

o A “Card Group Build” process will be performed every night following the transaction import processing from the previous day

Build Dates must be at least today, and the ending date can’t be earlier than starting date

The group will be re-built as every night, without fail, until you instruct it to stop (End Date)

Association settings – How are people added and removed from the group? (Member Filter Tab)

Associate Card – essentially it is the date that members are given as they are ACTIVATED into the group

o Time period to use in qualifying cards against your filters

Daily – Look at yesterday’s transactions and demographics to tell me what’s changed

Monthly – Look at monthly transaction totals and demographics to tell me what’s changed

o “As of” assessment - tells the system how the Start Date for each new (or re-joining member) will be determined. Pay attention, this affects transaction search results when using card group.





Remove Association– essentially it is the date that members are given as they are EXPIRED from group

o Time period to use in qualifying cards against your filters

Daily – Look at yesterday’s transactions and demographics to tell me what’s changed

Monthly – Look at monthly transaction totals and demographics to tell me what’s changed

_________________________________________________________________________________________________

Card Groups xl

Contents_________________________________________________________________________________________________

o “As of” assessment - tells the system how the End Date for each current (and former) members are going to be determined. Pay attention, this affects transaction search results when using card group.

Day Prior – Members are expired from group; day prior is the end date (expiration date)

End of Month – Removes from end of the month it is found; expires last day of month

End of Quarter – Removes from end of the calendar quarter; expires end of quarter

Start of time – Removes using the beginning of the system time (default 01/1/2000) or start of time in the membership details. Allows you to see that a card was a member of the group, but with Identical Dates for Start and End Dates, the system sees the member as inactive

Note These must be set when auto build is enabled.

Creating a Combo Filter in a Group without the Wizard

When using the wizard to create a group, there is typically a “Demo” filter (demographic), and a “Tran” filter (transaction). This is a little more challenging when creating manually because the wizard automatically attaches the transaction one as a Sub-Filter to the main demo filter. Card Group filters lead with the demographic elements; account, card, & cardholder

Typically those using the manual creation have a command of the system and are using repeatable and reusable elements. A filter set up for card status = active, can be attached to multiple groups. As the “Demo” filter is the primary, they are still easily created through this manual step; however it is recommended that you set up your transaction filters in advance. It can be done here, but it requires a specific training.

It is also important to point out that it requires a manual manipulation of the AND/OR comparison between multiple criteria. Below is an example of where that would be accomplished.

Existing Demo filters may be added through the “Filter Selection” tab. This tab will become present after selecting “Create New Filter” from the card group’s Member Filter tab.

Adding the transaction filter as a sub-filter (pre-filter) to the demographic ones is done on the “Settings tab. As you can see there is no functionality to create a new transaction filter. You simply start typing in your transaction filter name and when you see it, click on it. Then select update, to save that filter. There is no way to change the AND/OR evaluation from here.

In summary, manual creation of groups works very well for demographic filters, or for importing the membership list manually, but doing it for transaction filters is more complex. The Wizard is designed to assist with this highly complex operation. It can be achieved manually, but typically reserved for pro-users.

Manage Members & Upload Membership ListEach Card Group is enabled with a section to manually manage the current members of that group. This is referred to by the system as “Manage Members”. You will see this link via three locations inside the Card Groups section.

At the top of the Main Card Groups Screen – to the right of the search field

_________________________________________________________________________________________________

Card Groups xli

Contents_________________________________________________________________________________________________

Type in the field to find your group, and then once selected, click Manage Members

To the right of every card that is listed on the card groups main screen

Scroll down to find you desired group, and then click Manage Members all the way to the right

Via the Member Filter Tab of your selected Card Group

Directly above the Card Group Membership Build box, click Manage Members

Note Select any of these three Manage Members links to go to that group’s member.

The Member Management Tabs

The member management area for each group consists of 6 (six) total tabs. Collectively, they hold all the management capabilities to view and delete members, adjust start and end dates on members, and even upload a list to modify a group.

General Tab – Current group membership details & manual membership details; build group, apply changes

Membership Search – Search member list, delete cards from the membership; individual or mass select

Manual Members Search – Search manual list before it’s applied; delete, update start/end dates, include/exclude

File Upload – From here you can upload a file of Card ID or # to include or exclude them from the group list

File Upload History – View the history of changes to this group via the File Upload; rejected files show no details

Audit Search – See the history of all major changes to this group via the audit trail records

There is a tremendous amount of functionality on these pages, and the possible methods to use are vast. With the file upload ability you can upload a large list of custom members, or upload a “Do Not Mail” marketing suppression list to exclude them from your group. You can also make additions to that suppression list by uploading the new members that have opted-out of marketing programs to include them in your master suppression list.

Note

For Card Groups that are associated with an “active” Campaign, the manual membership will not allow the start and End Dates of the card to be updated’ They will be defaulted to the “beginning of time” (system minimum of 1/1/2000) and the End Date will be set to NULL. Note: the initial campaign build will ensure that data is accurately generated for the correct time periods.

For non-Campaign Card Groups, the manual membership will allow edits to the Start and End Dates of cards’ However, the system will prevent more than one manual card member from being added to the Group at a time’ For example, if a manual member card has been added with a date range of 1/1/2012 to 1/31/2012 and a User updates the date range for the card to 2/1/2012 to 2/15/2012, the system will replace the original dates (1/1/2012 to 1/31/2012) with the updates entered by the User (2/1/2012 to 2/15/2012).

_________________________________________________________________________________________________

Card Groups xlii

Contents_________________________________________________________________________________________________

Let’s go through each screen one by one displaying a description of the available details, and functions.

Member Management – General Tab

Card Group Membership Details

Last membership build – the system date on which the group was last built; Is NOT the initial member date

Total members – the total of all active and inactive members currently in the group

Active members – all current qualified members with a start date, but no end date

Inactive members – all previous members showing a start date, but also a member expiration date; inactive

Manual Membership Details

Last manual build – is the last system date on which a manual change was made to group, or file uploaded

Total manual members – is the total number of members that have been edited/included/excluded from group

Include members – the total number of group members that have been manually manipulation to be included

Exclude members – the total number of group members that have been manually manipulation to be excluded

Apply Manual Member

If you have made recent manual changes to a group, then it is possible you have not applied those changes to the group and officially made the change.

You MUST click this to apply all pending changes that have made to the group if you did not already

Card Group Membership Build Box

Has 3 (three) key components

o Last Card Group Initial Date

The member start date that was used the last time the group was built; see below

o Set Initial Start Date

The initial start date you would like to use when building or re-building the group with

o Build

Click this after entering your desired “Set initial start date”

This will permanently delete the existing membership and re-build the group

As a precaution consider downloading the current membership list before you proceed with a rebuild. At least you could revert back, via the file upload to an empty group

_________________________________________________________________________________________________

Card Groups xliii

Contents_________________________________________________________________________________________________

Member Management – Membership Search Tab

It is possible to run search without entering any parameters and simply clicking on Search link. It will show all the Members.

This tab will allow for a search of the active and inactive card group members. Searches will not yield any results for manual membership changes that have NOT been applied. Only the applied and current membership is available here.

Card ID – Enter the unique system id associated with the current member Card # you are looking for

Card Number - Enter the current member Card # you are looking for

Start Date - Enter the earliest membership start date you would like to search within; will NOT show earlier results

End Date - Enter the latest membership end date you would like to search within; will NOT show later results

Select BINs – Click to select specific BINs that you would like to search within; only results from those BINs will show

Hide Summary – Hides the BIN selections that are being used in the search; similar to transaction search function

Search – Once you have entered your search parameters, click to execute the search and return the results

Clear – Clears all of your search parameters and lets you start a new search

Export Members – Exports the selected members to a csv file to manage offline or use in a file upload

Include Card Numbers – An export option; will include the unmasked card numbers in the export download

Delete Items – Deletes whatever items returned in the search that you have checked off the “Select” box

Delete All Items – Deletes all the items returned in the search; selects all and then deletes all

Number of records per page – Allows user to determine how many results are shown on one page

Jump to page / Go To Page – Allows user to select page # to go to; Click “Got To Page” after you have selected

Member Management – Manual Members Search Tab

It is possible to run search without entering any parameters and simply clicking on Search link. It will show all the Members.

This tab will allow for a search ONLY on the manual members to the card group membership list. These members could be considered “pending” members until applied to the group. These members will be automatically applied to the group during the regular overnight processes. You may also instruct the system to apply them immediately through the General Tab’s “Apply Manual Member” link.

_________________________________________________________________________________________________

Card Groups xliv

Contents_________________________________________________________________________________________________

Card ID – Enter the unique system id associated with the pending member change you have NOT yet applied

Card Number - Enter the pending member Card #; that has NOT yet been applied to group

Select BINs – Click to select specific BINs that are pending a manual membership change; NOT yet applied

Hide Summary – Hides the BIN selections that are being used in the search; similar to transaction search function

Include or Exclude – All, Include, or Exclude; returns the include or exclude results for whichever type you select

Search – Once you have entered your search parameters, click to execute the search and return the results

Clear – Clears all of your search parameters and lets you start a new search

Export Members – Exports the selected members to a csv file to manage offline or use in a file upload

Include Card Numbers – An export option; will include the unmasked card numbers in the export download

Delete Items – Deletes whatever items returned in the search that you have checked off the “Select” box

Delete All Items – Deletes all the items returned in the search; selects all and then deletes all

Number of records per page – Allows user to determine how many results are shown on one page

Jump to page / Go To Page – Allows user to select page # to go to; Click “Got To Page” after you have selected

Edit – Each member entry returned can be edited to change the Start/End Date to whatever date you desire

Note Applied members are now a part of the current group membership.

Member Management – File Upload Tab

This tab is where users will upload a file of either Card ID#’s or unmasked Card Numbers. The list can be used to include the list into the group membership, or to exclude the list from the membership. So it can be used to either create a completely new group, or to edit an existing one.

Browse and select – Pick the file from your hard drive that you would like to upload into the system

Include or Exclude? – Pick one. Do you wish to include the member list you are uploading? Or exclude them?

This functionality is not for adding or removing card numbers from the system but just for including or removing card numbers from the particular Card Group.

_________________________________________________________________________________________________

Card Groups xlv

Contents_________________________________________________________________________________________________

Captcha Text - A security element; enter the text exactly as shown including capitals vs. lowercase

Click “Load Another Image” if you are having difficulty reading the text

Upload – Click when you have selected and entered everything; starts the upload verification process

Once you upload your selected file, the system will inform you if the file was successful or rejected. If there was an error in the upload process the file is not uploaded and the lists of errors are displayed as well as audited. Variables, app settings and security protocols are adjustable through various levels.

Contact your Saylent Relationship Manager for questions on your specific environment.

Note As a security setting, rejected records or files will return little to no information. This prevents card farming and other techniques.

Whether a file is rejected or not depends on how your administrator has elected to set the parameters.

There is an application setting that will say “if X % of a file does not match the institution’s cards and BINs”

Then the file will be rejected and no information will be returned to the user concerning the bad records.

Member Management – File Upload History Tab

This tab provides a running history of all uploads attempted on each group. The individual file upload history of each card group, will track both successful and failed attempts. Successful attempts will provide the user with some basic record count details. The “error” or failed attempts will not show any record count details though.

The following information is displayed in the File Upload History Tab:

Upload Id - the unique system assigned id allocated to the manual member file

User Name - the name of the User Id processing the file upload

Include or Exclude - shows if the members were included or excluded from the Card Group

Occurred - the date and time of the file upload

Status Code - the status of the file upload.

Processing Status Order (Some of these will happen fast and the User may not be able to see the individual status updates.)

Pending - when the Upload ID is created

Loading - as the contents of the file is sent to the database

Loading Complete - when the contents of the file are completely added to the database

Data Transferring – when records are matched with the existing cards in the system

Pending – the system is waiting for User input after the data was sent to the database and matched to records.

_________________________________________________________________________________________________

Card Groups xlvi

Contents_________________________________________________________________________________________________

o The User has to select one of the three options;

Accept and upload another file

Accept and apply manual members

Cancel my upload to change this status

Complete - When the file contents were applied to the Card Group

Note If at any of these steps a major error occurs (an error that stops the process from moving forward), the status will automatically be set to error.

Below are the descriptions of the individual columns in the File Upload History.

Record Count - number of records processed.

Parse Errors - count of errors while parsing the uploaded file.

Database Count - number of records saved as manual members in the database.

Matched - number of card numbers that are matching the already existing cards in the system. For a card to be saved as a member to a Card Group, the card number needs to already exist in the system.

Unmatched - number of records that do not already exist in the system. If the card numbers in the upload file are not in the system, they will be rejected and not added to the Card Group.

Dates Adjusted - if a Card Group is linked with a Campaign, the Start Date and End Date of the membership for the card numbers uploaded will be adjusted to 1/1/200 (start of time) and end date will be NULL. This column shows the number of dates adjusted.

Campaign Removed - the number of cards removed from the upload because the institution/BIN it belongs to is not part of the Campaign. This data is valid for Card Groups that have Campaigns. This column is a check against the institutions and BINs that are on the Campaign. If the User uploads a card that belongs to an institution/BIN and that institution/BIN is not in the Campaign the card will be removed from the Card Group of the Campaign.

Duplicates - if there are any duplicate card numbers in the file uploaded, they will not be uploaded twice but the number of duplicates will be captured in this column.

Member Management – Audit Search Tab

This tab will provide access to the groups audit trail. Every major action with regards to each group will be tracked and available for research. This is in addition to the system audit and user audit sections of the system.

Shows all the management actions conducted on the Card Group’ The User can select a Start Date and End Date and view all the actions conducted on the Card Group.

By default the Start Date and End Date are for the current week. The default Start Date is a week ago from today and the End Date is defaulted to tomorrow. These dates however can be changed to any desired dates.

The search results show the Audit Id, User Name, Date Occurred, Event Name and Group Name.

Typically this information is relied upon to determine what User and/or action was made to a Card Group.

_________________________________________________________________________________________________

Card Groups xlvii

Contents_________________________________________________________________________________________________

Apply Manual Members

All manual changes to groups, must be applied to the group in order to complete the process.

Method 1

The confirmation screens following a successful upload will provide three options for the user to choose. You may apply manual member changes through one of these options, or through the Member Management section on the General tab.

Accept and upload a file – You proceed, but you have NOT applied changes, they are pending

This adds the successful contents of your file to the pending manual membership change table

There it will remain until one of two options occur

o The user applies the membership changes manually

o The system will automatically apply the changes during the overnight processing

Accept and apply manual members – You’re done. Everything is applied. Ready to use.

No further action is required. Your group is ready to use for any task

Cancel my upload – I changed my mind and do not want to upload this file. Cancel everything.

If something doesn’t look right, or you are unsure, it is better to cancel and not have to fix later. Be sure

Method 2

You may also add your group changes through the “Apply Manual Member” link. This is located on the General Tab of your group’s Member Management detail.

If the User has not chosen any of the options under Method 1, and then navigates away from the page or times out for inactivity, the upload process will remain in Pending status and the three options will cease to be available. The previous process will remain in pending state and the member file will need to be uploaded again.

The system will track all the audit events, and display them on the General Tab of the Member Management section of the card group. A warning message is displayed on this tab to inform the User of any events that took place that may have an impact to the membership of the Card Group, for example a file upload that included or excluded members.

Each card group has its own management section, and in order to apply manual membership changes, you must do it via the individual group. There is NO mass “apply” feature other than the overnight processing builds, which act as a failsafe.

Once there are members in the pending tables, they will automatically be added to the group, unless you stop by deleting the affected members. You would do this through the Manual Members Search Tab.

If a group is part of a Campaign and there are manual changes that have not been applied, the Administrator of that Campaign can force the changes to the Card Group without warning, so the Collective Campaign Card Group can be locked and the Campaign can become active’

_________________________________________________________________________________________________

Card Groups xlviii

Contents_________________________________________________________________________________________________

File Upload - File Requirements

The Membership file format requirement is a standard comma delimited file (csv).

The file will need to contain 1 column with either the Card ID# or the actual Card Number.

There can be up to 3 total columns in the upload file, if the user wanted to upload pre-assigned Start and End Dates for each member record being uploaded.

The first column is required. The second column is optional and should contain the Start Date of the card’s membership in the Group. The third column is required only if the second column is used. If present, it must contain the End Date of the card’s membership in the Group’

All columns must include the headers shown below for each column that is present in the file.

CSV File Samples

Card Id only file

CardID

12345

12349

12342

12347

Card Id with Start and End Dates

CardID,StartDate,EndDate12345,10/21/2012,10/21/201312349,10/22/2012,10/22/201312342,10/23/2012,10/23/201312347,10/24/2012,10/24/2013

Card Number only file

CardNumber

123456789012345678

123456789012345679

123456789012345670

123456789012345671

Card Number with Start and End Dates

CardNumber,StartDate,EndDate123456789012345678,10/21/2012,10/21/2013123456789012345679,10/22/2012,10/22/2013123456789012345670,10/23/2012,10/23/2013123456789012345671,10/24/2012,10/24/2013

Assigning the Card Group to Module RolesEach group has the potential to be used for up to 3 (three) roles.

Reporting

_________________________________________________________________________________________________

Card Groups xlix

Contents_________________________________________________________________________________________________

For use throughout the system in searches. The default role for every group.

Marketing

Attached to one of the system tracked campaigns in Business Analytics Section

Groups attached to Campaigns may not be edited for some aspects, and may even be locked

Deleting or altering a card group that is in a campaign can have complication – please be sure any changes are valid and will not affect the campaign

Profitability

Attached to the profitability analysis area under the Business Analytics Section

Note

The system will also create new Card Groups associated with campaigns. The naming convention for the Campaign Card Group is: Cmp_”(a system assigned sequential Campaign number)”Campaign Name’ The original Card Group will not be associated with the Campaign Card Group – the system created Campaign Card Group will be associated with the Campaign’ The original Card Group will remain intact, and unchanged.

Editing an Existing Card GroupIf you need to modify the card group, its name or the filter used, enter the group detail by clicking on the group name hyperlink’ After making any necessary changes click on the “Save” button to store the changes’ Clicking “Cancel” will disregard any changes made since the last save action.

Create a New Campaign from Card Group Link

The option to create a new Campaign can be accessed from the Marketing Tab of a Card Group.

For Card Groups that are associated with an “active” Campaign, the manual membership will not allow the start and End Dates of the card to be updated’ They will be defaulted to the “beginning of time” (system minimum of 1/1/2000) and the End Date will be set to NULL. Note: the campaign builds will ensure that data is accurately generated for the correct time periods.

For non-Campaign Card Groups, the manual membership will allow edits to the Start and End Dates of cards’ However, the system will prevent more than one manual card member from being added to the Group at a time’ For example, if a manual member card has been added with a date range of 1/1/2012 to 1/31/2012 and a User updates the date range for the card to 2/1/2012 to 2/15/2012, the system will replace the original dates (1/1/2012 to 1/31/2012) with the updates entered by the User (2/1/2012 to 2/15/2012).

Note Campaigns can be complex. Please see the section on Creating New Campaigns.

Sample Card Group – Data BreachAs a reference to what can be done with a card group, the following is an example of a fraud-based card group. After hearing of a potential fraud issue or data breach, the Card360 system allows you to research and analyze your potential exposure to these external data breaches.

While each circumstance varies, here are the quick steps.

_________________________________________________________________________________________________

Card Groups l

Contents_________________________________________________________________________________________________

1. Start by building a transaction filter, which can be shared

Go to Filters

Select “NewFilter”

Name filter

Select Issuer Txn Search Type

Click Save

2. Select the Filter Items Tab

3. Add 3 filter criteria

Txn: Merchant Type = 7011(Lodging)

Txn: Merchant Name Starts with Best meaning the “Best Western”

Txn: State/Province In ‘MA’,’NH’

4. Now create Card Group using the filter

Go to New Group Wizard

Enter Data Breach as name

Provide a description

Build dates are both today’s date as it is a one-time build

Keep auto build UN-checked

Keep the Include/Remove on daily

Skip Step 2 for Existing Demographic filter unless appropriate

Skip Step 3 as well unless adding a Demographic item

On Step 4 check off the box to include transaction date with the group

Keep the pre-set “Include” located in the drop down box

On Step 5 add the Data Breach Filter that you just set up

On Step 6 define the date range of the transactions you are looking to search. This will be the period that the data breach was said to have occurred.

o Txn: Settlement Date >= 1/1/2013

o Txn: Settlement Date <= 3/1/2013

5. Finish building the group

Use the Initial Start Date as the beginning of the Data Breach Period

You are looking for anything more recent than that date, not prior to

That’s it. Once the group is built, you can begin researching your exposure to the potential data breach. The cards that had a transaction meeting the criteria will be a member of the group. You can then perform a search with the group, to research the transactions, or use the membership information to otherwise start normal fraud procedures, or to “Hot Card” and reissue those that are affected.

_________________________________________________________________________________________________

Card Groups li

Contents_________________________________________________________________________________________________

Sample Card Group – Low ActivityAs another reference to what can be done with a card group, the following is an example of a low activity card group.

Groups like this are how you segment out your lowest performing cards. By identifying them, you can use targeted strategies and campaigns to try and change the cardholder’s transaction behaviors. While each circumstance varies, here are the quick steps.

1. Create Card Group using the filter

Go to New Group Wizard

Enter Low Performers as name

Provide a description like “Card Perf 1 to 4 POS Signature Txns”

Build dates are both today’s date as it is a one-time build

Keep auto build UN-checked

Change the Include/Remove on Monthly

Skip Step2 for Adding an existing demographic filter

On Step 3 add two demographic items

o Card: BIN = 1

This means we are looking for the Low Performers in this BIN only

o Card: Card Status = A

This means we do not want to evaluate cards that are inactive

This status is a snapshot of the last demo file loaded; not historical

On Step 4 check the box off to include transaction data with this group

o Keep the drop down box on Include

Skip Step 5 as we do not need to add an existing transaction filter

On Step 6 create the following. This is our parameters for what determines a card to be low performing

o 5 Filter Items

Txn: Named Transaction = 19

Assume 19 is the code for POS SIG

Txn: Transaction Count >= 1

A count of greater than or equal to 1 transaction

Txn: Transaction Count <= 4

A count of less than or equal to 4 transactions

Txn: Settlement Date >= 01/01/2013

A settlement date of greater than or equal to 1/1/2013

Txn: Settlement Date <= 01/31/2013_________________________________________________________________________________________________

Card Groups lii

Contents_________________________________________________________________________________________________

A settlement date of less than or equal to 1/31/2013

2. Finish the remaining steps in the wizard and create the group using the earliest settlement date in your filter as the initial membership start date. 1/1/2013

Once the group is built, it is immediately available for use in the system. The general description of this group could be stated as:

This group represents cards in the month of January 2013 that are considered Low Performing POS Signature doing between 1 and 4 transactions within the month. This group only represents the Low POS SIG users from the BIN of [1] that have an active card status during the month of January 2013.

_________________________________________________________________________________________________

Card Groups liii

Contents_________________________________________________________________________________________________

Printable Cheat SheetsThe remaining pages of this document contain printable cheat sheets for the following tools, features, and/or processes:

Description of the Five Tabs Under Each Card Group

The Nine Steps to Creating a Card Group

Demographic-Based Filter Fields

Compare Functions - Demographic Filters

Transaction-Based Filter Fields

Compare Functions - Transaction Filters

Filter Codes


Auto Build

Apply Manual Members

File Upload - File Requirements

Simplifying Dates on Card Groups

_________________________________________________________________________________________________

Card Groups liv

Contents_________________________________________________________________________________________________

Description of the Five Tabs under Each Card GroupGeneral

Group Name

Group Description

Role of the group – Reporting (searching & analysis), Marketing, or Profitability

Build start date - controls when system starts building the group in the nightly processes

Build end date - controls when system stops building the group in the nightly processes

Ability to refresh the members list based on recent changes

The number of cards currently a member of the group

Ability to download a detailed list of all current members (unmask card # is avail with perm.)

Breakdown of all the members – number of cards respective of each card status when built

Member Filter

Auto Build Groups (check off for dynamic)

For a One Time Static Groups (Please leave unchecked – Most every group - Typical)

Build using “Filter” (will discuss in more detail later)

View Filter – the last used filter in creating the group

Create New Filter – design a new filter for this group built from

Associate Card (relevant for transaction searches) (not relevant in static/imported groups)

Daily – if you want members to be added to this group based on daily numbers

Monthly – if you want members added to this group based on monthly numbers

As of





Remove Association (relevant for transaction searches) (not relevant in static/imported groups)

Daily – if you want members to be removed from this group based on daily numbers

Monthly – if you want members removed from this group based on monthly numbers

As of

_________________________________________________________________________________________________

Card Groups lv

Contents_________________________________________________________________________________________________

Day Prior – is actually the day found, but since the system is not updated real time, it uses yesterday’s data, so the member technically will show as being removed from the group on the day prior.

o This is important because the cardholder may have transaction data on the last day of the month and you would want to make sure is included in any analysis.

End of Month – Removed the end of the calendar month being evaluated

End of Quarter – Removed the end of the calendar quarter being evaluated

Start of Time – Removed from the group the day it was added

o When removed membership end date will read 1/1/2000 (start of time) or the starting membership already listed this shows them as a member at some point.

Manage Members – (will discuss in more detail later) (must have permissions)

Select to be brought to the manually manage members section of the group: Use for:

o Details of group and the manual management history

o Searching the active membership list to view or delete

o Searching the manual membership list to view or delete

o Edit start and end dates for a member

o Add members to a group via a file upload using

Card ID

Card Number

Upload history to the group

Audit history on the group

Set initial start date – This is the date that the system will use to add cards to the membership of a group. It acts as the membership start date.

This will show the last “initial start date” used. (1/1/2000 is start of time in system default)

Any transactions or data before that date will NOT be returned in searches

Transactions or data that occurred on that date or all the way to the membership end date will included in search results

Group used for Marketing (Campaigns)

Tells you if card group is attached to a campaign

Group used for Profitability

Tells you if card group is used in the profitability section

And historical Auditing by date range

All entries of major changes to groups will be searchable here

_________________________________________________________________________________________________

Card Groups lvi

Contents_________________________________________________________________________________________________

The Nine Steps to Creating a Card Group1. Card Group / Build Information – basic details about the group and auto build

association/removal options

Name – to be used throughout the system

Description – to be shown on the main card groups section

Build Start Date – when system starts building group at night (Required on all – but an Auto Build item)

Build End Date – when system stops building group at night (Required on all – but an Auto Build item)

Auto Build Checkbox – for dynamic groups that you want to build every night or month (Rare)

o Leave unchecked for static groups - a typical group that never changes unless desired (Frequent)

When to add/remove card membership to the group (for auto build only)

o Daily – if you want members to be Added/Removed from this group based on the previous day

o Monthly – if you want members Added/Removed from this group based on the previous month

2. Pick Existing Demographic-Based Filters – select pre-existing filters based on transaction elements for the group

Any existing filter created for another card group or created under System » Setup » Filters will be available for use. You can also create filters on the next step to use in multiple groups based on cardholder, card, or account data elements (Demographics)


3. Create New Demographic-Based Filters – to create a “New Filter” only based on demographic elements

If you don’t have an existing demographic filter to use then this is the step where you will create one.

If you DO NOT need to create a new filter based on demographics, move on to the next step

4. Selecting To Use Transaction Data – decide to use or not use transactions to help define the group

First select if you want transactions to be a part of the group criteria or filters

i. Such as more than “x” transactions in a month

Decide to have your transaction setup be the basis for either including or excluding members from group

If the transaction option is selected then the proceed to step 5 and 6

o Note: Once selected, at least one item is required from step 5 or 6, but not both. _________________________________________________________________________________________________

Card Groups lvii

Contents_________________________________________________________________________________________________

o Users may include both existing and new filters to a group setup

Caution: The more you add, the smaller the membership – The system is looking for all criteria to be true. You can’t have something be “equal to less than 4” and at the same time be “equal to greater than 6”

If this option is NOT selected then proceeds to step 7

5. Pick Existing Transaction-Based Filters – select pre-existing filters based on transaction elements for the group

Any existing filter created for another card group or created under System » Setup » Filters will be available for use. You can also create filters on the next step to use in multiple groups based on transaction data elements (Transactions) like Transaction Type, Merchant Name, and much more.


6. Create New Transaction-Based Filters – to create a “New Filter” only based on transaction elements

If you don’t have an existing transaction filter to use, then this is the step where you will create one

If you DO NOT need to create a new filter based on demographics, move on to the next step


In the wizard, the system will display a summary of all selections that will define this group

If manually creating, review the information and filters you have selected before building

8. Enter Start date for use as members start date in the group

Tell the system to build the group

o In the wizard select “Finish” after entering the initial start date for members

o When manually creating you must use the member filter tab to enter date and select “Build”


_________________________________________________________________________________________________

Card Groups lviii

Contents_________________________________________________________________________________________________

Demographic-Based Filter FieldsN.H. = No “Help” is available.


U.D. = User-Defined


NoteMost demographic items have NO “Help”

Branch ID, BIN #’s, Card Status, Card Group ID, and Phone Type are the only demographic-based fields with “Help”

Demographics typically require a specific response that is particular to 1(one) account, card, or customer. The manner of your data feed determines the correct responses.

Descriptions below are not necessarily correct responses

Account

Account: Account Number (N.H. - U.D.) - Enter a specific account number(s)

Account: Account Type (N.H. - U.D.) - Enter the specific account type; DDA, Checking, Etc.

Account: Address Type (N.H. - U.D.) - Enter a specific type; Home = H, Business = B, Etc.

Account: Branch ID - Branches are related to a Branch ID; pick code from list OR manually enter code

Account: City (N.H. - U.D.) - Looking for the city the account was opened in

Account: Open Date (N.H. - U.D.) - Looking for the date the account was opened ( mm/dd/yyyy)

Account: Primary Holder? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

Account: State (N.H. - U.D.) - The state code or spelt out; however system shows the data set

Account: Zip (N.H. - U.D.) – The 5 digit zip or with 4 additional dash or no dash; however the data shows

Card

Card: Accept International? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

Card: Activation Date (N.H. - U.D.) - Looking for the activation date of the card ( mm/dd/yyyy)

Card: Allow Overdrafts? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

Card: Annual Fee (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

Card: BIN – BIN numbers are related to a BIN ID; pick code from list OR manually enter correct code

_________________________________________________________________________________________________

Card Groups lix

Contents_________________________________________________________________________________________________

Card: Card ID (N.H. - U.D.) – Looking for a specific Card ID that is unique to each card in system

Card: Card Number (N.H. - U.D.) - Looking for a specific Card number; typically no dashes

Card: Card Status - Each system card status has a corresponding code ex. [CODE], [A] or [Active], etc.

Card: Expiration Date (N.H. - U.D.) - Looking for the expiration date of the card ( mm/dd/yyyy)

Card: Hot Date (N.H. - U.D.) - Looking for the hot card date of the card ( mm/dd/yyyy)

Card: Institution (N.H. - U.D.) – Looking for a specific Institution

Card: Issue Date (N.H. - U.D.) - Looking for the issue date of the card ( mm/dd/yyyy)

Card: Last Used (N.H. - U.D.) - Looking for the date the card was last used ( mm/dd/yyyy)

Card: Reward Status (N.H. - U.D.) – Looking for specific entry based on data feed value

Card Group


Cardholder

Cardholder: Address Type (N.H. - U.D.) - Enter a specific type; Home = H, Business = B, Etc.

Cardholder: Birthdate (N.H. - U.D.) - Looking for the cardholder’s birthdate ( mm/dd/yyyy)

Cardholder: Cardholder Type (N.H. - U.D.) - Enter a specific type; Consumer = C, Business = B, Etc.

Cardholder: City (N.H. - U.D.) - Looking for the city the cardholder lives in based on current system address

Cardholder: Gender (N.H. - U.D.) – Looking for Male [M], Female [F], or however the data is shown

Cardholder: State (N.H. - U.D.) - The state code or spelled out; however system shows the data set

Cardholder: Zip (N.H. - U.D.) - The 5 digit zip or with 4 additional dash or no dash; however the data shows

Customer

Customer: Phone Number (N.H. - U.D.) - Looking for customer phone # however shown; dash or no dash

Customer: Phone Type - Enter a specific type; Home = H, Business = B, Office = O, Etc.

Institution

Institution: Processor Key - Enter the processor key value for the FI.

Note Demographic data is a snapshot in time — as of the last demo file upload.

_________________________________________________________________________________________________

Card Groups lx

Contents_________________________________________________________________________________________________

Compare Functions - Demographic Filters


= (Equals)


Cardholder State: = MA; or Cardholder State: = Massachusetts

Find me all the cardholders with their state equals to Massachusetts

>(Greater than)


Card: Issue Date > 01/01/2013

Find me all the cards that have an issue date later than January 1, 2013

<(Less than)


Card: Issue Date < 12/31/2010

Find me all the cards that have an issue date earlier than December 31, 2010

Is null(Is empty)


Card: Activation Date Is null

Find me all cards that have no date in the activation date field

In(Is part of)


Cardholder State: = MA,NH; or Cardholder State: = Massachusetts, New Hampshire

Find me all the cardholders in Massachusetts or New Hampshire


Customer: Phone Number Starts with 617

Find me all the customers with phone numbers in the (617) area code


Card: Card Number Ends with 5469

Find me the card number(s) that end in 5469


Card: Reward Status Contains VIP

Find me all the cards that contain VIP in the reward status field

_________________________________________________________________________________________________

Card Groups lxi

Contents_________________________________________________________________________________________________




Card: Expiration Date >= 12/31/2010

Find me all cards that have an expiration of at least Dec. 31, 2010 or later



Card: Hot Date <= 01/01/2013

Find me all cards with a hot date of Jan. 1, 2013 or earlier


Cardholder: Address Type Not equal to Business

Find me all the cardholders with an address not classified as a business address



Card: Activation Date Is not null

Find me all cards that have at least some value entered in the activation date field



Card: BIN Is not in 1111,2222,3333,4444

Find me all other cards that are NOT from the BINS of 1111, 2222, 3333, or 4444


Account: Account Number Does not start with 0

Find me all accounts that do not start with the number 0 (zero)


Account: Account Number Does not end with a 9

Find me all accounts that do not end with the number 9 (nine)


Card: Allow Overdrafts? Does not contain N

Find me all the cards that allow overdrafts; or have any other response except “N”

_________________________________________________________________________________________________

Card Groups lxii

Contents_________________________________________________________________________________________________

Transaction-Based Filter FieldsN.H. = No “Help” is available.


U.D. = User-Defined


Note Most transaction items have NO “Help”

Transactions typically require a specific response that is particular to 1(one) transaction or group of transactions. The manner of your data feed determines the correct responses.

Descriptions below are not necessarily correct responses

Card Group


Transaction

Txn: Amount (by group) (N.H. - U.D.) – The total transaction amount from the group

Txn: Amount Completed (N.H. - U.D.) – The total settled transaction Amount/Spend/Purchases

Txn: Amount Requested (N.H. - U.D.) – The total requested transaction Amount/Spend/Purchases

Txn: Base Transaction? (N.H. - U.D.) - Looking for Base=Yes[Y] or No [N]= Custom; PIN, SIG are base

Txn: Card Entry Method – Select from the system defined methods of entry; present, swipe, phone, etc.

Txn: Card ID (N.H. - U.D.) - Looking for a specific Card ID that is unique to each card in system

Txn: Cash Back Amount (N.H. - U.D.) – The total amount of cash back associated with a transaction(s)

Txn: City (N.H. - U.D.) - Looking for the city the transaction took place in

Txn: Country (N.H. - U.D.) - Looking for the Country the transaction took place in

Txn: Exception Amount (N.H. - U.D.) – The total exception amount attached to a transaction

Txn: Exception Fee (N.H. - U.D.) – The total exception fee attached to a transaction

Txn: Fraud Score (N.H. - U.D.) – The fraud score or range that is attached to a transaction(s)

Txn: International? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically - The International Txn Flag

_________________________________________________________________________________________________

Card Groups lxiii

Contents_________________________________________________________________________________________________

Txn: Issuer Network – Pick from a system defined issuer network list; the network attached to transaction

Txn: MCC Fraud Score (N.H. - U.D.) - The MCC Fraud Score or range that is attached to a transaction(s)

Txn: Merchant ID (N.H. - U.D.) - The Merchant ID or range that is attached to a transaction(s)

Txn: Merchant Name (N.H. - U.D.) - The Merchant Name that is attached to a transaction(s); BestBuy

Txn: Merchant Type - The associated merchant category code type that is attached to a transaction(s); Gas

Txn: Message Type - The message type that is attached to a transaction(s)

Txn: Month (N.H. - U.D.) - Looking for the Month that the transaction took place in

Txn: Named Transaction – Is where all of your “Base” transactions exist; POS PIN, POS SIG

Txn: Network - Looking for the Network that the transaction took place on

Txn: On Premise? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

Txn: Our Terminal? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

Txn: PIN Present? (N.H. - U.D.) - Looking for Yes[Y] or No [N] typically

Txn: POS Condition Code – Pick from the system POS Condition Codes that may be on a transaction(s)

Txn: Postal Code (N.H. - U.D.) - The 5 digit zip or with 4 additional dash or no dash; however the data shows

Txn: Processing Country (N.H. - U.D.) - Looking for the Country where the processing took place in

Txn: Quarter (N.H. - U.D.) - Looking for the calendar quarter that the transaction took place in

Txn: Response Code - Pick from the system Response Codes that may be on a transaction(s)

Txn: Response Reason- Pick from the system Response Reasons that may be on a transaction(s)

Txn: RTD Rule - Pick from the system RTD Rule Codes that may be on a transaction(s)

Txn: Settlement Date (N.H. - U.D.) - Looking for the settlement date that the transaction took place on

Txn: State/Province (N.H. - U.D.) - Looking for the State that the transaction took place in

Txn: Surcharge (N.H. - U.D.) - The total Surcharge amount attached to transaction(s)

Txn: Surcharge (by group) (N.H. - U.D.) - The total Surcharge amount by group attached to transaction(s)

Txn: Surcharge Count (N.H. - U.D.) - The total Surcharge count attached to transaction(s)

Txn: Switch Date/Time (N.H. - U.D.) – The date/time stamp that the transaction hit the processing switch

_________________________________________________________________________________________________

Card Groups lxiv

Contents_________________________________________________________________________________________________

Txn: Terminal Date/Time (N.H. - U.D.) - The date/time stamp that the transaction was sent through terminal

Txn: Terminal ID (N.H. - U.D.) – The merchant terminal id or ATM terminal id that is attached to transaction(s)

Txn: Transaction Code – The associated transaction code on the transaction detail

Txn: Transaction Count (N.H. - U.D.) - The total count of all transactions; by type, by card, by group

Txn: VAA Condition Code - The VAA Condition Code or range that is attached to a transaction(s)

Txn: VAA Reason Code - The VAA Reason Code or range that is attached to a transaction(s)

Txn: VAA Risk Score (N.H. - U.D.) - The VAA Risk Score or range that is attached to a transaction(s)

Txn: Year (N.H. - U.D.) - Looking for the Year that the transaction took place in

Note

Transaction data is time dependent.

Most every transaction-based filter should be accompanied by a “Date Range Selection” that typically uses “Settlement Date” greater than or equal to (>= ‘X’ Date) and less than or equal to (<= ‘X’ Date).

_________________________________________________________________________________________________

Card Groups lxv

Contents_________________________________________________________________________________________________

Compare Functions - Transaction Filters


= (Equals)


Txn: Merchant Name: = BestBuy, or Best Buy

Find me all the transactions from BestBuy or Best Buy or BB Store 29

>(Greater than)


Txn: Settlement Date > 01/01/2013

Find me all transactions that have a settlement date later than January 1, 2013

<(Less than)


Txn: Switch Date < 12/31/2010

Find me all the transactions that have a switch date earlier than December 31, 2010

Is null(Is empty)


Txn: Postal Code Is null

Find me all the transactions that have no zip code in the transaction

In(Is part of)


Txn: State/Province = MA,NH; or Txn: State/Province = Massachusetts, New Hampshire

Find me all the transactions in Massachusetts or New Hampshire


Txn: Merchant Name starts with Best

Find me all the transactions that have a merchant name beginning with “Best”.


Txn: Merchant Name ends with Buy

Find me all the transactions that have a merchant name ending with “Buy”

_________________________________________________________________________________________________

Card Groups lxvi

Contents_________________________________________________________________________________________________



Txn: Merchant Name contains Bath

Find me all the transactions that have a merchant name containing “Bath”



Txn: Terminal Date >= 12/31/2010

Find me all the transactions with a terminal date of at least Dec. 31, 2010 or later



Txn: Terminal Date <= 01/01/2013

Find me all the transactions with a terminal date of Jan. 1, 2013 or earlier


Txn: Amount Completed Not equal to 100

Find me all the transactions with a completed transaction amount NOT equal to $100



Txn: Card Entry Method Is not null

Find me all the transactions where the card entry method field has at least some entry



Txn: State/Province Is not in Massachusetts

Find me all the transactions that did NOT occur in Massachusetts


Txn: Merchant Name Does not start with W

Find me all transactions with a merchant name that does not begin with a W

_________________________________________________________________________________________________

Card Groups lxvii

Contents_________________________________________________________________________________________________



Txn: Merchant Name Does not end with a S

Find me all transactions with a merchant name that does not end with an S


Txn: Merchant Name Does not contain 0,1,2,3,4,5,6,7,8,9

Find me all transactions with a merchant name that does contain numbers

_________________________________________________________________________________________________

Card Groups lxviii

Contents_________________________________________________________________________________________________

Filter CodesThere are several codes that can be used for calculations within filters. These filters include:















[Today] – 5 If today’s date is May 7th, 2007, the expression [TODAY]-5 would return a value of 5/2/2007


_________________________________________________________________________________________________

Card Groups lxix

Contents_________________________________________________________________________________________________

Two Special Circumstances: And/Or and EXPCreating multiple filter parts requires the user to select how the different parts will interact with each other. This drastically changes the ending filter and group. As soon as you add a second filter item, you will see a new drop down box appear. This is where users will select AND/OR. With more than 2 parts, it’s recommended to use AND for all parts, or vice-versa. Mixing the two types in the same filter should be avoided unless specifically trained.

And/Or - The default will be AND, and you must either keep it, or select OR.

AND






OR






In some situations, you may need to create a dynamic filter that uses a formula to define their logic, and get a result. For example, if you wanted to make a filter to find somebody’s AGE, then the filter item must specify how to calculate that using the “Cardholder: Birthdate” demographic field. The way you enter it and the compare functions you select, can change results. See below

EXP – Expression or Formula Tells the system to calculate whatever has been entered into the “To” field

Example

[Today] – 5

If today’s date is May 7th, 2007, the expression [TODAY]-5 would return a value of 5/2/2007


Other filter codes shown below

_________________________________________________________________________________________________

Card Groups lxx

Contents_________________________________________________________________________________________________

Auto BuildIn the top left corner of the Member Filter tab there is the checkbox for Auto Build. This is defaulted to be off as the system standard practice is build one-time static groups. Dynamic groups that build as part of the nightly import process, are used in specific situations, are rarer, and are typically for only advanced users.

Please be cautious to only use auto build if you are absolutely sure it is needed. Unwanted or unused groups that are accidentally set with auto build enabled, creates an unnecessary drain on the system’s resources; via nightly imports

Remember, once you enable auto build, it is crucial that you manage all the settings for auto build. These settings are:

Your Build Start and End Dates (on the General Tab)

This is where you essentially schedule (Start Date) a task in the system, to have the group be built every night as part of the nightly import process. This is a recurring event until it reaches the End Date

A “Card Group Build” process will be performed every night following the transaction import processing from the previous day

o Build Dates must be at least today, and the ending date can’t be earlier than starting date

The group will be re-built as every night, without fail, until you instruct it to stop (End Date)

Association settings – How are people added and removed from the group? (Member Filter Tab)

Associate Card – essentially it is the date that members are given as they are ACTIVATED into the group

Time period to use in qualifying cards against your filters

o Daily – Look at yesterday’s transactions and demographics to tell me what’s changed

o Monthly – Look at monthly transaction totals and demographics to tell me what’s changed

“As of” assessment - tells the system how the Start Date for each new (or re-joining member) will be determined. Pay attention, this affects transaction search results when using card group.

o Day Found – Adds the card as a member from the day it meets the group criteria

o Start of Month – Adds from the beginning of the month it is found

o Start of Quarter – Adds from the beginning of the calendar quarter it is found

o Start of time – Adds from the beginning of the system time (default 01/1/2000)

Remove Association– essentially it is the date that members are given as they are EXPIRED from group

Time period to use in qualifying cards against your filters _________________________________________________________________________________________________

Card Groups lxxi

Contents_________________________________________________________________________________________________

o Daily – Look at yesterday’s transactions and demographics to tell me what’s changed

o Monthly – Look at monthly transaction totals and demographics to tell me what’s changed

“As of” assessment - tells the system how the End Date for each current (and former) members are going to be determined. Pay attention, this affects transaction search results when using card group.

o Day Prior – Members are expired from group; day prior is the end date (expiration date)

o End of Month – Removes from end of the month it is found; expires last day of month

o End of Quarter – Removes from end of the calendar quarter; expires end of quarter

o Start of time – Removes using the beginning of the system time (default 01/1/2000) or start of time in the membership details

Allows you to see that a card was a member of the group, but with Identical Dates for Start and End Dates, the system sees the member as inactive

Note These must be set when auto build is enabled.

_________________________________________________________________________________________________

Card Groups lxxii

Contents_________________________________________________________________________________________________

Apply Manual MembersAll manual changes to groups, must be applied to the group in order to complete the process.

Method 1

The confirmation screens following a successful upload will provide three options for the user to choose. You may apply manual member changes through one of these options, or through the Member Management section on the general tab.

Accept and upload a file – You proceed, but you have NOT applied changes, they are pending

This adds the successful contents of your file to the pending manual membership change table

There it will remain until one of two options occur

o The user applies the membership changes manually

o The system will automatically apply the changes during the overnight processing

Accept and apply manual members – You’re done. Everything is applied. Ready to use.

No further action is required. Your group is ready to use for any task

Cancel my upload – I changed my mind and do not want to upload this file. Cancel everything.

If something doesn’t look right, or you are unsure, it is better to cancel and not have to fix later. Be sure

Method 2

You may also add your group changes through the “Apply Manual Member” link. This is located on the General Tab of your group’s Member Management detail.

If the User has not chosen any of the options under Method 1, and then navigates away from the page or times out for inactivity, the upload process will remain in Pending status and the three options will cease to be available. The previous process will remain in pending state and the member file will need to be uploaded again.

_________________________________________________________________________________________________

Card Groups lxxiii

Contents_________________________________________________________________________________________________

File Upload - File RequirementsThe Membership file format requirement is a standard comma delimited file (csv).

The file will need to contain 1 column with either the Card ID# or the actual Card Number.

There can be up to 3 total columns in the upload file, if the user wanted to upload pre-assigned Start and End Dates for each member record being uploaded.

The first column is required. The second column is optional and should contain the Start Date of the card’s membership in the Group. The third column is required only if the second column is used. If present, it must contain the End Date of the card’s membership in the Group’

All columns must include the headers shown below for each column that is present in the file.

CSV File Samples

Card Id only file

CardID

12345

12349

12342

12347

Card Id with Start and End Dates

CardID,StartDate,EndDate12345,10/21/2012,10/21/201312349,10/22/2012,10/22/201312342,10/23/2012,10/23/201312347,10/24/2012,10/24/2013

Card Number only file

CardNumber

123456789012345678

123456789012345679

123456789012345670

123456789012345671

Card Number with Start and End Dates

CardNumber,StartDate,EndDate123456789012345678,10/21/2012,10/21/2013123456789012345679,10/22/2012,10/22/2013123456789012345670,10/23/2012,10/23/2013123456789012345671,10/24/2012,10/24/2013

_________________________________________________________________________________________________

Card Groups lxxiv

Contents_________________________________________________________________________________________________

Simplifying Dates on Card GroupsThe dates can be confusing when discussing card groups, so before we get into detailed descriptions of everything card group related, let’s take a moment to try and simplify our thinking around card group dates.

Note

There are essentially only 3 (three) dates in card groups that have any bearing”

Actual Build Date


Membership End Date

Manual-Builds – I clicked the “build” button in the UI

Example :

If today is 01/01/2013 and I press “build” – then the actual build date is 01/01/2013

You can’t control the date in any way, it is just today’s date

The actual build date is just the date in the system on the day the group builds or re-builds.

Auto-Builds – I told the system “start building the group on this date” and “don’t stop building until this future date”

Example :

Today is 2/1/2013, and you enter; “Build Start Date” of 2/15/2013, “Build End Date” of 2/28/2013

o The actual build date will show as “none” until 2/15/2013,

o The system will auto build the group that day, and the actual build date will now show 2/15/2013

o Every day after that, the actual build date will be updated after the auto build to show the next date

2/16, 2/17, 2/18, etc. until it hits 2/28/2013 and then the system will STOP auto building

o It will show 2/28/2013 forever, or until one of two things occurs

Auto build dates are changed or

A manual build is performed.

Actual build date is just the day that you told the system, to go look at all the records, and bring back the cards #’s

When the group is built, each member will receive a one line entry, or row, in the membership list. When they are added to the group, the system pulls in various details about each member like card ID, card number, name, address, city, state, etc. These are added as columns in the membership list. So each member has one row with all this data available to you.

_________________________________________________________________________________________________

Card Groups lxxv

Contents_________________________________________________________________________________________________

Below is a modified sample, of a card group membership list.

Two of the columns in the membership list, will hold the dates that the each member was added / removed from the group.

These dates are critical to:

Getting results when you use the card group in a transaction search

Look at the first member listed (John Smith)

o If you did a transaction search for 3/1/2013 you would not get any results from this member because they are no longer a member of the group as of 1/1/2013

The total count of members currently in the group

This is a group of 1 (Jane Doe) because the first listing has been expired from the group

Note

Recurring Members

If John Smith re-joined the group at a later date, he would receive a brand new row in the membership list with a new start date and an empty end date. Dynamic groups will hold a running tally of members over time. Manual builds delete the list.

Membership Start and End Dates are determined by 3 (three) methods only.

By the Manual Build process


o Whatever you enter for the “initial start date”

Membership End Date

o Always empty; unless you manually manage in some form

By the Auto Build process


o “Associate Card” – are we adding cards to the group based on monthly or daily

o “As-of” – once system finds a new member this determines what date will be entered as the membership start date

Membership End Date

_________________________________________________________________________________________________

Card Groups lxxvi

Contents_________________________________________________________________________________________________

o “Remove Association” – are we removing cards to the group based on monthly or daily

o “As-of” – once system determines a member should be removed, this determines what date will be entered for the membership end date

By the Manually Managing Membership via file upload or edit; dates are ignored when it is in campaign

Note You are responsible for telling the system how to determine the dates.

_________________________________________________________________________________________________

Card Groups lxxvii

Contents_________________________________________________________________________________________________

Saylent Contact InformationFor more information on any of the information contained in this document, please contact Saylent at:

Phone: (508) 570-2161

Email: [email protected]

Mail: Saylent

122 Grove Street, Suite 300

Franklin, MA 02038

_________________________________________________________________________________________________

Card Groups lxxviii

mailto:[email protected]

Card Groups - Zendesk · Web view- the number of cards removed from the upload because the...

Documents

Transcript of Card Groups - Zendesk · Web view- the number of cards removed from the upload because the...