Skip to main content
Clausum onboarding sets your organization_type, which determines required API fields, dashboard navigation, and which modules apply to your contract.
Not sure which path you are on? Check Dashboard → Configuración → Empresa or ask your Clausum account team.

Three client profiles

Merchant (Comercio)

E-commerce, marketplaces, and direct checkout integrations.

PSP / Aggregator

Payment service providers routing assess per sub-merchant.

Bank / Fintech

Core banking, treasury, pay-in rails, and payout disbursements.

How documentation is organized

LayerWhat it is
Segment guidesEnd-to-end checklist for your profile — what to integrate, in what order
Capability modulesDeep dives per feature (assess, webhooks, payout, …) — linked from your segment guide
Core conceptsShared mechanics (auth, decisions, blocklists)
API referenceOpenAPI 1.3.0 playground
See the full capability catalog for which modules each segment typically uses.

Shared first steps (all segments)

1

Access sandbox

2

Open Conexiones

Create keys and webhook URLs under Dashboard → Conexiones.
3

Run simulation

Validate rules in Simulación before production traffic — Simulation.
4

Follow your segment guide

Open Merchant, PSP, or Bank for the ordered integration plan.

Commercial modules (reference)

ModuleSKUTypical segments
Prevention (pay-in)CLM-MOD-PREVAll
Operations (cases, audit)CLM-MOD-OPSAll with fraud ops team
Institutional (payout, network)CLM-MOD-INSTBank, some PSP
Threat intel add-onCLM-ADD-INTELContract-dependent
Shared network consumeCLM-ADD-NET-CBank, PSP
Your contract defines which modules are active — the segment guide marks required vs optional steps.