CreditNow! CN-3000/CN-3100 AutoProcessor

Change log for the CreditNow! AutoProcessor.

19 March 2007: Version 3.1.16.3

GENERAL:

• Card identification code confused some Discover and Visa Purchase cards for Switch/Solo cards. This code is shared across all Auric applications, so problem appeared in CreditNow! AutoProcessor even though Switch/Solo cards are not supported. It is impossible to programatically identify some Visa vs. Switch/Solo cards since they both start with the digits 49. New card identification code always defaults to Discover or Visa where an overlap occurs. For products that support Switch/Solo, you must manually select that Method of Payment (MOP) for the transaction.
• Added ability to export configuration settings to Trevance.
• Updated User Manual.
  

21 February 2007: Version 3.1.15.2

GENERAL:

• Logging can now be turned on and off from within the application. No longer any need for external utility.
• Mask account and CVV2/CID values in all logs.
• CVV values in the database are explicitly cleared after every transaction completes.
• Selecting 'Other' as a delimiter for import files causes a range check error.
• Updated Payment Application Best Practices (PABP) documentation.

CHASE PAYMENTECH:

• After receiving a RAS 777 error (problem with remote modem) CreditNow! would cease attempting to communicate. Following changes were made:
• Add delays to the disconnection process.
• Wait longer before giving up on disconnect.

• Generate an error if the disconnect times out.

FIRST NATIONAL MERCHANT SOLUTIONS:

• FNMS discontinued dial-up support.
• Add VPN/Frame Relay support to CN-3000.

12 April 2006 Release 3.1.13.1

GENERAL:

• Corrected problem with new MasterCard/Diners cards. Card was correctly recognized, but indicator (DC) not being properly set in upload files to processor. Problem corrected for all processors.
  

30 January 2006 Release 3.1.12.3

GENERAL:

• Corrected range-check error in third-party database code. Problem occurs when a database table (typically ActivityLog.dat) exceeds 2 GBytes.
• Switched to RSA-style dynamically-generated key exchange to encrypt communications channel between Viewer and AutoProcessor. Previously, a hard-coded encryption key was used.
• Field reference now works properly with non-Internet Explorer default browsers. Previously, there were problems with directory paths containing spaces.
• Identified problem in third-party compression library used for communication between the Viewer and Server. Turned off compression in communication channel.
  

24 August 2005 Release 3.1.11.1

TRANSFIRST EPAYMENT SERVICES:

• Implement latest check processing specification.
  

1 August 2005 Release 3.1.10.4

GENERAL:

• CNServiceManager utility now runs properly under Windows 2003 Server.
• Corrected Viewer problem. Length of upload filename had been increased in AutoProcessor, but not in Viewer.
• Added PCI Compliance documentation to installer.
• Better handling for large volume of import files. Previous releases always did a 'find first' to get the next file in the import directory. In a high-volume environment, it was possible for a transaction to never 'rise to the top' to be processed. Files could be processed out of turn. CreditNow! now creates a list of all available importable files, sorts them by date/time, and then processes them in order. When the list is empty, CreditNow! loads up all available names and continues. This import logic is shared with CN!Express AutoProcessor where a problem is much more likely to occur than in the CreditNow! AutoProcessor which focuses on large batches.

TRANSFIRST EPAYMENT SERVICES:

• When processing checks, format unavailable birth date as blanks vs 0-filled.

30 November 2004 Release 3.1.10.3

GENERAL:

• More modifications to Archive process. Add a commit interval during deletion that reduces RAM requirements. Now ensures we get through large delete processes without running out of RAM. Previously, when deleting 100s of thousands of transactions, delete process would consume 2GBytes of RAM and then fail. Auric continuing to look at ways to improve this process for a large number of transactions.
  

TRANSFIRST EPAYMENT SERVICES:

• Change from PGP/FTP to S-FTP file transfer protocol.

12 November 2004 Release 3.1.10.2

GENERAL:

