Abstract: Systems and methods for using a cryptogram lockbox are disclosed. In one embodiment, in a merchant-specific cryptogram lockbox comprising at least one computer processor, a method for generating a cryptogram locally using a cryptogram lockbox may include: (1) receiving, from merchant backend, a request for a cryptogram comprising an account identifier received from a customer in a transaction; (2) generating a cryptogram for the account identifier using a limited use key for the account identifier; and (3) returning the cryptogram to the merchant backend. The merchant may conduct the transaction using the cryptogram.

Abstract: Systems and methods for token vault synchronization are disclosed. In one embodiment, in a third party provider information processing apparatus comprising at least one computer processor, a method for token vault synchronization using a third party provider may include (1) receiving, from a computer program executed by an electronic device associated with a customer, a request to provision an identifier for an account associated with the customer to the computer program; (2) generating the identifier; (3) creating an association of the identifier and the account; (4) storing the association of the identifier and the account in a third party provider vault; (5) electronically communicating the association of the identifier and the account to an issuer of the account; (6) receiving a cryptogram from the issuer; (7) electronically communicating the cryptogram and the association of the identifier and the account to the computer program.

Abstract: Systems and methods for token vault synchronization using a distributed ledger are disclosed. In one embodiment, in a distributed token ledger network comprising a plurality of nodes, each node associated with a token ledger and comprising at least one computer processor, a method for token vault synchronization using a distributed ledger may include: (1) a node receiving a lifecycle event for a payment token; (2) the node writing the lifecycle event to a token ledger for the node; (3) committing the lifecycle event to the distributed token ledger after the plurality of nodes in the distributed token ledger agree to committal; (4) a watcher at the node detecting the commitment of the lifecycle event to the distributed token ledger; and (5) the watcher communicating the lifecycle event to a non-node participant.