Abstract: Methods and systems for establishing a chain of relationships are disclosed. An identity verification platform receives a first request for registration comprising an identification of a first user, identification of an entity, and a relationship between the first user and the entity; verifies the identity of the first user and the relationship between the first user and the entity; and verifies that the entity is legitimate. Once a relationship between a first individual, invited by the first user, and the entity is confirmed, the platform creates a custom badge representing the relationship between the first individual and the entity for display on the entity's website. The platform receives an identification of a selection by an end user of the custom badge and, responsive to receiving the identification of the selection, renders, on a domain controlled by the identity verification platform, a verification that the relationship between the first individual and the entity is valid.

Abstract: Methods and systems for establishing a chain of relationships are disclosed. An identity verification platform receives a first request for registration comprising an identification of a first user, identification of an entity, and a relationship between the first user and the entity; verifies the identity of the first user and the relationship between the first user and the entity; and verifies that the entity is legitimate. Once a relationship between a first individual, invited by the first user, and the entity is confirmed, the platform creates a custom badge representing the relationship between the first individual and the entity for display on the entity's website. The platform receives an identification of a selection by an end user of the custom badge and, responsive to receiving the identification of the selection, renders, on a domain controlled by the identity verification platform, a verification that the relationship between the first individual and the entity is valid.

Abstract: Methods and systems for establishing a chain of relationships are disclosed. An identity verification platform receives a first request for registration comprising an identification of a first user, identification of an entity, and a relationship between the first user and the entity; verifies the identity of the first user and the relationship between the first user and the entity; and verifies that the entity is legitimate. Once a relationship between a first individual, invited by the first user, and the entity is confirmed, the platform creates a custom badge representing the relationship between the first individual and the entity for display on the entity's website. The platform receives an identification of a selection by an end user of the custom badge and, responsive to receiving the identification of the selection, renders, on a domain controlled by the identity verification platform, a verification that the relationship between the first individual and the entity is valid.

Abstract: Systems and methods are described for policy-validated transactions using a centralized or distributed ledger. A request to execute a transaction and a transaction signature is received from a user's computing device. The transaction signature is generated with a private key of the user's computing device. The transaction corresponds to a token associated with the user's computing device and the transaction is subject to a first policy of a set of one or more policies. The transaction signature corresponds to the request to execute the transaction is determined using a public key of the user's computing device. In response to the determination, the token associated with the user's computing device is retrieved from the centralized or distributed ledger. The transaction is executed if the token is associated with the first policy and the token is valid.

Abstract: Systems and methods are described for policy-validated transactions using a centralized or distributed ledger. A request to execute a transaction and a transaction signature is received from a user's computing device. The transaction signature is generated with a private key of the user's computing device. The transaction corresponds to a token associated with the user's computing device and the transaction is subject to a first policy of a set of one or more policies. The transaction signature corresponds to the request to execute the transaction is determined using a public key of the user's computing device. In response to the determination, the token associated with the user's computing device is retrieved from the centralized or distributed ledger. The transaction is executed if the token is associated with the first policy and the token is valid.