SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and...

45
SHAZAM Core Services Managing Cards Through the Real-Time Interface 2019 Compass XD™ CONFIDENTIAL – For Client Use Only Last Modified 9/3/19

Transcript of SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and...

Page 1: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

SHAZAM Core Services Managing Cards Through the Real-Time Interface 2019

Compass XD™ CONFIDENTIAL – For Client Use Only

Last Modified 9/3/19

Page 2: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation ii ©2019 ITS, Inc. All Rights Reserved

Revision/Approval History

Date Description Author

3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser 6/28/19 Update for RTI Release Lanisha Lomax 7/1/19 Approval from IP Counsel Lanisha Lomax 9/3/19 Removed reference to Instant Issue Lanisha Lomax 9/4/19 Approval from IP Counsel Lanisha Lomax

Page 3: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation iii ©2019 ITS, Inc. All Rights Reserved

Table of Contents Revision/Approval History ................................................................................................................. ii

Preface ............................................................................................................................................. vi

Purpose of Document ........................................................................................................................ vi

Who Should Read This Document ..................................................................................................... vi

Printing This Document...................................................................................................................... vi

Trademark Attributions ..................................................................................................................... vi

Before Beginning ...............................................................................................................................7

Prerequisite Knowledge ...................................................................................................................... 7

System Prerequisites ........................................................................................................................... 7

Roles of the SHAZAM Core UI and SHAZAM Access ........................................................................... 7

Become Familiar with Essential Concepts .......................................................................................... 7

User Access to Card-Management Features....................................................................................... 8

Understand BIN-Level Parameters and Determine Policies for Customizing Them ........................... 9

Card Embossing Restrictions ................................................................................................................. 9

Withdrawal and Deposit Limits ........................................................................................................... 10

Extended Processing ........................................................................................................................... 10

Waivable Service Charges for Card Orders ......................................................................................... 10

Where to Go Next ............................................................................................................................. 10

Placing Card Orders .......................................................................................................................... 11

Adding a New Card............................................................................................................................ 11

Adding another Cardholder to an Existing Card Number ................................................................. 14

Editing and Deleting Secondary Cardholders...................................................................................... 14

Reissuing Cards That Are About to Expire ........................................................................................ 14

Reordering a Card ............................................................................................................................. 15

Cancelling a Pending Card Order ...................................................................................................... 17

Instructions for Updating, Restricting, or Deleting Existing Cards ......................................................... 18

Before Beginning ............................................................................................................................... 18

Locating a Cardholder ....................................................................................................................... 18

Verifying and Editing Cardholder Contact Information .................................................................... 19

Page 4: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation iv ©2019 ITS, Inc. All Rights Reserved

Customizing the Withdrawal Limits for a Card ................................................................................. 20

Restricting All Card Activity (Hot Carding) ........................................................................................ 20

Temporarily Restricting Certain Card Activities ................................................................................ 21

Removing Temporary Restrictions ...................................................................................................... 22

Enabling Balance Round-Up .............................................................................................................. 22

Disabling Balance Round-Up ............................................................................................................... 23

Deleting a Card .................................................................................................................................. 23

Viewing the Status of Card Maintenance Actions .............................................................................. 24

Retrieving SHAZAM EFT Reports ....................................................................................................... 24

Researching Maintenance Questions ............................................................................................... 25

Viewing Past Transactions ................................................................................................................ 27

Reference: User Interface for the Card Management Tab ................................................................. 28

Fields on the Card Management Tab .................................................................................................. 29

List of Customer’s Cards.................................................................................................................... 29

Accounts Associated with the Selected Card .................................................................................... 29

Plastics and Card Authorization File (CAF) Settings .......................................................................... 30

Reference: Fields on the Card Management Edit Dialog Box ............................................................. 32

Card Information Section .................................................................................................................. 32

Contact Information Section ............................................................................................................. 32

Differences between Card Contact Information and CIS Profiles .................................................. 33

Reference: Fields on the Additional Name Form Dialog Box ........................................................... 34

PAN Restrictions Section ................................................................................................................... 35

Withdrawal Limits Section ................................................................................................................ 36

Deposit Account 1 (Primary) and Deposit Account 2-4 Sections ...................................................... 36

Savings Account 1 (Primary) and Savings Account 2 through 4 Sections ......................................... 37

Reference: Withdrawal Limits Dialog Box......................................................................................... 39

Reference: Extended Processing Edit Form ....................................................................................... 40

Roundup Feature .............................................................................................................................. 40

Example ............................................................................................................................................... 40

Additional Features ........................................................................................................................... 41

Appendix A: List of BIN-Level Parameters in Compass Rocket® LegaSuite® ......................................... 42

Page 5: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation v ©2019 ITS, Inc. All Rights Reserved

List of BIN Parameters ...................................................................................................................... 42

Appendix B: List of Restriction Codes ............................................................................................... 45

PAN Restriction Codes ...................................................................................................................... 45

Deposit and Savings Account Restriction Codes ............................................................................... 45

Page 6: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation vi ©2019 ITS, Inc. All Rights Reserved

Preface

Purpose of Document This document provides the following types of information:

• Step-by-step instructions for ordering and maintaining cards on the Card Management tab. • Explanations of features for researching card-related issues. • Descriptions of each configurable field.

Who Should Read This Document • Compass XD™ Users • SHAZAM Core Services Personnel

Printing This Document This document has been formatted for double-sided printing. If the reader chooses to print using a single sided print option, this document will produce blank pages in the introduction sections. This document is confidential and shall not be provided to any third-party without the express written permission of ITS, Inc.

Trademark Attributions The following trademarks are referenced in this document:

• ITS, Inc. has registered trademarks at the United States Patent and Trademark Office which include SHAZAM®, the SHAZAM logo and myPic Studio®.

• Compass XD™ is a trademark of ITS, Inc. • IBM® iSeries™, IBM iSeries Access™ for Windows®, IBM iAccess Client Solutions™ for Windows®,

IBM iAccess Client Express™ for Windows®, iSeries Operation Navigator™, and AS/400 NetServer™ are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.

• Mastercard® is a registered trademark of Mastercard International Incorporated. • Microsoft®, Windows®, Windows NT®, and Microsoft® Word™ are trademarks of Microsoft

Corporation, registered in the United States, other countries, or both. • Java® is a registered trademark of Oracle and/or its affiliates. Other names may be trademarks of

their respective owners, registered in the United States, other countries, or both. • Seagull Software® and J Walk® are trademarks of Rocket Software, Inc., registered in the United

States, other countries, or both. • Visa® is a trademark owned by Visa International Service Association and used under license.

Page 7: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 7 ©2019 ITS, Inc. All Rights Reserved.

Before Beginning

Prerequisite Knowledge This document assumes that users have knowledge about basic functionality of the SHAZAM Core user interface (UI), including logging in, navigating between pages and tabs, editing fields, and so on. In other words, this document does not teach UI fundamentals.

System Prerequisites The real-time interface requires that the following characteristics be true for the financial institution (FI) and its SHAZAM Core system:

• EFT Services: o Is enrolled in SHAZAM plastics or has plastics on file with SHAZAM. o Uses a cut-off time of 6:00 p.m. CT. o Does not participate in SHAZAM myPic Studio®.

• SHAZAM Core:

o SHAZAM Core runs in the SHAZAM Core Data Center rather than on an on-site machine. o Appropriate FI employees have SHAZAM Core accounts. Those accounts have the

appropriate permissions, groups, and/or roles administered to them through the Admin Console feature in the UI.

o The FI’s BINs and their parameters are defined in SHAZAM Access and SHAZAM Core, including default limits, restrictions, fees, and so on.

