Car Key Transponder Intelligence

Decode. Analyse.
Understand.

Specialised microservice for car key transponder chip analysis. PCF7953, NCF29A1, HITAG-AES — binary dump decoding, ISK extraction, clone readiness assessment, and pattern-matched learning.

View API Docs Admin Dashboard

Core Capabilities

Everything you need for car key transponder work.

Chip Decode

PCF7953 & NCF29A1 binary dump analysis. EROM zone mapping, EEPROM field extraction, memory region identification.

ISK Extraction

Immobiliser Secret Key detection from transponder dumps. Hex offset scanning, pattern matching, confidence scoring.

Clone Readiness

Automated assessment of transponder cloneability. AES-128 detection, crypto status, lock-bit analysis.

Reference Catalogue

79 vehicle-to-chip mappings, 23 ECU dump references, 26 EEPROM specs, 16 immo PIN locations across 15+ brands.

HMAC-Secured API

SHA-256 signed requests with replay protection. Rate-limited, logged, and auditable. Built for service-to-service calls.

Pattern Learning

19 decoder rules — VIN patterns, hex signatures, byte offsets, CRC detection. Rules engine learns from every decode.

Supported Transponder Chips

Deep decode support for NXP/Philips automotive transponder ICs.

PCF7953

NXP HITAG-Pro transponder. Used in BMW CAS4/FEM, JLR KVM, and other modern immobiliser systems.

  • 1KB EEPROM + EROM decode
  • ISK / crypto key extraction
  • Button-slot / key-slot mapping
  • Doctrine reference data

NCF29A1

NXP HITAG-AES next-gen transponder. Used in BMW BDC2, latest JLR systems. AES-128 encrypted.

  • 9-zone EROM mapping
  • AES-128 crypto detection
  • Unlock chain analysis
  • MDI FlashRunner doctrine

API Integration

HMAC-SHA256 authenticated endpoints. Designed for service-to-service integration across the Lock50 platform.

// Decode a transponder dump
POST /api/v1/transponder/decode
// Headers
X-Api-Key-Id: <key-id>
X-Timestamp: <unix-ms>
X-Signature: <hmac-sha256>
// Body
{ "hexContent": "0A1B2C...", "chipFamily": "PCF7953" }
Full API documentation