Recurring payment scheduling UI

[truthixify]

Tier: L (1-2 weeks) Type: feature

Context

Spectre supports scheduled payments. Demo currently doesn't expose this. Add a flow that lets users set up "send X to Y every interval" entries.

Scope

• New page /schedule listing active schedules
• Form to create: recipient, amount, asset, interval (daily/weekly/monthly), end date
• Display next-run-time per schedule
• Pause/resume/cancel actions
• Persistence: client-side (localStorage) for demo, with note that production would use Spectre

Acceptance criteria

• Page + form + list
• Mock execution logic with next-run timer
• Playwright test for create-pause-resume flow

Files to start with

• New: src/pages/Schedule.tsx

[DevSolex]

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

Hi Maintainer,

I’m a smart contract and full-stack developer and would love to contribute to this issue. I’m an experienced contributor with hands-on expertise in Rust, Soroban, Cairo, and TypeScript.

I’m passionate about building secure, scalable blockchain solutions, with a strong emphasis on writing clean and maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I’d greatly appreciate the opportunity to contribute and help move this forward.

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

[Lynndabel]

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

Hello, I have carefully reviewed this issue description and acceptance criteria and will like to work on this please. ETA is 6hours. Please assign me this, thanks

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

[Bokky73]

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

Hello sir, I would be so glad to work on this issues as I have a wonderful experience on problem solving.

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

[Emmy6654]

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

Please I Wiill Love to Work on this

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

[FELIX1090]

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

Hi maintainer i would like to work on this issue

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

[Meme11030]

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

Hi maintainer I will like to work on this issue

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

[Labi-Joy]

@Labi-Joy has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd like to work on this issue

Here's my plan:
I'll build the recurring payment scheduling UI end to end. This means a new /schedule page in src/pages/Schedule.tsx with a create form covering recipient, amount, asset, interval (daily/weekly/monthly), and optional end date. The list view will show all active schedules with calculated next-run times. Each entry gets pause, resume, and cancel controls. Persistence will use localStorage as scoped in the issue, with a clear inline comment noting the production path through Spectre.

For the mock execution logic, I'll implement a timer-based system that derives next-run timestamps from the interval and last-run time, updating the display in real time. The Playwright test will cover the full create-pause-resume flow as specified in the acceptance criteria.

I work with React and TypeScript daily and have built form-heavy scheduling interfaces before. I can deliver a clean, self-contained implementation within the week. Happy to clarify scope or align on any conventions before starting.

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

[drips-wave]

Congratulations, @Labi-Joy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Labi-Joy: 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 🌊

[truthixify]

@Labi-Joy Assigned. Welcome to wave 6.

Quick expectations:

1. Branch from develop (auto-default now).
2. Open a draft PR within ~3 days.
3. Update at least every 5 days; silence costs the assignment.
4. Acceptance criteria in the issue body are the merge bar.

Ask on the issue if anything is ambiguous before building.