Roles of the SHAZAM Core UI and SHAZAM Access The SHAZAM Core UI serves as the primary interface for managing cards. FI employees should typically limit card-management activity on the Cards tab in SHAZAM Access to read-only actions.

Become Familiar with Essential Concepts The following concepts are essential for understanding how SHAZAM Core interacts with SHAZAM authorization and card services.

• Bank Identification Number (BIN)—A unique 6-8-digit number that identifies the card type in transaction processing.

• BIN Code—A three-character, FI-defined name that groups a BIN with the parameters that define how the system treats cards with that BIN code. BIN codes are a user-friendly way for users to identify card types in the SHAZAM Core UI. For example, a BIN code of MCB might identify a type of Mastercard®-issued card with basic withdrawal limits, while MCV might identify a card with VIP limits.

Page 8: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 8 ©2019 ITS, Inc. All Rights Reserved

• Primary Account Number (PAN)—A unique number for each card that identifies the issuer financial institution and cardholder. Also known as a Customer Card Number (CCN). Each PAN can have multiple physical cards associated with it. Card-authorization parameters, such as withdrawal limits, are set on PANs and apply to all cards with that PAN.

• Card Authorization File (CAF)—A file maintained within the card authorization service on behalf of the FI that includes a record for each PAN and its parameters.

• Real-time authorization and transaction posting—SHAZAM Core performs the following actions in real time:

o The CAS authorizes or denies transactions according to the available balances of accounts in SHAZAM Core.

o SHAZAM Core receives and posts transactions to customer accounts. In both cases, “real time” means that the latest balances in SHAZAM Core are immediately available to the authorization service. Similarly, debits and credits immediately post to accounts.

• Real-Time Interface—The SHAZAM service that provides authorization of EFT transactions for card issuers. This service authorizes transactions using real-time available balance information from SHAZAM Core.

• Positive balance file—A file maintained within the CAS system on behalf of each FI. The file contains a record of balances for the accounts associated with each CAF record. The CAS system checks the positive file before it authorizes a transaction.

User Access to Card-Management Features The FI may want to restrict some users from performing certain card-management tasks. For example, users may want to allow customer support employees to reorder existing cards to replace broken cards, but users may not want them to open new cards. The ability to enable or disable a user’s ability to perform specific actions is referred to as setting the user’s permissions. This training document explains when performing a card-management task requires the user to have a particular permission enabled.

Note: A BIN can belong to multiple BIN codes if users want the system to treat cards with that BIN in different ways. Continuing the previous example of MCB and MCV, both BIN codes can correspond to

the same BIN if desired.

Note: Specific users at the FI set permissions through the Admin Console feature in Compass XD. For comprehensive documentation about the Admin Console functionality, refer to the

Compass XD – Admin Console Guide

Page 9: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 9 ©2019 ITS, Inc. All Rights Reserved

Understand BIN-Level Parameters and Determine Policies for Customizing Them Each new PAN inherits the default parameter values set for its BIN code. Some parameters reside at the BIN level and can be maintained only in Compass XD. However, users can customize the PAN-level values inherited from several of those parameters. Read the following sections to become familiar with these parameters and determine the FI’s policies for customizing them.

Card Embossing Restrictions Card vendors can emboss a limited number of characters on cards, users may want to develop guidelines for adapting names to fit within the limitations. Be aware of the following limitations when entering cardholder information:

• Length: When entering cardholders’ first and last names, middle initial, and title/salutation, the maximum length is one of the following values. Note that spaces, backslashes, and periods count as characters.

Brand Business/Consumer Chip Max Name Length Mastercard® Consumer No 21 Mastercard Business No 26 Mastercard Consumer Yes 19 Mastercard Business Yes 19 Visa® Consumer No 26 Visa Business No 26 Visa Consumer Yes 26 Visa Business Yes 26 ATM N/A No 26 ATM N/A Yes 26

• Special Characters: o For name fields, only uppercase and lowercase letters and periods (.) are supported. o For second-line/business embossing, all alphanumeric characters (A-Z and 0-9) and the

following characters are allowed: &, /, ‘, commas (,), and periods (.). • Second Line Embossing: This feature must be enabled at the BIN level in Compass XD

parameters.

If users violate these limitations, the SHAZAM Core UI might seem to apply the changes but fail to apply them and return an error in the card-processing log or reports.

Note: For a complete list of parameters maintainable in Compass XD, refer to Parameter Maintenance documentation located on the SHAZAM Client Login.

Page 10: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 10 ©2019 ITS, Inc. All Rights Reserved

Withdrawal and Deposit Limits Users can set several types of limits on the amounts of money a customer can withdraw via a card as well as the amounts they can withdraw after an unverified deposit or transfer. The FI sets default limits for each BIN but can customize the limits for a given PAN.

For detailed descriptions of each type of limit that applies to cards, refer to the Reference: Withdrawal Limits Dialog Box section. The system resets the amounts it counts toward limits each day at 12:00 AM.

Extended Processing Extended processing refers to operations that SHAZAM Core performs on transactions a customer performs. For example, the balance round-up operation rounds up debits made with the card and transfers rounded-up amounts to a particular account. Users may enable or disable a processing operation for a given PAN.

Waivable Service Charges for Card Orders SHAZAM Core can assess cardholders a fee when a card is ordered for them. The system will apply the charge to a deposit account assigned to the card, or, if no deposit account is assigned, a savings account. Users may choose to waive the charge on a customer-by-customer basis when reordering a card or the FI can also choose to disable all card-order charges. The fee amount and other parameters, such as transaction codes and the FI’s G/L account to credit with the fee, are set at the BIN level.

Where to Go Next The remainder of this document contains three major types of information:

• Step-by-step procedures for placing different types of card orders. • Step-by-step procedures for performing ongoing maintenance on cards. • Descriptions of fields that appear on card-related pages and dialog boxes in the UI.

Page 11: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 11 ©2019 ITS, Inc. All Rights Reserved

Placing Card Orders The SHAZAM Core UI provides features for performing the following card-order tasks. For step-by-step instructions for a particular task, select the link.

• Adding a New Card • Adding Another Cardholder to an Existing Card Number • Reissuing Cards That Are About to Expire • Reordering Cards

Adding a New Card Complete the following steps to add a new PAN and cards to the FI’s SHAZAM Core system for an existing customer. By adding a new card to SHAZAM Core, users automatically trigger the system to order physical cards for the customer.

Access Required: Users with the Add permission enabled for the Card Management tab can perform this task.

Step Action 1 Load the CIS profile for the customer who will be the primary cardholder. 2 Hover over the blue More link at the right side of the tab selector and then select Card Mgt in

the dropdown menu. 3 Become familiar with the components of the Card Management tab, shown below.

The Card Mgt tab selector appears only after that item is selected in the More drop-down menu.

This table lists any existing PANs for which the customer is the primary cardholder. This button displays a form for creating a PAN and ordering a new card.

4 Select the New Card button at the bottom-left corner of the tab to start setting up a new card for the current customer. Users may need to scroll down to see this button.

5 Select the BIN code that defines the card type to issue and select Submit. Note: The FI defines available BINs and their parameters. Refer to internal staff or documentation for information about how the FI configured a particular BIN.

Page 12: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 12 ©2019 ITS, Inc. All Rights Reserved

The Card Management Edit dialog box, shown and described below, displays. This dialog box contains many sections and fields, some of which are prepopulated.

The expandable sections contain the fields where users set the new card’s parameters. Red borders on fields, such as Last Name, indicate they are required or they contain an

invalid entry.

