Seller notifications with Telegram, Discord, email, and webhooks
How to route events without leaking data, spamming teams, or sending the same alert multiple times.
Subscribe by event and scope
A member may want buyer replies for assigned orders, while the owner wants device, payment, and critical incident alerts. Store subscriptions by channel, event, game, and assignment scope.
Sensitive message content should be optional and minimized in third-party channels.
Use an outbox
Write notification intent to an outbox in the same transaction as the business event. Workers deliver it with an idempotency key and record the provider result. This prevents lost alerts and duplicate sends during retries.
Backoff and dead-letter handling keep one failing integration from blocking the rest of the product.
Verify webhooks
Customer webhooks should include a timestamp, event ID, and signature. The receiver can reject stale or replayed payloads. Rotate secrets and allow the owner to test the endpoint with a safe sample event.
Do not send raw marketplace cookies, device tokens, or private keys through any notification channel.