Add unit tests for creator fee computation confirming correct bps application

[Chucks1093]

Summary

The creator fee is computed as a configurable bps percentage of the transaction value. Unit tests should verify the fee is computed correctly for several bps values and transaction amounts, and that the result always floors to a whole number of stroops.

Scope

• Test 500 bps (5%) on a 1000 stroop transaction → fee is 50
• Test 250 bps (2.5%) on a 1000 stroop transaction → fee is 25
• Test 100 bps (1%) on a 999 stroop transaction → fee floors to 9 (not 9.99)
• Test 0 bps → fee is always 0

Acceptance Criteria

• 500 bps on 1000 returns 50
• 250 bps on 1000 returns 25
• 100 bps on 999 floors to 9
• 0 bps always returns 0

ETA: 12 hours

---

Coordinate on Telegram

[MoscowDev]

I’d love to take this issue on. I’ve worked on production-ready applications and collaborated extensively through GitHub workflows. I’ll dig into the current setup, implement a solid and reliable fix, and deliver a well-tested PR. My focus is on clean, maintainable code and fast, dependable delivery.

[MoscowDev]

I’d love to take this issue on. I’ve worked on production-ready applications and collaborated extensively through GitHub workflows. I’ll dig into the current setup, implement a solid and reliable fix, and deliver a well-tested PR. My focus is on clean, maintainable code and fast, dependable delivery.

[ojuotimi932]

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

Hi Maintainer Can I resolve this kindly assign
ETA one hour

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

[Johnsmichael150]

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

I would love to work on this projects.

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

[Power70]

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

Hi Maintainer,
I can work on this issue.
Kindly assign it to me.
Thank you.

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

[Meemlahsabi]

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

Hi Maintainer, I’d be delighted to work on this issue. My approach will be to implement the requested functionality with clean architecture, maintainable code, and close attention to every detail outlined in the requirements. I’m ready to start immediately and would appreciate your consideration.

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

[drips-wave]

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

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