Filter
Top Products
Public/guest network access
Payment services
The service controller maintains a billing log that provides a simple audit trail of all
transactions The log supports the buffering and retransmission of up to 2000 billing records
to an external billing records server. You can configure log options on the Service
controller >> Public access > Records page.
Currency code
Specify the three-letter code for the currency in which all charges will be calculated. See the
online help for a complete list of currency codes.
Tax rate
Specify the tax rate to use when calculating sales tax for all charges.
Authorize.Net service
Payment URL
Specify the URL of the Authorize.Net server.
Login ID
Specify the login ID of the Authorize.Net account assigned to the service controller.
Transaction key
Specify the transaction key for the Authorize.Net account assigned to the service controller.
WorldPay service
Payment URL
Specify the URL of the WorldPay server.
Installation ID
Specify your WorldPay installation ID. This informs WorldPay to which merchant all sales
will be credited.
Response password
Specify your WorldPay installation response password.
Other configuration issues
To successfully make use of the WorldPay service you must also address the following issues:
The Internet port of the service controller must be reachable by the WorldPay servers.
This is required so that the WorldPay pages stored on the service controller can be
retrieved, and that the service controller can receive an HTTP/HTTPS post with payment
details. (To support HTTPS, a certificate signed by a well-known certificate authority
must be installed on the service controller.)
An access list must be defined on the service controller that gives users access to the
WorldPay site without being authenticated. For example:
access-list=factory,ACCEPT,tcp,*worldpay.com,all
If different, replace *worldpay.com with whatever is configured.
For complete configuration requirements, see the documentation on the WorldPay site.
8-37