Just so you are aware, the HF side in the NExT, you can write to, ( Phone easier/ convenient or the Proxmak ) but you cant change the UID, so depending on your work access system, it may not be compatible or you may have to enroll it ( We can give you some suggestions for this if you need it)
.
Do you have any more information on your work system?
Is it definitely HF? ( 13.56MHz )
Have you scanned your access card/fob with an NFC capable phone using an app like TagInfo?
Did you want to share an image of your fob/card and /or reader?
The more info you provide the easier it is to help you ( If you need it )
Definitely a good option, and it will be the ApexMax for that location.
For the public transport option, which system is it. ( i.e. Public Transport name, city etc. ) some don’t play well with implants, If you do another TagInfo scan, we might be able to answer that for you also. The Apex can emulate some card types but again, you can’t change the UID, so you will have to look at enrolling if it is compatible.
FYI This is generally what we refer to for our numbering
It is better practice to not directly share you TagInfo publically
But to be able to help you, there are some important bits we need.
The chip type: something like
MIFARE Classic (MF1S50) or MIFARE DESFire EV1 etc
and the UID (NUID) Byte total
ie. F3:94:2C:5B would be 4 Bytes
F3:94:2C:5B:12:2B:4C would be 7 Bytes
You could mask them or jumble them up or just tell us how many bytes
This will explain further how to share
If you get stuck on anything just ask.