Transfer confirmation code is sent to the initiator, not the intended new owner

[feyishola]

Both the "initiated" and "completed" notifications in certificate-transfer.service.ts:104-109,216-221 are created for initiatorId/approverId, and the initiation notification embeds the secret confirmationCode. The new owner (toEmail) is never notified and never receives the code, so the intended flow (new owner confirms with the code) is impossible — effectively the initiator both starts and approves the transfer. Fix: send the confirmation-code notification/email to toEmail, and notify the recipient on completion.

[Abulbayty]

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

I’ve gone through the acceptance criteria and fully understand the requirements. I’m confident I can resolve this issue and submit a high-quality PR within 24 hours.

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

[AdEmOnD07]

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

I will like to work on this issue

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

[johnbiliyaminu-bit]

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

I would love to work on this issue

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

[dDevAhmed]

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

I would like to work on this

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

[doncross03]

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

Hi Maintainer, I've carefully reviewed the issue and can implement a solution that meets the acceptance criteria. Please assign it to me.

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

[Beneaththesky001]

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

I’ve thoroughly reviewed the issue and have a clear understanding of the intended outcome. I’d like to take this on and deliver a well-integrated solution that meets the acceptance criteria while maintaining the quality and consistency of the existing project.

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

[drips-wave]

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

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