To access the MiraServ payment gateways, navigate to the Registry application System::Configuration::Payment Gateways node.
 |
Information
For those gateways that support multiple types of payments (e.g. Credit or Debit), add a new 'Key' to the Payment Gateways list in the format of PaymentGateway::PaymentType (e.g. MiraServ::Credit). For more information, refer to General Configuration - Lists. |
|
Field |
Description |
|
default_merchant_description |
The merchant description that is displayed on the customer’s credit card statement. This default setting can be overridden when configuring series and performances. You can also display this on the ticket.
If more than one merchant description is associated with an order, such as multiple performances with different descriptions, the application will display the default description from the Registry. If there is no default, then no description is displayed. |
|
hostname |
Name or IP of the computer running the MiraServ software. |
|
hostport |
Port number of the computer running the MiraServ software. |
|
library_path |
Absolute path to respective AudienceView payment gateway DLL. |
|
log_file |
Absolute path to a file on the local server where payment processing data is saved. Include the file name in the path. If the file does not exist, it will automatically be created. |
|
process_details |
For those gateways that support multiple types of payments, this field identifies the type of payment (e.g. Credit or Debit). |
|
process_strategy |
Identifies how the payment is to be processed:
-
External: Process payment external third party.
This is the only valid option for this payment gateway.
-
Account: Process payments as an AudienceView internal account.
-
Gift Card: Process payment as an AudienceView gift certificate.
-
Gift Certificate: Process payment as an AudienceView gift certificate.
|
|
rotate_log_file |
Y: a new log file will be created each day, with the creation date included as part of its name.
N: a single log file is used.
It is recommended that you use log rotation, as the log file is locked while the application is running and cannot be moved or deleted. |
|
terminal_allocation |
Queued: Requires AudienceView to queue the requests to the terminals.
Round Robin: Gateway can queue the requests on its terminals. |
|
terminal_required |
All: Requires terminal for all transactions (swiped and keyed).
For more information on configuring terminals, refer to Terminals and Configuring Payment Terminals. |
|
timeout |
Gateway timeout, in seconds. |
|
verbose_log |
Y: log file contains detailed information.
N: log file contains summary information. |