Designed for Reliability

The Ogloba System uses a cross-border acquiring solution. Centered on in-house products developed by Ogloba it is already reliably operated for Tier 1 retailers throughout the world. Ogloba generally assumes the lion’s share of the processing, notably relating to switching for authorizations and transactions, providing fraud analysis and monitoring, settlement and reconciliation files, exceptions support and a data warehouse for reporting and processing, with controlled access to the data as agreed between Ogloba and our clients. It is assumed that e-commerce and m-commerce transactions are to be handled as part of this arrangement and that e-commerce transactions will pass through the Ogloba switch for processing.

Ogloba’s acquiring platform supports the core processing services required by most of our clients but, interfaces can be developed as part of the integration with client’s systems and partners. These may include for example, interfaces for cash registers and terminal transaction sources, gift card mall aggregators and settlement processing.

Transaction Data Warehouse

In order to meet our client’s internal and external operational, management and financial reporting requirements, Ogloba can set up, operate and maintain a central Transaction Data Warehouse (TDW) which consists of several functional physical databases. All transactions processed by the Ogloba Realtime System can be replicated into the Transaction Data Warehouse (TDW) in near real time (approximately a one minute delay). Exception items (disputed transactions) will also be included in the TDW. The Realtime System does not store PAN/Serial number data in clear form.

Clients can also receive an automatically predefined set of operational, management and financial reports from the TDW. Licensed users will be able to access the TDW remotely via a graphical user interface (GUI) to create and generate new ad hoc reports, reuse existing predefined and stored ad hoc reports and configure automatic report generation and delivery according to their requirements, including reporting based on transaction source, card types, etc. This will allow the creation (manual or automatic) and delivery of standard and ad hoc reports, their formatting and scheduling in a user friendly way.

The TDW is set up to have appropriate authentication and user profile data access control on different levels and appropriate audit trail of the changes applied to its data. The TDW has a user friendly web based GUI available for all internal and external users.

Physical Design

The Ogloba system is designed to be as reliable as possible. The system is deployed in an active-active configuration at Ogloba’s Primary and Secondary Data Processing Centers in order to ensure high performance, high availability and a disaster recovery capability. Installations at Ogloba’s primary and secondary sites in the U.S. share the processing load, but in case of non-availability of a site, a single site can handle the full load. Load balancing is carried out by configuring the gateway interfaces with primary and secondary addresses. The Production system is deployed in an active-passive configuration.

The server hardware and system architecture is based on Stratus ftServers. They are truly fault-tolerant servers with no single points of failure. The servers are capable of continuing to process even in circumstances where parts fail. In these situations, the servers will also inform Ogloba of the failure so that a replacement part can be fitted without service interruption. Stratus ftServers are considered to provide “Five Nines” (99.999%) availability for Linux based systems.