Configuring the Fusebox Payment Module

1. In the EMC, select the Enterprise level, click Setup and Payments.
2. Insert a record and enter Credit Card as the name. 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 C:\MICROS\Simphony2\EgatewayService\handlers, select Micros.Payment.LoadableCreditCardModule.dll, and 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. In the Common Properties section, enter information in the following fields:

   Table 5-16 Common Properties Fields

   Field	Description
   Allow Manual Authorization Credit Card	This field indicates whether manual authorization of credit cards is allowed. Select True for processors using the Fusebox driver.
   Allow Partial Settlement On Batch	Select False for processors using the Fusebox driver.
   Do Not Batch	This field indicates whether batch creation and settlement occurs within Simphony. Select False for processors using the Fusebox driver.
   Encrypt Data	Select True for processors using the Fusebox driver.
   Manual Card Data Entry Retries	This field indicates the number of times a workstation operator can attempt to manually enter a card number. Oracle Hospitality recommends entering 5. The minimum value is 1.
   Offline Authorizations	This field indicates the number of offline card authorizations allowed before the application attempts to re-establish online communication.
   Prompt for Manual Card Data Entry	This field indicates whether workstation operators can manually enter a card number. Select True for processors using the Fusebox driver.
   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) If you need to configure Fusebox payment driver settings that are unique to the property or revenue center, continue with the following steps.
12. In the EMC, select the property or revenue center, click Setup and Payment Drivers.
13. Double-click the Fusebox record to open it.
14. On the General tab, click the Override this record link, and then click Yes.
15. Click the Configuration tab.
16. 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.
17. In the Elavon Driver Properties section, enter information in the following fields:

    Table 5-17 Elavon Driver Properties Fields

    Field	Description
    Chain Code	Elavon assigns the six-character alphanumeric code, 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 Point-of-Sale (POS), 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	After a communication failure with Fusebox, Simphony sends an inquiry to Fusebox to discover the cause of failure. This value is the amount of time Simphony waits before sending the request when a failure occurs. Oracle Hospitality recommends entering 5000.

18. Click Save.