Docstoc

MKT Credit Card Version 7

Document Sample
MKT Credit Card Version 7 Powered By Docstoc
					MKT Credit Card Version 7.0 Release Notes
This document describes the changes that have been performed to MKT Credit Card
Processing Add-on for each specific release.

Supported AccountMate Versions
Determine your AccountMate version before using the MKT Credit Card Processing Add-on.
Check our web site to get the latest information about supported versions and product
updates.

The following AccountMate versions are supported by MKT Credit Card Processing:
    •    AccountMate SQL/MSDE Version 6.04a through Version 6.07a
    •    AccountMate SQL/MSDE Version 7.02a through Version 7.05a

If you have a version that is not listed above do not use MKT Credit Card Processing Add-on
against your company data and contact our Technical Support staff at
support@tamlinsoftware.com or call us at 214-739-6576.

If you have any questions regarding the changes listed in this document please contact our
Technical Support Department support@tamlinsoftware.com or 214-739-6576.

Build 1009 (09/25/2009)
• Control # [109317] (Fixed)
   • Credit Card Setup Test button will give an error about EncryptVAMCard not found
   • Credit Card Processing screen will always say that a new Card # entered is invalid

Build 1008 (09/21/2009)
• Control # [109287] (Fixed/Enhanced)
   • Corrected Alias not found issue that could possibly occur during Ship Sales Order if the
       credit card transaction failed
   • Corrected the Credit Card Processing screen issue that does not properly display the
       selected credit cards information if the user selected the card using the drop down list.
   • Enhanced the Credit Card Processing data entry screen so that unencrypted card numbers
       are not shown on the screen, except when the user types in a new credit card number.
       However after they enter the credit card number it is immediately encrypted and will
       never be shown in plain text again. This change has been made to ensure compliance with
       PCI regulations.
   • Enhanced the Credit Card Processing data entry screen so that the credit card Security # is
       never shown after the initial data entry. This change has been made to ensure compliance
       with PCI regulations.




5646 Milton St Suite 540 Dallas, TX 75206 214.739.6576 Fax 214.739.7963 www.tamlinsoftware.com
MKT Credit Card Version 7.0 Release Notes

Build 1007 (07/03/2009)
• General
   • Added support for AccountMate SQL Version 7 Build MS704a
   • Added support for AccountMate SQL Version 7 Build MS705a
• Control # [108284] (Fixed)
   • Credit Card Transaction Log may show a transaction as successful even thought it failed
   • For AccountMate Version 6.5 users, the encrypted Credit Card would appear with twelve
       (12) X’s instead of 11.
   • For AccountMate Version 7 users, the Credit Card Refund screen was updating the Bank
       Reconciliation module; this was a carry forward from AccountMate Version 6.5 and is no
       longer necessary. This posting would actually create a duplicate entry in the BR module
       and would cause extra steps for reconciling the banks.

Build 1006 (03/06/2008)
• Control # [106230] (Fixed)
   • If the Expiration Date is typed into the Payment/Bill To/Ship To tab of the Sales Order or
       Invoice screen it will not default onto the Credit Card processing screen.
• Control # [106231] (Enhancement)
    •    Previously the system always required the user to enter a Card Holder Name.
    •    There is now a setup option called “Require Card Holder Name”, if marked the
         user must always enter a name, if not the user can leave the field blank
•   Control # [106232] (Fixed)
    •    The Refund to Credit Card function could become confused if a Sales Return
         created through the “Create Sales Return with Invoice #” function referenced an
         original Invoice # that had been paid by more than one credit card transaction.
    •    This would result in a decline message.
    •    The function will now repeat the sales return for each credit card transaction
         instance. The amount shown on each row will depend on the credit card
         transaction amount. For example, if a original sales Invoice for $100.00 received
         two credit card transaction payments, one for $60 and the other for $40. Then a
         Sales Return was entered returning $70 of product. The refund screen would show
         one row for the sales return with an open credit amount of $60 and another row for
         the sales return with an open credit amount of $10. To refund the entire sales
         return the user will have to process the refund twice in this example.
