RU2331110C2 - Computer system and method of money transfer - Google Patents

Abstract

FIELD: physics; computer technology.

SUBSTANCE: invention relates to the computer system of money transfer. The system includes many agent terminals, where agents work giving the service of money transfer; they are connected through a network of transferring data. The system includes a depository of data about accounts of the agents, storing data about accounts for each agent and the depository of data about the transactions, storing data about transactions for the transactions which are carried out by agents, carrying out remittances from the sending subject to the receiving subject. When data are entered into the terminal of the agent by the sending agent causing the carrying out of the money transfer, required by the sending subject, to the receiving subject data are transferred in a control system of remittance. The entered data identify the sending and receiving subjects, sending agent and receiving agent who should pay the money translated to it to the receiving subject or each receiving subject, and enter the name in the depository of data about transactions in the form of transaction, at data about accounts of agents in the depository of data about accounts of agents for sending and receiving agents update.

EFFECT: simplification of the system and method of money transfer.

42 cl, 9 dwg

Description

The present invention relates to a computer system and method for transferring money.

There are many services available for transferring money from a sender to a recipient. One method offered by money transfer companies requires the sender to come to the company’s office requesting money to be sent to the recipient, for example, abroad. One office closest to the recipient is determined, and money is transferred to this office. When the money arrives at this office, the recipient can come to this office and receive money, for example, in cash or by check. The problem with this system is that there is a significant time delay between the order to transfer money and the actual receipt of money. This method, however, really has the advantage that the sender does not need to have an account with the organization through which the money is transferred.

Another way in which money can be transferred is by transferring funds between accounts, for example between bank accounts. Although this method of transferring funds can be quick, it requires the sender and receiver to have accounts with the financial institution involved in the transfer.

Thus, it is an object of the present invention to provide simplified and efficient money transfer systems and methods.

According to a first aspect of the present invention, there is provided a computer system and a money transfer method for performing a money transfer service for transferring money from a sending entity, such as an individual or company, to at least one receiving entity, such as a person or company. There are many agent terminals on which money transfer service agents work. Agent terminals are interconnected via a data network, which may comprise any conventional data network, such as a wired network such as the Internet, or a wireless network. A money transfer controller is connected to the network to control the execution of the money transfer service. Agents are registered using the money transfer controller, in addition, account information for each agent is stored in the money transfer controller. A transaction data repository is also provided to store transaction data for transactions carried out by agents that transfer money from senders to recipients.

In order to start a money transfer, the agent terminal is used by the agent to enter data that identifies the sender, the specific recipient or each recipient, the sending agent and at least one receiving agent. The data also indicates the amount of money to be transferred. The entered data is received by the money transfer controller, and the transaction data record is stored in the transaction data warehouse. Just as the result of a transaction, the agent account information for the sending agent is updated based on the transaction.

Thus, in accordance with this embodiment of the present invention, a money transfer system is provided that does not require the sending entity or the receiving entity to have an account. The sending entity may simply instruct the agent of the money transfer service to complete the transfer, which is reflected in the agent’s account. Thus, the money transfer system is based on a network of agents, each of which is registered for the service and has accounts for the service. All transactions carried out by the agent are added to his account, in this way a regular money transfer service is provided, which has a network of agents that allows entities to transfer money between themselves without the need to have any relation to the money transfer service or between themselves.

In one embodiment, the money transfer system may provide for a currency-independent money transfer. The sending currency does not have to be the same as the receiving currency. In this embodiment, the money transfer controller includes exchange rate data enabling currency conversion. This allows not only the sending and receiving currencies to be different based on the exchange rate, but it also allows the agent account information to be in the agent’s local currency based on the exchange rate data involved in the accumulated transactions. Currency exchange may be direct or indirect through at least one intermediate currency.

In another embodiment of the present invention, the money transfer controller includes a transaction monitoring tool (monitor) for monitoring transactions. This enables transactions that meet predetermined criteria, for example, contain suspicious or incorrect transactions, to require additional information from the sender. The requirement for additional information for suspicious or incorrect transactions is a function of the rules of compliance with the practice of money laundering. Providing additional information by the sender helps inspectors to comply with the rules governing the practice of money laundering to detect potential money laundering operations. Based on the input of additional information, the money transfer controller can automatically block the transaction if it is determined that the stored rules of compliance with the money laundering practice have been violated.

In addition to, or instead of monitoring and using additional data, a transaction can be monitored against predetermined criteria to determine whether to allow this transaction. For example, a transaction can be compared with rules of conformity to the practice of money laundering to determine whether they are violated and, if so, to block the transaction. Alternatively or in addition, transaction monitoring can be performed, and transactions can be used in conjunction with agent account information to determine whether the transaction should continue. For example, if a transaction causes a change in agent account information outside predetermined criteria, then the transaction may be blocked. This provides automatic credit control, for example, allowing to block transactions until the agent’s account is improved, for example, by paying some of the outstanding debt resulting from previous transactions.

In one embodiment of the present invention, since agent account information and transaction data are stored centrally, this allows for mutual compensation of claims and obligations on agent accounts for agents with respect to other agents. Agents have access to their accounts and can monitor and manage their accounts.

In one embodiment of the present invention, the money transfer controller provides an interface that allows agents to register as primary agents and to register other agents as subagents. If an agent registers subagents, then it assumes responsibility for the transactions of these subagents. Thus, the account data for these subagents is related to the account data of the main agent, and in this way all transactions of the subagents are to some extent managed by the main agent. The organization of subagents and main agents can be hierarchical, and thus the subagents themselves can be the main agents for their own subagents. However, if the main agent is also a subagent, then the financial activities of the subagents of the main agents, which are also subagents, are the responsibility of the main agent at the top of the hierarchical tree.

In one embodiment, when the main agent has registered subagents, the transfer terminal that the main agent is running on may include a domain money transfer controller to control the execution of the money transfer service between agents in the group of agent terminals running the agents registered as subagents of the main agent. The domain money transfer controller also includes domain agent account data for the agent group and domain transaction data for transactions between agents in the agent group. This embodiment of the present invention provides a hub-and-spoke type money transfer system in which subagents can transfer money to other subagents of the same main agent or main agent using a domain money transfer controller implemented on an agent terminal, on which the main agent works. Thus, money transfers between subagents and the main agent can occur on a local basis without the need to contact the hub “nave” the main money transfer controller.

In one embodiment of the present invention, transaction data entered from an agent terminal identifies a sender and a plurality of recipients. In other words, the data represents a combined transaction directed to multiple recipients. This allows the sender to fulfill one request to the agent to send different amounts in different currencies to different recipients in the same transaction with the agent. This simplifies the transaction with the agent and within the money transfer controller, transaction data can be stored as a single sending transaction indexed for the sending entity, and / or as a set of receiving transactions indexed for each receiving entity. Alternatively or in addition, transaction data for a transaction may comprise one send transaction indexed for the sending agent and a plurality of receive transactions indexed for each receiving agent.

In a preferred embodiment of the present invention, the money transfer system comprises a World Wide Web (Web) based service running over an Internet Protocol (IP) network, such as the Internet. The money transfer controller contains a Web server system available for agent terminals using the Web interface. Agent terminals contain computers that implement a Web browser application that allows access to the Web interface of the server system.

