Subscription Bot Merchant Account Live Updates

Use merchant-accounts to refresh payment-provider settings in your Telegram subscription bot or Discord subscription bot project UI. The event carries identifiers; fetch account details using the viewer's own authorized REST request.

Subscribe to provider changes

Use a project-scoped user session as described in the Socket.IO connection guide. No account identifier is required:

{ "action": "subscribe", "channel": "merchant-accounts" }

merchant-accounts.changed

Sent after one or more merchant-account records change, including creation, activation, deactivation, credential or webhook configuration changes, and deletion.

{
  "channel": "merchant-accounts",
  "project_id": "93425026-6bb8-4f81-a75d-63f538e1a123",
  "merchant_account_ids": ["11111111-1111-1111-1111-111111111111"],
  "event_id": "9b724ac8-f0e1-4b56-8d7a-2c9c0d11b2f1",
  "emitted_at": 1790000000000
}

Refetch the project merchant-account list or the single account endpoint. A 404 for a previously visible account means it was deleted. No account credentials or configuration snapshot is included in the event.

This is a refresh hint, not confirmation that a provider operation finished. An installation or removal can emit several intermediate changes. Coalesce bursts and use REST responses as the source of truth.

Reconnection and missed events

Delivery is best effort, with no event replay. Refresh once after every subscribed acknowledgement, including after reconnect. Do not depend on receiving every transition or use emitted_at as proof of cross-server ordering. Changes made outside the running API may have no corresponding event.

See provider webhook verification for setup status and manual verification controls.