Skip to main content
Payment service providers (PSPs) often process on behalf of many submerchants. Clausum models them as a logical registry tied to your organization — not separate tenant accounts.

​
Requirements

RuleDetail
Organization typepsp (set during onboarding)
When registeredIf your org has any active submerchant, submerchant_id is required on every POST /api/v1/assess
KeysSame Partner keys (clm_sk_* / clm_pub_*) as the PSP org
Discover segment rules: GET /api/v1/assess → field_requirements_by_segment.psp.

​
Register submerchants

Dashboard: Conexiones → wizard sandbox/production → Subcomercios. API: 
curl -X POST "$CLAUSUM_API_BASE/api/v1/submerchants" \
  -H "Authorization: Bearer $CLAUSUM_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "external_id": "sm_acme_mx",
    "name": "Acme MX Store",
    "country": "MX",
    "mcc": "5411"
  }'
MethodPathPurpose
GET/api/v1/submerchantsList registry
POST/api/v1/submerchantsCreate
PATCH/api/v1/submerchants/:idUpdate
DELETE/api/v1/submerchants/:idDeactivate
All endpoints require Partner auth (401 without a valid clm_sk_*).

​
Assess with submerchant

{
  "amount": 4500,
  "currency": "USD",
  "email": "buyer@example.com",
  "submerchant_id": "sm_acme_mx",
  "order_id": "ORD-9912"
}
Response may include submerchant_id and submerchant_name for reconciliation and outbound webhooks.
Use stable external_id values from your onboarding system — they become the canonical submerchant_id in assess.