In one embodiment of the present invention, in order to eliminate the need for senders who regularly use the money transfer service to repeatedly enter personal data, the sender can be equipped with a device such as a smart card or other storage device that can be read on the terminal agent to automatically enter data identifying the sender.

In accordance with another aspect of the present invention, there is provided a computer system and a money transfer method performing a money transfer service for transferring money from a sender to a plurality of recipients in which a plurality of terminals are interconnected via a data network. The money transfer controller is connected to a data network to control the execution of the money transfer service. The money transfer controller includes a transaction data warehouse that stores transaction data for transactions that transfer money from the sender to the recipients. Data is entered on the terminal in order to cause the transfer of money from the sender to at least one recipient. Data is transferred from the terminal to the money transfer controller. The data identifies the sender and the recipients, and the money transfer controller writes data to the transaction data store in the form of a transaction from the sender to multiple recipients. The money transfer controller also allocates the transaction to each recipient and sends the data identifying the allocation for the respective recipients to at least one terminal in order to be able to complete the money transfer to the respective recipients.

Thus, in accordance with this aspect of the present invention, the sender can complete a separate transaction at a terminal of a money transfer system, in which the transaction requires the transfer of money to more than one recipient, which can be located on more than one terminal. Thus, although the money transfer controller can store one transaction for the sender, it must be allocated appropriately to each recipient to ensure that the money intended for the recipient is sent to the terminal to complete the money transfer.

In this embodiment of the present invention, senders and recipients can work at the terminals to provide a simple way to transfer funds from one sender to multiple recipients in one transaction at a time.

In another embodiment of the present invention, money transfer service agents operate on the terminals. Agents register for the service and have accounts for which transactions are recorded. Senders therefore contact agents and negotiate with agents to pay for sending money to recipients. The receiving agents for the recipients are identified, and the money is made available immediately by the specific receiving agent or by each receiving agent that operates on the agent terminal for receiving by the recipients.

In one embodiment, the money transfer controller stores the entered data as a single transaction indexed by the sender.

In another embodiment of the present invention, the money transfer controller is intended to save the entered data in the form of a plurality of related transactions connected by the sender and indexed by the recipient.

According to another aspect of the present invention, there is provided a “hub and spoke” type computer money transfer system performing a money transfer service for transferring money from a sender to at least one recipient. The system contains many agent terminals on which money transfer service agents work. The terminals of the agents are interconnected via a data network, to which a nodal controller (“hub”) is connected to transfer money to control the execution of the service for transferring money between unrelated agents. Associated agents contain child agents of the common parent agent. The central money transfer management system also includes a transaction data store that stores transaction data for transactions between unrelated agents that transfer money from the sender to at least one recipient, and an agent data store that contains relationships between agents that identify the parent hierarchy and affiliated agents.

At least one terminal of the agent on which the parent agent is operating comprises a peripheral money transfer controller (“knitting needle”) for controlling the execution of the money transfer service for transferring money between related agents. The money transfer peripheral controller also contains a local transaction data repository that stores transaction data for transactions between related agents that transfer money from the sender to at least one recipient, and an agent data repository that stores relations between agents that identify the hierarchy of parent and child agents .

When data is entered at the terminal by the sending agent, causing the transfer of money at the request of the sender to at least one recipient, the entered data identifies the sender and the recipient, the sending agent and at least one receiving agent who must pay the money transferred to him to a particular recipient or to each recipient . The entered data is transmitted either to the nodal money transfer controller or to the peripheral money transfer controller. Data is transferred to the nodal money transfer controller if the receiving agent, identified in the data, is not associated with the sending agent. The nodal money transfer controller writes the entered data to the transaction data warehouse in the form of a transaction from the sending agent to at least one receiving agent for the sender and at least one recipient and transmits information about all transactions to a specific agent terminal or to each agent terminal on which a specific receiving agent or each receiving agent is running.

If the data is sent to the peripheral money transfer controller, the peripheral money transfer controller writes the entered data to the local transaction data repository in the form of a transaction from the sending agent to at least one receiving agent for the sender and at least one receiver and transmits the transaction information to a specific agent terminal or to each agent terminal on which a particular receiving agent or each receiving agent is running.

Thus, in accordance with this aspect of the present invention, it is permissible for the peripheral money transfer controllers to process money transfers between related agents, which are either the agent working for the peripheral money transfer controller or its subagents. This provides a more distributed processing of money transfers and allows local processing of transfers within a domain without the need for a central central money transfer controller.

In accordance with this aspect of the present invention, it is possible for transactions to be processed locally by the peripheral money transfer controller, since the agent working on the peripheral money transfer controller manages the subagents within the domain, and the operator of the peripheral money transfer controller takes ultimate responsibility for financial transactions between its subagents.

In one embodiment of the present invention, in order to ensure that the nodal money transfer controller contains a complete picture of all transactions that occur during the execution of the money transfer management service, the nodal money transfer controller includes transaction data synchronization means for synchronizing transaction data in the storage transaction data in the nodal money transfer controller with a repository of transaction data in the peripheral money transfer controller.

According to another aspect of the present invention, there is provided a “hub and spoke” type money transfer system performing a money transfer service for transferring money from a sender to at least one recipient, the system comprising: a plurality of money transfer agent terminals operated by the transfer agents money; nodal money transfer controller for managing money transfer between unrelated agents; at least one peripheral money transfer controller for managing money transfer between related agents; wherein the agent terminals, the peripheral money transfer controller and the nodal money transfer controller exchange data with each other over the data network.

The present invention can be implemented using specialized data processing equipment or programmable data processing equipment, such as suitably programmed general purpose computers. Further, the present invention can be implemented by a single data processing device or several network data processing devices connected to a network via any conventional data network. The present invention, therefore, can be implemented by appropriate computer programming. Therefore, the present invention covers computer program code for controlling a data processing apparatus performing the method of the present invention. The computer program may be implemented on any suitable data medium supplied to the processing device, such as a variable data medium such as an electric, optical, microwave, radio frequency or acoustic signal (an example is a transmission control protocol / Internet protocol (TCP / IP) signal ) carrying computer code over an IP-based network such as the Internet) or on a storage medium such as a floppy disk, hard drive, tape recorder, CD or hard drive hotel memory.

Embodiments of the present invention are described below with reference to the accompanying drawings, in which:

figure 1 is a schematic representation of a money transfer system in accordance with an embodiment of the present invention;

figure 2 is a schematic representation of the data provided in the database, in the embodiment of figure 1;

3 is a schematic diagram illustrating various interfaces provided for a database in an embodiment of the present invention;

4 is a schematic diagram illustrating how agents can be managed and how they can be organized in a money transfer system in accordance with an embodiment of the present invention;

5 is an organizational chart illustrating a hierarchical organization of agents in a money transfer system in accordance with an embodiment of the present invention;

6 is a flowchart illustrating a method for registering agents in accordance with an embodiment of the present invention;

7a and 7b are a flowchart illustrating a money transfer process in accordance with an embodiment of the present invention; and

FIG. 8 is a schematic diagram of a system for performing a “hub and spoke” type money transfer service in accordance with an embodiment of the present invention.

