Card Format
The bit-layout structure of a physical or virtual access credential — defines how the reader interprets the bytes streamed off the card / wallet pass. Wiegand "26-bit standard" is the historical baseline; more secure deployments use longer formats (HID 35-bit, Corporate 1000, FASC-N) or smart-card cryptograms (Seos, MIFARE DESFire, Apple/Google mobile credentials).
Each PACS exposes a fixed enum of supported formats. AMAG, for example, supports exactly five: SeiwgV1, SeiwgGSC2_1, SRSeries_10And12Digit, SRSeries_15Digit, Standard. CCURE captures the format alongside the CHUID. Brivo defaults to "Standard 26 Bit" with explicit facility_code + card_number fields. AE-side provisioning must specify the format on every badge operation, or the PACS rejects it (the CardFormat-mandatory limitation in AMAG and the CHUIDFormatID requirement in CCURE).
What other systems call it
Per-vendor / per-standard terminology for this same concept.
| System | Term / Notes |
|---|---|
 AlertEnterprise | Credential Format (in Guardian) |
| LELenel | BadgeFormat (in OnGuard schema) |
| SHSoftware House C·CURE | CHUIDFormatID / Badge.CHUIDFormatID |
| AMAMAG | CardFormat (5 enumerated values) |
| BRBrivo | Standard 26 Bit (typical default) |
Used by 7 connectors
Connectors in the catalog that reference this concept.