The Heart of Payment Transactions

What Problems Does @Core Engine Solve?

Slow and Unreliable Payment Approvals

High Risk of Fraudulent Transactions

Inaccurate or Unavailable Account Balances

At the heart of your payment infrastructure, Core Engine delivers critical authorization capabilities with uncompromising performance and reliability. Acting as the central nervous system of transaction processing, it seamlessly coordinates data flow between core banking systems and card processor systems.

Fast and Reliable Payment Authorization

@Core Engine is an independent authorization system that enables instant transaction approvals without relying on card processor configurations. It intelligently evaluates payments in real time based on available balances, limits, and custom rules. With autonomous decision-making, high scalability, and a resilient architecture, it delivers maximum control over payment processes – even under extreme load.

☑️ Independent Authorization Processing
Operates autonomously, without dependency on card processors.

☑️ High Performance and Scalability
Processes multiple requests simultaneously, even under high traffic.

☑️ Resilient Architecture
Continues to authorize payments even during Core Banking outages.

Central Point for Authorizing Transactions

Manage Authorizations Quickly, Securely, and Independently from External Processors

250+ TPS per Core.
Stability Without Compromise.

In the world of payments, milliseconds matter.
@Core Engine is built to handle extreme transactional loads without slowing down. With 250+ TPS (Transactions Per Second) per core, even at peak times, everything runs smoothly, quickly, and without compromise.

☑️ Lightning-Fast Processing
Transaction approvals in milliseconds – no delays, no downtime.

☑️ Unstoppable Performance
Consistent speed, even under maximum system load.

☑️ Optimized for Scalability
Seamless performance from hundreds to millions of transactions – all with low latency.

Speed, Performance, Unmatched Efficiency!

Performance Metrics

☑️ 3 Independent Data Centers
Ensure high availability and robust security.

☑️ Balanced Network Connectivity
Optimized connections at the telco network level.

☑️ Highly Available Architecture
Live replication between instances for seamless uptime.

☑️ 250 TPS
Handles up to 250 transactions per second.

☑️ Average Decision Time: 6.33 ms
Instant payment authorization.

Feature Overview:

Acts as a centralized integration hub, collecting data from multiple sources

Customizable configuration

based on client needs and transaction requirements

Simultaneous evaluation of multiple authorization requests

enables efficient real-time processing of high transaction volumes

Balances are continuously updated based on authorized transactions, ensuring real-time accuracy

Supports multiple authorization protocol formats

(e.g., ISO8583, ISO20022, and REST API)

Transactions can be approved or declined even if the connection to the core banking system is interrupted

Independent and flexible decision-making

tailored to specific authorization needs

Can operate as a secondary stand-in mechanism

Vše, co potřebujete pro správu platebních autorizací

Autonomous operation without dependency on external payment processor configurations

Download:

Want to learn more about this product?

Download a detailed PDF document with all the key information, specifications, and integration options.

What’s inside the document?

☑️ Overview of features and key capabilities

☑️ Technical specifications and integration options

☑️ Business benefits and advantages

☑️ Support and security standards

Frequently Asked Questions

How Do We Achieve Such Fast Authorization Times?

To ensure fast and efficient processing of card transactions, we use Redis, a modern in-memory database known for its exceptional speed and reliability. By leveraging parallel processing, we can instantly authorize multiple card transactions received at the same time without delay.

The available balance, all card limits, restrictions, and individual card configurations are stored directly within our authorization system. This enables real-time approvals without the need for additional external lookups during the authorization process, significantly reducing response times and enhancing the user experience.

How Is Data Replication Between Nodes Ensured?

Data replication between nodes is handled using Redis Sentinel, which operates on a master-slave architecture. In this setup, the master node is responsible for all data writes, while replica nodes (slaves) perform read operations and continuously synchronize data from the master.

Redis Sentinel continuously monitors the health and availability of all nodes. In the event of a master node failure, Sentinel automatically performs a failover, promoting one of the replicas to become the new master.

Client applications then automatically reconnect to the new master node, ensuring high availability, reliability, and continuous operation without requiring manual intervention.

Can the Performance of Core Engine Be Further Scaled?

Yes. After deploying the system to a production environment, we conducted extensive performance (PERF) testing and verified disaster recovery (DR) resilience. During these tests, a single instance of Core Engine achieved a peak throughput of up to 250 authorizations per second (TPS).

To ensure high availability, geographical redundancy, and disaster recovery readiness, we typically operate with at least two separate instances of Core Engine. This setup allows us to comfortably handle peak loads of approximately 500 TPS.

If higher performance is required in the future, the system is designed to scale linearly by simply adding more Core Engine instances, ensuring flexible and predictable capacity expansion.

Can Core Engine Perform Authorizations Even If the System Providing Available Balances Is Unavailable?

Yes. All critical data required for successful card authorization is stored locally within the authorization system itself. External primary systems—such as the Core Banking System, Card Management System, or Anti-Fraud System—provide only updates and change information, which are continuously reflected in the locally stored dataset.

Thanks to this architecture, the system can respond efficiently to changes, even when one or more primary systems become temporarily unavailable. During such outages, the authorization system continues to process transactions reliably using the most recent available data on balances, card limits, and restrictions.

This approach significantly increases system robustness, minimizes the risk of errors, and ensures uninterrupted service availability for end users.