Events
Thresholds are configured at the environment level, so you can set several alert levels (for example 80%, 50%, and 20% remaining). Each
credit_balance.low payload includes thresholdPercentage, the threshold that was crossed, along with remainingBalance, remainingBalancePercentage, and the creditCurrency the balance is in. Each event’s reference page shows its full payload.
To receive these events, add a webhook endpoint in Stigg and subscribe it to both. See Webhooks for setup and signature verification.
Choose a response for each threshold
Escalate the message as the balance drops:Handle the webhooks
- Alert your customer success team in Slack or Teams when a high-value customer runs low
- Update a usage dashboard with the latest balance
- Restrict access when a balance is depleted, if the currency doesn’t use a soft limit
Recommendations
- Deduplicate on
messageId, since Stigg can deliver the same webhook more than once. - Set at least three thresholds so customers have time to act before they run out.
- Include the credit currency name and remaining balance in each message.
- Link directly to the page where customers top up or manage credits.
- Track which notifications lead to top-ups, and adjust thresholds and wording based on the results.