the reader is built around an arduino pro micro and a nfc module v3 by elechouse. it connects to a pc with a usb c cable and scans any tags inside the cartridge sled. once the button is pressed, it sends a key combo to the pc, which opens a one time terminal, after which the reader types out the text payload on the cartridge. executing the command on it. for more information, check the readme on my github repo. while i advise using the install scripts inside the repo, you can use your own method of assigning the key combo

https://github.com/glass-cup/NFC_cartridge_system.git

I just got a new phone, a gift from my mum, and I'm gutted that it doesn't have NFC capability. My last one did and was bought in the same region. It wasn't something I even thought to check.

Is there any way around this. I tried adding my cards to Google wallet but it says no NFC detected, unable to add.

I used my phone instead of carrying cards, it's incredibly convenient for me as I hate to carry a bag. Any and all suggestions welcome!! Thank you!

Hi,

I have tried a few now and all report `Xposed module is not working` or unsupported tag even though its on same frequency as the rest of the mifare classic fam?

I know little about NFC, and I want to see if I can clone a hotel card to my phone to avoid juggling and guessing which one's mine

Tag type says ISO 14443-3A, NXP - Mifare Ultralight EV1 48 bytes

Technology available says NfcA, MifareUltralight, NdefFormatable

Can I clone it? If so, how do I clone it?

EDIT: I'm leaving the hotel tomorrow (7/11/2026), the conclusion was that I couldn't clone it unless I bought a flipper zero, and no way I was gonna drop $200 to clone a hotel card I'm staying for 5 days

Just trying to make sure as much as possible that these are the right cards before I buy them

***UPDATE***

This is a MIFARE Classic fob. I was able to clone it using a different device. Certainly learned a lot this week! Thank you to everyone who contributed.

***Original***

Trying to make a copy of a key fob to my place of living.

Avigilon product that registers at 0-~3cm from access control reader. NFC Tools app on my phone did not register the presence of this fob. Thus, I assumed it may be 125khz.

This RFID reader/writer does not read the fob and I’m not sure what that indicates. Could this mean it’s 13.56mhz? Any insight offered would be much appreciated. My apologies if this is the wrong sub.

I'm trying to find an NFC card reader that works as a USB HID keyboard (keyboard wedge), similar to how many barcode scanners work.

Looking to automate the logon to a retail POS system. The idea is that the employee taps an NFC card, then the reader types a "username" + enter and then "password" + enter (really any two alphanumeric strings) into the currently active login screen, just like a keyboard would.

This is for a retail POS system where the login screen isn't customizable, so I can't integrate directly with the software. Security its not really an issue. The goal is mainly accountability... we want employees to stop sharing cashier login codes with each other. We'd rather they each carry an NFC card or key fob that's quick to tap than have to memorize or share PINs.

We currently do it with a Magnetic Stripe Reader (MSR) where we use track 1 and track 2 for username and password. But, due to the heavy usage the cards and readers stop working within months.

Any recommendations or products you've had good experiences with would be greatly appreciated.

大家好，
我想分享我在為 Yoto 卡片準備空白 NFC 卡時發現的一些事情。
一開始我以為我的 NTAG 當中有一個是有缺陷的，因為：
iOS NFC 工具顯示 **「不支援 NDEF」**
「擦除標籤」失敗
「格式化記憶體」似乎沒有任何反應
標籤從來沒有變成可寫入的 NDEF 標籤
然而，經過在 Android 手機上的測試後，我發現了一些有趣的事情。
**測試環境**
iOS 上的 NFC 工具
Android 上的 NFC 工具
NXP TagInfo
空白的 NTAG203 / NT2H0301 標籤
**初始記憶體（空白標籤）**

**第 03 頁**
**00 00 00 00**

**第 04 頁**
**00 00 00 00**

**第 05 頁**
**00 00 00 00**

該標籤被 Android 偵測為：

android.nfc.tech.NdefFormatable
但沒有 NDEF 數據。

**iOS NFC 工具**
**格式化記憶體**
操作完成，但記憶體保持不變。
標籤仍顯示：
不支援 NDEF
擦除標籤失敗
無可寫入的 NDEF 記錄
記憶體：

第 03 頁
00 00 00 00

**Android NFC 工具**
立即執行 **格式化記憶體** 使標籤成功初始化。
記憶體變為：

