[Bug] Fix transaction lookup by reference number returning incorrect records

[sublime247]

• Category: Bug
• Difficulty: Medium
• Labels: bug, database, lookup, medium

Description

This issue focuses on addressing: "[Bug] Fix transaction lookup by reference number returning incorrect records". This component requires enhancement to ensure system stability, security, and developer ergonomics across the Mobile Money ↔ Stellar Bridge.

Acceptance Criteria

• Implement/resolve changes associated with the Fix transaction lookup by reference number returning incorrect records.
• Ensure all existing and new unit tests compile and run successfully.
• Code must pass all lints, clippy checks, and formatting guidelines.

Tasks

• Review implementation requirements and trace dependency entry points.
• Apply code modifications matching the scoped task.
• Verify functionality locally using mock execution frameworks.

[GiftedGiftB]

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

Hi maintainer, i can get this work done in less than 24 hours.

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

[shaarknado]

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

I Would love to work on this task

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

[thelight08]

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

Please assigned me boss😭😭🤲

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

[onakijames-droid]

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

Hi Maintainer, I’d like to work on this issue.

I’ve reviewed the scope and I’m confident I can take this from investigation through implementation, testing, and documentation while keeping the changes focused and aligned with the repository’s existing conventions.

My approach would be to first understand the current implementation and identify the smallest clean solution that fully addresses the issue. I’ll then implement the changes incrementally, test the relevant behaviour and edge cases, and verify that I haven’t introduced regressions elsewhere.

I’ll also make sure the final PR is easy to review, with a clear description of what changed, why it changed, and how I validated it. Where appropriate, I’ll update tests and documentation alongside the implementation rather than leaving those for later.

I’m particularly interested in contributing a complete, maintainable solution rather than just making the issue technically “work.”

If assigned, I can start working on it immediately and will keep the implementation focused on the requirements described in the issue

ETA 3HRS

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

[dice-png]

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

⁠Hello Maintainer, I’ve reviewed the issue and understand the requirements. I can handle it effectively. Kindly assign it to me.

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

[muazumikail1915-create]

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

Hi maintainer.
I would like to take on this issue

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

[drips-wave]

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

🧑‍💻 @muazumikail1915-create: 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 marked as completed by a Drips Wave moderator for @muazumikail1915-create as part of the Stellar Wave Program's 8th Wave 🥳

Moderator's reason: [Auto-assessed] The PR was merged by maintainers (mergedAt 2026-08-31T06:03:39Z) and successfully addresses the transaction lookup issue as well as related items (#1783, #1784, #1785, #1786) with robust code modifications and corresponding unit tests.

😎 @muazumikail1915-create: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.