Overview
Build an admin risk analytics dashboard that helps identify unusual repayment, wallet funding, contract, and fleet patterns.
Problem
As ChainMove grows, admins need a dashboard that highlights operational and financial risk signals before they become bigger issues. This should help admins review late repayments, repeated failed payments, unusual funding activity, inactive contracts, and underperforming vehicle pools.
Expected solution
Create a risk analytics dashboard with:
- late repayment summary
- repeated failed transaction summary
- inactive driver or contract indicators
- underperforming pool indicators
- repayment delay trends
- high-value wallet funding flags
- admin review status for flagged records
- filters by date, user role, status, and risk type
- risk detail drawer or detail page
Backend considerations
Add reusable aggregation helpers where needed. The risk rules should be clearly named and easy for maintainers to adjust later.
Files likely involved
- admin risk dashboard pages/components
- transaction models/API routes
- repayment/contract models
- dashboard aggregation helpers
- table/filter/detail components
Acceptance criteria
- Admin can view risk summary metrics.
- Admin can inspect flagged repayment and funding records.
- Risk rules are clear and reusable.
- Filters and detail views are implemented.
- Access is restricted to admins.
- Empty/loading/error states are handled.
npm run lint and npm run build pass.
Suggested labels
dashboard, admin, analytics, risk, backend, frontend, hard
Difficulty
Hard
Overview
Build an admin risk analytics dashboard that helps identify unusual repayment, wallet funding, contract, and fleet patterns.
Problem
As ChainMove grows, admins need a dashboard that highlights operational and financial risk signals before they become bigger issues. This should help admins review late repayments, repeated failed payments, unusual funding activity, inactive contracts, and underperforming vehicle pools.
Expected solution
Create a risk analytics dashboard with:
Backend considerations
Add reusable aggregation helpers where needed. The risk rules should be clearly named and easy for maintainers to adjust later.
Files likely involved
Acceptance criteria
npm run lintandnpm run buildpass.Suggested labels
dashboard,admin,analytics,risk,backend,frontend,hardDifficulty
Hard