• Improved RAS dialing. It was possible for CreditNow! to get in a state where the Remote Dialing (RAS) connection did not disconnect. This has been identified in a situation where there are many busy signals or hang-ups. We duplicated the problem by unplugging the modem and attempting to dial. Now, whenever we attempt to dial, we first always hang-up the connection.
• Import files were not always being opened in read/write exclusive mode.
• Fixed problem updating two-year old databases. Field was referred to as BCD vs Float.
• Integrated CN-3000 and CN-3100 into single build.

TRANSFIRST EPAYMENT SERVICES:

• Confirmation passwords were being truncated on Transfirst setup dialog.
• Fixed problem where importing check number field greater than 6 characters caused batch import to fail.
• Stop truncating 160-byte records.
• Initialize Status in record type 05 to 0s instead of spaces.

29 October 2004 Release 3.1.9.1

GENERAL:

• Added File/Optimize function. Recovers space from database tables. Useful after Archiving a large number of transactions. Optimize walks through each database table and makes a copy containing only the active transactions. The copy is created in the DataTemp directory. The original file is then replaced with the new copy. Recommend you make a backup of the files in your Data directory before running Optimize. The embedded database used by CreditNow! AutoProcessor reuses empty space in data tables, so it is not necessary to run Optimize on a regular basis. Optimize is most useful after you archive an unusually large number of transactions and want to recover hard disk space.
• Quicker Archiving. Archiving is now significantly quicker--particularly when there are a large number of transactions being left in the database. Example: Archiving 2,000 of 103,000 transactions was taking over 6 minutes. Now takes 45 seconds.
• Renamed File/Validate menu item to File/Verify (and Repair)... This is a better description for the operation. A dialog appears describing what is about to happen and providing an opportunity to cancel.
• Miscellaneous additional feedback notices in the log during Verify and Archive operations.
• Any import error generated by data in the CheckAcctType field did not report properly in the warning file.
• If a country is not provided on import, send a blank rather than assume the country is US. Sending a blank is preferable to sending a default country.
• If the IP address of the server changed while CreditNow! was running, the AutoProcessor would crash because the AutoProcessor would try to bind to the old address and fail. Now the AutoProcessor logs an error and then resets to a default port and the current active IP and keeps on running.
• Config report dialog text field was not resizing properly when dialog was resized.

20 October 2004 Release 3.1.9.1

GENERAL:

• CN-3100 supports pluggable custom import modules. Custom import modules can be written to support arbitrarily complex incoming data formats. Provides ability to support existing custom data formats.
• First custom import module release.

23 September 2004 Release 3.1.7.1

GENERAL:

• Tested under Windows XP Service Pack 2.
• See ReadMe.txt file regarding firewall.
• Transactions Authorized with the CN!Express AutoProcessor can now be captured/deposited with the CreditNow! AutoProcessor. This capability is supported only within the same processor (e.g. First National Merchant Solutions or Paymentech). Authorizing at one processor and capturing at another processor is not supported. Requires the following product versions:
  
  • CN!Express 3.6.3.5.
  • CreditNow! 3.1.6.2.
  • Cosmetic: In Configuration report, Import columns without an assigned name would appear in the report as #001. Now says (unassigned).
  • See processor-specific information below for details.

FIRST NATIONAL MERCHANT SOLUTIONS:

• Transactions that are authorized using the CN!Express AutoProcessor through PayFuse may now be captured using CreditNow! AutoProcessor. PayFuse returns several fields that must be transfered from CN!Express to CreditNow!. These fields are conveniently gathered into the Transaction Reference Key field. The Transaction Reference Key field generated by CN!Express for the transaction should be included with the transaction when performing the batch capture. The following are the minimal fields that need to be transferred from the CN!Express for PayFuse to the CreditNow! for BAS:
• Transaction Reference Key
• Account number
• Amount
• Expiration Date

PAYMENTECH:

