Method and system for recording point to point transaction processing
A method for providing a multi-service platform to entities includes the storage of profiles for a plurality of entities involved in services with other entities, including point to point and business to business transactions, including entities not registered, that can be claimed by each entity, where each entity can provide for roles and hierarchies of authorized users of the platform for that entity, and where the platform is configured to provide, among other services, registration of procurement status for purchase orders in a digital ledger that provides for auditability and immutability.
1. A method for account management in a services platform, comprising:
receiving, by a receiver of a processing server, hierarchy data for an entity, wherein the hierarchy data includes user data for each of a plurality of users, the user data including at least contact data for a respective user;
executing, by the processing server, a query on a memory of the processing server to insert, for each of the plurality of users, a user profile in the memory that includes at least the respective user data and authentication credentials;
electronically transmitting, by a transmitter of the processing server, the authentication credentials included in the respective user profile to each user of the plurality of users using the contact data for the respective user;
receiving, by the receiver of the processing server, at least authentication credentials, revised credentials, and a public key of a cryptographic key pair for each user of the plurality of users;
executing, by the processing server, a query on the memory of the processing server to update, for each of the plurality of users, the user profile in the memory to change the authentication credentials to the revised credentials and include the respective public key;
generating, by the processing server, a ledger data entry for each of the plurality of users, wherein the ledger data entry includes at least the respective public key; and
inserting, by the processing server, the generated ledger data entry for each of the plurality of users into a digital ledger.
2. The method of claim 1 , further comprising:
storing, in the memory of the processing server, an entity profile related to an entity, wherein
the entity profile includes at least an entity identifier and a public key associated with the related entity, and
the hierarchy data further includes the entity identifier.
3. The method of claim 2 , wherein the user profile for each of the plurality of users is stored in the entity profile.
4. The method of claim 1 , wherein
the user data further includes a user role, and
each ledger data entry includes the user role for the respective user.
5. The method of claim 1 , wherein receiving the public key of a cryptographic key pair for each user of the plurality of users includes generating, by the processing server, the cryptographic key pair including the public key and a private key for each of the plurality of users.
6. The method of claim 5 , further comprising:
electronically transmitting, by the transmitter of the processing server, the private key to the respective user to each of the plurality of users using the contact data for the respective user.
7. The method of claim 1 , wherein the digital ledger is a blockchain.
8. The method of claim 7 , wherein each ledger data entry further includes a digital signature generated using a private key of the cryptographic key pair of the respective user.
9. A system for account management in a services platform, comprising:
a receiver of a processing server configured to receive hierarchy data for an entity, wherein the hierarchy data includes user data for a plurality of users, the user data including at least contact data for a respective user;
the processing server configured to execute a query on a memory of the processing server to insert, for each of the plurality of users, a user profile in the memory that includes at least the respective user data and authentication credentials; and
a transmitter of the processing server configured to electronically transmit the authentication credentials included in the respective user profile to each user of the plurality of users using the contact data for the respective user, wherein
the receiver of the processing server is further configured to receive at least authentication credentials, revised credentials, and a public key of a cryptographic key pair for each user of the plurality of users, and
the processing server is further configured to
execute a query on the memory of the processing server to update, for each of the plurality of users, the user profile in the memory to change the authentication credentials to the revised credentials and include the respective public key,
generate a ledger data entry for each of the plurality of users, wherein the ledger data entry includes at least the respective public key, and
insert the generated ledger data entry for each of the plurality of users into a digital ledger.
10. The system of claim 9 , further comprising:
the memory of the processing server configured to store an entity profile related to an entity, wherein
the entity profile includes at least an entity identifier and a public key associated with the related entity, and
the hierarchy data further includes the entity identifier.
11. The system of claim 10 , wherein the user profile for each of the plurality of users is stored in the entity profile.
12. The system of claim 9 , wherein
the user data further includes a user role, and
each ledger data entry includes the user role for the respective user.
13. The system of claim 9 , wherein receiving the public key of a cryptographic key pair for each user of the plurality of users includes generating, by the processing server, the cryptographic key pair including the public key and a private key for each of the plurality of users.
14. The system of claim 13 , wherein the transmitter of the processing server is further configured to electronically transmit the private key to the respective user to each of the plurality of users using the contact data for the respective user.
15. The system of claim 9 , wherein the digital ledger is a blockchain.
16. The system of claim 15 , wherein each ledger data entry further includes a digital signature generated using a private key of the cryptographic key pair of the respective user.