AmbiTap NFC Reader Module

Made in India · Built for OEM Integration

A locally designed and manufactured NFC reader module for EV chargers, identification, authentication and embedded contactless applications.

Reduce dependence on imported NFC modules while gaining local engineering support, domestic sourcing and a clear path from prototype to production.

Talk to an Engineer Download Preliminary Datasheet · PDF · Rev 0.9.1 · 1.7 MB

AmbiTap NFC reader module — assembled PCB, angled view. 3D CAD render of board revision AE176_CLRC_01.01, not a production photograph.

Localize the NFC Interface in Your EV Charger

Many EV charger manufacturers depend on imported NFC reader modules for card interaction and contactless workflows. That works, but it ties a charger BOM to import lead times, forex exposure, customs handling and a support relationship conducted across time zones. AmbiTap gives Indian OEMs a locally manufactured alternative backed by Ambimat engineering support.

Product snapshot

The figures below are the module-level specifications Ambimat has confirmed from its own design documentation. Parameters that have not yet been characterised for the assembled module are deliberately absent rather than estimated.

Read range, current consumption, assembled-module temperature range, ESD and EMC behaviour and regulatory status are under characterisation and are not published here. Ask us where a specific parameter matters to your design and we will tell you what has been measured.

Contactless technologies are not published in this issue. The frontend is an NXP CLRC66303HNY, and what that silicon supports is documented by NXP. What AmbiTap supports at the assembled-module level is a separate statement, published only once it has been verified on the assembled board. Tell us the credential types your application has to work with and we will tell you what has been verified against them. This is a deliberate publication policy, not a gap in the design — it exists so that an integrator can rely on everything this page does list.

Designed to integrate with your host controller

AmbiTap exposes the host-control and communication signals needed to connect the NFC frontend to a charger controller or embedded host.

Assembled PCB, near top-down view. The ten-way host header runs along the board edge; reference designators and test-point labels are silkscreen. 3D CAD render, not a production photograph.

Conceptual architecture

A functional view of the module inside an OEM system. The blocks describe function only — component selection, matching-network topology and component values are Ambimat design information and are not disclosed.

Power conditioning across the VDD, PVDD and TVDD domains sits behind all four blocks, with 5 V and 3.3 V connections available on the board. Conceptual functional view, not a schematic; RF and antenna characterisation for the assembled module is pending.

Host interface connector

Multifunction signal usage depends on the selected host interface and system configuration. The pin names above show the alternate functions carried on each line; which set applies is determined by the interface you select and the firmware configuration on the host side.

Board power connections

Signal groups only. Pin order, connector designation, orientation and physical position on the board are issued with the final mechanical drawing. Confirm the intended supply arrangement with Ambimat engineering before wiring an evaluation setup.

The board outline is confirmed; the third dimension is not. PCB thickness, mounting-hole pattern, connector height, overall Z-height and enclosure clearance are issued with the dimensioned mechanical drawing. Do not commit an enclosure, bracket or bezel design against this page — send us the proposed mounting arrangement and we will review it first.

A contactless interface for the charging experience

In a charger, the reader is the point where a driver’s credential meets your system. AmbiTap is the contactless hardware at the front of that sequence; the identification, authorisation and session logic stay in your controller and back end. Charge-point teams often write this requirement down as an “RFID reader”; the word describes the requirement rather than a credential list, and what separates the options is where the NFC software runs. Our guide to choosing an RFID reader for an EV charger works through that decision.

Payment workflows require the appropriate certified payment, security and acquiring architecture around the reader hardware. AmbiTap supplies the NFC reader hardware within that architecture; it is not by itself a certified payment terminal.

Whether step 2 is identification or authentication is a system-design decision rather than a reader setting. Reading a card’s UID is not the same as authenticating the credential cryptographically, and which of the two a charging network needs determines where key material has to live.

Where it is used

AmbiTap is supplied to the manufacturer of the equipment, not to the site operator. In EV charging that means the EVSE OEM or charge-point manufacturer integrating a contactless interface into their own enclosure and their own controller. Ambimat supplies the reader module and the integration engineering around it; session authorisation, metering and back-office messaging remain functions of your charger controller and your platform.

