While the NAV-X Credit Car setup performs most of the setups for you, you might want to understand and review the setups to be able to make changes when needed. All setups described below can be reached from the “Search” box in Dynamics NAV or from the “Credit Card Setup” page.
Payment Method Setup
Payment Methods are used by NAV-X Credit Card to determine, if the customer will pay by credit card or a different method of payment.
NAV-X Credit Card creates automatically a new payment method for you called “CREDITCARD”. This payment method is setup to be used on customer setups and sales or service documents to indicate that the customer pays via credit card. If you want to configure a new payment method in this manner, you cannot define a “Bal. Account No.” and you have to set the field “Payment Type” to “Credit Card”.
Unit of Measure Setup
Unit of measures are used to define the packing sizes items are sold in or stored in inventory. Unit of measures are also transmitted to the gateway on credit card transactions in the line level detail. These details are transmitted for PCI compliance. Unit of measures are standardized for this and we need to map the units of measure you have in your solution to the standard codes used for credit card processing. NAV-X Credit Card already has done this automatically for you. If it could find a proper match, the match is configured. If not, the standard code of “PCE” for “Piece” was used.
While you can process credit card transactions with this setup, it is suggested to review the configured units of measure and make sure that the mappings are done properly.
If you process transactions in multiple currencies, the currency for a particular transaction is transmitted to the credit card processor. The currencies are transmitted as standard currency codes, which are defined in a separate configuration table and mapped to the standard currencies that you have configured in your environment. If you are using the standard 3 character ISO codes for currencies, the mapping is done automatically for you.
You can process credit cards without this setup, if you are processing only in one currency. It is, however, suggested, for you to review the currency setups and validate that the field “Standard Currency Code” has the proper mappings defined.
Your items require to be configured on your items. To be PCI Level III compliant, document line details must be transmitted for a transaction. You already defined the standard codes for units of measure, which is one of the data elements that needs to be transmitted. The second element is the “Commodity Code”. A commodity code classifies an item – usually only required for exports of goods. This field can be found in the “Costs & Pricing” tab under “Foreign Trade”.
Source Code Setup
Source codes are tags on transactions to identify the source of a transaction. For instance, any transaction posted from a sales order has a specific source code attached to identify this source. A source code is also required for credit card transactions. This is done automatically at the time of installation, but you can review and modify the source code. The field for credit card transaction source codes is called “Credit Card Payments” and accessible on the Source Code Setup. You can find this page through the Dynamics NAV search.