Skip to content
ADVISORY RECONCILIATION · STRIPE ↔ ENTITLEMENTSRun the browser-only CSV audit

INTEGRATION · WEBHOOKS

Your endpoint. Your allowlist. Your responsibility.

Send findings to any HTTPS endpoint whose hostname is explicitly approved by the deployment administrator. SSRF guards apply at every step.

How it works

Configure a custom webhook destination with an HTTPS URL. The hostname must be in ALERT_WEBHOOK_ALLOWED_HOSTS. The payload is sent as JSON with finding details.

  • HTTPS only, no HTTP
  • Hostname must be explicitly allowlisted
  • Private IPs and localhost are blocked
  • Redirects are disabled
  • Validation at save time and send time

Security boundaries

The allowlist is an environment variable set by the deployment administrator. Users cannot add hosts at runtime. This prevents abuse of the alert system as a proxy.

Frequently asked

Can I use a webhook for a non-allowlisted host?

No. The hostname must be in ALERT_WEBHOOK_ALLOWED_HOSTS.

Is the payload encrypted?

The payload is sent over HTTPS. The destination URL is stored as destination metadata, not encrypted.

Next step

Start with the evidence. Connect nothing until the workflow earns it.

START WITH THE EVIDENCE

See the gap before it becomes a refund.

Run a private CSV audit in your browser, or create a workspace and connect an isolated Stripe TEST account.