OmniPayments Architecture

OmniPayments is based on a modern, component-based design and an open  SOA environment.  It is built on the HP NonStop platform in order to satisfy the highest possible reliability, availability, scalability, and performance demands of today’s payments industry.  OmniPayments easily can be configured to meet existing transaction processing rates and later can be scaled to accommodate new growth requirements.  User exits are easy to customize, and the graphical user interface is intuitive and requires little training.




OmniDirector is a rules-based routing engine that serves as the OmniPayments foundation for communication over a variety of protocols and to provide data transformation, intelligent routing, and custom business functions. OmniDirector offers the core services necessary for an enterprise to operate in real time. It routes messages or transactions between source devices and enterprise backend systems to implement business functions that must react without delay.

Business Logic Modules

At the core of OmniPayments is a set of Business Logic Modules, or BLMs, each tasked with enabling a specific service.   For instance, OmniATM manages ATMs, OmniPOS controls POS devices, and OmniAuth provides authorization services.  OmniPayments’ structured design permits the ongoing addition of new BLMs that can support new features and business functions as the market demands.


Adapters manage the information exchanged between end users and the business components (BLMs).  They can be designed to communicate with any acquiring or issuing entity, including Internet portals, hardware devices, service providers or interchanges (Visa, MasterCard, etc.) and in-house systems. OmniPayments provides Acquirer Adapters for ATMs, POS devices, IVR systems, the Internet, and bank tellers.  Issuer Adapters are provided for local host communications and for the variety of financial interchange switches with which OmniPayments must interface.

Core Services

Core services include:  Communication adapters supporting protocols such as TCP/IP, HTTP, SOAP, and IFX  ●  Rules-based intelligent routing of messages between issuing devices and service providers  ●  Validation of incoming clients upon connection requests ● Encryption of in-flight and at-rest data  ●  Database adapters for Oracle, NonStop SQL, Enscribe, MySQL, and others  ● Exception handling by retrying messages within the allowed transaction timeout  ●  Failover and retry of transmissions over failed communication channels  ●  Multithreading of context-sensitive message-processing sessions  ●  Data transformation between message formats such as XML and ISO 8583  ●  Transaction processing adapters for NonStop Tuxedo, IBM MQ series, NonStop Pathway, and others  ●  Load balancing among pooled service providers.

Modern User Interface

OmniPayments includes a graphical user interface for operations such as terminal network monitoring, system maintenance, and system administration.  The interface is presented to the user in a file tab structure that simplifies the look and organization of data.  Built-in functions simplify user operations. They include drop-down lists, pop-up hints, data entry validations and context-sensitive online help.  Users can perform transaction log queries and produce on-demand transaction and MIS reports.

Active/Passive, Active/Active Architectures

OmniPayments supports both active/passive and active/active architectures.  In an active/passive architecture, a geographically remote idle backup system (or one running other less critical applications) is available to take over processing should the active system fail. In an active/active architecture, two or more geographically dispersed systems cooperate to simultaneously process transactions for the same application. Should one system fail, all further transactions are simply routed to surviving systems.