Payments view implements client-side sort instead of server-side

[usmanimamu17-create]

The payments view (src/components/payments/payments-view.tsx) fetches paginated data from the backend but implements sorting client-side via toggleSort and sortedItems useMemo. This means only the current page's items are sorted, not the entire dataset. Users viewing paginated payments will see incorrect sort orders when the dataset spans multiple pages.

Root cause: Lines 113-125 in src/components/payments/payments-view.tsx - Client-side sort only sorts current page.

Why this is architecturally hard

1. Backend API supports server-side sorting but frontend service layer doesn't expose sort parameters
2. Changing to server-side sort requires updating API call, service interface, and component state
3. Current UI uses loading state only triggered on filter changes, not sort changes

Acceptance criteria

• Sorting payments by Amount, Date, or Status sorts the entire dataset
• Sort parameters passed to backend API
• Loading indicator appears while sorted data is fetched

Getting started

Files: src/components/payments/payments-view.tsx, src/services/paymentService.ts

[beulah7717108-eng]

Hello Maintainer
please assign me this issue to fix i have review the acceptance criteria and am confident of submitting a pr for review

[grantfox-oss]

🦊 GrantFox — @beulah7717108-eng has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #265)
2. Your PR will be reviewed by the ApexChainx maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@beulah7717108-eng's PR #280 was approved and merged by @usmanimamu17-create.

🏆 @beulah7717108-eng: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (201 total points). Track your full progress on GrantFox.

👏 Great work, @beulah7717108-eng! Keep contributing to ApexChainx.