6 Review the fields in the Card Information section and set the name to emboss on the card. (For detailed description of each field, select the linked section name.) Note: In the previous screenshot, SHAZAM Core automatically populated the Card Number field. However, the FI can instead require users to manually enter card numbers. If the FI has enabled this behavior in BIN-level parameters, ask an administrator how to enter an appropriate card number.

7 In the Contact Information section, complete the following tasks: • Confirm that the address listed is where the customer wants the card mailed.

Page 13: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 13 ©2019 ITS, Inc. All Rights Reserved

Note: The system maintains cardholder contact information in card records, which is separate from the information in the cardholder’s CIS profile. Therefore, ensure that changes to cardholder information are made in both locations.

• Set how many cards to order in the Card Order Count field. • To set when the system will reissue a new card, update the Months for Reissue field.

The Card Information section displays the pending card’s expiration date.

8 In the PAN Restrictions section, review any default restrictions on the accounts with which the card can perform transactions. Change the restrictions, if desired.

9 In the Withdrawal Limits section, review the default limits on the amounts of money a customer can withdraw via a card as well as the amounts they can withdraw after an unverified deposit or transfer.

10 In the Deposit Account or Savings Account section, identify the customer’s account that serves as the primary account for card activities.

If… Then… The PAN is a Visa or Mastercard debit card User must assign at least one deposit account The PAN is a Traditional ATM card User must assign a deposit or savings account

Users may also can restrict specific activities for assigned accounts, such as not allowing deposits to the account via ATM.

11 Use the following table to proceed. If… Then… Only the primary cardholder will use this PAN

1. Select the Submit button at the bottom of the dialog box

2. Proceed to the section labeled “Result” at the end of this procedure

Secondary cardholders will use this PAN Select the Submit and Add Names button. Proceed to the next step

12 On the Additional Names tab, select the Add button. 13 In the Additional Name Form dialog box that appears, use the following table to proceed.

If… Then… The secondary cardholder has a CIS profile in SHAZAM Core, and the profile has a relationship to the primary cardholder

Select the secondary cardholder in the Select Existing Relationship dropdown menu

The secondary cardholder does not have a CIS profile and/or relationship to the primary cardholder

Proceed to the next step

14 Review and complete the fields in this dialog box and select Submit to return to the Card Management Edit Form dialog box. Note: For detailed descriptions of the fields in this dialog box, refer to the following section of this document: Reference: Fields on the Additional Name Form Dialog Box.

Result: Once the user has added a PAN to the primary cardholder’s profile, the following actions occur:

Page 14: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 14 ©2019 ITS, Inc. All Rights Reserved

1. Return to the Card Management tab, where the new card record is listed. For descriptions of the components in a card record, refer to the following section of this document: Reference: User Interface for the Card Management Tab.

2. SHAZAM transfers card orders to the card vendor according to the FI’s order-frequency settings unless configured to a particular card to be rushed. SHAZAM transfers rush orders the same day the order is placed. Contact the card vendor to request overnight delivery or special handling.

3. Each cardholder receives their card at the mailing address entered when the PAN was added.

Tip: SHAZAM Core Services recommends that users review SHAZAM reports to verify the cards added. For more information about these features, refer to Viewing the Status of Card Maintenance Actions.

Adding another Cardholder to an Existing Card Number Complete the following steps to order a card with the same PAN as the primary cardholder’s but embossed with a different name. The additional cardholder does not need to be a customer in the SHAZAM Core system.

Access Required: Users with the Edit permissions enabled for the Card Management tab can perform this task.

Step Action 1 Load the CIS profile for the customer who is the primary cardholder. 2 On the Card Management tab, expand a card record and select the Edit icon: 3 Expand the Additional Names on Card section in the edit card dialog box. 4 Select the Add button at the bottom of the section. 5 In the Edit Name Form dialog box that appears, use the following table to proceed.

If… Then… The secondary cardholder has a CIS profile in SHAZAM Core and the profile has a relationship to the primary cardholder

Select the secondary cardholder in the Select Existing Relationship dropdown menu

The secondary cardholder does not have a CIS profile and/or relationship to the primary cardholder

Proceed to the next step

6 Review and complete the fields in this dialog box and select Submit to return to the Card Management Edit Form dialog box. Note: For detailed descriptions of the fields in this dialog box, refer to the following section of this document: Reference: Fields on the Additional Name Form Dialog Box.

Editing and Deleting Secondary Cardholders To edit or delete a card for a secondary cardholder in the future, complete steps 1-3 of this procedure, select the secondary cardholder in the Additional Names on Card menu, and then select the Edit or delete icon, respectively.

Reissuing Cards That Are About to Expire SHAZAM will automatically reissue new cards to replace cards that will expire during the current month. However, prior to the automatic reissuance users must ensure all cardholders due for reissue have

Page 15: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 15 ©2019 ITS, Inc. All Rights Reserved

correct information in the system and that they should receive a new card. Use the Plastics Reissuance (CM250-R) Report to learn which cards are due for reissue.

If a cardholder’s plastics information requires changes, such as to cardholder names or addresses, users must make corrections in the SHAZAM Core UI by 6:00 p.m. CT on the fifth day of the month after the system creates the Plastics Reissuance (CM250-R) Report. The following table presents an example of the process for reviewing and reissuing cards.

Example Date Action December 8 System generates the Plastics Reissuance (CM250-R) Report, which identifies

plastics that will expire during the next reissue period. This occurs on the eighth day of each month.

December 9 SHAZAM Core user retrieves the CM250-R report via the Optical Inquiry (RVI) program in Compass XD. For step-by-step instructions, refer to the procedure for Retrieving SHAZAM EFT Reports.

December 9-January 5

FI reviews report and makes changes to cardholder plastics information in the SHAZAM Core UI.

End of day, January 5

1. SHAZAM system creates the card order file, which has the following characteristics:

a. Excludes any hot cards and cards where the plastics information has been deleted.

b. Requests as many new cards per PAN as is set in the card record’s Card Order Count field.

2. System advances the expiration date of cards that were reissued. 3. System sends card order file to card vendor.

Note: If the FI applies a card reorder fee, SHAZAM Core creates transactions to debit the customer according to BIN-level parameters. Refer to Appendix A.

After January 5 1. Card vendor receives and processes file. 2. Card vendor creates plastics and mails plastics to cardholders.

Result: Cardholders receive their new cards. Card records in SHAZAM Core contain the new expiration date.

For more information about the CM250-R report, browse to SHAZAM Resource, navigate to Reports and Files » Plastics, and refer to the Plastics Reissuance (CM250-R) Report document.

Reordering a Card As the previous section describes, SHAZAM automatically reissues cards prior to expiration. However, if a card is damaged, users might need to manually order new cards with the same PAN sooner.

Complete the following steps to reorder cards for a primary or secondary cardholder.

Note: FIs have the option to reissue cards one month prior to their expiration rather than during the same month they expire. If the FI is set up that way, adjust the information below accordingly.

Page 16: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 16 ©2019 ITS, Inc. All Rights Reserved

Before Beginning: Verify that the cardholder’s mailing address in the card record is correct. The new card will be mailed to that address. Refer to the Verifying and Editing Cardholder Contact Information procedure for steps for completing this task.

Access Required: Users with the Card Mgt»Reorder Card permission enabled can perform this task.

Step Action 1 Load the CIS profile for the customer who is the primary cardholder. 2 On the Card Management tab, expand the profile for the card of interest and select the

Additional Options button. 3 Select Reorder Card in the dropdown menu. 4 In the Select Cardholder for reorder menu, select the cardholder for which to order a new

card. To reorder cards for all cardholders, leave the primary cardholder selected and place a checkmark in the Reorder for all Secondary Card Holders checkbox.

5 In the Reorder Card dialog box that displays, use the following table to proceed. If… Then… Set a new expiration date

