Skip to content

Build Zambia mobile-money crypto ramp MVP - #1

Open
alphacoder1 wants to merge 1 commit into
mainfrom
cursor/zambia-crypto-ramp-mvp-5a49
Open

Build Zambia mobile-money crypto ramp MVP#1
alphacoder1 wants to merge 1 commit into
mainfrom
cursor/zambia-crypto-ramp-mvp-5a49

Conversation

@alphacoder1

Copy link
Copy Markdown
Owner

Summary

  • Scaffolded a production-shaped Next.js/TypeScript MVP for a Zambia-focused non-custodial crypto on/off-ramp.
  • Added mobile-first landing, buy, sell, transaction history, FAQ, support, and admin dashboard pages.
  • Implemented Prisma/PostgreSQL schema and initial migration for quotes, transactions, users, audit logs, webhooks, idempotency keys, and admin sessions.
  • Added typed API routes for quotes, buy/sell initiation, transaction tracking, sell deposit verification, mobile-money webhooks, admin auth, analytics, liquidity, and freeze/review actions.
  • Added swappable mobile-money provider abstraction with mock and generic HTTP providers for Lipila/Flutterwave/PayChangu/Pesapal-style integrations.
  • Added Wagmi/Viem MetaMask integration, hot-wallet helper, EVM token deposit verification, Redis-ready queue abstraction, Docker Compose, Dockerfile, Vercel config, env example, and architecture docs.

Verification

  • npm run typecheck
  • ADMIN_JWT_SECRET='local-admin-secret-change-me-32-bytes' MOBILE_MONEY_WEBHOOK_SECRET='local-webhook-secret' npm run build

Notes

  • MVP recommends USDC on Base, USDT on Polygon, and WBTC on Polygon. Native Bitcoin is modeled but disabled until dedicated Bitcoin address management and UTXO monitoring are added.
  • npm audit --omit=dev currently reports moderate findings in upstream Prisma/Next dependency trees; npm suggests force downgrades/breaking changes, so no forced remediation was applied.
Open in Web Open in Cursor 

Co-authored-by: Emmanuel Mangalashi <alphacoder1@users.noreply.github.com>
@alphacoder1
alphacoder1 marked this pull request as ready for review May 18, 2026 12:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants