Mercury Payment Systems
Mercury Payment Systems is the easy and affordable way to get fast
2-3 second transaction processing and real-time web reporting. Traditional
Dial-Up Processing: Merchants can process through Mercury Payment
Systems by using a Datacap DataTran configured for Global Payment's
East (NDC) platform. Mercury Payment Systems also works with terminals
from Verifone, Hypercom and Nurit (and many others as well).
IP Processing Always On Dial-Up Connection: Merchants can use a
router and
modem combination to create a reliable dial-up connection in lieu
of a
broadband connection. This option still provides fast processing
(4-5 seconds)
and real-time web reporting. It also has the advantage of permitting
multiple credit card transactions simultaneously (a Datatran is
not used).
IP Processing Always On Broadband Connection: The ideal scenario
is where
the merchant can obtain a broadband connection (DSL, cable, etc.).
This option is a little bit faster (2-3 second processing).
How MercuryPay Works
Mercury Payment Systems' MercuryPay is co-developed with our Strategic
Partner
Datacap Systems, Inc. The MercuryPay system is a client-server payment
processing
application that moves transaction information from the client to
server in encrypted
tcp/ip packets. On the client side is an activeX component that
is integrated into the
Point of Sale program. This component works with the MercuryPay
server, standalone
NetEpay servers, as well as Datacap's System's Datatran dial-up
processing machine.
From Mercury's servers they are sent over a point-to-point connection
to Global
Payments Inc. The FDIC insured funds are then securely and rapidly
transferred by
HSBC Bank to the merchant's account at the bank of their choice.
The full card numbers
are never stored on Mercury's servers (only in the processing host).
MercuryPay Server Configuration
Mercury Payment Systems maintains multiple servers for redundancy and
load balancing. These servers are located in different regions of the
country to maintain independent operations even if a whole region is
experiencing telecommunications difficulties. Each MercuryPay server is
directly connected to the processing host.
Each server has a DNS name - the client component is configured with a
list of these names. In the event that the primary MercuryPay server
name is unresponsive during an attempted transaction, the client component
will use the alternate server.
To have us order, customize, and/or install your Mercury Payment
Systems,
please contact us and let us know
how we can help!
|
