CN!Express CX-6000 AutoProcessor

Change log for CN!Express CX-6000 AutoProcessor.

10 November 2007: Version 3.6.9.1

CHASE PAYMENTECH SOLUTIONS:

• PTI34 Orbital Gateway specification requires AmountDetails on refund transactions, although not specified in DTD.

• CPS says ECOrderNum and OrderID need to match. We had used TransactionDBID for one and OrderNumber for the other.

June 6 2007: Version 3.6.7.1

GENERAL:

• Address problem of overlap between Switch/Solo and some Visa cards. CN!Express mistakingly identified some Visa cards as Switch/Solo cards. This occurred because there is an overlap in the account number for these two card types. Now always defaults to Visa.

May 7 2007 Version 3.6.6.1a

GENERAL:

• Able to turn on logging from within program. No longer any need for external utility.
• Reviewed all logs to ensure account number and CVV2/CID values never appear in logs -- including debug logs.
• Updated PABP documentation.
  

CHASE PAYMENTECH SOLUTIONS:

• Updated to latest XML specification.
• Support for full AVS functionality.
• Support for European Direct Debit as method of payment.
• European Direct Debit requires the following fields: EDD Bank Sort Code, Alpha-Numeric, 10 characters
• EDD Country Code, Alpha-Numeric, 2 characters
• EDD RIB Code (Releve Identité Bancaire), Alpha-Numeric, 2 characters
  

13 February 2006 Version 3.6.5.3

GENERAL:

