Data (particularly encrypted data) in transit can be captured and sometimes replayed to attackers benefit. Adding a sealed marker (expiration value, transaction number) can protect against these replay scenarios (e.g., use a hash of data known to the application, but not the user, to protect against replay. Any other crypto function is either too slow, or not secure).