Upgrading to 4.1.3 Build 1186

From Payment Processing Software Library
Revision as of 10:06, 4 December 2014 by Admin (Talk | contribs)

Jump to: navigation, search
This article is part of the
Payment Processing Software Library

Categories

Get it...

Credit Card Software
Download

Install it...

Installation
Upgrade & Migration

Connect to it...

Point Of Sale Integration

Set it up...

Quick Start Guide
Setup
Processor Setup

Licensing

Learn to use it...

Manual & User Guide
Knowledge Base
Frequently Asked Questions
Compliance Guide
Merchant Account Rates
User Interface Guides

Fix it...

Errors & Troubleshooting
Knowledge Base
Corrupted Install Repair

Get Help...

Contact
Processor Support Contacts

More Info ...

Glossary
Articles

See also...

911 Software
Help

CreditLine Payment Processing Software Upgrading to 4.1.3(SP3) Build 1186 PCI 2.02. This site can also be reached at http://docs.911software.com

Looking for better rates?   Get a Free Credit Card Processing Cost Comparison!

Preparation

  1. Make sure to batch out everything before upgrading, to avoid journal corruption.
  2. Stop the CreditLine service and all the CreditLine applications.

Upgrading from 4.1 Build1102 (PCI 1.0) to 4.1.3(SP3) Build 1186 (PCI 2.02)

The following is a list of important changes to take note of.

Strong Encryption and Possibility of Data Loss

Due to heightened security, the following may cause a loss of data and corruption of the journal:

  1. Running CreditLine Manager and CreditLine Server on different PCs. Please, run the Manager on the same PC as the Server. See #CreditLine Manager and Server Location
  2. Transferring the journals to another PC and batching it there without the security keys, or failing to transfer those keys back after the operation
  3. Upgrading from the older version without batching out all outstanding transactions
  4. Reinstalling or repairing the version without batching out all outstanding transactions.
  5. Running an older version of the DLL with the new version of server

Integration Considerations

Make sure to use and test the latest DLL. Statically linked software products will need to recompile. Contact your software dealer, if in doubt. The new DLL has to be propagated to all terminals/clients.

CreditLine Manager and Server Location

Until further notice, CreditLine Manager and CreditLine Server must be run on the same PC. This has to do with the security keys. We are working to eliminate this restriction. Until then, you would need to remote into the server or work locally on the server to operate CreditLine Manager.

Settlement at a Different Location

There are some cases when settlements are completed at a store other than the one, where the original auth transactions are performed (for instance, in the case of a dealer troubleshooting the setup) Because of PA-DSS, each CreditLine server is required to maintain a set of unique key tables (DataEncryptingKey, KeyEncryptingKey). In this case, only the corresponding key tables can decrypt the transaction data encrypted in CCV_JOR.dat file. Therefore, DataEncryptingKey.ini and KeyEncryptingKey.ini files are needed to be put in the same data folder as CCV_JOR.dat. Please, also to move the key tables after End-Of-Day Batch back to the original store. It is important to always synch the key tables and the JOR files.

MasterCard Mandate

This version has implemented the ‎MasterCard Unique Lane ID/Terminal ID Mandate. We have worked with the processors to comply with the Mandate. Some processors received an extension from MC or instructed to continue with the old protocol, due to their internal understanding with MC.

Vantiv/Fifth Third Bank MC Mandate

Vantiv 5/3rd Bank is the only processor that requires additional steps to be compliant at the moment. If you are using Vantiv, please see Vantiv Fifth Third Bank Setup for this processor specific Lane ID/Terminal ID setup instructions.

Dealer Mode

Dealer Mode is deprecated for security reasons. An improved procedure for resetting passwords and enabling TraceMode is specified below.

Resetting Passwords

A new procedure for securely resetting passwords is specified here: Reset Password

Trace Mode

A new procedure for securely temporarily enabling the TraceMode is specified here: TraceMode

Key Rotation

Per PA-DSS, each CreditLine server is required to maintain a set of unique secure key tablesThese key tables need to be updated every 90 days. Not updating key tables will not block payment processing. See Key Rotation for complete info

Import

Import file now needs to be encrypted. Please, see CreditLine_Import/Export#Import for the simple procedure.

Export

Export is deprecated. A new function, called Re-Auth eliminates the need for Export.

Re-Auth

A new function, Re-Auth, is introduced to replace the old Import+Export functionality.