Stack guide
Slack alerts for payment anomalies that matter
Monitoring dies by notification, not computation: teams mute chatty channels and blindness arrives disguised as tidiness. Alert design for payment findings therefore optimises for human sustainability — thresholds tuned to materiality, digests absorbing noise, payloads complete enough to act without context-switching. The mute-test governs everything: would a senior engineer mute this channel within a week? Then redesign before shipping.
Threshold architecture
Two tiers mirror production defaults: immediate routing above $500 (material, actionable), daily digest above $100 (visibility without interruption). Per-org configurability respects that a $200 finding means different things to different platforms. Below-threshold items remain queryable rather than announced.
Payload anatomy
Amount, cause classification, risk band, charge and transfer ids, deep link to the finding drawer — everything action requires minus dashboard archaeology. Finance acting from Slack directly is the success criterion; "check the dashboard" defeats the purpose.
{
"text": "Severe finding · $1,240 unreversed transfer",
"blocks": [{
"type": "section",
"fields": [
{ "type": "mrkdwn", "text": "*Cause:* Unreversed transfer" },
{ "type": "mrkdwn", "text": "*Risk:* Severe (84)" },
{ "type": "mrkdwn", "text": "*Charge:* ch_3Px…9sK" }
]
}]
}Channel topology
#payments-critical for immediates; #finance-digest for dailies; nothing else. Extra channels fragment attention and multiply muting surfaces — two channels survive contact with reality; five do not.
Common questions
Email too, or Slack only?
Both — email digests survive Slack-outage weeks and satisfy audit-trail preferences. Cadence configurable per organisation.
Does this require a FeeGuard integration?
No — the page stands alone as stack guidance. FeeGuard observes your event stream externally rather than embedding in it.