Enter the desired month and year in the Expiration date field. Note: Changing the expiration date will cause all cards associated with this card number to be reordered, including both primary and secondary cardholders. Fee charges will apply for each card.

Leave the expiration date unchanged

Select the cardholder for which to reorder a card in the Select Cardholder for reorder menu. Leave the Expiration date field unchanged. Only the cardholder selected will have cards reordered.

6 If the FI charges a default card-reorder fee, the Waive $X.XX ATM Card reorder fee?

checkbox allows users to specify whether to waive that fee. If the FI does not charge this fee, this checkbox is not visible.

7 Select Submit to place the order. Result: SHAZAM orders as many new cards per cardholder as is set in the Card Order Count field for each cardholder. If the FI applies a card reorder fee, SHAZAM Core creates transactions to debit the customer according to BIN-level parameters. For descriptions of the parameters, refer to the Parameters Maintenance documentation located on the Client Login.

Page 17: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 17 ©2019 ITS, Inc. All Rights Reserved

Cancelling a Pending Card Order Access Required: Users must have credentials to log into SHAZAM Access.

Complete the following steps in SHAZAM Access to cancel a card order that was previously submitted in the SHAZAM Core UI. Users cannot perform this task in the SHAZAM Core UI.

Before Beginning: This process must be completed prior to 6:00 p.m. CT on the same day the card was ordered.

Step Action 1 Log into SHAZAM Access. 2 Under the Cards tab, search for and select the PAN. 3 Under the Plastics Information heading, verify that the Order Status field reads Order

Entry followed by a date. Users cannot delete an order unless the card is in this status Note: The Update/Order screen will show Pending.

4 Uncheck the Order plastics field 5 Select Submit 6 Select Confirm 7 Select Continue 8 Verify the plastics record 9 Use the following table to decide how to proceed.

If… Then… Deleted the order of a card that was ordered for the first time

Perform the procedure for Deleting a Card in the SHAZAM Core UI to delete the card record from the system entirely

Deleted an existing card that was reordered/reissued

A. In the SHAZAM Core UI, perform the procedure for Reordering a Card and revert the PAN’s expiration date to its value prior to being reordered.

B. Repeat steps 1-8 to delete the cards just reordered while completing step A. Delete cards for the primary and all secondary cardholders.

Result: SHAZAM does not submit the new card order to the card vendor.

Page 18: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 18 ©2019 ITS, Inc. All Rights Reserved

Instructions for Updating, Restricting, or Deleting Existing Cards The Card Management tab also provides features for performing ongoing maintenance on cards in the system. For example, users may need to perform the following tasks after a customer has received a card:

• Editing most of the same information and parameters set when the PAN was added. • Enabling PAN or account restrictions, including hot carding all cards with the PAN. • Deleting the card.

Before Beginning The FI might restrict some users from performing certain card-management tasks. For example, users may allow customer service employees to replace broken cards but not allow them to issue a new PAN to a customer. The procedures in the following sections begin by specifying whether every user can perform the steps or if only a user with specific permissions can perform them.

Locating a Cardholder Access Required: All users can perform this task.

To interact with cards, including to order a new card, first identify the existing customer who is the primary cardholder.

Step Action 1 If necessary, complete the following steps to open the Inquiry Search page:

A. Select the Menu icon at the top-left of the user interface: B. Select one of the menu systems that displays. The menu system available depends

on the roles assigned to the user ID. C. Select the menu item for customer and account inquiry.

2 Enter one of the following pieces of customer information in the Inquiry Search textbox: • Account or Customer Information System (CIS) number • PAN • Social security number • Customer short name

3 Select Search. The system returns either a list of matching customers or the profile for the

exact customer if the search term was precise enough. 4 The customer’s profile loads with the CIS Info tab visible. To open the card-management

tab, hover over the blue More link at the right side of the tab list and then select Card Mgmt in the drop-down menu.

Page 19: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 19 ©2019 ITS, Inc. All Rights Reserved

Verifying and Editing Cardholder Contact Information Access Required: Users with the Edit permission enabled for the Card Management tab can perform this task.

Because SHAZAM Core maintains cardholder contact information in card records, separately from the information in the cardholder’s CIS profile, it’s useful to verify that the card record information is in sync with the CIS profile information. For example, users might want to ensure that a change to the last name or address in a CIS profile is also reflected in the customer’s cardholder records.

Users can edit most of the same information and parameters set when the PAN is added, including primary and secondary cardholders’ contact information, the number of cards to order when new cards are issued, etc.…

Step Action 1 On the Card Management tab, expand the profile for the card of interest and select the

Edit icon: 2 On the Card Information or Contact Information section of the dialog box, hover over the

informational glyph beside a field: . The value of the corresponding field within the cardholder’s CIS profile displays. In the following screenshot, the cardholder’s last name in his CIS profile is Jones rather than Montgomery.

3 (Optional) To apply the values set in the cardholder’s CIS profile, select the Additional

Options button at the top of the dialog box and select Refresh from Core. 4 (Optional) Manually enter any new/changed information in the fields in the Card

Information or Contact Information sections.

Page 20: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 20 ©2019 ITS, Inc. All Rights Reserved

5 Select Submit to save the changes. 6 (Optional) To order a new card that reflects changed information, such as an updated

cardholder’s last name or a second line/business name, complete the steps for reordering a card.

Customizing the Withdrawal Limits for a Card Access Required: Users with the Card Mgt»Withdrawal Limits permission enabled can perform this task.

After adding a new card, users may want to customize the amounts of money a customer can withdraw via the card as well as the amounts they can withdraw after an unverified deposit or transfer. The FI sets default limits for each BIN, but users can customize the limits for a given PAN.

Step Action 1 On the Card Management tab, expand the profile for the card of interest and select the

Additional Options button. 2 Select Withdrawal Limits. The following dialog box displays.

3 Update the fields for limits to customize.

Note: For detailed descriptions of each type of limit that applies to a PAN, refer to the Reference: Withdrawal Limits Dialog Box section.

4 Select Submit to save the changes.

Restricting All Card Activity (Hot Carding) Access Required: Users with the Card Mgt»Hot Card permission enabled can perform this task.

Complete the following steps to block all transactions attempted with the card. Applying this block is referred to as hot carding.

Caution: Users cannot remove the hot-card status from a PAN unless the PAN is for a Traditional ATM card.

Step Action 1 On the Card Management tab, expand the profile for the card of interest and select the

Additional Options button.

Note: Limits are reset each day at 12:00 AM.

Page 21: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 21 ©2019 ITS, Inc. All Rights Reserved

2 Select Hot Card in the dropdown menu. 3 Confirm the status change in the dialog box that displays.

Result: Hot cards remain in SHAZAM Core with the hot-card status applied until the card record is deleted. However, hot cards are tracked separately in the Visa and Mastercard systems, as the following table describes.

Card Type Action on the Card

Visa When the card’s purge date arrives, the network is notified to remove the card from its hot-card list. The system automatically sets a purge date that is one year in the future. To manually set a purge date other than one year in the future, hot-card the card in SHAZAM Access.

Mastercard When the card’s purge date arrives, and the network is notified to remove the card from its hot-card list. This is only important if / when Mastercard stands in.

The system automatically sets a purge date that is 180 days from the date the card is hot carded in the SHAZAM Core UI. Mastercard recommends hot carding the card every 180 days until expiration; however, this isn’t required.

Temporarily Restricting Certain Card Activities Access Required: Users with the Edit permission enabled for the Card Management tab can perform this task.

To temporarily block transactions that involve an account assigned to a card, enable restrictions at the PAN or account level:

• PAN-level restrictions limit all activity with all accounts of a particular account type, whether deposit or savings.