1 is a schematic representation of a money transfer system in accordance with an embodiment of the present invention. In this embodiment, the transaction server 1 performs the function of managing the transfer of money, and it is connected via the Internet to the computer 3 of the first agent and the computer 5 of the second agent. Computer 3 of the first agent implements a Web browser 3a and is equipped with a device reader 3b for receiving device 3c from a sender who wishes to send money to the recipient. Thus, the agent running on agent computer 3 acts as the sending agent for the sender. The device 3c may be any conventional storage device, such as a smart card, magnetic card, or other solid state device. The device 3c may store personal information for the sender, who is a regular user of the money transfer service, in order to eliminate the need for the user to manually provide his personal data each time he wants to instruct the sending agent to trigger the transfer of money. A sending agent working on agent’s computer 3 will receive payment from the sender regarding the money that must be transferred to the recipient. Agent computer 3 communicates with transaction server 1 to perform money transfer, which is described in detail below. The transaction server 1 is also connected via the Internet to the computer 5 of the second agent, on which, in this example, the agent designated as the receiving agent is running. The computer 5 of the receiving agent is located in the office, which is conveniently available to the recipient of the transferred money. Agent computer 5 implements a Web browser 5a to perform data transfer via the Internet 2 to the transaction server 1. Thus, the data containing the order for the transfer of money is transferred from the computer 3 of the sending agent after payment by the sender to the computer 5 of the receiving agent, after which the receiving agent pays the money to the recipient. Thus, this system allows the sender to come to the office of the sending agent and pay in cash or by any usual payment method acceptable to the sending agent, after which the instruction is sent to the computer of the receiving agent for payment to the recipient, and the receiving agent pays to the recipient when he himself appears in the office the recipient, in any usual form, such as cash or by check. The transfer of instructions between the sending agent and the receiving agent for payment to the sender is almost instantaneous. No need to wait for the transfer of funds. Credit is thus provided between the receiving and sending agents. This is reflected in their accounts, which are stored on the transaction server 1 in the database 10, which is described in detail below.

The transaction server 1 in this embodiment of the present invention comprises a World Wide Web (Web) -based service provided by a web server 6 providing web page interfaces to web browsers 3a and 5a on the sending agent computer 3 and the receiving agent computer 5, respectively. Web server 6 in transaction server 1 is provided with Yava code (Yava code) in the repository 9 of Yava code for generating the corresponding Web pages. Also, static web pages and web page templates are provided in the repository of 7 static web pages and web page templates. Database application 8 is provided to interface Web server 6 with database 10, which stores agent account information and transaction information, which is described in detail in this application below.

Thus, it can be seen in FIG. 1 that the present invention provides a Web-based system that enables the global provision of a money transfer system with a global network of agents using the easily accessible Internet. Connections between computers over the Internet must be secure and can be implemented either by using the Secure Sockets Layer (SSL) protocol, or by implementing a virtual private network (VPN) between computers.

In addition to agents acting as the sending and receiving agents, the system provides an administrative interface to provide administrative functions. 1 shows an administrator computer 4, which is also provided with a web browser 4a for accessing the web pages provided by the web server 6, for providing an administrator interface to information in the database 10.

Figure 2 shows in detail the contents of the database 10 in the server 1 transaction.

The database 10 stores records 11 of the sending entity. The sending entity represents the customer of the service. Records contain information about the customer. Each sending entity or customer is assigned a customer number. For each customer’s number, the customer’s name, address, contact information such as phone number, fax number and email address are entered along with the date of birth, age and gender. Records may also indicate whether the records are active or inactive so that the administrator can block access to the customer. Records can also store a list of recipients in the form of recipient numbers to whom the sender sent money earlier.

Database 10 also includes records 12 of the receiving subject. Records 12 of the receiving entity contain information about the recipients of money transfers made by the customer. Each recipient is assigned a recipient number, and personal details of the recipient, such as name, age, date of birth, gender, address, etc., are stored as a record. Also, for each recipient, the agent number is stored for the receiving agent, which he used to receive money.

Database 10 also includes records of 13 agents that contain a record for each agent. Each agent is assigned an agent number or identifier. The agent number or identifier may indicate the type of agent. For example, the agent may be the main agent or subagent. The agent identifier indicates whether the agent has been registered as a subagent since the identifier includes the identifier of the parent agent. The relationship between parent and child agents can be specified either through an agent identifier, or through relationships in the database. An agent record also indicates the type of agent, for example, whether it is a sending agent, a receiving agent, or both a sending and receiving agent. The ability to send and receive money may be governed by local money transfer rules. The agent record also includes the agent name, address (location) and contact details. For security, the Internet Protocol address (IP address) of the agent’s computer can also be stored in the agent’s record, so that the IP address of the computer used during the transfer of money can be checked to ensure that data is transferred during the transfer of money to the computer an agent, not a hacker. The agent entry further includes security details such as username and passwords. If the agent is an organization, then there may be an organization password that provides a certain level of access, and each operator may have an individual password that provides lower level access. The access level may adjust the level of administrative access permitted for information in the database. The agent’s record additionally stores information on the credit limit indicating the level of credit allowed for the agent and / or deposit information indicating the level of funds deposited by the agent. Additionally, the agent’s record may indicate the type or fraction of the commission that the agent must earn for money transfers, so that it is possible to use separate types of commissions or separate commissions for different agents. For example, where an agent creates a large volume of business operations, a special type or commission splitting can be set for this agent. The agent record additionally stores an indicator of whether the agent record is active or inactive so that the administrator can block access to the agent if necessary.

Database 10 also stores records of 14 inspectors on compliance with the rules governing the practice of money laundering (IPRO, MLRO). An IPOD entry is provided for each IPOD. Typically, each country requires an IPOD that is familiar with the rules for complying with the money laundering practices of that country so that it can update records when necessary. The IPOD record stores regulatory information, statutory limits for transactions, internal limits for transactions along with username and password information.

Database 10 additionally contains records 15 administrator. Administrator entries contain an entry for each administrator who has access to information in the database. The entry for the administrator contains the administrator number, administrator level, indicating the access level allowed to the administrator, the geographic region for which the administrator is responsible, and information about the user name and password for the administrator.

Database 10 additionally contains records 16 of the loan controller. Each loan controller is provided with a record with the number of the loan controller, an indicator of the region for which the loan controller is responsible, and a username and password for the loan controller. This allows credit controllers to check agent accounts to fulfill their credit control responsibilities for the regions for which they are responsible.

Database 10 additionally stores transaction records. A transaction record is created for each transaction or money transfer that takes place. A transaction record contains a transaction number unique to a transaction, a sender number, a recipient number or numbers, the number of the sending agent, the receiving agent or agents, the principal, i.e. the amount paid by the sender, the amount to be paid to the specific recipient or each recipient, the commission charged for the transaction, the sending and receiving currencies, the actual and realized exchange rates (the actual exchange rate represents the exchange rate used by the sending agent to calculate the amount that is necessary pay to the recipient, depending on the actual amount paid by the sender, while the realized exchange rate represents the exchange rate at the time of settlement on tr nzaktsii with the sending agent). A transaction record may also include an indicator of whether the transaction is suspicious or incorrect or not. If the transaction is a suspicious or incorrect transaction, then the transaction record may include either additional data about the transactions that the sender must enter, or a pointer to additional data about the transactions. The transaction record further stores a status indicator indicating the status of the transaction. A transaction has four states:

1) the state of being in progress, indicating that instructions have been received to pay the recipient to the receiving agent, but the payment to the recipient has not yet been made;

