Brand lander

Kastle Systems Compatible Key Cards & Fobs

Security ID Systems supplies compatible key cards and fobs for Kastle Systems 32-bit installations — encoded to your building's facility code, card number, issue level, and Kastle parity so they read identically at every reader in your system. Because Kastle operates as a managed-access provider, tenants and employers often have no direct path to order spares, making an independent compatible supplier a practical necessity.

01

Proprietary Format on File

The Kastle 32-bit proprietary format — facility code, card number, issue level, and Kastle parity — is encoded in-house. No guesswork, no generic blank cards: every credential is built to the exact bit structure your readers validate.

02

Independent of the Managed-Access Channel

Orders are fulfilled directly by Security ID Systems, with no involvement from Kastle or your building operator. Tenants and employers get the spares they need without waiting on a managed-platform procurement cycle.

03

Single Replacements to Bulk Runs

Whether you need one replacement fob or a hundred cards for a new tenant floor, we supply to order. All credentials are pre-encoded and ready to enrol — no programming equipment required on your end.

Kastle Systems Compatible Credentials

Kastle Systems is a managed cloud-access provider that controls credential issuance as part of its service contract. That closed-loop model works well for the building operator, but it creates a supply gap for tenants, employers, and facilities managers who need additional or replacement cards quickly — and without routing every order through the managed-access channel. Security ID Systems fills that gap with credentials that are fully compatible with Kastle readers and panels.

Our compatible cards and fobs are manufactured to the Kastle proprietary bit structure and supplied pre-encoded to the values your system is already programmed to accept. No firmware changes, no panel modifications, and no involvement from the building's access provider are required on your end — the credential is presented to the reader and the door opens exactly as it would with an original-issue card.

This page covers the 32-bit Kastle format in detail, explains why managed access creates the supply constraint most tenants encounter, and outlines exactly what information you need to provide when placing an order. For a fuller narrative on the managed-platform model and how Kastle credentials are produced, see our deep dive on Kastle Systems fobs and cards.

The 32-Bit Kastle Format

The Kastle proprietary format encodes four distinct fields into a 32-bit transmission: facility code, card number, issue level, and a Kastle-specific parity sequence. This is not a standard Wiegand format such as the widely documented HID H10304 46-bit or the common Lenel 42-bit structure — the parity algorithm and field boundaries are Kastle's own design. Readers programmed for Kastle will reject any credential that does not pass parity validation, which is why off-the-shelf 26-bit or generic proximity cards will not work in these systems.

Understanding the format also explains why this is a Tier-S supply — the 32-bit Kastle credential is rarely offered by generic access-card vendors. Security ID Systems has the format on file and can encode to any valid facility code and card-number range, including the issue-level field that some Kastle installations use to distinguish credential generations.

Kastle installations typically operate on 125 kHz LF proximity technology, placing these credentials in the same frequency family as standard 125 kHz LF proximity cards and fobs. The credential communicates passively when brought into range of the reader, with no battery or user interaction required.

The issue-level field deserves particular attention. Unlike facility code and card number, which remain stable across an installation's lifetime, the issue level can be incremented when a building refreshes its credential stock — for example, after a bulk loss event or a planned rotation. If your building has ever reissued credentials en masse, there is a good chance the active issue level differs from what was printed on the original card. Providing the correct current issue level is the single most common point of failure in self-sourced Kastle replacement orders, and it is one of the questions our order process specifically captures.

Why Managed Access Makes Spares Hard to Source

In a traditional access-control installation, the building owner or facilities manager holds the system credentials and can order replacements from any compatible supplier. Kastle's managed-access model differs: the access platform, credential database, and often the physical credential supply chain are all under Kastle's administration. Tenants typically cannot purchase additional fobs directly from a hardware distributor because the required encoding parameters — particularly the facility code and parity — are not published.

Security ID Systems operates as an independent supplier in the managed and cloud-access segment. We are not part of the Kastle service infrastructure, and credentials ordered from us are manufactured and encoded to your specifications independently. This is the same category of supply used for other managed-platform formats — for example, organisations running Verkada compatible access cards or Avigilon compatible credentials face a structurally similar sourcing challenge. Proprietary-format systems from other vendors in this segment — including Software House CCOTZ 37-bit and ADT 31-bit compatible proximity cards — all require the same approach: knowing the encoding parameters and working with a supplier that holds the format.

