Version 7.1 FAQs

• Overview
• Questions

Only Version 7.1 of OMS uses the PA-DSS Payment Application - Data Security Standards certified Payment Module.

Using the Payment Module is only a small step towards becoming PCI compliant. There are many other aspects of your business that need to be reviewed and updated to become PCI Compliant. Refer to the PCI website for full details. Review the Monsoon Commerce Implementation Guide for information about installing our applications in accordance with PCI -DSS guidelines.

No, you can use a single instance of SQL Server or SQL Express as long as all workstations running OMS /Payment Module have network access to the server or workstation where the SQL instance resides and have the appropriate permissions.

That's a complicated question.

It is expected that the merchant will transition to AuthNet CIM going forward at the time Version 7.1 is installed.

During the migration of payment information from an existing SE store data file, AuthNet AIM data can be mapped to an AuthNet CIM account in the Payment Module. You can also select the option one of the possible attributes of a product; for example, blue is an option for the color attribute of a product to Record Customer Information at that time, which minimizes the need to contact customers for credit card information when filling backorders or any other future payments. Be aware that AuthNet will charge and void a $0.01 transaction during the conversion process to create the customer profile.

While the Payment Module supports AuthNet AIM primarily for processing returns, in order to process a new payment transaction through OMS V7.1, you will need to contact the customer for credit card information to process a new payment (once per customer per credit card).

In addition, some shopping carts may not pass customer profile information along with the TransactionID, which may make if necessary for you to contact new customers, one time, to obtain full credit card information and record it through the Payment Terminal so that the program gets the customer profile information from the payment processor. Once the program has a "token" from AuthNet CIM, future transactions can be performed without the need to contact the customer for credit card information.

If your business is mostly phone or mail orders, this may not be a big problem. If most of your business is from web orders, you might want to consider switching to a payment gateway that only needs a previous TransactionID to process new payments, such as PayFlowPro or USAePay.

 

 

 

 

Upgrading to V7.0 before installing V7.1 is the recommended path, although you can upgrade to V7.1 after V7.0 has been installed and tested successfully.

You do not need to stay on V7.0 for an extended period of time before upgrading to V7.1, although doing so would provide time for the users of the program to grow accustomed to the new user interface before introducing the  changes to payment processing (V7.1).

PCCharge is not supported in V7.1.

Depending on the shopping cart, you might be able to import orders by text file or you may be able to utilize the Generic Cart License to implement direct XML a mark-up language similar to HTML, except that it is used to structure data, not display it. XML is used to order data in such a way that it can be passed between applications with relative ease. communication between your cart and OMS .

• Passwords must be at least 8 characters in length and must contain at least one uppercase letter, one lowercase letter, one number and one special character.

• Invalid login attempts can be set anywhere between 3-6.

• Lockout duration can be set between 30-120 minutes.

• Password Duration can be set to anywhere between 30-90 days

• Reuse of previous passwords can be set anywhere between 4-6.

Yes, you can still manually record payments such as Checks, Purchase Orders or traditional PayPal payments through OMS . The Payment Module only handles electronic payment transactions for credit or debit sales, voids or credits through selected payment gateways or processors..  

That depends on the payment processor.

Payflow Pro and USAePay XML are able to use an existing Transaction ID to process new payments.

Other gateways, such as Cybersource, require a customer profile (or token) as well as a Transaction ID to process a new payment. If the shopping cart does not pass the customer profile information to OMS , you will need to contact the customer for credit card information and manually Record the Customer at the Payment Terminal to obtain a token from the payment processor through which future payments can be processed. This is a one-time per credit card per customer exercise.