Card Issue Technical Documentation

This document provides a comprehensive guide to the Card Issue functionality within the Flex system, designed for technical users and as a resource for AI chatbot interactions.

1. Card Issue File Overview

A Card Issue File is a critical component for managing cardholder data within the Flex system and its integration with card processors.

1.1. Definition

A file generated with cardholder data.
Purpose: To add the card record to the processor’s database.

1.2. Purpose

Applies cardholder data to the processor’s database.
Generates a new card for member use.

1.3. Production in Flex

Information is initially entered in Card Maintenance.
Information is linked to a member’s account in Flex.
The file is then built in the CARD PROCESSING menu.

1.4. Information Contained in an Issue File

The following information is typically included in an Issue File (but is not limited to):

Card Number
Card Type
Issue Option (Codes found in “Maintain Card types, by Card Type”):
- Immediate Issue
- Current Expiration
- New Expiration
Name #1 (Primary, First Name, Middle Initial, Last Name)
Number to Issue
Name #2 (Secondary, First Name, Middle Initial, Last Name)
Member Account Number
Last Used
Issue Code (Codes found in “Maintain Card types, by Card Type”):
- Activation Code

2. Card Issue Reports

Flex generates various reports when an issue file is processed, providing detailed information and error listings.

2.1. CDISSERRX: Card Issue Error Listing

Purpose: Identifies and lists errors preventing cards from being included in the Issue File.
Content:
- Effective date and time of the report.
- Card case and card types.
- Indication if for “New Cards only.”
- Specifies if it’s a “send file” (Y) or a “Worksheet” (N).
- Includes the same information as the Issue File.
- Lists specific errors.

2.2. CDISSX: Card Issue Listing

Purpose: Provides a comprehensive list of cards processed for issue.
Content:
- Effective date of the report.
- Card types configured in the “Control Parameters” menu that may go out in the file.
- Indication if cards are “New Cards only.”
- States if the file has been sent or is a worksheet.
- Processed from the “Card Processing” menu.
Issue Codes:
- I: Immediate/New Issue
- S: Standard/Reissue
- R: Rush
Activation Codes:
- N: None
- I: Issue/All Cards
- R: Reissue/New Exp Dt Only
- D: Duplicating/No Action
- Blank: Not Offered

2.3. CDISXSND: Card Issue Send Report

Purpose: Confirms the success or failure of the issue file transmission.
Content:
- Send start time with send code method.
- Confirmation of Card Issue File copied to drive/folder, including file name.
- Total number of records sent.
- Commands used during transmission.

2.4. CDISSUPDx: Issue Reference Update Report

Purpose: Displays changes made to card information during an issue update.
Content:
- Old and New Card Information:
  - Card Number
  - Account Number
  - Type
  - Issue Option
  - Expiration Date
  - Account Type

2.5. CDISSFEEX: Card Issue Fee-Posting Report

Purpose: Details fees associated with card issuance and their posting.
Content:
- Card Number
- Product Type Name
- Open/N/R status
- Account
- Suffix
- Fee amount
- Available Balance
- Totals (General Ledger, Count, Amount)

3. Transmission of Issue Files to the Processor

Flex offers various methods for transmitting issue files to card processors. The transmission method is configured within the “Control Parameters” menu.

3.1. Transmission Methods

Manual Processing:
- Credit Unions may manually process files by sending them to an I drive or Flex folder.
- Note: Flex is moving away from the I drive method.
- Credit Unions are responsible for uploading files to their processor, often via secure HTTPS.
SFTP (Secure File Transfer Protocol):
- Files can be sent via a direct connection to the credit union’s card processor.

3.2. Locating Transmission Method Configuration

Navigate to Cards / Configuration / Control Parameters.
Select the Processor.
Select Build Send the Issue file.
Press F9 for “Trans”.
Locate the Field Send Method Code.

3.3. Common Send Method Codes

4: SFTP
I: I drive
S: Stream
3: Flex Old Relay (Flex recommends moving clients away from this method to method 4. Note: This method may incur a one-time fee and monthly monitoring fees, unless the Credit Union is a Hosted Credit Union. It is considered a more reliable and secure method.)

4. Troubleshooting Common Card Issue Scenarios (Ticket Review)

This section outlines resolutions to frequently encountered issues related to card issuance.

4.1. Card Not Issued Due to Member Name Length (Ticket 870871)

Issue: Member’s name exceeded 22 characters, causing an error during card issue.
Resolution: Shorten the member’s name.

4.2. Excluding Inactive Cards from Re-Issue File (Ticket 867130)

Issue: Credit Union wanted to exclude cards unused for 3 years from the re-issue file.
Resolution:
1. Navigate to the Maintain Card types menu.
2. Select the relevant card type.
3. Go to page 4 of 8.
4. Locate the field Inactivity Days Max.
5. Change the value from 999 (infinite) to 998.

4.3. Block Codes Not Included in RCM Uploads (Ticket 822128)

Issue: Block codes were not being included in the RCM upload file (issue or update file).
Resolution:
1. Add the block codes to be included in the “Control Parameters” menu.
2. Select the processor.
3. Select Build send update.
4. Ensure options to Include or Exclude block codes are correctly configured.

4.4. Card Not on Issue Report (Ticket 854612)

Issue: Card was not appearing on the issue report for a Credit Union that processes “NEW cards only.” The issue file was looking for a “Pending” status, but a Z file had added an expiration date prior to the issue file run.
Resolution:
- Configurations for “new Cards only” are found in the Advanced configuration in the Control Parameters Menu. Review these settings to ensure they align with the Credit Union’s processing needs.