2407129_en-US

[#1]

Is SmartMX2 the right choice for my project?

Hi all,

I'm evaluating secure element options for a standalone contactless payment device (not a phone) that would need to hold several tokenized payment card applets on one chip, with the ability to select which applet is active/exposed to a terminal before each transaction.

A couple of specific questions on SmartMX2:

1. Roughly how many separate payment applets / GlobalPlatform Security Domains can a single SmartMX2 chip realistically support?
2. Does the platform support runtime AID selection triggered by an external host command — i.e., can host-side firmware tell the chip which provisioned applet to expose before a tap, rather than the chip always presenting a static/priority-ordered AID list?
3. Is SmartMX2 still the right product line for this kind of banking/payment use case, or is there a newer NXP family better suited to it?

Any pointers to public documentation, dev kits, or the right internal team to talk to would be appreciated. Thanks!

Re: Is SmartMX2 the right choice for my project?

Hello @Javiergg 

Please see the comments on your questions:

1. The NXP SmartMX2 product page on nxp.com is a good starting point for public datasheets and overview documentation.
- For deeper technical specs, the product's reference manual (available under NDA) would cover GlobalPlatform SD limits and AID management.
2. For dev kits and direct engagement with the right team, reaching out through NXP's official sales or FAE (Field Application Engineer) channel is recommended, as they can connect you with the secure element specialists for banking/payment applications.
3. Regarding whether SmartMX2 is still the right fit vs. a newer family — NXP's SE050 or SN100 series are also worth exploring depending on your interface and form factor requirements, and an FAE can help compare options for your specific use case.