• Better handling of failed Ship transactions. When a ship transaction fails (due, for example, to a timeout or network error, it now maintains the internal Ship information that needs to be transmitted to the processor. Previously, this information would have been removed and an attempt to resubmit the transaction fail.
• Better support for split shipments using Auth/Deposit and Hold/Ship transactions. Two Deposit/Ship transactions for the same Auth/Hold transaction can now be processed in sequence. Previously, if the two Deposit/Ship split shipment transactions were submitted at the same time (either in two files right behind each other or in the same file), the second transaction would fail because the internal information required to be transmitted to the processor was not available. Now the split shipment is noted at import time and a new internal tracking transaction is created that contains the amount remaining on that authorization. For example:
• Process a Hold transaction for $50.00.
• Ship $30.00 of that transaction.
• An internal tracking transaction now exists for $20.00.
• Ship $20.00 of that transaction.
• Transaction successful.
• One known problem with this approach is, if the first split-shipment transaction in the example above should fail (network errors), you now have two tracking transactions in CN!Express: one for $30 and one for $20. You need to resubmit the $30.00 ship transaction. You cannot just submit a transaction for the original $50.00.

• Corrected a range-check error in third-party database code. Problem is related to large ActivityLog databases over 2 GBytes. Merchant should archive on a regular basis. Large table sizes lead to slow start-up times. Future versions of the CN!Express AutoProcessor will have a built-in archiver. Additional testing will now be done at the 4 GByte file size.
• Switched to RSA-style dynamically-generated key exchange to encrypte communications between the Viewer, Capture Manager, and AutoProcessor. Previously, a hard-coded encryption key was used.
• The Field reference now works properly with non-Internet Explorer default browsers. There were previously problems with directory paths containing spaces.
• Identified problem in third-party compression library used for communication between Viewer, Capture Manager, and AutoProcessor. Turned off compression in communication channel.

20 June 2005 Version 3.6.4.5

GENERAL:

• Corrected small memory leak.

PAYMENTECH:

• Improved handling when empty HTTP response is received from Paymentech Orbital Gateway. AutoProcessor version 3.6.4.2 (October 2004) added an automatic retry whenever an empty HTTP response is received. IN the rare instance where the Orbital Gateway did not return the proper response on retry, CN!Express AutoProcessor considered that to be a severe error and proceeded to stop processing the rest of the transactions in a multi-transaction batch and exported any unprocessed transactions as declined with the error "Empty response from gateway." This has been changed so that an empty response after the first retry is no longer considered a severe error. Only the transaction that received an empty HTTP response twice is marked with 'Empty response' and further transactions in a multi-transaction batch are processed. PLEASE NOTE: All transactions with the Orbital Gateway that are marked as timeout or received blank response need to be checked on the Paymentech Virtual Terminal to determine whether or not they were processed.
  

18 February 2005 Version 3.6.4.4

GENERAL:

• CN!Express Service Manager, the utility that installs CN!Express AutoProcessor as a service, now runs properly under Windows 2003 Server.
• Better handling for large volume of files. Previous releases always did a 'find first' to get the next file in the directory. In a high volume environment, it was possible for a transaction to never 'rise to the top' to be processed. Transactions could be processed out of turn. CN!Express now creates a list of all available import files, sorts them by date/time, and then picking the next file by reading the name off the list. When the list is empty, CN!Express loads up all available names into the list and continues. This change ensures earlier transactions are always processed first.
  

      November 10 2004 Version 3.6.4.3

GENERAL:

• Config report dialog text field was not resizing properly when dialog was resized.
• Import files were not always being opened in read/write exclusive mode.
• Fixed problem when updating two-year old databases. Field was referred to as BCD vs F loat.

October 28 2004 Version 3.6.4.2

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 the operation and 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 reject file.
• If a country is not provided on import, send a blank to the processor rather than assume it is US. Sending a blank is preferable to sending a default country.
• If the IP address of the server changed while CN!Express 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.
• "Z-Ship" transactions would think a credit card transaction was an electronic check transaction if the bank routing number column was imported -- even though the routine number was blank. A database query needed to be modified to properly handle a blank as well as a null bank routing number field.
  

PAYMENTECH:

• Automatically retry one time after receiving blank HTTP response from Orbital Gateway. The Orbital Gateway occasionally returns a valid, but blank HTTP response. (This behavior has been reported to Paymentech.) When CN!Express AutoProcessor receives a valid but blank response from Paymentech, it automatically performs one retry before returning a blank response error. We have found that the transaction has usually been processed even though a blank response was received. The retry contains the proper duplicate-tracking ID in the HTTP header so the retried transaction is seen as a duplicate by the Orbital Gateway. The transaction information does seem to be reliably returned on the second attempt. NOTE: this does not seem to be related to timeouts. The AutoProcessor does receive a response.
  

October 4 2004 Version 3.6.3.6

GENERAL:

• Added feature to allow custom export plug-ins.
• Released first custom export for customer.

September 14 2004 Version 3.6.3.5

GENERAL:

• IMPORTANT: Non-digits are no longer stripped from account numbers on export. In previous releases an account imported as 4111-1111-1111-1111 would export as 4111111111111111. Now the export matches the import string. Note: Non-digits are still stripped before being sent to the processor.
• Cosmetic: In Configuration report, Import columns without an assigned name appeared in the report as #001. Now says (unassigned).
• This release tested under Windows XP Service Pack 2.
• Transactions Authorized with CN!Express can now be captured/deposited with 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. This functionality requires the following product versions:
• CN!Express 3.6.3.5
• CreditNow! 3.1.6.2
• See processor-specific information below for details.
• See below for Firewall configuration information.

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:

• AVS was being sent twice in two different branches of the XML. This confused the Orbital gateway and resulted in higher Interchange rates.
• 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

February 16 2004 Version 3.6.2.6

FNMS & Paymentech:

• Processor-specific transaction information obtained during the original Authorization transaction was not being added to later Void transactions.
  

December 11 2003 Version 3.6.2.5c

• Corrected problem in QuickPrint DLL.

November 17 2003 Version 3.6.2.5

• XML data was not being properly escaped. An '&' or '<' character in a field would cause improper XML data to be created. Several merchants reported this as a problem when they put text such as 1356&3422 in an order number field.
• Viewer now provides better explanatory message on log-in errors.

October 06 2003 Version 3.6.2.4

•  Allow blank and 00/00 expiration dates for Paymentech Orbital Gateway.

 September 09 2003 Version 3.6.2.3

• Support for Chase Merchant Services through FDMS South Platform (NABANCO) over Datawire IPN
• Support for First National Merchant Services PayFuse.

March 31 2003 Version 3.5.3.1

• CN!Express is proud to be the first product to be certified for the new Paymentech Orbital Retry/Duplication Detection functionality. (Version 1.00 dated Feb 26, 2003)

March 01 2003 Version 3.5.2.62

• Restrict user from setting Import and BatchImport directories to same directory. Would cause file to be imported multiple times.
• General improvements in multi-threading.
• Support default currency per Merchant ID.
• Optional Merchant ID aliases.
• When AutoProcessor loses communications with the import/export folders it retries connections every few seconds. Useful when import/export folders are on remote system and remote system has been rebooted.
• Option to start in Paused mode. Requested by customer using AutoProcessor in automated environment where they reboot their web server 2x a day. Allows automated scripts to clean up any transactions they may have had in process before restarting processing.
• Option to clear all pending single-transaction imports on start-up. Requested by customer looking for Paused mode. See readme file for documentation.
• Improved support for offnow.cn! and onnow.cn! files to pause and resume processing programmatically. Files can be put in the Import or BatchImport directories.
• Added LastActionSucceeded to far-right of default template. LastActionSucceeded indicates whether the transaction was successful or not. Extremely useful in automated situations since the interfacing software can check a single flag and not have to interpret result codes.
• Support ICVerify(r)-style import/export files.
• Viewer now shows recent history when first started vs showing only events occurring after Viewer starts.
• Various UI and code-review improvements.
• Documentation for all fields (per Processor) is available on-line through the help menu.
• Updated documentation.

December 2002 Version 3.5.2.38

• Initial Release of CN!Express® CX-6000® AutoProcesor supporting Internet protocols.