• Transactions that are authorized using the CN!Express AutoProcessor through Orbital Gateway (using BIN 001--Salem) can be captured using the CreditNow! AutoProcessor. Note: This was possible in previous releases, and is now officially supported and documented. Paymentech tracks the information necessary to allow transactions to be authorized on the Orbital Gateway and captured via the Salem Batch platform. The transaction's Order Number used for the Orbital Gateway authorization must be the same order number used when performing the batch capture operation with CreditNow! AutoProcessor. The Transaction Reference Key conveniently gathers several interesting fields together for transfer from CN!Express to CreditNow!. For consistency with other processors, you can include the Transaction Reference Key generated by CN!Express to the CreditNow! import transaction. The following are the minimal fields that need to be transferred from the CN!Express for Orbital Gateway to the CreditNow! for Salem Batch:
  
  • Transaction Reference Key
  • Account number
  • Amount
  • Expiration Date
• (CN-3100 only) Additional Files Now Downloaded and Stored CreditNow! AutoProcessor 3100 scans the FTP output directory for returned batch files. This change affects what is done with unexpected files (i.e., files that do not match any that were uploaded). In previous versions, unrecognized files were simply renamed. In the current version, these files are downloaded to a local directory. The local directory is "FilesFromProcessor" by default. The directory name can be changed using the Configure/Directories menu entry. CN-3100 for Paymentech scans and downloads all files with extensions of ".done" or ".dfr"
  

TRANSFIRST EPAYMENT SERVICES:

• Add support for passive FTP and FTP through proxies.
• Processing Status "E60" returned in pending file for E-checks would cause CreditNow! to report "Unrecognized Response Code" instead of display the proper message, "No Response from Processing Center."
• (CN-3100 only) Additional Files Now Downloaded and Stored CreditNow! AutoProcessor 3100 scans the FTP output directory for returned batch files. This change affects what is done with unexpected files (i.e., files that do not match any that were uploaded). In previous versions, unrecognized files were simply renamed. In the current version, these files are downloaded to a local directory. The local directory is "FilesFromProcessor" by default. The directory name can be changed using the Configure/Directories menu entry. CN-3100 for TransFirst ePayment Services scans and downloads all files that match Transfirst output file naming conventions.
• Fixed a bug that could cause returned batch information to not get stored properly, causing exported files to be exported without the returned information from the processor.

6 August 2004 Release 3.1.6.2

TRANSFIRST EPAYMENT SERVICES:

• Add eCheck functionality with QuickBatch.

FIRST NATIONAL MERCHANT SOLUTIONS:

• Two column names have changed:
• The Merchant Name column is now called Soft Descriptor 1.
• The Merchant City column is now called Soft Descriptor 2.
• This change was so that the two soft descriptor columns that contain information that should appear on the customer's credit card statement now have a consistent name.
• The on-line field reference (available under the Help menu) documents how the fields should be used.
• There is no change to the data layout that appears in the two fields.
  

23 July 2004 Release 3.1.6.1

TRANSFIRST EPAYMENT SERVICES:

• Initial release supporting credit card processing with QuickBatch.
• Communications with TransFirst processor is via the Internet.
• Transfers PGP-encrypted files.
  

25 June 2004 Release 3.1.5.8

FIRST NATIONAL MERCHANT SOLUTIONS:

• Authorized Amount field is now sent for all transaction types.
• Store field removed from setup. Required only for retail.
• Terminal ID field removed from setup. Required only for retail.
  

21 May 2004 Release 3.1.5.7

GENERAL:

• Corrected situation where losing connection during upload/download process would not cause the AutoProcessor to retry the transfer.
• Additional error handling and retry operations when hanging-up a RAS connection to processor.
• Provide Option to select if remote session is used as default gateway. Please see README file for details.

19 March 2004 Release 3.1.5.5

PAYMENTECH:

• Correct RAS dial-up problem under Windows NT 4.0. Would keep application from starting on NT4.
• Necessary phone book entry for RAS dialing was not always being entered into system. Work around was to do a download any which forced the phone book entry to be initialized.
  

