Badge / Credential
The physical or virtual artifact a cardholder presents at a reader to authenticate. In its most generic form this is a card with an embedded credential identifier (Wiegand bits, CHUID, smart-card cryptogram, etc.). In modern deployments the credential may instead live in an Apple Wallet, Google Wallet, or Samsung Wallet pass on the cardholder's phone, or in a TOTP/biometric template.
AE Guardian uses Asset or Card as the canonical term; PACS vendors use a startling variety of names — Badge (Lenel, CCURE, AMAG, Honeywell), Token (Avigilon ACM), Credential (Brivo, SSG, modern REST APIs), Card (most legacy systems). Multi-vendor deployments must standardize the AE-side mapping so the same physical badge is represented consistently across all integrated systems.
Within a single PACS, a cardholder typically has one primary credential plus zero or more secondary / temporary credentials (visitor badges, replacement cards during reissuance, mobile passes alongside physical cards).
What other systems call it
Per-vendor / per-standard terminology for this same concept.
| System | Term / Notes |
|---|---|
 AlertEnterprise | Asset / Card (in Guardian) |
| LELenel | Badge (BADGEKEY-keyed; CARDNUMBER as wire identifier) |
| SHSoftware House C·CURE | Badge (CHUID, CHUIDFormatID, CardNumber, FacilityCode) |
| AMAMAG | Card (CardInfoTable.CardNumberDisplay; supports 5 format types — SeiwgV1, SeiwgGSC2_1, SRSeries_10And12Digit, SRSeries_15Digit, Standard) |
| GEGenetec | Credential |
| HOHoneywell | Card (BADGE_CARD_ALL.CARDNO) |
| BRBrivo | Badge (CardNumber + FacilityCode; e.g. 'Standard 26 Bit' format) |
| AVAvigilon | Token (TokenInternalNumber, plus 9 boolean flags including TokenVIP, TokenTrace, TokenExtAccess) |
| SSSSG | Credential (mobile-first; "Card" in API) |
Used by 25 connectors
Connectors in the catalog that reference this concept.