Revision History

[ADDED] Additional configuration check added to see if the 3D-Secure IFrame file is missing. This should help prevent problems when the person installing the software forgets to upload this file, or when they upload it the wrong place.

[UPDATED] References to “CVV number” changed to refer to “CV2 number”, in alignment with Sage Pay's usage of the term to refer to CV2/CVV codes/numbers.

[BUGFIX] Security check on 3D-Secure IFrame wrapper page was using a function not supported by Zen Cart 1.2.x. Compatibility code for Zen Cart 1.2.x added.

[BUGFIX] Payments/Surcharges define names were not able to be built correctly by stores using Zen Cart 1.2.x as, unlike Zen Cart 1.3.x, it doesn't store the language code in the session. Compatibility code for Zen Cart 1.2.x added.

[UPDATED] Documentation updated to add information for new version of My Sage Pay. Information for old version of My Sage Pay removed as the old version has been discontinued.

[ADDED] Additional security check added: 3D-Secure IFrame wrapper now redirects the user to the login page if they aren't logged in.

[ADDED] Module now checks if the database table name files are missing. This should help prevent problems when the person installing the software forgets to upload some files, or when they upload files to the wrong place.

[BUGFIX] Module was attempting to redirect back to an SSL version of the Zen Cart admin order page if SSL is enabled in the admin, whereas this page should only be used in non-SSL mode!

[BUGFIX] Configuration check was failing to recognise a test server as being in use when the module was configured to use the Sage Pay simulator.

[ADDED] Transaction Admin added! Integrates fluidly with the Zen Cart admin orders page, enabling stores to carry out many “Transaction Actions” directly within the Zen Cart admin.
Authenticated transactions can be Authorised (in full or in part) or Cancelled.
Deferred transactions can be Released or Aborted.
Orders can even be Refunded (in full or in part), or, if not yet settled, Voided.
With all of the transaction actions, the Zen Cart totals for the order can be automatically updated, as can the overall Zen Cart order status - a level of integration never before seen in Zen Cart!
The current status of the transaction is displayed clearly on the orders page to make it easier to know what could/should be done.
When a transaction action is performed, e-mails can be sent automatically, to inform the customer and/or the store's staff! (E.g. “We have refunded your card for the amount of ...”).
Security settings in the module's configuration allow the transaction admin functionality to be used by all the store's Zen Cart admin users or restricted to specific admin users.
A complete record of all transaction actions (including who performed them) is maintained and accessible through the transaction admin itself.
The interface of the transaction admin has been carefully designed to be as efficient and intuitive as possible. When an order is first displayed, a space-saving summary of the transaction information is shown, rather than the full admin panel, so the admin user can still see the order information on one page without having to scroll un-necessarily.
The transaction admin panel isn't included when the order page is printed, making printouts of the order page neater and clearer.

[ADDED] Full transaction recording added. The initial transaction is registered in the database before contacting Sage Pay and its progress recorded at any significant points along the way. This allows tracking of how far any incomplete transactions got, and as a consequence, for the possibility of linking up with cart recovery software to recreate an order which wasn't associated with a completed payment (although this hasn't been implemented in any way). The tracking also records details about the session, including a human readable-description, based on the customer's name, so a series of transaction attempts by a customer can be grouped together for easy analysis/trouble-shooting.

[ADDED] Support for multiple Sage Pay Go accounts added. Any number of Sage Pay Go accounts can be used with the module by configuring which currencies use which account (by specifying the currency/currencies and the Vendor Name for each account). This replaces the “Default Merchant Account Currency” and “Accepted Merchant Account Currencies” functionality used previously, which could only handle one vendor name being used for all currencies. The default currency is now simply the first currency defined in the list of “Merchant Account Accepted Currencies and Associated Vendor Names”.

[ADDED] Module now automatically selects itself as the current payment method whenever a customer enters any data or makes any selections in the payment form. Makes checkout that little bit quicker/easier for the customer!

