AirLive WIAS-1200G
User’s Guide
54
Authorize.Net
Before setting up “Authorize.Net”, it is required that the merchant owners have a valid Authorize.Net
account. Please see
Appendix B – Accepting Payments via Authorize.Net,
Appendix E – Examples of
Making Payments for End Users
for more information about opening an Authorize.Net account and
related maintenance functions.
External Payment Gateway/ Authorize.Net Payment Page Configuration
¾
Authorize.Net Payment Page Configuration
Merchant ID:
This is the “Login ID” that comes with the Authorize.Net account
Merchant Transaction Key:
The merchant transaction key is similar to a password and is used by
Authorize.Net to authenticate transactions.
Payment Gateway URL:
This is the default website address to post all transaction data.
Verify SSL Certificate
: This is to help protect the system from accessing a website other than
Authorize.Net
MD5 Hash:
If transaction responses need to be encrypted by the Payment Gateway, enter and confirm
a MD5 Hash Value and select a reactive mode. The MD5 Hash security feature enables merchants to
verify that the results of a transaction, or transaction response, received by their server were actually
sent from the Authorize.Net.
Test Mode
: In this mode, merchants can post
test
transactions
for free
to check if the payment
function works properly.
