Troubleshooting guide
Hotel key card not working?
If the card taps rather than swipes, it was not demagnetised; that is not physically possible for an RFID card. Below are the seven causes that actually occur, ranked by how often they turn up, and the five-step check a front desk can run before anyone sends a second card upstairs.
Published · Updated · For front-desk, engineering and procurement teams
The short answer
RFID key cards cannot be demagnetised. They store data in a silicon chip attached to an antenna loop, not in magnetic particles, so no phone, magnet or airport scanner can erase one. When a tap card stops working the cause is almost always one of these: the encoded validity has passed, the card was mis-encoded at check-in, the chip no longer matches what the lock expects after a security update or phased upgrade, the antenna cracked from bending, or the lock battery is flat. Only magstripe cards, the kind you swipe, can genuinely be demagnetised, and the usual culprit is a magnetic bag or wallet clasp rather than a phone.
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
The seven real causes, by how often they occur
Ordered by how often each turns up in practice, not by how often it gets blamed. The chip-mismatch cause is listed first because it is the one procurement can prevent before an order is placed. None of these is conclusive on its own; treat a failed tap or swipe as an observation and confirm it with a controlled comparison.
| 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. Extending the reservation in the property management system alone does not update the card. |
| 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 | Retire the card. A broken antenna loop is invisible through the laminate and does not recover. |
| 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 | Engineering replaces the batteries or services the reader using the model’s instructions. This is a door issue, not a card issue. |
| 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 | Clean the reader or encoder head with a cleaning card and put it on a schedule. A worn write head garbles good blanks. |
| Genuine demagnetisation or stripe wear | Swipe fails on every door and every reader; reissue rates creep up across the property. | Magstripe only | Re-encode. If it recurs within the same stay, the stripe is worn. Keep cards away from magnetic clasps, and review whether LoCo stock suits the property’s swipe volume. |
Card or lock?
Five-step front-desk check
This sequence separates a card fault from a lock fault before anyone is sent upstairs with a second card that will fail the same way. 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. If the card opens a different door, the card is working and the original lock needs attention. If it fails everywhere, the card or its encoding is 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. This writes a fresh credential and a new validity and resolves the two most common causes, expiry and mis-encoding. An RFID card can be re-encoded many times, so replacing it on the first failure discards a working card.
-
Issue a second card from different stock
If the re-encoded card still fails, take a card from a different box or batch. When the fresh card works, the first batch is suspect. When it also fails, look at the encoder that wrote both, then at the lock.
-
Inspect the card for physical damage
Hold the card up to a bright light. A crease across the middle usually means a broken antenna loop, which is permanent and invisible from the outside. Retire any card that has been folded, chewed by a reader, delaminated or run through a wash cycle.
-
Check the lock before sending a third card upstairs
If every card fails on one door while working elsewhere, the lock is low on power or its reader has failed. Many hotel locks give a low-battery signal before they stop reading, so a door that suddenly rejects all cards has often been warning staff for some time. Hand the door to engineering with the symptoms recorded.
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. There is no magnetic storage anywhere in that chain, so there is nothing a magnet can erase.
What does kill an RFID card is mechanical. The antenna is a thin loop of etched or wound conductor. Fold the card and the loop cracks; the break is invisible through the laminate, but the card is finished. This is why a card that has been sat on, bent back in a pocket or chewed by a reader will fail intermittently before it fails for good, and why a card that reads on the fourth tap should be retired rather than handed to the next guest. Set visibly cracked, bent or delaminated stock aside for assessment; appearance alone cannot confirm an internal fault, but it is a reliable reason to stop reissuing that card.
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
Most repeat failures trace back to three fixable things
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 rather than by guest, this is why. 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. Properties that bin returned cards buy several times the stock they need; a return box at check-out and a habit of re-encoding rather than replacing is the single largest saving available in a key card programme. The cost guide works through the arithmetic and quantity planning shows how returns change the annual order.
Worn stock still in rotation. Cards do not fail politely; they go intermittent first. Pulling visibly creased or delaminated cards during the returns sort removes most mystery failures before a guest ever meets one.
Four operational habits account for most of the remaining failures:
- Put front-desk encoders on a cleaning schedule. A dusty encoder with a worn write head writes garbled data onto perfectly good blanks, which then fail on first use. If failures cluster by which desk issued the card, this is the cause.
- Wipe cards between guests at beachfront and high-humidity properties. Sand and salt residue interfere with reads long before the card looks damaged.
- Re-key extended stays before the original check-out hour, not after. A card programmed to expire at a set time does so whether or not the reservation was extended in the property management system, and back-to-back bookings that were never linked fail the same way.
- Review LoCo stripe stock if you are still on it. Low-coercivity stripes wear out faster than HiCo. A property reissuing an unusual number of magstripe cards is often paying for stripe grade rather than bad luck. 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 the broader explanation of card wear, encoding and access issues, see why hotel key cards stop working. 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?
Not an RFID card. RFID cards store data in a silicon chip, so there is no magnetic data to erase and a phone cannot wipe one. Magstripe cards can be demagnetised, but phone magnets are weak; magnetic bag and wallet clasps, money clips and name-badge magnets are far more common causes. If your card taps rather than swipes, demagnetisation is not the explanation.
Can RFID hotel key cards be demagnetised?
No. An RFID key card holds its data in a chip connected to an antenna loop, with no magnetic storage involved, so it cannot be demagnetised by phones, magnets or airport scanners. RFID cards fail for other reasons: expiry, mis-encoding, a chip that no longer matches the lock’s security configuration, a cracked antenna from bending, or a flat lock battery.
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 a re-encoded magstripe card fails again within the same stay, the stripe is worn and the card should be retired.
Why did my hotel key card stop working after one day, and do cards always expire at 11 a.m.?
Usually because the encoded validity passed. Key cards are written with a check-out date and time, so a card issued for a one-night stay stops working around check-out the next morning even though it worked hours earlier. No universal time applies; staff should verify the credential’s configured validity in the installed system. Extending a stay requires re-encoding the card; the extension in the property management system alone does not update it.
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 or credential configuration most likely does not match that part of the lock estate. 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?
The encoder at that desk is the common factor. Dust on the write head, or a head worn from volume, writes garbled data onto perfectly good blank cards. The tell is that failures cluster by which desk issued the card rather than by room, floor or guest. Front-desk encoders need a periodic clean and inspection like any other write head.
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. Because an RFID card survives many re-encodes, treating cards as single-use is the largest avoidable cost in a key card programme; returned-card reuse is why return boxes at check-out pay for themselves. 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.