Per-Invoice Recipient Split History Panel

[Kingsman-99]

Description

Users reviewing a single invoice cannot see how each recipient's payment obligation was fulfilled over time—whether by a lump sum or multiple partial payments—because no per-recipient timeline exists within the invoice view. A collapsible history panel for each recipient row on the detail page should surface this data.

Technical Context

src/components/invoice/RecipientRow.tsx adds a chevron toggle that expands an inline src/components/invoice/RecipientPaymentHistory.tsx (new) panel. The panel fetches from src/app/api/invoices/[id]/recipients/[recipientId]/history/route.ts (new), which queries Horizon for payment and path_payment operations filtered to the recipient's address and the invoice's escrow account. Each history entry shows the operation hash, amount, and timestamp using RelativeTime (Issue 52) and TxHash (Issue 30).

Acceptance Criteria

• Each recipient row on src/app/invoice/[id]/page.tsx has a chevron that expands a payment history panel
• The expanded panel lists all on-chain payment operations from the escrow to the recipient with amount and timestamp
• The history is fetched lazily on first expand and cached for the page session
• Each history entry shows a truncated transaction hash with copy button using the TxHash component
• An empty history panel shows "No payments recorded yet" instead of a blank space
• All CI checks (npm test, npm run build, ESLint/TypeScript) pass and the branch has no merge conflicts

[Theophilus131]

I'd like to work on this issue. It combines blockchain integration, API development, and frontend UX in a meaningful way. I'll implement the lazy-loaded recipient payment history panel, add the new API route to retrieve on-chain payment history from Horizon, ensure the results are cached for the page session, and integrate the existing RelativeTime and TxHash components for a consistent user experience. I'll also cover the empty state and make sure the implementation passes all existing tests and CI checks.

[OmniZlatoon]

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

What can I do for you to assign me this issue sir? I assure you completion of the issue on time with expected output.

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

[directorfloo]

@directorfloo 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 expertly, please assign it to me

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

[Abba073]

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

assign this to me it will be done now

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

[ahmadrabiumustapha]

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

I would like to work on this issue because I can work on it

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

[drips-wave]

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

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