Elements of Performance
Transaction processing performance is measured by two elements: response time and
accuracy. PaymentNet's client/server architecture delivers superior performance against
both criteria, especially as throughput demand increases.
- PaymentNet's unparalleled response time is accredited to the use of multiple threads and
simultaneous processing (as opposed to serial throughput), with our processing system
optimized for transaction speed.
- PaymentNet’s accuracy is secured through monitoring user connectivity throughout
the transaction process; abandoned or disconnected sessions result in abandoned
transactions (not accidental payment). This level of user connectivity monitoring is not
possible using http-based solutions, giving a distinct advantage to businesses using
PaymentNet solutions.
PaymentNet’s Record
Our results speak for themselves. While we will guarantee round-trip transaction times
of less than 10 seconds, over 90% of our transactions are returned back to the client in
less than 3 seconds! PaymentNet is committed to add capacity as our (and your) transaction
volumes grow to maintain or improve transaction throughput.
Performance Measurements
Performance measurements are difficult on the Internet. The figure below shows the life of
a transaction and some typical transaction times for each step. By not only
designing our system for highest possible throughput, but also instrumenting the system
with performance monitors at both the client and the transaction server, PaymentNet is
able to assess our service performance in real-time and provide transaction performance
reports to our highest volume customers.
| The timing of the
transaction at different stages can vary widely between Internet business implementations.
The following numbers are meant for comparison use only. |
| 1. Consumer request sent from consumer's browser to
merchant web server. |
1.0 second |
| 2. Merchant web site prepares request for payment
processing. |
0.5 seconds |
| 3. Merchant web site sends payment authorization request
to PaymentNet server. |
0.5 seconds |
| 4. PaymentNet server receives authorization request,
prepares to send to processor. |
0.1 seconds |
| 5. PaymentNet server sends authorization request to
processor. |
2.0 seconds |
| 6. PaymentNet server logs and prepares result for client. |
0.2 seconds |
| 7. PaymentNet server sends results to merchant web site. |
0.5 seconds |
| 8. Merchant web site receives result, logs it, and
prepares HTML response for consumer. |
1.0 second |
| 9. Merchant web site sends HTML response to consumer's
web browser. |
1.0 second |
| Typical Transaction Time |
6.8 seconds |
|
