Recipe: AML sanctions screening

Overview

This recipe wires Meridian's address-resolution engine to live sanctions lists. Every inbound or outbound address is checked against consolidated OFAC SDN, EU consolidated, and UN Security Council datasets. Matches trigger a configurable block-or-flag policy with full audit trail.

Ingredients

• Meridian Screening API key (scoped to sanctions:read)
• One or more active sanctions list subscriptions
• A webhook endpoint to receive match notifications
• Policy engine rule defining block vs. flag behavior

Steps

1. Provision the API key. In the Meridian dashboard, create a key with the sanctions:read scope.
2. Select lists. Enable OFAC, EU Consolidated, and UN Security Council under Screening → Sources.
3. Define the policy. Choose “Block and alert” for exact matches and “Flag for review” for fuzzy matches above 90% confidence.
4. Register a webhook. Meridian POSTs a signed JSON payload on every match. Verify the signature with your webhook secret.
5. Integrate the SDK. Call meridian.screen(address) before any transaction broadcast.

Response shape

{
  "address": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
  "matches": [
    {
      "list": "OFAC_SDN",
      "confidence": 1.0,
      "action": "block",
      "entity": "Entity name redacted"
    }
  ],
  "timestamp": "2026-01-17T14:22:00Z"
}