System and Method for Dynamic Fob Synchronization and Personalization

1. A method, comprising: receiving, by a computing system, a request for a transponder, wherein the request indicates one or more requested applications; communicating, by the computing system, with a partner entity to retrieve a cryptographic key associated with access to one of the one or more requested applications; adding, by the computing system, the one or more requested applications to a data object for the requested transponder; adding, by the computing system, the cryptographic key to the data object; and causing, by the computing system, the data object to be downloaded to the requested transponder.

2. The method of claim 1 , further comprising: accessing, by the partner entity, files corresponding to the one of the one or more requested applications on the transponder using the cryptographic key, wherein the accessing occurs during a point of sale transaction.

3. The method of claim 1 , further comprising: updating, by the partner entity, a file structure corresponding to the one of the one or more requested applications on the transponder using the cryptographic key.

4. The method of claim 1 , wherein the cryptographic key is not maintained by any entity other than the partner entity and the transponder after issuance of the transponder.

5. The method of claim 1 , further comprising: retrieving a second cryptographic key from a second partner entity, wherein the second cryptographic key is associated with a second one of the one or more requested applications; and adding the second cryptographic key to the data object.

6. The method of claim 1 , further comprising: storing the data object in an object database; and in response to a request for a replacement transponder, causing the stored data object to be downloaded to a replacement transponder.

7. The method of claim 1 , wherein causing the data object to be downloaded to the requested transponder includes at least one of: transferring the data object to the transponder or transferring the data object to a printer entity and instructing the printer entity to transfer the data object to the transponder.

8. The method of claim 1 , further comprising: receiving an indication that the requested transponder is in communication with a point-of-sale device, wherein the point-of-sale device does not include one or more functions associated with the one of the one or more applications; and providing the one or more functions for the one of the one or more applications using a support server.

9. The method of claim 1 , further comprising issuing the requested transponder.

10. An apparatus, comprising: one or more processors; and one or more memories having program instructions stored thereon that are executable by the one or more processors to cause the apparatus to perform operations comprising: receiving a request for a transponder, wherein the request indicates a requested application; retrieving a cryptographic key from a partner entity, wherein the cryptographic key is associated with access to the requested application; adding the requested application to a data object for the requested transponder; adding the cryptographic key to the data object; and causing the data object to be downloaded to the requested transponder.

11. The apparatus of claim 10 , wherein access to the requested application is restricted to entities with knowledge of the key.

12. The apparatus of claim 10 , wherein the operations further comprise: deleting the cryptographic key after adding it to the data object.

13. The apparatus of claim 10 , wherein the operations further comprise: maintaining the data object in an object database after issuing the requested transponder; and reissuing the requested transponder based on the data object.

14. The apparatus of claim 13 , wherein the operations further comprise, before the reissuing: synchronizing the data object based on information received from a partner entity; and synchronizing the object based on information received from a point-of-sale device in communication with the transponder.

15. The apparatus of claim 10 , wherein the operations further comprise activating the requested transponder.

16. A non-transitory computer-readable medium having instructions stored thereon that are executable by a computing device to perform operations comprising: receiving a request for a transponder, wherein the request indicates a requested application; retrieving a cryptographic key from a partner entity, wherein the cryptographic key is required to access files of the requested application; adding the requested application to a data object for the requested transponder; adding the cryptographic key to the data object; and causing the data object to be downloaded to the requested transponder.

17. The non-transitory computer-readable medium of claim 16 , wherein the operations further comprise: discarding the cryptographic key after adding it to the data object such that the cryptographic key is stored only by the requested transponder and the partner entity.

18. The non-transitory computer-readable medium of claim 16 , wherein the operations further comprise: maintaining the data object in an object database after issuing the requested transponder; and replacing the requested transponder with a new transponder using the maintained data object.

19. The non-transitory computer-readable medium of claim 16 , wherein the operations further comprise: gathering legacy data associated with a user requesting the transponder; and adding the legacy data to the data object.

20. The non-transitory computer-readable medium of claim 16 , wherein causing the data object to be downloaded to the requested transponder includes at least one of: transferring the data object to the transponder or transferring the data object to a fob creation entity and instructing the fob creation entity to transfer the data object to the transponder.