Difference between Logging Payments or Credits versus Credit Card Transactions

Contents of this Topic: Show

Overview

Logging payments or credits

"Logging" a payment or credit merely records the payment information within Monsoon Order Manager – no electronic payment transaction is executed by the program. For instance, you might run the credit card transaction directly at the payment gateway, but still want to record the payment information in Monsoon Order Manager.

The Payment tabs of the Manual Orders and Process Orders screens is where you manually log payment or credit information. 

Other reasons to log a payment or credit is if the customer pays with a paper check or money order, or if you want to send the customer a refund by paper check rather than issuing store credit. Logging a payment or credit here generates a note in the order.

Although not covered in this topic, it is worth mentioning that non-electronic customer payments can also be recorded through the Apply Payment function of the Customers screen, which does not generate a note in the order, but you can spread the amount paid across multiple orders. See its Knowledge Base topic for more information.   

Credit/Debit Card Transactions

In order to process electronic payments through the program, you must have the Monsoon Commerce Payment Module (MCPM) installed and configured. Part of the configuration includes entering your payment gateway credentials into a payment account defined in the MCPM and assigning a payment account to manual orders and/or shopping carts/marketplaces.

The types of credit card transactions which can be performed depends on the capabilities of the payment processor or gateway. The MCPM should only allow transactions supported by the gateway, but you may want to check with the payment gateway or processor to identify supported its transaction types.

Two Monsoon Order Manager parameters, WebTransactionType and AssumePaidInFull affect how credit card transactions are handled in Monsoon Order Manager. If you authorize the charges at the Web store and capture the funds in Monsoon Order Manager, set WebTransactionType to Pre-Authorize. To authorize and capture the payment at the Web store, set WebTransactionType parameter to Sale.

AssumePaidInFull should normally be set to FALSE. Setting it to TRUE means that regardless of the payment status of the order at the cart, the program is going to assume the order has been paid for. This is useful for marketplaces which require the payment to be captured at their site, not in the Monsoon Order Manager.

Additional Information

Set System Parameters

Special System Parameters

 

Created:

Revised: 7/9/15

Published: 08/19/15