PEP Screening System Development (Politically Exposed Persons)

A financial regulator fined a crypto exchange $3 million for lacking EDD on a PEP client. Such cases are not rare: FATF R12 requires mandatory identification of politically exposed persons. If your AML system cannot distinguish between PEP and RCA (relatives and close associates), you risk missing high-risk clients. We build turnkey PEP screening: from provider selection to EDD workflow and continuous monitoring. We assess your project in 2 days, deployment in 2–4 weeks.

Without automation, the compliance team spends hours manually checking each client. Our system reduces this to seconds, processing requests in real time via the ComplyAdvantage or World-Check API. Screening accuracy exceeds 95% after filter tuning. In this article, we'll cover how to avoid typical pitfalls and build a reliable PEP system.

Problems we solve

False positives. ComplyAdvantage's database yields 30% matches, but most are false positives. We configure fuzziness and filters by DOB for 95% accuracy.

Missing RCA. PEP relatives are equally risky. We integrate APIs with relative coverage.

Regular rescreening. PEP status changes over time. We set up a weekly cron with compliance officer notification.

How we do it

We use ComplyAdvantage as the primary source. Example TypeScript integration:

class PEPScreeningService {
  async screenPerson(params: {
    firstName: string;
    lastName: string;
    dateOfBirth?: string;
    nationality?: string;
  }): Promise<PEPScreenResult> {
    
    const response = await this.complyAdvantage.search({
      search_term: `${params.firstName} ${params.lastName}`,
      fuzziness: 0.7,
      filters: {
        types: ["pep", "pep-class-1", "pep-class-2", "pep-class-3", "pep-class-4"],
      },
    });
    
    const matches = response.content.data.hits;
    
    if (matches.length === 0) return { isPEP: false, isRCA: false };
    
    // Filter by DOB if available
    const strongMatches = params.dateOfBirth
      ? matches.filter(m => this.dobMatches(m, params.dateOfBirth!))
      : matches;
    
    if (strongMatches.length === 0) {
      return { isPEP: false, possibleMatches: matches.slice(0, 3) };
    }
    
    const match = strongMatches[0];
    return {
      isPEP: match.doc.types.some(t => t.startsWith("pep")),
      isRCA: match.doc.types.includes("relative-close-associate"),
      pepClass: this.extractPEPClass(match.doc.types),
      positions: match.doc.fields?.filter(f => f.tag === "position") ?? [],
      country: match.doc.fields?.find(f => f.tag === "country_names")?.value,
      matchScore: match.score,
      entity: match.doc,
    };
  }
  
  private extractPEPClass(types: string[]): number {
    if (types.includes("pep-class-1")) return 1; // Head of state, government ministers
    if (types.includes("pep-class-2")) return 2; // Parliament members, senior judiciary
    if (types.includes("pep-class-3")) return 3; // Senior military, state-owned enterprise heads
    if (types.includes("pep-class-4")) return 4; // Local government, lower-risk positions
    return 0;
  }
}

After determining status, we launch an EDD workflow for PEP classes 1–2 — requires senior management approval.

async function handlePEPResult(userId: string, result: PEPScreenResult): Promise<void> {
  if (!result.isPEP && !result.isRCA) {
    await db.setUserRiskFactor(userId, "pep", false);
    return;
  }
  
  // PEP requires Enhanced Due Diligence
  await db.setUserRiskFactor(userId, "pep", true);
  await db.updateUserRiskLevel(userId, RiskLevel.HIGH);
  
  const eddRequired: EDDRequirement = {
    sourceOfFunds: true,
    sourceOfWealth: true,
    seniorManagementApproval: result.pepClass <= 2,
    enhancedOngoingMonitoring: true,
    annualReview: true,
  };
  
  await requestEDD(userId, eddRequired);
  await notifyComplianceOfficer(userId, result);
}

For continuous monitoring, we set up weekly rescreening of all active customers.

@Cron("0 2 * * 0") // every Sunday at 2:00 AM
async weeklyPEPRescreening() {
  const activeCustomers = await db.getActiveCustomers();
  
  for (const customer of activeCustomers) {
    const result = await this.pepService.screenPerson(customer);
    const previousStatus = customer.pepStatus;
    
    if (result.isPEP && !previousStatus) {
      // New PEP — immediate notification
      await this.handleNewPEPDetection(customer.id, result);
    }
  }
}

Why PEP classification by risk level matters?

