Oof, that burned-code scheme sounds like it has some painfully sharp UX edges if something goes awry in the new code resync portion.
But I'm guessing that's for serious security, where going to the guard shack is preferable to letting anyone unauthorized in?
Some cards use some kind of challenge-response but are weak and are easily crackable.
Some cards have an anti-copy protection based on rolling codes, be careful with these. The idea is that when you use it to, say, open a door, the card sends a code to the reader and if correct, that code is burned and the reader replies with the next code, which is stored in the card for the next time, making every other copy (possibly including the original) unusable. If the card emulator doesn't store the rolling code, you are completely locked out.
Some cards have a proper challenge-response mechanism that works and can't be easily copied.