AML screening
Overview
AML (Anti-Money Laundering) screening is a critical compliance process that helps identify potential risks associated with individuals and businesses. This guide covers how to integrate and use Parcha’s AML screening capabilities.
Quick Start
API Reference
Endpoint Details
- URL:
https://api.parcha.ai/startKYCAgentJob
(for individuals) orhttps://api.parcha.ai/startKYBAgentJob
(for businesses) - Method:
POST
- Authentication: JWT Bearer token required
- Content-Type:
application/json
Response Codes
200 OK
: Request successful400 Bad Request
: Invalid input data401 Unauthorized
: Invalid or missing authentication, or insufficient permissions429 Too Many Requests
: Rate limit exceeded500 Internal Server Error
: Server-side error
Response Format
Input Requirements
1. Required Fields
Every request must include:
agent_key
: The unique identifier for the agent to be usedkyc_schema
orkyb_schema
: The schema containing the entity information
2. Self-Attested Data
Individual (KYC)
Business (KYB)
Screening Types and Vendor Data
1. PEP Screening
Politically Exposed Person (PEP) screening helps identify individuals who hold prominent public functions.
Vendor Data Schema
2. Adverse Media Screening
Checks for negative news and adverse media mentions.
Vendor Data Schema
3. Sanctions Screening
Checks individuals and businesses against global sanctions lists.
Vendor Data Schema
Complete Request Examples
Individual Screening Request
Business Screening Request
Business Screening Request with Vendor Data
Business Screening Request with Associated Individuals
Authentication and Security
Authentication
All requests must include a valid JWT token in the Authorization header:
The API uses role-based access control. Users must have appropriate permissions to access specific agents and endpoints.
Rate Limits
- PEP screening has a concurrent request limit
- Extraction operations have separate rate limits
- Rate limits are enforced per agent and per operation type
Webhooks
Parcha uses signed webhooks for secure delivery of screening results. Webhook payloads are signed using your API secret key.
To verify webhook signatures:
- Extract the signature from the
X-Parcha-Signature
header - Use your API secret key to verify the signature against the payload
Best Practices
-
Data Quality
- Provide as much information as possible for better matching
- Use standardized formats for dates (YYYY-MM-DD) and country codes
- Include all known aliases and alternative names
-
Performance
- Use the
run_in_parallel
flag for parallel processing - Implement appropriate retry logic with exponential backoff
- Monitor webhook deliveries and implement proper error handling
- Use the
-
Security
- Keep API keys and webhook signing secrets secure
- Implement proper access controls
- Validate webhook signatures
- Follow data retention policies
Error Handling
-
Common Errors
- Invalid input data: Check required fields and data formats
- Authentication errors: Verify JWT token and permissions
- Rate limit exceeded: Implement appropriate backoff strategy
-
Best Practices
- Implement retry logic for transient failures
- Log detailed error information for debugging
- Monitor webhook delivery failures
Support
For additional support:
- Technical Documentation: docs.parcha.ai
- API Status: status.parcha.ai
- Email Support: support@parcha.ai