Configuring the Fusebox Payment Module

  1. Select the Enterprise level, click Setup, and then click Payments.
  2. Insert a record, enter Credit Card as the name, and then click OK. If a Credit Card payment record exists, skip this step.
  3. Double-click the record to open it.
  4. On the General tab, click the Import from a file link.
  5. Browse to [Drive Letter]:\MICROS\Simphony2\EgatewayService\handlers, select Micros.Payment.LoadableCreditCardModule.dll, and then click Open.
  6. Select Fusebox from the Driver drop-down list.
  7. Select the appropriate device from the Device drop-down list.
    • Select Internal for Oracle Hospitality devices.

    • Select the third-party device if the property is using a custom device driver.

  8. Click the Configuration tab.
  9. From the Common Properties section, enter information in the following fields:

    Table 12-16 Common Properties Fields

    Field Description

    Allow Manual Authorization Credit Card

    Select True for processors using the Fusebox driver. This field indicates whether manual authorization of credit cards is allowed.

    Allow Partial Settlement On Batch

    Select False for processors using the Fusebox driver.

    Do Not Batch

    Select False for processors using the Fusebox driver. This field indicates whether batch creation and settlement occurs within Simphony.

    Encrypt Data

    Select True for processors using the Fusebox driver.

    Manual Card Data Entry Retries

    Enter the number of times a workstation operator can attempt to manually enter a card number. Oracle recommends entering 5. The minimum value is 1.

    Offline Authorizations

    Enter the number of offline card authorizations allowed before the application attempts to re-establish online communication.

    Prompt for Manual Card Data Entry

    Select True for processors using the Fusebox driver. This field indicates whether workstation operators can manually enter a card number.

    Retry Authorization Reversals On Batch

    Select False for processors using the Fusebox driver.

    Run As Service

    Select False for processors using the Fusebox driver.

  10. Click Save.
  11. (Optional) To configure Fusebox payment driver settings that are unique to the property or revenue center:
    1. Select the property or revenue center, click Setup , and then click Payment Drivers.
    2. Double-click the Fusebox record to open it.
    3. On the General tab, click the Override this record link, and then click Yes.
    4. Click the Configuration tab.
    5. If stunnel is installed on a single workstation at the property, enter the Primary Host in the Transport Service Properties section. This is the IP address of the machine that houses stunnel for Fusebox, or the IP address for authorizations to the ProtoBase Hosted Solution.
    6. From the Elavon Driver Properties section, enter information in the following fields:

      Table 12-17 Elavon Driver Properties Fields

      Field Description

      Chain Code

      Enter the six-character alphanumeric code assigned by Elavon, which is used for key management in gateway environments. The Chain Code is used with Fusebox, but not with ProtoBase.

      LocationName

      If Elavon supplied a Location Name or Source IP Adress to pass from the POS client, enter it here. This value passes on every transaction and can be the location name or Fusebox workstation. You can leave this field blank.

      The LocationName is used with Fusebox, but not with ProtoBase.

      TerminationID

      Enter the Terminal Code assigned by Elavon for the property to use with credit cards.

      TransactionInquiryRetryDelayTimeoutMS

      Enter the amount of time Simphony waits before sending the request when a failure occurs. After a communication failure with Fusebox, Simphony sends an inquiry to Fusebox to discover the cause of failure. Oracle recommends entering 5000.

    7. Click Save.