[Bug] mobilePayments.ts bare catch block does not narrow error type before property access

[RUKAYAT-CODER]

Overview

mobilePayments.ts catches errors with catch (error: unknown) but immediately accesses properties like error.message without first checking if error is an Error instance. This causes a secondary TypeError at runtime.

Specifications

Features:

• Add a type narrowing function toError(caught: unknown): Error that wraps non-Error values
• Use it consistently in all catch blocks across mobilePayments.ts

Tasks:

• Implement toError utility
• Apply it in all catch blocks in the file
• Run TypeScript strict mode to find remaining unsafe accesses

Impacted Files:

• src/services/mobilePayments.ts
• src/utils/toError.ts (new)

Acceptance Criteria

• No unchecked error.message access in catch blocks
• toError utility is exported and reusable across the codebase
• TypeScript strict mode emits no errors in this file

[JClark011]

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

Hi maintainer Let me work on this issue
I'll definitely give you quick response

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

[Oluwasuyi-Oluwatimilehin-Daniel]

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

Hey Maintainer, I have gone through the details of the issue and i am capable of resolving it, I would love to be assigned to work on it ASAP.please assign me!!
ETA: 4 hours

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oluwasuyi-Oluwatimilehin-Daniel to this issue.

[michaelsimeon001]

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

Hi, I'd like to work on this issue.

I'm a software engineer with strong experience in JavaScript and building scalable web applications. I'm comfortable working across the stack, writing clean, maintainable code, and collaborating in open source environments.

I've reviewed the issue and I'm confident I can implement a solid solution while following the project's conventions.

Please assign this issue to me, I'd be happy to contribute.

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

[drips-wave]

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

🧑‍💻 @michaelsimeon001: 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 completed by @michaelsimeon001 as part of the Stellar Wave Program's 7th Wave 🥳

😎 @michaelsimeon001: 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. You can also Leave a review to share your experience working on this issue.

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