#081: Payroll Scheduler Backend Wiring

[Wilfred007]

#81: Payroll Scheduler Backend Wiring

Category: [FRONTEND]
Difficulty: ● HARD
Tags: scheduler, backend, cron, api, wizard

Description

Connect PayrollScheduler.tsx (and SchedulingWizard.tsx) to the backend scheduling API so that scheduled payroll configs are persisted in the database and the backend cron job triggers on-chain bulk payments at the configured time. The frontend should reflect the next scheduled run and allow real-time cancellation of pending schedules.

Acceptance Criteria

• Save Schedule submits to POST /api/schedules and persists config.
• Active schedules listed with next-run timestamp from backend.
• Cancellation calls DELETE /api/schedules/:id and updates UI immediately.
• CountdownTimer driven by the server-returned next_run_at timestamp.
• Backend job executes bulk_payment contract invocation at the scheduled time.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Lakes41]

@Lakes41 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello maintainer,

I am interested in working on this task. To connect the PayrollScheduler and SchedulingWizard to the backend API, I will implement the integration with the POST /api/schedules endpoint to persist payroll configurations and ensure the UI reflects the next_run_at timestamp provided by the server.

My approach involves setting up the API service layer for schedule management (including DELETE for real-time cancellations), binding the CountdownTimer component to server-side data for accuracy, and verifying that the backend cron job correctly triggers the bulk_payment contract on-chain at the designated time.

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

[meshackyaro]

@meshackyaro has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I'll like to work on this. I am a backend/smart contract developer and I am familiar with the codebase

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

[drips-wave]

Congratulations, @meshackyaro! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @meshackyaro: 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 issued 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 @meshackyaro as part of the Stellar Wave Program's 2nd Wave 🥳

😎 @meshackyaro: You earned 200 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.