End user mobile experience
The mobile app handles onboarding, login, 2FA, biometric lock, wallet views, buy and sell flows, transfer, swap, receive by QR, activity, education, and support.
Back to selected work
Case study
AfriX is a multi-surface token exchange platform spanning mobile trading, agent operations, admin governance, and blockchain-connected transaction flows.
This project is notably different from a normal fintech landing page or wallet app. The codebase shows a coordinated system with a PostgreSQL API, a dedicated admin dashboard, and an Expo mobile experience built around mint, burn, transfer, swap, escrow, dispute, and compliance-heavy flows.
Visit live project
Category: Token exchange platform
Project snapshot
3
distinct product surfaces: backend, admin web, and mobile app
36
admin web app route files in the dashboard surface
80
mobile app route files in the Expo app layer
13+
versioned backend route groups mounted under `/api/v1`
What NEXGEN built
A fintech workflow system, not just an exchange interface.
Token exchange flows for buying, selling, sending, receiving, and swapping digital assets
Agent-led operational system for KYC, deposits, withdrawals, request handling, reviews, and performance tracking
Admin dashboard for users, agents, withdrawals, disputes, escrows, financial oversight, education, and security operations
Mobile-first user experience built in Expo/React Native with biometric lock, push notifications, QR-based receive flow, and Zustand-powered state
Blockchain and treasury tooling for testnet token deployment, mint workflows, balance checks, and transaction verification
Role-based product design
The platform is shaped around distinct users with different responsibilities.
AfriX has stronger operational complexity than a single-audience fintech app, because users, agents, merchants, and admins all interact with different parts of the system.
Agent operations
Agents are a first-class operating role with registration, KYC, deposit addresses, withdrawal requests, dashboard metrics, reviews, and handling responsibilities for mint and burn requests.
Merchant and payment layer
The backend includes merchants, payment requests, merchant payments, settlement-related logic, and merchant verification, which expands the platform beyond simple P2P exchange.
Admin and compliance layer
The admin dashboard spans user management, agent management, withdrawals, disputes, escrows, financial operations, education progress, and security management.
Architecture
Three coordinated apps with backend operations and blockchain support.
Backend API in Express with PostgreSQL/Sequelize, optional Redis, background jobs, structured services, and versioned route groups
Admin web dashboard in Next.js for operations, financial review, dispute handling, security workflows, and reporting
Expo mobile app with Expo Router, SecureStore, notifications, biometrics, QR code flows, and Zustand stores
Blockchain layer with Hardhat scripts, token contracts, treasury tooling, and verification helpers for testnet-oriented asset workflows
Technology stack
Node.js
Express 5
PostgreSQL
Sequelize
Redis
Socket.io
Next.js
React 19
Expo Router
React Native
Zustand
Tailwind CSS
Ethers
Hardhat
OpenZeppelin
What stands out
The most distinctive part of AfriX is the way transaction modes are modeled differently instead of being collapsed into one abstract wallet action. Mint, burn, transfer, and swap each have their own operational logic and risk model.
System breakdown
The core workflows reveal careful product thinking around trust and control.
Mint and burn lifecycle
AfriX models buying tokens as an agent-confirmed mint flow and selling tokens as an escrow-backed burn flow. That split creates a stronger transaction design than a vague one-step exchange button.
Escrow and dispute handling
Burn requests lock tokens in escrow first, then move through fiat proof, user confirmation, expiry, or dispute. Background jobs and admin controls reinforce the operational safety model.
Transfer and swap system
The platform also supports instant peer-to-peer transfers and in-app token swaps, giving users more than one transaction mode and making the wallet layer much more useful.
Education and terminology controls
The backend includes education routes, progress tracking, and terminology-safe language guidance. That suggests intentional product design around comprehension, trust, and regulatory sensitivity.
Repo evidence
Concrete codebase signals behind the case-study claims.
The repo is explicitly structured around `afriX_backend`, `afrix-web`, and `afriX-mobile`, showing a coordinated multi-surface product rather than one app with extra screens.
Lifecycle docs detail mint, burn, send, receive, and swap flows, including statuses, timeouts, escrow behavior, disputes, and which surface handles each step.
The backend mounts route groups for auth, agents, requests, wallets, transactions, merchants, payments, escrows, disputes, education, notifications, users, and admin.
The mobile app includes biometric security, push notification setup, transfer listeners, QR-based receive flows, and dedicated store slices for auth, wallet, mint, burn, swap, transfer, agent, and education.
Project readout
Why this project matters in the portfolio.
AfriX demonstrates NEXGEN working on a trust-sensitive financial product where state transitions, role permissions, operational visibility, and dispute handling all matter. That is a more demanding product challenge than standard payments UI alone.
It also broadens the portfolio narrative: NEXGEN is not only building commerce and ops systems, but also exchange-style transaction infrastructure with mobile delivery, admin oversight, and blockchain-aware implementation.