[BE-92] Asset transfers with an approval workflow

[yusuftomilola]

Overview

The frontend has a full transfers API layer (frontend/lib/query/queries/transfers.ts) including approve and reject actions, and a multisig_transfer Soroban contract exists — transfers with approval are a core workflow.

API contract: the frontend already calls these endpoints — see frontend/lib/api/ and frontend/lib/query/keys.ts. Match the paths exactly so the existing UI works without changes.

GET  /transfers                    list with filters
POST /transfers                    request a transfer
GET  /transfers/${id}
POST /transfers/${id}/approve
POST /transfers/${id}/reject
POST /assets/${id}/transfer         initiate from an asset

Tasks

• Create the Transfer entity: assetId, fromDepartmentId/toDepartmentId, fromLocationId/toLocationId, fromUserId/toUserId, requestedByUserId, approverUserId, status (PENDING/APPROVED/REJECTED/CANCELLED/COMPLETED), reason, decisionNote, requestedAt, decidedAt.
• Build the endpoints above with a pending-approvals inbox view.
• Enforce that the requester cannot approve their own transfer.
• On approval, atomically update the asset's department/location/assignee and write a history entry.
• Move the asset to IN_TRANSIT while pending, if that suits the workflow — document the choice.
• Prevent concurrent conflicting transfers for one asset.
• Notify the approver on request and the requester on decision.
• Generate a migration and write tests covering every state transition.

Acceptance Criteria

• A transfer request, approval, and asset relocation work end to end.
• Self-approval is refused.
• Two simultaneous transfers of one asset cannot both complete.

Dependencies

Blocked by [BE-86], [BE-87], [BE-88].

Notes for Contributors

The backend is being rebuilt from a clean NestJS skeleton — backend/src/ currently contains only app.module.ts, app.controller.ts, app.service.ts, and main.ts. Follow standard NestJS module structure (module / controller / service / dto / entities) and register your module in app.module.ts. Comment below to be assigned.

[abdulrcrtw]

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

Hello, I'd like to pick this issue up.

I'm a full-stack developer with solid experience in modern JavaScript/TypeScript, REST APIs, and frontend frameworks like React. I enjoy working in open source and following existing project conventions.

I've reviewed the issue and I'm confident I can implement a solid solution while following the project's conventions.

Looking forward to contributing — please assign this issue to me.

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@abdulrcrtw's PR #1243 was approved and merged by @yusuftomilola.

🏆 @abdulrcrtw: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (481 total points). Track your full progress on GrantFox.

👏 Great work, @abdulrcrtw! Keep contributing to DistinctCodes.

[drips-wave]

This issue has been completed by @abdulrcrtw as part of the Stellar Wave Program's 7th Wave 🥳

😎 @abdulrcrtw: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.