Webhook endpoints let external systems push transactions in real-time via HMAC-signed HTTP requests. Each endpoint has its own secret key and rate limit.

PAYLOAD='[{"amount":5000,"currency":"USD","sender":"ACC-001","receiver":"ACC-002","transaction_date":"2026-04-24T10:00:00Z"}]'
SIG="sha256=$(echo -n $PAYLOAD | openssl dgst -sha256 -hmac YOUR_SECRET | awk '{print $2}')"
curl -X POST "https://vaultmind-6.polsia.app/api/compliance/ingest/webhook?endpoint_id=YOUR_ENDPOINT_ID" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "X-Webhook-Signature: $SIG" \
  -d "$PAYLOAD"

import hmac, hashlib, json, requests

SECRET = "YOUR_SECRET"
API_KEY = "YOUR_API_KEY"
ENDPOINT_ID = "YOUR_ENDPOINT_ID"

payload = [{"amount": 5000, "currency": "USD", "sender": "ACC-001",
            "receiver": "ACC-002", "transaction_date": "2026-04-24T10:00:00Z"}]
body = json.dumps(payload)
sig = "sha256=" + hmac.new(SECRET.encode(), body.encode(), hashlib.sha256).hexdigest()

resp = requests.post(
    f"https://vaultmind-6.polsia.app/api/compliance/ingest/webhook?endpoint_id={ENDPOINT_ID}",
    headers={"Content-Type": "application/json", "X-API-Key": API_KEY, "X-Webhook-Signature": sig},
    data=body
)
print(resp.json())

const crypto = require('crypto');

const SECRET = 'YOUR_SECRET';
const API_KEY = 'YOUR_API_KEY';
const ENDPOINT_ID = 'YOUR_ENDPOINT_ID';

const payload = JSON.stringify([{
  amount: 5000, currency: 'USD', sender: 'ACC-001',
  receiver: 'ACC-002', transaction_date: new Date().toISOString()
}]);
const sig = 'sha256=' + crypto.createHmac('sha256', SECRET).update(payload).digest('hex');

const res = await fetch(
  `https://vaultmind-6.polsia.app/api/compliance/ingest/webhook?endpoint_id=${ENDPOINT_ID}`,
  { method: 'POST', headers: { 'Content-Type': 'application/json',
    'X-API-Key': API_KEY, 'X-Webhook-Signature': sig }, body: payload }
);
console.log(await res.json());

Real-time alerts from the rule-based scan engine. Review flagged transactions and mark them as resolved.

Clerk proactively emails you when compliance scans detect high-risk flags — no need to check the dashboard. Competitors show dashboards. You get notified automatically.

MCB AIAUP compliance requires human review of all high-risk alerts. Reviewer actions (confirm, dismiss, escalate) are logged to the model audit trail with timestamps and override tracking.

Immediately disables ML predictions and falls back to rule-based detection only. Required by bank AI governance policy. Activating requires a documented reason.

Bias analysis across geographic segments, account types, and transaction size brackets. Flags segments where false positive rate exceeds 2× baseline (disparate impact ratio). Required for MCB AIAUP vendor compliance.

Enable scheduled scans so Clerk monitors your transactions 24/7 — no manual clicks required. Email alerts fire automatically when critical flags are detected.

Send real-time compliance events to Slack, Teams, PagerDuty, or any HTTP endpoint. Payloads are HMAC-SHA256 signed for verification.

Generate an exam-ready compliance audit package for OCC/FDIC regulatory reviews. Export includes transaction summary, flag details, audit trail, and system configuration.

Manage API keys for secure bank integrations. All keys start with ck_live_. The full key is only shown once at creation.

Automatically generate and email compliance summaries on a weekly or monthly cadence. Arrives Monday morning — board-ready.

Generate regulatory-grade reports for SAR narratives, risk assessments, and exam preparation — formatted for BSA/AML compliance teams.