fix(api-gateway):resolve type assertion errors in settlement status t…

[KCEE0901]

Please include a clear, concise summary of the changes introduced by this pull request. Explain the rationale behind the solution, any design trade-offs made, and context on how the changes achieve the goal.

Fixes / Closes: #24

---

Type of Change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that would cause existing functionality to not work as expected)
• Refactoring / Performance (clean-up or performance optimization without behavioral changes)
• Documentation / CI (changes to docs, workflows, config files)

---

Verification & Test Plan

Please outline how you verified these changes. Include steps to reproduce, test scripts, or command logs where applicable.

Automated Tests

For example: cargo test in contract package, pnpm test in backend.

# Provide the commands run to test the code

Manual Verification

---

Sub-System Checklist

1. Smart Contracts (BettaPay-Contract)

• Code compiles without warnings (cargo build --release --target wasm32-unknown-unknown)
• Cargo test suite passes locally (cargo test)
• Emits events for state changes
• Implemented proper authorization controls (auth.require_auth())

2. Backend Services (BettaPay-Backend)

• Prisma models updated and migrated (if database schema changes)
• Zod validation checks added/updated
• API routes and services build successfully (pnpm build)
• Local env variables updated in .env.example

3. Frontend Dashboard (BettaPay-Frontend)

• Local build completes successfully (pnpm build)
• Focus states, labels, and aria attributes tested for accessibility
• No regression on styling or components
• Env parameters documented in .env.local

---

Checklist

• My code follows the style guidelines of this project (run formatters/linters)
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[drips-wave]

@KCEE0901 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[therealjhay]

Kindly resolve conflict