Automated Bill Payment Scheduling

[Nathydre]

Description: Implement recurring payment functionality with automated scheduling for regular utility bills.

Technical Details:

• Create cron-based job scheduler
• Implement payment retry logic with exponential backoff
• Add user notification system for scheduled payments
• Create payment history and failure tracking
• Implement wallet balance checking before scheduled payments

Impact: Improves user convenience, reduces late payments

[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

[Georgebingi]

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

Hi my name is George and I'm a full stack develop I'll like to work on this issue because It picks my interest and Ive got experience with similar projects I'll have it solved in 24 hours or less

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

[drips-wave]

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

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

[dijangh904]

@dijangh904 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

i would love to work on this issue

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

[drips-wave]

Congratulations, @dijangh904! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

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

[Sammyowase]

@Sammyowase has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I’d like to work on this issue because it aligns closely with my backend experience, especially in building systems that require scheduling, reliability, and transaction safety.

I have experience working with Node.js and Express, Nestjs, and I’ve built systems using Redis-backed queues with Bull/BullMQ for background job processing, as well as cron-based schedulers for recurring tasks. I’m also comfortable working with SQL databases using Prisma for schema design, transactions, and data integrity.

For this task, I understand the need to design a robust recurring payment system that leverages cron jobs for scheduling and BullMQ for handling queued payment execution, retries, and exponential backoff. Using Redis will ensure reliable job management, while Prisma with a SQL database will handle payment records, wallet balances, and failure tracking with strong consistency.

I’m also experienced in implementing event-driven patterns (e.g., MQTT or similar messaging systems) for notifications, which can be used to inform users of successful payments, failures, or retries. I would structure the system by separating scheduling, payment processing, retry logic, and notification services to ensure maintainability and scalability.

I can deliver a clean, well-tested, and production-ready implementation within a reasonable timeframe, with proper handling of edge cases like insufficient balance, duplicate executions, and failure recovery.

Looking forward to contributing.

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

[Phantomcall]

@Phantomcall has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I would implement automated bill payment scheduling by creating a cron-based job system that queues and executes recurring payments at defined intervals, with pre-checks for wallet balance before processing. Failed payments should trigger a retry mechanism using exponential backoff, while all attempts (success or failure) are logged in a payment history for traceability. Additionally, I’d integrate a notification system to alert users before execution, on success, and on failure, ensuring transparency and a smooth, reliable user experience.

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