Backend: Implement Custom Webhook Event Filtering and Subscription Manager

[Smartdevs17]

Context

Merchants receive all webhook events for their account, forcing them to filter irrelevant events client-side, wasting bandwidth and processing.

Current Limitation/Problem

Webhook subscriptions are all-or-nothing. Merchants cannot subscribe to specific event types, filter by criteria, or route different events to different endpoints.

Expected Outcome

A granular webhook subscription system where merchants create multiple subscriptions with event type filters, condition expressions, and target endpoints.

Acceptance Criteria

• Create multiple webhook subscriptions per merchant
• Filter by event type, resource ID, amount range, chain, currency
• Condition expressions using JSONPath or simple DSL
• Route different event types to different endpoints
• Subscription testing with sample events before activation
• Delivery metrics per subscription (count, success rate, latency)
• Pause/resume individual subscriptions
• Subscription version history

Technical Scope

• Prisma: WebhookSubscription model with filter conditions
• backend/src/services/webhooks/subscription-manager.ts - subscription logic
• backend/src/services/webhooks/event-matcher.ts - filter evaluation
• Frontend: /dashboard/developers/webhooks/subscriptions - subscription management
• Edge cases: overlapping subscriptions, delivery deduplication, filter evaluation performance

[rahimatonize]

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

I maintainer, I would love to work on this issue, could you please assign me on it?

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

[somotochukwu-dev]

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

Good day maintainer
Please assign this issue to me,I would like to work on this issue.
Thanks.

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

[dimka90]

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

Can i work on this?

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @dimka90 as part of the Stellar Wave Program's 6th Wave 🥳

😎 @dimka90: 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.