App notifications

App notifications send concise payment status updates to an operations chat. They complement Agent Payments Webhooks: use signed Webhooks or the management API as the source of truth for automation, and use app notifications to give people timely visibility.

Supported destinations

• Telegram uses the shared StableOps bot. You can connect a private chat, a group, or a forum topic.
• Discord uses an Incoming Webhook created in the destination channel.

Open Agent Payments → Integrations → App notifications to connect and manage destinations. Destinations and quotas are isolated across the main product, Agent Payments, Sandbox, and Live environments.

Default events

New destinations initially subscribe to approval, settlement-risk, resource-failure, and pause events that commonly need human attention, including:

• agent_payment.intent.awaiting_approval
• agent_payment.settlement.unknown
• agent_payment.settlement.settled
• agent_payment.resource.failed
• agent_payment.agent.paused
• agent_payment.organization.paused

You can enable all Intent, approval, authorization, settlement, resource-outcome, and circuit-breaker events as needed. Messages contain only the Agent, Intent, amount, origin, and a shortened recipient, with a link to the Agent Payments payment or Agent detail. Policy documents, keys, and full context are not included.

Connect Telegram

1. Select Telegram and create a connection.
2. Open the group or private-chat link. For a forum topic, copy the displayed /connect command into that topic.
3. Return to the console after the chat is detected, choose a name, language, and events, then confirm.

The connection link expires after ten minutes. The bot must remain in the destination and be allowed to post messages.

Connect Discord

1. In Discord, open the destination channel's integration settings and create an Incoming Webhook.
2. Copy its URL, select Discord in StableOps, and paste the URL.
3. Choose a name, language, and events, then connect.

StableOps sends a verification message before saving the destination and stores the Webhook URL with envelope encryption.

Delivery and recovery

Transient failures are retried with backoff. Rate-limit responses honor the provider's retry delay. Invalid or inaccessible destinations are automatically disabled, while failed and dead-letter deliveries can be replayed from the console after the destination is fixed.

For machine-readable Agent Payments events and signature verification, see Agent Payments Webhooks.