PSP submerchant protection

PSPs manage many child merchants under one organization. Clausum uses a simple model:

Template — defaults for every submerchant (thresholds, alerts, score adjustment).
Propagate — push the template to all non-customized children in one click.
Customize — override rules and alerts for a specific submerchant when needed.

Org-level rules in Protection still apply to everyone. Submerchant settings add on top — they do not replace your base policy.

Where to configure

Task	Dashboard path
Template + propagate	Merchants → Template & propagation (`/dashboard/submerchants/protection`)
Portfolio	Merchants (`/dashboard/submerchants`)
Per-merchant detail	Merchants → [merchant] → Protection
Org-wide rules & blocklists	Protection (`/dashboard/protection`)

Protection template APIs require a dashboard session (admin/owner). Partner API keys can set per-submerchant overrides via PATCH /api/v1/partner/submerchants/{id} — see PSP submerchants.

Dashboard

Surface	Path	What you get
Home (PSP)	`/dashboard`	Compact portfolio summary card
Portfolio	`/dashboard/submerchants`	Stats table, risk tiers, drill-down
Template	`/dashboard/submerchants/protection`	Defaults + propagate
Child detail	`/dashboard/submerchants/[id]`	Enterprise protection + alerts

APIs (dashboard session): GET /api/v1/submerchants/portfolio, GET /api/v1/submerchants/[id]/stats, protection defaults routes.

Step 1 — Set the template

Open Merchants → Template & propagation and configure:

Field	What it does
Score adjustment	Adds to risk score for every inherited submerchant
Max amount	Cap per payment (major currency units)
Approve / decline thresholds	Score bands for approve vs decline
Alerts enabled	Creates default alert rules per submerchant (volume spike, high score)

Click Save template to store without touching existing children.

Step 2 — Propagate

Click Save and propagate to non-customized to:

Update every submerchant with customized = false
Sync alert rules from the template
Skip merchants you already marked as customized

You will see a summary: how many were updated vs skipped.

Step 3 — Customize one merchant

Open a submerchant → Protection:

Switch	Effect
Inherit org template (on)	Uses template + org rules in Protection
Mark as customized (on)	Stops propagation; enables scoped rules and alert overrides for this child only

When customized, assess merges:

Org rules (psp_submerchant_id null)
Submerchant-scoped rules and blocklists
Template/profile overrides (thresholds, score adjustment, max amount)

Submerchant-scoped entries win over org defaults when both match the same signal.

How assess uses it

Every POST /api/v1/assess with submerchant_id resolves the effective profile before scoring:

Alerts

Default template alerts (when enabled):

Alert	Trigger
Volume spike	Transaction volume vs baseline (ratio ≥ 2.5)
High risk score	Score ≥ 0.75

Alerts are stored per submerchant in behavior_alert_rules. Customize notification roles in the template or per merchant.

Partner API (overrides only)

Programmatic per-submerchant adjustments (org-level clm_sk_* with submerchants:write):

curl -X PATCH "$CLAUSUM_API_BASE/api/v1/partner/submerchants/{id}" \
  -H "Authorization: Bearer $CLAUSUM_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "inherits_defaults": false,
    "customized": true,
    "protection": { "score_adjustment": 10, "max_amount_major": 5000 },
    "thresholds": { "decline": 70 }
  }'

Template save and propagate remain dashboard-only today.

PSP submerchants

Registry, keys, and assess

Protection workspace

Org-wide rules and blocklists

PSP integration

Full PSP onboarding path

Transaction monitor

Alerts and behavior rules

Get started

Integrate by client type

Solutions & prevention

Capabilities — events & ops

Dashboard

Core concepts

Reference

PSP submerchant protection

Where to configure

Dashboard

Step 1 — Set the template

Step 2 — Propagate

Step 3 — Customize one merchant

How assess uses it

Alerts

Partner API (overrides only)

PSP submerchants

Protection workspace

PSP integration

Transaction monitor

​Where to configure

​Dashboard

​Step 1 — Set the template

​Step 2 — Propagate

​Step 3 — Customize one merchant

​How assess uses it

​Alerts

​Partner API (overrides only)

​Related guides

PSP submerchants

Protection workspace

PSP integration

Transaction monitor

Where to configure

Dashboard

Step 1 — Set the template

Step 2 — Propagate

Step 3 — Customize one merchant

How assess uses it

Alerts

Partner API (overrides only)

Related guides