Support · Troubleshooting
Connected but seeing no findings
Walk the tree in order — each step eliminates a cause, and if all four check out, zero may simply be true. The scan total proving cleanliness is a result, not a failure.
1 · Are all eight events enabled?
Check your Stripe webhook endpoint configuration against the required list. Missing events create silent blind spots — charge.refunded alone is not enough; dispute, transfer, payout and balance events each feed specific detectors.
2 · Did the historical scan run?
Real-time detection covers new events only. The 90-day lookback populates your baseline — if it never ran, the queue starts empty because history was never read, not because nothing exists.
3 · Does your refund volume make findings likely?
A platform with three refunds a quarter may genuinely produce one finding per year. Check the scan’s processed-charge count against your expectations rather than eyeballing the empty queue.
4 · Is tolerance filtering sub-cent noise?
The two-minor-unit tolerance suppresses rounding phantoms. If you exported data and computed gaps of one or two cents, those are noise by design — the alternative is a queue full of ghosts nobody trusts.
If everything checks out
Then the number is zero and that is the answer. Verify quarterly; the point of monitoring is that you never have to wonder again.