Powering Regulatory Oversight: A Configurable API Platform for the Central Bank of Armenia

Executive Summary

Industry: FinTech, GovTech

Engagement: Business Analysis, Software Development

Region: Armenia

Project at a Glance

When a new regulation required every foreign exchange operator in Armenia to report transaction data to the central bank every 30 minutes, CBA needed the infrastructure to make it work. VOLO delivered NeX, a configurable API platform built to ingest those reports at scale, request additional detail when supervisory logic called for it, and adapt as regulatory requirements evolve.

About the Client

The Central Bank of Armenia (CBA) is the country's central monetary authority, responsible for monetary policy, financial stability, and oversight of Armenia's banking and foreign exchange sectors. As Armenia's financial market continues to develop, CBA has been investing in modern regulatory infrastructure that can keep pace with market activity in real time.

Foreign exchange oversight is one of those investment areas. With banks, exchange offices, and other operators handling transactions throughout the day, CBA needed regulatory technology built for high-frequency data and configurable enough to evolve with the rules.

Our Engagement

Given VOLO's strong focus and portfolio in the financial sector, particularly within Armenia's financial ecosystem, CBA engaged us to design and deliver this system. The receiving system needed to ingest operator reports, evaluate whether additional detail was required, automatically request that detail back through a callback mechanism, and remain configurable so CBA staff could adjust reporting parameters as regulations evolve.

VOLO led business analysis, backend development, and quality assurance for NeX, working with a focused team in a waterfall delivery model. The compact team kept the scope tight; close coordination with CBA ensured that the regulatory intent was translated accurately into platform behavior.

Our scope covered the core operational layer of the platform:

Regulatory data ingestion API. Built the API surface that receives 30-minute transaction summaries from foreign exchange operators across Armenia, with validation logic to ensure submissions meet regulatory specifications.

Automated callback flow. Designed the mechanism that allows NeX to call back to operators through their APIs to request additional data when summary-level reporting wasn't sufficient.
Configurable reporting logic. Built configurability into the platform from the ground up, allowing CBA to adjust reporting rules and parameters without engineering work each time.
Scheduled job infrastructure. Implemented background processing using Hangfire, MongoDB, and Redis to handle the 30-minute reporting cadence reliably at scale.
QA for a regulatory system. Validated platform behavior across edge cases, malformed submissions, and high-frequency data flows, where the cost of bugs is higher than in commercial software.

Have a Complex Challenge to Solve?

Talk to an Expert

Key Takeaways

Regulatory technology demands precision.

NeX serves a supervisory function, so VOLO's BA and QA work focused on getting the behavior exactly right, with no margin for ambiguity in how the platform interprets the regulation. 

Architecture should match the cadence of the work.

Hangfire, MongoDB, and Redis were chosen specifically for a high-frequency, schedule-driven regulatory workflow. The infrastructure was built around the actual operational tempo. 

Configurability is a feature, not a nice-to-have.

Regulations evolve. Building configurability in from the start meant CBA wouldn't depend on engineering cycles for every parameter change. 

Small focused teams can deliver institutional-grade software.

With one BA, one developer, and one QA engineer, VOLO delivered a platform built to serve the central bank of an entire country. Discipline matters more than headcount. 