Build automated dunning management with configurable retry strategies

[Smartdevs17]

Context

Failed subscription payments need automated dunning with configurable retry strategies.

Current Limitation

Dunning is basic with no configurable retry logic.

Expected Outcome

• Configurable retry strategies per failure type
• Progressive dunning with escalation
• Dunning analytics and optimization
• Dunning template management

Acceptance Criteria

• Configurable retry strategies (insufficient funds, expired card, network)
• Progressive dunning (retry → notification → escalation)
• Dunning analytics (recovery rate, time to recovery)
• Dunning template management
• Dunning A/B testing
• Dunning reporting dashboard
• Dunning integration with payment providers

Technical Scope

• backend/services/billing/ - Billing domain
• contracts/subscription/src/ - Subscription contract
• src/store/subscriptionStore.ts - Subscription store
• backend/services/notification/ - Notification domain

[Essence-3]

@Essence-3 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi, I have a solution to this issue and I would love to work on it.

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

[AlphaMaleBaDI]

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

I am highly interested in implementing the automated dunning management system for SubTrackr. My background in building robust payment infrastructure aligns perfectly with the requirements of this issue, and I am eager to contribute to the Stellar Wave by developing flexible, configurable retry strategies that improve revenue recovery while maintaining a positive user experience.

Relevant Experience and Technical Approach:

• Backend Engineering: I have extensive experience building scalable payment workflows using Node.js and Go, specifically handling asynchronous job processing and state machine management for billing cycles.
• Retry Logic Implementation: I have previously architected exponential backoff strategies and jitter implementation for third-party API integrations, ensuring that rate limits are respected while maximizing successful collection rates.
• Configurability: I am familiar with designing JSON-based schema configurations that allow stakeholders to define custom dunning intervals and communication triggers without requiring hard-coded deployments.
• Observability: I prioritize building logging and alerting mechanisms into dunning flows, ensuring that failed payment events are captured, categorized, and easily retrievable for auditing purposes.

I am confident that I can deliver a reliable, modular solution that integrates seamlessly with the existing SubTrackr codebase. I am ready to begin immediately and look forward to the opportunity to contribute to this project.

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

[Kaizer4show]

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

Hello Maintainer, I'd love to take ownership of this issue and submit a high-quality pull request once completed.

I'll add configurable retry strategies per failure type (insufficient funds, expired card, network) in backend/services/billing/, progressive dunning with retry → notification → escalation via backend/services/notification/, dunning analytics (recovery rate, time to recovery), a reporting dashboard, template management, A/B testing, and payment-provider integration, wired against src/store/subscriptionStore.ts and contracts/subscription/src/.

Thank you.

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

[agenes01]

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

can i work on this

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

[drips-wave]

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

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