> ## Documentation Index
> Fetch the complete documentation index at: https://docs.didit.me/llms.txt
> Use this file to discover all available pages before exploring further.
# Crear regla de monitorización de transacciones (KYT)
> Crea reglas KYT personalizadas con la API de Didit: condiciones, ventanas de velocidad, alcance y acciones. Pruébalas en modo TEST y actívalas.
Prompt para la API de creación de reglas
Copiar el prompt al portapapeles
\
\`Create a custom transaction-monitoring rule on my Didit application.
Endpoint:
POST https://verification.didit.me/v3/transactions/rules/
Authentication:
Use the x-api-key header with my Didit API key.
Request body (application/json):
\{
"title": "Structuring - inbound (custom)", // required, unique per application - duplicate -> 400
"description": "20+ inbound EUR transfers, all under 10,000 EUR, 30 days",
"category": "finance", // required: finance, aml_ctf, anomaly_detection, fatf, device_intelligence, crypto_monitoring, travel_rule, responsible_gaming, e_commerce, ...
"mode": "TEST", // required: TEST (recommended start - evaluates, never affects transactions), ACTIVE, DISABLED
"evaluation_mode": "ALL", // ALL = every condition must match, ANY = at least one
"scope": {"transaction_types": ["finance"], "directions": ["INBOUND"]}, // constrains the transaction being evaluated; optional keys: transaction_types, directions (INBOUND/OUTBOUND), action_types
"conditions": [ // read the transaction being evaluated, never the history window
\{"field": "currency", "operator": "eq", "value": "EUR"},
\{"field": "amount", "operator": "lt", "value": 10000}
],
"aggregation": [ // velocity over the history window: ALL entries must match
\{"metric": "count", "operator": "gte", "value": 20, "window": "30d",
"filters": {"direction": "INBOUND", "transaction_type": "finance", "currency": "EUR", "subject_vendor_data": "__current__"}},
\{"metric": "max", "field": "amount", "operator": "lt", "value": 10000, "window": "30d",
"filters": {"direction": "INBOUND", "transaction_type": "finance", "currency": "EUR", "subject_vendor_data": "__current__"}}
],
"actions": [{"type": "add_score", "value": 35}]
}
Schema essentials:
\- Condition operators: eq, ne, gt, gte, lt, lte, in, not_in, contains, not_contains, contains_any (list of strings), regex, fuzzy_match (needs "score" 0-100), exists/is_not_empty/is_not_null, not_exists/is_empty/is_null.
\- Condition fields include amount, preferred_currency_amount, direction, action_type, payment_details, subject_vendor_data, counterparty_country, subject_device_fingerprint, subject_payment_method_*, travel_rule_status, tags, and custom_values. for your own custom_properties.
\- value_type turns "value" into a List UUID ("list"), another field path ("field"), or a relative date ("relative_date").
\- Aggregation windows: m (MINUTES), h, d. A filter value of "__current__" means same-as-the-evaluated-transaction.
\- Conditions and aggregation filters are NOT interchangeable. A condition constrains only the transaction being evaluated; an aggregation filter constrains only the historical window, and it compares by equality or list membership - there is no lt/gte filter. Express a range over the window as a max/min aggregation (e.g. max amount lt 10000 with currency pinned to EUR keeps every transaction in that window under 10,000 EUR), and repeat direction/currency/transaction_type on BOTH halves when the rule promises them - otherwise the rule fires on transactions it never meant to cover.
\- Actions: add_score {value}, change_status {value, workflow_id (REQUIRED for AWAITING_USER)}, add_tags {tag_uuid|tag_name, tag_color}, add_note {note}, add_to_list {list_id}, open_case {blueprint, grouping, attach_matched_transaction}.
Recommended workflow:
1\. Create in mode TEST.
2\. POST /v3/transactions/rules/backtest/ with the SAME conditions, aggregation, evaluation_mode and scope to see matches over your history. Omitted conditions, aggregation and scope add no constraints of their own; dropping scope can include directions or transaction types the saved rule skips. Omitted evaluation_mode defaults to ALL (which can reduce matches for an ANY rule), and omitted period_days defaults to 90 days, not unlimited history.
3\. PATCH the rule to mode ACTIVE once the numbers look right.
Sandbox fixtures for this example: at least 20 inbound EUR finance transactions for the same subject within 30 days, each with raw amount below 10000. No normalized amount is required. Sandbox ingestion does not evaluate rules; call backtest explicitly.
Failure modes:
\- 400 - duplicate title, unknown operator/metric, malformed window, invalid scope direction, contains_any without a list, fuzzy_match without a score, or AWAITING_USER without workflow_id. The body names the exact index and problem.
\- 401 - missing or malformed x-api-key.
Full guide: /transaction-monitoring/rules-api.`
\
Pegar en
## OpenAPI
````yaml es/openapi-25.json POST /v3/transactions/rules/
openapi: 3.0.0
info:
version: 3.0.0
title: Didit Verification API
description: API de verificación de identidad. Autentícate con el encabezado x-api-key.
servers:
- url: https://verification.didit.me
security: []
tags: []
paths:
/v3/transactions/rules/:
post:
tags:
- Transactions
summary: Crear regla
description: >-
Crea una regla CUSTOM de monitorización de transacciones. Los títulos
son únicos por aplicación (un duplicado devuelve 400). Una acción
`change_status` cuyo destino sea `AWAITING_USER` debe incluir
`workflow_id`. Las reglas creadas en modo ACTIVE se aplican de inmediato
a las nuevas transacciones; el procedimiento recomendado es crearlas en
modo TEST, hacer un backtest y, después, cambiar el modo a ACTIVE.
operationId: createTransactionRule
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/TransactionRuleCreateRequest'
example:
title: Structuring - inbound (custom)
description: 20+ inbound EUR transfers, all under 10,000 EUR, 30 days
category: finance
mode: TEST
evaluation_mode: ALL
scope:
transaction_types:
- finance
directions:
- INBOUND
conditions:
- field: currency
operator: eq
value: EUR
- field: amount
operator: lt
value: 10000
aggregation:
- metric: count
operator: gte
value: 20
window: 30d
filters:
direction: INBOUND
transaction_type: finance
subject_vendor_data: __current__
currency: EUR
- metric: max
field: amount
operator: lt
value: 10000
window: 30d
filters:
direction: INBOUND
transaction_type: finance
subject_vendor_data: __current__
currency: EUR
actions:
- type: add_score
value: 35
responses:
'201':
description: La regla creada.
content:
application/json:
schema:
$ref: '#/components/schemas/TransactionRuleDetail'
'400':
description: >-
Error de validación: título duplicado, operador o métrica
desconocidos, ventana mal formada, dirección de alcance no válida o
AWAITING_USER sin workflow_id.
content:
application/json:
schema:
type: object
example:
title:
- A rule with this name already exists.
security:
- ApiKeyAuth: []
x-codeSamples:
- lang: curl
label: curl
source: >-
curl -X POST 'https://verification.didit.me/v3/transactions/rules/'
\
-H 'x-api-key: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"title": "Structuring - inbound (custom)", "description": "20+ inbound EUR transfers, all under 10,000 EUR, 30 days", "category": "finance", "mode": "TEST", "evaluation_mode": "ALL", "scope": {"transaction_types": ["finance"], "directions": ["INBOUND"]}, "conditions": [{"field": "currency", "operator": "eq", "value": "EUR"}, {"field": "amount", "operator": "lt", "value": 10000}], "aggregation": [{"metric": "count", "operator": "gte", "value": 20, "window": "30d", "filters": {"direction": "INBOUND", "transaction_type": "finance", "subject_vendor_data": "__current__", "currency": "EUR"}}, {"metric": "max", "field": "amount", "operator": "lt", "value": 10000, "window": "30d", "filters": {"direction": "INBOUND", "transaction_type": "finance", "subject_vendor_data": "__current__", "currency": "EUR"}}], "actions": [{"type": "add_score", "value": 35}]}'
- lang: python
label: Python
source: |-
from didit import Didit
# Reads DIDIT_API_KEY.
client = Didit()
result = client.transactions.rules.create(
title="Structuring - inbound (custom)",
description="20+ inbound EUR transfers, all under 10,000 EUR, 30 days",
category="finance",
mode="TEST",
evaluation_mode="ALL",
scope={
"transaction_types": ["finance"],
"directions": ["INBOUND"],
},
conditions=[{
"field": "currency",
"operator": "eq",
"value": "EUR",
}, {
"field": "amount",
"operator": "lt",
"value": 10000,
}],
aggregation=[{
"metric": "count",
"operator": "gte",
"value": 20.0,
"window": "30d",
"filters": {"direction": "INBOUND", "transaction_type": "finance", "subject_vendor_data": "__current__", "currency": "EUR"},
}, {
"metric": "max",
"field": "amount",
"operator": "lt",
"value": 10000.0,
"window": "30d",
"filters": {"direction": "INBOUND", "transaction_type": "finance", "subject_vendor_data": "__current__", "currency": "EUR"},
}],
actions=[{
"type": "add_score",
"value": 35,
}],
)
print(result)
- lang: javascript
label: Node.js
source: |-
import Didit from "@didit-protocol/sdk-node";
// Reads DIDIT_API_KEY.
const didit = new Didit();
const result = await didit.transactions.rules.create({
title: "Structuring - inbound (custom)",
description: "20+ inbound EUR transfers, all under 10,000 EUR, 30 days",
category: "finance",
mode: "TEST",
evaluation_mode: "ALL",
scope: {
transaction_types: ["finance"],
directions: ["INBOUND"],
},
conditions: [{
field: "currency",
operator: "eq",
value: "EUR",
}, {
field: "amount",
operator: "lt",
value: 10000,
}],
aggregation: [{
metric: "count",
operator: "gte",
value: 20.0,
window: "30d",
filters: { direction: "INBOUND", transaction_type: "finance", subject_vendor_data: "__current__", currency: "EUR" },
}, {
metric: "max",
field: "amount",
operator: "lt",
value: 10000.0,
window: "30d",
filters: { direction: "INBOUND", transaction_type: "finance", subject_vendor_data: "__current__", currency: "EUR" },
}],
actions: [{
type: "add_score",
value: 35,
}],
});
console.log(result);
- lang: go
label: Go
source: "ctx := context.Background()\n// Reads DIDIT_API_KEY.\nclient := didit.NewClient()\n\nresult, err := client.Transactions.Rules.Create(ctx, didit.TransactionRuleCreateRequest{\n\tTitle: \"Structuring - inbound (custom)\",\n\tDescription: didit.String(\"20+ inbound EUR transfers, all under 10,000 EUR, 30 days\"),\n\tCategory: \"finance\",\n\tMode: \"TEST\",\n\tEvaluationMode: didit.Some(didit.TransactionRuleCreateRequestEvaluationMode(\"ALL\")),\n\tScope: didit.Some(didit.TransactionRuleScopeParam{\n\t\tTransactionTypes: didit.Some([]string{\"finance\"}),\n\t\tDirections: didit.Some([]didit.TransactionRuleScopeDirections{\"INBOUND\"}),\n\t}),\n\tConditions: didit.Some([]didit.TransactionRuleConditionParam{{\n\t\tField: \"currency\",\n\t\tOperator: \"eq\",\n\t\tValue: didit.Some[any](\"EUR\"),\n\t}, {\n\t\tField: \"amount\",\n\t\tOperator: \"lt\",\n\t\tValue: didit.Some[any](10000),\n\t}}),\n\tAggregation: didit.Some([]didit.TransactionRuleAggregationParam{{\n\t\tMetric: didit.Some(didit.TransactionRuleAggregationMetric(\"count\")),\n\t\tOperator: didit.Some(didit.TransactionRuleAggregationOperator(\"gte\")),\n\t\tValue: 20.0,\n\t\tWindow: didit.String(\"30d\"),\n\t\tFilters: didit.Some(map[string]any{\"direction\": \"INBOUND\", \"transaction_type\": \"finance\", \"subject_vendor_data\": \"__current__\", \"currency\": \"EUR\"}),\n\t}, {\n\t\tMetric: didit.Some(didit.TransactionRuleAggregationMetric(\"max\")),\n\t\tField: didit.String(\"amount\"),\n\t\tOperator: didit.Some(didit.TransactionRuleAggregationOperator(\"lt\")),\n\t\tValue: 10000.0,\n\t\tWindow: didit.String(\"30d\"),\n\t\tFilters: didit.Some(map[string]any{\"direction\": \"INBOUND\", \"transaction_type\": \"finance\", \"subject_vendor_data\": \"__current__\", \"currency\": \"EUR\"}),\n\t}}),\n\tActions: didit.Some([]didit.TransactionRuleActionParam{{\n\t\tType: \"add_score\",\n\t\tValue: didit.Some[any](35),\n\t}}),\n})\nif err != nil {\n\tlog.Fatal(err)\n}\nfmt.Printf(\"%+v\\n\", result)"
- lang: java
label: Java
source: >-
import java.util.List;
import java.util.Map;
import me.didit.Didit;
import me.didit.types.TransactionRuleAction;
import me.didit.types.TransactionRuleActionAddScore;
import me.didit.types.TransactionRuleAggregation;
import me.didit.types.TransactionRuleCondition;
import me.didit.types.TransactionRuleCreateRequest;
import me.didit.types.TransactionRuleScope;
// Reads DIDIT_API_KEY.
Didit client = new Didit();
var result =
client.transactions().rules().create(TransactionRuleCreateRequest.builder()
.title("Structuring - inbound (custom)")
.description("20+ inbound EUR transfers, all under 10,000 EUR, 30 days")
.category("finance")
.mode(TransactionRuleCreateRequest.Mode.of("TEST"))
.evaluationMode(TransactionRuleCreateRequest.EvaluationMode.of("ALL"))
.scope(TransactionRuleScope.builder()
.transactionTypes(List.of("finance"))
.directions(List.of(TransactionRuleScope.Directions.of("INBOUND")))
.build())
.conditions(List.of(
TransactionRuleCondition.builder()
.field("currency")
.operator(TransactionRuleCondition.Operator.of("eq"))
.value("EUR")
.build(),
TransactionRuleCondition.builder()
.field("amount")
.operator(TransactionRuleCondition.Operator.of("lt"))
.value(10000)
.build()))
.aggregation(List.of(
TransactionRuleAggregation.builder()
.metric(TransactionRuleAggregation.Metric.of("count"))
.operator(TransactionRuleAggregation.Operator.of("gte"))
.value(20.0)
.window("30d")
.filters(Map.of("direction", "INBOUND", "transaction_type", "finance", "subject_vendor_data", "__current__", "currency", "EUR"))
.build(),
TransactionRuleAggregation.builder()
.metric(TransactionRuleAggregation.Metric.of("max"))
.field("amount")
.operator(TransactionRuleAggregation.Operator.of("lt"))
.value(10000.0)
.window("30d")
.filters(Map.of("direction", "INBOUND", "transaction_type", "finance", "subject_vendor_data", "__current__", "currency", "EUR"))
.build()))
.actions(List.of(TransactionRuleAction.ofAddScore(TransactionRuleActionAddScore.builder()
.type(TransactionRuleActionAddScore.Type.of("add_score"))
.value(35L)
.build())))
.build());
System.out.println(result);
- lang: php
label: PHP
source: |-
transactions->rules->create([
'title' => 'Structuring - inbound (custom)',
'description' => '20+ inbound EUR transfers, all under 10,000 EUR, 30 days',
'category' => 'finance',
'mode' => 'TEST',
'evaluation_mode' => 'ALL',
'scope' => [
'transaction_types' => ['finance'],
'directions' => ['INBOUND'],
],
'conditions' => [[
'field' => 'currency',
'operator' => 'eq',
'value' => 'EUR',
], [
'field' => 'amount',
'operator' => 'lt',
'value' => 10000,
]],
'aggregation' => [[
'metric' => 'count',
'operator' => 'gte',
'value' => 20.0,
'window' => '30d',
'filters' => ['direction' => 'INBOUND', 'transaction_type' => 'finance', 'subject_vendor_data' => '__current__', 'currency' => 'EUR'],
], [
'metric' => 'max',
'field' => 'amount',
'operator' => 'lt',
'value' => 10000.0,
'window' => '30d',
'filters' => ['direction' => 'INBOUND', 'transaction_type' => 'finance', 'subject_vendor_data' => '__current__', 'currency' => 'EUR'],
]],
'actions' => [[
'type' => 'add_score',
'value' => 35,
]],
]);
print_r($result->toArray());
- lang: ruby
label: Ruby
source: |-
require "didit"
# Reads DIDIT_API_KEY.
didit = Didit::Client.new
result = didit.transactions.rules.create(
title: "Structuring - inbound (custom)",
description: "20+ inbound EUR transfers, all under 10,000 EUR, 30 days",
category: "finance",
mode: "TEST",
evaluation_mode: "ALL",
scope: {
transaction_types: ["finance"],
directions: ["INBOUND"],
},
conditions: [{
field: "currency",
operator: "eq",
value: "EUR",
}, {
field: "amount",
operator: "lt",
value: 10000,
}],
aggregation: [{
metric: "count",
operator: "gte",
value: 20.0,
window: "30d",
filters: { direction: "INBOUND", transaction_type: "finance", subject_vendor_data: "__current__", currency: "EUR" },
}, {
metric: "max",
field: "amount",
operator: "lt",
value: 10000.0,
window: "30d",
filters: { direction: "INBOUND", transaction_type: "finance", subject_vendor_data: "__current__", currency: "EUR" },
}],
actions: [{
type: "add_score",
value: 35,
}]
)
puts result.to_h
- lang: csharp
label: .NET
source: >-
using System;
using System.Collections.Generic;
using System.Text.Json;
using Didit;
// Reads DIDIT_API_KEY.
using var client = new DiditClient();
var result = await client.Transactions.Rules.CreateAsync(new
TransactionRuleCreateRequest
{
Title = "Structuring - inbound (custom)",
Description = "20+ inbound EUR transfers, all under 10,000 EUR, 30 days",
Category = "finance",
Mode = "TEST",
EvaluationMode = new TransactionRuleCreateRequestEvaluationMode("ALL"),
Scope = new TransactionRuleScope
{
TransactionTypes = new string[] { "finance" },
Directions = new TransactionRuleScopeDirections[] { "INBOUND" },
},
Conditions = new TransactionRuleCondition[]
{
new()
{
Field = "currency",
Operator = "eq",
Value = "EUR",
},
new()
{
Field = "amount",
Operator = "lt",
Value = 10000,
},
},
Aggregation = new TransactionRuleAggregation[]
{
new()
{
Metric = new TransactionRuleAggregationMetric("count"),
Operator = new TransactionRuleAggregationOperator("gte"),
Value = 20.0,
Window = "30d",
Filters = new Dictionary { ["direction"] = "INBOUND", ["transaction_type"] = "finance", ["subject_vendor_data"] = "__current__", ["currency"] = "EUR" },
},
new()
{
Metric = new TransactionRuleAggregationMetric("max"),
Field = "amount",
Operator = new TransactionRuleAggregationOperator("lt"),
Value = 10000.0,
Window = "30d",
Filters = new Dictionary { ["direction"] = "INBOUND", ["transaction_type"] = "finance", ["subject_vendor_data"] = "__current__", ["currency"] = "EUR" },
},
},
Actions = new TransactionRuleAction[]
{
new()
{
Type = new TransactionRuleActionType("add_score"),
Value = 35,
},
},
});
Console.WriteLine(JsonSerializer.Serialize(result));
components:
schemas:
TransactionRuleCreateRequest:
type: object
required:
- title
- category
- mode
properties:
title:
type: string
description: >-
Nombre de la regla. Único por aplicación entre las reglas no
eliminadas; los duplicados devuelven 400.
description:
type: string
nullable: true
category:
type: string
description: >-
Tema de riesgo que se usa para agrupar y generar informes, p. ej.,
finance, aml_ctf, anomaly_detection, fatf, device_intelligence,
crypto_monitoring, travel_rule, responsible_gaming, e_commerce.
mode:
type: string
enum:
- ACTIVE
- DISABLED
- TEST
description: >-
ACTIVE evalúa en vivo. TEST evalúa y registra las ejecuciones de
reglas, pero nunca modifica la puntuación ni el estado: es el modo
inicial recomendado. DISABLED se omite.
evaluation_mode:
type: string
enum:
- ALL
- ANY
default: ALL
description: >-
Indica si deben cumplirse todas las condiciones (ALL) o al menos una
(ANY). Se ignora cuando las condiciones usan group_index.
scope:
$ref: '#/components/schemas/TransactionRuleScope'
conditions:
type: array
items:
$ref: '#/components/schemas/TransactionRuleCondition'
aggregation:
type: array
items:
$ref: '#/components/schemas/TransactionRuleAggregation'
actions:
type: array
items:
$ref: '#/components/schemas/TransactionRuleAction'
metadata:
type: object
description: Metadatos libres guardados en la regla.
description: >-
Crea una regla CUSTOM. Las reglas en modo ACTIVE se aplican de inmediato
a las nuevas transacciones. Créalas en modo TEST y haz primero un
backtest.
TransactionRuleDetail:
type: object
properties:
uuid:
type: string
format: uuid
title:
type: string
description: >-
Nombre de la regla. Único por aplicación entre las reglas no
eliminadas; los duplicados devuelven 400.
description:
type: string
nullable: true
category:
type: string
description: >-
Tema de riesgo que se usa para agrupar y generar informes, p. ej.,
finance, aml_ctf, anomaly_detection, fatf, device_intelligence,
crypto_monitoring, travel_rule, responsible_gaming, e_commerce.
mode:
type: string
enum:
- ACTIVE
- DISABLED
- TEST
description: >-
ACTIVE evalúa en vivo. TEST evalúa y registra las ejecuciones de
reglas, pero nunca modifica la puntuación ni el estado: es el modo
inicial recomendado. DISABLED se omite.
evaluation_mode:
type: string
enum:
- ALL
- ANY
default: ALL
description: >-
Indica si deben cumplirse todas las condiciones (ALL) o al menos una
(ANY). Se ignora cuando las condiciones usan group_index.
scope:
$ref: '#/components/schemas/TransactionRuleScope'
conditions:
type: array
items:
$ref: '#/components/schemas/TransactionRuleCondition'
aggregation:
type: array
items:
$ref: '#/components/schemas/TransactionRuleAggregation'
actions:
type: array
items:
$ref: '#/components/schemas/TransactionRuleAction'
metadata:
type: object
description: Metadatos libres guardados en la regla.
severity:
type: string
enum:
- UNKNOWN
- LOW
- MEDIUM
- HIGH
- CRITICAL
nullable: true
description: >-
Gravedad informativa que incluyen las reglas de la biblioteca; no se
puede establecer en reglas personalizadas.
source:
type: string
enum:
- PRESET
- CUSTOM
description: >-
Las reglas PRESET provienen de la biblioteca (instalar/desinstalar,
ediciones solo del modo); las reglas CUSTOM son completamente tuyas.
library_key:
type: string
nullable: true
description: >-
Identificador estable de la biblioteca; null para reglas
personalizadas.
latest_triggered_at:
type: string
format: date-time
nullable: true
run_count:
type: integer
description: Cuántas transacciones coincidieron con esta regla.
approved_count:
type: integer
reviewed_count:
type: integer
declined_count:
type: integer
awaiting_user_count:
type: integer
approved_pct:
type: number
reviewed_pct:
type: number
declined_pct:
type: number
created_at:
type: string
format: date-time
updated_at:
type: string
format: date-time
TransactionRuleScope:
type: object
properties:
transaction_types:
type: array
items:
type: string
description: >-
Restringe a tipos de transacción, por ejemplo finance, kyc,
travel_rule, user_event. Vacío o ausente = sin restricción.
directions:
type: array
items:
type: string
enum:
- INBOUND
- OUTBOUND
description: >-
Restringe a direcciones de transacción (sin distinguir mayúsculas y
minúsculas al escribir).
action_types:
type: array
items:
type: string
description: >-
Restringe a tus valores de action_type, por ejemplo withdrawal,
deposit.
description: >-
A qué transacciones se aplica la regla. Solo se aceptan estas tres
claves.
TransactionRuleCondition:
type: object
required:
- field
- operator
properties:
field:
type: string
description: >-
Ruta del campo de la transacción que se evalúa. Campos principales:
amount, currency, direction, action_type, score, severity,
transaction_type, payment_details, preferred_currency_amount (si no
existe, se usa amount_in_default_currency), default_currency_code,
subject_country, counterparty_country, subject_vendor_data,
counterparty_vendor_data, subject_device_fingerprint,
counterparty_device_fingerprint, subject_browser_family,
subject_browser_version, subject_platform, subject_accept_language,
subject_session_age_ms, subject_ip_country, counterparty_ip_country,
subject_ip_address, counterparty_ip_address,
subject_payment_method_type, subject_payment_method_country,
subject_payment_method_fingerprint,
subject_payment_method_account_id (y sus equivalentes
counterparty_payment_method_*), travel_rule_status,
travel_rule_required, travel_rule_obligations_count,
counterparty_dd_status (tu decisión sobre la contraparte de Travel
Rule: APPROVED, RESTRICTED o BLOCKED; una entidad sigue la de su
marca), counterparty_risk_level (LOW, MEDIUM o HIGH; HIGH mientras
tu propio análisis de la contraparte esté marcado),
counterparty_jurisdiction (el país del VASP de la contraparte),
counterparty_responsiveness (RESPONSIVE, UNRESPONSIVE o UNKNOWN),
subject_days_since_previous_transaction, tags y custom_values.
para cualquier clave enviada en custom_properties al crear la
transacción. Los campos de código de país aceptan ISO-2 o ISO-3;
ambos lados se normalizan a ISO-3 antes de la comparación.
operator:
type: string
enum:
- eq
- ne
- gt
- gte
- lt
- lte
- in
- not_in
- contains
- not_contains
- contains_any
- regex
- fuzzy_match
- exists
- is_not_empty
- is_not_null
- not_exists
- is_empty
- is_null
description: >-
Operador de comparación. in/not_in comprueban la pertenencia (value
puede ser una lista o un único valor escalar). contains/not_contains
son comprobaciones de subcadena sin distinguir mayúsculas y
minúsculas sobre un valor de tipo cadena. contains_any recibe una
lista de cadenas y coincide cuando alguna de ellas es una subcadena
del valor del campo, sin distinguir mayúsculas y minúsculas. regex
compara el patrón de value con el campo. fuzzy_match compara con la
cadena de value usando el umbral `score` requerido (0-100).
gt/gte/lt/lte nunca coinciden cuando falta alguno de los dos lados.
exists/is_not_empty/is_not_null (alias) y
not_exists/is_empty/is_null (alias) son comprobaciones de presencia
que ignoran `value`.
value:
description: >-
Valor de comparación. Su forma depende del operador y de value_type;
omítelo para los operadores de comprobación de presencia. Todos los
demás operadores necesitan un valor que no sea `null` ni una lista
vacía; de lo contrario, la regla se rechaza con `400`.
`contains_any` necesita una lista de cadenas, y `contains`,
`not_contains` y `regex` necesitan una única cadena.
value_type:
type: string
enum:
- list
- field
- relative_date
description: >-
Interpretación opcional del valor. `list`: el valor es el UUID de
una lista y las entradas de la lista pasan a ser el valor de
comparación. `field`: el valor es la ruta de otro campo y se compara
campo con campo. `relative_date`: el valor es un objeto de fecha
relativa, p. ej. {"direction": "past", "unit": "days", "amount":
30}.
score:
type: number
minimum: 0
maximum: 100
description: >-
Obligatorio cuando operator es fuzzy_match: el umbral de similitud
de 0 a 100.
group_index:
type: integer
description: >-
Lógica agrupada opcional. Cuando alguna condición incluye
group_index, las condiciones que comparten un mismo índice forman un
grupo y la evaluación agrupada sustituye a evaluation_mode.
group_logic:
type: string
enum:
- AND
- OR
default: AND
description: Cómo se combinan las condiciones DENTRO de un grupo.
groups_logic:
type: string
enum:
- AND
- OR
default: OR
description: >-
Cómo se combinan los resultados ENTRE grupos. Se lee de la primera
condición.
description: >-
Una condición lee solo la transacción que se está evaluando: nunca
filtra la ventana de agregación.
TransactionRuleAggregation:
type: object
required:
- value
properties:
metric:
type: string
enum:
- count
- sum
- max
- min
- avg
- distinct_count
default: count
description: >-
Cómo se agregan las transacciones históricas que coinciden.
unique_count se acepta como alias de distinct_count.
field:
type: string
default: amount
description: >-
Campo que se agrega mediante sum/max/min/avg/distinct_count. Se
ignora con count.
operator:
type: string
enum:
- eq
- ne
- gt
- gte
- lt
- lte
default: eq
description: Comparación aplicada a la métrica calculada.
value:
type: number
description: Umbral con el que se compara la métrica calculada.
window:
type: string
pattern: ^\d+(m|h|d)$
default: 1d
description: >-
Ventana retrospectiva que termina en el txn_date de la transacción:
m (MINUTOS, no meses), h (horas) o d (días), por ejemplo
30m, 24h, 7d, 30d.
filters:
type: object
additionalProperties: true
description: >-
Restringe qué transacciones históricas se agregan. Las claves son
rutas de campo del catálogo de campos de condición; un valor
"__current__" se resuelve al valor del mismo campo en la transacción
que se está evaluando (p. ej., {"subject_vendor_data":
"__current__"} limita la ventana al mismo sujeto), y un valor de
lista indica pertenencia. Los filtros comparan SOLO por igualdad o
pertenencia: no hay filtro lt/gte, así que aquí no se puede expresar
un rango como "transacciones históricas inferiores a 10,000". Aplica
el rango a la métrica en su lugar (la métrica max con el operador lt
mantiene todas las transacciones de la ventana por debajo del
umbral).
description: >-
Control de velocidad sobre las transacciones históricas de la aplicación
dentro de la ventana. Todas las entradas de agregación deben coincidir
para que la regla coincida, independientemente de evaluation_mode. Una
agregación solo restringe la ventana; la transacción que se evalúa está
restringida por scope y conditions, así que repite direction, currency o
transaction_type en ambas partes cuando la regla los garantice.
TransactionRuleAction:
oneOf:
- $ref: '#/components/schemas/TransactionRuleActionAddScore'
- $ref: '#/components/schemas/TransactionRuleActionChangeStatus'
- $ref: '#/components/schemas/TransactionRuleActionAddTags'
- $ref: '#/components/schemas/TransactionRuleActionAddNote'
- $ref: '#/components/schemas/TransactionRuleActionAddToList'
- $ref: '#/components/schemas/TransactionRuleActionOpenCase'
discriminator:
propertyName: type
mapping:
add_score: '#/components/schemas/TransactionRuleActionAddScore'
change_status: '#/components/schemas/TransactionRuleActionChangeStatus'
add_tags: '#/components/schemas/TransactionRuleActionAddTags'
add_note: '#/components/schemas/TransactionRuleActionAddNote'
add_to_list: '#/components/schemas/TransactionRuleActionAddToList'
open_case: '#/components/schemas/TransactionRuleActionOpenCase'
description: >-
Una acción de regla. Una regla puede tener varias; todas se aplican a la
vez cuando la regla coincide. Las reglas en modo TEST registran lo que
habrían hecho sin aplicar ninguna acción.
TransactionRuleActionAddScore:
type: object
required:
- type
- value
properties:
type:
type: string
enum:
- add_score
value:
type: integer
description: >-
Puntos que se suman a la puntuación de riesgo de la transacción.
Pueden ser negativos.
description: >-
Suma puntos a la puntuación de riesgo acumulada de la transacción; el
total determina el estado según los umbrales de revisión/rechazo de la
aplicación.
TransactionRuleActionChangeStatus:
type: object
required:
- type
- value
properties:
type:
type: string
enum:
- change_status
value:
type: string
enum:
- APPROVED
- IN_REVIEW
- DECLINED
- AWAITING_USER
description: >-
Estado que se establece de inmediato, independientemente de la
puntuación. Clave alias: status.
workflow_id:
type: string
format: uuid
description: >-
OBLIGATORIO cuando el valor es AWAITING_USER: el flujo de
verificación que se pide completar al sujeto. Clave alias:
remediation_workflow_id. Didit crea una sesión de remediación
alojada para el sujeto cuando se dispara la regla.
description: >-
Establece directamente el estado de la transacción. DECLINED siempre
prevalece entre las reglas coincidentes.
TransactionRuleActionAddTags:
type: object
required:
- type
properties:
type:
type: string
enum:
- add_tags
tag_uuid:
type: string
format: uuid
description: Etiqueta existente de la aplicación que se va a asociar.
tag_name:
type: string
description: >-
Nombre de la etiqueta que se asociará; se crea en el primer uso (se
almacena en mayúsculas). Indica tag_uuid o tag_name.
tag_color:
type: string
description: >-
Color hexadecimal que se usa cuando tag_name crea una etiqueta
nueva, p. ej., #007AFE.
description: Adjunta una etiqueta de la aplicación a la transacción coincidente.
TransactionRuleActionAddNote:
type: object
required:
- type
- note
properties:
type:
type: string
enum:
- add_note
note:
type: string
description: >-
Texto de la nota adjunta a la transacción (autor: Rule Engine).
Clave alias: value.
description: Adjunta una nota automática de analista a la transacción coincidente.
TransactionRuleActionAddToList:
type: object
required:
- type
- list_id
properties:
type:
type: string
enum:
- add_to_list
list_id:
type: string
format: uuid
description: Lista a la que se añade el vendor_data del sujeto.
description: >-
Añade el vendor_data del sujeto a una lista de bloqueo, una lista de
permitidos o una lista personalizada.
TransactionRuleActionOpenCase:
type: object
required:
- type
properties:
type:
type: string
enum:
- open_case
blueprint:
type: string
format: uuid
description: >-
UUID de la plantilla de caso; por defecto, la plantilla
predeterminada de la aplicación.
grouping:
type: string
enum:
- by_applicant
- by_rule_and_applicant
description: >-
Indica si las coincidencias repetidas se agrupan en un caso por
solicitante o en uno por regla+solicitante.
attach_matched_transaction:
type: boolean
description: Adjunta la transacción coincidente al caso.
description: >-
Abrir un caso de investigación (o añadir a uno). Solo se aplica la
primera acción open_case de una regla.
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: x-api-key
description: >-
La clave de API de tu aplicación, que encontrarás en Developers -> API
keys en la Business Console. La clave principal tiene acceso completo.
Una clave con nombre puede tener un alcance limitado: ninguno, lectura o
escritura por recurso, limitada a algunos flujos o a sesiones aprobadas,
a una lista de direcciones IP y a una fecha de caducidad. 401 significa
que la clave es incorrecta, se revocó o expiró; 403 significa que no se
envió ninguna clave, que la clave no tiene acceso a este recurso o
acción, o que la solicitud provino de una dirección fuera de su lista de
IP; 404 en una ruta de sesión significa que la sesión está fuera de los
flujos o estados de la clave. Una clave sin acceso a contenido
multimedia recibe las URL de imágenes, videos y PDF como null, y una
clave sin permiso de escritura en sesiones recibe los enlaces y tokens
de sesión como null. Consulta https://docs.didit.me/console/api-keys.
````
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.