OPUSCharge Distributor Manual (Pro+)


Table of Contents

 Click here to expand...

Before You Begin


Introduction

 The iParc Pro+ OPUSCharge software is an on-demand web application (web app) and graphical user interface (GUI) that supports real-time processing of credit card transactions.

The OPUSCharge User Interface (OPUSCharge UI Pro+) enables users to configure credit settings, to view credit reports, and to manually process credit card transactions.

This online manual provides information to assist users with the installation and setup, operation, and troubleshooting of the iParc Pro+ version of the OPUSCharge UI software and operations.

For information about the iParcProfessional (B19) version of the OPUSCharge UI, go to OPUSCharge Distributor Manual (B19) located in the AMI Knowledge Portal (AKP).

CAUTION!

Do not put credit card software into service until the proper testing and verification has been performed. Failure to follow these testing and audit procedures for all credit card software installations, updates, or upgrades may result in the irretrievable loss of credit card transaction data and associated revenue.

Important! ~ Greece 3.0 Changes!

With the Greece 3.0 software release, the OPUSCharge UI (Pro+) now allows multiple Merchant IDs when using Payment Express® (Windcave®) as a gateway.

Some of the Payment Express® gateway settings that were formerly in the OPUSCharge UI (Pro+) Gateway Settings sub-menu option now reside in each OPUSCharge UI Client service (see image right). 

This change requires that each OPUSCharge UI Client service must be configured with the site’s Merchant ID, PxPay User, PxPay Key, PostUsername and Payment Express Post Password settings. Before upgrading to the Greece 3.0 release, copy all of the Payment Express gateway settings to a secure location so that they can be manually entered into the OPUSCharge UI Client fields following the upgrade.

Testing Process

  1. Test a credit card transaction via the Credit Card client.
  2. Set a settlement time and let OPUSCharge UI (Pro+) process the settlement (1 transaction).
  3. Verify the test transaction matches all Settlement Reports within the OPUSCharge UI (Pro+) client.
  4. Call the bank processor to verify the test transaction was correctly processed.
  5. Immediately report any discrepancies to the AMI Software Support Center: 1-866-727-5457.
  6. Process a test transaction via each installed payment method (e.g., credit card in/out, debit recharge, auto bill balance due, valet terminal, Express Parc, Fee Computer, Paystation, etc.).
  7. When all test scenarios are proven successful, the system may be put into service.

Daily Audit Process

  1. Sites should settle all pending transactions daily, possibly multiple times each day, based on transaction volume. Note: Many credit card processors do not accept batch and settlement processes for transaction counts greater than 900. 
  2. After completing each settlement, the appropriate Activity Reports should be run and audited against the Settlement Report for accuracy.
  3. Verify the credit card processor received all transactions correctly by reviewing Summary Reports from the processor, or by contacting the processor directly and verifying total value of the settlement. Note: This should be done daily or within a maximum of three (3) days.

Please refer to the AMI SOFTWARE LICENSE AGREEMENT AND LIMITED WARRANTY for additional information.

Port Configuration

Application

Port

Connecting App

Connecting Port

Protocol

Encrypted Channel

OPUSCharge UI

443

Web Service

Ephemeral

TCP

TLS/SSL

 OPUSCharge UI – Payment Express Gateway Settings (prior to Greece 3.0).


Adding a Trusted Site

Important!

The URL for the Fully Qualified Domain Name (FQDN) hosting the OPUSCharge UI (Pro+) must be added as a trusted site in Internet Explorer®. Failure to add the FQDN host URL may result in inoperable web-page menus.

To add a trusted site:

  1. Open Internet Explorer®.
  2. Click the gear icon in the upper-right corner and select Internet Options.
  3. Click the Security tab and select Trusted Sites.
  4. Click Sites.
  5. In the Add this website to the zone field, type in the URLs for OPUSCharge UI (Pro+): https://name_of_computer/OPUSChargePro+.
  6. Click Add to add the URL to the Websites list.
  7. Click Close when finished and close Internet Explorer®.

OPUSCharge UI – Adding a Trusted Site in Internet Explorer.

Installation


Note:

The iParc Pro + Greece 11 release is supported on Windows Server 2019 with Microsoft SQL 2019. If you are running Windows Server 2016, you can install the new Greece 11 software system or system updates. However, to avoid difficulties when the earlier versions expire, if you are running Windows Server 2012 R2 with Microsoft SQL 2012, you should run new installs of Windows Server 2019 with Microsoft SQL 2019 followed by the iParc Pro+ PARCS software installation, as detailed in this document.

Important!

Verify the OPUSite and iParcPro+ application programs have been installed from the Pro+ Installer CD, before installing the OPUSCharge UI (Pro+) software. Run the OPUSite and Pro+ installations if they have not been installed.

  1. Insert the Pro+ Installer CD into the application server and click 3. Install OPUSCharge.
  2. Click Run in response to any security warnings.
  3. Click Next on the initial installation wizard screen.
  4. Read the end-user license agreement. Click Print to print the license agreement, if desired.
  5. Once the license agreement has been read and printed, check the I accept the terms… checkbox and click Next.
  6. Install the OPUSCharge UI (Pro+) software in the default directory, unless specified otherwise. Click Next to continue with the default directory or click Change to switch to a different directory. 

 

OPUSCharge UI – OPUSCharge Installation Setup Wizard.


7. Enter the SQL server connection information into the Server Name: field. Either the SQL server name or SQL server IP address may be used.

AMI Tip!

Named Pipes must be enabled in the SQL Configuration Manager for OPUSCharge UI (Pro+) to connect to the SQL server via FQDN. TCP/IP must be enabled in the SQL Configuration Manager for OPUSCharge UI (Pro+) to connect to the SQL Server via the server IP address.

  • If Windows Authentication is used, verify the Windows Authentication checkbox is checked and press Next.
  • If SQL Authentication is used, verify the Windows Authentication checkbox is unchecked. Type in the correct SQL credentials in the User name: and Password: fields, and press Next. A pop-up window informs you when the wrong SQL information is entered.

8. Click Install to begin the OPUSCharge UI (Pro+) software installation.

9. Verify the installation has completed successfully and click Finish to close the install wizard.

OPUSCharge UI – SQL Server Information / Setup Screen.


Activating OPUSCharge UI (Pro+)

Good to Know!

A certificate is required to view the OPUSCharge UI (Pro+) web-page. Refer to the Pro+ PARCS Software – Quick Install Guide if a self-signed certificate has not yet been created. Use the AMICA Certificate Creator if the facility has any OPUS devices or AMG 6700 devices on-site.

1. Open Internet Explorer® and navigate to: https://servername/OPUSCharge.

2. The OPUSCharge UI (Pro+) First Time Sign-In page is displayed.

3. Enter a Username, an administrative Email address, and a Password for the Administrator account. Click Login when finished.

IMPORTANT!

The Email address is used to email a lost password. Always use a valid and active email address or the account cannot be recovered if the password is lost. Record the OPUSCharge UI (Pro+) username, email address and password in a secure location.

4. Click the About tab on the main menu bar to view and enter OPUSCharge UI (Pro+) version information. Click the Activate button.

5. Type in the License ID, Password, and Installation Name provided by the branch supervisor.

6. Once the activation information is entered, click the Complete Activation button. A pop-up confirmation box Activation Successful is displayed. The Deactivate button becomes active, further indicating that the OPUSCharge UI (Pro+) is successfully activated.