PEP class 1 (heads of state, prime ministers) requires senior management approval and extended source-of-funds checks. Class 4 (local-level officials) only needs light EDD. Misclassification leads to fines or compliance overload. Our API returns pepClass, enabling automation.

How to set up automatic PEP status updates?

We use a regular cron script: every Sunday at 2:00 AM. The ComplyAdvantage API returns updated statuses. When a new PEP is detected, the system immediately notifies the compliance officer and triggers the EDD workflow. This eliminates human error and ensures compliance with FATF Recommendation 12.

PEP data provider comparison

ComplyAdvantage is best for startups due to simple integration, while World-Check suits banks with deeper data. We help you choose the provider based on your budget and regulatory requirements.

Stages and timelines

What's included

• API and workflow documentation (OpenAPI, diagrams)
• TypeScript source code (migration scripts, tests)
• Monitoring dashboard with false positive graphs
• 2-hour compliance team training
• 1 month of post-launch support

Typical mistakes in PEP screening integration

• Ignoring RCA — check not only the PEP but also their close associates. Data is available from all providers.
• Too high fuzziness threshold (>0.9) — you'll miss real matches due to name typos. Optimal is 0.7.
• No rescreening — PEP status can appear after account opening. Set up automatic recalculations.

Estimated timelines

From 2 to 4 weeks depending on the number of providers and EDD logic complexity. Basic integration with one provider and basic screening takes 2 weeks. Full cycle with RCA, rescreening, and dashboard — 4 weeks.

Contact us for a project assessment — we'll calculate timelines and costs in 2 days. Order a turnkey PEP screening system development now. We have 7+ years of AML system experience, 30+ integrations with PEP providers, and guarantee AML audit pass. Learn more about the ComplyAdvantage API.

Why does your project risk without blockchain compliance services?

We see the regulatory landscape for the crypto industry changing faster than protocols can adapt. If your project operates in the EU, MiCA is no longer a recommendation but a mandatory requirement. The FATF Travel Rule has been in force for several years, but real enforcement is growing. Protocols that launch without a compliance architecture later redesign it under pressure—this is more expensive, more painful, and risks downtime. Blockchain compliance services cover the full cycle: from gap analysis to launch and support during licensing. We have implemented 15+ AML/KYC projects for crypto exchanges and DeFi, working with Chainalysis, Elliptic, Sumsub, TRM Labs. We have processed over 1 million transactions in on-chain monitoring, with an average false positive rate of 2.3% for AML screening.

Why is the Travel Rule a technical, not a legal challenge?

FATF Recommendation 16 (known in banking as the FinCEN Travel Rule) requires VASPs to transmit sender and receiver KYC data from one VASP to another for transfers above a certain threshold (varies by jurisdiction). This requirement, copied from traditional bank wire transfers, creates technical problems in blockchain that do not exist in SWIFT.

The first problem is determining VASP-to-VASP. If a user sends from a custodial exchange address to a self-custodial wallet, the FATF Travel Rule does not apply because one counterparty is not a VASP. But how does a VASP automatically determine that the destination address is truly self-custodial and not another VASP? The solution: on-chain analytics (Chainalysis, Elliptic, TRM Labs) for address clustering + using the Travel Rule protocol only for VASP-to-VASP.

The second problem is interoperability between VASPs. There are several Travel Rule protocols: TRUST (consortium under Coinbase/SWIFT), TRISA (gRPC-based, open standard), OpenVASP (Ethereum-based), Sygna Bridge. They are not interoperable. Most major exchanges support several simultaneously. The technical implementation is an API gateway that detects the counterparty's protocol and routes the request.

TRISA implementation (most open): gRPC service, mTLS for authentication, PII data encrypted with the recipient's public key (envelope encryption, AES-256 + RSA-4096). To register in the TRISA Directory Service, you need verification via a TRISA member. The code is an open SDK in Go and Python.

Specific pain point: timing. Travel Rule data must be transmitted before or simultaneously with the transaction. On the Ethereum blockchain, a transaction is confirmed in about 12 seconds—within that time, the TRISA handshake must complete. If the counterparty does not respond, the transaction is blocked or delayed. The UI must explain this to the user, otherwise a flood of support tickets is guaranteed.

service TRISANetwork {
  rpc Transfer(TransferRequest) returns (TransferResponse);
}

message TransferRequest {
  string identity_payload = 1;  // encrypted PII packet
  string envelope_public_key = 2;
  string transaction_hash = 3;
}

How to choose a KYC/AML provider for a crypto project?

