QRISGUE is an internal payment gateway platform I built to unify QRIS payments, payment links, merchant APIs, webhooks, ledger accounting, settlements, withdrawals, and finance operations. The architecture separates web, API, worker, and shared business packages so payment logic stays isolated and maintainable.
Problem
Bots, websites, and internal products needed one consistent QRIS payment flow. Scattered integrations made reconciliation, webhooks, merchant balances, auditing, and finance operations difficult to keep safe and predictable.
Solution
I built a full-stack monorepo with Next.js for the web app, NestJS for the API and worker, PostgreSQL/Prisma as the source of truth, and Redis/BullMQ for background jobs and reconciliation. The system uses RBAC, API keys, idempotency, an immutable ledger, signed webhooks, and separate TEST/LIVE environments.
Result
The result is a private-first payment gateway foundation with merchant/admin/finance dashboards, a REST API, developer documentation, audit logs, reconciliation tooling, and a TEST sandbox for bot and website integrations.