What is the only difference between PN7160 and PN7161?

The PN7161 adds Apple Enhanced Contactless Polling (ECP) support. All other protocols, interfaces, and performance are identical. Choose PN7161 if you need Apple Wallet or Apple Pay compatibility.

Is the PN7161 a drop-in replacement for the PN7160?

Yes for I2C designs. Same interface, same protocols, just update the chip initialization in your firmware. The MINI SPI version uses SPI instead of I2C.

Does the PN7160 work with Android NFC?

Yes. Both PN7160 and PN7161 fully support Android NFC for ISO 14443A/B, ISO 15693, and NFC Forum tags.

PN7160 vs PN7161 - ELECHOUSE

PN7160 vs PN7161 is a focused decision page for one question only: do you need Apple ECP support or not? In most hardware and software respects, these two module families are intentionally very close.

Short Answer

Choose PN7160 if you want Linux, Raspberry Pi, or embedded NFC controller integration and do not need Apple ECP.
Choose the PN7161 family if your project needs Apple ECP, Apple Wallet-related reader behavior, or Apple VAS-style use cases.

Main Difference

Feature	PN7160	PN7161
Apple ECP	No	Yes, across PN7161 variants
NCI 2.0 workflow	Yes	Yes
I2C standard module available	Yes	Yes
MINI SPI version available	No	Yes, PN7161 MINI V1 — SPI
Raspberry Pi / Linux suitability	Yes	Yes
Default lower-cost choice when Apple ECP is not needed	Yes	No

Recommendation by Scenario

Use PN7160 when:

You are building on Raspberry Pi or Linux
You want NCI 2.0 controller integration
You do not need Apple ECP
You prefer the lower-cost option for standard NFC controller work

Use PN7161 family modules when:

You need Apple ECP support
Your use case is tied to Apple Wallet or Apple VAS-like flows
You want the PN7160 hardware and software model plus Apple-specific capability
You will choose between PN7161 I2C and PN7161 MINI V1 — SPI based on your host interface

Use PN7161 MINI V1 — SPI when:

Your host platform uses SPI instead of I2C
You want a compact PN7161-family module
You are building on Raspberry Pi SPI or ESP32 VSPI
You want PN7161-family capability with a tested SPI workflow

What Does Not Change

Both PN7160 and PN7161 are NFC controller-oriented modules, not beginner-first hobby boards.
Both are more natural on Linux and embedded systems than classic hobby-only workflows.
Both use the same family setup logic and similar host integration model.
The key product decision is still whether Apple ECP is required and whether your hardware uses I2C or SPI.

Interface Choice Matters

When comparing PN7160 and PN7161, remember that PN7161 is a family. The standard PN7161 I2C module uses I2C, while the PN7161 MINI V1 — SPI module is the SPI version for projects that need the PN7161 family on an SPI bus.

What We Recommend

If you are unsure, start with PN7160. Move to PN7161 I2C when Apple ECP is clearly part of your requirement. Choose PN7161 MINI V1 — SPI when you need both PN7161-family capability and an SPI interface.

Related Docs

Arduino and ESP32 Library Notes

Use ELECHOUSE_PN7150_PN7160 (GitHub) for PN7160, PN7161 I2C, and PN7161 MINI V1 SPI development.
For PN7161 in this library, use the PN7160-compatible path.
For PN7161 MINI V1 SPI, the standard repository examples can now be used directly after changing PN71XX_USE_SPI from 0 to 1.