Implement a recurring remittance schedules management screen wired to /api/remittance/recurring

[Baskarayelu]

📋 Description

The backend already exposes recurring remittance schedules CRUD at app/api/remittance/recurring/route.ts (see backend issue Recurring Remittance Schedules (CRUD)), and there is mock data in lib/mockdata/recurringRemittances.ts, but there is no frontend screen to view, create, pause, or delete a schedule.

This issue builds the recurring schedules management UI.

Why this matters: families send money on a cadence (monthly support, school fees). A managed recurring schedule turns a one-off send into the product's stickiest retention feature.

🎯 Requirements & Context

Functional requirements

• Add a route (e.g. app/send/recurring/page.tsx or under dashboard) listing schedules from /api/remittance/recurring via apiClient.
• Support create (recipient, amount, currency, cadence, next date) using the recipient validation hook/pattern from RecipientAddressInput.
• Support pause/resume and delete with confirmation.
• Loading/empty/error states via LoadingSkeletons / WidgetEmptyState / WidgetErrorState.

Context & constraints

• Replace the use of lib/mockdata/recurringRemittances.ts with live data (keep mock for tests only).
• Validate cadence + future date.

🛠️ Suggested Execution

git checkout -b feat/recurring-remittance-screen

• Build list + create + pause/delete + states, add TSDoc.

npm run lint
npx tsc --noEmit
npm run test:coverage
npm run build
npm run test:e2e

• Edge cases: empty list, invalid recipient, past next-date, delete confirm cancel, API failure, reduced motion, mobile.
• a11y: confirmation dialogs keyboard-operable; list semantics.
• i18n: externalize cadence labels.

Example commit message

feat(recurring): add recurring remittance schedules management screen

Lists, creates, pauses, and deletes schedules via
/api/remittance/recurring with loading/empty/error states.

✅ Acceptance Criteria & Guidelines

Requirement	Target
List + create + pause/delete	Required
Live data (mock removed from prod path)	Required
Loading/empty/error states	Required
Recipient + cadence validation	Required
Accessibility + responsive + i18n	Required
Lint + typecheck + build clean	Required
Timeframe	96 hours from assignment

💬 Community & Support

Join the RemitWise contributor community on Discord: https://discord.gg/CtQuPZFMA

Comment to claim before starting. 🚀

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[jaynomyaro]

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

[T-kesh]

I'd like to take this on.

I've reviewed the existing requirements and understand the work involved: building the recurring remittance management UI, integrating with /api/remittance/recurring, replacing production mock usage, implementing create/pause/resume/delete flows, validation, loading/empty/error states, and ensuring accessibility and responsiveness.

I'll follow existing project patterns (including recipient validation), add appropriate documentation, and verify the implementation passes lint, typecheck, build, and test requirements before submission.

Looking forward to working on it.

[Senorespecial]

I would like to work on this issue please assign

[grantfox-oss]

🦊 GrantFox — @Senorespecial has been assigned to this issue!

Next steps:

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

Good luck! Track your progress on GrantFox.