Prompt

customer due diligence api

Legal / Compliance & Regulatory1 observationLast seen Oct 29, 2026

Latest observation

Oct 29, 2026OpenAI APIWeb search: off

A Customer Due Diligence (CDD) API is typically used in fintech, banking, and compliance workflows to verify and monitor customers for AML/KYC purposes.

Common CDD API capabilities

  • Identity verification: name, DOB, address, ID document checks
  • Sanctions/PEP screening: check against watchlists
  • Adverse media screening: news/risk indicators
  • Beneficial ownership checks: UBO and corporate structure
  • Risk scoring: assign customer risk level
  • Ongoing monitoring: re-screening on a schedule or event
  • Case management: store reviews, exceptions, approvals

Typical API endpoints

  • POST /customers — create customer profile
  • POST /customers/{id}/verify — run CDD checks
  • GET /customers/{id}/risk-score — retrieve risk score
  • POST /screenings/sanctions — run sanctions screening
  • POST /screenings/pep — run PEP screening
  • GET /cases/{id} — review compliance case
  • POST /monitoring/subscriptions — enable ongoing monitoring

Example request

POST /customers/123/verify
Content-Type: application/json

{
  "full_name": "Jane Doe",
  "date_of_birth": "1990-04-12",
  "country": "GB",
  "address": {
    "line1": "10 High Street",
    "city": "London",
    "postal_code": "SW1A 1AA"
  },
  "id_document": {
    "type": "passport",
    "number": "123456789"
  }
}

Example response

{
  "customer_id": "123",
  "status": "review_required",
  "risk_score": 72,
  "checks": {
    "identity": "passed",
    "sanctions": "clear",
    "pep": "match_found",
    "adverse_media": "no_match"
  },
  "case_id": "case_456"
}

If you’re building one, key design points

  • Authentication: OAuth2 / API keys with mTLS for sensitive environments
  • Audit logs for every screening and decision
  • Data minimization and encryption at rest/in transit
  • Configurable risk rules by country/product/customer type
  • Support for human review and evidence storage
  • Idempotency for repeat submissions
  • Versioned schemas for regulatory change

If you want, I can also provide:

  1. a full OpenAPI spec,
  2. a sample FastAPI/Node.js implementation, or
  3. a CDD API data model.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.