16 February 2004 Release 3.1.5.2

GENERAL:

• Corrected a problem that could cause file writes to networked drives to fail in certain situations. Specifically, the AutoProcessor could incorrectly issue a "Can't find Export Directory' error or a logging error when either the export directory or the log directory were on a remote networked drive and the dial-up connection was active. This problem only exhibited itself when accessing remote drives using TCP/IP (such as Active Directory) and when explicit routing rules had not been set. The AutoProcessor now dynamically creates explicit network routes to the payment processor's FTP server, so that other network addresses are properly searched for on the local network.
• Added debug-level ability to write batch created for upload to disk in unencrypted format. This feature is available only in Demo mode.

PAYMENTECH:

• Ecommerce type indicator not being set properly. If the Transaction Class field (Class) was set to "ECommerce" either by a setting on the default dialog or importing an "E", and the ECommerce Type was set to "Merchant Default", either by a setting on the default dialog or by importing a "D", the Transaction Type transmitted to Paymentech would be a blank, or Merchant Default. This was determined to be incorrect (or perhaps just confusing) behavior. Have removed the "Merchant Default" setting on the Import Defaults screen for Ecommerce Type and also removed the ability to import a "D" (meaning Merchant Default) for the Ecommerce Type field. If transaction class is set to "E", the new version defaults to Non-SET Channel Encrypted which is the long way of saying you have received the transaction via HTTPS over the Web or via some other encrypted electronic mechanism.

24 December 2003 Release 3.1.5.1

PAYMENTECH:

• Problem reported when downloading batch from Paymentech that has 10 or more duplicate order numbers. If order numbers are not unique, CreditNow! adds a sequence number to the transaction. This process was failing in batches where more there were 10 or more duplicate order numbers.

24 November 2003 Release 3.1.4.1

GENERAL:

• Minor changes to improve backwards compatibility with 16-bit CreditNow! AutoProcessor.
• When a file is uploaded, the number of records, orders, and monetary amount for total, sales, and refunds is written to the log file. Also writes the name of the file as uploaded to Paymentech.
• Increased length of FirstName fields to 40 characters. Note: This does not increase the number of characters sent to Processor. Combination of LastName, FirstName, MiddleInitial is truncated to Processor specifications.
• Provide the Presenter ID (PID) field as export-only. (Paymentech)

8 Sept 2003 Version 3.1.3.3

  GENERAL:

• IMPORTANT: Possible data corruption problem fixed. Immediate upgrade recommended for all users. Environments that are doing simultaneous upload/download/import/export operations may experience data corruption problems. This has been addressed through improved threading of the encryption/decryption modules.
• Corrected bug in Indy TCP/IP module that would return a Socket Error #0 error when the remote host resets the connection rather than the proper Connection reset by peer message.
• Removed FTP directory scan. Previous versions scanned the list of files available via ftp at the processor's site to determine if the file was one that already existed in the CreditNow! database. The first block of each file was downloaded examined. This is no longer performed. Now, files on the processor's server that are marked for download (i.e., have the proper file extension) are downloaded and then examined. the reason we no longer scan the first blocks is that the method of terminating the download after the first block (sending an FTP ABOR message) is sensitive to the specific FTP implementation used on the server. Thus, CreditNow! would have possibly had problems in the future if the processor decided to change their FTP implementation. This potential future problem is now removed. Additionally, in the vast majority of production environments, all files on the server should be suitable for download. Removing the initial scan effectively speeds-up the overall download process.

FIRST NATIONAL MERCHANT SOLUTIONS:

• Initial release of First National Merchant Solutions BAS dial-up FTP interface.

PAYMENTECH:

• All file total accumulators now use 64-bit integers. Previously, total dollar amount allowed in a file was $21,474,836.47. Now supports the full 14-digits in the Paymentech 96-byte specification.

1 May 2003 Version: 3.1.1.27

• Initial release of Paymentech 96-byte Batch Format using dial-up FTP interface.