The Programming and Gividends EFT Teams work diligently on processing known issues using a priority list and following our SDLC (Software Development Life Cycle) Policy.
Here is a list of the implementations performed for your review. Because the issue stated on the project request can be very technical, we have added an additional explanation about what this change means to your EFT or other related CU*BASE features. We hope you enjoy this change!
Remember to use Monitor for additional details.
Also consult the Mandate Review page for where we stand on required changes requested by your network, VISA or MasterCard.
Learn more about CU*BASE Releases
Questions can be directed to The Gividends EFT email at gividendseftgroup@cuanswers.com
Implementation Date 2/20/12
There were no EFT Implmentations this week.
Implementation Date 2/13/12
There were no EFT Implementations this week.
Implementation Date 2/6/12
|
Project |
Description | What this means to you |
| 30806 | If the card sequencing flag is turned off, a request to issue another card with the same PAN will receive an message that there is a duplicate card on file. The status of the original card does not matter. It could be OPEN or CLOSED. The duplicate card will not activate at the network, therefore deny any member transaction. | This card edit will prevent a ‘duplicate’ card to be ordered that would not be activated. When the message is delivered, it will prompt the user to order a new card number (PAN). |
| 31243 | ISO File Re-Organization programs have been enhanced to ignore files that are empty. | This is an internal improvement for the CU*BASE EFT Platform programming. |
Implementation Date 01/30/12
|
Project |
Description | What this means to you |
| 30610 | If a Credit Card BIN is not configured on CU*BASE, the program that creates the credit card inquiry would not display all cards for that account base. | All cards will be displayed accurately in the Credit Card Inquiry for each account base. |
Implementatoion Date 01/23/12
|
Project |
Description | What this means to you |
| 30713 | The authorization process is now accurate with the calculation of the available balance when multiple transactions are processing in stand-in. | Now the subtraction of each subsequent stand-in transaction will be performed to deliver the appropriate available balance for authorization. |
| 31143 | Original Message Type of 0221 is now added to the program routine for incremental authorizations. This affects ELAN clients only. | After adding this message type code, a debit to the member account will process for the second incremental transaction, rather than a reversal, recognizing that two transactions were involved for posting. |
Implementation Date 1/9/12
|
Project |
Description | What this means to you |
| 31032 | The online credit card processing for ‘special’ characters in the transaction description was inadvertently dropping the letter ‘Z’. This has been resolved. | Transaction descriptions in the member transaction history will now be accurate if they contain the letter ‘Z’. |
| 30482 | The additional signer for an online credit card will now be included on the card emboss screen, without regard to the timing of the additional signer record maintenance. | Previously the additional signer needed to be added before the credit card loan was created on the member account for the emboss screen to include this name. Now if an additional signer is added to the loan, the card emboss screen will recognize this name. |
| 30416 | The pop-up window confirmation for the condition of a savings account entered into the checking account field for ATM/Debit Card funding accounts will no longer appear when additional card maintenance is performed. | Once the confirmation is presented and the end user agrees, they will not have to keep ‘agreeing’ to this confirmation on additional card maintenance. More streamlined processing is accomplished. |
Implementation Date 1/2/12
Holiday – No EFT Implmentations
Implementation Date 12/27/11
|
Project |
Description | What this means to you |
| 29164 | The PANCARD FILE INFORMATION Report (PADLIM) now shows pertinent information to be updated by the credit union with enhanced summary totals. Previously this report showed ATM/DEBIT cards linked to closed memberships. | This report is now more meaningful and delivers records that need to be reviewed and updated. The ATM/DEBIT cards attached to closed memberships have been deleted. We now do not allow a membership to be closed with a card attached. |
| 29432 | The ATM Column indicator in Member Inquiry and Phone Operator Inquiry is now updating from a ‘Y’ to a ‘N’ if the card is closed or the funding accounts are changed. | You can rely on the accuracy of this column indicator to be accurate as cards are closed or the funding account base is updated. |
| 31000 | FSCC Shared Branching (Acquirer) was not transmitting any loan data if there was no share or checking account. | This issue was resolved and will insure accuracy for all accounts being sent to the teller credit union when requested. |
Implementation Date 12/12/11
|
Project |
Description | What this means to you |
| 27687 | For Batch ATM/Debit clients, the ATM/DEBIT card number was added to the Posting Exception Report (TATMXX). The Pre-post exception report (RATMXX2) has the card number but not the member account number. Working the exception list required both reports to get the fields necessary. | This will allow for the use of one report (TATMXX) to process exceptions. It now provides all the information you need. |
| 30361 | Card maintenance for multiple fields in the same day are now sending correct data for all fields maintained. Previously it was sending the last maintenance record only. | This update now allows for the maintenance of multiple fields in the same day to be processed correctly by the network. |
| 30901 | We can now identify a reversal transaction as either a partial reversal or a full reversal. | Reversals were posting multiple times previous to this implementation. Although this was very infrequent, reversals will process accurately . |
Implmenetation Date 12/5/11
|
Project |
Description | What this means to you |
| 30529 | Non-English characters in the ATM location field in the member transaction history caused errors in the transaction display in online banking, GOLD, and in account statement processing. These characters are now being ignored at the time the EFT transaction is received by CU*Answers. This was an infrequent occurrence. | There will be no interruption for any display or processing of the member transaction history due to non-English characters in the ATM location field. |
| 30711 | If an update to a cardholder’s name is made on the same day a replacement card is ordered, the name change record will now process prior to the card order record to insure the correct name is placed on the plastic card. This timing issue affected all vendors. | Replacement card orders will now be embossed correctly if a name change is also processed on the same day. |
| 30819 | An update was made to the EFT transaction Activity file received from Fiserv so that the automated Purge feature will process. This file is the one used when the Activity function for the detail of the EFT transaction through Member Inquiry, Phone Operator or ATM/Debit Card Activity Option #2 on MNATMD is used. | Purging the EFT transaction data file for Fiserv clients will now function to keep the activity retention to 60 days. This will result in faster processing when this file is used for the Activity detail. |
| 30415 | Online Certification for a new COOP client was processed successfully. | No impact for any existing EFT clients. |
| 30828 | An change was made for a Self Processing Credit Union to resolve the interruption during End of Day when producing the EFT card transaction activity reports (LPAN reports) | This only affected one Self Processing client who will no longer need to make a change when the report processing halts during End of Day. |
Implementation Date 11/21/11
Due to the upcoming Thanksgiving holiday, there are no EFT implementations for this week. This is to reduce any risk of adverse issues so members will have a successful Black Friday and weekend shopping spree!
Implementation Date 11/14/11
There were no EFT Implementations for this week.
Implementation Date 11/07/11
|
Project |
Description | What this means to you |
| 30612 | When creating a card emboss record, there are two data files involved that need to be in synch for the sequence number of each cardholder. This was not the case and caused no card emboss record to be created. | Credit Cards orders will now have accurate card emboss records created and sent for card production. |
