Search

US-20260127583-A1 - SYSTEMS AND METHODS FOR DATA COMMUNICATION USING A STATELESS APPLICATION

US20260127583A1US 20260127583 A1US20260127583 A1US 20260127583A1US-20260127583-A1

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.

Inventors

  • Alex McMahon
  • Paul Carey
  • Archana Loganathan
  • Wayne Crombie

Assignees

  • CITIBANK, N.A.

Dates

Publication Date
20260507
Application Date
20251231

Claims (20)

  1. 1 - 20 . (canceled)
  2. 21 . A system, comprising: one or more memory-coupled processors programmed to execute instructions causing the one or more memory-coupled processors to: extract, from a shared ledger using a stateless application, transaction information associated with a user, wherein the transaction information has been committed to the shared ledger based on a user initiation, and wherein the stateless application persists configuration data; generate, based on the transaction information, a message file for a transaction between two jurisdictions; provide, for the transaction, the message file to a cross border function, wherein the cross border function causes transfer of funds from a platform user; receive a status update related to the transaction; store an instance of data related to the transaction within an interchange construct that is independent of a first format in which the instance of the data was received; and write the instance of the data in a second format that is different from the first format to a data destination.
  3. 22 . The system of claim 21 , wherein the first format comprises a predetermined electronic data interchange format.
  4. 23 . The system of claim 22 , wherein the interchange construct is independent of the predetermined electronic data interchange format and is based on a predefined set of parameters received in metadata associated with the instance of the data.
  5. 24 . The system of claim 21 , further comprising application code instructions to translate, when stored, the instance of the data to the second format.
  6. 25 . The system of claim 24 , 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.
  7. 26 . The system of claim 21 , 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.
  8. 27 . A method for executing transactions, the method comprising: extracting, from a shared ledger and using a stateless application, transaction information associated with a user, wherein the transaction information has been committed to the shared ledger based on a user initiation, and wherein the stateless application persists configuration data; generating, based on the transaction information, a message file for a transaction between two jurisdictions; providing, for the transaction, the message file to a cross border function, wherein the cross border function causes transfer of funds from a platform user; storing an instance of data related to the transaction within an interchange construct that is independent of a first format in which the instance of the data was received; and writing the instance of the data in a second format that is different from the first format to a data destination.
  9. 28 . The method of claim 27 , wherein the first format comprises a predetermined electronic data interchange format.
  10. 29 . The method of claim 28 , 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.
  11. 30 . The method of claim 27 , further comprising translating the instance of the data to the second format.
  12. 31 . The method of claim 27 , wherein the second format comprises a predefined tamper-proof sequence of data for another data destination comprising a shared ledger function that is coupled to the stateless application executing on one or more computing devices.
  13. 32 . The method of claim 27 , wherein the data destination comprises a shared ledger function that is coupled to the stateless application executing on one or more computing devices and is coupled to at least one client memory-coupled processor.
  14. 33 . The method of claim 32 , 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.
  15. 34 . The method of claim 27 , further comprising receiving a status update related to the transaction.
  16. 35 . One or more non-transitory computer-readable media having instructions embodied thereon, the instructions causing one or more processors to perform operations comprising: extracting, from a shared ledger and using a stateless application, transaction information associated with a user, wherein the transaction information has been committed to the shared ledger based on a user initiation, and wherein the stateless application persists configuration data; generating, based on the transaction information, a message file for a transaction between two jurisdictions; providing, for the transaction, the message file to a cross border function, wherein the cross border function causes transfer of funds from a platform user; storing an instance of data related to the transaction within an interchange construct that is independent of a first format; and writing the instance of the data in a second format that is different from the first format to a data destination.
  17. 36 . The one or more non-transitory computer-readable media of claim 35 , wherein the first format comprises a predetermined electronic data interchange format.
  18. 37 . The one or more non-transitory computer-readable media of claim 36 , 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.
  19. 38 . The one or more non-transitory computer-readable media of claim 36 , wherein the data destination comprises a shared ledger function that is coupled to the stateless application executing on one or more computing devices and is coupled to at least one client memory-coupled processor.
  20. 39 . The one or more non-transitory computer-readable media of claim 36 , wherein the instructions further cause the one or more processors to receive a status update related to the transaction.

Description

CROSS REFERENCE TO RELATED APPLICATIONS This application is a continuation of U.S. patent application Ser. No. 18/820,219, filed Aug. 29, 2024, which is a continuation of U.S. patent application Ser. No. 17/967,284, filed Oct. 17, 2022 (now U.S. Pat. No. 12,112,319 issued October 8, 2024), which is a continuation of U.S. patent application Ser. No. 15/641,500, filed Jul. 5, 2017 (now U.S. Pat. No. 11,507,947 issued November 22, 2022). The content of the foregoing application is incorporated herein in its entirety by reference. FIELD OF THE INVENTION The present invention relates generally to the field of electronic data communication, and more particularly to systems and methods for orchestration of electronic data communication using a stateless application. BACKGROUND Current funds transfer systems present many challenges to participating entities, such as banks. For example, it is difficult to track and audit funds transfers as they pass through multiple correspondent banks. There is also a risk, for example, of loss of critical information about payments as payment messages are transferred across banks and borders. Other challenges include, for example, lack of currency exchange transparency. There is a present need for a solution that resolves all of the foregoing issues and provides, for example, improved methods and systems for communication of electronic data in a stateless environment that assure, for example, that funds may be received into an account, such as a client account, and represented in a tamper-proof way and that enable payment from that account on receipt of a tamper-proof representation of value. SUMMARY OF THE INVENTION Embodiments of the invention employ computer hardware and software, including, without limitation, one or more processors coupled to memory and non-transitory computer-readable storage media with one or more executable programs stored thereon which instruct the processors to perform the methods described herein. Such embodiments are directed to technological solutions that may involve systems that include, for example, at least one memory-coupled entity processor 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. In an aspect of the system for embodiments of the invention, the data may be received in the first format from the data source comprising, for example, an entity financial system processor. In an additional aspect, the data may be received from the entity financial system processor in the first format comprising, for example, a predetermined electronic data interchange format. In a further aspect, the predetermined electronic data interchange format may comprise, for example, a metadata repository containing descriptions of messages and business processes and a maintenance process for contents of the metadata repository. In another aspect, the predetermined electronic data interchange format may comprise, for example, a representation of cash management and status messages. In still another aspect of the system for embodiments of the invention, the stateless application executing on the at least one entity processor may cause the at least one entity processor, for example, to store the received data within an interchange construct independent of the first and second formats. In a still further aspect, the stateless application executing on the at least one entity processor may cause the at least one entity processor, for example, to store the received data within the interchange construct based at least in part on a predefined set of parameters. In a further aspect, the predefined set of parameters may comprise mandatory, conditional, and optional fields. In additional aspects, the predefined set of parameters may further comprise, for example, mandatory fields across all countries, conditional fields for a specific country, and optional fields correlating a particular transaction to a set of systems in a transaction to which the received data relates. In another aspect of the system for embodiments of the invention, the stateless application executing on the at least one entity processor may, for example, cause the at least one entity processor to translate the received data to the second format comprising a predefined tamper-proof sequence of data. In further aspects, for example, the stateless application executing on the at least one entity processor may cause the at least one entity processor to translate the received data to the tamper-proof sequen