Configuring the MICROS Standard Credit Card Payment Module

  1. In the EMC, select the Enterprise, property, revenue center, or zone, click Setup and Payments.
  2. Insert a record and name it based on the payment driver you are using (for example, MCreditDebit).
  3. Double-click the record to open it.
  4. Select 3 - DLL in the Content Type drop-down list.
  5. Select the Import from a file link.
  6. Browse to C:\MICROS\Simphony2\EgatewayService\handlers\Micros.Payment.MCreditDebit.dll, and click Open.
  7. Click the Configuration sub-tab.
  8. In the Assembly/Class section, enter information in the following fields:

    Table 5-25 Assembly/Class Fields

    Field Description

    Module ID

    Enter a description for the payment driver (for example, MicrosCreditDebitPaymentModuleStandard).

    Description

    Enter a description for the payment driver (for example, Micros Standard Credit/Debit Payment Driver).

  9. In the Common Properties section, enter information in the following fields:

    Table 5-26 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 MICROS standard credit and debit payment driver.

    Allow Partial Settlement On Batch

    Select False for processors using the MICROS standard credit and debit payment driver.

    Bank Identification Number

    Enter the 6-digit bank identification number provided by the bank or processor.

    Batch Number

    Enter a value between 1 and 9999 to indicate the next sequence number. The number increments by one each time a new batch is created, and resets to 1 after reaching 999. The bank or processor assigns the value for this field and uses it to detect duplicate batches.

    Do Not Batch

    This field indicates whether batch creation and settlement occurs within Simphony. Select False for processors using the MICROS standard credit and debit payment driver.

    Encrypt Data

    Select True for processors using the MICROS standard credit and debit payment module.

    Host Timeout

    Enter the timeout value in seconds. Setting the value to 0 (zero) equals a 30-second timeout. Do not leave this field blank. Oracle Hospitality recommends entering 60.

    This field applies only to Win32 machines. You cannot change the timeout from the default setting of 100 seconds on WinCE machines.

    Merchant Number

    Enter the merchant number provided by the bank or processor.

    Offline Authorizations

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

    Primary Host

    Enter the uniform resource locator (URL) of the payment provider application. As an example, this field should include something.receiving-url.com. For MerchantLink, enter g1.merchantlink.com.

    Primary Host Port

    Enter the port number used for the Primary Host. For MerchantLink, enter 443.

    Prompt for Manual Card Data Entry

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

    Retry Authorization Reversals On Batch

    Select False for processors using the MICROS standard credit and debit payment module.

    Run As Service

    Select False for processors using the MICROS standard credit and debit payment module.

    Store Number

    Enter the 4-digit store identification number used to identify the merchant store. The bank or processor assigns the value for this field.

    Terminal Number

    Enter the workstation number at the merchant store.

    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.

    VisaQ Compatibility

    Select False for processors using the MICROS standard credit and debit payment driver.

  10. If you are using the VisaD driver, enter information in the VisaD Driver Specific section fields:

    Table 5-27 VisaD Driver Specific Fields

    Field Description

    Agent Bank Number

    Enter a six-digit number that identifies the Agent Bank Number. This value identifies the agent of the acquirer which signed the merchant. The acquirer provides this value to the merchant.

    Agent Chain Number

    Enter a six-digit number that identifies the Agent Chain Number. This value identifies a specific chain of an agent organization. The merchant's bank or processor provides this number.

    City Code

    The city code identifies the merchant’s location. Within the United States, enter the five- or nine-digit zip code of the merchant’s address. In other countries, the bank or processor assigns the code.

    Country Code

    Select the country that identifies where the merchant is located. The bank or processor assigns the value for this field. The United States country code is 840.

    Currency Code

    Select the currency that the merchant uses. The bank or processor assigns the value for this field. The United States currency code is 840.

    Enable Card Level Results

    Select True to have the the VisaD driver retrieve card-level results during authorization and return the data at settlement.

    Enable POS Data Code

    Select True to have the VisaD driver report the POS Data Code at authorization and settlement.

    Include Exp Date And Extra Mag Card Data

    Select True to include the expiration date and modified magnetic stripe reader data during settlement.

    Industry Type

    Select a value to identify the industry type to the merchant. The bank or processor assigns the value for this field.

    Language Indicator

    This field is used to designate the language in which Authorization Response messages should be returned to the workstation for display and printing. The bank or processor assigns the value for this field.

    Max Batch Records

    Enter the maximum number of records that can be transferred in one batch (for example, 9999). Some banks and driver types can support only a specific number of records during credit card settlement. When you enter 0 (zero), all records are processed in the same batch.

    Merchant Category

    Enter the four-digit number assigned by the bank or processor to identify the merchant type.

    Merchant Location

    Enter the merchant location or city name provided by the bank or processor. For auditing purposes, the Merchant Location should correspond to the location or city that prints on a credit card voucher.

    Merchant Name

    Enter the merchant’s name. For auditing purposes, the Merchant Name should correspond to the name that prints on a credit card voucher.

    Merchant State

    Enter the merchant’s state or province code provided by the bank or processor. For auditing purposes, the Merchant State should correspond to the state or province code that prints on a credit card voucher.

    Request URI

    If applicable, enter the uniform resource identifier (URI) to use when sending VisaD messages to the processor. For MerchantLink, enter /Micros/process_transaction.cgi.

    Secondary Host

    Enter the uniform resource locator (URL) of the secondary host. As an example, this field should include something.receiving-url.com. For MerchantLink, enter g2.merchantlink.com.

    Secondary Host Port

    Enter the port number used for the Secondary Host. For MerchantLink, enter 443.

    Send RFID Data

    Select True to add RFID-related fields to the message. Some processors require this information to authorize and settle RFID transactions.

    Time Zone

    Select the code used to calculate the local time within the VisaNet Authorization System. The bank or processor assigns the value for this field.

  11. Click Save.

Related Topics