Appendix
E.
External
Payment
Gateways
This
section
is
to
show
independent
Hotspot
owners
how
to
configure
related
settings
in
order
to
accept
payments
via
Authorize.net,
PayPal,
SecurePay
or
WorldPay,
making
the
Hot
Spot
Wi
‐
Fi
an
e
‐
commerce
environment
for
end
users
to
pay
for
and
obtain
Internet
access
with
credit
cards.
1.
Payments
via
Authorize.Net
To
configure
Payments
via
Authorize.Net,
go
to:
Users
>>
Authentication
>>
On
‐
demand
User
>>
External
Payment
Gateway
>>
Authorize.Net
.
Before
setting
up
“Authorize.Net”,
it
is
required
that
the
merchant
owners
have
a
valid
Authorize.Net
account.
>
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.
Test
Mode
:
In
this
mode,
merchants
can
post
test
transactions
for
free
to
check
if
the
payment
function
works
properly.
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
are
actually
sent
from
the
Authorize.Net.
129