Invoice Creator Revenue Share

[Kingsman-99]

Description

Platform fees accrue exclusively to the platform treasury, but invoice creators (e.g., freelancers or service providers deploying the dApp) have no on-chain mechanism to claim a portion of the collected total as their own service fee. A configurable creator_fee_bps field should allow the creator to declare a basis-point share deducted before recipient payouts, with a combined cap alongside the platform fee.

Technical Context

contracts/split/src/types.rs — add creator_fee_bps: u32 to the Invoice struct (valid range 0–10 000); contracts/split/src/lib.rs — release_funds() computes creator_fee = total_collected * creator_fee_bps / 10_000 using checked_mul/checked_div, transfers to invoice.creator, then distributes the remainder to recipients; contracts/split/src/validation.rs — at initialize(), assert creator_fee_bps + platform_fee_bps <= 10_000; contracts/split/src/events.rs — emit event::creator_fee_paid(invoice_id, creator, amount).

Acceptance Criteria

• Invoice stores creator_fee_bps and initialize() rejects values where creator_fee_bps + platform_fee_bps > 10_000 with Error::FeeSumExceedsCap
• release_funds() deducts the creator fee from gross collected funds before computing per-recipient shares
• The creator fee transfer occurs before any recipient transfer in every code path of release_funds()
• A creator_fee_paid event is emitted with invoice ID, creator address, and exact fee amount on every successful release
• Tests in contracts/split/src/tests/creator_fee_tests.rs cover zero fee, a representative non-zero fee, maximum combined fee, and over-cap rejection
• All CI checks (cargo build --target wasm32-unknown-unknown, cargo test, cargo clippy) pass and the branch has no merge conflicts

---

[khanavi272-spec]

@khanavi272-spec 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

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

[adeniran19-maker]

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

I'm a full-stack developer and I'd like to take this issue.
I understand the requirements and will follow the existing project structure, keep the implementation clean, and include proper tests where applicable.

ETA: 1–3 days (depending on scope)

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

[fairbid01]

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

I would like to work on the this before the end of the wave

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

[drips-wave]

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

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