Refactor: session-provider stores bigint balances as strings in localStorage — breaks JSON round-trip

[henrypeters]

Category: Frontend - Bug
Priority: High
Estimated Time: 1 hour

Description:
components/session-provider.tsx calls JSON.stringify(next) on the session object and JSON.parse(stored) as Session on load. The Session type only contains token, userId, and merchantId — all strings — so the round-trip is currently safe.

However, the broader pattern in lib/api.ts uses bigint for amount_stroops, available, and pending fields. If any future code attempts to persist Balance or Payment objects through the same JSON.stringify path, BigInt serialisation will throw TypeError: Do not know how to serialize a BigInt. The custom stringifyWithBigInts / parseWithBigInts pair in lib/api.ts must be used for any persistence of API response objects.

Tasks:

• Add an ESLint rule or TypeScript type guard preventing direct JSON.stringify calls on API response types containing bigint fields
• Add a comment in session-provider.tsx explaining why only Session (string-only) is safe to use with plain JSON.stringify
• Add a unit test asserting that JSON.stringify of a Balance object throws and that stringifyWithBigInts handles it correctly

[Michael997glitch]

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

I’ve resolved similar problems in the past and am confident I can implement a clean, efficient fix quickly,if am given the opportunity.

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

[pascalmary]

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

Please I will like to work on this. i have reviewed the issue scope.

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

[Zarmaijemimah]

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

Hi maintainer I’ll love to work on this issue please kindly assign thank you

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

[drips-wave]

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

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