As @endnode has pointed out, the NFCT peripheral on the nRF52832 can only be used as a NFC Tag (i.e. NFC Forum compliant listening device NFC-A), please see this page on our Infocenter.
I guess there is misunderstanding of role and transport layer on NFC (or ISO14443 to be more precise). Even if you emulate card (PICC) aka slave you do bidirectional communication. And yes, you could develop your own library or HAL layer on top of well documented NFC HW peripheral block on nRF52 if you know what to do (e.g. you've ever implemented some ISO14443 card OS on dedicated HW without having this done by chip vendor). Alternatively (seems more likely given the level of your questions) you should seek some expert and subcontract the job externally.
I guess there is misunderstanding of role and transport layer on NFC (or ISO14443 to be more precise). Even if you emulate card (PICC) aka slave you do bidirectional communication. And yes, you could develop your own library or HAL layer on top of well documented NFC HW peripheral block on nRF52 if you know what to do (e.g. you've ever implemented some ISO14443 card OS on dedicated HW without having this done by chip vendor). Alternatively (seems more likely given the level of your questions) you should seek some expert and subcontract the job externally.
