MSM7xx Controllers Configuration Guide v6.4.0

Service settings
Payment method: Credit card
Enable this option to allow users to pay for services via credit card. The controller makes use
of a third-party credit card processing service (either Authorize.NET or WorldPay) to handle
credit card transactions.
Communications with the credit card service occurs via an SSL connection. In the case of
Worldpay, you must purchase the appropriate certificate as required and install it on the
Controller >> Security > Certificates stores page. The other payment methods do not require
installation of a certificate.
The controller does not keep a record of the users credit card information. All information
handled by the system is securely managed in accordance with the PCI DSS v1.2 standard.
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 > Billing 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
422 Public/guest network access