• Account-level restrictions affect use of the card with only a specific account. This allows users to fine-tune the restricted activities. For example, users may block transfers from an account but still allow inquiries on its balance. These restrictions apply only for the card and not for the account as a whole, meaning that another card that is assigned to the account can have different restrictions.

Complete the following steps to enable PAN or account restrictions.

Note: SHAZAM does not automatically reissue cards when the hot-card status is applied even if their expiration date is approaching.

Page 22: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 22 ©2019 ITS, Inc. All Rights Reserved

Step Action 1 On the Card Management tab, expand the profile for the card of interest and select the

Edit icon: 2 Scroll to the section of the dialog box that contains the desired restriction.

If… Then… Enable a PAN-level restriction Expand the PAN Restrictions section Enable a restriction on an account Expand the section that corresponds to the

account. For example, Deposit Account 2 corresponds to the second checking account assigned to the card.

3 Configure the checkboxes for the restrictions to enable. For detailed descriptions of each restriction, refer to the PAN Restrictions section or the reference sections for deposit accounts or savings accounts.

4 Select the Submit button to save the changes. Removing Temporary Restrictions To remove a PAN- or account-level restriction, open the Card Management Edit Form dialog box, browse to the same section where the restriction is enabled, and remove the checkmark from the restriction checkbox.

Enabling Balance Round-Up Access Required: Users with the Card Mgt»Extended Processing permission enabled can perform this task.

Balance round-up causes the system to round up the amount of each debit made with the card to the nearest dollar and later transfer rounded-up portions to another account. For more information, refer to the Roundup Feature section.

Complete the following steps to enable balance round-up for one or more accounts assigned to the card.

Step Action 1 On the Card Management tab, expand the profile for the card of interest, and select the

Additional Options button. 2 Select Extended Processing in the dropdown menu.

Note: Each FI chooses whether it uses extended processing features like balance round-up. If the FI does not use this feature, ignore this section.

Page 23: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 23 ©2019 ITS, Inc. All Rights Reserved

3 In the Receiving Account menu above the table, select the account in which the rounded-up amounts are to be deposited. This menu contains only accounts assigned to the card.

4 In the table, place a checkmark in the Roundup column for any account whose debits are to

be rounded up. 5 Select Submit.

Result: The system begins performing round-up transactions the next time nightly processing occurs.

Disabling Balance Round-Up To disable this extended-processing feature, remove the checkmark from the Roundup column for one or all accounts.

Deleting a Card Access Required: Users with full access to Card Management features can perform this task.

Complete the following steps to delete a card from SHAZAM Core.

Step Action 1 On the Card Management tab, expand the profile for the card of interest, and select the

Delete icon . 2 Confirm the action.

Result: The system removes both the plastics and card-authorization file information. This causes the physical cards to stop working and prevents the system from reissuing new cards. Users may want to delete a card record in the following situations:

• When an account is closed • When a cardholder no longer wants the card

Note: The Extended Processing Edit Form dialog box also contains the Additional Features section shown above. This section is reserved for future use. In the current release, SHAZAM Core does not provide any additional built-in processing options.

Page 24: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 24 ©2019 ITS, Inc. All Rights Reserved

Viewing the Status of Card Maintenance Actions After adding, ordering, or updating cards, SHAZAM Core Services recommends checking the status of the action to see whether the operation succeeded. To help verify the success or failure of actions, the following reports are available via the Optical report imaging system on the day after an order or maintenance:

• File Maintenance Log (SSR080)—Lists the data in each plastics maintenance request message and the response code associated with each request. Provides information about the previous day plastics maintenance activity including card orders, name and address changes, Social Security number changes, phone number changes, etc. The maintenance type for maintenance performed in the SHAZAM Core UI is listed as Web.

• Card Account File Maintenance (CD200-R)—Provides detailed information about card account file maintenance performed, such as changes to hot-card status, limits, or assigned accounts.

• SHAZAM Warning Bulletin (SCD010)—Lists debit cards to have reported as lost or stolen and the warning notice regions each card is listed in, if applicable.

Retrieving SHAZAM EFT Reports Each night when processing runs, SHAZAM Core distributes SHAZAM EFT reports to the Optical/Real Vision report imaging system. These reports include card-maintenance, settlement, and card reissuance reports. Complete the following steps to access SHAZAM EFT reports.

Before Beginning:

• Access to SHAZAM Compass LegaSuite®. Users cannot access these reports through the new SHAZAM Core UI in which the Card Management tab resides.

• User account must have access to Optical.

Step Action 1 Log into Compass LegaSuite. 2 At the top-right corner of Compass, select the stop-light glyph called out below. Users may

have to select this twice.

3 Browse for and select Optical Inquiry (RVI) in the list of Help Display topics.

Note: Several additional reports for other types of EFT activity are typically published to the Optical system, such as reports for settlement activity. For information about the contents of any SHAZAM

Access report, open SHAZAM Resource, browse to Reports and Files, and refer to the documentation for each report of interest.

Page 25: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 25 ©2019 ITS, Inc. All Rights Reserved

4 On the screen that displays, enter the date whose reports to view. 5 In the application code field, enter AT for ATM reports. 6 Browse the list of all reports that were generated for the day entered.

Note: The FI determines which SHAZAM EFT reports are available in Optical. For help with the FI’s configuration, contact SHAZAM Client Support at (800) 537-5427 and select option 2. The following screenshot shows a subset of the EFT reports from a particular date.

7 If… Then…

View a text version of a report Enter V beside the report to view and press <Enter>.

Print a report Enter P beside the report to print and press <Enter>.

Result: Reports in Optical remain available indefinitely.

Researching Maintenance Questions If users believe that the system did not apply card maintenance performed in the SHAZAM Core UI correctly, compare the information stored in SHAZAM Core with the information in SHAZAM Access. Complete the following steps to view the PAN information that is stored in SHAZAM Access.

Step Action 1 On the Card Management tab, expand the profile for the card of interest and select the

Edit icon: 2 Select the Additional Options button at the top of the dialog box and select SHAZAM Data. 3 Review the values the system may not have applied correctly. The SHAZAM Data dialog box

contains the following sections: • Plastics Information—Information about the card, including the cardholder contact

information and expiration date. • Card Authorization File Information—Information SHAZAM uses to authorize or

decline a transaction, such as withdrawal limits and activity restrictions.

Page 26: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 26 ©2019 ITS, Inc. All Rights Reserved

4 Exit the dialog box when the information needed is retrieved. Results: If user discover that information in SHAZAM’s plastics or Card Authorization File records is inconsistent with the information in the SHAZAM Core UI, attempt to repeat actions and fix issues in the SHAZAM Core UI rather than in SHAZAM Access. If users make changes in SHAZAM Access, the new information can get out of sync with SHAZAM Core and cause even greater issues. If an action consistently fails in the SHAZAM Core UI, contact SHAZAM Client Support at (800) 537-5427 and select option 8.

Page 27: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 27 ©2019 ITS, Inc. All Rights Reserved

Viewing Past Transactions Access Required: Users with the Transaction History permission enabled can perform this task.

Complete the following steps to view a history of all transactions, including both approved and denied transactions, performed with a PAN.

Step Action 1 On the Card Management tab, expand the profile for the card of interest and select the

Additional Options button. 2 Select Transaction History in the drop-down menu. 3 Review the list of transactions. Expand the profile for a transaction of interest to see

more details. 4 Exit the dialog box when the research is finished.

Note: Information about approved transactions performed with a card also displays on the Activity tab of the Accounts pane when loading the account involved in the transaction.

Page 28: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 28 ©2019 ITS, Inc. All Rights Reserved