[ADDED] Ability for customer to indicate that their card has no CVV number added back into the software. Includes run-time JavaScript functionality to dynamically add the necessary “indication” checkbox gadget to the form when the customer has filled in all other card details but not entered a CVV number. (Necessary for Laser cards as some do not have CVV numbers).

[ADDED] The card number and card CVV number fields are now highlighted whenever an error has been encountered and these sensitive details aren't being stored in the session, to make it clearer to the customer that they must re-enter the card number (and CVV number if it is being used).

[ADDED] Length of value entered for the card holder is now checked when JavaScript is disabled and an appropriate error message displayed.

[ADDED] Automatic database creation functionality added. Software will now automatically create its database table when it is being installed.

[ADDED] Automatic upgrade functionality added. Will be used to upgrade future versions of the software automatically. Also, when Ceon Sage Pay Direct 2.0.0 is being installed for the first time, it will upgrade any previous version of Sage Pay Direct or Protx Direct. The configuration for the old module will be copied across. All previous transaction information will also be copied across (from both previous modules' databases, if both are present!). The order database will then be updated to set Ceon Sage Pay Direct as the payment module responsible for all of the previous Sage Pay Direct/Protx Direct orders, so it will handle the display of payment information on the Zen Cart orders page. This means that the old modules can then be permanently removed, freeing up system resources!

[ADDED] New session description generation method added. Includes a lookup for the number of previous orders for the customer, so that the description can indicate which order number this for the customer (first, second etc. order by the customer, rather than the actual store order number).

[ADDED] New CeonBlowfishEncryption class, associated subclasses and Ceon PEAR basic functionality/compatibility class added. Ceon Sage Pay Direct no longer uses the PEAR library for encryption of sensitive card details, this new CeonBlowfishEncryption functionality is used instead.

[ADDED] Sample modified core file added to the distribution with code to fix a bug on Zen Cart's admin order page. Although not essential, it is advised to apply the fix as it makes the order admin work better. Without this fix the “Back” button may not work as expected!

[UPDATED] Option to store details in the session changed to being an option to store the “sensitive” details in the session (card number and CVV number). All other card details are now always stored in the session for the customer's convenience.

[UPDATED] Laser cards can only be used if the currency being used is Euros.

[UPDATED] All error messages for the data entered are now displayed. Previously just the first error was displayed.

[UPDATED] Module updated to pass the 3D-Secure parameters to the 3D-Secure IFrame wrapper and the 3D-Secure IFrame via session variables instead of query string parameters. This avoids the problem of poorly written/configured SEO software breaking the data being passed.

[UPDATED] Method of passing error messages changed to conform to new format for Zen Cart 1.3.9+ of using session variables instead of query string parameters. This avoids problems with the security changes implemented in 1.3.9+ versions of Zen Cart, which would cause a 406 error to be generated and a blank page to be displayed, anytime an error occurred and the module was trying to pass the message via the query string variable previously used for passing error messages.

[UPDATED] Debug functionality upgraded. The debug functionality no longer stops the user testing the site from checking out.. links are now generated and displayed so that, once the debug information has been made use of, the user can carry on within the checkout process, whether that is to go back to have an error displayed, or to go forward to the 3D-Secure page or the final success page.

[UPDATED] The checks against the transaction mode are now case-insensitive. This change was made solely to prevent problems with people using the wrong case for the value of this critical setting when integrating the module with software such as the (not too great) Zen Cart Multisite module.

[UPDATED] Format of Vendor Tx Code generated greatly improved. Default format is now “ZC - [Company/Customer Name - Customer ID - Customer Order ID | Admin ID] - uTime” (without spaces). This should make it much easier to identify transactions in My Sage Pay by simply looking at the Vendor Tx Code itself.

[UPDATED] Vendor Tx Code is now used as the index for the database table. No checks have been added to ensure previous uniqueness of data as it is likely that this will always have been unique due to the use of timestamps in the generated code.

[UPDATED] Default CSS style added to align 3D-Secure images to the right hand side of the 3D-Secure IFrame wrapper 3D-Secure intro/overview.

[UPDATED] Method of notifying the software that a debug link is being used updated so that the actual debug link itself must get used, rather than the user simply coming back to the same page. This prevents problems with the user not completing the checkout process after the debug link is used. If the user had then come back to the page after having left the checkout process, the software would wrongly think that the debug link was being used for the previous checkout session, which could cause the wrong order to be linked with a transaction. (This situation would only occur is user was performing strange testing, but it's better to have prevented this from ever happening again anyway!).

[UPDATED] Module updated to use new version of Ceon Payments Surcharges/Discounts module. Version 2.0.0+ of Ceon Payments Surcharges/Discounts is now required for the Surcharges/Discounts to work.

[UPDATED] Surcharges/Discounts functionality is now disabled in a fresh installation, so that an error (warning) message isn't displayed in the admin as soon as the module is installed if the Ceon Payment Surcharges/Discounts module isn't installed/enabled.

[UPDATED] Configuration options updated for new Blowfish encryption functionality. Unneeded options removed and encryption key option name/description updated to be clearer that it is do with Blowfish encryption and nothing to do with the payment gateway's encryption functionality.

[UPDATED] Some of the string “types” cleaned by the string cleaning method have been updated to allow additional characters to be used (not “cleaned”), in full accordance with the latest version of the Sage Pay Direct integration documentation.

[UPDATED] Card number and expiry date checks moved from separate class to confirmation pre-check method.

[UPDATED] JavaScript checks for length of card holder's name and the length of the card holder updated to fallback to check against default values if suitable values have not been entered in the Zen Cart “Minimum Values” configuration.

[UPDATED] Keys for configuration options and language defines, names of CSS styles and all variables' names changed to use “Ceon” namespace.

[UPDATED] Reference characters removed from method parameters in module's files as parameters are already passed by reference in later versions of PHP (Results in better compatibility with PHP 5.3).

[UPDATED] Last remaining uses of PHP's ereg functions migrated to using preg equivalent functions for full compatibility with PHP 5.3/6.0.

[BUGFIX] If an order had been placed using Ceon Sage Pay Direct and the customer went back to place another order without leaving the checkout, and if sensitive card details were being stored in the session, the software would wrongly try to decrypt the non-existent sensitive details from the previous order.

[BUGFIX] The code to determine whether or not the module was installed - and could therefore perform extra checks of the configuration - was missing some essential quotation marks!

[BUGFIX] The code to look up the two letter code for the state based on its zone_id was never running because of some leftover debug code.

[BUGFIX] The look-up table for US States was using the wrong capitalisation for the “District Of Columbia”, meaning it wouldn't match correctly.

[ADDED] New “Integration Process” and “Basic Configuration Guide” sections added to the documentation, to describe the entire process of setting up a Sage Pay Go account, as well as how to configure the Sage Pay Go account and the Ceon Sage Pay Direct module itself.

[ADDED] New “Transaction Admin User Guide” added to the documentation, including informative slideshows with screenshots and informational text.

[UPDATED] Installation documentation now has selective display technology to only display the steps necessary for the version of Zen Cart the store is using.

[UPDATED] Installation instructions and FAQs updated with information about configuring/fixing SEO software to work with the module.

[UPDATED] Installation instructions and FAQs updated with information about the “Back” button bug on the Zen Cart admin order page and information on how to apply the bug fix supplied in the sample modified core file.

[UPDATED] Installation documentation updated to stress the separation of the files for the admin from the files for the main store. Most Zen Cart stores have renamed their admin folder but some people were forgetting to check what the name the store's admin folder has before copying the files across. This should further reduce the number of people making that mistake.

[UPDATED] Configuration information and FAQs updated to remove information about PEAR/Blowfish, as it is no longer relevant. New “Temporary storage of card details” information has been added instead.

[UPDATED] Problems found with Sage Pay's protocol by Ceon. Module updated to conform to new protocol guide issued by Sage Pay.

[UPDATED] Initial release of Sage Pay Direct module, based on code from Protx Direct 3.8.1.

[ADDED] Support for Laser cards added.

[ADDED] Ability to independently enable and disable Sage Pay and Protx logos in the sidebox added.

[UPDATED] Issue number is no longer sent if the card type doesn't use issue numbers but the customer has mistakenly entered one (possibly because their previous card failed).

[UPDATED] Start date is no longer sent if the card type doesn't require a start date but the customer has entered one.

[UPDATED] Functionality to display message about problems with issue numbers/start dates removed now that the module handles the issue itself.

[BUGFIX] A default postcode is used if none was entered by the customer (which is possible for stores selling to the Republic of Ireland and possibly for other countries).

[BUGFIX] Error message encoding/decoding routines updated to better encode messages to be passed in the query string. urlencode() function wasn't doing the job it was expected to, which could cause problems with servers with strict controls on the format/legitimacy of query string parameters.

[BUGFIX] Module wasn't displaying the necessary warning if the module was using the Test server or the VSP Simulator.

[BUGFIX] Module was expecting any state entered manually to be a full name; updated to allow the use of two-letter US state codes as well.

[UPDATED] Support for version 2.23 of Protx's Protocol added. (US Addresses now require a two letter state code).

[ADDED] Option to disable Blowfish encryption added.

[ADDED] Information about switching off Blowfish encryption or storage of details in session added to admin and ConfigCheck class.

[ADDED] ID attributes added to all form gadgets to allow for custom styling of the payment form.

[UPDATED] Vendor Tx Code is now stored alongside every transaction so it can be used in REPEAT, REFUND transactions etc. Format of VendorTxCode parameter updated to make it more readable whilst remaining as unique as possible.

[UPDATED] FAQs completely rewritten to make them a lot more informative, usable and easier to comprehend. Lots more information about configuring servers for access to PEAR/Crypt_Blowfish added.

[ADDED] Module now automatically checks include paths against any open_basedir restrictions and displays the information necessary to fix a misconfigured server's access to its PEAR installation/Crypt_Blowfish files.

[UPDATED] FAQs updated in documentation with some more information about how to fix problems with a server's access to the PEAR:Crypt_Blowfish package.

[ADDED] Option to enable/disable storage of entered card details added. If details aren't being stored, encryption is not necessary.

[ADDED] Module now checks for ability of PHP installation to access PEAR library on the server, as well as its ability to access PEAR:Crypt_Blowfish.

[ADDED] Module now warns the user on the catalog side if the card details are being stored in the session but encryption can't be used.

[BUGFIX] Security problem fixed. A malicious customer was able to modify their cart's contents after having reached the 3D-Secure screen without the amount being billed being adjusted! Now any hack attempts are detected and the customer is returned to the first checkout page if they have attempted to “hack” the 3D-Secure checkout in this way. ALL USERS SHOULD UPGRADE!

[BUGFIX] Debug output now always outputs information about the open_basedir setting for the server. Previously this information was (wrongly) only displayed if safe mode was enabled.

[REMOVED] CVV Not Present checking functionality removed. CVV code is now always required.

[UPDATED] Encryption Keyphrase configuration option moved to the Security section and description updated to make things easier for new users of the module.

[UPDATED] FAQs updated in documentation with much more comprehensive information about how to fix problems with a server's access to the PEAR:Crypt_Blowfish package.

[ADDED] Ability for customer to indicate that their card has no CVV number added. Includes run-time JavaScript functionality to dynamically add the necessary "indication" checkbox gadget to the form when the customer has filled in all other card details but not entered a CVV number.

[BUGFIX] Algorithm to generate Shopping Cart Data to be sent to Protx rewritten. Previously it only used the shop's default currency and always included any tax in the shipping but reported the shipping as not containing any tax. It also didn't calculate the tax properly for products with attributes.

[BUGFIX] Module will no longer add products to the basket string being sent to Protx if it would breach the limit for the length of the string.

[UPDATED] Security issue identified with session clearing-functionality... all users should upgrade so that card details are cleared upon a successful checkout!

[UPDATED] Minor documentation updates, including information about adding an extra code snippet to file for Zen Cart 1.2.x.

[UPDATED] Documentation updated to use new display class for better on-screen rendering. Better print output formatting also added. (Tested in IE6-7, Mozilla 2.x and Safari 3.x).

[BUGFIX] Quotes were missing in the SQL for the module's status check. Could cause an error when a payment zone was selected and a non-numeric country ID encountered (which is very rare, occurs only when all the zones for a store have been deleted!).

[UPDATED] Code added to account for Zen Cart bug in zen_href_link() which wrongly appends the session ID to a static URL with an ampersand (&) instead of a question mark when there are no parameters for the URL.

[ADDED] Automatic 3D-Secure IFrame generation and handling added. Customer now stays within main layout of store and is given full instructions/information on what is happening, why it is happening and what they can/should do next. All browser technologies (IFrame support/Javascript support) are accounted for, with automatic fallback to simpler output if a particular technology is not supported/active.

[ADDED] Ability to set custom formats for the month and year select gadgets added.

[ADDED] Option to append model number to product's description in cart details sent to Protx added.

[ADDED] Module now automatically disables itself if a configuration problem is identified.

[UPDATED] Error handling improved by including checks for specific error codes in returned status detail.

[UPDATED] Module now allows usage of normal HTML tags for error messages due to new support of error message encoding.

[UPDATED] Check for Surcharge/Discount rate updated to cope with type conversion problems on misbehaving servers.

[UPDATED] Documentation updated with details of the recommended 3D-Secure rule to be added in the VSP admin.

[UPDATED] Documentation updated with more information about what to do when module doesn't appear on the store catalog side.

[BUGFIX] Colons and commas are now stripped from the names of products sent to Protx as part of the shopping cart summary information.

[BUGFIX] The response code was not handled properly for a successful transaction when the Transaction Mode was set to Authenticate.

[UPDATED] Format of amount being sent to Protx locked down to use 2 decimal places regardless of the currency in use.

[UPDATED] Module updated with URLs for Protx's new systems.

[UPDATED] Support for new test card numbers and AVS/CV2 test values added.

[ADDED] Icons added for 3D-Secure message page.

[ADDED] Support for new Authenticate Transaction Mode added.

[REMOVED] Support for old Pre-Authorisation Transaction Mode removed.

[ADDED] “Cards Accepted” sidebox added to allow dynamic display of accepted card types even before the checkout stage.

[UPDATED] A warning is now displayed when one of the test Transaction Modes is being used.

[UPDATED] Documentation (FAQs) updated with information about manual installation of the necessary Blowfish encryption files.

[ADDED] Version information section added to Admin to aid identification of the currently installed version of the module. Also allows online version checking through use of “Check for updates” link.

[BUGFIX] Code added to clean up the descriptions of line items when information about the cart's contents are sent to Protx. Should avoid any parsing problems due to illegal characters.

[UPDATED] Documentation updated with instructions on how to download the latest version of the module.

[BUGFIX] Warnings if user has safe mode enabled fixed by checking if safe mode is enabled. However, as a result, communication time with Protx is then reduced to 5 seconds less than the script's max_execution_time, increasing the risk of timeouts. Safe mode is not good, disable it if you can and harden your server in better ways! :)

[BUGFIX] Major bug in 3D-Secure handling fixed. Protx tech support completely messed up in their definitions of what should occur for particular response status codes (despite repeated requests for clarification). The proper way for things to work has now been identified by them and the module updated to work accordingly. (This bug affected orders with 3D-Secure-enabled cards for which the customer had entered incorrect details).

[ADDED] The “Status” information for a completed transaction is now displayed alongside the other order information in the admin.

[ADDED] Notes about some of the possible 3D-Secure Statuses added to the FAQs.

[UPDATED] The details of the cart's contents are now sent to Protx with a restriction on the number of decimal places used for prices, determined by the number of decimal places the order's currency uses.

[UPDATED] The text for an “INVALID” response from Protx is now more customer-friendly.

[BUGFIX] Small bug in multi-currency handling found and fixed. (No-one reported any problems but good to have found this for preventative reasons).

[UPDATED] Documentation about the module's comprehensive multi-currency support rewritten to make it easier to understand.

[BUGFIX] Added code to make sure no invalid characters can become part of the Vendor TX code.

[UPDATED] Surcharges/Discounts notes updated to represent additional “Percentage plus Specific Value” option for surcharges (option is not available for discounts though!).

[UPDATED] Documentation reworked into multiple files. Ready for release!

[ADDED] Checks for database existence/integrity added to Languages Definitions file so warning and instructions can be output in Admin if necessary.

[ADDED] Information and advice about 3D-Secure functionality added to documentation.

[REMOVED] Ability to store full Card Number removed as it is unnecessary for Protx Direct; number with middle digits masked is stored for reference purposes only.

[UPDATED] References to “Delta” changed to “Visa Debit” as this is the official/proper name for these cards now.

[UPDATED] Card icons updated/added for Visa, Visa Debit, Visa Electron, MasterCard and Maestro.

[UPDATED] Configuration settings re-ordered slightly for more logical grouping.

[BUGFIX] URLs for Live and Test transaction modes fixed for 3D-Secure.

[BUGFIX] The card details were dropped after a 3D-Secure redirect. They are now stored temporarily (with the card number obfuscated and CVV missing) so they can be recorded alongside the other order details upon order creation.

[BUGFIX] Format of SQL upgrade patch updated to allow automatic prepending of table prefix.

[ADDED] Full support for 3D-Secure (“Verified by Visa”/“MasterCard SecureCode”) added.

[ADDED] Surcharge/Discount support added.

[ADDED] Full support for Protx's various types of error messages added. Error messages are now much more specific and therefore quicker/easier to understand and respond to.

[ADDED] Details about the shopping cart's contents can now be sent to Protx. Enabled by default.

[UPDATED] References to “Switch” have been removed... As of 30th June 2007, “Switch” will have become “Maestro”.

[UPDATED] Full support for Maestro Cards is restored in version 3.0.0, courtesy of its 3D-Secure support.

[BUGFIX] An attempt to send delivery address details to Protx is no longer made if the cart consists solely of virtual products.

[BUGFIX] Critical bug found/fixed in version 2.2.0, includes/modules/payment/protx_direct.php, which caused incorrect AVS/CV2 value to be sent to Protx. All users of 2.2.0 must upgrade!

[ADDED] Ability to specify message about problems with Start Dates/Issue Numbers for particular cards added.

[ADDED] Configuration checks added to Languages Definitions file so that any currency configuration issues/conflicts can be highlighted in the admin.

[ADDED] Option to get the IP address used by the store's server added to help with the configuration of the VSP admin.

[UPDATED] Support for Switch/Maestro dropped for version 2.x as the changeover from Switch to Maestro in June 2007 means that Maestro cards will require 3D-Secure verification. Version 3.0.0, having full 3D-Secure support, will have full support for Maestro cards.

[UPDATED] Admin configuration keys kludged to implement nicely laid out configuration sections. Should help make configuring the module even clearer!

[UPDATED] Communication settings updated to allow for longer timeouts when contacting Protx and for verification of Protx's SSL host.

[UPDATED] Documentation updated to add a Configuration Section and to detail the new features.

[UPDATED] Length of Encryption Keyphrase restricted to 56 characters.

[BUGFIX] An attempt to send the delivery address is no longer made for orders which consist entirely of virtual products.

[BUGFIX] Handling of Protx's response updated to parse the data more reliably (as the response can be Base64 encoded, equals signs can be part of the actual value for a key/value pair).

[BUGFIX] In Zen Cart 1.2.x only, snippet of code used to clear sensitive data from session incorrectly cleared data when updating the shopping cart's contents; should not clear data if user is already in the checkout process! Documentation/snippet updated accordingly.

[BUGFIX] Tests were being made against the POSTed values of CVV Number, Start Date and Issue Number even if these options weren't enabled.

[UPDATED] Removed the form_action_url property as it was not used by the module.

[UPDATED] Documentation updated to give more accurate information for Zen Cart 1.3.5.

[UPDATED] The Language Definitions file has been extensively updated to use “Credit/Debit Card” where appropriate, rather than using “Credit Card” exclusively all the time.

[UPDATED] “UK Maestro” is now identified simply as “Maestro”.

[UPDATED] The Card Type on the Confirmation page now uses full text rather than Protx's Card Type codes.

[UPDATED] FAQs have been added the documentation due to the increasing volume of e-mail about particular issues.

[BUGFIX] The Debug Mode was ignored if an error occurred during the cURL transaction, now it runs and outputs correctly.

[BUGFIX] The Contact Us links in error messages didn't link to the correct address.

[UPDATED] The changeover from Switch to Maestro means that some Switch cards have issue numbers while others don't. Also, some have a Start Date while some don't. The module has been updated to therefore display both these fields but require neither. This should mean that every possible variation of fields used is once again catered for!
Please note that this means that the omittance of a required Start Date or Issue Number field can no longer be checked for, using Javascript, before sending the payment details, as the individual banks only report a Requirement Error after sending the data through Protx. Of course at this point, if the customer has not supplied some required information, they will then be shown an appropriate error message and asked to supply this missing information, so no business will be lost! :)

[UPDATED] Documentation slightly updated for changing Shopping Cart link(s) to use SSL.

[UPDATED] Debug Information's layout improved. Information now includes whether Encryption was used and, if not, the include_path and safe_mode/open_basedir settings for the server.

[BUGFIX] Extraneous comma removed from HTML for Issue Number field.

[ADDED] Option added to disable browsers' Autocomplete functionality for the CVV field (if this field is being used).

[UPDATED] Documentation updated with information about Known Issue when Terms & Conditions checkbox is being used.

[BUGFIX] Extraneous comma removed from HTML for CVV field.

Many updates and improvements!

[ADDED] Icons for each Credit Card accepted can be displayed if option is enabled in admin.

[ADDED] Option added to disable browsers' Autocomplete functionality for the Credit Card Number's field.

[UPDATED] Dynamic Start Date and Issue Number support added.

[UPDATED] Use of Protx's Test Server added to list of Transaction Modes.

[UPDATED] Warning added in Admin if not using Blowfish Encryption.

[UPDATED] Encryption Keyphrase now set in Admin, setting value in file no longer necessary!

[UPDATED] All text output is now defined in the language file (Credit Card names were hard-coded previously).

[UPDATED] Module split into two versions, one for Zen Cart 1.2.x and one for Zen Cart 1.3.x

[ADDED] Debug Mode added.

[ADDED] Warning added for catalog if Debug Mode is enabled (ZC 1.3.x only).

[BUGFIX] If this Protx Direct module was installed after a different Protx Direct module, minor warnings would be displayed when attempting to view orders which were processed by the other module. These warnings are no longer displayed as they can be safely ignored.

[BUGFIX] Documentation updated with information on how to prevent Credit Card Details from being wiped when editing the Shopping Cart on a server using SSL. (Those not using SSL are unaffected).

[ADDED] Information on Known Issues added to Documentation.

Initial Release