| If your payment processor’s system is
down, you lose orders -- and customers. If your payment processing system loses your
transactions, you lose revenue. If your payment processing solution settles transactions
that never were completed, you lose time and customer goodwill when correcting the
problem. Reliability is a critical requirement for any transaction processing service.
PaymentNet’s service architecture has been designed to provide both high service
reliability and high transaction processing accuracy. High Service Availability
We maintain high service availability at our secure
operations center through redundant connections to the Internet and to our processing
partner operation center and through our redundant, real-time failover system design. The
design of our server complex eliminates single points of failure at the hardware, network
and application levels. Networking equipment is installed in identical, cross-connected,
auto-failover pairs, with identical sets (two or more) for each service we provide. At the
application level, our servers provide both load balancing and auto-failover when using
network and database resources. At the backend, if a single connection to a processor
fails, traffic is automatically routed to other working connections. The result: High
service availability from a robust system that can automatically recover from incidental
failures and that can adjust and recover from more substantial ones -- all without
interruption of service delivery.
High Transaction Accuracy
Reliable processing also requires accurate transmission
of payment data. PaymentNet’s client monitors user connectivity throughout the
transaction process with abandoned or disconnected sessions that result in abandoned
transactions. Our client API also provides a facility for specifying a timeout period.
This timeout period is passed to the PaymentNet transaction servers and the servers will
attempt to process the transaction in the time allotted. Should the financial host
processor not respond in time, PaymentNet’s server will respond with a "Host
Time-out" error. Should the client not receive a response in time, the client will
issue a "client time-out" error. By actively monitoring at the client,
PaymentNet’s servers log only completed transactions.
The communication process used between the client and
server was designed to ensure that transactions are reliably transmitted to the PaymentNet
servers. Once in our secure data center, the transaction is logged (in addition to being
logged with the host financial system). PaymentNet provides all customers with a
comprehensive set of reports and transaction management tools that allow easy
reconciliation of settled transactions. |
