Systems and methods for decryption as a service via a configuration of read-only databases
Systems and methods for decryption of payloads are disclosed herein. In various embodiments, systems and methods herein are configured for decrypting thousands of transactions per second. Further, in particular embodiments, the systems and methods herein are scalable, such that many thousands of transactions can be processed per second upon replicating particular architectural components.
1. A system for fast decryption of one or more payloads, the system comprising:
a frontend server for receiving encrypted payloads;
a plurality of read-only databases operatively connected to the frontend server;
a master read-only database operatively connected to each of the plurality of read-only databases; and
a read/write database operatively connected to the master database, the read/write database for transmitting event messages to the master read-only database, wherein the system is configured for:
receiving event information at the read/write database;
upon receiving the event information at the read/write database, automatically transmitting authentication data to the master read-only database, wherein the authentication data has been updated by the event information;
refreshing the read-only master database to include the authentication data; and
refreshing each of the plurality of read-only databases with authentication data matching the refreshed read-only master database, wherein the authentication data is for determining whether a payload has been transmitted by a tampered device.
2. The system of claim 1 , wherein the authentication data is data for authenticating a particular payload.
3. The system of claim 2 , wherein the authentication data is a serial number or firmware identifier for a particular device configured to transmit the particular payload to the system.
4. The system of claim 3 , wherein the authentication data is an indication of a type of firmware running on a particular device configured to transmit the particular payload to the system.
5. The system of claim 2 wherein the authentication data is for authenticating a particular partner associated with the particular payload.
6. The system of claim 5 , wherein the particular partner is a third-party payment processor configured to transmit the particular payload to the system.
7. A computer-implemented method for fast decryption of one or more payloads, the method comprising the steps of:
providing a frontend server for receiving encrypted payloads;
providing a plurality of read-only databases operatively connected to the frontend server;
providing a master read-only database operatively connected to each of the plurality of read-only databases;
providing a read/write database operatively connected to the master database, the read/write database for transmitting event messages to the master read-only database;
receiving event information at the read/write database;
upon receiving the event information at the read/write database, automatically transmitting authentication data to the master read-only database, wherein the authentication data has been updated by the event information;
refreshing the read-only master database to include the authentication data; and
refreshing each of the plurality of read-only databases with authentication data matching the refreshed read-only master database, wherein the authentication data is for determining whether a payload has been transmitted by a tampered device.
8. The computer-implemented method of claim 7 , wherein the authentication data is data for authenticating a particular payload.
9. The computer-implemented method of claim 8 , wherein the authentication data is a serial number or firmware identifier for a particular device configured to transmit the particular payload to the system.
10. The computer-implemented method of claim 8 , wherein the authentication data is an indication of a type of firmware running on a particular device configured to transmit the particular payload to the system.
11. The computer-implemented method of claim 8 , wherein the authentication data is for authenticating a particular partner associated with the particular payload.
12. The computer-implemented method of claim 11 , wherein the particular partner is a third-party payment processor configured to transmit the particular payload to the system.