[SPIKE] [ADMIN] Payment Reports

#### Description:
As part of MVP, we will need to be able to provide financial breakdowns through reports.

#### Acceptance Criteria:

🧱 Data Model Review:

- [ ] Assess whether the current data model supports all required fields.
- [ ] Create a ticket to Expand the data model if necessary, particularly around payment capture.

🛠️ Backend Development:

- [ ] create a ticket for API endpoints
- [ ] create a ticket to Implement backend logic to transform transaction data into report-ready formats.
- [ ] create tickets to Generate reports in spreadsheet format (e.g., CSV, Excel) as needed; Validate recreated reports with stakeholders to ensure accuracy and usability. Iterate based on feedback.

#### Development Checklist:

- [ ] ...
- [ ] ...
- [ ] ...

#### Dependencies:

- Blocked by Rizzies ticket > https://bcparksdigital.atlassian.net/browse/RS-1794?atlOrigin=eyJpIjoiZDljY2IxNzI3MWQyNDRhZmE2ZTU2MWNkZDRiMmM0ZjYiLCJwIjoiaiJ9 (DONE)
- Blocking

#### Relevant documentation as reference:

- Financial reporting needs> https://bcgov.sharepoint.com/:x:/r/teams/01963-DiscoverCampingTeamChannel/Shared%20Documents/Discover%20Camping%20Team%20Channel/Financial%20Reports%20-%20MVP.xlsx?d=wa11fa02cb24d4b59b8f3ca5aa87244f7&csf=1&web=1&e=Kg6AOY

#### Notes:
- Rizzies to provide a list of what is needed for MVP and breakdown of fields.
-

**Definition of Ready**

- [ ] Acceptance criteria are included
- [ ] Wireframes are included (if applicable)
- [ ] Design / Solution is accepted by Product Owner (if applicable)
- [ ] Dependencies are identified (technical, business, regulatory/policy)
- [ ] Story has been estimated (under 13 pts)

**Definition of Done**
- In progress:
- [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- [ ] UI meets accessibility requirements
- [ ] Unit tests are written
- [ ] Work is traceable in GitHub
- [ ] PR linked to ticket number
- [ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment

- Code review:
- [ ] Code is peer reviewed and has passed CI/CD tests

- QA:
- [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- [ ] Code is potentially shippable to the production environment
- [ ] Functional features have been tested and passed by QA
- [ ] UI components tested by designer
- [ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)

- PO Review:
- [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- [ ] Reviewed and approved by Product Owner

Start with the completed Rizzies ticket and the linked Financial Reports - MVP.xlsx reference to identify the required fields and report formats. Confirm the MVP scope with stakeholders, then break the data-model, API, transformation, and report-generation work into separate tickets. Done means the scope and follow-up tickets are agreed and documented.

Written by the indexing model from the issue text.