"Fund Invoice" and "Mark Goods Shipped" skip the confirmation step used by sibling actions in the same component

[K1NGD4VID]

Category: UX Refinement

Repository location: apps/web/components/invoice/InvoiceCard.tsx (lines ~319-359)

Problem
fundInvoice/shipInvoice are invoked directly via handleAction, while confirmDelivery/repayInvoice/defaultInvoice in the same file go through requestConfirmation. Funding an invoice deploys pool USDC on-chain and marking as shipped changes escrow state — both are irreversible, but neither gets a "review before you sign" step, unlike their siblings in the same component.

Evidence
InvoiceCard.tsx: fundInvoice/shipInvoice call handleAction directly; confirmDelivery/repayInvoice/defaultInvoice call requestConfirmation first.

Suggested implementation
Wrap the fundInvoice/shipInvoice calls in requestConfirmation, mirroring the pattern already used for the other three actions.

Acceptance criteria

• Clicking "Fund Invoice" or "Mark Goods Shipped" shows the same confirmation dialog pattern as the other invoice actions.
• Existing tests for the other confirmed actions are extended to cover these two.

Difficulty: Easy

Expected impact: Closes the same class of accidental-irreversible-action risk as the detail-page issue, for a different entry point.

---

Filed as part of the second repository-wide audit (deeper refinements following the first cleanup pass).

[pimaster900]

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

Grant me this job and you are 💯 percent guarantee with me,just give me a try

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

[omoakinD]

@dammy03-dtv has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I'd love to take this on! As a Stellar/Rust dev, I know how critical it is to prevent accidental on-chain transactions like funding or escrow state changes. I'll update apps/web/components/invoice/InvoiceCard.tsx to wrap fundInvoice and shipInvoice in requestConfirmation, bringing them in line with sibling actions. I will also extend the existing unit tests to cover both confirmation flows. Let me know if I can get assigned to open a PR!

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

[luciusverus-cyber]

@luciusverus-cyber has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

HELLO ORG MAINTAINER CAN I WORK ON THIS

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

[drips-wave]

Congratulations, @luciusverus-cyber! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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