Setting Up the Credit Card Interface

This topic describes how to set up the Credit Card Interface.

Prerequisites

Note: For Cloud users, CenPOS is the only supported gateway.

Use the Credit Card Interface Configuration Guide to configure the Credit Card Interface.

During this process you must have this information:

A valid account with a supported credit card system such as CenPOS. For a full list of the supported credit card systems (gateways), see the Credit Card Interface Configuration Guide.
An RP (merchant) number if the supported system is Hypercom
A Merchant ID if the supported system is CenPOS
The URL of the Web Service used for credit card processing by the supported system.
For Cloud users, specify https://mguseastap-ism.ssmgf.inforcloudsuite.com/WSWebClient as the Payment Server.
For on-premise WinClient users, specify https://web_server/WebRelayService/ as the Payment Server. For on-premise WebClient users, specify https://web_server/WSWebClient/ as the Payment Server.

This information is recorded on the Credit Card Interface Parameters form during the implementation.

Note: A test URL and test credit card numbers are provided in the Credit Card Interface Configuration Guide.

Adding Connection Information

In the Credit Card Interface Parameters form, specify this information to connect to each supported credit card system:

Credit Card System

Specify the provider to which the credit card transactions are sent. Select External if you have developed an interface to a gateway that is not currently supported by the standard application.

See Using the External Option to Create Links to Other Gateways.

Caution:

See "If You Switch Credit Card Systems," below.

User ID and Password

Specify the user ID and password provided by the third-party system to access their credit card processing software.

Payment Server

Specify the URL of the web service used for credit card processing. See the Credit Card Interface Configuration Guide for the appropriate URL.

RP Number

This field is displayed only if the credit card system is Hypercom. Specify the merchant number supplied by Hypercom.

Merchant ID

This field is displayed only if the credit card system is CenPOS. Specify the Merchant ID supplied by CenPOS.

Specifying General Information About How the Interface Is Used

In the Credit Card Interface Parameters form, specify this information:

Select Auto Return if you want transactions to be sent to the credit card processing software for credit memos that are linked to an invoice (through the Apply To Invoice field) and that were originally paid by credit card. The original credit card number is used.
When a credit memo is linked to an invoice that was previously paid by credit card, and Auto Return is selected, then a "return" transaction is generated for that credit card when the credit memo is posted.
If Auto Return is not selected, and a credit memo is issued that is linked to an invoice that was previously paid by credit card, then an open credit exists and you must manually return the amount to the credit card.
Select Auto Post Open Payment to create an open payment in Accounts Receivable for the credit card payment amount. If you do not select this option, you must manually apply payment to a specific invoice.
For more information, see Auto Post Open Payment.
Select Charge for Contract During Invoice Generation to charge the credit card linked to a contract when an invoice is generated. A line is displayed in the invoice to reflect the credit card payment. If this check box is cleared, the charge is delayed until the Credit Card Contract Invoice Payments utility is run based on the Invoice Due Date.
Select Level Three Reporting if you want the credit card interface to send additional information in order to qualify for Level 3 processing. Otherwise, data qualified for Level 2 processing is collected and sent to the credit card system.
For more information, see Level Three Reporting.
Select Skip Credit Check When Authorization Exists to bypass any credit limit or credit check holds if there is a prior credit card authorization. This applies when a credit card is being used to pay for a sales order, service order, service contract, or rental contract.
For service orders and sales orders, if you will pre-authorize purchase amounts as well as credit card numbers, specify a Default Authorization method (percent or amount) and then specify the value to be pre-authorized (fixed amount or percentage of the gross sale).
For more information, see Pre-authorizing Credit Card Amounts or Percentages.
In the Contract Authorization Amount field, specify the amount to use when a contract is authorized to be paid by credit card.

Specifying Payment Information

For each of your customers who will pay by credit card, you can set up credit card information on the Credit Card Payment Information form and click Store for Future Orders to save the information.

(You can also fill out this form during entry of an order for the customer.)

Only a token to the credit card is recorded; no credit card numbers are stored in the ERP system.

Debugging the Interface

If it becomes necessary to track problems in your credit card interface, select Debug on the Credit Card Interface Parameters form. This creates entries in the Application Debug Log table. You can view these entries on the Application Debug Log Listing form.

Caution:

Because this feature can cause performance issues in your live system, it should not be used unless you are trying to troubleshoot an issue while working with support.

If You Switch Credit Card Systems

If you change from one gateway provider to another, any pre-existing credit card transactions and any stored credit card information becomes invalid.

Use the Customer Credit Cards form to determine which customer credit cards were stored using the old system. These records must be deleted and re-entered using the new system and the Credit Card Payment Information form.

Use the Credit Card Transactions form to determine which transactions were in process and must be reauthorized using the new system.