OPUSCharge UI – About OPUSCharge information screen.

Launching OPUSCharge UI (Pro+)

Use any of the methods described below to launch the OPUSCharge UI (Pro+).

Start Menu (Windows)

1. Click the Windows Start  icon in the bottom-left corner of the screen and click the down-arrow  icon to expand all programs.

2. Click the OPUSCharge listing in the Amano McGann program section. The OPUSCharge UI (Pro+) login screen is displayed.

3. Enter the username and password and click Login. The OPUSCharge UI (Pro+) main menu screen is displayed, shown right.

Card Access

1. Start Card Access.

2. Click the Access menu and hover the cursor over Credential.

3. Once Credential has expanded, select OPUSCharge.

Web Browser

1. Open a web browser.

2. Navigate to: https://servername/OPUSCharge and click the OPUSCharge.exe filenameThe OPUSCharge UI (Pro+) login screen is displayed.

3. Enter the username and password and click Login. The OPUSCharge UI (Pro+) main menu screen is displayed, shown right.

 

OPUSCharge UI – OPUSCharge UI Home Screen.

Initial Configuration Settings


Initial Warning Messages

After activation of the OPUSCharge UI (Pro+), three (3) warnings are displayed near the main menu bar that notifies the user of any initial configuration settings that must be performed:

  • API Password NOT Set
  • Default MerchantID NOT Set
  • Management Client MerchantID NOT Set

Refer to the Config Menu section below for additional information regarding each setting.

To Set the API Password

If the warning message API Password NOT Set appears:

1. Login to OPUSCharge UI (Pro+). Activate OPUSCharge UI if has not been activated already.

2. Click on the Config tab on the main menu bar to open the sub-menu options.

3. Click on the General sub-menu option. The General Settings configuration screen is displayed. A pop-up window notifies you of the risks of enabling Store & Forward functions before properly configuring that feature.

Warning!

If configured incorrectly, Store & Forward settings in the General Settings configuration screen can be damaging to facility operations. Do NOT enable the Store & Forward feature until you are aware of the risks of using it. For the initial configuration, make sure the Enable Store and Forward Feature setting is set to No (see image right), or irretrievable loss of pending credit card transaction data may result.

Before you configure Store & Forward settings, it is important to read and understand the Store & Forward Configuration section below.

4. Type in the API Password.

Important!

The API Password field in the OPUSCharge UI (Pro+) corresponds with the External API Password field found in the Card Access > Web API Options sub-menu. You must verify that the two password fields match. Processing of credit card transactions will fail if the API Password is incorrect or not set.

5. Click Save. The API Password NOT Set message panel disappears once a new page is loaded.

6. Click OK on the pop-up confirmation box.

OPUSCharge UI – Enable Store & Forward configuration setting.

To Set the Default Merchant ID

If the warning message Default Merchant ID NOT Set appears:

1. Login to OPUSCharge UI (Pro+). Activate OPUSCharge UI if has not been activated already.

2. Click on the Config tab on the main menu bar to open the sub-menu options.

3. Click on the Gateway sub-menu option. Enter the following settings:

  • Default Merchant ID – matches the device Terminal ID number. Verify that the numbers match.
  • Request Port  matches the IP Port number.

Important!

Verify that the value in the Request Port field is exactly the same value that appears in the IP Port field in the Merchant Connect® MULTI® application. To navigate to the IP Port field, open the Merchant Connect® MULTI® application and open the Start Server menu.

  • Timeout  defaults to 60 seconds.

4. Click Save. The Default MerchantID NOT Set message will disappear.

OPUSCharge UI – Tender Retail Gateway Settings.

 

OPUSCharge UI – Merchant Connect® MULTI® Gateway Settings.

To Set the Management Client Merchant ID

If the warning message Management Client Merchant ID NOT Set appears:

  1. Login to OPUSCharge UI (Pro+). Activate OPUSCharge UI if has not been activated already.
  2. Click on the Config tab on the main menu bar to open the sub-menu options.
  3. Click the Clients sub-menu option.
  4. In the |Credit Card Clients| forms table, click the Edit  icon corresponding to the Management Client listing. The Edit configuration screen is displayed.
  5. Use the drop-list to select the Merchant ID (Terminal ID).
  6. Clic.

The initial configuration of OPUSCharge UI (Pro+) is now complete. Continue with the procedures below to configure OPUSCharge UI (Pro+) as required by the facility.

OPUSCharge UI – Management Client Merchant ID setting.

Config Menu 


The Config tab on the main menu bar contains all configuration settings for OPUSCharge UI (Pro+). These settings enable a user to tailor OPUSCharge UI (Pro+) functions to serve the facility's needs. The sub-menu options listed in the Config tab include:

Caution!

If configured incorrectly, Store & Forward settings in the General Settings configuration screen can be damaging to facility operations, since pending transaction data may be irretrievably lost. The Store & Forward settings are explained in detail in the section immediately following this one. Before you configure Store & Forward settings, it is important to read and understand that section to configure the Store & Forward feature correctly.

General Settings 

The General Settings sub-menu option contains configuration settings that do not pertain to the other configuration categories including:

  • Maximum Charge: – the maximum fee allowed by OPUSCharge UI (Pro+). This value does not apply to Store & Forward transactions.
  • Card on file Monthly Maximum Charge: – the maximum fee that is charged to a credit card on file.
  • Duplicate Transaction Interval (seconds): the delay in seconds before a duplicate transaction is accepted in OPUSCharge UI (Pro+).
  • Enable Store and Forward: – enables or disables the Store & Forward feature. The Store & Forward feature is responsible for storing transactions if the iParcs Pro+ server cannot connect to the credit card processor. Once the connection is restored, the first successful credit card transaction will trigger the Store & Forward feature to attempt to send the stored transactions to the processor.
  • Store and Forward Max: – the maximum single charge allowed by OPUSCharge UI (Pro+) while the connection to the credit card processor is lost or disabled. This setting does not apply to normal transactions that are processed by the credit card service.
  • Stored Transaction Limit (Days): – the maximum number of days the Store & Forward feature will collect credit card transactions if the processor cannot be contacted.

Important!

If the Stored Transaction Limit is reached and the credit card processor has not processed the stored transactions, new credit card transactions will not be accepted until the connection to the credit card processor has been restored and the stored transactions have been processed.

  • Store and Forward Email Frequency (Hours): – the frequency interval in hours that the Store & Forward feature auto-generates a status update email.

Note:

OPUSCharge UI (Pro+) sends an initial email alert when Store & Forward transactions exist. It can then be determined whether to send continuous email alerts and how often. OPUSCharge UI will also send an email once the transactions are processed.

  • API Password: password for the OPUSCharge UI (Pro+) Web API.

Important!

The API Password field in the OPUSCharge UI (Pro+) corresponds with the External API Password field found in the Card Access Web API sub-menu. You must verify that the two password fields match. Processing of credit card transactions will fail if the OPUSCharge UI (Pro+) API Password is incorrect or not set.

Refer to Amano McGann, Inc. SOFTWARE LICENSE AGREEMENT AND LIMITED WARRANTY for additional information.

To configure OPUSCharge UI (Pro+) general settings:

1. Launch the OPUSCharge UI (Pro+) and click on the Config tab on the main menu bar. The General Settings configuration screen is displayed by default.

2. Use the drop-lists to choose the General Settings sub-menu options. Refer to the configuration settings descriptions listed above.

