1. Home
  2. Reference Topics
  3. Difference between Logging Payments or Credits versus Credit Card Transactions

Difference between Logging Payments or Credits versus Credit Card Transactions

Contents

Overview

  • “Logging” a payment or credit merely records the payment information within SEOM – no payment transaction is executed through the program.
  • The Payment tabs of the Manual Orders, Process Orders or POSscreens allow you to manually log payment or credit information. For instance, you might run the credit card transaction directly at the payment gateway, but still want to record the payment information in SEOM.
  • “Logging” a payment or credit is also the process to be used 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.
  • In order to run credit card transactions, the SEOMsystem parametersfor the designated payment gateway used to process the transaction must be set. In fact, the Payment tab is not visible at the Process Orders screenuntil parameter CreditCardProcessor is no longer set to NONE.
  • In order to run credit card transactions, the PM must be properly configured with your payment account information.
  • The types of credit card transactions that can be performed depends on the capabilities of the payment processor or gateway. Check with the payment processor to identify supported transactions.
  • The Point-of-Sale system has a separate set of parameters to identify and configure the payment gateway it uses. The POS system can use a different payment gateway than that used by imported or manually placed orders.
  • You can specify the payment account or accounts used to process POS payments when the PM is configured. The same is true for manual orders or orders imported from one or more shopping carts. They can all use different payment accounts, or they can all use the same payment account.
  • Individual shopping carts can also use different payment gateways by settings the cart-based, or “special system parameters”.
  • Two SEOM parameters, WebTransactionType and AssumePaidInFull, also affect how credit card transactions are handled in SEOM. If you authorize the charges at the Web store and capture the funds in SEOM, set WebTransactionType to Pre-Authorize and AssumePaidInFull to FALSE. To authorize and capture the payment at the Web store, set WebTransactionType parameter to Sale and AssumePaidInFull to TRUE. To pre-authorize or charge new transactions on import, WebTransactionType must be set to TOKEN.
Updated on June 19, 2019

Was this article helpful?

Related Articles