Mobile key is the answer to the issuance-and-revocation question. PIN is the answer to the what-if-they-do-not-have-a-phone question.

Publicado em: abr 22, 2026

Mobile Key vs PIN Access

Mobile Key vs PIN Access

A distributor walks into our factory floor almost every week with the same question framed as a tiebreaker: "Mobile key or PIN access — which one do I put on the lock?" The question sounds like a feature-versus-feature comparison, and most catalogs answer it that way, with two columns of icons and a "winner" badge at the bottom. That framing is the wrong place to start. Mobile key vs PIN access is not a feature comparison between two credential media on the same door; it is a lifecycle comparison between two distinct ways of issuing, carrying, revoking, replacing, and auditing identity at the door. The buyer who asks "which is better?" needs to be walked back one step, to "which is more honest about who has the authority to issue a credential, who has the authority to revoke it, and which audit trail survives the morning after a tenant disputes entry?" That is the editorial position this article takes, and it is the only position a manufacturer who has shipped both lanes into the same 79-model catalog is entitled to take.

The question behind the question

When a property manager asks for "mobile key" they are usually asking for a single thing: a way to send a tenant or guest a credential that arrives on their phone, lets them in, and then disappears. When a property manager asks for "PIN access" they are usually asking for a different single thing: a fixed string of digits a person types on a keypad, that the manager can change by hand, that travels without a phone. The two requests are not opposite. They are responses to different problems the property manager has lived with. Mobile key is the answer to the issuance-and-revocation question. PIN is the answer to the what-if-they-do-not-have-a-phone question. Pretending one replaces the other erases the problem each one actually solves.

That is the editorial position. It is not the marketing position. A marketing position would pick a lane. A manufacturer who ships both lanes into a 24-hotel-lock line, an 18-keypad line, a 9-RFID line, a 37-fingerprint line, and a 79-model overall catalog, has no business picking a lane. The honest position is that the two lanes are not interchangeable on the same door; they cover different points in the credential lifecycle; and the right configuration is almost always both lanes on the same lock, governed by who is allowed to issue which lane to whom.

What "mobile key" actually names

"Mobile key" in a B2B conversation usually refers to an app-based unlock delivered over Bluetooth on the door side, with the credential issued through a phone-resident credential wallet and revoked by the issuing administrator's app or, in hotel-class installs, by the hotel PC software. The catalog references talk to three platform families when the conversation turns to the app layer: TTLock, Tuya, and Doodle are the three app platforms that our app-capable locks bind against, and the per-model binding is something each catalog entry confirms on its own dated product page. We do not in this article assert that any specific SKU is on TTLock, Tuya, or Doodle. That confirmation belongs to the dated product page of the SKU under discussion, and the rule of thumb the buyer should hold is that the binding is per-SKU and per-project, not per-category.

A "mobile key" therefore has four properties that are easy to lose sight of once the marketing icons take over. First, the credential lives in an app, and the app belongs to a tenant of the phone — not to the lock, not to the building, not to the manager. Second, the manager holds the issuance authority on the issuing side, but the carrying authority belongs to the phone's user after they accept the credential. Third, the revocation authority is the issuer's, exercised through the same admin surface that issued the credential; this is the property that makes mobile key structurally good at high-turnover doors. Fourth, the audit record on the lock side is automatic — every time a credential opens a door, the door records which credential was used at which timestamp, and the lock's audit buffer is what carries the day when the phone is lost, stolen, dead, or simply out of range.

What "PIN access" actually names

"PIN access" refers to a numeric code, typically four to eight digits, entered on a physical or capacitive keypad on the lock. The code is stored in the lock's local memory against a user slot, a validity window, or a one-time-use flag. The code is issued by an administrator either directly on the lock, through the same app the mobile-key lane uses, or — on the hotel-class installs — through the hotel PC software with the keypad on the door acting as the secondary credential surface for staff and back-of-house doors.

