Implement query validation and response schema for SEP-24 deposit and withdraw routes

[Cjay-Cyber-2]

Description

SEP-24 interactive deposit and withdrawal endpoints require strict query parameter verification to ensure anchor integrations receive fully compliant parameters (such as asset_code, account, memo, memo_type, and wallet_name). We need to solidify input schema validation and normalize response structures for SEP-24 routes.

Context & Requirements

Anchor deposit/withdraw flows are handled in src/routes/sep24.ts. Currently, some input parameters lack rigorous schema validation before processing, which can lead to unhandled errors when interacting with external SEP-24 anchor services.

Requirements:

• Define comprehensive Zod schemas for /deposit and /withdraw interactive endpoints adhering to the Stellar SEP-24 spec.
• Validate that asset_code matches supported Stellar assets configured in the backend.
• Enforce correct combination validation for memo and memo_type (e.g. memo_type must be one of text, id, hash if memo is supplied).
• Return standard structured JSON error responses (HTTP 400) for missing or invalid parameters.

Acceptance Criteria

• SEP-24 deposit and withdrawal endpoints validate query parameters against Zod spec schemas.
• Invalid asset_code or mismatched memo/memo_type combinations return descriptive HTTP 400 errors.
• Valid request parameters generate correct anchor interactive URL parameters.
• Unit tests cover parameter validation for valid and malformed requests.

Implementation Guidance

• Define schema validators in src/schemas/sep24.ts (or within src/routes/sep24.ts).
• Apply Fastify schema validation options directly to route declarations in src/routes/sep24.ts.
• Cross-check SEP-24 standard specification for field requirements and error codes.

Testing & Validation

• Add test cases in tests/routes/sep24.test.ts covering invalid assets, malformed memos, and missing mandatory parameters.
• Run integration tests with npm run test:integration or unit tests with npm test.

Submission Guidelines

• PR body must state "Closes #".
• Request assignment on the issue before starting implementation.
• Follow standard project naming conventions and code style.

---

Wave complexity: Medium

[samad13]

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

hi, let me work on this

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

[thelight08]

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

Assign me boss

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

[drips-wave]

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

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