Reference: User Interface for the Card Management Tab After adding a card record, the Card Management tab displays card information and provides features for maintaining the card. The following screenshot calls out features of the Card Management tab to use to inquire on and maintain the card.

View and update card information on the same Card Management tab.

View all cards for which the customer is primary cardholder in this table. This example shows a single card with its profile expanded.

Quickly reorder a card; hot-card a PAN; edit withdrawal limits; and view the PAN’s transaction history.

Delete the PAN so all cards stop working and new cards are not issued in the future.

Collapse or expand a card’s profile.

Edit the card and cardholder information defined when the card was added.

View accounts with which the card can perform transactions and any restrictions on them.

Add and order a card with a new PAN for the customer.

Page 29: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 29 ©2019 ITS, Inc. All Rights Reserved

Fields on the Card Management Tab The Card Management tab contains the following sections.

List of customer’s cards Accounts assigned to the selected card Settings for the selected card

List of Customer’s Cards The top section of the Card Management tab lists each card on which the customer is the primary cardholder. This list does not display cards for which the customer is a secondary cardholder.

Field Description Card Number A masked version of the PAN. To unmask the PAN, edit the card record,

and remove the checkmark from the Show Mask checkbox in the Card Edit Form.

BIN Code The BIN code helps identify the type of card and the default values the card inherits from the BIN-level parameters.

BIN Description A text description of the card’s BIN Code. This description is a BIN-level parameter.

Expiration Date The date when the card expires. SHAZAM Core calculates this date by counting forward N number of months from today’s date, where N is the value of the Months to Reissue field, which is another field in the card record.

Accounts Associated with the Selected Card This section of the Card Management tab lists all the customer accounts with which the card can perform transactions. Observe the following concepts in the screenshot of this section:

Page 30: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 30 ©2019 ITS, Inc. All Rights Reserved

Users may assign up to four deposit and four savings accounts that exist in SHAZAM Core to a

card. Any account with which the customer has any relationship can be assigned. Each account has two columns associated with it: the account number and a corresponding

numeric restriction code, which indicates that one or more restrictions is active for the account. In this example, the primary deposit account has an active restriction. For a list of all restriction codes and their definitions, refer to Deposit and Savings Account Restriction Codes.

Primary accounts of each type appear at the left of the table. Any additional accounts of each type appear in rows to the right of the primary columns.

Plastics and Card Authorization File (CAF) Settings This section summarizes information about the card, including the contact information for the customer and limits on the withdrawal and credit amounts.

Field Max Length (chars)

Description

Name on Card * The name to emboss on the card. * Although this field displays many characters, card vendors can emboss only a limited number of characters. In other words, if limitations are violated, cards will not display the exact value in this field. Refer to Card Embossing Restrictions for more information about these limitations.

Mailing Name 22 or 26 Card mailing name Address Line 1 26 Mailing address for card Address Line 2 26 Mailing address for card—line 2 City, State, Zip City, State, and Zip Code Phone Number 10 Customer phone number Alternate Phone 10 Alternate phone number Daily Withdrawal Limit 5 The maximum amount cardholders can withdraw daily

from attended and unattended terminals, such as ATMs and POS terminals, or transfer via funds transfer debits.

Daily Unmanned W/D Limit 5 The maximum amount cardholders can withdraw per day at an unmanned terminal, such as an ATM.

Three Day W/D Limit 5 The maximum amount cardholders can withdraw during a three-day period, not including withdrawals from Mastercard or Visa POS terminals.

Card Stock Field 3 If the FI offers multiple card backings for a BIN, this is the numeric code that indicates the backing to use on the card. These codes are FI-defined.

Page 31: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 31 ©2019 ITS, Inc. All Rights Reserved

Field Max Length (chars)

Description

Unverified Dep Credit Limit 5 The maximum amount that can be withdrawn from a deposit at unattended terminals, such as ATMs, without the deposit being verified. A deposit is verified after the issuing FI receives the transaction file and sends a new balance file for the cardholder.

Transfer Dep Credit Limit 5 The maximum amount credited to accounts for transferred funds.

Month for Reissue 2 This field is reserved for future use. Auto Reorder 1 This field is reserved for future use. The FI must manually

reissue new cards to replace cards that will expire at least 30 days in advance.

PAN Restrictions 2 A numeric code that indicates one or more PAN-level restrictions are enabled. For definitions of each code, refer to the PAN Restrictions section.

Page 32: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 32 ©2019 ITS, Inc. All Rights Reserved

Reference: Fields on the Card Management Edit Dialog Box Users enter information for new cards and maintain existing cards in the same Card Management Edit dialog box. The following tables describe the fields that appear in each dialog box section.

Card Information Section This section contains the following fields.

Field Max Length (char) Description

Card Number 10 The card number, excluding the BIN number. FIs can set a BIN-level parameter so that SHAZAM Core auto-generates this number or allow users to manually enter a number. Users cannot change this number after ordering a card.

BIN Code 3 The three-character value that serves as a short name for a BIN. Salutation 4 A name prefix, such as Mr, without a period. First Name 22 or 26

(combined) The portion of the customer’s first name to print on the card.

Last Name The portion of the customer’s first name to print on the card. Middle Initial 2 Customer’s middle initial to print on the card. Second Line Embossing

26 An additional name or identifier to print on the card, such as a business name. This field is visible only for Business Debit BINs.

Birthdate 6 The cardholder’s birth month and year in MMYYYY format. Expiration Date 6 The card expiration date in MMYYYY format. SHAZAM Core

automatically calculates this date by counting forward N months from today’s date, where N is the value of the Months for Reissue field in the Contact Information section of this dialog box.

Contact Information Section This section contains fields related to ordering and mailing physical cards to the primary cardholder and any secondary cardholders. A secondary cardholder receives a card with the same PAN that is subject to the same limits, but the card is embossed with a different name.

Note: Although the name-related fields in this section allow users to enter many characters, card vendors can emboss only a limited number of characters. In other words, if the limitations

are violated, cards will not display the exact value in this field. Refer to Card Embossing Restrictions for more information about length and special-character limitations.

Note: The buttons and fields for secondary cardholders appear in this section only after adding a card record for the primary cardholder, and then edit that card record. In other words, users

can add a secondary cardholder only to PANs that are already in the system.

Page 33: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 33 ©2019 ITS, Inc. All Rights Reserved

Differences between Card Contact Information and CIS Profiles Contact information for cardholders is maintained separately from the information in customer CIS profiles. Therefore, if a customer’s information changes, enter updates in both locations or refresh the cardholder data to match the CIS profile.

Field Max length (chars)

Description

Mailing Name 34 Card mailing name Mailing Address 1 26 The address to which to mail cards Mailing Address 2 26 Card mailing address, line 2 Mailing City 18 Card mailing city Mailing State 2 Card mailing state Mailing Zip Code 9 Card mailing zip code Phone Number 10 Phone number 1 Alternate Number 10 Phone number 2

Card Order Count 3 Number of cards to order for the primary cardholder. Months for Reissue

2 This field is reserved for future use.

Card Stock Field 3 If the FI offers multiple card backings for a BIN, this is the numeric code that specifies the backing to use on the card. These codes are FI-defined.

Image Ref ID ? This field is reserved for future use. Rush Card Order 1 If the FI’s orders are transferred to the card vendor weekly, place

a checkmark in this checkbox to have the order transferred to the card vendor the same day. Be aware that the card vendor uses regular mail services to mail the card to the cardholder and may assess rush-order fees to the FI.

Page 34: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 34 ©2019 ITS, Inc. All Rights Reserved