A PIN has four mirror properties to the mobile key, and they are the reason the conversation refuses to die. A PIN lives on the lock, not on the tenant's phone. The lock owns the credential; the tenant owns a piece of memorized information. The revocation authority is also the issuer's, but the carrying authority is shared — the issuer cannot physically take the PIN back, they can only overwrite it in the lock, which means the gap between revocation and over-the-air overwrite is the gap that produces the worst PIN incidents. The audit record on the door is also automatic — every PIN entry that succeeds is logged against the user slot, and every wrong-attempt counter increments is logged, which is the property that makes PIN access structurally good at low-friction staff doors.

Why the question usually gets asked the wrong way

The wrong framing is: "Which credential is more secure?" The honest framing is: "Which credential is more honest about who issued it, who can revoke it, who can reissue it tomorrow, and which audit trail survives a dispute?" The first question yields a feature comparison with one winner. The second question yields a configuration question with no winner and a clear answer: both lanes, governed, on the same lock.

The reason the wrong framing persists is that two credential types are easy to compare as objects — one is a piece of paper you do not carry, the other is an app on a phone you do — and they are hard to compare as lifecycles. A lifecycle comparison has to talk about issuance, carrying, revocation, replacement, audit, decommissioning, and what happens at every stage when the people in the building are not the people the lock was designed for. None of those stages are visible on a marketing checkbox.

The honest comparison, lane by lane

Issuance. A mobile key issuance is one-sided: the administrator generates a credential through an admin app or a property-management software and pushes it to a phone-resident wallet. The tenant accepts it. The lock never sees the issuance event; it only sees the unlock event when the tenant arrives. A PIN issuance is two-sided at the door: the administrator sets the code, the tenant receives it out-of-band (text message, paper slip, voice), and the tenant has to type it on the keypad. The lock sees both events — the write to the slot and the entry of the code.

Carrying. A mobile key is carried on a phone, with all of the phone's failure modes: dead battery, lost phone, broken screen, operating-system upgrade that wipes the wallet, employee turnover where the phone stays with the employee. A PIN is carried in memory, with all of memory's failure modes: forgotten code, written-down code, shared code, code passed to the next tenant by word of mouth.

Revocation. A mobile key is revoked by the administrator deleting the credential from the issuing app's user record. The next time the phone arrives at the door, the lock rejects the unlock. The revocation is exact and immediate. A PIN is revoked by the administrator overwriting the slot in the lock — and the overwrite is exact on the lock side, but the tenant may still remember the old code. The gap between "revoked on the lock" and "tenant no longer holds the code" is the structural vulnerability of PIN access.

Replacement. A mobile key replacement is identical to an issuance; the administrator sends a new credential to the same phone or to a different phone. A PIN replacement is also identical to an issuance — the administrator sets a new code and communicates it out-of-band. The two lanes are symmetric here. The asymmetry returns at the next property manager turnover.

Audit. Both lanes produce audit records on the lock side, automatically, with no user action. The mobile key audit record carries the credential ID; the PIN audit record carries the user slot ID. Both can be pulled by the administrator. For the SLK-9936S hotel-class lock, the catalog spec block notes an audit/event-record buffer of up to 1,000 records — a number we treat here as documentation of one SKU and one SKU only, with the explicit rule that the same figure is not portable to any sibling model. Every other SKU's audit-buffer depth, audit-pull cadence, and audit-retrieval interface is a per-SKU figure the buyer confirms against the dated product page.

Decommissioning. A mobile key decommissioning is the deletion of every credential issued from a property-management software or app on the day the tenant leaves. The phone may still carry an expired credential, but the door rejects it. A PIN decommissioning is the overwrite of every code slot the tenant held, plus the rotation of any one-time-use code flags the lock carried. The phone carries the credential until the issuer revokes it; the lock carries the code until the issuer overwrites it.

The two lanes are not the same at any stage. They are complementary at every stage.

What the mobile-key lane does that the PIN lane cannot

