Add docs for webhook event payload schemas for all supported event types

[Chucks1093]

Summary

Developers registering webhooks need to know the exact shape of each event payload to build their receivers. A reference document should describe every supported event type with a full example payload and field descriptions.

Scope

• List every supported webhook event type
• For each event type: event name, description of when it fires, full example JSON payload, and description of each field in the payload
• Include a note on the X-Accesslayer-Signature header format and how to verify it
• Document any fields that may be null or absent depending on the event context

Acceptance Criteria

• All supported event types documented
• Each entry includes event name, trigger description, example payload, and field descriptions
• Signature header verification documented
• Nullable/optional fields clearly marked

ETA: 12 hours

---

Coordinate on Telegram

[MoscowDev]

I’d love to take this issue on. I’ve worked on production-ready applications and collaborated extensively through GitHub workflows. I’ll dig into the current setup, implement a solid and reliable fix, and deliver a well-tested PR. My focus is on clean, maintainable code and fast, dependable delivery.

[MoscowDev]

I’d love to take this issue on. I’ve worked on production-ready applications and collaborated extensively through GitHub workflows. I’ll dig into the current setup, implement a solid and reliable fix, and deliver a well-tested PR. My focus is on clean, maintainable code and fast, dependable delivery.

[Meemlahsabi]

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

Hi Maintainer, I’m excited about the opportunity to contribute to this project. After carefully studying the issue description, I’m confident I can deliver a thoughtful and high-quality implementation within a reasonable timeframe. I’d appreciate being assigned to work on this issue.

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

[JamesVictor-O]

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

Hello! I’d love to take on this issue. I’ve reviewed the requirements and have a clear path forward for the implementation. I estimate I can have a PR ready within about 3 hours of being assigned. Could you please assign this to me?

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

[drips-wave]

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

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