[SEP-12] Support Customer Deletion Requests

[Ceejaytech25]

📋 Issue #617: [SEP-12] Support Customer Deletion Requests

💡 Description & Objective

This issue tracking item focuses on addressing [SEP-12] Support Customer Deletion Requests within the backend-sep12 component scope. Contributors should follow the detailed guidelines below to implement, document, and test the solution correctly.

---

🛠️ Step-by-Step Implementation Guide

To solve this issue, please proceed as follows:

• Create DELETE customer routing path clearing stored metadata.
• Ensure formatting rules are respected before pushing.

---

🧪 Local Validation

Validate your changes locally by running:

npm run test:backend

---

🤝 Contribution Guidelines

🌿 1. Branch Naming Rules

Create a new branch from main using the following exact format:

feature/issue-617-sep-12-support-customer-deletion-re

💬 2. Commit Message Standard

Use Conventional Commits format when creating commits. Your final commit (or PR squash commit) must include:

feat(backend-sep12): [sep-12] support customer deletion requests (closes #617)

Example: feat(backend-sep12): [sep-12] support customer deletion requests closes #617

🚀 3. Pull Request Details

• Ensure all tests pass locally.
• Do not commit local SQLite files or lock files.
• Submit your branch for peer review.

[TochukwuJustice]

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

Hi, I would like to contribute to this issue. I’m a smart contract and backend dev working mostly with Solidity, TypeScript, and secure EVM setups. My focus is always on writing clean, gas-optimized, production-ready code without adding unnecessary clutter. I'll dive straight into fixing just this specific issue, document everything clearly, and make sure not to touch or disrupt anyone else's work.

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

[GideonBature]

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

I want to work on this issue. Please assign me.

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

[drips-wave]

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

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