The mobile-key lane is structurally better at three jobs, and naming them honestly is the only way to keep the comparison from collapsing into a marketing shootout.

First, mobile key is structurally better at high-turnover doors. A serviced apartment, a short-stay rental, a coworking hot desk, a hotel room: these doors admit a different person every one to seven nights. Mobile key issuance scales to dozens per day at one front desk; PIN issuance at the same cadence requires the manager to write down, text, or print the code each time, and the gap between "code written" and "code typed at the door" is the gap that produces the most common PIN incident.

Second, mobile key is structurally better at audit clarity for the dispute. When a tenant disputes a door entry — "I never went in that day" — the mobile key audit record carries the credential ID and the timestamp. The credential ID maps to the tenant's wallet record on the issuing app, which the manager can pull. A PIN audit record carries the user slot ID; the user slot ID maps to a number, and the number maps to a person only if the manager kept the slot-to-person register up to date. The PIN record is honest; the human-side register is not always.

Third, mobile key is structurally better at revocation under time pressure. When a tenant is evicted, dismissed, or denied access for cause, the manager's next admin action is the same in both lanes: delete the credential, change the code. In the mobile-key lane, the deletion is immediate. In the PIN lane, the change requires the manager to be physically at the lock or to push the change through the admin app, and the lock has to receive it. The gap between "decision to revoke" and "lock-side revocation applied" is the gap that produces the second most common PIN incident.

What the PIN lane does that the mobile-key lane cannot

The PIN lane is structurally better at three other jobs, and they are the three jobs the mobile-key marketing rarely admits.

First, PIN is structurally better at doors where the carrying party does not own a phone. A maintenance contractor, a cleaning service, a once-a-week vendor, a child, an elderly resident, a guest who walked out the door with a dead phone: these carrying parties either do not have a phone, have a phone they will not install the manager's app on, or have a phone that will be in another room when the door needs opening. PIN works without a phone. The marketing position that "everyone has a smartphone" is empirically true at a population level and operationally false at the building level.

Second, PIN is structurally better at doors where the manager's issuing authority is not the same as the carrying authority. A back-of-house staff door, a maintenance closet, a server-room entry, a stockroom: the manager wants the credential to live on the lock, not on a phone that may walk out of the building at the end of the shift. The lock owns the PIN. The phone owns the mobile key. The right credential for a fixed-role door is the one the door owns.

Third, PIN is structurally better at failure-mode recovery. When the phone is dead, lost, stolen, or in for repair, the mobile key is unreachable. When the lock's app platform is offline — a building network outage, a hotel network cutover, an app-platform service incident — the mobile key is unreachable. PIN access survives both failures. The PIN lane is the lane that holds when everything else has failed. The most disciplined property managers we see treat PIN as the belt and the mobile key as the braces, not the other way around.

The honest framing is "both, governed, on the same lock"

The honest answer to the distributor's question is not "mobile key or PIN." It is "both lanes, governed, on the same lock, with a written rule for who gets which lane under which circumstances." The 18-keypad catalog line carries locks with PIN as the primary credential lane and, on a subset of those models, mobile key as the secondary lane. The app-capable models in the catalog — which bind to one of the three app platforms TTLock, Tuya, or Doodle per their dated product page — carry mobile key as the primary lane and PIN as the secondary lane. The choice of primary lane is set by the property's credential population and turnover, not by the lock's category.

A short-stay serviced apartment runs mobile key as the primary lane for guests and PIN as the secondary lane for housekeeping and maintenance. A long-stay residential property runs PIN as the primary lane for residents and mobile key as the secondary lane for guests and family. A coworking space runs mobile key as the primary lane for member access and PIN as the secondary lane for one-off visitors and after-hours staff. A boutique hotel runs mobile key as the primary lane for guests and PIN as the secondary lane for back-of-house. The configuration rule is the same at every property type; what changes is which lane is primary for which population.

Why the catalog exposes the choice, not the answer

