Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
An RFID and keypad based door lock using Arduino can unlock a prototype when a compatible RC522 RFID card, a correct keypad PIN, or both are accepted. The design uses an Arduino Uno, SPI-connected MFRC522 reader, 4×4 matrix keypad, and externally powered transistor-switched actuator; it is not automatically a secure residential lock.
The useful design distinction is between authentication input and physical locking hardware. The reader and keypad only provide data. The Arduino makes the authorization decision, while a separate protected driver supplies the current needed by a solenoid, electric strike, cabinet latch, or servo.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Key takeaways
- An Arduino RFID and keypad door lock can authenticate an RC522-compatible 13.56 MHz card, a keypad PIN, or both before operating an electrically controlled latch.
- The MFRC522 is an ISO/IEC 14443-A proximity-reader frontend for supported MIFARE and NTAG applications, not a universal reader for every RFID card, NFC phone, or access credential.
- A directly wired 4×4 matrix keypad uses four row wires and four column wires, while an I2C expander can reduce the Arduino’s direct GPIO requirement.
- A solenoid is an inductive load and must receive power from a suitable external supply through a transistor or MOSFET driver with flyback protection; an Arduino GPIO must not power the solenoid directly.
- This Arduino door-lock project is an educational prototype, not automatically a secure residential access-control system. Security also depends on credential storage, retry limits, power-loss behavior, physical installation, and the selected actuator.
What does an RFID and keypad based door lock using Arduino do?
An RFID and keypad based door lock using Arduino checks one or two local credentials and then drives an actuator for a limited period. In the simplest policy, a recognized RFID card or correct PIN unlocks the prototype. In a two-factor policy, the system requires both credentials before it energizes a solenoid, releases a latch, or moves a servo.
The system has five functional blocks:
- Controller: an Arduino Uno reads inputs and runs the authentication state machine.
- RFID input: an MFRC522/RC522 module reads a compatible 13.56 MHz proximity credential over SPI.
- PIN input: a 4×4 matrix keypad supplies numeric keys, confirmation, and cancellation input.
- Decision logic: firmware compares the presented credentials with stored authorization data.
- Actuator circuit: a transistor or MOSFET switches externally supplied power to the selected lock or latch.
The Arduino should control the lock rather than serve as the lock’s power supply. Treat the project as a bench prototype until the electronics, mechanical release, enclosure, power-failure behavior, and credential handling have been tested deliberately.
Popular on Amazon
- TURN CODE INTO REAL-WORLD RESULTS — Follow 22+ guided lessons to make LEDs blink, read temperature and distance, move servo and stepper motors, control an LCD and respond to joystick or IR input; ideal for a family weekend build, homeschool unit, coding club or STEM classroom
- MORE PROJECT VARIETY IN ONE ORGANIZED KIT — Includes the UNO R3 controller, LCD1602 with pre-soldered header, breadboard power module, ultrasonic and DHT11 sensors, joystick, IR receiver and remote, SG90 servo, stepper motor, relay, DC motor, fan blade, displays, LEDs, buttons, resistors and jumper wires
- START WITHOUT SOLDERING — Plug-in modules, a solderless breadboard and the pre-soldered LCD help beginners focus on wiring, code and testing; the illustrated component list makes it easier to find each part and move from one lesson to the next
- LEARN THE LOGIC, THEN CREATE YOUR OWN — Use Arduino IDE and the included example code to understand digital input and output, analog sensing, timing, motor control and display functions, then change thresholds, speeds and sequences for alarms, environmental monitors, reaction games and motion projects
- CLEAR SETUP SUPPORT FOR FIRST-TIME BUILDERS — Download the latest tutorial and code, select the UNO board and correct computer port, check component polarity and breadboard rows, and keep power-module input at 9V or below; younger learners should work with an experienced adult
Which parts are needed?
A practical prototype needs the following parts. Exact voltage, current, mounting dimensions, and fail-safe behavior depend on the actuator and modules selected.
| Part | Purpose | Selection note |
|---|---|---|
| Arduino Uno R3 or compatible board | Runs the firmware and coordinates the reader, keypad, and driver | Use the official Arduino Uno R3 documentation and datasheet for the board’s electrical and pin information. |
| MFRC522 RC522 RFID reader module | Reads supported proximity cards and key fobs over SPI | Confirm the module’s supply and logic requirements; inexpensive RC522 boards from different sellers can vary in quality. |
| Compatible 13.56 MHz RFID card or key fob | Provides the RFID credential | Choose a credential technology supported by the reader and library rather than assuming every RFID or NFC device will work. |
| 4×4 16-key membrane keypad | Accepts the PIN and control keys | Direct wiring normally consumes eight GPIO lines: four rows and four columns. |
| Transistor or logic-level MOSFET | Switches actuator current | Choose a device suitable for the actuator’s voltage and current, including startup conditions. |
| Flyback diode | Suppresses the inductive voltage produced when a DC coil is switched off | Place it across a DC solenoid or similar coil as shown in the Adafruit solenoid reference design. |
| Regulated actuator power supply | Supplies the lock or latch | Do not assume the Arduino’s 5 V rail can provide the actuator’s voltage or current. |
| Breadboard, jumper wires, enclosure, and test indicator | Supports safe bench testing | Test with an LED, lamp, or disconnected latch before attaching a real door mechanism. |
The most relevant RFID purchase description is MFRC522 RC522 RFID reader module. The name identifies the central reader family without implying that an inexpensive module is equivalent to a commercial access-control reader.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesWhat RFID cards work with the RC522?
The RC522 is a 13.56 MHz RFID frontend intended for ISO/IEC 14443-A proximity applications. According to NXP Semiconductors’ 2016 MFRC522 datasheet, the MFRC522 operates at 13.56 MHz and is intended for MIFARE and NTAG applications using that technology.
The commonly used Arduino library is designed for MFRC522 and other RC522-based modules and communicates through SPI. The library documentation describes support for several MIFARE Classic cases but also records important limitations, including unsupported phone communication, card emulation, and some other card or interface paths. A phone displaying NFC capability therefore is not automatically a replacement for a compatible card or key fob.
For a beginner prototype, use a compatible MIFARE Classic-style card or key fob and identify the credential technology in the parts list. Do not advertise the finished project as universal NFC access control. The reader’s practical range also depends on the particular module, credential, enclosure, wiring, and installation; the supplied research does not establish a universal range figure.
How should the Arduino, RC522, and keypad be wired?
The following is one example pin allocation for an Arduino Uno. It is an example design, not an immutable standard; change the firmware and wiring together if a different allocation is required.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Also popular on Amazon
- 35+ Guided Electronics Projects: Progress from LEDs and buttons to RFID access, real-time clocks, motion and distance sensing, environmental monitoring, motor control and interactive displays for STEM learning, coding clubs and maker projects
- More I/O and Memory for Larger Builds: The MEGA 2560 R3 provides 54 digital I/O pins, including 15 PWM outputs, 16 analog inputs, 4 hardware serial ports and 256 KB flash for projects that combine more sensors, controls and displays
- 200+ Components for Prototyping: Includes LCD1602, RC522 RFID, RTC, DHT11, HC-SR501 PIR, ultrasonic and water-level sensors, GY-521, MAX7219, keypad, joystick, rotary encoder, relay, SG90 servo, stepper motor, DC motor, breadboard and more
- Learn, Modify and Create: Follow 35+ guided lessons with example code, then adjust sensor thresholds, timing, display text, motor behavior and control logic to turn structured exercises into access systems, monitors, alarms and interactive projects
- Organized for Repeatable Learning: Pre-soldered modules, a solderless breadboard, storage case and small-parts box reduce setup time and keep sensors, LEDs, ICs, wires and other components easy to find between projects
| Function | Example Uno connection | Responsibility |
|---|---|---|
| RC522 SDA/SS | D10 | SPI chip-select line |
| RC522 SCK | D13 | SPI clock |
| RC522 MOSI | D11 | SPI controller-to-reader data |
| RC522 MISO | D12 | SPI reader-to-controller data |
| RC522 RST | A0 used as a digital output | Reader reset control |
| Keypad rows | D2, D3, D4, D5 | Four row lines |
| Keypad columns | D6, D7, D8, D9 | Four column lines |
| Lock-driver control | A1 used as a digital output | Logic-level command to the transistor or MOSFET |
Keep the reader’s SPI wiring visually separate from the keypad’s row and column wiring in the schematic. Label every wire at both ends. The documented Arduino 4×4 keypad example illustrates the normal direct-wiring model: four row pins, four column pins, a key map, and repeated polling through a keypad library.
Before connecting the RC522, check the particular module’s supply and logic requirements. Clone boards are not guaranteed to be electrically identical. The MFRC522 library documentation is useful for library-specific wiring and compatibility notes, while the NXP component datasheet documents the MFRC522 itself.
How can an I2C keypad reduce GPIO use?
An I2C keypad design places an expander such as a PCF8574 between the Arduino and keypad, so the Arduino uses the I2C interface instead of eight individually assigned row and column GPIO lines. The approach is useful when the reader, display, alarm, sensor, and actuator already consume most of the Uno’s pins.
The trade-off is additional configuration and another possible failure point. The expander’s I2C address, wiring, library, interrupt option, and keypad board must all agree. The Keypad_I2C implementation documentation describes the address and interface configuration. Direct wiring is easier to audit; I2C expansion is more economical with GPIO.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall| Keypad method | Direct Arduino connections | Advantages | Trade-offs |
|---|---|---|---|
| Direct 4×4 matrix | Four rows plus four columns | Simple signal path and straightforward troubleshooting | Consumes eight GPIO lines |
| I2C expander | I2C plus the expander-to-keypad wiring | Preserves Arduino GPIO for other functions | Requires an expander, correct address, I2C wiring, and compatible software |
How do you connect a solenoid lock safely?
Connect the Arduino output to a transistor or MOSFET control terminal, and power the solenoid from a separate regulated supply selected for the lock. Connect the supply ground to the Arduino ground where the driver design requires a common reference. Place a flyback diode across the DC solenoid, oriented so it is reverse-biased during normal energizing and conducts when the coil is switched off.
A solenoid is an inductive load. When current is interrupted, the coil can create a voltage spike capable of damaging the switching device or disturbing the Arduino. The Adafruit security-keypad reference design documents a transistor-switched solenoid arrangement with a 1N4001 diode across the solenoid.
Also popular on Amazon
- 30+ Guided Electronics Projects: Start with LEDs and build toward LCD1602 displays, RFID access, motion detection, distance sensing, motor control and environmental monitoring for STEM learning, coding clubs, classrooms and hobby projects
- 200+ Components Across 63 Types: Includes an ELEGOO UNO R3 controller, LCD1602, RC522 RFID, RTC, HC-SR501 PIR sensor, ultrasonic sensor, DHT11, GY-521, MAX7219, keypad, joystick, relay, SG90 servo, stepper motor, breadboard and more
- Begin Without Soldering: Pre-soldered modules, a solderless breadboard, organized storage case and small-parts box reduce setup time and help beginners move from lesson to lesson while keeping LEDs, ICs, wires and sensors easy to find
- Learn, Modify and Create: Program the ELEGOO UNO R3 board with Arduino IDE using the included PDF tutorial and example code, then adjust sensor thresholds, timing, display text and motor behavior to turn guided lessons into original projects
- Flexible Power and Project Setup: Includes a 9 V, 1 A power supply, breadboard power module, 9 V battery and USB cable to support controller, breadboard and module experiments without sourcing basic setup accessories separately
The exact actuator must be selected from its own datasheet. A “12V DC solenoid lock” is a product category, not a universal specification: models differ in current, stroke, holding force, mounting, duty cycle, and whether they remain locked or unlocked when power disappears. A servo, cabinet latch, electric strike, and solenoid are not interchangeable mechanically or in their power-failure behavior.
Never power a solenoid directly from an Arduino GPIO. Use wiring that can handle the actuator current, provide a suitable supply, protect the switching device, and prevent the moving mechanism from trapping someone during a test.
Should the lock accept RFID, a PIN, or both?
The authentication policy determines the convenience and security properties of the prototype. Select the policy before writing the firmware because the state machine and user prompts depend on it.
| Policy | Unlock condition | Benefit | Weakness |
|---|---|---|---|
| RFID only | Recognized card or key fob | Fast and convenient | Anyone who obtains the accepted credential can unlock the prototype. |
| PIN only | Correct keypad PIN | No RFID credential to distribute | A disclosed, observed, or poorly stored PIN is enough to unlock the system. |
| RFID or PIN | Either credential succeeds | Convenient fallback when one method is unavailable | Compromise of either credential can unlock the prototype. |
| RFID plus PIN | Both a recognized credential and the correct PIN | Demonstrates two-factor access and reduces reliance on one factor | Less convenient and still limited by the quality of both credential systems. |
| RFID identity plus PIN confirmation | Known card identifies a user, followed by that user’s PIN | Supports a user-to-credential data model | Requires separate records, careful storage, and a clear account-management process. |
For a construction or workshop prototype, “RFID plus PIN” is the clearest demonstration of two local authentication methods. For a simple cabinet demonstrator, “RFID or PIN” may be easier to operate. Neither policy makes UID-only matching a strong credential system by itself.
What should the Arduino firmware state machine do?
A reliable sketch should treat RFID reading, PIN entry, authorization, actuator timing, and lockout as separate states rather than placing all behavior in one delay-heavy loop.
- Startup: initialize serial diagnostics, the SPI bus, the RC522 library, the keypad, and the actuator-control pin.
- Defined locked state: set the actuator output to the documented default state. Do not assume that a reboot automatically means the physical door is secure.
- Idle: poll for a new RFID card and independently poll the keypad.
- RFID candidate: read only the credential data needed by the chosen policy, then clear the transient card buffer when the decision is complete.
- PIN entry: append keys to a bounded buffer, use a defined confirmation key such as
#, and use a cancellation key such as*. - Authorization: compare the card and PIN according to the selected policy. Keep the decision explicit: card only, PIN only, either, or both.
- Unlock: activate the driver for a bounded interval or command a servo to its unlock position.
- Relock: return the actuator to its locked state after the timeout, then clear the PIN buffer and any temporary credential data.
- Failure and lockout: count failed attempts, impose a delay after repeated failures, and return to idle without printing full credentials.
A compact pseudocode structure looks like this:
setup reader, SPI, keypad, serial diagnostics, and lock driver
set actuator to its defined startup state
loop:
if lockout timer is active:
keep actuator in defined state
wait without accepting authorization
if a new RFID card is present:
read supported credential data
update authentication state
if a keypad key is pressed:
cancel on '*'
append a digit only while the buffer has room
submit on '#'
if selected policy is satisfied:
clear temporary credential data
activate driver for bounded unlock time
if unlock timer expires:
deactivate driver or return servo to locked position
clear PIN buffer
if an attempt fails:
increment retry count
start lockout when the configured limit is reachedUse non-sensitive diagnostics such as “RFID rejected,” “PIN length invalid,” or “lockout active.” Do not print a complete PIN or a credential secret to the serial monitor. A tutorial screenshot should never expose a real PIN.
Also popular on Amazon
- Powerful: The Arduino Nano V3.0 Board Microcontroller Built with ATmega328P and CH340 chips instead of FT232, Improved new version CH340G Replace FT232RL, making it ideal for beginners
- Seamless Compatibility: Fully compatible with Arduino Nano, supporting Arduino IDE, ISP programming and USB download. Works seamlessly with Windows, Mac, and Linux operating systems for a hassle-free experience.
- Versatile I/O & Compact Design: Features 14 digital I/O pins (6 PWM outputs), 6 analog inputs, a 16MHz quartz oscillator, USB-C power socket, ICSP port, and reset button. Its compact, breadboard-friendly design ensures easy handling and integration.
- Flexible Power Supply Options: Supports multiple power sources, including USB-C, 6-12V unregulated external power, or 5V regulated external power. The Nano board intelligently switches to the higher voltage source automatically—no jumper selection required.
- Excellent Communication Capabilities: Designed for seamless communication with PCs and arduino microcontrollers, the Nano board is fully compatible with multiple operating systems and offers stable and reliable performance for a variety of projects.
How should the project be tested before installation?
Test the electronics and the mechanical installation separately. A door lock that works on a breadboard can still fail when the actuator is mounted against a misaligned latch or powered through an undersized cable.
- Test the Uno alone: confirm the board accepts the sketch and produces ordinary startup diagnostics.
- Test the keypad: print key labels only and verify every row-column combination, including the cancellation and confirmation keys.
- Test the RC522: identify only a compatible test card and confirm that the SPI wiring, reset line, supply, and library configuration are correct.
- Test the driver without the lock: use an LED or suitable test load to verify that the Arduino output changes the driver state.
- Test the actuator on its own supply: check startup behavior, heating, wiring voltage drop, and the actual locked/unlocked movement.
- Test the combined policy: verify accepted and rejected cards, incorrect PINs, cancellation, repeated failures, timeout relocking, and reboot behavior.
- Test power loss deliberately: remove and restore power while locked, unlocking, and between authentication steps. Record whether the selected mechanism fails secure or fails safe.
- Test manual release: provide a deliberate emergency-entry or manual-release procedure before placing the assembly on a door or enclosure.
Do not trap a person inside a room or behind a test enclosure. For a construction-site or workshop deployment, use a clearly accessible mechanical override and treat the prototype as unapproved until a qualified person has reviewed the installation.
Why is an Arduino RC522 door lock not automatically secure?
An RC522 reader and keypad provide input methods, not a complete security model. A beginner sketch that compares a card UID and a plaintext PIN may demonstrate the workflow while offering limited resistance to credential copying, observation, firmware extraction, wiring bypass, or mechanical attack.
Evaluate at least these boundaries:
- Credential technology: verify whether the card technology supports the authentication properties required for the application. RC522 compatibility does not mean universal or high-assurance NFC security.
- UID handling: treat UID-only authorization as a prototype mechanism rather than proof of a secure credential.
- PIN storage: avoid exposing the PIN in source screenshots, serial logs, documentation, or unsecured configuration.
- Retry control: impose limits and delays so unlimited guessing is not the default behavior.
- Firmware integrity: protect programming access and review the code before trusting the system with valuable equipment.
- Physical bypass: protect the controller, reader wiring, driver, and emergency-release route inside an appropriate enclosure.
- Power behavior: define what happens during brownout, unplugging, supply failure, and a controller reboot.
- Mechanical security: match the actuator to the door, latch, frame, load, and required fail-safe or fail-secure behavior.
The project should therefore be described as an educational access-control prototype. It should not be presented as a certified residential door lock, life-safety device, or universal RFID access-control system without separate engineering, testing, compliance review, and an appropriate commercial mechanism.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What are the common failure points?
| Symptom | Likely area | What to check |
|---|---|---|
| RC522 is not detected | Power, SPI, reset, chip select, or module quality | Confirm the example pin map, SPI lines, reset and SS assignments, ground, supply requirements, and library configuration. Try a known-compatible card and inspect the module for poor soldering. |
| Some cards work and others do not | Credential compatibility | Check whether the card uses a supported ISO/IEC 14443-A technology and whether the selected library path supports it. Do not infer universal compatibility from one successful read. |
| Wrong keypad characters appear | Row and column order | Verify the physical membrane connector order against the row and column arrays in firmware. Test each key individually. |
| Arduino resets when the lock activates | Actuator supply noise, voltage drop, or inadequate grounding | Use the specified external actuator supply, separate high-current wiring, a suitable driver, a flyback diode, and an appropriate common-ground arrangement. |
| Lock clicks but does not release | Mechanical fit or actuator rating | Check voltage, current, stroke, alignment, latch friction, duty cycle, and the actuator’s datasheet. Electrical operation does not prove mechanical suitability. |
| Lock remains in the wrong state after reboot | Undefined startup and power-loss behavior | Set the output deliberately during initialization and test the selected actuator’s behavior during power removal and restoration. |
Which implementation should you choose?
Choose the implementation according to the installation rather than according to the reader or keypad alone.
Also popular on Amazon
![Arduino Uno REV3 [A000066] - ATmega328P Microcontroller, 16MHz, 14 Digital I/O Pins, 6 Analog Inputs, 32KB Flash, USB Connectivity, Compatible with Arduino IDE for DIY Projects and Prototyping](https://m.media-amazon.com/images/I/515P6aYSP4L._SL160_.jpg)
- ATmega328P Microcontroller: Powered by the reliable ATmega328P, running at 16 MHz with 32KB of flash memory, 2KB SRAM, and 1KB EEPROM, offering ample resources for a wide range of basic to advanced electronics projects.
- 14 Digital I/O Pins & 6 Analog Inputs: Features 14 digital I/O pins (6 of which support PWM output) and 6 analog inputs (10-bit resolution), providing flexible options for sensors, motors, and other external components.
- USB Connectivity for Easy Programming: The built-in USB port allows for direct programming and serial communication, enabling a simple connection to your computer for sketch uploading and debugging through the Arduino IDE.
- Compatible with Arduino IDE: Full compatibility with the Arduino IDE ensures easy access to a vast array of libraries, code examples, and community-driven projects, making the Uno a great choice for both beginners and experienced makers.
- Widely Used in Education & Prototyping: The Arduino Uno is a standard in educational environments, widely used for learning and teaching electronics and programming. It's perfect for prototyping, robotics, IoT projects, and more.
| Use case | Suitable prototype direction | Important qualification |
|---|---|---|
| Learning RFID and keypad integration | Uno, RC522, direct 4×4 keypad, LED or small latch | Keep the setup on a bench and focus on state transitions and compatibility. |
| GPIO-constrained prototype | Uno, RC522, I2C keypad expander, driver, and actuator | Validate the expander address, library, and I2C wiring. |
| Two-factor demonstration | Compatible RFID card plus PIN before a time-limited unlock | Use bounded buffers, retry limits, and non-sensitive diagnostics. |
| Cabinet or equipment enclosure | Electronic cabinet latch or appropriately rated solenoid | Check mounting, manual release, power-loss behavior, and physical bypass resistance. |
| Residential or life-safety door | A properly specified commercial access-control product reviewed for the installation | Do not substitute an uncertified Arduino prototype for a compliant access-control or emergency-egress system. |
What should you buy first?
Start with an Arduino Uno R3-compatible development board, an MFRC522 RC522 RFID reader module, compatible 13.56 MHz RFID cards or key fobs, and a 4×4 16-key membrane keypad. Add the driver, flyback diode, regulated actuator supply, and selected latch only after the reader and keypad work independently.
For the actuator stage, search for a 12V DC solenoid lock only after checking the individual model’s current, mounting, duty cycle, and fail behavior. Pair the actuator with a correctly rated MOSFET or transistor solenoid driver with flyback diode; do not treat a product label as a substitute for the electrical datasheet.
The central compatibility decision is the RFID credential. Buy a module and card or key-fob combination explicitly described as compatible with the RC522/MFRC522 and the intended library. Neither the research nor the component documentation supports a universal claim about every inexpensive board, phone, card, enclosure, or installation.
Recommended Free Tools
Frequently Asked Questions
Can Arduino unlock a door using an RFID card and password?
Yes. An Arduino Uno can read a compatible RC522/MFRC522 RFID credential over SPI and read a PIN from a 4×4 keypad, then control a lock actuator through a transistor or MOSFET driver. The Arduino must not power a solenoid directly, and RC522 compatibility does not include every RFID card, NFC phone, or access credential.
How do I connect a 4×4 keypad to an Arduino?
A directly wired 4×4 matrix keypad uses four row lines and four column lines, for eight keypad signal connections. An I2C expander such as a PCF8574 can reduce the number of Arduino GPIO connections, but it adds address, wiring, library, and hardware configuration requirements.
Is an RC522 RFID door lock secure?
No. An RC522 RFID door lock is not automatically secure because security depends on the credential technology, whether authorization relies only on a UID, PIN storage, retry limits, firmware protection, physical bypass resistance, and power-loss behavior. An Arduino prototype should not be treated as a certified residential access-control system.
What RFID cards work with an RC522?
The RC522 is a 13.56 MHz ISO/IEC 14443-A proximity-reader frontend intended for supported MIFARE and NTAG applications. A compatible MIFARE Classic-style card or key fob is a sensible beginner choice, but the commonly used Arduino library does not make the module a universal reader for every RFID card, NFC phone, or card technology.
The Bottom Line
An Arduino can combine an RC522-compatible RFID credential and a keypad PIN to control a lock actuator, but the safe design separates logic power from actuator power, uses a protected transistor or MOSFET driver, defines startup and power-loss behavior, and treats authentication and physical security as separate engineering problems. Build and test it as a prototype before considering any real door installation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