More than a module supplier

Ambimat has been designing and manufacturing embedded electronics since 1982, including a long-standing NFC, UHF and RFID design practice. For an OEM programme, the module is usually the smallest part of the problem — the work is in the integration, the enclosure, the antenna environment and getting a repeatable build. That is the part we expect to be involved in.

Depending on the programme, support can include hardware integration guidance, host-interface selection, antenna and RF engineering discussion, connector and form-factor changes for qualified OEM opportunities, prototype-to-production support, and domestic manufacturing and volume commercial discussions. Design changes are considered on a per-programme basis after technical review rather than offered as an off-the-shelf entitlement.

The same hardware design and testing discipline used for customer programmes is what stands behind the module.

Currently importing an NFC reader module?

If your charger currently uses an imported CLRC663-based reader module, Ambimat can review your existing electrical interface, mechanical constraints, host interface and software integration requirements, and assess the migration path to AmbiTap.

We will not tell you it is a drop-in part before we have looked at yours. Pin assignment, mechanical fit and firmware behaviour differ between modules, and compatibility is something to establish against your specific incumbent hardware rather than assume. Send us the module you use today and the constraints around it, and we will give you a straight assessment of what a migration would involve.

Discuss your existing module

Need pinout, power and integration details?

The AmbiTap NFC Reader Module preliminary datasheet covers the connector pinout, power rails, host integration guidance and mechanical outline. It is published at Revision 0.9.1: the specifications it carries are the ones Ambimat has confirmed for the module, and the parameters still under characterisation are listed in it rather than estimated. Ask our engineering team where a specific parameter matters to your design.

Download Preliminary Datasheet PDF · Rev 0.9.1 · 1.7 MB · Talk to an Engineer

Frequently asked questions

Is AmbiTap made in India?

Yes. AmbiTap is designed and manufactured in India by Ambimat for OEM and embedded applications.

Is AmbiTap intended for EV chargers?

EV charging is one of the primary applications. The module can also be considered for other embedded NFC and contactless systems.

Which NFC controller is used?

The module is based on NXP’s CLRC66303HNY NFC frontend.

What host interfaces are available?

The hardware exposes multifunction signals corresponding to SPI, UART and I²C-style host connectivity. The actual interface used depends on system configuration and firmware.

What is the module size?

The PCB measures 42 mm × 42 mm.

Can AmbiTap replace the CLRC663 module we currently import?

Ambimat can review the existing module’s electrical, mechanical and software interfaces and assess the migration path. Compatibility should be verified before treating any module as a drop-in replacement.

Can the module be used for tap-and-pay?

AmbiTap can provide the NFC and contactless reader hardware within a payment-enabled system. Payment acceptance and certification depend on the complete terminal architecture, software, security implementation and acquiring or payment ecosystem used by the OEM.

Can Ambimat support OEM quantities?

Yes. OEM and volume requirements can be discussed directly with Ambimat.

Is customisation possible?

Connector, mechanical, RF or other design changes may be considered for qualified OEM and volume programmes after technical review.

Can I buy the module online?

Online INR purchasing is planned. Until the commercial launch is complete, please contact Ambimat for evaluation and OEM requirements.

Talk to the engineering team

Tell us what you are building, the host controller you are integrating with and the constraints you are working inside — mechanical, electrical or commercial. You will get an engineer, not a form response.

Need a more complete reader platform?

AmbiTap is the compact reader subsystem: you own the host controller, and AmbiTap gives that host a contactless interface to talk to.

Where the requirement is broader — extended reading range, a contact interface alongside the contactless one, hardware SAM slots or a secure element, or a wireless link to a mobile host — that is AmbiPay, Ambimat’s smart-card and NFC reader platform. The two are complementary rather than alternatives.

Ambimat module platforms

AmbiTap is one of two Ambimat OEM module platforms. They address different problems and are not alternatives to one another.

See all Ambimat products, or read about our IoT and embedded product design work.