KYC providers for cryptocurrencies fall into several tiers:

Tier 1 (enterprise, regulatory grade): Jumio, Onfido, Sumsub, Veriff. Support 200+ countries, video verification, liveliness checks, AML screening via Refinitiv/Dow Jones. Integration via REST API + webhooks. Sumsub is popular in European crypto projects—good SDK documentation for mobile apps.

Tier 2 (DeFi-native, privacy-focused): Fractal ID, Synaps, Persona. Less regulatory overhead, faster integration, but less global coverage for high-risk jurisdictions.

On-chain KYC via credentials: Quadrata Passport, Civic, PolygonID—user verifies once, gets an on-chain credential, protocols verify it without repeated verification. Privacy-preserving via ZK. Not mainstream yet, but we are laying the groundwork in the architecture.

Architectural principle: KYC data is never stored on-chain. Personal data is stored with the provider or in your encrypted database; on-chain only a hash (commitment) or credential (if using VC/SBT approach). This ensures GDPR compliance: the right to erasure is achievable if data is off-chain.

Typical mistake: storing wallet-to-identity mapping in plaintext in PostgreSQL without row-level encryption. One SQL injection and the entire KYC database is compromised. Minimum: column encryption for PII fields (PGP or AES via pgcrypto), separate key management (AWS KMS, HashiCorp Vault), audit log for all PII access.

For AML screening, we use Chainalysis, Elliptic, or TRM Labs. Integration is asynchronous via webhook: results come in 1–5 seconds. Threshold-based blocking: HIGH risk — auto-block, MEDIUM — manual review. Hold period for suspicious transactions is 24–72 hours until manual review. Sanctions screening separately: OFAC SDN list updates several times a week; we use direct OFAC list integration (free) with custom address matching logic.

How do we implement MiCA support?

Markets in Crypto-Assets Regulation (EU 2023/1114) requires CASP (Crypto-Asset Service Provider) licensing in one EU state with passporting. Technical requirements affecting development:

White paper is mandatory for issuers of ART (Asset-Referenced Tokens) and EMT (E-Money Tokens)—not a marketing document but a legally binding prospectus with technical description, holder rights, and redemption mechanisms.

Custody requirements: client assets separate from operational assets. Technically: separate wallets/accounts per client (or omnibus with off-chain mapping + regular reconciliation), no possibility to use client funds for operational needs.

Transaction monitoring and reporting: CASPs must keep records of all transactions for at least 5 years and provide them to the regulator upon request.

Travel Rule in MiCA: the threshold for VASP-to-VASP transfers is zero (not the FATF threshold). Implementation requires a Travel Rule endpoint operating 24/7.

Compliance infrastructure implementation process

Compliance architecture is not added on top of an existing product without pain. The correct order: compliance requirements → data model → business logic → UI. If you already have a product without a compliance layer, we start with a gap analysis: what data is already collected, where the gaps are, what will require schema migration.

1. Gap analysis — audit of current architecture and data flow (1–2 weeks).
2. Design — selection of KYC provider, Travel Rule protocol, AML tool, data model.
3. Integration — connecting KYC API, implementing AML screening in the pipeline, setting up Travel Rule gateway.
4. Testing — end-to-end tests, simulating Travel Rule handshake, verifying sanctions screening.
5. Deployment and monitoring — rollout with feature flags, setting up alerting for compliance service errors, audit trail.
6. License support — preparing documentation for the regulator, assisting with inspections.

What does the blockchain compliance service include?

• Compliance architecture documentation (data flow, ER diagrams, API specifications).
• Integration of KYC/AML/Travel Rule APIs with your backend.
• Setup of monitoring and alerting for compliance services.
• Training your team on tools (Chainalysis, Sumsub, etc.).
• Support during the licensing process (MiCA, FATF).

Timeline benchmarks

• KYC/AML integration with Sumsub or Jumio — from 3 to 6 weeks.
• Travel Rule (TRISA or Sygna) — from 6 to 10 weeks.
• Full compliance infrastructure for CASP licensing — from 4 to 8 months.
• On-chain compliance via VC/SBT with ZK (MiCA-ready) — from 5 to 9 months.

Scope is refined after gap analysis. To evaluate your project, contact us—we will conduct a free analysis of your current architecture and select the optimal set of tools. Get a consultation on compliance architecture for MiCA or Travel Rule. Our team has over 7 years of blockchain development experience and 15+ deployed compliance solutions. Request an audit of your protocol for compliance with current regulatory requirements.