第 03 頁
E1 10 06 00

第 04 頁
03 04 D8 00

第 05 頁
00 00 FE 00
之後：
標籤變成了 NDEF 標籤
NFC 工具報告它為可寫的
iOS NFC 工具現在可以正常讀取和寫入它

**iOS 擦除標籤（在 Android 格式化後）**
有趣的是，一旦 Android 初始化了標籤，iOS 的「擦除標籤」運作得非常好。
它產生了一個空的 NDEF 結構：

第 03 頁
E1 10 06 00

第 04 頁
03 03 D0 00

第 05 頁
00 FE 00 00

注意到 iOS 保留了能力容器 (CC)，而不是將其刪除。

**結論**
根據我的測試，看起來：
Android NFC 工具 **可以將空白的 NTAG 初始化為有效的 NDEF 標籤**。
iOS NFC 工具 **無法初始化完全空白的 NTAG**，儘管它稍後可以擦除並重新寫入已格式化的 NDEF 標籤。
一旦 Android 執行了初始格式化，iOS 就能完美運作。
還有其他人觀察到相同的行為嗎？
這是 iOS Core NFC 的限制，還是僅僅是 NFC 工具在 iOS 上實現的差異？

​

Hi everyone,

I work for a manufacturer in China that produces RFID and NFC cards, tags, and labels.

One thing I've noticed is that many people starting an NFC project focus on the card design first, but the chip selection is actually much more important.

Here are a few common options:

NTAG213 – Great for simple URLs, social media links, and digital business cards.

NTAG215 – More memory, often used for applications requiring additional data storage.

NTAG216 – Best when you need the largest user memory for NFC applications.

MIFARE Classic – Common for access control systems (depending on regional requirements).

MIFARE DESFire – Better security, often used in transportation and enterprise access systems.

The "best" chip really depends on your application, budget, and compatibility requirements.

I'm curious:

What NFC project are you currently working on?

Which chip have you chosen, and why?

Have you run into any compatibility issues with Android or iPhone?

I'd be happy to answer questions about NFC manufacturing, chip selection, printing, or customization from a factory perspective.

Looking forward to learning from everyone's experience as well.

Estoy intentando copiar una tarjeta, viendo tutoriales y al intentar mapearla para copiar la información de la tarjeta no se abre donde aparecen los sectores y códigos.
No sé si necesito tener las claves, sí es así no sé cómo conseguirlo, alguna ayuda alguien?

I have exeed rx phev car but I don’t know how to activate NFC. I downloaded exeed link app. I’m not sure if its the correct app but it doesn’t recognize my car it says there isn’t a car and I don’t know how can I activate NFC if anyone has any idea please let me know

Hi, I am researching a device concept for an ISO14443 13.56MHz contactless transportation card.

The concept is a small accessory device where the original passive card is inserted inside.

The user points the device toward the existing NFC card reader and the goal is to improve the usable reading distance to around 8–10cm without physically touching the reader.

The original card remains unchanged.

I would like to ask NFC/RFID engineers:

Is it technically possible to improve the coupling distance between an ISO14443 passive card and a reader using an external device?

Would a passive antenna/coupling design be enough, or would an active RF architecture be required?

What are the main engineering at 13.56MHz for reach this distance? (8-10cm)

If an active approach is needed, what type of architecture should be researched?

What parameters should be evaluated first (antenna size, Q-factor, impedance matching, field strength, load modulation)?

I am looking for technical guidance on feasibility and the correct development approach.

Thank you.

Heya, got this keychain as a gift. Any cool things to write on this badass tech (aside from rickroll)? 😛

For curious reasons I wanted to ask in theory if someone were to put magnetic emv panels over emv transaction panels is double charging a real thing. I couldn’t ask ChatGPT. it was like “sounds like you want instructions”.

I’ve never really been interested in committing a crime but the ABILITY to be able to double charge nfc like at a gas pump and mimic a real charge sounds like a hectic crime when done in bulk throughout multiple counties worth of gas stations. If anybody is familiar I would love to chat about it.

In Tasker it is possible to start an action, if the phone detects a read-only NFC tag.

How is this possible wiith Macrodroid?

How to connect an RFID module without a solering iron to the m5stickc plus 1.1