nfc

Through our work at getkisi.com, have a bit of experience with this topic: We manufacture NFC card / mobile readers and also allow to enroll 3rd party NFC cards including credit cards: https://docs.kisi.io/references/credentials/physical_credentials/third_party_nfc_credentials?_highlight=nfc When using credit card wallets such as Apple Wallet or crypto related wallets like you suggest, those will encrypt the credit card number and require a security decoding at the receiving end - in this case the NFC wall reader. The only way to use NFC based cards on wallets on Apple devices is via Apple Wallet as outlined here: https://www.getkisi.com/guides/apple-wallet-access

Hello, same thing happened to me. I've replied to email with questions from applepayentitlements in november 2023, now 3 months later, in february 2023 we still don't have any resolution to NFC pass type id certificate request. How it ended up for you?

Would something like an NFC tag affixed onto or under your phone case be a good workaround here? Something like this: https://taptag.shop/products/tap-tag-hyperslim.

While I want Apple to support this natively, this may be possible using a small NFC tag under your phone's case or attached to the back. Something like this: https://taptag.shop/products/tap-tag-hyperslim. (The price is ridiculous, but I guess they know they have a niche thing that people want.) It essentially doesn't use the iPhone's NFC chip. I don't have one of these (yet) and am not sure if this would affect Qi charging or have any other ill effect.

Apps will be able to offer NFC payments without using Apple Pay or the Wallet app through Host Card Emulation.

What is difference between Smartcard extension and Persistent Token extension? A persistent token extension allows you to create an entirely virtual token. A smart card extension is meant to present a smart card interface, with cards being inserted and removed, APDU stuff, and so on. Which one I should use? That depends on much your reader looks like a traditional smart card reader. It sounds like it’s very close, in which case a smart card extension would make sense. Since my smartcard reader has lightening port, curious to know if EAAccessory is allowed to be used in CTK extension? I don’t know. This is more of an EA question than a CTK question, and that’s not an area in which I maintain expertise. I know that some CTK extensions do the crypto in their container app rather than in the appex. This is necessary for technologies, like Core NFC, where the API only works in an app. That process is rather convoluted, but it does work. I helped a developer go down that path once, and my final advice was

I can help if you need to make your android phone as nfc card

we can request for NFC entitlement through their technical support and that will resolve the entitlement issue of Tap and Pay.

This response may be a little late, but just in case, here are some NFC readers you could use: https://www.acs.com.hk/en/products/548/walletmate-mobile-wallet-nfc-reader-apple-vas-google-smart-tap-certified/ https://www.vtapnfc.com/vtap-boxed-readers/