Systems and methods for validating transactions
Systems and methods of validating transactions are provided. An exemplary system includes a server including a memory and a processor. The server is configured to: receive from an entity a transaction validation request of validating a transaction; validate the transaction; generate a logging record of the transaction validation; cryptographically hash the logging record to create a hashed logging record; digitally sign the hashed logging record using a key to create a signed hashed logging record; and transmit the signed hashed logging record to a computer device.
1 . A system for validating transactions, comprising a server including a memory and a processor, wherein the server is configured to:
receive, from a second device, a transaction validation request of validating a transaction;
validate the transaction;
generate a logging record of the transaction validation;
cryptographically hash the logging record to create a hashed logging record;
assemble a public key from one or more parts of the public key;
digitally sign the hashed logging record using the public key to create a signed hashed logging record; and
transmit, to a first device, the signed hashed logging record.
2 . The system according to claim 1 , wherein the public key is obfuscated.
3 . The system according to claim 1 , wherein the public key is managed by a hardware security module of the server.
4 . The system according to claim 1 , wherein an entity digitally signs the hashed logging record using the public key by accessing the server.
5 . The system according to claim 1 , wherein the logging record comprises a monotonically increasing sequence number.
6 . The system according to claim 1 , wherein the logging record comprises a hash of hashes of previous logging records.
7 . The system according to claim 1 , wherein the signed hashed logging record is transmitted to the first device in real time.
8 . The system according to claim 2 , wherein the public key is obfuscated in the code of a transaction validation service.
9 . A method for validating transactions performed by a server, comprising:
receiving, from a second device, a transaction validation request of validating a transaction;
validating the transaction;
generating a logging record of the transaction validation;
cryptographically hashing the logging record to create a hashed logging record;
assembling a public key from one or more parts of the public key;
digitally signing the hashed logging record using the public key to create a signed hashed logging record; and
transmitting, to a first device, the signed hashed logging record.
10 . The method according to claim 9 , wherein the signed hashed logging record is transmitted to the first device in batch.
11 . The method according to claim 9 , wherein the signed hashed logging record is transmitted to the first device through file logging service.
12 . The method according to claim 9 , wherein the signed hashed logging record is transmitted to the first device through a messaging service.
13 . The method according to claim 9 , wherein the server is further configured to generate a heartbeat-patterned message to monitor runtime of the server.
14 . The method according to claim 13 , wherein the heartbeat-patterned message comprises timestamps indicating a time interval.
15 . The method according to claim 9 , wherein the logging record comprises an event identity, event type information, a timestamp, and event details.
16 . A non-transitory, computer-readable medium comprising instructions for validating transactions that, when executed on a computer arrangement, cause the computer arrangement to perform actions comprising:
receiving, from a second device, a transaction validation request of validating a transaction;
validating the transaction;
generating a logging record of the transaction validation;
cryptographically hashing the logging record to create a hashed logging record;
assembling a public key from one or more parts of the public key;
digitally signing the hashed logging record using the public key to create a signed hashed logging record; and
transmitting, to a first device, the signed hashed logging record.
17 . The non-transitory, computer-readable medium according to claim 16 , wherein the public key is managed by a hardware security module.
18 . The non-transitory, computer-readable medium according to claim 16 , wherein the logging record comprises an event identity, event type information, a timestamp, and event details.
19 . The non-transitory, computer-readable medium according to claim 16 , wherein the logging record comprises a hash of hashes of previous logging records.
20 . The non-transitory, computer-readable medium according to claim 16 , wherein the actions further comprises generating a heartbeat-patterned message.