## Issue #93: Build Daily Revenue Email/Webhook Report

[orunganiekan]

Category: Backend / Scripts
Complexity: High
Points: 200
Branch: feat/daily-revenue-webhook

Background

daily-revenue-summary.ts computes revenue but only outputs to console. Merchant operators want daily revenue reports delivered automatically to their preferred notification channel (email, Slack, Discord, or generic webhook).

Problem

Daily revenue reports are only available by manually running a script. There is no automated delivery mechanism to push reports to merchant notification channels.

Acceptance Criteria

• scripts/daily-revenue-summary.ts is extended to support --webhook <url> flag
• Webhook payload: { date, total_volume_xlm, total_charges, unique_merchants, new_subscribers, cancellations, fee_collected_xlm }
• Slack formatting: payload is formatted as a Slack Block Kit message when SLACK_WEBHOOK_URL is set
• Report caching: if a report for today's date already exists in data/reports/, skip re-computation and re-delivery (unless --force)
• Error handling: failed webhook delivery is logged with full response body; script exits 0 (report computed successfully even if delivery failed)

Implementation Guidelines

Key files: scripts/daily-revenue-summary.ts
Approach: After computing the report, check if a cached file exists for today. If not, compute, cache to data/reports/YYYY-MM-DD.json. Format for Slack or generic JSON. POST to webhook URL.
Edge cases: Webhook URL not set (skip delivery, still output to console); partial day run (report for today may be incomplete — note in payload as partial: true); date in different timezone (use UTC consistently).
Validation: Run script with a test Slack webhook, verify message format and delivery

PR Requirements

• TypeScript with strict types
• Error handling and graceful failure
• README or inline JSDoc for usage
• Configuration via environment variables

[Inspector222]

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

Hi! I can complete this task efficiently while ensuring a high-quality implementation. I'd be glad to take ownership of it.

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

[Yinklekay]

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

I would love to work on this issue

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

[Windowlight]

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

Hi, I'm interested in this issue and have experience with contracts, backend systems, and frontend implementation.
I've reviewed the issue requirements and my plan is to:
• Understand the existing implementation.
Implement the requested changes.
•Add tests where applicable.
•Submit a clean, well-documented PR.
I can start immediately and will provide regular progress updates as I work through the task.
Thanks for considering my application.

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

[drips-wave]

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

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