Hotel Key Card Compatibility: Saflok, Onity, VingCard, Salto

Why hotel key cards are blanks, not pre-coded keys

A guest key card is not a fixed credential the way an office prox badge is. When a guest checks in, the front desk encoder writes that stay's data, the room number, the valid check-in and check-out window, and an audit sequence, onto the card's memory. The lock reads that data offline and decides whether to open. At check-out the data simply expires, and the card is wiped and re-encoded for the next guest. The property management and locking system owns the encoding logic; the card is just programmable memory.

That changes what compatibility means. You are not buying pre-coded room keys and you are not reproducing anyone's stay. You are buying compatible blank cards on the chip type your encoders and locks expect, so your own system can enrol them. This is why a hotel can reorder thousands of cards from an independent supplier and use them immediately: the blanks drop into the existing encoder, and the system does the rest. We supply blanks compatible with each platform's chip; the keys, and your property's security, stay in your hands.

Which chip does each lock platform use?

Nearly every current hotel platform sits on the 13.56 MHz smart-card family under ISO/IEC 14443 Type A, but the specific chip varies by brand and generation, and that is the spec you must match. Getting the chip family right is the difference between a card the encoder accepts and a coaster.

ASSA ABLOY Global Solutions (the VingCard line) ships modern locks on an AES-upgradeable 13.56 MHz guest card and on AES-secured 2K and 4K cards for higher-security and mobile-ready properties. Dormakaba Saflok and the related Confidant RFID locks also run 13.56 MHz smart cards on genuine, licensed silicon, most often the AES-secured card on current installs. Onity's HT and DirectKey RFID systems typically encode a legacy 1K card or a plain memory tag; older magstripe Onity locks are a separate, non-RFID story. Salto standardized on the AES-secured 13.56 MHz smart card for its electronic locks and wall readers. Among specialty brands, CISA hospitality locks use a legacy 1K card (the CT6 AERO/SMART line), Messerschmitt's HM1 system uses an ISO/IEC 15693 vicinity smart card, Häfele Dialock runs 13.56 MHz HF cards, MIWA spans both 125 kHz LF (EM4100 on PR-series locks) and 13.56 MHz HF smart cards on newer ALV2/LA hardware, and Hotek encodes a 3DES-authenticated memory tag. When in doubt, the encoder model and a single sample card tell you the exact chip.

• VingCard / ASSA ABLOY: genuine, licensed AES-upgradeable or AES-secured 13.56 MHz smart card
• Dormakaba Saflok / Confidant: genuine, licensed 13.56 MHz smart card, commonly the AES-secured card
• Onity HT / DirectKey: genuine, licensed 1K card or memory tag (13.56 MHz)
• Salto: genuine, licensed AES-secured 13.56 MHz smart card
• CISA: genuine, licensed 1K card (CT6 AERO/SMART)
• Messerschmitt HM1: genuine, licensed ISO/IEC 15693 vicinity smart card (13.56 MHz)
• MIWA: EM4100 at 125 kHz (PR-series) or genuine, licensed 13.56 MHz HF smart card (newer locks)

Disposable legacy blanks vs durable AES-secured blanks

Because the property re-encodes cards constantly, the right blank depends on how long the card lives in circulation. Disposable guest cards that are handed out and often not returned favor lower-cost chips, typically a genuine, licensed 1K card or memory tag, where the print finish and minimum order quantity matter more than chip security. Many properties print these in branded runs and treat them as semi-consumable.

Durable cards that stay in service for years, staff and master cards, room cards on properties that recycle keys, and any platform that mandates a secured chip, favor a genuine, licensed AES-upgradeable or AES-secured card with AES. These cost more per card but carry the encryption modern locks expect and survive thousands of read/write cycles. The decision is a procurement one: match the chip your locks require, then choose the durability and finish tier that fits your reuse rate and brand standard.

• Disposable, high-volume, often not returned: genuine, licensed 1K card or memory tag
• Durable, recycled, or security-mandated: genuine, licensed AES-upgradeable / AES-secured card (AES)
• Specialty platforms: match the exact chip (ISO 15693 vicinity card, 3DES memory tag, EM4100)
• Custom print and key-card sleeves are usually ordered in the same run

How does bulk supply and reordering work?

Hotel cards are a recurring consumable, so the supply logic is built around bulk reorder rather than one-off encoding. You confirm the chip your platform uses (from the encoder model or a sample card), choose a card finish, blank white, custom-printed, or your existing artwork, and order in case quantities. The cards arrive blank, and your front desk encoders write each stay's data exactly as before. There is no per-card programming on the supplier side for guest blanks, which is what keeps high-volume reorders fast.

For specialty or legacy locks, the chip is the gating detail. A MIWA PR-series lock needs a 125 kHz EM4100 card, while a newer MIWA reader needs a 13.56 MHz smart card; a Messerschmitt HM1 needs an ISO/IEC 15693 vicinity card specifically, not an ISO 14443-A card. Sending one current sample card with a reorder removes the guesswork, since the chip can be confirmed on receipt before a full run ships.

The cost angle versus OEM-branded cards

The chips themselves — the legacy 1K/4K card, memory tags, AES-upgradeable cards, AES-secured cards, and ISO 15693 vicinity cards — are genuine, licensed silicon available to any card manufacturer. An OEM-branded hotel card and a compatible blank on the same chip behave identically in your encoder, because the lock reads the chip and the data your own system wrote, not a brand printed on the plastic. That is why compatible blanks run at a fraction of OEM pricing while remaining fully functional in VingCard, Saflok, Onity, Salto and the specialty platforms.

The honest scope is worth stating. We supply compatible blank cards on the correct chip type; your property's own system enrols them with its keys, exactly as it would credentials ordered through the OEM channel, and on AES-secured platforms the security lives in your system's keys, which never leave your control. We are an independent supplier of compatible cards and are not affiliated with, authorized by, or endorsed by ASSA ABLOY, dormakaba, Onity, Salto, or any other manufacturer. For a property standardizing its reorder, the move is to confirm the chip, request a quote on the matching compatible blank, and validate one sample on your encoder before committing to a bulk run.