Troubleshooting guide
Hotel key card not working?
A failed hotel key card can involve its permissions, encoding, physical condition or the door. Use these possible causes and five checks to narrow the investigation; confirm the installed system’s procedure before taking action.
Published · Updated · For front-desk, engineering and procurement teams
The short answer
RFID chips use electronic memory, not magnetic-stripe storage. Some hybrid cards also have a separate magnetic stripe. A failed read can have several causes, including permissions, encoding, card damage or the lock. Compare approved credentials and follow the installed system’s instructions to identify the cause.
Staying at the hotel? Start with the front desk. Ask staff to check your stay and card after their normal identity verification, and tell them which door failed and what the reader did. Leave lock servicing and card testing to authorised hotel personnel. The rest of this page is written for staff.
Narrow the investigation
Seven possible causes to investigate
These possibilities are not ranked by frequency. A failed tap or swipe is an observation, not a diagnosis; confirm the cause with authorised, controlled comparisons.
| Cause | How to tell | Affects | What to do |
|---|---|---|---|
| Wrong chip for the lock’s current security mode | New stock fails across a wing or the whole property while older approved cards still work; often follows a lock firmware or security update, or a phased lock upgrade. | RFID | Confirm which credential the installed system now expects. A lock updated to require Ultralight C or DESFire will reject MIFARE Classic 1K stock that used to work. Check the chip guide and the lock compatibility hub, then test samples in your own locks before reordering. See which chip your locks need and the lock compatibility hub. |
| Encoded validity has passed | Card worked earlier in the stay, then stopped around the check-out hour or after an extension was entered in the PMS. | RFID and magstripe | Confirm the stay and re-encode with the new validity under the hotel’s procedure. Check how the installed system applies extensions and update the credential if required. |
| Encoding error at check-in | The card never worked, not once, since it was issued. | RFID and magstripe | Re-encode after confirming room and permissions. If a second card from different stock also fails, record the workstation and encoder for engineering. |
| Card physically worn or cracked | Intermittent: opens on the third or fourth tap, or only when pressed flat against the reader. | RFID and magstripe | Set damaged cards aside for assessment. Visible wear alone does not prove an internal antenna fault. |
| Low lock battery or reader fault at one door | Every card fails on this one door; the lock shows a low-power warning, an unusual LED pattern or no response. | RFID and magstripe | Record the indicators and ask engineering to check the lock, permissions and approved credentials using the model’s instructions. |
| Dirty or worn read or write head | Same card works on other doors but fails on one; or cards from one front-desk workstation fail on first use across many rooms. | Mainly magstripe | Inspect and clean the reader or encoder as directed by its manufacturer; compare results from an approved workstation. |
| Genuine demagnetisation or stripe wear | Swipe fails on every door and every reader; reissue rates creep up across the property. | Magstripe only | Check the stripe and re-encode under hotel policy. If the issue recurs, investigate the card, encoding and reader before concluding that the stripe is worn. |
Card or lock?
Five-step front-desk check
Use this sequence to collect evidence about the card, permissions, encoder and lock. Change one variable at a time and keep guest names and active credential data in the hotel’s internal case record.
-
Test the card on a second authorised door
Where hotel policy permits, try another door the guest is authorised for, such as a pool or gym entrance, or an approved test door. Compare the results with the credential’s permissions and with another approved credential at the affected door; neither result alone identifies the fault. Do not try cards at rooms or facilities outside the approved test scope.
-
Re-encode rather than replace
After confirming the stay, room and permissions, re-encode the card. If the installed system requires an update, re-encode according to its instructions and retest. Replacing a physically sound card immediately may not resolve a permissions or door issue.
-
Issue a second card from different stock
If the re-encoded card still fails, take a card from a different box or batch. Record the outcome and compare the two cards’ specifications and settings. A second failure can also involve permissions, the encoder or the lock.
-
Inspect the card for physical damage
Look for creases, cracks, delamination or other damage. Set suspect cards aside; their appearance alone cannot confirm an internal antenna fault.
-
Check the lock before sending a third card upstairs
If authorised credentials fail at one door, record the symptoms and hand the issue to engineering. Check permissions, power and the reader using the installed model’s instructions.
Validity periods and indicator meanings are system-specific. For example, dormakaba’s Ambiance lock guidance distinguishes programmed expiry, permissions and lock status. Apply the documentation for the actual installed model, not a universal check-out time or LED rule.
Before you re-encode
Confirm what the card should be allowed to do
- Verify the assignment. Confirm the room, stay dates, approved access areas and whether a room move, extension or replacement card was recently issued. Follow the property’s process for updating credentials.
- Record the response. Note the affected door, time, visible damage and the exact reader lights or sounds. Ask whether the card ever worked; a card that never worked points to encoding or chip mismatch, while a card that worked and then stopped points to validity, wear or the door.
- Use an approved comparison. Compare a current, approved test credential at an authorised test door. A successful read at one door does not establish permissions or compatibility at every door.
Separate the technologies
Why RFID cards cannot be demagnetised
A magstripe card stores data as magnetic polarity in a band of ferromagnetic particles. A strong enough external field re-orients those particles and the data is gone. That is demagnetisation, and it is real. How easily it happens depends on coercivity: Zebra explains magnetic-stripe coercivity and why HiCo stripes resist stray fields better than LoCo. Even so, a failed swipe alone does not prove demagnetisation; a dirty read head or a worn stripe produces the same symptom.
An RFID key card works on a different principle. It holds a silicon chip connected to a thin antenna loop, both laminated inside the card body. The reader emits a field at 13.56 MHz (or 125 kHz for low-frequency systems), which induces enough current in that loop to power the chip, and the chip answers with its credential. NXP’s MIFARE Classic EV1 data sheet, for example, describes EEPROM memory and a coil antenna. The RFID chip does not use magnetic-stripe storage; a hybrid card may also have a separate stripe.
Physical damage can affect an RFID card’s antenna or other components. Set visibly cracked, bent or delaminated stock aside for assessment; appearance alone cannot confirm an internal fault.
A phone is not a definitive card tester. Android documents that MIFARE Classic support is optional. A negative phone result does not establish low frequency or damage, and a generic NFC response does not identify the exact chip or prove hotel compatibility. For procurement, use the chip identification guide and obtain the system provider’s specification.
Stop it from recurring
Recurring issues to investigate
Mismatched chips across a security update or phased lock upgrade. Hotels that replaced locks wing by wing, or enabled a stronger security mode on part of the estate, often run two credential configurations at once. A card encoded for MIFARE Classic 1K will not open a lock that now expects Ultralight C or DESFire, and vice versa. If failures cluster by floor or wing, compare the configurations and permissions before deciding on a cause. The chip identification guide walks through how to tell which chip your locks want, and the lock compatibility hub lists commonly used pairings by system; both are reference starting points to confirm with test samples in your own locks.
Cards treated as single-use. An RFID card survives many re-encodes. Where hotel policy and system requirements permit, collecting and reusing sound cards can reduce replacement demand. The cost guide works through the arithmetic and quantity planning shows how returns change the annual order.
Worn stock still in rotation. Set visibly creased or delaminated returned cards aside for assessment instead of reissuing them.
Other operational checks include:
- Put front-desk encoders on a cleaning schedule. If failures cluster by issuing desk, compare settings and equipment, then inspect and clean according to the manufacturer’s instructions.
- Wipe cards between guests at beachfront and high-humidity properties. Use cleaning methods approved for the card and reader; inspect returned cards for residue and damage.
- Re-key extended stays before the original check-out hour, not after. Check how the installed system updates credentials when reservations are extended or linked.
- Review LoCo stripe stock if you are still on it. Review stripe condition, encoding and reader performance when reissues increase. Confirm that the encoder and locks are configured for the coercivity you plan to order.
Prepare a useful handover
Give engineering or the system provider a clear test record
- Equipment: exact lock model, encoder model and software version, and any security mode or firmware update applied since the last card order.
- Pattern: affected doors, times, card batches and issuing workstations; include what still works.
- Comparison: approved stock and test credentials used, with the outcome of each authorised check from the five-step sequence above.
- Follow-up: the manufacturer’s next diagnostic step and who is responsible for it.
Engineering should interpret power warnings and carry out reader or lock maintenance using the model’s service instructions. Avoid repeated issuance or bulk replacement until the evidence supports the next step.
For replacement-card planning, see how to identify the credential your locks need. Terms such as coercivity, UID and credential configuration are defined in the glossary.
Before a replacement order
Validate the credential on your installed system
Confirm the card specification with your lock-system provider, including any security mode enabled since the last order, then agree a sample test using the hotel’s authorised encoder and representative test doors. Keep print and material approval separate from credential compatibility. Share equipment models and a non-sensitive summary; do not send guest data, active access credentials or security secrets.
Frequently asked questions
Can a phone demagnetise a hotel key card?
The RFID chip stores data electronically, not on a magnetic stripe. A hybrid card may also contain a stripe, which can be affected by magnetic fields. Ask hotel staff to identify the technology and investigate the actual failure.
Can RFID hotel key cards be demagnetised?
The RFID chip uses electronic memory rather than magnetic-stripe storage. A hybrid card may also have a separate magnetic stripe. For an RFID failure, check permissions, encoding, card damage and the lock with authorised equipment.
How do you fix a demagnetised hotel key card?
Take it to the front desk to be re-encoded. That writes fresh data to the stripe in seconds and is the only reliable fix. Rubbing the card, wiping it on fabric or the widely shared trick of running it through your hair do nothing; none of them restore encoded data. If it fails again, staff should investigate the stripe, encoding and reader rather than assume the cause.
Why did my hotel key card stop working after one day, and do cards always expire at 11 a.m.?
The credential’s validity or permissions may need updating, but other card or lock issues are possible. There is no universal expiry time. Staff should check the reservation and the installed system’s procedure for extending access.
How many times can a hotel key card be re-encoded?
An RFID key card can typically be re-encoded many times; the practical limit is physical wear on the card body rather than the chip, because chip memory tolerates far more write cycles than a card survives in circulation. Magstripe cards degrade faster because each swipe abrades the stripe. This is why RFID cards suit reissue programmes and magstripe cards are usually treated as consumable.
Our new cards do not work in some doors. What went wrong?
The chip family, credential configuration, permissions or lock may need investigation. Hotels that upgraded locks in phases, or applied a security update to some locks, often run two configurations at once, for example MIFARE Classic in one wing and Ultralight C, Ultralight EV1 or DESFire in another. A card encoded for one will not open the other. Check what each wing expects with the system provider before reordering; a sample test in the actual doors catches this before a full production run.
What is the difference between LoCo and HiCo magstripe cards?
Coercivity is how strong a magnetic field it takes to write, or erase, the stripe. LoCo (about 300 Oe) stripes are easier to encode but wear faster and are more easily scrambled by everyday magnets; HiCo (about 2750 Oe) stripes hold data more firmly and survive more swipes. Hotels reissuing an unusual number of magstripe cards are often on LoCo stock in a property whose swipe volume calls for HiCo. Confirm which coercivity your encoder and locks are configured for before changing stock.
Why do all the cards from one front desk fail?
A shared workstation is a useful clue, not proof of a faulty encoder. Compare approved cards, settings and another workstation; inspect and maintain equipment according to its manufacturer’s instructions.
If a second card also fails, is the encoder definitely faulty?
No. Both cards may share an incorrect specification, permissions or encoding settings, and the door may have a separate issue. Change one variable at a time: a different batch, a different encoder, a different door. Record each controlled comparison and have the system provider review the evidence.
Should we replace or re-encode returned key cards?
Re-encode any card that is physically sound and retire cards with visible creases, cracks, delamination or water damage. Where the system and hotel policy permit, reusing sound cards can reduce replacement demand. Repeated re-encoding is not, however, a substitute for investigating a recurring fault.
What should a guest do when a hotel key card stops working?
Contact the front desk and follow the hotel’s identity-check process. Explain which door rejected the card and whether there was a light or sound. Staff can check the stay and arrange access or maintenance under hotel policy.
Does a phone failing to detect the card prove that it is damaged?
No. Phone hardware, supported card technologies, app behaviour and how the card is presented all limit detection. A negative NFC result proves neither damage nor a low-frequency credential, and a generic NFC response does not identify the exact chip. Use the hotel’s approved equipment and the system provider’s specification to investigate.
What should a hotel confirm before ordering replacement cards?
Confirm the exact lock model, encoder, software version and credential specification with the system provider, including any security mode enabled since the last order. Validate a sample using the hotel’s authorised encoder and representative test doors before approving a batch. A print sample alone does not establish encoding or door compatibility.
Start your order
Plan your hotel key card order
Share the installed lock and encoder details, quantity per design, artwork and destination. Confirm the credential and sample checks before production.