MIWA Hotel Key Cards

MIWA lock generations — ALV2, ALV3, V3HTM, AL5H and PiACK

MIWA Lock Co. (美和ロック) is a Japanese manufacturer founded in 1945, ISO 9001 and ISO 14001 certified, and the largest hotel-lock manufacturer in Japan. MIWA introduced the first offline electronic hotel locking system in 1981. The current generation taxonomy follows a clear progression: ALV2 (MIFARE-native), ALV3M / ALV3MA (BLE option), V3HTM / V3HTMA (BLE built in), AL5H (magstripe + smart-card hybrid for migration estates), plus the PiACK residential / SOHO line that adds FeliCa support and 2025-vintage Matter integration.

A typical MIWA hotel estate runs a single generation across the room-door fleet but may have a parallel V3HTM or AL5H deployment for staff areas, service entrances or amenity zones. The card SKU that ships to the property must match the room-door reader head; FeliCa-equipped staff credentials issued for VERSA-II controllers operate as a separate credential class but can be the same physical card if the property's encoder workflow supports both.

The table below maps the most common MIWA hotel locks to their default credential set, encoder pairing, and certification context. Verify lock firmware before locking in a chip — MIWA has historically refreshed reader heads to extend chip support without a model-name change.

Chip-family compatibility per generation

MIWA's chip support is wider than typical western hotel locks because FeliCa is a first-class credential on PiACK and VERSA-II. This section summarises which chip families drop in cleanly for which generation.

• MIFARE Classic 1K / 4K (ISO/IEC 14443A, 13.56 MHz) — the historical default across ALV2 and ALV3 reader heads. MIWA's spec language references "industry standard MIFARE 14443A technology". As with every Classic deployment, Crypto-1 is publicly broken; new estates should prefer DESFire.
• MIFARE Plus — supported on ALV3M / ALV3MA reader heads; useful as a Classic-compatible migration step where the encoder can issue Plus in SL1 mode.
• MIFARE DESFire EV2 / EV3 — supported on ALV3M / ALV3MA and V3HTM / V3HTMA. EV3 ships in EV2/EV1 backwards-compatible default per the NXP datasheet, so EV3 stock can serve an estate originally specified for EV2.
• FeliCa IDm — supported on PiACK II / III, VERSA-II, and on certain ALV2 firmware lines that expose the FeliCa antenna mode. This is uniquely MIWA — none of the dormakaba / ASSA ABLOY / SALTO platforms accept FeliCa natively. Suica, PASMO, ICOCA and other JR-issued transit IC cards can therefore be used as guest credentials in Japanese deployments.
• FKL FeliCa key card — MIWA's own FeliCa-based hotel and SOHO key card. Listed in MIWA's catalog and on Amazon JP as a replacement consumable. Common pairing with PiACK and FKALT residential locks.
• ISO/IEC 7811 magstripe — native only on the AL5H hybrid lock. New estates should not specify magstripe-only stock.
• 125 kHz proximity (HID Prox, EM4100) — not native on MIWA hotel locks. Appears only in custom integrations that pair a MIWA lock with a separate access-control reader head.

MIWA Card Issuing System — encoder and back-end stack

MIWA's encoder hardware is published as the "Card Issuing System" rather than under separate Gen I / Gen II model numbers; specifications are dated 2018. The encoder is a USB desktop unit measuring W105 × H65 × D40.2 mm, writes MIFARE Classic 1K / 4K credentials, and offers an optional BLE module for KEYMO mobile-key provisioning.

• MIWA Card Issuing System (USB encoder) — single SKU on MIWA's published catalog. USB to the front-desk PC. Supports MIFARE Classic 1K / 4K out of the box; BLE option enables KEYMO key provisioning to guest phones.
• MIWA card-issuing software — runs on the front-desk PC, drives the encoder, and bridges to the PMS via a configurable interface. MIWA does not publish a marketed back-end product name in English; the software is referenced simply as "MIWA ALV2 Card Issuing System" in PMS-integration documentation (e.g. RoomKeyPMS).
• Encoder firmware revisions over time have extended chip support from Classic 1K only to Classic 4K and Plus / DESFire. Verify encoder firmware before ordering DESFire EV3 stock for an ALV3-era property.
• Guest card, staff card, emergency card and all-in-one (master) card types are issued through the same encoder workflow. Card class is set in the issuing software at encoding time.

