|
If you currently operate a legacy payment processing system, you ought to be asking yourself the following questions:
Can I implement a new network interface in less than 60 days?
Am I satisfied with my current cost per transaction?
How expensive was our last hardware upgrade?
Do our software license and maintenance fees increase because of hardware upgrades or business expansion?
Is what we are paying in software consulting fees for upkeep of our system seem excessive?
Do I feel like we have to pay a premium price to maintain a OLTP specialist team?
Am I tired of being told that our payment system environment is 'unique' and the changes we need will takes months or years?
++++++++++++++++++++++++++
If you are running a legacy payment system right now, you may be caught in an increasingly indefensible position:
a costly, proprietary architecture; a limited, expensive labor pool; and an increasingly callous software vendor only interested in collecting their annuity from you.
|
|
OLS.Switch - Next Generation Payment Switch
OLS has provided real 24x7x365 production support for mission-critical payment systems for over a decade. Using 'best business and technology practices' accumulated from the hundreds of installations we have been involved with, we developed a robust, intuitive, high performance, easily changeable, rapidly implementable payment systems engine we market under the brand name "OLS.Switch".
You can use OLS.Switch to (a) replace your current switch; (b) work in conjunction with your current switch to reduce development costs; or (c) transition from an outsourced to 'in-sourced' solution.
Whether you currently "in-house", "in-source" or "outsource", OLS can devise a risk-mitigated migration plan so you can quickly implement OLS.Switch to replace, or co-exist with, your current payment solution. With OLS.Switch, you can begin reducing your cost per transaction sooner rather than later, resulting in a rapid "mean-time to payback" on your investment.
Why did we develop a new product of this nature for the payments processing market?
|
Payment system users were was looking for more open, cost effective answers to its payments processing needs and trying to move away from “legacy” OLTP solutions
Collection of best practices for payment systems for retailing, banking, pharmacies, payroll companies.
Payment processing has moved far beyond processing basic bank supplied debit and credit card transactions and is still evolving as on-line processing of the full realm of personal consumption expenditures (PCE) is becoming reality.
The entire IT industry has dedicated significant resources to realizing the benefits available through the use of Linux, Java and other web-oriented open technologies.
Our clients and the many organizations we interface with repeatedly communicated the need for changes to their payments processing environment such as new devices, message formats, network interfaces or industry mandates to be implemented quickly and easily. |
OLS.Switch Success Stories
 |
High Performance
OLS customer benchmarks OLS.Switch at over 300 transactions per second (TPS).
OLS.Switch was benchmarked running on a small PC sever pool using Microsoft Server technology. The benchmark driver reached capacity at a little over 300 TPS and OLS.Switch was still below its maximum capacity. |
|
 |
Ultra High Performance
OLS Customer implements OLS.Switch in custom environment to run 1,000 transactions per second (TPS).
OLS.Switch technology was used by a customer in a special hardware and system software environment to prepare for processing over 1,000 transactions per second. The implementation will eventually be processing up to 2,000 TPS. |
|
 |
Rapid Implementation
OLS customer implements OLS.Switch in less than 60 days.
OLS.Switch technology was used by a customer in a special hardware and system software environment to prepare for processing over 1,000 transactions per second. The implementation will eventually be processing up to 2,000 TPS. |
|
 |
Employee IDS and Stored Value Cards
| OLS customer uses OLS.Switch to implement "new" payment types. OLS.Switch was processing debit and credit transactions accepted on terminals in a retail store environment. The OLS.Switch system was enhanced by OLS' Consulting Service consultants to verify employee ID cards as well as process for authorization several forms of stored value cards. |
|
 |
Stored Value Remittance cards
| OLS customer uses OLS.Switch to implement International remittance cards. OLS.Switch was enhanced by OLS' Consulting Service consultants to authorize customer issued card transactions. These transaction cards were used to send monies from the US back home to relatives in various countries. |
|
OLS.Switch Features and Benefits
For a detailed overview of OLS.Switch, click here (PDF).
OLS.Switch for Merchants/Acquirers
To see how messages flow through OLS.Switch for merchants and acquirers, click here (PDF).
OLS.Switch for Issuers/Authorizers
To see how messages flow through OLS.Switch for issuers and authorizers, click here (PDF).
OLS.Switch Architectural Diagram
To see a high level architecture diagram of OLS.Switch, click here (PDF).
OLS.Switch Transaction Flow
To see an architectural view of message flows thorugh OLS.Switch, click here (PDF).
|