The 79-model catalog exposes the credential-lanes available on each model — fingerprint, passcode, RFID/IC card, mechanical key, app/Bluetooth, remote control, 3D face on a few models, hotel PC software, camera/cat-eye, 4G models — and asks the buyer to check the model’s published specification which lanes are present, which lane is primary, and what the issuance-and-revocation interface looks like in practice. The catalog does not pick a lane because the catalog cannot pick a lane without falsifying the operating reality of the property. The buyer picks the lane by writing down the property's credential populations, their turnover rates, their phone ownership, their failure-mode tolerances, and their audit-dispute history. The lock delivers the lanes the property has specified.

This is also the editorial position the article takes on the common claim that mobile key is "the future" and PIN is "the past." That claim is empirically wrong on a 79-model catalog that ships both lanes into 80+ countries and 10+ years of production history. PIN is not the past; PIN is the lane that survives the failure of every other lane. Mobile key is not the future; mobile key is the lane that scales issuance and revocation at high cadence. The honest framing is "both, governed." The future of the catalog is the lock that carries both lanes with a written governance rule, not the lock that carries only one.

The platform-boundary question, honestly

When the conversation turns from credential media to app platform, the buyer hears three names and assumes there is a winner. There is no winner. TTLock, Tuya, and Doodle are three different platform families with different admin surfaces, different integration surfaces, and different credential-wallet behaviors. The per-SKU binding to one of those three platforms is a per-SKU and per-project confirmation that the buyer routes to the dated product page. The cross-platform credential portability — can a TTLock-issued credential open a Tuya-bound lock? — is a per-platform question that the buyer routes to the platform documentation, not to the lock spec sheet.

The honest editorial position on the platform question is that the platform choice is downstream of the lane choice. Decide whether mobile key is the primary lane. Then decide which platform's admin surface fits the property's existing credential-issuance workflow. Then check the model’s published specification that the lock the buyer is about to specify actually binds to that platform at the firmware revision the buyer is about to order. The reverse order — pick the platform first, pick the lane second — produces configurations that do not survive a property handover.

A note on what neither lane does

Neither lane, on its own, replaces a written credential policy. A property that hands out mobile keys without a written issuance register is a property that does not know who has access on day 31. A property that hands out PIN codes without a written slot-to-person register is a property that does not know who used which code on day 31. Both lanes produce audit records on the lock side, but the lock-side audit is only as honest as the human-side register that ties the audit record to a person. The credential policy — who is authorized to issue, what the validity window is, how the revocation is triggered, how the audit record is reconciled — is upstream of both lanes, and a buyer who specifies a lock without specifying a credential policy is specifying a lock whose audit trail will not be readable the morning after a dispute.

That note is also the editorial position this article takes on the deeper version of the distributor's original question. The question is not "mobile key or PIN." The question is "what is the credential policy our property will run, and which lanes does that policy need on each door?" A lock with two lanes is not a luxury. A lock with two lanes and no credential policy is an audit risk. A lock with one lane and a credential policy is a configuration. A lock with two lanes and a credential policy is the configuration the catalog exists to serve.

An illustrative configuration across a small mixed-use estate

Consider a 120-door mixed-use estate running a hotel annex on the upper floors, a serviced-apartment block on the middle floors, a coworking floor on the lower floors, and a back-of-house staff corridor connecting all three. The estate owner asks the distributor for a single credential-lanes answer, and the distributor who has read this article answers it as a configuration, not a tiebreaker.

The hotel-annex doors run mobile key as the primary lane, bound to the property's existing hotel PC software, with PIN as the secondary lane for housekeeping and engineering. The serviced-apartment doors run mobile key as the primary lane for guest turnover and PIN as the primary lane for long-stay residents. The coworking-floor doors run mobile key as the primary lane for member access, with PIN as the secondary lane for one-off visitors and after-hours staff. The back-of-house staff corridor runs PIN as the primary lane for every credential, because the carrying authority for a staff corridor is the lock, not the phone, and the audit trail the corridor needs is the lock-side audit record, not a per-phone wallet. The mechanical key override remains on every door — the catalog includes it as standard, the architectural reason is independent of the credential-lanes question, and the rule the buyer inherits is that the mechanical override is a separate design conversation from the mobile-vs-PIN question.