Our buyer's guide on compatible vs genuine access cards explains in practical terms what compatibility means, what information you need to provide, and how to confirm a compatible credential will function in your specific installation — useful reading before placing a first order for any proprietary-format system.

Encoded to Your Building

Ordering compatible Kastle credentials requires supplying the encoding parameters your installation uses. At minimum, this means the facility code and the card-number range you need. If your installation uses the issue-level field, that value must also be provided so the credential passes parity correctly. The format identification guide walks through how to retrieve these values from an existing credential or your access-control admin console.

Cards and fobs are encoded to order — we do not ship blank credentials for Kastle installations. This ensures that every credential we supply is ready to enrol in your system's cardholder database and present correctly at the reader without additional programming on your side. Order quantities start at individual replacement cards and scale to bulk runs for employers managing multi-tenant floors or high-turnover workforces.

For installations that use non-standard facility codes or tightly controlled card-number sequences, we also recommend reviewing our guide to corporate custom facility codes and FlexSecur formats — it covers the documentation typically needed to ensure accurate encoding for formats where the bit structure is not publicly standardised, which applies directly to the Kastle 32-bit format.

Credential Form Factors and Practical Considerations

Compatible Kastle credentials are available in two form factors: ISO-sized clamshell card and standard key fob. The clamshell card fits ID-card holders and badge reels and is the most common choice for office tenants who carry the credential alongside other building-access cards. The key fob attaches to a keyring and is the preferred option for residential tenants and employees who do not carry a badge holder.

Both form factors carry identical electrical performance at 125 kHz: read range is determined by the reader's antenna, not the credential type, so substituting a fob for a card — or vice versa — does not affect the read distance you experience at your specific readers. If your building uses combination readers that accept both cards and fobs, either form factor will function at the same range.

Durability is worth noting for high-turnover environments. The clamshell card format encases the antenna and chip in a rigid PVC shell that resists the flexing damage common in wallet-carried credentials. Key fobs use an overmoulded housing that protects the internal assembly from the mechanical stress of everyday keyring use. Both are manufactured to standard commercial tolerances for access-control credentials and are not rated for industrial wet environments.

If your organisation is issuing credentials to a mix of staff categories — some carrying lanyards and badge holders, others on keyrings — you can specify a split quantity across both form factors in a single order. Each credential is individually encoded to its assigned card number, so the cardholder database enrolment process is identical regardless of form factor.

Request a Kastle Quote

To receive a quote for compatible Kastle Systems cards or fobs, use the contact form and include your facility code, required card-number range, and preferred credential form factor — ISO card, clamshell card, or key fob. Indicate whether your installation uses the issue-level field and, if so, which value is active. Bulk pricing applies to orders of ten credentials or more.

Security ID Systems is an independent manufacturer and supplier of compatible access-control credentials and is not affiliated with, authorized by, or endorsed by Kastle Systems.

Kastle Systems 32-Bit Format at a Glance

ParameterKastle 32-Bit Detail
Bit length32 bits (proprietary)
Field structureFacility code + Card number + Issue level + Kastle parity
Frequency125 kHz LF proximity
ParityKastle-proprietary algorithm; non-standard Wiegand
Credential form factorsISO clamshell card, key fob
EncodingPre-encoded to order; blank credentials not supplied
Supply tierTier-S — not stocked by generic proximity-card vendors
Minimum orderSingle credential (bulk pricing at 10+)
Issue-level fieldOptional field used by some installations; must be provided if active

All referenced brands and all other brand and product names are trademarks of their respective owners. Security ID Systems is an independent manufacturer and supplier of compatible access-control credentials and is not affiliated with, authorized by, sponsored by, or endorsed by these companies. Brand and format names are used only to identify the systems our products are compatible with. MIFARE and DESFire are registered trademarks of NXP B.V.

Compatible formats we cover for this

125 kHz Rare format

Kastle Systems 32-bit

Compatible with Kastle Systems

Chip
T5577 / EM4305
Format
32-bit Kastle format: facility code + card n…
View compatible credential
LF+HF Rare format

Verkada Pass / Verkada One (Ucode 9 UHF)

Compatible with Verkada