3. Take special care to understand the Store & Forward functions before saving the configuration. For detailed information, refer to the next section Store & Forward Configuration Settings

4. Once you have configured the OPUSCharge UI (Pro+) General Settings, click Save to save your changes.

OPUSCharge UI – General Settings configuration screen.

Store & Forward Configuration Settings 

The Store & Forward feature stores credit card transaction data whenever the iParcPro+ PARCS server cannot connect to the credit card processing service (e.g., Tender Retail®).

Once the connection to the credit card processing service is restored, the first successful card transaction will trigger the Store & Forward feature to transmit the stored transaction data in a batch.

Perform the following steps to configure the Store & Forward functions:

1. Back up the iParcPro+/SQL credit database and iParcPro+/McGann database by saving out and renaming the files with the current date and time (e.g., C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Backup\backupfilename_063020_10:21).

2. Stop or disable the credit card processing service or services (e.g., Tender Retail®).

Warning!

If the credit card processing services are not disabled and the PC is rebooted while in batch mode, the Tender Retail® service will start automatically processing credit card transactions. This can result in the loss of transaction data and facility revenue. In addition, the Store & Forward function may stop working.

3. Launch the OPUSCharge UI (Pro+) and click on the Config tab on the main menu bar. The General Settings configuration screen is displayed by default.

4. For the Store & Forward Max: setting, use the drop-list to set the maximum upper limit that a customer can pay and still exit the facility in store-and-forward mode. Hint: a typical maximum is $50 - $100.

Good to Know!

While in store-and-forward mode, any credit cards used for payment of fees are not checked for validity. The card transaction data will be added to the batch as long as the credit card has not expired.

5. Set the Stored Transaction Limit (Days): to 14. This allows the Store & Forward feature to store the transaction data for up to 14 days before the transaction expires.

Important!

The Stored Transaction Limit setting determines how long the Store & Forward feature will store transaction data whenever the iParcProfessional PARCS server is in store-and-forward mode. If the limit is reached and the credit card processor still cannot process transactions, any stored transaction data will be scrambled and the customers' payments will not be processed, resulting in lost revenue. Configure the Stored Transaction Limit setting based on the longest historical suspension of credit card processor connection.

6. For the Enable Store and Forward: setting, use the drop-list to select Yes to enable the Store & Forward feature.

7. Once you have configured any additional OPUSCharge UI (Pro+) General Settings, click Save to save the configuration settings.

8. Test a credit card transaction. If the card transaction is successful, verify that the transaction date is being stored correctly in the Store & Forward batch list. Launch OPUSCharge UI (Pro+), click the Credit tab on the main menu bar and select the Store & Forward sub-menu option to view the transaction included in the batch.

The Store & Forward configuration is now complete.

OPUSCharge UI – Store & Forward transactions table.

Gateway Settings 

The Gateway Settings sub-menu option enables a user to configure the credit card processor service connections with OPUSCharge UI (Pro+).

Perform the following steps to configure the Gateway Settings. Refer to the sections below for detailed information about configuration settings.

1. Launch the OPUSCharge UI (Pro+) and click Config on the main menu bar. Select the Gateway sub-menu option. The Gateway Settings configuration screen is displayed.

2. Use the drop-list to choose the Processor TypeThe Processor Type designates the credit card processing service provider. Hint: Selecting a service changes the display of corresponding settings.

3. Configure the settings as described below for each of the listed Processor Types. (e.g., Tender Retail®, Apriva®, Payment Express®). 

4. Once you have configured the settings for a given Processor Type, click Save to save the settings. Click OK on the pop-up confirmation window to confirm the saved settings.

Tender Retail Gateway

Tender Retail® gateway and authentication settings include the following:

Note:

Verify that the requested port is not blocked by the Windows Firewall.

  • Request Port – the port the credit card processor application uses to submit credit card transaction data. Verify this port is not blocked in the Windows firewall. The default value is 3858.
  • Request Timeout (seconds) – the time limit for unanswered information requests from the credit card processor. The default value is 60.
  • Default Merchant ID – the default Merchant/Terminal ID a device uses when it is registered to OPUSCharge UI (Pro+).

OPUSCharge UI – Tender Retail Gateway Settings.

Apriva Gateway