2) the status of the payment made, indicating that the recipient received the payment;

3) the state of mutual settlement, indicating that it was paid to the sending agent;

4) an unsuccessful completion / cancellation state, indicating that the transaction failed or was blocked.

The transaction record can additionally store a password that the recipient must provide to the receiving agent before he receives the payment.

Database 10 additionally stores data 18 on the exchange rate and commission. Exchange rate data should be regularly updated to reflect current exchange rates. Commission data may contain commission rates that must be used for transactions. Exchange rate and commission data are accessed when generating a transaction record.

Thus, it is clear that the data stored in the database 10 contains a large amount of information on transactions carried out by agents, which can be accessed and which can be viewed in the form of reports to administrators, agents, IPOD inspectors or credit controllers.

Thus, the entities in the money transfer system consist of agents that can be organized hierarchically in the form of parent and subsidiary agents or main agents and subagents, administrators who can be granted administrative access at various levels, a loan controller and IPOD. Each subject needs access to a database of 10 data with different access levels. Figure 3 shows the interfaces provided for the database 10 by generating the corresponding Web pages using the Web server 6 using the Yava code 9. The agent transaction interface 110 is provided for interfacing with the transaction processing module 111 containing the code implemented in the Web -server 6. The subject’s request interface 112 is provided so that the agent can fulfill the request functions through the exchange rate processor 113 implemented in the Web server 6. This allows the agent to give an answer with information on exchange rates, countries, cities and places where money can be sent by the entity, the proposed location of the sending agent, the closest to the location of the desired recipient, the total cost to complete the transaction, the net amount received in a particular country in a particular currency, the total amount payable, and the ability to check the status of transactions performed by the entity.

The agent is also provided with the administrative interface 114 of the agent, allowing the agent to access the database 10 to view information about his account and transactions performed by him, i.e. sending and receiving transactions. The administrative interface of the agent allows the agent to access the following information:

access the agent profile;

View all transactions made by or on behalf of an agent

View the total income and commission earned over a period of time;

View the amount owed by the money transfer organization.

The agent can enter from the keyboard a record of cash paid to the bank instead of payments made. The agent can also view the status of the transactions for which it is responsible.

An administrative interface 115 may be provided for the database 10 to provide access to administrators at various levels. For example, the chief administrator may have access to all the data in the database. Local administrators, on the other hand, can only access certain parts of the database related to a certain number of agents or geographic region. The administrator can view information depending on his access level. The administrator can not only access the data, but can also make changes to them, for example, current exchange rates, commission rates, and other data. The administrator can receive reports on agents for which the administrator is responsible, depicting transactions over time periods or transactions that satisfy certain criteria.

Credit controllers are provided with a credit control interface 116, allowing them to perform credit control. Inspectors for compliance with the rules governing the practice of money laundering (IPOD) are provided with IPI interface 117, which allows them to fulfill their regulatory function.

Figure 4 shows how various entities can be organized in a money transfer system. The money transfer organization 70 controls the money transfer controller 71. The money transfer organization 70 also includes an administrator 72, a loan controller 74, and an inspector 73 to comply with the rules governing the practice of money laundering. This allows the money transfer organization to provide central management of the money transfer service. The money transfer organization 70 may also include its own agents 75, which are under its direct control. Outside the money transfer organization 70, agents can work independently, such as agent 90. Such an agent, for example, may be the owner of a newsstand. This allows people to come to the newsstand and send money to recipients abroad. Since the system is a Web-based system, the owner of a newsstand acting as an agent simply needs access to the Internet to provide the service. He also needs to enter into a contractual relationship regarding the opening of an account with an organization 70 for transferring money.

4, an organization 100, such as a company, contains two separate agents 101 and 102. Organization 100 also has an administrator 103 to provide administrative functions to agents 101 and 102. Thus, the money transfer organization 70 provides the organization with two agent interfaces and an administrative interface. at the level required for organization 100.

Organization 80, which may consist, for example, of a company, has agent 83 and two subagents 82 and 84, which are subagents of agent 83. The main agent 83 of the organization, therefore, registered subagents 82 and 84 as subagents of agent 83 on transfer controller 71 money. This process is described in more detail later in this application. Organization 80 also has an administrator 81 to provide administrative management of agent 83 and subagents 82 and 84. Thus, the money transfer organization 70 provides the organization 80 with interfaces to the money transfer controller 71, enabling three agents to access the money transfer controller 71, two of which are subagents of the main agent 83, and the administrative interface.

5 is an organizational chart illustrating a hierarchical organization of agents with respect to a money transfer controller and entities. The relationships shown in solid lines in FIG. 5 are financial liability relationships. For example, each agent or parent agent 21, 26, 27, 28, and 34 has a contractual relationship with the money transfer controller 20, and a loan is provided so that these agents can complete transactions. The remaining agents 22, 23, 24, 25, 29, 30, 31, 32, and 33 are all subsidiaries or subagents that were established as subagents of the parent agents 21, 26, and 28. These are the parent agents 21, 26, and 28 are financially responsible for the subagents they have registered. Subagents 22, 23, 24, 25, 29, 30, 31, 32, and 33 can perform transactions with any other agents. Transactions, however, are displayed on the accounts of the main or parent agents, especially for the purpose of checking a loan. Agents 21, 26, and 28 have limited credit, which requires that they ensure that transactions are paid as a result of mutual settlements with receiving agents, and that their subagents carry out mutual settlements with transactions with receiving agents.

5, it can be seen that the subagents can be registered as the main agents for the subagents, and thus the agent hierarchy can be registered using the money transfer controller 20. Each agent can make money transfers for individual entities, such as individuals or companies, or an agent such as a company can serve as an agent, and therefore the agent becomes an agent / entity, such as agents / entities 25 and 34.

The dashed lines in FIG. 5 depict money transfers between entities. Subject 46 is a sending entity using agent 24 as a sending agent. The sending agent 24, although it is financially responsible to the parent agent 21, can connect to the money transfer controller 20 using the Web interface. The money transfer controller 20 determines that the receiving agent is agent 21, and thus the information will be transferred to the agent 21, so that the agent 21 can complete the money transfer to the receiving entity 40. It can be seen that this transfer contains a transfer affecting the subagent 24 of the parent agent 21. This, therefore, is a transaction that can be performed as a local transaction on a “spoke” (peripheral element) in a transaction model of a “hub and spoke” type, which will be described in detail with reference to an embodiment 8.

Another transaction shown in FIG. 5 by a dashed line is a transaction from a sending entity 47 to multiple receiving entities 48, 50, and 60. The sending entity 47 uses the sending agent 26 to form one transaction for which the sending entity makes one payment, presented as Transactions from one sending entity to multiple receiving entities. Transaction data also indicates that the two receiving agents 27 and 33 are involved in completing the transfer to the three receiving entities 48, 50 and 60. The money transfer controller 20 thus receives transaction data from the sending agent 26, saves it as a transaction and gives instructing receiving agents 27 and 28 to pay their respective receiving entities 48, 50 and 60. Thus, it can be seen that for this transaction it is possible for the sending entity to complete one transaction with multiple receiving entities, thus simplifying the process transaction for sending entity.

