Skip to main content
Generic ingest is the default inbound path in Connections → Inbound: one webhook URL + clm_wh_*, processor-agnostic. Optional processor guides (Stripe, Mercado Pago, …) are secondary helpers — not a logo catalog. Ingest lets you push events from your PSP, acquirer, or middleware into Clausum for enrichment, audit, and optional assess triggers — complementary to real-time assess (which you call at checkout).

When to use ingest vs assess

Assess does not replace ingest for full transaction lifecycle; many merchants use both. Banks/PSPs use the same generic ingest — no payment-brand grid.

Create an ingest key

  1. Dashboard → Connections → Inbound (webhooks) — hero is generic inbound webhook
  2. Create Webhook ingest key → prefix clm_wh_*
  3. Store the secret (shown once)
Ingest keys (clm_wh_*) are not partner secret keys (clm_sk_*). Using the wrong key returns 401.

Ingest endpoint

Example payload

Clausum normalizes known fields and attaches the event to your organization scope.

Security

  • HTTPS only in production
  • Rotate ingest keys from Connections if compromised
  • Do not expose clm_wh_* in browser code — server-side only

Monitor

Connections → Monitor shows recent partner API activity. For outbound deliveries from Clausum to your servers, use the delivery log on the same Monitor tab.