Abstract: A pool of game outcomes is generated on a smart card that is associated with a gaming machine. The pool of game outcomes is identical to a previously generated pool of game outcomes. A seed is created and a pool of game outcomes is generated using the seed, a pseudorandom number generator (pRNG), game rules, and a pool size. The seed, a game identifier associated with the game rules, and the pool size are stored in a database that is remote from the smart card. The seed, the game identifier, and the pool size are usable for audit purposes to recreate the pool of game outcomes using the same pRNG and the same game rules that are used to generate the original pool of game outcomes. A memory of the smart card associated with the gaming machine is loaded with the seed. The smart card includes same pRNG that is used to generate the original pool of game outcomes.

Abstract: A method is provided to cryptographically link a physical object to a digital version of the physical object and to maintain in a database of an object management system data regarding the physical object and the digital version of the physical object. The digital version of the physical object is represented as a digital file. The object management system includes a data record for a Near Field Communication (NFC) tag that is associated with the physical object. The NFC tag has a memory and a secure process for obtaining access to the memory. A hash generator generates a Non-Fungible-Token (NFT) of the digital file. The generated NFT of the digital file is added to the database in the data record for the NFC tag. Data related to the generated NFT of the digital file is added to the memory of the NFC tag by a cryptographically secure process, thereby cryptographically linking the physical object to a digital version of the physical object via the NFC tag that is associated with the physical object.

Abstract: A smart card architecture includes a run-time environment, a card manager, one or more security domains, a provider application and an issuer application. One or more APIs provide communication. The life cycle of the card and card manager includes states: Pre-production, Ready, Initialized, Secured, Locked and Terminated. The life cycle of an application includes states: Installed, Selectable, Personalized, Blocked, Locked and Deleted. A card registry keeps track of card manager and application data elements. The functionality of a security domain on a smart card is extended to allow it to perform delegated management of smart card applications: delegated loading, installation and/or deletion of an application. A provider of an application is assured of more direct control and management of their application, yet an issuer still maintains some control over the management of the card.

Abstract: A smart card architecture includes a run-time environment, a card manager, one or more security domains, a provider application and an issuer application. One or more APIs provide communication. The life cycle of the card and card manager includes states: Pre-production, Ready, Initialized, Secured, Locked and Terminated. The life cycle of an application includes states: Installed, Selectable, Personalized, Blocked, Locked and Deleted. A card registry keeps track of card manager and application data elements. The functionality of a security domain on a smart card is extended to allow it to perform delegated management of smart card applications: delegated loading, installation and/or deletion of an application. A provider of an application is assured of more direct control and management of their application, yet an issuer still maintains some control over the management of the card.

Abstract: The embodiments of the present invention teaches a system and method which allows card issuers to securely add applications during the lifetime of the card after the card has already been issued (post issuance). The system and method according to embodiments of the present invention allows the loading of an application and/or objects from an application server via a card acceptance device and its supporting system infrastructure delivery mechanism, onto a card post issuance in a secure and confidential manner.

Abstract: A system and method allow card issuers to securely add applications during the lifetime of the card after the card has already been issued (post issuance). Loading of an application and/or objects from an application server via a card acceptance device (and its supporting system infrastructure delivery mechanism) onto a card post issuance is performed in a secure and confidential manner. A smart card includes a card domain application that manages the card. Any number of security domain applications on the card provide security for loaded applications by managing keys; each application is associated with a security domain. Each of the card domain and security domains has a command interface for off-card communication, and an API for internal card use. The card life cycle includes the states of masked, initialized, load secured and blocked. An application life cycle includes the states of not available, loaded, installed, registered, personalized, activated and blocked. An application can block the card.