Systems and methods for personal identification and verification

A system for providing personal identity verification and controlling transactions involving cryptography-based electronic money (CBEM), the system comprising:

• one or more computer-readable storage media configured to store a transactions database;
• a central approval server comprising one or more processors programmed to execute computer program instructions that, when executed, cause the central approval server to:
• provide, via an encrypted network, a registration interface for submission of documents for verification of the legal identity of a registrant to create an account for a valid registered user;
• allow only valid registered users to communicate with a client wallet associated with the valid registered user to generate one or more valid multisignature currency addresses;
• allow only multisignature transactions;
• receive at least a portion of one unit of CBEM by verifying a submitted credential with the central approval server;
• record ownership of the CBEM into the transactions database using the one or more valid multisignature currency addresses, wherein generating the one or more multisignature currency addresses requires combining a client public key from the client wallet and an approval public key from the central approval server;
• record CBEM transactions in the transactions database;
• verify the CBEM transaction against one or more transaction approval rules at the central approval server, wherein each of the CBEM transactions is associated with a transaction request, wherein each transaction request is required to be signed using at least two private keys, wherein:
• all transaction requests associated with the CBEM transactions are sent from the client wallets to the central approval server to obtain an approval private key for signing each of the CBEM transactions, wherein the approval private key is sent from the central approval server to a respective one of the client wallets upon approval of the transaction request to obtain the approval private key, wherein a transaction-validation script embedded inside a source code of the system enforces that only pay-to-script-hash multisignature transactions are generated and propagated and prevents signing of the CBEM transactions without the approval private key from the central approval server, wherein the central approval server releases the approval private key in response to:
• receiving, via an API call, a request carrying the submitted credential;
• and
• verifying the submitted credential matches an active credential stored in a client information database;
• the at least two private keys for signing each transaction request include the approval private key from the central approval server and the rest of the at least two private keys is or are each a private key stored in one of the client wallets;
• and
• the approval private key is restricted to be from the central approval server;
• and
• reject transactions requests that are not singed using at least two private keys, wherein transaction requests are only created in the presence of a valid credential, and wherein valid registered users remain pseudonymous to each other in multisignature transactions.