# US 12,112,319 B1 · Systems and methods for data communication using a stateless application > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,112,319 B1 - Document ID: US12112319B1 - Status: Granted - Kind: B1 - Application number: 17/967,284 - Filed: 2022-10-17 - Granted: 2024-10-08 - Earliest claimed: 2017-07-05 - Assignees: Citibank, N.A. - Applicants: Citibank, N.A. - Inventors: Alex McMahon; Paul Carey; Archana Loganathan; Wayne Crombie - Web page: https://patentgrep.com/patent/US12112319B1 ## CPC - G06Q 20/382: {insuring higher security of transaction} - G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes} - G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures - G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems - G06Q 20/38: Payment protocols; Details thereof - G06Q 20/381: {Currency conversion} - G06Q 40/04: Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Systems and methods for communication of electronic data in which one or more memory-coupled entity processors programmed to execute a stateless application that persists no data except configuration data in the stateless application and causes the at least one entity processor to receive data in a first format from a data source to which the stateless application executing on the at least one entity processor is loosely coupled; translate the received data to a second format for a data destination; and submit the data in the second format to the data destination to which the stateless application executing on the at least one entity processor is also loosely coupled. ## Claims ### Claim 1 A system, comprising: one or more memory-coupled processors programmed to execute a stateless application that persists no data except configuration data in the stateless application itself, the stateless application causing the one or more memory-coupled processors to: store an instance of data received from a second processor within an interchange construct that is independent of a first format in which the instance of the data was received; discard the instance of the data in the first format as the instance of the data is read without discarding the configuration data of the stateless application; and write the instance of the data in a second format that is different from the first format to a data destination associated with a third processor without persisting any of the instance of the data received, stored, or written in the stateless application except for the configuration data. ### Claim 2 (depends on 1) The system of claim 1, wherein the first format comprises a predetermined electronic data interchange format. ### Claim 3 (depends on 2) The system of claim 2, wherein the interchange construct is independent of the predetermined electronic data interchange format and is based at least in part on a predefined set of parameters received in metadata associated with the instance of the data. ### Claim 4 (depends on 1) The system of claim 1, wherein the second processor is separate from the one or more memory-coupled processors and is coupled to the stateless application executing on the one or more memory-coupled processors. ### Claim 5 (depends on 1) The system of claim 1, further comprising application code instructions to translate, when stored, the stored instance of the data to the second format. ### Claim 6 (depends on 5) The system of claim 5, wherein the second format comprises a predefined tamper-proof sequence of data for another data destination comprising a shared ledger function operating on a fourth processor that is separate from the one or more memory-coupled processors and is coupled to the stateless application executing on the one or more memory-coupled processors and is coupled to at least one client memory-coupled processor associated with a client. ### Claim 7 (depends on 1) The system of claim 1, wherein the data destination comprises a shared ledger function operating on the third processor that is separate from the one or more memory-coupled processors is coupled to the stateless application executing on the one or more memory-coupled processors and is coupled to at least one client memory-coupled processor. ### Claim 8 (depends on 1) The system of claim 1, wherein the one or more memory-coupled processors of a first user of a consortium of users share a distributed private blockchain ledger with one or more processors of each of a plurality of other users of the consortium of the users. ### Claim 9 A method to execute a stateless application that persists no data except configuration data in the stateless application itself, comprising: storing, by one or more computing devices, an instance of data received from a second processor within an interchange construct that is independent of a first format in which the instance of the data was received; discarding, by the one or more computing devices, the instance of the data in the first format as the instance of the data is read without discarding the configuration data of the stateless application; and writing, by the one or more computing devices, the instance of the data in a second format that is different from the first format to a data destination operating on a third processor without persisting any of the instance of the data received, stored, or written in the stateless application except for the configuration data. ### Claim 10 (depends on 9) The method of claim 9, wherein the first format comprises a predetermined electronic data interchange format. ### Claim 11 (depends on 10) The method of claim 10, wherein the interchange construct is independent of the predetermined electronic data interchange format and is based at least in part on a predefined set of parameters received in metadata associated with the instance of the data. ### Claim 12 (depends on 9) The method of claim 9, wherein the second processor is separate from the one or more computing devices and is coupled to the stateless application executing on the one or more computing devices. ### Claim 13 (depends on 9) The method of claim 9, further comprising translating the instance of the data to the second format. ### Claim 14 (depends on 9) The method of claim 9, wherein the second format comprises a predefined tamper-proof sequence of data for another data destination comprising a shared ledger function operating on a fourth processor that is separate from the one or more computing devices and is coupled to the stateless application executing on the one or more computing devices and is coupled to at least one client memory-coupled processor associated with a client. ### Claim 15 (depends on 9) The method of claim 9, wherein the data destination comprises a shared ledger function operating on the third processor that is separate from the one or more computing devices and is coupled to the stateless application executing on the one or more computing devices and is coupled to at least one client memory-coupled processor. ### Claim 16 (depends on 9) The method of claim 9, wherein the one or more computing devices of a first user of a consortium of users with one or more processors of each of a plurality of other users of the consortium of the users. ### Claim 17 A computer program product, comprising: a non-transitory computer-readable medium having computer-readable program instructions embodied thereon, the computer-readable program instructions comprising instructions to: store an instance of data received from a second processor within an interchange construct that is independent of a first format in which the instance of the data was received; discard the instance of the data in the first format as the instance of the data is read without discarding configuration data of a stateless application; and write the instance of the data in a second format that is different from the first format to a data destination operating on a third processor without persisting any of the instance of the data received, stored, or written in the stateless application except for the configuration data. ### Claim 18 (depends on 17) The computer program product of claim 17, wherein the first format comprises a predetermined electronic data interchange format. ### Claim 19 (depends on 18) The computer program product of claim 18, wherein the interchange construct is independent of the predetermined electronic data interchange format and is based at least in part on a predefined set of parameters received in metadata associated with the instance of the data. ### Claim 20 (depends on 19) The computer program product of claim 19, wherein the computer-readable program instructions are executed by at least one memory-coupled entity processor, and wherein the second processor is separate from the at least one memory-coupled entity processor and is coupled to the stateless application executing on the at least one memory-coupled entity processor.