The IDPylon Platform

One API. Every identity check your compliance stack needs.

Orchestrate document verification, liveness, database checks, and AML screening through a single integration that adapts to each applicant's risk profile.

Risk-first routing

The engine scores each session before selecting checks. Low-risk sessions skip expensive checks. High-risk sessions escalate automatically.

Stateful sessions

IDPylon tracks the full verification history for each user, enabling step-up verification, re-verification triggers, and consistent audit trails.

Pluggable check modules

Each verification module operates independently. Enable or disable modules, set thresholds, and configure fallback paths without code changes.

10,000+ ID types, cross-validated

IDPylon extracts machine-readable zones (MRZ), NFC chip data where available, and visual security features. Forgery detection uses model-based anomaly scoring, not a static rules list.

Doc verification result

{
  "check": "document_verify",
  "result": "pass",
  "doc_type": "passport",
  "mrz_valid": true,
  "tamper_score": 0.02
}

Active and passive liveness, used only when warranted

Passive liveness checks session images for presentation attack indicators without requiring the applicant to move. Active liveness only triggers on elevated risk scores.

Liveness check result

{
  "check": "liveness_passive",
  "result": "pass",
  "attack_type": null,
  "confidence": 0.97
}

Sanctions, PEPs, and adverse media screening

Configurable screen against OFAC, EU, and UN sanctions lists. PEP matching with entity disambiguation. Adverse media monitoring available as an add-on.

Watchlist screen result

{
  "check": "watchlist_screen",
  "result": "clear",
  "lists_checked": ["OFAC", "EU"],
  "pep_match": false
}

Escalation queue with decision context

When automated checks cannot reach the configured confidence threshold, sessions route to your compliance team's review queue with all collected evidence attached.

Manual review event

{
  "event": "manual_review.requested",
  "reason": "confidence_below_threshold",
  "confidence": 0.61,
  "queue_position": 3
}

An API designed by engineers who have integrated KYC before

One POST to /v1/sessions starts a verification. The response tells you what happened and what comes next. Idempotency keys prevent duplicate sessions on mobile network retries. Webhooks fire on every state transition so your backend stays in sync without polling.

POST /v1/sessions

curl -X POST https://api.idpylon.com/v1/sessions \
  -H "Authorization: Bearer sk_live_..." \
  -H "Idempotency-Key: req_7f2a9" \
  -d '{
    "applicant_ref": "usr_8ab12x",
    "checks": "auto"
  }'

// 200 OK
{
  "session_id": "ses_a7f2k9m",
  "decision": "pass",
  "confidence": 0.94
}

Your users' data is not a retention liability

IDPylon's default data retention is 90 days for verification session data. Document images are encrypted at rest and automatically purged. You can configure shorter retention windows or opt into zero-retention mode where IDPylon returns only the structured result without storing raw documents.

Data type	Default retention	Configurable
Session metadata	90 days	Yes (30-365 days)
Document images	90 days	Yes (0-90 days)
Liveness frames	30 days	Yes (0-90 days)
Audit log entries	1 year	Scale tier: rolling export
Zero-retention mode	Off by default	Scale tier

See the platform in your own environment

Start Free Trial View API Docs