compliance.verification-verdict.final
A KYC, KYB or AML provider's verdict on a subject was applied: approved, rejected, under review or action required, with the claim it issued or revoked. Carries the verdict status only, never the provider's documents, reason text or claim values.
Delivery contract
| Field | Value |
|---|---|
| Event type | compliance.verification-verdict.final |
| Version | 1 |
| Lifecycle state | final |
| Counter-signed receipts | No event-specific advice |
| SDK type | Webhook.ComplianceVerificationVerdictFinalV1 |
The receipt recommendation does not change delivery behavior. DALP waits for a counter-signed receipt only if the webhook endpoint's counterSignedReceipts value is true when DALP queues the delivery. When the value is false, a normal 2xx response completes the delivery.
Related references:
compliance_webhook_events
Payload schema
The schema and examples describe the full payload. Thin delivery omits personal data fields. Use the payload-shape guidance to choose the endpoint configuration.
{
"type": "object",
"properties": {
"chainId": {
"type": "integer",
"exclusiveMinimum": 0
},
"subjectIdentityAddress": {
"type": "string",
"minLength": 42,
"maxLength": 42,
"pattern": "^0x[a-fA-F0-9]{40}$",
"description": "A valid Ethereum address (42 characters, starting with 0x)",
"examples": ["0x71C7656EC7ab88b098defB751B7401B5f6d8976F"]
},
"status": {
"type": "string",
"enum": ["approved", "rejected", "under_review", "action_required"]
},
"provider": {
"type": "string",
"pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$"
},
"providerId": {
"type": "string",
"minLength": 1
},
"topicName": {
"type": "string",
"minLength": 1
},
"claimEffect": {
"type": "string",
"enum": ["issued", "revoked", "none"]
},
"decidedAt": {
"type": "string"
}
},
"required": [
"chainId",
"subjectIdentityAddress",
"status",
"provider",
"providerId",
"topicName",
"claimEffect",
"decidedAt"
],
"additionalProperties": true
}TypeScript SDK example
Use the request's raw body and headers with your endpoint's webhook secret. This handler illustrates verification and event selection. Before writing downstream state, deduplicate deliveries by evt_id and recognize replayed outcomes by their domain identifiers.
const result = await verifyWebhook({
rawBody,
headers,
secret: process.env.DALP_WEBHOOK_SECRET!,
});
if (!result.ok) {
throw new Error(`Webhook verification failed: ${result.code}`);
}
if (result.event.type === "compliance.verification-verdict.final") {
const event: Webhook.Event<"compliance.verification-verdict.final"> = result.event;
console.log(event.payload);
}HTTP delivery example
This illustrative request shows the delivery shape. Its timestamp and signature are placeholders; a verifier rejects them. Use a signed platform delivery to verify your endpoint.
curl -X POST https://consumer.example.com/dalp/webhooks \
-H "content-type: application/json" \
-H "webhook-id: evt_f22d4bb6427bd5cb4a51ff77eb8e9828" \
-H "webhook-timestamp: 1778112000" \
-H "webhook-signature: v1,docs-example-signature" \
--data '{"evt_id":"evt_f22d4bb6427bd5cb4a51ff77eb8e9828","source_id":"example:compliance.verification-verdict.final@1:0","lifecycle_state":"final","payload":{"chainId":537001,"subjectIdentityAddress":"0xcccccccccccccccccccccccccccccccccccccccc","status":"approved","provider":"sumsub","providerId":"0192a4c1-5f3e-7a01-9b2c-3d4e5f607182","topicName":"kyc","claimEffect":"issued","decidedAt":"2026-09-28T09:15:00.000Z"},"related":{"compliance_webhook_events":"compliance_webhook_events_example"},"type":"compliance.verification-verdict.final","version":1,"request":{"idempotency_key":"idem_01JZP7R5W8M9N0P1Q2R3S4T5"}}'Version and manifest
This page documents version 1 of compliance.verification-verdict.final. This event type is not deprecated. The DALP events manifest contains the machine-readable AsyncAPI entry.
compliance.unfreeze.final
A freeze on a subject's holding of an asset was released, sent once the chain finality watermark reaches the source block. `address` scope lifts the address-wide freeze; `amount` scope releases `amount` token units.
custody.account-created.final
A System's account factory created a smart account; sent once the chain finality watermark reaches its source block. Carries the account, its first owner, the factory and the identity bound at creation, if any.