Dashboard: Recipient Management

[0xdevcollins]

Summary

Build a recipient management system so merchants can save, edit, and reuse payout recipients.

Requirements

• New Prisma model: Recipient (name, destination type, destination details, merchantId)
• API endpoints:
  • POST /v1/recipients — Save recipient
  • GET /v1/recipients — List saved recipients
  • PATCH /v1/recipients/:id — Update recipient
  • DELETE /v1/recipients/:id — Remove recipient
• Dashboard UI:
  • Recipients list in Settings or Payouts section
  • Add/edit recipient form
  • Search/filter recipients
  • Select saved recipient when creating a payout (autocomplete)
• Validation per destination type

Acceptance Criteria

• Recipients CRUD fully functional
• Recipient selectable during payout creation
• Destination details validated per type
• Recipient list searchable and paginated

[theFirstCodeManiac]

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

I will like to work on this.

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

[codefather2026]

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

Hi maintainer, i will like to solve this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @codefather2026 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 recipient management system is essential for improving payout usability by allowing merchants to store, reuse, and manage payout destinations efficiently instead of re-entering details each time.

I will implement a new Prisma Recipient model capturing name, destination type, destination details, and merchantId, then build full CRUD API endpoints (POST, GET, PATCH, DELETE) with proper validation per destination type. On the frontend, I will add a recipients management section in Settings/Payouts with list view, pagination, search/filtering, and an add/edit form. I will also integrate recipient selection into the payout flow using autocomplete for saved recipients, ensuring a smooth and reusable payout experience, with tests covering API logic, validation rules, and UI interactions.

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

[drips-wave]

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

🧑‍💻 @theFirstCodeManiac: 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 @theFirstCodeManiac as part of the Stellar Wave Program's 6th Wave 🥳

😎 @theFirstCodeManiac: 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.