The Chief Technology Officer (CTO) of Afridext Integrated Services Inc (Respectmart), Enitan A. Awosanya, who joined the company as a Lead Software Developer, has played a key role in building fintech and logistics systems for cross-border operations. With experience spanning backend engineering, fintech systems, and SaaS platform development, and a strong academic foundation including an MSc in Fintech from Teesside University, United Kingdom, Awosanya in this interview, shares insights into the technical, architectural, and operational challenges of designing reliable transaction systems and what it means for the future of borderless digital commerce.

Let’s start with your professional journey. How did it all begin?
My journey into software engineering began in 2018 at DamisaGurus Limited, a Nigerian tech startup, where I worked as a web developer. I built a secure school-record management system using PHP and MySQL and also taught backend development best practices.

That early experience grounded me in designing systems that prioritise data integrity, access control, and usability while working under real delivery constraints. It also shaped how I think about software, not just as features, but as systems that must behave reliably in real-world conditions.

As my career progressed, I moved into more complex backend systems, eventually specialising in fintech and SaaS platforms where correctness, security, and scalability are critical.

What was the next phase — when did leadership and architecture come into the picture?
By 2020, at Upperlink Limited, I transitioned into backend-focused engineering, working on fintech systems that integrated multiple third-party financial APIs and handled real transactional workloads.

I rebuilt an e-commerce backend that improved load time by 30% and integrated multiple payment gateways, increasing checkout conversion by 20%. More importantly, I worked on a fintech application where I optimised transaction processing pipelines, reducing processing time by 40% and enabling the system to handle 30% more daily volume.

At this stage, my focus shifted from feature delivery to system-level optimisation, dealing with query performance bottlenecks, API latency and throughput, as well as data consistency across distributed integrations.

In 2021, I joined Afridext Integrated Services Inc (Respectmart) as Lead Software Developer and later assumed CTO-level responsibilities, where I led architecture decisions and managed a team building a multi-tenant SaaS platform.

When did you first realise this was a systemic problem, not just an organisational issue?
The realisation came during my time at Upperlink while working on fintech systems that integrated multiple third-party financial APIs and handled increasing transaction volumes.

As the system scaled, we began to see consistent failure patterns that pointed to architectural weaknesses rather than isolated bugs. There were duplicate transactions triggered by retries and network timeouts, inconsistent transaction states when external APIs partially succeeded, and complex reconciliation across multiple providers with no single source of truth.

These issues were most evident in asynchronous flows, where external operations could succeed but internal state updates would fail or lag, leaving transactions in undefined or conflicting states.

At that point, I was already implementing security controls such as MFA and role-based access control, and optimising performance. However, it became clear that neither security nor performance addressed the core issue—the system lacked deterministic control over transaction lifecycles.

My MSc in Fintech further reinforced this understanding through exposure to distributed trust systems and fraud prevention models. It became evident that the root problem was nondeterministic system design, where workflows were not explicitly modelled or enforced.

That was the turning point. I shifted from designing systems as request-response interactions to structuring them around explicit transaction state machines to enforce valid transitions, idempotent operations to guarantee safe retries, and asynchronous processing layers to isolate external dependencies. This approach allowed the system to behave predictably under failure conditions, ensuring that every transaction is consistent, traceable, and recoverable.

Why is robust fintech and logistics infrastructure important for startups and SMBs operating across borders?
From a technical standpoint, cross-border systems introduce layered complexity, including currency conversion and settlement delays, regulatory fragmentation across regions, unreliable third-party integrations, and security risks in financial workflows.

Many startups build systems that scale functionally but not operationally. Without proper architectural controls, they often encounter duplicate or failed transactions, lack visibility into system state, and face high operational overhead for reconciliation.

To operate effectively in a global digital economy, systems must be designed with idempotent financial operations, state-driven workflow management, secure authentication and role-based access control, as well as reliable integration layers with proper failure handling.

Tell us more about Respectmart — what exactly are you solving?
Respectmart is a cloud-based, multi-tenant SaaS platform designed to unify logistics operations and financial workflows into a single system.

We are addressing three core challenges: cross-border payment friction, currency limitations, particularly NGN to USD constraints and fragmented logistics infrastructure.

From an architectural perspective, I designed the system to support domain-based multi-tenant isolation, handle high-volume transactional workflows, and maintain auditability across both logistics and financial processes.

The platform includes shipment lifecycle management from booking to reconciliation, integrated payment workflows with real-time tracking, and inventory and pricing engines based on dimensional weight. This ensures that both logistics and financial operations function within a consistent and observable system state.

That sounds interesting — what are some of the key innovations like the virtual debit card and automated shipment system?
One of the key innovations is the virtual USD debit card system, designed to address currency spending limitations for African users.

From a technical perspective, this required secure API integrations with financial providers, transaction validation and authorisation pipelines, enforcement of idempotency to prevent duplicate charges, and multi-factor authentication with role-based access control.

On the logistics side, I led the development of an automated SaaS shipment system supporting air cargo, ocean freight, and container shipping, with real-time tracking through event-driven updates and dynamic pricing models based on shipment attributes.

To ensure system reliability, I implemented state-driven workflows for shipment and payment entities, asynchronous queue-based processing to decouple external dependencies, and retry mechanisms with exponential backoff.

The system was built using PHP (Laravel), Go, and Python, allowing us to balance rapid development with performance-critical services.

You’ve mentioned deterministic systems—what does that mean in practice?
In practice, a deterministic system ensures that given the same input and system state, the outcome is always consistent.

In fintech systems, this is critical because requests may be retried multiple times, external systems may fail or respond inconsistently, and network conditions are unpredictable.

To achieve this, I design systems around idempotent operations to prevent duplicate execution, state machines to enforce only valid transitions, and immutable logs to capture every state change.

For example, instead of executing a payment request directly, the system first validates the current state of the transaction, checks whether the transition is allowed, and confirms whether the request has already been processed. Only then is the operation executed, ensuring consistency and auditability.

What leadership principles have guided you through this journey?
I focus on three principles. First, technical clarity over complexity—systems should be understandable and maintainable, not just functional.

Second, architecture is a shared responsibility. I mentor engineers on system design principles, ensuring the team understands decisions around state management, APIs, and security.

Third, impact-driven engineering. I measure success through outcomes, such as reducing unauthorised access by 50% and increasing system throughput by 30%, while maintaining reliability.

I also prioritise documentation and knowledge sharing to ensure long-term scalability.

What’s next for you and Respectmart?
We are scaling Respectmart across more African and international markets, with a focus on improving reliability and expanding financial capabilities.

From a technical perspective, I am exploring blockchain-based approaches to enhance transparency and fraud resistance, building on my MSc in Fintech at Teesside University, where I researched secure and verifiable transaction systems.

As CTO, my focus is on strengthening system architecture for global scale, building a high-performing engineering team, and introducing automation in compliance and transaction monitoring.

Our goal is to create infrastructure that allows startups and SMBs to operate globally without friction.