Implemented Payment History Table

[Tanya-garg10]

🎯 Transaction History Table Added

Payment Page Update:

• Scan to Pay QR code
• Payment Breakdown

Features:

• Columns: Date | Amount | Payment Method | Status
• Color-coded Paid / Pending badges
• Mobile responsive & modern design
• Real-time updates for users & admins

How It Works:

• Admin marks payment → transaction auto-created
• Users/Admins view all transactions in table

✅ Clean, easy-to-read transaction history now available on Payment page.

Fix: #6

[vercel]

@Tanya-garg10 is attempting to deploy a commit to the Revon Team on Vercel.

A member of the Team first needs to authorize it.

[gitguardian]

⚠️ GitGuardian has uncovered 6 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
24024965	Triggered	Generic Password	4ff6ff2	services/mockApi.ts	View secret
24024968	Triggered	Generic Password	4ff6ff2	services/mockApi.ts	View secret
24024969	Triggered	Generic Password	4ff6ff2	services/mockApi.ts	View secret
24024970	Triggered	Username Password	4ff6ff2	services/mockApi.ts	View secret
24024971	Triggered	Generic Password	4ff6ff2	services/mockApi.ts	View secret
24024972	Triggered	Generic Password	4ff6ff2	services/mockApi.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}