Prompt
customer due diligence api
Latest observation
Oct 29, 2026
OpenAI 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 profilePOST /customers/{id}/verify— run CDD checksGET /customers/{id}/risk-score— retrieve risk scorePOST /screenings/sanctions— run sanctions screeningPOST /screenings/pep— run PEP screeningGET /cases/{id}— review compliance casePOST /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:
- a full OpenAPI spec,
- a sample FastAPI/Node.js implementation, or
- a CDD API data model.