Public/guest network access
Managing payment services
14-36
The 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 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 controller.
Transaction key
Specify the transaction key for the Authorize.Net account assigned to the 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 controller must be reachable by the WorldPay servers. This is
required so that the WorldPay pages stored on the controller can be retrieved, and that
the 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
controller.)
An access list must be defined on the 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.
To Next Page
Loading...
Need help?
General
