Fix SDK `cancelInvoice` sending extra `submitterAddress` argument

[Levi-Ojukwu]

Description:

The SDK's cancelInvoice method sends 2 arguments (submitterAddress, invoiceId) but the contract's cancel_invoice only accepts 1 user argument (invoice_id: u64). The freelancer/submitter is determined internally via require_submitter_by_id and should not be passed.

pub fn cancel_invoice(env: Env, invoice_id: u64)

// SDK at cancelInvoice.ts:60-64 — WRONG
const op = contract.call(
  "cancel_invoice",
  nativeToScVal(submitterAddress, { type: "address" }),  // EXTRA
  nativeToScVal(invoiceId, { type: "u64" })
);

Why it matters: Invoice cancellation is broken through the SDK. Freelancers cannot cancel pending invoices, and partially-funded invoices cannot trigger LP refunds.

Acceptance Criteria:

• Remove the submitterAddress argument from the contract call
• Pass only invoiceId as the argument
• Verify submitter authentication works via require_submitter_by_id
• Add tests for successful cancellation
• Add tests verifying partial funding refunds work correctly

Relevant Files: sdk/src/methods/cancelInvoice.ts:60-64, contracts/invoice_liquidity/src/lib.rs:1393

---

[kingbitnation]

Hi! I'd love to work on this issue. I have experience with the required technologies and can deliver a clean, well-tested solution. Looking forward to contributing!

[miracleokaa]

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

Please assign this issue to me, i've gone through the task description and can deliver quickly.

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

[drips-wave]

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

🧑‍💻 @miracleokaa: 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 removed from the Stellar Wave Program by the repository maintainers.

@miracleokaa, you have been unassigned from this issue. If you have any questions, please reach out to the repo maintainers.

[D-Lord-15]

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

Hello maintainer, i would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @D-Lord-15 to this issue.

[drips-wave]

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

🧑‍💻 @D-Lord-15: 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 🌊