Reference: Fields on the Additional Name Form Dialog Box The Additional Name Form dialog box allows users to set up and order a duplicate card with matching PAN but embossed with a different name. These secondary cardholders can be customers in SHAZAM Core but are not required to be.

To launch this dialog box, locate the card record on the primary cardholder’s profile, select the Edit icon , and then expand the Additional Names on Card section and select Add.

Field Max Length (chars)

Description

Select Existing Relationship

N/A Lists customers in SHAZAM Core that have a relationship to the primary cardholder where that relationship record possesses the specific relationship code the FI designated as meaning the customers can share a PAN.

Salutation 10 The prefix for the name, such as Mr, if any First Name 22 or 26

(combined) First name of person to add

Last Name Last name of person to add Middle Initial 1 The one-character middle initial Tax ID 9 Tax ID number Birthdate 6 The cardholder’s birthday in the format MMDDYY

Page 35: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 35 ©2019 ITS, Inc. All Rights Reserved

Rush Card Order 1 If the FI’s orders are transferred to the card vendor weekly, place a checkmark in this checkbox to have the order transferred to the card vendor the same day. Be aware that the card vendor uses regular mail services to mail the card to the cardholder and may assess rush-order fees to the FI.

Card Order Count 3 Number of cards to order for the secondary cardholder Note: The following fields are read-only. The system populates their values from the primary cardholder’s information in the card record. Card Number A masked version of the PAN Card Type The three-character value that serves as a short name for a BIN Second Line Embossing

An additional name or identifier to print on the card, such as a business name. This field is visible only for Business Debit BINs.

Expiration Date The card expiration date in MMYYYY format. The SHAZAM Core UI automatically populates this value according to the BIN-level Months to Reissue parameter. SHAZAM automatically reissues new cards one or two months prior to the Expiration Date, depending on the FI’s parameters.

Mailing Name Card mailing name Mailing Address 1 Card mailing address Mailing Address 2 Card mailing address, line 2 Mailing City Card mailing city Mailing State Card mailing state Mailing Zip Card mailing zip code Phone Number Phone number 1 Alternate Number Phone number 2

PAN Restrictions Section PAN restrictions supersede any account-level restrictions entered. For example, if users restrict all savings activity at the PAN level, savings accounts assigned to the card cannot interact with the card at all.

Field Description Restrict Debit Activity Block all activity with all deposit accounts assigned to the card. Restrict Savings Activity Block all activity with all savings accounts assigned to the card. Warm Card Prevents authorization of transactions involving all debit, savings,

and credit accounts. This is not a temporary card block. Hot Card No transactions are allowed.

Page 36: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 36 ©2019 ITS, Inc. All Rights Reserved

Withdrawal Limits Section Users can set several types of limits on the amounts of money a customer can withdraw via a card as well as the amounts they can withdraw after an unverified deposit or transfer.

Field Description Daily Withdrawal Limit The maximum amount cardholders can withdraw daily from

attended and unattended terminals, such as ATMs and POS terminals, or transfer via funds transfer debits.

Daily Unmanned W/D Limit The maximum amount cardholders can withdraw per day at an unmanned terminal, such as an ATM.

Three Day W/D Limit The maximum amount cardholders can withdraw during a three-day period, not including withdrawals from Mastercard or Visa POS terminals.

Unverified Dep Credit Limit The maximum amount that can be withdrawn from a deposit at unattended terminals, such as ATMs, without the deposit being verified. A deposit is verified after the issuing bank receives the transaction file and sends a new balance file for the cardholder.

Transfer Dep Credit Limit The maximum amount credited to accounts for funds transferred.

Deposit Account 1 (Primary) and Deposit Account 2-4 Sections Assign the customer’s deposit accounts to the PAN so that cards can perform transactions with the accounts. Users also restrict activities the cardholder can perform on these sections.

Note: Visa and Mastercard debit cards must have at least one deposit account assigned. Traditional ATM cards can have a deposit or savings account assigned.

Page 37: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 37 ©2019 ITS, Inc. All Rights Reserved

Field Description Account Number The available account numbers are type D accounts associated with the

customer CIS number in SHAZAM Core. Type This read-only value is D, which indicates a deposit account. Restrictions FIs can set the default status of each restriction in the BIN parameters. No ATM Deposits Restricts use of card to make a deposit at an ATM. No Withdrawals or Payment

Restricts use of card to make a withdrawal or payment.

No Transfer Deposits Restricts use of card to make a transfer deposit. No Transfer Withdrawals Restricts use of card to make a transfer withdrawal. No Balance Inquiries Restricts use of card to make a balance inquiry.

Savings Account 1 (Primary) and Savings Account 2 through 4 Sections Assigns the customer’s savings accounts to the PAN so that cards can perform transactions with the accounts. Users also restrict activities the cardholder can perform on these sections.

Note: Visa and Mastercard debit cards are not required to have a savings account assigned. Traditional ATM cards can have a deposit or savings account assigned.

Page 38: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 38 ©2019 ITS, Inc. All Rights Reserved

Field Description

Account Number The available account numbers are type S accounts associated with the customer CIS number in SHAZAM Core.

Type This read-only value is S, which indicates a savings account. Restrictions The default status of each restriction is a FI-specific setting in the BIN Code parameters. No ATM Deposits Restricts use of card to make a deposit at an ATM. No Withdrawals or Payment

Restricts use of card to make a withdrawal or payment.

No Transfer Deposits Restricts use of card to make a transfer deposit. No Transfer Withdrawals Restricts use of card to make a transfer withdrawal. No Balance Inquiries Restricts use of card to make a balance inquiry.

Page 39: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 39 ©2019 ITS, Inc. All Rights Reserved

Reference: Withdrawal Limits Dialog Box This dialog box maintains the limits on the amounts of money a customer can withdraw via the card as well as the amounts they can withdraw after an unverified deposit or transfer.

For instructions for accessing this dialog box, refer to the Customizing the Withdrawal Limits for a Card section of this document.

Field Max Length (chars)

Description

Daily Withdrawal Limit 5 The maximum amount cardholders can withdraw daily from attended and unattended terminals, such as ATMs and POS terminals, or transfer via funds transfer debits.

Three Day W/D Limit 5 The maximum amount cardholders can withdraw during a three-day period, not including withdrawals from Mastercard or Visa POS terminals.

Unverified Dep Credit Limit 5 The maximum amount that can be withdrawn from a deposit at unattended terminals, such as ATMs, before the deposit is verified. A deposit is verified after the issuing FI receives the transaction file and sends a new balance file for the cardholder.

Daily Unmanned W/D Limit 5 The maximum amount cardholders can withdraw per day at an unmanned terminal, such as an ATM.

Transfer Dep Credit Limit 5 The maximum amount credited to accounts for funds transferred.

Page 40: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 40 ©2019 ITS, Inc. All Rights Reserved

Reference: Extended Processing Edit Form Extended processing refers to operations the SHAZAM Core system can perform on a transaction, such as applying charges for various activities or implementing special built-in programs, such as balance round-up.

For instructions for accessing this form, refer to the Enabling Balance Round-Up section of this document.

Roundup Feature The following fields appear in this section. For step-by-step instructions for enabling balance round-up, refer to the Enabling Balance Round-Up section.

Field Description Receiving Acct Num The account to round-up amounts to be deposited. Search Filters the list of accounts to show only accounts that contain the characters

entered. Roundup checkbox If checked for a particular account, enables rounding on debit transactions

that involve the account.

When enabling balance round-up, SHAZAM Core performs the following operations:

1. For each transaction made with the card during PIN or signature-based POS transactions, rounds up the amount to the nearest dollar. SHAZAM Core does not include the rounded-up portions in the transaction amounts, but rather, adds and stores them internally.