The configuration the estate runs at delivery is not "mobile key or PIN." The configuration the estate runs at delivery is "mobile key and PIN, on every door, governed by a written credential policy that names which lane is primary for which population, who is authorized to issue which lane, and what the audit-record reconciliation cadence is." The lock delivers the lanes. The estate delivers the policy. The audit trail survives because both parties wrote their part down.

What the factory floor tells you

A factory that has shipped both lanes into the same catalog for a decade will tell you three things a marketing shootout will not.

First, the lock that carries only one lane is a lock that has decided the property's question for the property. The buyer who specifies a single-lane lock is a buyer who has decided the property's credential policy before writing the policy down, and that is the wrong order. The catalog exposes both lanes because the catalog has watched properties reverse the decision.

Second, the failure mode a property manager complains about is almost never the lane's fault. It is the credential-policy fault. The PIN that was not overwritten fast enough is not a PIN-lane problem; it is a written-slot-register problem. The mobile key that was not revoked at the right time is not a mobile-key problem; it is a written-issuance-register problem. The lane is a delivery mechanism. The policy is the operating discipline. The lane failure gets blamed first because the lane failure is visible.

Third, the audit trail that survives a dispute is the audit trail that was reconciled against a written human-side register before the dispute arrived. The lock's audit record is honest. The manager's register is the variable. The buyer who treats the lock's audit buffer depth as the audit-trail depth is a buyer who has not yet been in a dispute. The buyer who treats the manager's register discipline as the audit-trail depth is the buyer whose configuration survives the morning after.

Where the buyer goes from here

The buyer who has read to this point has three next moves, not one. The first is to write down the credential populations on the property — guests, residents, staff, contractors, family, one-off visitors — and the turnover rate for each. The second is to name which lane is primary for each population, on each door. The third is to write the credential-issuance register, the credential-revocation register, the slot-to-person register (for PIN), the credential-to-person register (for mobile key), and the audit-record reconciliation cadence. None of these is a lock decision. All of them are decisions the property manager makes before the catalog enters the conversation.

When those three documents exist, the catalog enters as a confirmation exercise: which lock delivers mobile key on which app platform — TTLock, Tuya, or Doodle — recorded in the model specification; which lock delivers PIN as a primary lane with what keypad type, what slot count, what validity-window interface; which lock carries both lanes with what the issuance-and-revocation admin surface looks like in practice; and which mechanical override profile the lock carries, as a separate decision from the credential-lanes question. The distributor's job at that point is to source a lock that matches the policy, not a lock that picks the policy.

For the buyers who want the architectural vocabulary of the hotel-class system before they specify a single credential lane, the cluster pillar on hotel-system architecture (/blog/hotel-smart-lock-system-architecture) walks the four-component operating system — lock hardware, card medium, encoder, hotel PC software, with an optional centralized database above it — that any hotel-class credential-policy decision has to sit inside. For the buyers who are choosing between mobile key and RFID card rather than between mobile key and PIN, the sibling article on Mobile Key vs RFID Key Card walks the same lifecycle comparison for that lane pair, with the same honest framing and the same documentation discipline. For the buyers who are choosing between fingerprint and RFID for a hotel door, the sibling on Fingerprint vs RFID for Hotels walks the same editorial position through a different pair. The cluster shares the position: the lane is a delivery mechanism; the policy is the operating discipline; the catalog delivers the lanes the policy has specified.

The closing question is not "mobile key or PIN." The closing question is "what is your credential policy, and which lane is primary for which population on which door?" Bring the policy. The factory will confirm the lock.

O seu carrinho
A sua experiência neste site será melhorada se permitir cookies Política de cookies
Chat on WhatsApp