•   Control # [106233] (Fixed)
    •    Previously the Credit Card Processing setup screen would not allow the user to
         confirm the screen if there were any RMA Orders or sales order shipments not yet
         invoiced that used a Pay Code authorized to be used for credit card processing.
    •    This old data restriction has now been removed




5646 Milton St Suite 540 Dallas, TX 75206 214.739.6576 Fax 214.739.7963 www.tamlinsoftware.com
MKT Credit Card Version 7.0 Release Notes

Build 1005 (02/02/2008)
• Control # [105989] (Enhancement)
   • Added support for credit card swipe readers on the Credit Card Processing screen.
       • Only Track 1 is read from the card
       • The software will read the Card #, Expiration Date, and Card Holder Name
• Control # [105988] (Fixed)
    •    If a user selects to fully apply all open credits to a sales order or invoice
         transaction and the total of the open credits exceeds or equals the total of the order,
         the user will receive an update conflict message when they try to save the order.
         This issue affected the following functions:
         • Create Invoice
         • Ship Sales Order
         • ACCU-DART SO Ship Goods and SO Ship with Cartons
•   Control # [106005] (Fixed)
    •    Cash Receipts created during may not contain the Credit Card # in the Chk/Card
         field. This issue affected the following functions:
         • Create Invoice
         • Ship Sales Order
         • ACCU-DART SO Ship Goods and SO Ship with Cartons
•   Control # [106006] (Fixed)
    •    When an open credit is applied during the credit card transaction process the
         customers balance and open credit fields are not properly updated

Build 1004 (12/27/2007)
• Control # [105798] (Enhancement)
   • Extracted source code hidden in the MKTCC.EXE program into a new
       MKTCCMOD.VCX class library file.
   • This change will allow AccountMate Business Partners to modify how the MKT Credit
       Card application loads inside specific screen forms and program files.
• Control # [105799] (Fixed)
    •    When upgrading from one MKT Credit Card build to another and apply credit
         information has been used with previous sales order transactions an error regarding
         an invalid variable LNHANDLE will occur.




5646 Milton St Suite 540 Dallas, TX 75206 214.739.6576 Fax 214.739.7963 www.tamlinsoftware.com
MKT Credit Card Version 7.0 Release Notes

Build 1003 (11/28/2007)
• Control # [105659] (Fixed)
   • Void Payment and Refund to Credit Card functions may indicate the wrong credit card
       number if a rare data condition exists in the Credit Card transaction log. The rare data
       condition is caused by the issue corrected by Control # 105660.
   • NOTE: This issue only exists in AccountMate Version s 7.2 and 7.3
• Control # [105660] (Fixed)
   • Apply Payment screen may generate an error stating that the object TFRMTBR does not
       exist. This occurs only if a credit card decline occurred while saving the payment. When
       this occurs and the user attempts the exact same process again for the same customer each
       subsequent attempt will add a record with the same Transaction # to the Credit Card
       Transaction Log.
   • NOTE: This issue only exists in AccountMate Version s 7.2 and 7.3

Build 1002 (10/05/2007)
• Control # [105420] (Fixed)
   • Retries setting should allow an option for (0) zero retries
   • If a credit card transaction was declined the message indicating that the card declined and
       the reason would not show, instead a simple message indicated that the transaction failed
       was provided. The only way to see the reason for the decline would be to run the Credit
       Card Transaction Log report.




5646 Milton St Suite 540 Dallas, TX 75206 214.739.6576 Fax 214.739.7963 www.tamlinsoftware.com
MKT Credit Card Version 7.0 Release Notes

Build 1001 (09/25/2007)
• General
   • Added support for AccountMate SQL Version 7 Build MS702a
   • Added support for AccountMate SQL Version 7 Build MS703a
