Secure Credit Card Processing for Microsoft Dynamics NAV

Visa Cardholder Information Security Program (CISP)Payment Application Best Practices  (PABP) Validation

ChargeLogic has been independently audited and validated using Visa's CISP security guidelines. The CISP Payment Application Best Practices establishes a set of 13 best practices designed to protect sensitive information from being compromised. These best practices, which also include numerous sub-best practices, are directed to assist software vendors to create secure payment applications that help merchants and service providers comply with CISP.

ChargeLogic is committed to protecting the confidentiality and integrity of credit card and personal data.

Fortrex Technologies Security Audit

The ChargeLogic source code and architecture have passed an extensive security audit performed by an industry-approved assessor. All applicable security measures were found to be in place and in compliance with industry best practices.

FirstData Payment Application Certification

ChargeLogic has been certified by FirstData for all supported credit card types. In addition, FirstData has certified the compatibility of ChargeLogic with the Verifone Everest Plus PIN Pad.  

Microsoft Gold Certified

The developers of ChargeLogic have attained Gold Certification status with Microsoft for both the Microsoft Business Solutions and the ISV/Software Solutions competencies. 

Certified for Microsoft Dynamics NAV

ChargeLogic, is now Certified for Microsoft Dynamics, signifying that the solution has met Microsoft Corporation's highest standard for partner-developed software.

ChargeLogic is the only PCI compliant credit card processing software that is both fully integrated and Certified for Microsoft Dynamics NAV.

Tokenization

Credit Card Tokenization is a creative new alternative to data encryption.  With Tokenization you can process payments without the need to store sensitive information on their system.

So how does it work? When a credit card or debit card (or any other alternative payment method) is used in a transaction the initial information is sent to the company providing the tokenization services, in the case of ChargeLogic this would be a payment gateway. Immediately after the gateway receives the transaction information they will generate a random and unique number return it to the merchant. This number, or token, is the only thing that needs to be stored on an internal system.