feat: add secure admin payment dashboard - #17
Conversation
|
@udaycodespace Do add bonus labels like good-backend , good-pr , good-ui |
Temporary labels have been assigned based on the PR description. Final labels will be assigned after the review. Also, since the PR includes an extensive testing checklist, please share the relevant testing evidence (terminal output/screenshots where applicable), such as:
This helps with validating the implementation during the review. Thanks! |
|
@udaycodespace Thanks for the review. I have completed the requested validation and added the relevant testing evidence below. Backend validation
Frontend production build
Admin authorization
Sanitized payment response
Filters and sortingVerified:
PaginationVerified page-size selection and Previous/Next navigation using multiple transaction records.
Summary metricsVerified that total transactions, status counts, and successful mock revenue shown in the frontend match the API summary response.
I have also included the frontend ss in the PR. |
lgtm! |
Merge PR #17 from Jidnyasa-P Add a secure admin payment dashboard with payment management features. Highlights: - Add admin payment records dashboard - Sanitize API responses to protect sensitive payment data - Add search, filtering, sorting, and pagination - Display payment summary metrics - Support responsive desktop and mobile layouts - Add accessible transaction details dialog - Protect endpoints with admin authentication and authorization - Add documentation for the payment records API - Include testing validation and build verification Closes #9.
|
@Jidnyasa-P I went through the code for PR #16, everything looked good, so I merged it. For PR #17, the latest changes from |
Done |




























Description
Adds a secure admin payment-records dashboard with sanitized transaction data, summary metrics, filtering, sorting, pagination, responsive layouts, and an accessible details dialog.
Fixes #9
Backend changes
Replaced the raw payment-document response with a strict sanitized DTO
Added search by:
Added payment-status filtering
Added start and end date filtering
Added newest and oldest sorting
Added amount sorting
Added validated pagination and page size
Added aggregate summary metrics
Corrected course population to use
C_titleandC_priceAdded compatibility for legacy
enrolledpayment statusesEscaped regex search input
Protected the endpoint using existing admin authentication and role middleware
Frontend changes
Added a Payments section to the admin dashboard
Added summary cards for:
Added responsive desktop and mobile transaction layouts
Added search and filter controls
Added date filtering
Added newest/oldest and amount sorting
Added configurable page size
Added pagination controls
Added loading skeletons
Added empty and retryable error states
Added an accessible transaction-detail dialog
Security
The API and frontend do not expose:
Only a masked card identifier may be returned.
Documentation
Added
docs/admin-payment-records.mdwith:Testing
Screenshots