• MKT Credit Card Processing Setup Screen
   • Activation Tab
       • A product key is now required to activate MKT Credit Card Processing. Future add-
           on options such as Data Level III can only be activated by installing the appropriate
           product key
       • The product key will also be AccountMate version specific.
   • Account Tab
       • Added a secondary backup URL. If entered and the system cannot connect to the
           primary URL the system will attempt connection through the secondary URL See the
           Settings tab for additional communication options.
       • Bin (Center) ID was added for future processors that require the indication of which
           processing center your account has been assigned too.
   • Settings Tab
       • The Data Level option allows you to select if Data Level II or Data Level III
           transactional information will be sent to the processor. MKT Credit Card Processing
           always transmits a minimum of Data Level II. Data Level III will be available on a
           future release and requires an appropriate product key to be entered.
       • Save Credit Card Security # will now issue a new warning. New Credit Card
           Processing regulations prohibit the saving of Card Security Values for use on new
           transactions. You are allowed to continue to save this information, but doing so is
           against current regulations and is not recommended.
       • Retry Attempts now allows the system to be setup to retry a credit card transaction
           several times. This is helpful for installations that do not have stable internet
           connections.
       • Timeout Period instructs the system how long to wait for a response from the credit
           card processor before indicating that the transaction has failed.
       • Transmit XML is a display only checkbox, that depending on the processor would
           indicate if the transactions are submitted in XML.
       • Authorized Pay Codes provides a way to tell the system specific pay codes that can be
           used for credit card processing. See Authorized Pay Codes fully described below for
           more information.
• Authorized Pay Codes
   • The system has now been changed to handle Pay Codes differently.
   • Previously, any Pay Code that was a Credit Card type and was marked to “Automatically
       Apply” could be used by the MKT Credit Card Processing system.
   • Now, only those Pay Codes listed in the MKT Credit Card Processing Setup screen can be
       used. Furthermore, only Pay Codes set to a Credit Card type and that are not marked to
       “Automatically Apply” can be used.
   • These changes were necessary to facilitate a change in how credit card transactions are
       processed and the AccountMate data is updated. See Credit Card Processing Changes
       below for more information.
• Credit Card Processing Changes
   • These changes only affect the Ship Sales Order, Create AR Invoice, and the ACCU-
       DART Shipment modules.




5646 Milton St Suite 540 Dallas, TX 75206 214.739.6576 Fax 214.739.7963 www.tamlinsoftware.com
MKT Credit Card Version 7.0 Release Notes
    •    Previously a credit card transaction was processed just before updating the AccountMate
         data and committing its transactions to the SQL Server. We have found this to cause
         some problems if for some reason AccountMate could not save the transaction such as
         performing the “Ship Sales Order”. When the AccountMate transaction failed to save, a
         condition would occur were the customers credit card would be charged but no record of
         the charge in the Cash Receipts report would be listed. Please note that a record of the
         charge would always be present in the Credit Card Transaction Log.
    •    The system now processes credit card transactions differently. Before attempting to
         update (save) the AccountMate transaction the credit card will be processed and a Cash
         Receipt will be written into the system. Then AccountMate would be allowed to continue
         with its standard processing. The actual sequence of events is listed below:
         • Write Cash Receipt Record
         • Process Credit Card
         • If the Credit Card was processed, update the cash receipt record to show the Approval
             Code in the Pay Reference Field
         • If the Credit Card could not be processed, void the cash receipt
         • Next, list the Cash Receipt Open Credit as a credit to be applied to the resulting
             invoice when it is saved.
         • If processing Sales Order Shipments and the AccountMate transaction failed to save,
             the Credit Card transaction now a open credit, is already marked to be applied to the
             next invoice generated from the sales order that shipment was attempted.
         • If processing through the Create AR Invoice function and the invoice could not be
             saved the credit card transaction will reside as an open credit that is available to be
             applied to another transaction.
    •    The Transaction # that was previously sent to the credit card processor for invoices was
         always the AR Invoice #. This has now been changed to always be the AR Cash Receipt
         #.




5646 Milton St Suite 540 Dallas, TX 75206 214.739.6576 Fax 214.739.7963 www.tamlinsoftware.com

				
DOCUMENT INFO