The agent registration process for a money transfer service is described below with reference to the flowchart of FIG. 6. Any prospective agent for the service must first access the agent registration web page (step S1). If the agent has already registered, then the agent can enter the system (step S2) to enable him to register subagents (step S5).

If the agent is not logged in (because it is not registered), then it enters the agent data (step S3) to form an agent record in the database 10 (step S4). When an agent registers, he needs to either get a secured loan or deposit money into a bank to use the service. The level of credit or the level of its contribution determines the credit available to him for transactions.

After the agent has registered, the agent can choose to register subagents for which he will be responsible financially (step S5). If he does not select the registration of subagents, then the registration process ends (step S6). If the agent selects the registration of subagents (step S5), then the Web page 6 generates a Web page for registering the subagent (step S7). Then, the agent may choose to register child subagents of the registered subagent (step S8). If the agent does not choose to register the subagents of the registered subagent at this point, but instead wishes to register the subagent, then the subagent data is entered (step S9) and an agent record is created for the subagent as the agent subagent (step S10). The agent can then select the registration of the child subagents (step S11). If he does not select and register child subagents, then the registration process ends (step S6). If the agent selects the registration of the child subagents (step S8 or step S11), then the parent subagent for the child subagent is selected (step S12) and the data of the child subagent is entered (step S13). Then, an agent record is generated for the child subagent as the child subagent of the parent subagent (step S14). This process may be repeated for additional child subagents (step S11).

In this way, an agent acting as the main or parent agent can register a hierarchy of subagents for which the main or parent agent is financially responsible. Such an agent is agent 28, shown in FIG. 5, which has two subagents 29 and 33. Subagent 29 has subsidiary subagents 30, 31 and 32. All of these agents 29, 30, 31, 32 and 33 fall under the financial responsibility of parent agent 28 .

The process of transferring money from a sending entity to one or more receiving entities is described below with reference to the flowchart of FIGS. 7a and 7b.

When the sending entity instructs the agent to transfer money to one or more receiving agents, the sending agent enters the money transfer system and accesses the money transfer web page provided by the web server 6 (step S20). The sending agent receives the following information from the customer:

customer number (if not a new customer);

name of sender;

Sender name;

surname of the sender;

date of birth or age of the sender;

full address of the sender;

Sender's postal code

sender's phone number;

Sender email address

type of payment, for example in cash, bill of exchange or to a bank account;

bank, bank account number, branch, bank branch code;

where should the money be sent;

amount to be dispatched;

payment currency (by default, this is the local currency of the sending agent);

payout currency;

the password that he wants the recipient to submit to receive the money;

reasons for departure (required by the rules governing the practice of money laundering), i.e. personal, family or foreign tourist;

This is the money of the sender (yes or no);

Recipient name

date of birth or age of the recipient;

receiver name;

the name of the recipient;

address of the recipient;

Recipient's phone number

The total amount payable by the sending customer

payment method, for example in cash, by check or by credit card.

Thus, data on the sending and receiving entities and data on money transfer are entered (step S21). Exchange rate and commission data are used to determine the amount payable by the receiving agent to the receiving entity (step S22).

During the determination of the exchange rate and the completion of the transaction, the sender is issued a receipt to the sender. The sender can also see the status of all previous transactions performed on his behalf.

Data is sent to and received from the transaction server (step S23). The transaction server adds the information about the sending agent obtained by identifying the agent during the login sequence (step S20) to the obtained data for the stored transaction data (step S24). The transaction server then determines whether the transaction data identifies more than one receiving subject (step S25). If so, then transaction data is stored as a related group of transaction records, where transaction records are associated or linked by the sending entity and / or agent and indexed by the receiving agents and / or entities. If transaction data identifies only one receiving entity (step S25), then transaction data is stored as a transaction record (step S27). The transaction records or records are then compared with the sending agent data and the regulatory data (step S28). If a comparison of the record or transaction records of the regulatory data identifies that the transaction is a suspicious or incorrect transaction (step S29), a Web page is generated requesting additional transaction data from the sending entity (step S30). Therefore, the sending entity must provide additional data, such as passport details, driver’s license or other valid ID. The comparison (step S28) allows the processing of a possibly reliable, but suspicious or incorrect transaction with the necessary additional data in order to detect money laundering. Additional transaction data is received on the transaction server (step S31) as a result of filling out forms on the Web page by the sending agent, and additional transaction data is entered into the transaction record or entries (step S32).

If additional transaction data has been entered in the transaction records, or if the transaction is not a suspicious or incorrect transaction, the transaction server then determines whether the transaction exceeds the credit limit for the sending agent, whether the agent was prohibited from using the service, or if the transaction violates the compliance rules the practice of money laundering. If so, a Web page is generated to inform the sending agent that the money transfer cannot be accepted (step S34), the transaction is then marked as rejected in the transaction records (step S35). Thus, the transaction server in this way can monitor transactions, manage them and prevent transactions that would expose the receiving agent to the unacceptable risk of credit default (because the credit limit of the sending agent was exceeded, or access to this agent was blocked), or they violated would be the rules of conformity with the practice of money laundering applicable to the transaction.

If it is determined that the credit limit for the sending agent has not been exceeded, the access of this sending agent has not been blocked and the rules have not been violated (step S33), a Web page is generated to inform the sending agent that the transfer is accepted, and the number is displayed or transaction numbers (step S36). The transaction server marks the transaction or transactions as being in progress (step S37), and the receiving agent or agents are notified of the transaction or transactions (step S38). The receiving agent or agents then access a Web page showing the transactions in progress for which they are the receiving agent (step S39). The receiving agent or agents then takes measures to make the payment to the receiving entity or entities, and an indicator is entered that the payment or payments have been made (step S40). In order for the receiving agent to pay the receiving entity, the receiving entity must confirm its name, address, telephone number, the amount that it expects to receive, from whom it expects to receive money, the country from which the money is expected to come, password ( if applicable), identification form and choice of payment method.

The transaction server then updates the transaction record or records to the payout state and writes the exchange rate at the time of payment to the transaction record (step S41). Recording the exchange rate at the time of payment in the transaction record allows you to determine the difference in exchange rates for recording the transaction, i.e. the difference between the courses. Since the money transfer organization accepts payment from the sending entity based on the exchange rate at the time of payment by the sending entity, and then makes payment to the receiving entity based on the exchange rate at the time of payment, there is a potential difference in exchange rates. All this happens at the expense of the money transfer organization. This difference in exchange rates can result in a gain or loss. A careful selection of the exchange rates used to calculate the payment to be made by the sending entity must be used in order to avoid losses caused by exchange rates. At the end of each day, the sending agent pays all the money that he received from all customers, minus his commission, to the bank indicated by the money transfer organization. This allows the money transfer organization to credit accounts accordingly, i.e. transfer funds to receiving agents who have paid money to receiving entities. Cash payment records made by money transfer organizations can be entered by the sending entity using the administrative interface 114.

If transactions have been completed, then using the administrative interface, agents can view their account data from previous transactions. This allows agents to work on mutual compensation of claims and obligations with respect to any other agents at any time, using current exchange rates.

FIG. 8 is a schematic representation of a money transfer system in accordance with another embodiment of the present invention. The system operates as a “hub and spoke” type money transfer system in which a transaction server 1000 serves as a “hub” or a node server, and the host agent computer 3000 serves as a “spoke” or peripheral server. In this embodiment of the present invention, the main agent running on the main agent computer 3000 has registered two subagents running on the computers 4000 and 5000 subagents, each implementing a corresponding web browser 4000a and 5000a. All agents are part of the organization 6000. The main agent is responsible for their subagents, as described above in this application.

