Dashboard: Payout List with Status Tracking & Retry

[0xdevcollins]

Summary

Build the payout history list page with status tracking, filtering, and failed payout retry.

Requirements

• Paginated data table: Payout ID, Recipient, Amount, Currency, Destination Type, Status, Date
• Status badges: Pending (orange), Processing (blue), Completed (green), Failed (red), Cancelled (grey)
• Filters: status, destination type, date range, batch ID
• Search by recipient name or payout ID
• Expandable row detail: full destination info, Stellar tx hash (linked), failure reason
• Quick actions: Retry (failed only), Cancel (pending only)
• Batch view: group payouts by batch ID
• Export to CSV
• Empty state + skeleton loaders

Acceptance Criteria

• All payout statuses display correctly
• Failed payouts show reason and retry button
• Batch payouts grouped and viewable together
• Stellar tx hash links to explorer
• Export produces valid CSV

[Benedict315]

@Benedict315 has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hello I would like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Benedict315 to this issue.

[1sraeliteX]

@1sraeliteX has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I would like to work on the issue because building a robust payout history dashboard with proper status tracking, filtering, and retry mechanisms is critical for operational transparency and reliability in the payout system. I’ll implement a paginated data table showing payout metadata (ID, recipient, amount, currency, destination type, status, and date), along with status badges mapped to each payout state. I’ll also add advanced filtering (status, destination type, date range, batch ID), search functionality, expandable row details including Stellar transaction hashes and failure reasons, and batch grouping by batch ID. Additionally, I’ll implement retry and cancel actions with proper state validation, CSV export functionality, and UI states including skeleton loaders and empty states, along with comprehensive tests for UI behavior, filtering logic, and action flows.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @1sraeliteX to this issue.

[drips-wave]

Congratulations, @1sraeliteX! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @1sraeliteX: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @1sraeliteX as part of the Stellar Wave Program's 4th Wave 🥳

😎 @1sraeliteX: You earned 100 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.