Skip to main content
Clausum sits between your application and money movement. You enrich each transaction with context, Clausum returns a decision, and confirmed outcomes feed back into blocklists and cases.

​
The protection loop

1

Assess

Your backend calls POST /api/v1/assess (pay-in) or POST /api/v1/assess/payout (disbursements) before capture or transfer. Clausum evaluates blocklists (with flow_scope), rules, velocity, payer history, optional managed threat intel, and returns decision + risk_score.
2

Enforce

Honor the decision: approve, manual review, step-up challenge, or decline. Do not capture or disburse on decline.
3

Report

On confirmed fraud, call POST /api/v1/report-fraud. Clausum opens a case and auto-populates blocklists.
4

Learn

New blocklist entries and payer history immediately affect the next assess.
5

Notify

Clausum sends signed outbound webhooks (transaction.created, transaction.blocked, case.created, …) to your configured URL in Conexiones → Entrada (webhooks).

​
Surfaces

See Access & environments for hostname policy.

​
Components

​
Two authentication surfaces

Programmatic (API keys)

Server and browser integration — assess, report fraud, ingest. Keys: clm_pub_*, clm_sk_*, clm_wh_*. Create under Conexiones → Claves API.

Management (dashboard JWT)

Dashboard-backed routes — blocklists, cases, submerchants, team. Supabase session after sign-in.
See Authentication.

​
Segment-specific behavior

Field requirements vary by segment — call GET /api/v1/assess for the catalog, or follow your segment guide:

Merchant

Comercio integration plan

PSP

Aggregator integration plan

Bank

Institutional integration plan

​
Data you provide

Clausum is payment-platform agnostic (Stripe, Mercado Pago, SPEI, wires, custom rails).
  • Transaction: amount, currency, order id
  • Identity: email, phone, customer id
  • Payment method: card BIN/last4, country, wallet
  • Device: IP, fingerprint, user agent
  • Payout: beneficiary CLABE/IBAN, origin account, initiator
  • Behavior: SDK session signals (optional)
Only amount and currency are strictly required; each additional field unlocks more signals.