Mobile Access — KEYMO BLE app, Matter, partner mobile-key platforms

MIWA's mobile-access track has two threads: a first-party KEYMO BLE app for hotel deployments on ALV2 (BLE option) and V3HTM / V3HTMA, and a residential / SOHO smart-lock track via PiACK that picked up Matter support in 2025 through a SEALSQ partnership for the PiACK HOME PG SKU.

• KEYMO — MIWA's first-party hotel mobile-key app, available for iOS (16+) and Android. Listed in the Google Play Store as `com.miwa.alv2ble`. Requires ALV2 with BLE option or V3HTM / V3HTMA hardware.
• PiACK HOME PG with Matter (2025) — SEALSQ announced "Japan's first Matter-compatible smart lock" in collaboration with MIWA, using SEALSQ's PKI Root of Trust for cryptographic identity. This is a residential / SOHO product but signals MIWA's direction on credential interoperability.
• OpenKey × MIWA — third-party mobile-key partnership announced in March 2018, integrating OpenKey's mobile-key platform with MIWA hotel locks for properties already on OpenKey from earlier dormakaba or VingCard relationships.
• UniKey × MIWA — earlier touch-to-open smartphone partnership announced in 2014; still referenced in MIWA's catalog but largely superseded by KEYMO and OpenKey.
• OpenWays — historical mobile-key integration listed on MIWA's own site; less actively promoted than KEYMO or OpenKey.
• Aavgo — hotel-tech integration partner with a published MIWA pairing for digital check-in workflows.
• Apple Wallet and Google Wallet — not confirmed as native MIWA support as of May 2026. Properties wanting wallet keys should confirm directly with MIWA; KEYMO and OpenKey cover the BLE mobile-key surface.

PMS integration — Oracle OPERA, Tap Co., Temairazu, RoomKeyPMS

MIWA integrates with both western (Oracle OPERA, RoomKeyPMS) and Japanese (Tap Co., Temairazu) PMS platforms. The Japanese-PMS integration ecosystem is uncommon in English-language MIWA coverage and is the procurement detail most often missed by competitor pages.

• Oracle OPERA — supported via the MIWA ALV2 / ALV3 card-issuing software interface; pairing common at international-brand hotels in Japan and APAC.
• Tap Co., Ltd (Japanese PMS) — 39-year-old Japanese hotel PMS operator with a published MIWA integration. Common pairing in Japanese-domestic hotel chains.
• Temairazu — Japanese channel manager and PMS that integrates with MIWA-equipped properties; widely deployed in Japanese ryokan and limited-service hotels.
• RoomKeyPMS — published MIWA ALV2 card-issuing system interface; common pairing in independent hotels in North America and Canada that run MIWA.
• Aavgo — digital check-in platform with a published MIWA integration for keyless arrival workflows.
• Cloud-based PMS platforms typically bridge via the front-desk PC running the MIWA card-issuing software locally; the software brokers the PMS reservation to the USB encoder.

Security posture — no public CVE, ANSI A156.25 Grade 1, ISO 9001 / 14001

MIWA's security posture is unusually well-credentialled for a hotel-lock manufacturer of its scale. As of May 2026 there are no public CVE entries in NVD or cve.org for MIWA Lock Co. The lock hardware is ANSI A156.25 Grade 1 electronic mortise-lock certified, and MIWA's Japanese factories are ISO 9001 (quality) and ISO 14001 (environmental) certified. The 2025 PiACK HOME PG launch added a SEALSQ Root-of-Trust PKI layer for the Matter smart-home credentials track.

MIWA publishes a Security Statement page that documents its responsible-disclosure and security-update philosophy. There is no Saflok-style public disclosure incident in MIWA's history — the closest analogues in the hotel-lock space (Saflok / Unsaflok CVE-2024-29916, Onity HT-series 2012 Brocious disclosure, SALTO ProAccess SPACE 2019 CVE cluster) have no direct MIWA equivalent.