In this embodiment of the present invention, when the main agent is registered as the main agent, the main agent computer 3000 is configured as a "spoke" in a "hub and spoke" type money transfer system. The host agent computer receives the code to implement the host agent application 3003, which has a subset of 3004 databases, which is a subset of the database 1005 on the host transaction server 1000 (ie, “hub”). The host agent computer 3000 also implements a Web browser 3001 and a Web server 3002.

The transaction server 1000 serving as the nodal money transfer system comprises a Web server 1001 that implements Yava code stored in the Yava code store 1003, and static Web pages and templates stored in the store 1002 of static Web pages and templates. The database application 1004 serves as an interface between the web server 1001 and the database 1005. The principle of operation of the transaction server 1000 is essentially the same as described in this application above for the previous embodiment.

When the receiving agent instructs the subagent, if the receiving entity wishes to use the receiving agent that has the agent computer 7000, since it is not under the control of the main agent, the subagent should use the transaction server 1000 as a nodal money transfer system, as described above in this application for the previous embodiment. However, if money is to be transferred from the sending agent working on the computer 5000 subagents to the agent working as the receiving agent and working on the computer 4000 subagents, then the computer 3000 main agent can be used as a peripheral money transfer system ("knitting needles") . Since there is no responsibility outside the organization of 6000 for the transfer of money, you do not need to involve a nodal money transfer system. It is simply a transfer of funds between agents for which the main agent is ultimately responsible. Thus, the web browser 5000a of the subagent computer 5000 can be used by the sending agent to access the web server 3002 on the host agent computer 3000. The main agent application 3003 can then access the data in a subset of the database 3004 to complete the transaction for the receiving agent using the 4000 subagent computer. In this way, the transaction is managed through the main agent application 3003, and the subset 3004 of the database contains records of local transactions within the organization 6000.

In order to guarantee that the nodal money transfer system implemented by the transaction server 1000 contains a global database 1005 corresponding to the current moment, the database application 1004 periodically performs the synchronization procedure of the subset 3004 of the database with the database 1005.

Thus, it can be seen that this second embodiment of the present invention allows local transactions to be performed using a peripheral money transfer system implemented under the control of the main agent for transactions between subagents of the main agent.

Although the present invention has been described above in this application with reference to specific embodiments, it will be apparent to those skilled in the art that modifications can be made within the spirit and scope of the present invention.

For example, although the currency exchange was described earlier in this application as a direct exchange of the sender’s currency to the recipient’s currency, the present invention covers the use of any number of intermediate currencies in the currency exchange process.

Claims (44)