Chip
T5577 / EM4305 · Genuine NXP MIFARE
Format
Verkada Pass / Verkada One - 140x88mm card o…
View compatible credential
125 kHz Rare format

Lenel 42-bit (L11601-adjacent)

Compatible with Lenel

Chip
T5577 / EM4305
Format
42-bit: parity + 14-bit site + 12-bit card +…
View compatible credential
125 kHz Rare format

Avigilon 56-bit (Avig56)

Compatible with Avigilon

Chip
T5577 / EM4305
Format
56-bit Avigilon Wiegand: facility code + car…
View compatible credential
125 kHz Rare format

Software House CCOTZ 37-bit (C-CURE/iSTAR)

Compatible with Software House

Chip
T5577 / EM4305
Format
37-bit CCOTZ (Software House proprietary) us…
View compatible credential
125 kHz Rare format

HID ADT 31-bit (ADT31)

Compatible with HID Global

Chip
T5577 / EM4305
Format
31-bit: 4-bit facility + 23-bit card number,…
View compatible credential
125 kHz Rare format

ATS Wiegand 30-bit (ATSW30)

Compatible with ATS

Chip
T5577 / EM4305
Format
30-bit: parity + 12-bit site + 16-bit card +…
View compatible credential
125 kHz Rare format

Visa2000

Compatible with Visa2000

Chip
T5577 / EM4305
Format
ASK; 64-bit Visa2000 format with checksum (k…
View compatible credential
125 kHz Rare format

HID H800002 46-bit

Compatible with HID Global

Chip
T5577 / EM4305
Format
46-bit HID format (H800002): facility code +…
View compatible credential
Browse all compatible formats

Kastle Systems Compatible Key Cards & Fobs — common questions

Can you supply a compatible Kastle fob?

Yes. Security ID Systems manufactures and supplies compatible key fobs for Kastle Systems installations, encoded to the proprietary 32-bit format with your facility code, card number, issue level, and correct Kastle parity. Fobs are supplied ready to enrol in your system's cardholder database and require no additional programming.

Can I get a spare Kastle card without going through the building?

Yes. As an independent supplier, Security ID Systems encodes compatible Kastle credentials directly to your specifications. You do not need to route the order through the building operator or managed-access provider. You will need your facility code and card-number range, which can often be read from an existing credential or retrieved from your system admin.

What is the 32-bit Kastle format?

The Kastle 32-bit format is a proprietary proximity encoding that carries four fields: facility code, card number, issue level, and a Kastle-specific parity sequence. It operates at 125 kHz and is not interchangeable with standard Wiegand formats such as 26-bit H10301 or common 34-bit or 37-bit structures. Readers programmed for Kastle validate the parity field and will reject credentials that do not conform to it.

Can you match my building's facility code?

Yes — provided you can supply the facility code value, we encode compatible credentials to it. If you are unsure of your facility code, the format identification guide on our site explains how to retrieve it. For the issue-level field, the value from your most recently issued credentials is what we replicate.

Can we order Kastle fobs or cards in bulk?

Yes. Orders can be placed from a single replacement credential up to multi-hundred-unit runs. Bulk pricing applies at ten credentials or more. For larger programmes — multi-tenant buildings, corporate campuses, or high-turnover environments — use the contact form and specify your required card-number range and quantity.

What is the Issue Level field on a Kastle card?

The issue level is a sub-field within the Kastle 32-bit encoding that some installations use to distinguish between successive generations of credentials for the same card number. When a building refreshes its credential stock — after a bulk loss event or a planned rotation — the issue level is incremented so that older credentials can be deactivated while new ones continue to work. If your installation uses this field, you must provide the currently active value when ordering; a credential encoded to an outdated issue level will fail parity validation at the reader.

Will a compatible Kastle card work on every reader in my building?

Yes, provided the encoding matches what your system's panel is programmed to accept. A compatible credential encoded to the correct facility code, card number, issue level, and Kastle parity will function at every reader on that panel — just as an original-issue credential would. If readers in one zone behave differently from others, the most common cause is a panel configuration difference rather than a credential issue; your building's access admin can confirm whether zone-level restrictions apply.

Request a quote

Tell us what you need and we'll quote it

Send the format, quantity and your existing system (or a photo of a card and reader). We confirm compatibility before production and ship worldwide — including the rare formats no one else lists.