Payment Reminder Escalation Flow

[Kingsman-99]

Description

Creators currently have no structured follow-up strategy for overdue invoices beyond manually resending the invoice link. This issue implements a configurable reminder escalation flow where creators define a sequence of reminder actions (email notification, activity feed alert, on-chain memo notification) at intervals after the due date, and the system automatically executes each step. The escalation state is visible on the invoice page and can be paused or cancelled by the creator.

Technical Context

Create components/invoice/EscalationFlowBuilder.tsx on the invoice detail page allowing creators to add escalation steps with { delayDays, channels: ('email'|'feed'|'memo')[], message }. Persist the escalation config in the invoice record via PATCH /api/invoices/[id]. Implement app/api/cron/escalation/route.ts as a Next.js Cron Route (or Vercel Cron) that runs daily, queries overdue invoices with active escalation flows, computes which steps are due, and dispatches them. Email dispatch uses nodemailer or Resend SDK. On-chain memo notifications use a zero-amount Stellar transaction with memo text to the payer's address. Track each dispatched step in an EscalationLog table. Surface escalation status on app/invoice/[id]/page.tsx as a timeline showing past and upcoming steps.

Acceptance Criteria

• Adding an escalation flow with at least two steps and saving the invoice persists the escalation config in the database and displays the timeline on the invoice page
• The cron route dispatches the correct escalation step on the correct day after the due date (verified via a mock date injection in tests)
• Pausing escalation halts all future step dispatches; resuming re-calculates the next due step based on the current date
• Email escalation steps send an email to the payer address (if on file) with the creator's custom message and a link to the public invoice page
• Each dispatched escalation step is logged in EscalationLog with status (success/failure), channel, timestamp, and any error message
• All CI checks (npm test, npm run build, ESLint/TypeScript) pass and the branch has no merge conflicts

---

[jessiE-bliz445]

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

Hello 👋, I would like to contribute to this project by

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

[chukwudiikeh]

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

Hi I would like to work on this issue.

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

[drips-wave]

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

🧑‍💻 @chukwudiikeh: 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 @chukwudiikeh as part of the Stellar Wave Program's 7th Wave 🥳

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