Update Radar settings

Overview

Update Radar settings

Enables or disables Radar screening and updates monitor/block mode or card-network passthrough for the organization.

When to use this

Use when onboarding merchants to fraud screening or changing how risky charges are handled.

Good to know

Radar is opt-in. When mode is block, charges that hit block rules are rejected before completion.

See also

Get Radar settings · List risk assessments

Authentication

Merchant routes require an API key in the X-API-KEY header (see Integration overview). Use a test key against https://sandbox.api.lomi.africa and a live key against https://api.lomi.africa.

Endpoint

PATCH /organization/radar-settings

Base URLs:

• https://sandbox.api.lomi.africa
• https://api.lomi.africa

Request

Path parameters

No path parameters beyond the URL pattern.

Query parameters

No query parameters.

Headers

Request body

JSON request payload.

Schema: UpdateRadarSettingsDto

Example body:

{
  "enabled": true,
  "mode": "monitor",
  "stripe_radar_passthrough": true
}

Responses

Errors

Errors follow the standard JSON error format (status code and machine-readable message). Validate inputs before calling; 401 indicates a missing/invalid key, 404 a missing resource for this organization, 429 rate limiting. For safe retries on create-style calls, send an idempotency key when your flow supports it.

Example

curl -sS -X PATCH "https://sandbox.api.lomi.africa/organization/radar-settings" \
  -H "X-API-KEY: $LOMI_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{"enabled":true,"mode":"monitor","stripe_radar_passthrough":true}'

OpenAPI

• operationId: RadarController_updateSettings
• Operation: PATCH /organization/radar-settings

Full schemas and Try it: API reference. Machine-readable contract: repo apps/docs/openapi.json.