1. A computer-based money transfer management system for connecting to a plurality of agent terminals via a data network to control the execution of a money transfer service for transferring money from a sending entity to at least one receiving entity, said agent terminals being interconnected via said data network and agents work for them in order to trigger the transfer of money requested by the sending entity to at least one receiving entity, while the subject contains agent account data repository storing account data for each agent; a transaction data repository storing transaction data for transactions performed by agents transferring money from a sending entity to at least one receiving entity; receiving means for receiving data from said agent terminal, wherein the entered data identifies the sending and receiving entities, the sending agent and at least one receiving agent, which is to pay the money transferred to it to a specific receiving entity or to each receiving entity; recording means for recording the entered data into said transaction data storage in the form of a transaction from the sending agent to at least one receiving agent for the sending entity and at least one receiving entity; account data updating means for updating agent account data in an agent account data repository for sending and receiving agents based on a transaction; and transaction management tool for managing a transaction by comparing a transaction with regulatory data on compliance with money laundering practices, representing rules of conformity with money laundering practices, and to block a transaction if, as a result of a comparison, it is determined that the transaction violates the rules for compliance with money laundering practices. 2. The computer-based money transfer management system according to claim 1, wherein the requested money transfer is made from the sending currency to the receiving currency; said money transfer management computer system includes an exchange rate data store storing exchange rate data, said agent account data repository stores account information for each agent in a local currency for the agent; and said computer-based money transfer management system includes currency conversion means for using exchange rate data in said exchange rate data storage for converting currencies for transactions in order to determine the amount in the receiving currency based on the amount in the sending currency and to store the amounts in as part of a transaction stored in said transaction data store, and said account data update tool is for updating agent account data in the store agent account data for agents in local currency based on exchange rate data. 3. A computer-based money transfer management system for connecting to a plurality of agent terminals via a data network to control the execution of a money transfer service for transferring money from a sending entity to at least one receiving entity, said agent terminals being connected to each other via said data network and agents work for them in order to cause the transfer of money requested by the sending entity to at least one receiving entity, while the subject contains agent account data repository storing account data for each agent; a transaction data repository storing transaction data for transactions performed by agents transferring money from a sending entity to at least one receiving entity; receiving means for receiving data from said agent terminal, wherein the entered data identifies the sending and receiving entities, the sending agent and at least one receiving agent, which is to pay the money transferred to it to a specific receiving entity or to each receiving entity; recording means for recording the entered data into said transaction data storage in the form of a transaction from the sending agent to at least one receiving agent for the sending entity and at least one receiving entity; account data updating means for updating agent account data in an agent account data repository for sending and receiving agents based on a transaction; and transaction monitoring tool for monitoring transactions, for sending a request for additional information from the sending entity to the terminal of the agent on which the sending agent is running, if the transaction meets the predefined criteria, to receive this additional information from the agent terminal and to associate this additional information with the transaction in transaction data store. 4. The computer-based money transfer management system according to claim 3, including a transaction management tool for managing a transaction based on comparing the returned additional information and predetermined criteria and for blocking the transaction if it meets the aforementioned predetermined criteria. 5. The computer-based money transfer management system according to claim 1 or 4, wherein said transaction management tool is for transmitting a message to the terminal of the agent on which the sending agent works, in order to inform the sending agent that the money transfer has been blocked. 6. The computer-based money transfer management system according to claim 1 or 3, which includes an interface that allows agents working on agent terminals to register as the main agent and other agents to register as subagents, while the said account data update tool is designed to linking account data in the account data warehouse for subagents with the main agent. 7. The computer-based money transfer management system according to claim 1 or 3, wherein said receiving means is intended for receiving input data from an agent terminal identifying a sending entity and a plurality of receiving entities, and said recording means is intended for storing transaction data in a data warehouse transactions as a single send transaction indexed for the sending entity, and as a set of receiving transactions indexed for each receiving entity. 8. The computer-based money transfer management system according to claim 1 or 3, wherein said receiving means is for receiving input data from an agent terminal, identifying a sending entity, a sending agent, a plurality of receiving entities and a plurality of receiving agents, and said recording means is for storing transaction data in the transaction data warehouse as a single send transaction indexed for the sending agent and as a set of receiving transactions, index Required for each receiving agent. 9. The computer-based money transfer management system according to claim 1 or 3, implemented as a Web service over a network based on the Internet protocol, and each of the agent terminals implements a Web browser application for organizing data transfer with said money transfer management system. 10. The computer-based money transfer management system according to claim 1 or 3, including an administrative interface that allows agents to access the relevant agent account data in said agent account data store and transaction data in said transaction data store. 11. The computer-based money transfer management system according to claim 1 or 3, which includes a means of mutual compensation of claims and obligations on accounts, allowing agents to determine mutual compensation of claims and obligations on their accounts in the account data warehouse with respect to any other agent. 12. An agent terminal for use with a central computer money transfer management system, wherein an agent registered as the main agent in said central money transfer control computer system operates on an agent terminal, the agent terminal comprising a domain money transfer management system for managing the execution of a money transfer service between agents in a group of agent terminals operated by agents registered as subagents of the main agent and for sending transaction data to a central computer money transfer management system for the implementation of a money transfer service between agents in said group of agents and at least one other agent not from said group of agents connected to a central computer control system with money, wherein said transaction data identifies the sending and receiving entities, the sending agent and at least one receiving agent; a domain agent account data repository storing account data for said agent group; and a domain transaction data repository storing transaction data for transactions between agents in said agent group. 13. A method for controlling the execution of a money transfer service for transferring money from a sending entity to at least one receiving entity using a computer money transfer management system connected to a plurality of agent terminals via a data network, said agent terminals being interconnected via said transmission network data, and agents work for them in order to cause the transfer of money requested by the sending entity to at least one receiving The object, the method comprising the steps of: store invoice data for each agent in the agent account data repository; receiving data from said agent terminal, the data identifying the sending and receiving entities, the sending agent and at least one receiving agent that is to pay the money transferred to it to a particular receiving entity or to each receiving entity; write the entered data to the transaction data warehouse in the form of a transaction from the sending agent to at least one receiving agent for the sending entity and at least one receiving entity; Update agent account data in the agent account data repository for the sending and receiving agents based on the transaction; and they manage the transaction by comparing the transaction with the regulatory data on compliance with the money laundering practice, representing the rules of conformity with the money laundering practice, and blocking the transaction if, as a result of the comparison, it is determined that the transaction violates the rules for compliance with the money laundering practice. 14. The method according to item 13, in which the requested transfer of money is carried out from the sending currency to the receiving currency; said agent account data store stores the account data for each agent in a local currency for the agent, and the method includes the steps of using the exchange rate data in the exchange rate data store to convert currencies for transactions to determine the amount in the currency receipts, based on the amount in the sending currency, save the amounts as part of the transaction stored in the said transaction data store, and update the agent account data in the agent account data warehouse for agents in places second currency, based on their exchange rates. 15. A method for controlling the execution of a money transfer service for transferring money from a sending entity to at least one receiving entity using a computer-based money transfer management system connected to a plurality of agent terminals via a data network, said agent terminals being interconnected via said transmission network data and agents work on them in order to cause the transfer of money requested by the sending entity to at least one receiving sou the subject, the method comprises the steps of store invoice data for each agent in the agent account data repository; receiving data from said agent terminal, the data identifying the sending and receiving entities, the sending agent and at least one receiving agent that is to pay the money transferred to it to a particular receiving entity or to each receiving entity; write the entered data to the transaction data warehouse in the form of a transaction from the sending agent to at least one receiving agent for the sending entity and at least one receiving entity; Update agent account data in the agent account data repository for the sending and receiving agents based on the transaction; and they monitor transactions, send a request for additional information from the sending entity to the terminal of the agent on which the sending agent works, if the transaction meets the predefined criteria, receive this additional information from the agent terminal and associate this additional information with the transaction in the transaction data store. 16. The method according to clause 15, comprising the steps of managing the transaction based on the comparison of the returned additional information and predetermined criteria and blocking the transaction if it meets these predetermined criteria. 17. The method according to item 13 or 16, which includes transmitting a message to the terminal of the agent on which the sending agent works, in order to inform the sending agent that the money transfer was blocked. 18. The method according to item 13 or 15, comprising the step of managing the transaction by accessing transaction data and accounts in said account data storage for the sending agent. 19. The method according to item 13 or 15, which includes the steps of providing an interface that allows agents running on agent terminals to register as the main agent and to other agents to register as subagents, and link invoice data to the data warehouse about accounts for subagents with the main agent. 20. The method of claim 13 or 15, wherein said received input from an agent terminal identifies a sending entity and a plurality of receiving entities, and transaction data is stored in a transaction data store as one sending transaction indexed for the sending entity, and as a set of receive transactions indexed for each receiving entity. 21. The method according to item 13 or 15, in which the said received input from the agent terminal identifies the sending entity, the sending agent, the plurality of receiving entities and the plurality of receiving agents, and the transaction data is stored in the transaction data storage as a single sending transaction, indexed for the sending agent, and as a set of receive transactions indexed for each receiving agent. 22. The method according to item 13 or 15, comprising the step of providing an interface in the form of a Web service over a network based on the Internet protocol, wherein each of said agent terminals implements a Web browser application for exchanging data with said system money transfer management. 23. The method according to item 13 or 15, comprising the step of providing an administrative interface that allows agents to access relevant agent account data in said agent account data store and transaction data in said transaction data store. 24. The method according to item 13 or 15, which includes the step of providing an interface that allows agents to determine mutual compensation for claims and obligations on their accounts in the account data repository for any other agent. 25. A method of operating on an agent terminal for use with a central money transfer management computer system, wherein an agent registered as the main agent in said central money transfer management computer system operates on an agent terminal, the method comprising the steps of implement a domain money transfer management system to manage the execution of a money transfer service between agents in the group of agent terminals operated by agents registered as subagents of the main agent, and to send transaction data to a central computer money transfer management system to implement the money transfer service between agents in said agent group and at least one other agent not from said agent group connected to a central computer control system transferring money, while the mentioned transaction data identifies the sending and receiving entities, the sending agent and at least one receiving agent; save invoice data for said group of agents; and save transaction data for transactions between agents in said agent group. 26. A computer-based money transfer management system for connecting to a plurality of agent terminals via a data network to control the execution of a money transfer service for transferring money from a sending entity to at least one receiving entity, said agent terminals being interconnected via said data network and agents work for them in order to cause the transfer of money requested by the sending entity to at least one receiving entity, while the stem contains agent account data repository storing account data for each agent; program memory storing instructions executed by the processor; a processor for executing instructions stored in program memory; while the instructions executed by the processor contain instructions for controlling the processor so that it executes the method according to any one of claims 13-24. 27. A computer money transfer system that performs a money transfer service for transferring money from a sender to a plurality of recipients, the system comprising a plurality of terminals interconnected via a data network; a money transfer management system connected to a data transmission network for controlling the execution of a money transfer service, the money transfer management system including a transaction data warehouse storing transaction data for transactions that carry out money transfers from the sender to the recipients; wherein said terminal is designed to respond to data entered in order to cause the transfer of money from the sender to at least one recipient, to transmit the entered data to the money transfer management system; moreover, the entered data identifies the sender and recipients; and at the same time, the money transfer management system is designed to record the entered data into the said data warehouse of transactions in the form of a transaction from the sender to many recipients, to allocate the transaction to each mentioned recipient and to send data identifying the allocation for the respective recipients to at least one terminal, to ensure that the transfer is completed to the appropriate recipients. 28. The computer money transfer system according to claim 27, wherein said money transfer management system is intended to store the entered data in a single transaction indexed by the sender. 29. The computer money transfer system according to claim 28, wherein said terminal is designed to receive input data as data representing a single transaction, and said money transfer management system is intended to store the input data in the form of a plurality of related transactions connected by the sender and indexed by the recipient. 30. The computer money transfer system according to any one of paragraphs.27-29, in which the senders include agents of the money transfer system, acting on the instructions of the sending entities, or the senders include the sending entities; and the recipients include agents of the money transfer system authorized to pay the transferred money to the receiving entities, or the recipients include the receiving entities. 31. A money transfer management computer system for connecting to a plurality of terminals via a data network for controlling the execution of a money transfer service for transferring money from a sender to a plurality of recipients, said terminals being interconnected via said data network and are used to cause execution money transfer from the sender to many recipients, while the system contains a transaction data store that stores transaction data for transactions that transfer money from the sender to the recipients; receiving means for receiving data from the terminal in order to cause the transfer of money from the sender to multiple recipients, while the received data identifies the sender and recipient; and transaction processing means for recording the received data in said transaction data warehouse in the form of a transaction from the sender to a plurality of recipients, for allocating a transaction to each mentioned recipient and for sending data identifying the allocation for the corresponding recipient to at least one terminal, allowing completion of the transfer of money to the corresponding to the recipient. 32. The computer-based money transfer management system of claim 31, wherein said transaction processing means is for storing the entered data as a single transaction indexed by the sender. 33. The computer-based money transfer management system of claim 32, wherein said receiving means is for receiving input data in the form of data representing a single transaction, and said transaction processing means is for storing the entered data as a plurality of related transactions associated with the sender and indexed by the recipient. 34. The computer-based money transfer management system according to any one of claims 31-33, wherein the senders include agents of the money transfer system acting as directed by the sending entities, or the senders include the sending entities; and the recipients include agents of the money transfer system authorized to pay the transferred money to the receiving entities, or the recipients include the receiving entities. 35. A method for controlling the execution of a money transfer service for transferring money from a sender to a plurality of recipients using a computer money transfer management system connected to a plurality of terminals in a data network, said terminals being interconnected via said data network and are used to cause the transfer of money from the sender to many recipients, the method comprising the steps of receive data from the terminal in order to cause the transfer of money from the sender to a plurality of recipients, in which the received data identifies the sender and the recipient; write the received data to the transaction data warehouse as a transaction from the sender to a plurality of recipients; allocate a transaction to each mentioned recipient; and send data identifying the allocation for the respective recipient to at least one terminal, allowing completion of the transfer of money to the corresponding recipient. 36. The method according to clause 35, in which the entered data is stored as a single transaction, indexed by the sender. 37. The method according to clause 36, in which the entered data is taken as data representing a single transaction, and the entered data is stored as a set of related transactions associated with the sender and indexed by the recipient. 38. The method according to any one of claims 35-37, wherein the senders include money transfer agents acting as directed by the sending entities, or the senders include sending entities; and the recipients include agents of the money transfer system authorized to pay the transferred money to the receiving entities, or the recipients include the receiving entities. 39. A computer-based money transfer management system for connecting to a plurality of terminals via a data network for controlling the execution of a money transfer service for transferring money from a sender to a plurality of recipients, said terminals being interconnected via said data network and are used to cause execution money transfer from the sender to many recipients, while the system contains program memory storing instructions executed by the processor; a processor for executing instructions stored in program memory; while the instructions executed by the processor contain instructions for controlling the processor so that it executes the method according to any one of claims 33-36. 40. A computer money transfer system that performs a money transfer service for transferring money from a sender to at least one recipient, the system comprising a plurality of agent terminals operated by money transfer service agents, said agent terminals being interconnected via a data network, with agents registered in the central money transfer management system as parent agents and subsidiary agents, and the parent agents operate the peripheral service for money transfer for a group of subsidiary agents; a central money transfer management system connected to a data transmission network to control the execution of a money transfer service between subsidiaries in different groups and between main agents and including a transaction data warehouse that stores transaction data for transactions between subsidiaries in different groups and between the main agents that transfer money from the sender to at least one recipient, and an agent data store containing agent relationships identifying the hierarchy oditelskih subsidiaries and agents; wherein at least one terminal of the agent on which the parent agent is operating comprises a peripheral money transfer management system for controlling the execution of the money transfer service for transferring money between subsidiaries in the group of agents; a local transaction data repository storing transaction data for transactions between subsidiaries in said group that transfer money from the sender to at least one recipient; and an agent data store containing relationships between agents identifying a hierarchy of parent and child agents; moreover, said terminal is designed to respond to data entered by the sending agent, causing the transfer of money at the request of the sender to at least one recipient, and identifying the sender and recipient, the sending agent and at least one receiving agent who must pay the money transferred to him to a specific recipient or to each recipient, and for transferring the entered data: a central money transfer management system if the receiving agent identified in the data is not in the same group as the sending agent; the central money transfer management system is designed to record the entered data into the said transaction data store in the form of a transaction from the sending agent to at least one receiving agent for the sender and at least one recipient and for transmitting transaction information to a specific terminal of the agent or each an agent terminal on which a particular receiving agent or each receiving agent is running; or said peripheral money transfer management system if the receiving agent identified in the data is in the same group as the sending agent; wherein the peripheral money transfer management system is designed to record the entered data into the said local transaction data repository in the form of a transaction from the sending agent to at least one receiving agent for the sender and at least one recipient and for transmitting transaction information to a specific agent terminal or each agent terminal on which a particular receiving agent is running or each receiving agent. 41. The computer money transfer system of claim 40, wherein said central money transfer management system includes transaction data synchronization means for synchronizing transaction data in a transaction data storage in a central money transfer management system and in a transaction data storage in peripheral money transfer management system. 42. A peripheral computer money transfer system for use with a central computer money transfer system to manage the execution of a money transfer service between subsidiaries in the same group, the agents being registered in the central computer money transfer control system as parent agents and subsidiary agents wherein the parent agents operate a peripheral money transfer service for a group of subsidiary agents, the peripheral computer system revoda money operated as a master agent, the system comprising a transaction data warehouse storing transaction data for transactions between subsidiaries that transfer money from a sender to at least one recipient in the same group; an agent data store containing relationships between agents that identify the hierarchy of parent and child agents; receiving means for receiving data entered by the sending subsidiary in the said group at the sending terminal, causing the transfer of money at the request of the sender to at least one recipient, and identifying the sender and recipient, the sending agent and at least one receiving agent that must pay the transferred him money to a specific recipient or to each recipient; transaction processing means for, if at least one receiving agent is in said group, writing the entered data to said transaction data storage in the form of a transaction from the sending agent to at least one receiving agent for a child sender in said group and at least one recipient and to send transaction information to a specific receiving agent or to each receiving agent and to transmit transaction information to a specific terminal of the agent or each the agent’s terminal on which the particular receiving agent or each receiving agent is running, or for, if the at least one receiving agent is not in the said group, sending received data to a central money transfer management computer system. 43. The peripheral computer money transfer system according to claim 42, including a transaction data synchronization means for synchronizing transaction data in a transaction data storage in said central money transfer management system and in a transaction data storage in said peripheral money transfer management system . 44. A data transmission medium carrying a machine-readable code for implementation by a computer in order to perform the method according to any one of claims 13-25 or 35-39.

Images