A computing device, comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the computing device to: store, in one or more smart contracts maintained by a distributed network system, a revocation database comprising security certificates to be treated as invalid and an audit database comprising previously received nonce values; obtain, from a requesting device, a request to execute a transaction, wherein the request comprises transaction request data indicating: a security certificate associated with the requesting device; and a receiving party, a transaction value, and a nonce; transmit a receiving party authorization request to a client device associated with the receiving party; obtain, from the client device associated with the receiving party, authorization data associated with the receiving party; wherein the instructions cause the computing device to validate the transaction request by causing the computing device to: compare the security certificate associated with the requesting device with the invalid security certificates stored in the revocation database; compare the nonce to the audit database to determine that the nonce has not been previously received; determine that the authorization data associated with the receiving party was obtained during a threshold time period of obtaining the transaction request; and decrypt the authorization data obtained from the receiving party using a public key associated with the receiving party; wherein the instructions further cause the computing device to: initiate, based on the request to execute the transaction and the validation of the transaction request, a transfer of the transaction value from a wallet associated with the requesting device to a wallet associated with the client device by sending data comprising an indication to execute a smart contract to the distributed network system; and updating the audit database based on the nonce. one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the computing device to: store, in one or more smart contracts maintained by a distributed network system, a revocation database comprising security certificates to be treated as invalid and an audit database comprising previously received nonce values; obtain, from a requesting device, a request to execute a transaction, wherein the request comprises transaction request data indicating: a security certificate associated with the requesting device; and a receiving party, a transaction value, and a nonce; store, in one or more smart contracts maintained by a distributed network system, a revocation database comprising security certificates to be treated as invalid and an audit database comprising previously received nonce values; obtain, from a requesting device, a request to execute a transaction, wherein the request comprises transaction request data indicating: a security certificate associated with the requesting device; and a receiving party, a transaction value, and a nonce; a security certificate associated with the requesting device; and a receiving party, a transaction value, and a nonce; transmit a receiving party authorization request to a client device associated with the receiving party; obtain, from the client device associated with the receiving party, authorization data associated with the receiving party; wherein the instructions cause the computing device to validate the transaction request by causing the computing device to: compare the security certificate associated with the requesting device with the invalid security certificates stored in the revocation database; compare the nonce to the audit database to determine that the nonce has not been previously received; determine that the authorization data associated with the receiving party was obtained during a threshold time period of obtaining the transaction request; and decrypt the authorization data obtained from the receiving party using a public key associated with the receiving party; compare the security certificate associated with the requesting device with the invalid security certificates stored in the revocation database; compare the nonce to the audit database to determine that the nonce has not been previously received; determine that the authorization data associated with the receiving party was obtained during a threshold time period of obtaining the transaction request; and decrypt the authorization data obtained from the receiving party using a public key associated with the receiving party; initiate, based on the request to execute the transaction and the validation of the transaction request, a transfer of the transaction value from a wallet associated with the requesting device to a wallet associated with the client device by sending data comprising an indication to execute a smart contract to the distributed network system; and updating the audit database based on the nonce.