For card procurement: the absence of a public CVE is a favourable trust signal but not a substitute for standard validation. New estates should still standardise on MIFARE DESFire EV2 or EV3 (where the lock supports it) to retire the industry-wide Crypto-1 surface that affects MIFARE Classic 1K / 4K across every vendor.

Common field failure modes

Field failures on MIWA estates follow a predictable pattern. Understanding where the break usually happens shortens the troubleshooting cycle and prevents unnecessary card replacements.

• Card held too far from the reader. MIWA documents a short authentication distance: "place the card within half an inch of the reader and the lock will open." Wallet-thickness, lanyard wear and oblique presentation can all push the card outside the antenna's reliable range.
• FeliCa-only credentials rejected on ALV2 firmware lines that do not have the FeliCa antenna mode enabled. Reader-head firmware update via MIWA service rather than a card change is the fix.
• Encoder rejects DESFire EV3 stock on a Card Issuing System with older firmware. Verify the encoder firmware was upgraded to extend chip support from Classic-only to Plus / DESFire before ordering.
• AL5H hybrid lock falling back to magstripe-only despite the smart-card chip being present. Check the lock's RFID-module enable flag in the locking plan — IR programming via MIWA's documented "15-20 second" workflow restores RFID-first behaviour.
• MIFARE Classic sector-key mismatch after a MIWA card-issuing software reinstall. Re-export the site key from the software and re-initialise the encoder before issuing a test card.
• KEYMO app fails to provision a key against a V3HTM lock. Most often the BLE option on the encoder is not installed or the property's KEYMO subscription is not yet active for the specific lock.

Card material and thickness constraints

MIWA reader heads tolerate standard hotel card stock without surprises. The short read distance documented by MIWA does, however, make material and antenna geometry more sensitive than typical western locks.

• Standard ISO/IEC 7810 ID-1 thickness (0.76 mm ± 0.08 mm) is the safe default across ALV2, ALV3 and V3HTM reader heads.
• Thicker cards (1.0–1.2 mm) — premium PVC, wood-effect, recycled-content cards — read reliably on ALV3 and V3HTM. ALV2 reader heads can be marginal at thicknesses above 0.9 mm due to the narrower antenna tolerance.
• Bamboo and wood cards with a MIFARE DESFire EV2 or EV3 inlay read well on V3HTM / V3HTMA; pilot a production-thickness sample before committing to a full order, especially on slim-type ALV2 doors.
• Metal-edge and anti-metal cards are not recommended for MIWA hotel locks; the shielding detunes the antenna and produces intermittent reads given MIWA's already short authentication distance.
• MIWA FKL FeliCa key cards are sold under MIWA's own SKU; substitute FeliCa cards may have different antenna geometries that read at shorter ranges.
• Dual-interface cards (magstripe + RFID) are required for AL5H hybrid migrations; the magstripe track format must match MIWA's documented layout for the AL5H reader head.

What to validate before scaling

A MIWA pilot should exercise the chip, the reader-head firmware, the encoder firmware, the card-issuing software and the PMS connector together. Scaling before all five are proven is the most common source of pilot regret.

• Test one baseline MIFARE Classic 1K card on at least one room-door lock plus, if applicable, one back-of-house V3HTM lock before approving a card SKU for the estate.
• If DESFire EV3 is the target chip, confirm both the reader-head firmware and the Card Issuing System encoder firmware support DESFire before ordering bulk stock.
• Run a full check-in, extend, re-encode and cancel cycle on a live PMS reservation through the MIWA card-issuing software to surface PMS-connector edge cases.
• If FeliCa is in scope for the estate, validate FKL FeliCa cards and any expected transit-card IDm reads separately — FeliCa antenna behaviour is independent of MIFARE behaviour on the same reader head.
• Plan a small (100–200 card) first production batch before scaling to the full property order; most field failures show up in the first 30 days of live issuance.

FAQ