Case study
The monorepo shows a serious infrastructure product: SDK routing logic, provider adapters, a Prisma-backed API, merchant dashboards, developer docs, and sample integration surfaces. It is much more than a payment wrapper or dashboard skin over one gateway.
Project snapshot
10
workspace packages and apps spanning core SDK, provider adapters, dashboard, docs, marketing site, API, and sample commerce demo
4
payment providers supported across Paystack, Flutterwave, Monnify, and Korapay
46
API source files for auth, billing, analytics, webhooks, enterprise services, transaction storage, and merchant operations
2
operating modes beyond simple SDK usage: aggregator model and orchestrator model with managed or private execution
What NEXGEN built
Core payment-routing engine that registers provider adapters, scores provider health, and selects the best path based on routing strategy, cooldown windows, and retryability.
Unified API and merchant infrastructure for payment initialization, verification, analytics, billing, developer tooling, enterprise controls, and environment-aware authentication.
Webhook normalization layer that ingests disparate events from multiple providers, converts them into one internal schema, and forwards signed merchant webhooks with retry support.
Merchant dashboard for transactions, API key management, developer settings, billing, webhook history, and operational visibility across test and live environments.
Developer ecosystem surface that includes landing site, docs app, React package, sample e-commerce integration, and provider-specific packages for self-hosted orchestration flows.
Why it matters
PayUnify’s value comes from the combination of routing, observability, webhook normalization, and merchant tooling. The repo consistently frames resilience as the main product promise.
Built for Nigerian payment reality
The core framing in the repo is that provider failure is normal, not exceptional. PayUnify’s architecture assumes downtime, degraded success rates, and inconsistent gateway behavior, then routes around it instead of making merchants solve that complexity alone.
Product plus protocol thinking
This is not only a merchant dashboard. It combines a routing engine, a normalized payment API, provider adapters, merchant operations, auditability, and developer-facing integration surfaces into one coherent platform.
Flexible operating model
The platform supports both a managed SaaS-style aggregator path and orchestration models where enterprises keep their own provider relationships and keys. That makes the architecture much more adaptable than a one-mode gateway wrapper.
Developer experience is part of the product
The monorepo includes docs, React integration surfaces, a sample commerce app, and premium dashboard tooling because adoption depends on how quickly developers can test, understand, and trust the system.
Architecture
Technology stack
What stands out
The most distinctive part of PayUnify is that it supports different commercial models without changing its core identity: managed payment infrastructure for smaller merchants, and orchestration intelligence for larger teams that already own their provider relationships.
System breakdown
Routing and health engine
The core package contains the payment router, provider registry, health monitor, and validator layer. The docs describe weighted routing, cooldown windows, retry chains, and preview tooling so merchants can understand how the switch behaves under stress.
Merchant auth and key infrastructure
The API layer includes a dedicated key service, auth middleware, tier enforcement, and database-backed merchant context so the platform can support test/live isolation, API key rotation, and secure multi-tenant access patterns.
Webhook and audit operations
Webhook handling is treated as a product surface, not a footnote. The system normalizes provider callbacks, stores delivery records, retries failed deliveries with backoff, and exposes history and inspection views in the dashboard.
Merchant and developer surfaces
Dashboard routes cover transactions, developers, API keys, billing, settings, and webhook history, while the wider monorepo includes docs and a sample e-commerce app that demonstrates how PayUnify is meant to be embedded in real products.
Repo evidence