2. At the end of each business day, transfers the total rounded-up amount from accounts with round-up enabled to the receiving account of the customer’s choice.

If SHAZAM Core performs balance round-up on a transaction and the transaction is later reversed, the rounded-up portion of that transaction is debited from the receiving account and credited back to the deposit account.

Example Consider the following example:

1. A cardholder makes purchases of $4.95 and $5.95 with the card. 2. These debits post to the card’s primary deposit account as $4.95 and $5.95. 3. SHAZAM Core adds and records the difference between the rounded-up dollar amounts, $5.00

and $6.00 respectively, which is $0.10. 4. At the end of the day, SHAZAM Core transfers $0.10 from the deposit account to the customer’s

receiving account.

Page 41: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 41 ©2019 ITS, Inc. All Rights Reserved

Additional Features This section of the Extended Processing Edit Form dialog box is reserved for future use. In the current release, SHAZAM Core does not provide any additional built-in processing options.

Field Description Categories A list of groups of processing operations. The category selected determines

which operations appear in the Available Options drop-down menu. Available Options A list of processing operations that can be enabled for the PAN.

Drag an option from this list to the Selected list to enable the option. Selected A list of the operations that are enabled.

Page 42: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 42 ©2019 ITS, Inc. All Rights Reserved

Appendix A: List of BIN-Level Parameters in Compass Rocket® LegaSuite® Each PAN inherits the default parameter values set for its BIN code. Users with access to the Enter/Update Debit Card BIN Parameters/AS1110 program in SHAZAM Core can view and set BIN parameters. Users can access this program in Cardinal Compass LegaSuite® and via a terminal session, shown as follows.

List of BIN Parameters Field Description

BIN Code The three-digit code that helps users identify the type of card they are working with in the SHAZAM Core UI.

BIN/Routing The bank identification number portion of the card number.

BIN/Routing Length The number of characters in the value of the BIN/Routing field.

(Visa issuers) Set a nine-digit BIN to avoid potential conflicts with tokenized BINs in the future. If the BIN is shorter than nine digits, pad the BIN in the BIN/Routing field with zeros (0) so that the BIN is nine digits long.

Total PAN length including BIN and Check Digit

The number of characters in the card number, which includes both the value in the BIN/Routing field and the check digit.

BIN Description A descriptive name or phrase that appears in the SHAZAM Core UI to help users assign the appropriate BIN code to new cards. This value can be up to 30 characters long and contain letters, numbers, and special characters.

Brand A description of the card brand.

Check digit type The following values are valid:

• 0: No check digit • 1: Modulus 10 check digit • 2: Modulus 11 check digit

SHAZAM Check Action

This field is reserved for future use.

Calculate PAN Whether to automatically calculate the PAN portion of card numbers instead of allowing users to manually enter it.

Charge for Card Order

Whether to charge the customer’s account for card orders: Y/N.

Page 43: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 43 ©2019 ITS, Inc. All Rights Reserved

Card Charge Amount The amount to charge the customer each time the system orders them a new card.

Charge Card Debit Tran Code

The transaction code to apply to the debit to the customer when assessing a card-order charge.

Charge Card GL Credit Tran Code

The transaction code to apply to the credit to the FI’s GL account when assessing a card-order charge.

Card Charge GL Branch

The branch at which the FI’s GL account resides.

Card Charge GL Acct The number of the GL account to credit with card-order charges.

Transaction Description

The description to apply to the card-order charge transactions between the customer and the FI’s GL account.

Authorized Signer Code

The relationship type code that, when applied to two customers in SHAZAM Core, allows each customer to be easily added to the other customer’s PANs as a secondary cardholder.

Enable 2nd Line Embossing

Whether cards that belong to the BIN are allowed to have a second name line embossed on them: Y/N.

Name on Card Length

The maximum length of the first name line on a card.

2nd Line Embossing Length

The maximum length of the second name line on a card, which is often used for a business name.

PAN Default Values Reissue in __ Months

The number of months after the card is issued when a new card should be issued. This value is used to automatically calculate expiration dates.

Reissue Indicator This field is reserved for future use.

Vendor The ID code of a card vendor defined in ASPAR3.

CAF Maint The ID code of a CAF-maintenance method defined in ASPAR2.

Restrictions

PAN A numeric restriction code that corresponds to one or more restrictions at the PAN level. For a list of the valid values, refer to the list of PAN Restriction Codes.

Checking A numeric restriction code that corresponds to one or more restrictions on activity with checking accounts. For a list of the valid values, refer to the list of Deposit and Savings Account Restriction Codes.

Page 44: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 44 ©2019 ITS, Inc. All Rights Reserved

Savings A numeric restriction code that corresponds to one or more restrictions on activity with savings accounts. For a list of the valid values, refer to the list of Deposit and Savings Account Restriction Codes.

Credit A numeric restriction code that corresponds to one or more restrictions on activity with credit accounts. For a list of the valid values, refer to the list of Deposit and Savings Account Restriction Codes.

Withdrawal Limits

Daily Withdrawal The maximum amount cardholders can withdraw daily from attended and unattended terminals, such as ATMs and POS terminals, or transfer via funds transfer debits.

Unmanned Daily Withdrawal

The maximum amount cardholders can withdraw per day at an unmanned terminal, such as an ATM.

3 Day Withdrawal The maximum amount cardholders can withdraw during a three-day period, not including withdrawals from Mastercard or Visa POS terminals.

Availability Limits

Checks Tendered The maximum amount credited to accounts for checks tendered at attended terminals, such as POS terminals.

Unverified Deposit The maximum amount that can be withdrawn from a deposit at unattended terminals, such as ATMs, without the deposit being verified. A deposit is verified after the issuing FI receives the transaction file and sends a new balance file for the cardholder.

Transferred Deposit The maximum amount credited to accounts for transferred funds.

Warning Region for Hot Card

This field is reserved for future use.

Page 45: SHAZAM Core Services3/31/16 Original Steven Moser 1/19/17 Revised to reflect new features and changes. Steven Moser 1/30/17 Removed references to the Card Processing Log. Steven Moser

Managing Cards Through the Real-Time Interface 2019

SHAZAM Core Services Documentation 45 ©2019 ITS, Inc. All Rights Reserved

Appendix B: List of Restriction Codes Restrictions on card activity can be set at the PAN and account levels. When viewing a card record on the Card Management tab, the tab indicates that one or more restrictions is active by displaying a numeric restriction code. The following sections define the valid restriction codes at the PAN and account levels.

PAN Restriction Codes The following table defines valid restriction codes at the PAN level.

Code Definition 0 N/A - No restrictions 1 No DDA activity allowed 2 No savings activity allowed 3 No DDA or savings activity allowed 4 No credit activity allowed 5 No DDA or credit activity allowed 6 No savings or credit activity allowed 7 No DDA, savings, or credit activity allowed; warm card 80 VIP account with no restrictions 81 VIP account with no DDA activity allowed 82 VIP account with no savings activity allowed 83 VIP account with no DDA or savings activity allowed 84 VIP account with no credit activity allowed 85 VIP account with no DDA or credit activity allowed 86 VIP account with no savings or credit activity allowed 90 Hot card

Deposit and Savings Account Restriction Codes The following table defines valid restriction codes at the account level. The value in this field is the sum of all restrictions. For example, if users restrict an account to no ATM deposits and no transfer withdrawals, the value will be 09 (1/No ATM deposits + 8/No transfer withdrawals).

Code Definition 0 N/A - No account restrictions 1 No ATM deposits 2 No withdrawals or payments 4 No transfer deposits 8 No transfer withdrawals 16 No balance inquires 99 The balance record for this account will be deleted when sending in a request to delete a

card. Other The sum of two or more active codes.