Implement Stellar Transaction Memo Verification and Parsing Utility

[Cjay-Cyber-2]

Description — what to implement and the why/impact.

Mergepay relies on structured Stellar transaction memos (MP:<code>) to automatically reconcile and verify on-chain settlements against pending expenses. This issue implements a robust utility for generating, formatting, and parsing memo strings safely according to Stellar memo limits and format specifications.

Context & Requirements — background, constraints, design references, edge cases; grounded in the actual repo (real files, stack, conventions).

Stellar transaction memos have strict character length limits (28 bytes for text memos). This utility must validate code lengths, sanitize input strings, and provide helper functions to extract expense references from incoming transaction payloads.

Acceptance Criteria — a checklist ("- [ ] ...") of specific, testable conditions that define "done".

• Implement memo generation and parsing functions in src/lib/.
• Enforce Stellar 28-byte text memo constraints with Zod validation or strict assertions.
• Add comprehensive unit tests covering edge cases, special characters, and length limits.
• Pass npm run typecheck, npm run lint, and npm test.

Implementation Guidance — likely files/modules to touch (use real paths from the repo context) and a suggested approach, without over-prescribing.

• Add tests in src/lib/__tests__/ alongside existing utility tests.
• Ensure compatibility with @stellar/stellar-sdk memo classes.

Testing & Validation — how the contributor should prove it works (tests to add/run, manual checks, screenshots for UI).

• Run npm test to verify all memo unit tests pass successfully.

Submission Guidelines — must open a PR that includes "Closes #"; assignment is required before starting; follow the repo's existing style and conventions.

---

Wave complexity: Medium

[Ranjeet2063]

Hi maintainers,

I would like to resolve this issue. Here is my proposed execution plan for Implement Stellar Transaction Memo Verification and Parsing Utility:

• Implementation: Deliver a clean, modular solution for Implement Stellar Transaction Memo Verification and Parsing Utility adhering strictly to mergepay/mergepay-web's architecture.
• Testing & Verification: Cover implementation with automated unit tests for edge cases and core workflows.
• Delivery: Ready to ship a thoroughly tested PR within 12–24 hours with passing CI.

I am ready to start immediately—please assign this to me!

[guptakumarranjeet150]

Hello @maintainers,

I would love to take this on. My planned approach:

• Deliver a clean, modular solution for Implement Stellar Transaction Memo Verification and Parsing Utility strictly following mergepay/mergepay-web conventions.
• Cover changes with automated tests ensuring CI passes smoothly.

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!

[shobhamerabacha-star]

Hey team,

I can tackle Implement Stellar Transaction Memo Verification and Parsing Utility. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in mergepay/mergepay-web
• Implementation: Deliver a clean, modular solution for Implement Stellar Transaction Memo Verification and Parsing Utility strictly following mergepay/mergepay-web conventions.
• Testing: Cover changes with automated tests ensuring CI passes smoothly.
• PR: Atomic commit with clean git hygiene and passing CI

Looking forward to contributing—please feel free to assign!