Apriva® gateway and authentication settings include the following:

  • Apriva OAuth Base Url – type in the Terminal ID/Merchant ID in the text box (ex., https://ws.accounts.apriva.com/).
  • Apriva Transaction Url – type in the name of the branch installer in the text box (ex., https://ws.api.apriva.com/).
  • Apriva Oauth2Scope Url – type in the name of the site or facility in the text box (ex., https://ws.accounts.apriva.com/auth/user).
  • APK – set a logging level, if necessary. The default value is None. Other options include error and debug logging.
  • Client ID – type in a Client ID for service requests (provided by Apriva).
  • Secret – type in the long alpha-numeric encrypted code for the ClientID secret email (provided by Apriva).
  • Product ID – type in the product I.
  • RecurringCustomer Client ID – type in the current customer ID (provided by Apriva).
  • RecurringCustomer Secret type in the long alpha-numeric code for the RecurringCustomer Client ID secret email (provided by Apriva).

OPUSCharge UI – Apriva Gateway Settings.

Payment Express (Windcave) Gateway

Important! ~ Greece 3.0 Changes!

With the Greece 3.0 software release, the OPUSCharge UI (Pro+) now allows multiple Merchant IDs when using Payment Express® (Windcave®) as a gateway.

Some of the Payment Express® gateway settings that were formerly in the OPUSCharge UI (Pro+) Gateway Settings sub-menu option now reside in each OPUSCharge UI Client service (see image right). 

This change requires that each OPUSCharge UI Client service must be configured with the site’s Merchant ID, PxPay User, PxPay Key, PostUsername and Payment Express Post Password settings. Before upgrading to the Greece 3.0 release, copy all of the Payment Express gateway settings to a secure location so that they can be manually entered into the OPUSCharge UI Client fields following the upgrade.

All gateway and authentication settings are provided by Payment Express® (Windcave®) per site.

  • Payment Express Request URL – type in https://uat.paymentexpress.com/pxaccess/pxpay.aspx in the text box.
  • Payment Express Post URLhttps://uat.paymentexpress.com/pxpost.aspx in the text box.
  • Currency – use the drop-list to select the type of currency (USD or CAD).

OPUSCharge UI – Payment Express (Windcave) Gateway Settings.

Secondary Gateway Settings 

The Secondary Gateway Settings sub-menu option enables a user to configure the secondary credit card processor service connections with OPUSCharge UI (Pro+).

Perform the following steps to configure the Secondary Gateway Settings.

1. Launch the OPUSCharge UI, login as an administrator and click Config on the main menu bar. Select the Secondary Gateway sub-menu option. The Secondary Gateway Settings configuration screen is displayed.

2. Use the drop-list to choose the Processor Type as shown in the on-boarding worksheet. The Processor Type designates the secondary credit card processing service provider. For purposes of this example, Rapid Connect® is selected as the Processor Type.

3. Type in the URL address of the Secondary Gateway provider.

4. Configure the Secondary Gateway settings:

  • Set the Maximum Charge (if required).

  • Set the Request Timeout between OPUSCharge UI and the processing service (if required).

5. Click Save to save the settings. Click OK on the pop-up confirmation window to confirm the settings have been saved.

OPUSCharge UI – Secondary Gateway Settings Screen.

Credit Card Email Alert Settings 

The Alerts sub-menu option contains the credit card email alerts settings for OPUSCharge UI (Pro+) including:

  • Send Credit Card Alerts – enables/disables the OPUSCharge UI (Pro+) alerts feature. When this feature is enabled, OPUSCharge UI (Pro+) sends email alerts to authorized recipients. Refer to the Users section below for details regarding user configuration.
  • Alert Email Address – the email address that alerts are sent from. Many facilities will use sender addresses like 'alerts@facilityname.com'.
  • Email Server IP or Name – the Fully Qualified Domain Name (FQDN), or IP Address, of the SMTP server.

AMI Tip!

AMI recommends using the FQDN as the IP Address since the SMTP server is more likely to change.

  • SMTP Port – port number used by the SMTP server. Port 25 is the default port used by SMTP. Servers using SSL will use a different port number (often 465).
  • Use Secure Sockets Layer (SSL) – set to No if the SMTP server is not using SSL encryption. Set to Yes if the SMTP server is using encryption.
  • SMTP Authentication Login Required – enable this option if the SMTP server requires login credentials to access the desired email account.
  • SMTP User Name – the SMTP account username, which is only required if SMTP Authentication Login Required = Yes.
  • SMTP Password – the password corresponding to the SMTP user, which is only required if SMTP Authentication Login Required = Yes.

Note:

 OPUSCharge UI (Pro+) requires an SMTP server to use the alerts features. Neither alerts features nor password resets will function if the SMTP server is not set up.

Follow the steps below to configure the credit card email alerts settings:

1. Launch the OPUSCharge UI (Pro+) and click Config on the main menu bar. Select the Alerts sub-menu option. The Credit Card Alert Settings configuration screen is displayed.

2. Use the drop-lists to choose the Credit Card Alert Settings sub-menu options. Refer to the configuration setting descriptions listed above.

3. Click Test to test the SMTP connections. The result of the test is displayed in a pop-up window. Click OK to confirm success or failure and close the pop-up window.

4. If the test failed, verify that the configuration settings you selected are correct. Test the settings again.

5. Click Save to save the settings.

OPUSCharge UI – Credit Card Alert Settings Screen.


Receipt Settings 

The Receipt sub-menu option is used to configure the header and footer text that is printed on receipts when an OPUSCharge UI (Pro+) transaction is processed.

Good to Know!

The Receipt sub-menu configuration screen is not shown if the Tender Retail® card processor service is used. That function is performed by the gateway service.

1. Launch the OPUSCharge UI and click Config on the main menu bar. Select the Receipt sub-menu option. The Receipt Settings configuration screen is displayed.

2. Enter the header and footer information desired and click Save to save the changes.

OPUSCharge UI – Receipt Settings Screen.


Credit Cards Settings 

The Credit Cards sub-menu option defines what credit card types can be used at the facility. BIN (Bank Identification Number) ranges for any card type can be excluded, as necessary.

Good to Know!

A BIN number range is often excluded to prevent patrons from using certain types of cards that are not credit cards (i.e., gift cards, cash cards).

1. Launch the OPUSCharge UI (Pro+) and click Config on the main menu bar. Select the Credit Cards sub-menu option. The Accepted Credit Cards configuration screen is displayed.

2. Click the Edit  icon associated with a card type to alter the credit card settings.

  • Accepted – this checkbox enables/disables the card type. If the value is set to Yes (checked), that card type will be accepted at the facility. If the value is set to No (unchecked), that card type will not be accepted at the facility.
  • BIN Range | Accepted: – determines what BIN ranges are accepted at the facility for the card type.

3. Select Update to save the changes or Cancel to exit without saving the changes.

 

OPUSCharge UI – Accepted Credit Cards configuration settings.


Client Settings 

The Clients sub-menu option enables the end-user to edit a credit card client record. Credit card clients are devices or web apps that accept credit card payments. Each is identified by a unique combination of Client Name, Client GUID and Merchant IDDifferent Merchant ID numbers can be used at specific devices and web apps to relieve service demands on a single Merchant ID.

1. Navigate to the Clients sub-menu option by clicking Config on the main menu bar and selecting Clients. The Credit Card Clients forms table is displayed.

2. Click the Edit  icon corresponding to the client record you want to alter. The Edit configuration screen is displayed over the forms table. It includes the following settings:

  • Client Name – the default name shown is taken from the device name assigned in the Card Access module.
  • Client GUID – device identifier number. Do not change the default text string, unless you are specifically requested to change it by AMI Customer Support.

Important!

This Client GUID number assigned to a client device must be unique. If there are issues processing credit cards at the facility, first check for duplicate or incorrect GUID's.

  • Merchant ID – credit card application Merchant ID/Terminal ID number to use. Each device can only have one Merchant ID.

Important!

Changing the Client Name in the OPUSCharge UI (Pro+) will not change the device name in the Card Access module.

4. Click Update to save the changes or click Cancel to exit without saving the changes.

OPUSCharge UI – Credit Card Client GUID settings.


Settlement Settings 

The Settlements sub-menu option is used to configure the settlement time(s) and settlement count that OPUSCharge UI (Pro+) uses when settling its credit card transactions. Multiple settlement times can be added, if necessary, to relieve demand on a processing service.

  • New Settlement Time – enables the addition of a new settlement time.
  • SettlementCount – designates how many transactions OPUSCharge UI (Pro+) settles once a settlement time is reached. 

1. Navigate to the Settlements sub-menu option by clicking Config on the main menu bar and selecting Settlements. The Settlement Settings configuration table is displayed.

2. Add multiple settlement times, as necessary, using the New Settlement Time: field. Click the Clock  button enter the desired settlement time and click Add. The settlement time is added to the list.

3. Check the Settle When Count Reaches checkbox to activate when the SettlementCount value is reached.

4. Choose a SettlementCount. Use the UP/DOWN arrows to adjust the value by increments of 1, or type in the desired value in the text field.

AMI Tip!

Many credit card processor services will not allow settlement batches of more than 900 transactions. Please adjust the settlement count accordingly.

Refer to the Amano-McGann, Inc. Software License Agreement and Limited Warranty for additional information.

OPUSCharge UI – Settlement Settings Screen.


User Settings 

The Users sub-menu option is used to create new user accounts and credentials. Each user can be assigned access to a combination of OPUSCharge UI (Pro+) menus.

Navigate to the Users sub-menu option by clicking Config on the main menu bar and selecting Users. The Users forms table is displayed. User settings include:

Account Options

  • User Name – employee's user name.
  • Email Address – employee's email address. The email address entered will be used when sending alerts and password resets.
  • Receive Alerts – drop-list used to select whether the user will receive alerts for OPUSCharge credit card alarms.
  • Locked – drop-list used to lock a user account. This function is often used when a user will be out for a long period of time. Rather than deleted and re-adding the account, the account can be locked to prevent improper access.

User Rights

  • User Type – drop-list used to select whether the user rights.

♦ An Administrator has access to all menus and can add/remove other user accounts.

A User has access only to certain menus (depending on the |User Rights| sub-menu settings) and cannot add or remove other user accounts.

  • Credit Menu – drop-list used to grant Credit Menu access to a User. This right is granted to Administrators by default.
  • Reports Menu – drop-list used to grant Reports Menu access to a User. This right is granted to Administrators by default.
  • Config Menu – drop-list used to grant Config Menu access to a User. This right is granted to Administrators by default.

To Add a New User Account

1. Click the  button at the top of the Users forms table.

2. Type in the new user information in the User Name and Email Address text fields. The email address entered will be used to send email alerts and password resets.

3. Use the Receive Alerts drop-list to select whether the new user will receive alerts for OPUSCharge UI (Pro+) credit card alarms.

4. Use the Locked drop-list to lock the new user account.

AMI Tip!

The Locked function is often used when a facility will be closed for a significant period of time. Rather than deleting and re-creating the account, it can be locked temporarily to prevent access.

5. Use the User Type drop-list to select the type of new user account.

6. Click Save to create the new user record or Cancel to exit without creating the new user.

Important!

The SMTP Server settings must be set and the user's email address must be correct in order for the user's first-time login password to be emailed.

To Reset a User Password

1. Navigate to the Users sub-menu option.

2. Click the Reset Password button corresponding to the desired user.

3. Select OK to confirm the password reset and OK once more to confirm the sent email.

Deleting a User Account

1. Navigate to the Users sub-menu option.

2. Click the Delete button corresponding to the desired user account.

3. Click OK to confirm the deletion. The user account is removed from OPUSCharge UI (Pro+).

OPUSCharge UI – User Settings configuration screen.

Credit Menu


The Credit menu contains the sub-menu options to configure the credit features. The sub-menu options include:

  • Sales – used to manually process a credit card transaction.
  • Returns – used to return a gateway credit card transaction.
  • Secondary Gateway Returns – used to return a secondary gateway credit card transaction.
  • Store & Forward – contains the batched credit card transactions stored in the database waiting to be forwarded to the credit card processor.
  • Settlements – used to manually settle credit card transactions.
  • Blacklist – contains blacklisted credit cards that cannot be used at the facility.
  • Statistics & Alarms – displays credit card transaction statistics and alarms.

Click the Credit tab on the main menu bar to access the sub-menu options. The Sales configuration screen is displayed by default.

Please refer to sections Store & Forward Configuration and Store & Forward Settlements for additional information and warnings regarding the Store & Forward feature.

OPUSCharge UI – User Settings configuration screen.

Sales

Credit card transactions can be processed manually via the Sales sub-menu option when necessary.

Navigate to the Sales sub-menu option by clicking Credit on the main menu bar to open the Sales configuration screen. All information in the text boxes are required fields.

Good to Know!

If using the Payment Express® gateway, the steps to manually process a transaction vary slightly from all other payment gateway options. The default Sales configuration screen that appears will also vary based on the gateway in use. Refer to the appropriate sub-section below for details on each set of steps.

Payment Express® Gateway

To manually process a credit card transaction via Payment Express:

1. Navigate to the Sales sub-menu option by clicking Credit on the main menu bar. The Sales configuration screen is displayed by default.

2. In the Comment text box, enter any useful information for tracking the transaction.

3. In the Amount text box, enter the amount of the transaction.

4. In the Email Address text box, enter the email address of the user.

5. Use the Card is Present drop-list to select whether the credit card being used in the transaction was present when the purchase occurred.

6. Click Process. The user is redirected to the Payment Express Hosted Payment webpage.

7. From the Payment Express Hosted Payment webpage, under the Payment Checkout heading, in the Amount field, ensure that the amount entered on the Sales configuration screen appears.

8. Enter the account details for the method selected.

9. Click Submit to complete the payment or Cancel Transaction to exit without processing.

OPUSCharge UI – Sales configuration screen.

OPUSCharge UI – Payment Express Hosted Payment Webpage.

All Other Payment Gateways

To manually process a credit card transaction via any other payment gateway:

1. Navigate to the Sales sub-menu option by clicking Credit on the main menu bar. The Sales configuration screen is displayed by default.

2. In the Comment text box, enter any useful information for tracking the transaction.

3. Enter the credit card number in the Account Number text box.

4. Use the Calendar  icon to select the credit card Expiration Date, or type in the month/year (mm/yyyy).

5. Type in the Zip Code for the credit card in the text box.

6. Type in the amount to charge the card in the Amount text box.

7. If the card is present, use the Card is Present drop-list to select Yes. Otherwise, leave the selection unchanged (default = No).

8. Click Process to process the transaction after all desired values are entered. A Sale Transaction Result confirmation box is displayed that details the transaction process result.

  • A successful transaction will return an Approved: True result. An unsuccessful transaction will return an Approved: False result.
  • An unsuccessful transaction will return a ResultCode: number with a reason for the failed transaction. For example, an erroneous Merchant ID may return a ResultCode:ReceivedFailed status. Failed transactions will still return a TransactionID: for reporting purposes.

9. Click OK to close the Sale Transaction Result confirmation box.

OPUSCharge UI – Sales configuration screen.

Returns

Credit card return charges are processed via the gateway Returns sub-menu option. Navigate to the Returns sub-menu option by clicking Credit on the main menu bar and selecting Returns. The Returns configuration screen is displayed.

The initial Returns configuration screen contains an Account Number: text field and a Search button. Refer to the figure shown right.

1. Enter the account number of the credit card charge to return charges in the Account Number: text field. Click the Search to search for the records of charge(s) against that card.

2. A list of transactions for the designated account number are displayed in a forms table. Click on any listed transaction to begin processing a return for that transaction. The Process Return pop-up configuration window is displayed.

3. Type in the reason in the Reason for return: text field.

4. Place a check in the Card is present: checkbox if the card is present when processing the return.

5. Use the Calendar  icon to select the credit card's Expiration Date, or type in the month/year (mm/yyyy).

6. Click Process to process the return.

The charges to the designated credit card and transaction record will be reversed.

OPUSCharge UI – Returns configuration screen.

Secondary Gateway Returns

Secondary gateway credit card return charges are processed via the Secondary Gateway Returns sub-menu option.

Navigate to the Secondary Gateway Returns sub-menu option by clicking Credit on the main menu bar and selecting Secondary Gateway Returns. The Secondary Gateway Returns configuration screen is displayed. It includes the following settings:

  • Last Four of Credit Card: – the last four digits of the credit card number to search.
  • Start DateTime: – click the Calendar  icon to select a start date and the Clock  icon to select a start time for the search.
  • End DateTime: – click the Calendar  icon to select a start date and the Clock  icon to select a start time for the search.

Click the Search button to initiate the search. A forms table of search results is displayed.

OPUSCharge UI – Secondary Gateway Return configuration screen.


Store & Forward Settlements 

The Store & Forward feature enables a facility to store credit card transactions when the internet connection with the credit card processing service is lost.

Important!

If stored transactions exist, a red banner appears below the OPUSCharge UI navigation bar.

Once the internet connection is restored, the saved transaction data is forwarded to the credit card processor. Authorized users can also manually forward credit card transaction data.

1. Navigate to the Store & Forward sub-menu option by clicking Credit on the main menu bar and selecting Store & Forward. The Store & Forward transactions table is displayed by default with a list of stored credit card transactions.

2. Click Process to attempt a manual forward of the listed transactions.

3. A successful process result will display a Store & Forward transactions table with no listed transactions. Verify all transactions were processed successfully by refreshing the screen. Note: The red banner disappears after all stored transactions are processed.

4. Review the daily audit process to verify all revenue is accounted for.

OPUSCharge UI – Store & Forward transactions table.


Settlements

OPUSCharge UI (Pro+) attempts to settle credit card transaction at 2:00 am each day by default. However, should the occasion warrant, settlements can be manually transacted.

1. Navigate to the Settlements sub-menu option by clicking Credit on the main menu bar and selecting Settlements

  • If no settlement is required, an information pop-up message is displayed so indicating.
  • If transaction records are pending, a selection window is displayed that enables the user to choose between Settle All Merchants or Settle Selected Merchant options.

2. To process a settlement, select the radio button beside Settle All Merchants or Settle Selected Merchant and click Process. The results of the settlement action are displayed in a forms table after the settlement has finished processing.

3. The Settlement ID and associated Merchant ID are displayed with the settlement result. Press the Print  icon to print the settlement result. Scroll through the settlement results using the navigation buttons in the lower-left corner of the result window.

OPUSCharge UI – Manual Settlements transaction screen.


Blacklist

A facility can blacklist credit card account numbers to block them from future use at the facility. Use the OPUSCharge UI (Pro+) Blacklist sub-menu option to add and delete credit card accounts to and from the blacklist.

1. Navigate to the Blacklist sub-menu option by clicking Credit on the main menu bar and selecting Blacklist. A forms table of current blacklisted cards is displayed.

2. Click the +Add Card to Blacklist button to add a card account to the blacklist. The Add Card to Blacklist configuration screen is displayed.

3. Enter the credit card number for the blacklisted card in the Account Number text field.

4. Enter the Expiration Date of the blacklisted credit card.

5. Click Update to blacklist the card or press Cancel to cancel the addition.

An added record to the Blacklist forms table is displayed with the card type, the last four digits of the credit card account number, and the date the card was blacklisted.

OPUSCharge UI – Blacklisted Credit Cards configuration screen.


Statistics & Alarms

The Statistics & Alarms sub-menu option displays the collective credit card statistics for the iParcPro+ PARCS management software and any credit card alarms generated by OPUSCharge UI (Pro+).

Navigate to the Statistics & Alarms sub-menu option by clicking Credit on the navigation bar and selecting Statistics & Alarms. The Statistics & Alarms data table is displayed. The upper portion of the screen shows the credit card statistics. The lower portion of the screen shows alarms generated by OPUSCharge UI (Pro+).

The |Statistics| field displays:

  • The number of outstanding transactions with its added total.
  • The number of unsettled transactions with its added total.
  • The number of daily charges with its added total.
  • The number of daily denies with its added total.
  • The |Last Settlement Batch| field displays the last settlement time of stored transactions.
  • The |Last Settlement| field displays the date and time of the last successful settlement.

The |Alarms| field displays displays the credit card alarms generated by OPUSCharge UI (Pro+). Each alarm is shown with a time and descriptionIn a preceding section, an alarm was generated for Store & Forward transactions still pending. The alarm notification in the |Alarms| data table notifies the user that a Store & Forward transaction settlement was successful.

OPUSCharge UI – Statistics & Alarms data table.

Reports Menu


The Reports menu contains the sub-menu options to generate a range of credit card transaction reports generated by OPUSCharge UI (Pro+). The sub-menu options include:

  • Transaction Report – generates a report of one or more credit card transactions for a selected time range.
  • Settlement Transaction Report – generates a settlement report of credit card transactions for a selected merchant and time range.
  • Settlement Summary Report – generates a settlement summary report of credit card settlements for a selected merchant and time range. 
  • Unsettled Transaction Report – generates a report of any processed transactions that have not been settled by Merchant ID and card type.
  • Unsettled Summary Report – generates a summary of any processed transactions that have not been settled by card type and sale amount.
  • Expiring Credit Cards Report – generates a report of credit cards that will expire for a selected month and year.

Click the Reports tab on the main menu bar to access the sub-menu options. The Transaction Report configuration screen is displayed by default.

OPUSCharge UI – Transaction Report configuration screen.

Transaction Report

The Transaction Report sub-menu option displays the individual credit card transactions processed at a facility for a specified account number (or all account numbers) and time period.

Navigate to the Transaction Report sub-menu option by clicking Reports on the navigation bar. The Transaction Report configuration screen is displayed by default and includes the following parameters:

  • StartDate – start date and time of the transaction range data to display. Click the Calendar  icon to select a start date and the Clock  icon to select a start time.
  • EndDate – end date and time of the transaction range data to display. Click the Calendar  icon to select an end date and the Clock  icon to select an end time.
  • Last 4 CC Numbers – view transactions for a specific account/credit card number. Hint: Leave this field blank to display transactions for ALL credit card account numbers.
  • Authorization Code – the five- or six-digit code from the credit card processor to the merchant that authorizes the transaction and settlement.
  • Amount – amount of the transaction in dollars (or national denomination).
  • Comment – a note associated with the transaction.

1. Once you have configured the report parameters, click Get Report to generate the Transaction Report. The generated report contains the following columns: ID, Time, Merchant ID (MID), Comment, Credit Type, Amount, Type, Approval, Authorization Code, Account, and ResultCode for each transaction.

Example:

As illustrated by the example report shown right, the Forward Me transaction was denied due to lack of connection to the credit card processor (ResultCode: SendFailed). Once the Store & Forward feature was enabled, the Forward Me transaction was accepted and stored (ResultCode: AddedToBatch). The Authorization Code for stored transactions is BATCH.

2. Use the navigation panel  at the bottom-left corner of the Transaction Report to navigate through the report pages.

3. Click the PDF  icon to export the report as an Adobe® PDF file.

4. Click the Excel  icon to export the report to a Microsoft®Excel file.

5. Click the Cancel icon to close the report and return back to the Transaction Report configuration screen.

OPUSCharge UI – Transaction Report configuration screen.

OPUSCharge UI – Transaction Report data table.

Settlement Transaction Report

The Settlement Transaction Report sub-menu option displays a report of all approved credit card transactions for a selected merchant and time range. The report also displays any voided transactions returned with a VoidOK result code.

Navigate to the Settlement Transaction Report sub-menu option by clicking Reports on the navigation bar and selecting Settlement Transaction Report. The Settlement Transaction Report configuration screen is displayed and includes the following parameters:

  • StartDate – start date of the desired time range data to view. Click the Calendar  icon to select a start date and the Clock  icon to select a start time.
  • EndDate – end date of the desired time range data to view. Click the Calendar  icon to select an end date and the Clock  icon to select a end time.
  • Merchant ID – the designated merchant(s) for the generated settlement report. Select a specific Merchant ID number, or select ALL to capture settlement records for all merchants within the time range.

1. Once you have configured the report parameters, click Get Report to generate the Settlement Transaction Report. The generated report contains the following columns: Settlement ID, Time, Merchant ID, and Result for each transaction. A list of all settlements for the selected merchant(s) is displayed.

2. Place a check corresponding to each settlement you want to view in the |Check/Uncheck| column, then click Get Settlement Totals. The Settlement Transaction Report is displayed.

3. Use the navigation panel  at the bottom-left corner of the Settlement Transaction Report to navigate through the report pages.

4. Click the Close Report icon to close the report and return back to the Settlement Transaction Report configuration screen.

OPUSCharge UI – Settlement Transaction Report configuration screen.

OPUSCharge UI – Settlement Transaction Report data table.


Settlement Summary Report

The Settlement Summary Report sub-menu option displays a summary report of all settlements within a user-specified date range.

Navigate to the Settlement Transaction Report sub-menu option by clicking Reports on the navigation bar and selecting Settlement Summary Report. The Settlement Summary Report configuration screen is displayed and includes the following parameters:

  • StartDate – start date of the desired time range data to view. Click the Calendar  icon to select a start date and the Clock  icon to select a start time.
  • EndDate – end date of the desired time range data to view. Click the Calendar  icon to select an end date and the Clock  icon to select an end time.
  • Merchant ID – the designated merchant(s) for the generated settlement report. Select a specific Merchant ID number, or select ALL to capture settlement records for all merchants within the time range.

1. Once you have configured the report parameters, click Get Report to generate the Settlement Summary Report. The generated report contains the following columns: Credit Type, Sale Count, Sale Total, Void Count, Void Total, Return Count, Return Total for each transaction.

2. Use the navigation panel  at the bottom-left corner of the Settlement Summary Report to navigate through the report pages.

3. Click the PDF  icon to export the report as an Adobe® PDF file.

4. Click the Excel  icon to export the report to a Microsoft®Excel file.

5. Click the Close Report icon to close the report and return back to the Settlement Summary Report configuration screen.

OPUSCharge UI – Settlement Summary Report configuration screen.

OPUSCharge UI – Settlement Summary Report data table.


Unsettled Transaction Report

The Unsettled Transaction Report sub-menu option displays any individual processed transactions that are not yet settled.

To view all unsettled individual transactions, navigate to the Unsettled Transaction Report sub-menu option by clicking Reports on the navigation bar and selecting Unsettled Transaction Report. The Unsettled Transaction Report is displayed.

The Unsettled Transaction Report includes the following parameters: ID (transaction number), Time, Merchant ID, Comment, Credit Type, Account Number (last four digits), Type (of transaction), Authorization Code, and Amount.

1. Use the navigation panel  at the bottom-left corner of the Unsettled Transaction Report to navigate through the report pages.

2. Click the PDF  icon to export the report as an Adobe® PDF file.

3. Click the Excel  icon to export the report to a Microsoft®Excel file.

Transactions are no longer displayed in the Unsettled Transaction Report once the transactions have been settled.

OPUSCharge UI – Unsettled Transaction Report data table.


Unsettled Summary Report

The Unsettled Summary Report sub-menu option displays a summary of all processed transactions that are not yet settled.

To view all unsettled transactions, navigate to the Unsettled Summary Report sub-menu option by clicking Reports on the navigation bar and selecting Unsettled Summary Report. The Unsettled Summary Report is displayed.

The Unsettled Summary Report includes the following parameters: Credit (card) Type, Sale Count, Sale Total, Void Count, Void Total, Return Count, and Return Total.

1. Use the navigation panel  at the bottom-left corner of the Settlement Transaction Report to navigate through the report pages.

2. Click the PDF  icon to export the report as an Adobe® PDF file.

3. Click the Excel  icon to export the report to a Microsoft®Excel file.

OPUSCharge UI – Unsettled Summary Report data table.


Expiring Credit Cards Report

The Expiring Credit Cards Report sub-menu option displays a summary report of credit card expiration dates for a selected month and year.

Navigate to the Expiring Credit Cards Report sub-menu option by clicking Reports on the navigation bar and selecting Expiring Credit Cards Report. The Expiring Credit Cards Report configuration screen is displayed and includes the following parameters:

  • Month – use the drop-list to select the expiration month from 1-12.
  • Year – use the drop-list to select the expiration year from the current year (e.g., 2020) through a 20-year range (e.g., 2039).

The Expiring Credit Cards Report includes the following parameters: FirstName, LastName, AccountNumber, Address1, City, State, Zip, Phone and Expiration.

1. Use the navigation panel  at the bottom-left corner of the Expiring Credit Cards Report to navigate through the report pages.

2. Click the PDF  icon to export the report as an Adobe® PDF file.

3. Click the Excel  icon to export the report to a Microsoft®Excel file.

4. Click the Close Report icon to close the report and return back to the Expiring Credit Cards Report configuration screen.

OPUSCharge UI – Expiring Credit Cards Report configuration screen.

OPUSCharge UI – Expiring Credit Cards Report data table.

About Menu


The About tab on the main menu bar provides detailed information about the OPUSCharge UI (Pro+) installation, including version information, and is used to activate and deactivate the OPUSCharge UI (Pro+) application.

It includes the following categories:

  • Product: – the application name.
  • Version: – version build number of the application.
  • Copyright: – the software copyright notice.
  • Trademark: – the trademark notice.
  • SSL Expiration Date: – expiration date of the SSL certification.
  • License ID: – identification number of OPUSCharge UI (Pro+) installation.
  • Name: – the contact name.
  • Company: – the organization responsible for installing the product.
  • Installation: – the installation name given to OPUSCharge UI (Pro+) by the technician who installed the product (often named after the facility).
  • Status: – activation status of OPUSCharge UI (Pro+).

AMI Tip!

Certificates generated by the AMICA Certificate Creator are 10-year certificates. After 10 years, a new certificate must be created. Check for expired certificates if credit cards are unable to process suddenly.

OPUSCharge UI – About OPUSCharge information screen.

Diagnostic Files


Note:

To reach the diagnostic files, certain hidden folders must be enabled. To enable the viewing of hidden folders/files, open any Windows file folder, click the View tab, and check the Hidden items checkbox in the toolbar.

  • Navigate to C:\ProgramData\AMI\OPUSCharge\Logs on the host server to view the log files.
  • Navigate to C:\Program Files(x86)\AMI\OPUSCharge\web.config on the host server to view the Web Config file.


LogDescriptionLog File URL
Debug LogContains general logging data for OPUSCharge UI (Pro+). Logging levels are set by the Log4net configuration file....\Logs\debug.log
Error LogContains a log of all errors OPUSCharge UI (Pro+) encounters during normal operation. The Error Log is useful for troubleshooting general errors and sudden crashes....\Logs\error.log
Transaction LogProcessed OPUSCharge UI (Pro+) transaction. Previous Transaction Logs contain the year, month, and day after the *.log file extension....\Logs\Daily\transactions.log
Web ConfigOPUSCharge UI (Pro+) configuration information. ...\web.config

Troubleshooting


The following section is a list of typical OPUSCharge UI (Pro+) issues. Each section has a scenario, a difficulty level, risk level, and troubleshooting procedure.

Many of the OPUSCharge UI (Pro+) scenarios have a medium-to-high risk factor, since credit card operations are often vital to a facility.

Contact AMI Technical Support at 1-866-727-5457, if you are uncomfortable performing any of the troubleshooting procedures below.

Credential Host Unavailable

  • Scenario: Error message Credential Host Unavailable is displayed when attempting to process credit cards.
  • Difficulty: Easy.
  • Risk: Medium.

When a Credential Host Unavailable message is received, begin troubleshooting by verifying the credit card processor application and processor service is running. The Merchant Connect MULTI® service will be used in this scenario, as it is the most common credit card processor application used with AMI products.

MULTI Running as an Application

1. Click the notification UP arrow in the bottom-right corner of Windows Server 2012.

2. Double click the MULTI icon. The Merchant Connect MULTI® application interface is displayed.

3. Verify the Terminal IDs have an Active  icon beside them, designating a running Terminal/Merchant ID.

4. If any Terminal IDs have a Pause II icon, start the server by clicking the System menu and selecting Start Server.

Important!

You must verify that Card Information Response Format is set to Masked Card Info when starting the Merchant Connect MULTI® credit card server.


Windows Server – Customize and Credit/Debit configuration screens.

MULTI Running as a Service

  1. Click the Start  icon in the bottom-left corner of Windows Server.
  2. In the Type to Search text field, type "services" and click theServices result on the right side of the screen to open
  3. Locate the CDCA Multi Client service. Right-click on the filename to view the splash-box and click Properties to open the Properties dialog box and confirm the Service Status: is Running.
  4. If the service is not running, click Start.

AMI Tip!

Use this opportunity verify the Startup Type: parameter in the Properties dialog box for the CDCA Multi Client service is set to Automatic. If the Startup Type: is not set to Automatic, use the drop-list to change it. Click Apply to confirm the change. Click OK.

If the server name has changed, the service URL of OPUSCharge UI (Pro+) will not change to reflect the new server name. This means that the iParcProfessional system will look in the wrong location (the old server name) for the OPUSCharge UI (Pro+) service address. Follow the steps below to verify/change the OPUSCharge UI (Pro+) service URL in the OPUSite web.config file.

Warning!

The following procedure is a High Risk undertaking. Please be cautious when performing the steps listed below and follow them precisely. AMI recommends that you perform this troubleshooting during facility down time.

1. Close all iParcProfessional PARCS system applications and web interfaces.

2. Click the Windows Explorer  icon on the Windows Server UI taskbar.

3. Navigate to C:\Program Files(x86)\AMI\OPUSite.

4. Open the Web.config file using Notepad.

5. Between the '<appSettings>' tags are the '<add key>' tags. Look for the add key OPUSChargeSvcURL.

6. The value= section should have the following reference: "https://[servername]/opuscharge/".

7. If necessary, modify the [servername] to match the FQDN (Fully Qualified Domain Name) of the OPUSCharge UI (Pro+) server.

8. Once the change is made in Notepad, click the File menu and select Save. Do not make any more changes.

9. Exit Notepad.

10. Restart the iParcProfessional PARCS applications and web interfaces that you closed earlier.

Windows Server – Services configuration screen.

Windows Server – Merchant Connect MULTI client service properties.


Host Timeout

  • Scenario: Error message Host Timeout is displayed when attempting to process a credit card.
  • Difficulty: Easy.
  • Risk: Low.

The Merchant Connect MULTI® service could not connect to the credit card processor. Contact the credit card processor. 

OPUS Device Registration

  • Scenario: The OPUS devices at the facility did not register in OPUSCharge UI (Pro+).
  • Difficulty: Easy
  • Risk: Low

To register a device with OPUSCharge UI (Pro+), the IO100 Certificates must be downloaded to the OPUS device's IO100 Controller Board.

1. Create an IO100 Controller Board device certificate using the AMICA Certificate Creator applet from AMI. Name the device certificates IO100CA.pem, IO100client.pem and IO100server.pem.

Note:

The CA certificate passwords must be known, or the certificate will not work. It is important to record and store all certificate passwords when the certificate is created.

2. Navigate to the OPUS device's IO100 webpage.

3. Login to the IO100 webpage.

4. Hover the mouse over the Network tab and select SSL.

5. Click the Choose File button in the |Import Settings| section and browse to the IO100CA.pem file created in Step 1. Click on the filename to select it.

6. Click Upload.

7. Repeat Step 5 and Step 6 for the IO100client.pem and IO100Server.pem files.

8. Hover the mouse over the System tab and select System Reboot.

9. Click Reboot System and wait for the IO100 Controller Board to fully reboot.

10. Ensure you can login to the IO100 Controller Board. The IO100 board can only be accessed using the URL prefix https:// (rather than http://) since a secured connection is required. 

IO100 Endpoint Address

  • Scenario: The Host Web Services must contain the correct URLs to the iParcProfessional APIs.
  • Difficulty: Easy
  • Risk: Low

1. Navigate to the OPUS device's IO100 webpage.

2. Login to the IO100 webpage.

3. Hover the mouse over the Parking tab and select Board Settings.

4. Verify the OPUSCharge UI (Pro+) service URL contains the address (where FQDN is the fully qualified domain name of the OPUSCharge UI (Pro+) server): fqdn/opusite/opusadapter/api/aminet

5. Verify the Resolve parameter is set to [servername]443[serverip address]. Where [servername] is the name of the iParcProfessional PARCS host server and [serverip address] is the IP address of the iParcProfessional PARCS host server.

6. Save any changes.

7. Refresh OPUSCharge UI (Pro+) after pausing a few moments.



Can't Reset Password

  • Scenario: Forgot the administrator password and did not configure the SMTP server.
  • Difficulty: Hard
  • Risk: Medium

Important!

This is a difficult process that requires SQL Server knowledge and access. AMI recommends you contact AMI Technical Support for assistance.

1. Download the Papercut® mail server program from the Amano Knowledge Portal (AKP) to the Application Server. 

2. Launch Papercut.exe on the Application Server.

3. On the SQL Server, click the Windows Start  icon and launch Microsoft SQL Server Management Studio.

4. Login and click Connect to open the SQL database. The Object Explorer window is displayed.

5. Expand Databases > iParcCredit > Tables in the explorer tree.

6. Right-click on the dbo.CreditCardConfig filename to open the splash screen and select Edit Top 200 Rows. The Credit Card Config table parameters screen is displayed.

7. Scroll down the list until you locate the SMTP Server setting.

8. Check the Value checkbox corresponding to the SMTP Server setting.

9. Change the Value to 127.0.0.1 and click Enter.

10. The Papercut® mail server program does not use login credentials. Please verify the following parameters for each SMTP setting.

  • SMTPEmailAddress: (if no email address is provided, enter something@email.com)
  • SMTP Login Required: False
  • SMTP Port: 25
  • SMTPServer: 127.0.0.1 (as configured in Step 9)
  • SMTPUseSSL: False

11. Navigate to OPUSCharge UI (Pro+) on the SQL Server.

12. Enter the administrator User Name and any Password, if any.

13. Click Login. OPUSCharge UI (Pro+) will display the Reset Password button.

14. Click Reset PasswordThe Papercut® program will display a notification on the Application Server taskbar.

15. Launch Papercut® and click the OPUSCharge Password email. The temporary password is displayed.

16. Login to OPUSCharge UI (Pro+) using the new OPUSCharge UI (Pro+) password and reset the SMTP settings using the Alerts page. Refer to the Alerts section above for detailed information.

17. Close the Microsoft SQL Server Management Studio.

Windows Server – Microsoft SQL Server Management Studio.

OPUSCharge UI – Papercut Mail Server Program configuration.


OPUSCharge ↔ Merchant Connect MULTI® Communications

  • Scenario: Unknown whether OPUSCharge UI (Pro+) is communicating with Merchant Connect MULTI®.
  • Difficulty: Easy
  • Risk: Low
  1. Launch the Merchant Connect MULTI® service UI (C:\MerchantConnectMulti\Multi.exe).
  2. Verify the Terminal IDs are running (indicated by theicon).
  3. Position the MULTI UI window toward the right side of the monitor.
  4. Launch Internet Explorer®, navigate to OPUSCharge UI (Pro+) and login.
  5. Click Credit on the main menu bar. The Sales transaction screen is displayed by default. 
  6. Enter a sales transaction and click Process. If OPUSCharge UI (Pro+) is communicating with the MULTI® service, the Terminal ID display a red square icon and the Status column show Processing.

OPUSCharge UI – MerchantConnect MULTI communications.