A system for the transfer of funds

Abstract

The present invention relates to a system (1) for accepting transfers to the same currency account of the recipient's choice regardless of whether it is linked to a single IBAN or account number; assigning a different account for each currency, if desired; depositing the amount into the predetermined currency account without requiring any acceptance or rejection process in case of assignment; and linking it to not only a single account but also one account in each currency to its address.

Description

[0001] DESCRIPTION

[0002] A SYSTEM FOR THE TRANSFER OF FUNDS Technical Field

[0003] The present invention relates to a system for accepting transfers to the same currency account of the recipient’s choice regardless of whether it is linked to a single IBAN or account number; assigning a different account for each currency, if desired; depositing the amount into the predetermined currency account without requiring any acceptance or rejection process in case of assignment; and linking it to not only a single account but also one account in each currency to its address.

[0004] Background of the Invention

[0005] Today, EFT (Electronic Funds Transfer) is an interbank funds transfer that is available during business hours and requires the entry of an IBAN (International Bank Account Number) or bank code, branch code and account number. It checks first and last names. FAST (Instant and Continuous Transfer of Funds) is a system that can transfer funds 24 / 7, and the required fields are the same as for EFT. KOLAS -the supportive product- is a system that supports sending funds via a GSM (Global System for Mobile Communications) number, e-mail, or TRIN (Turkish ID No.) without requiring any information, such as Fast or IBAN for EFT. However, the GSM number, e-mail, or ID number of an individual must be paired to only one account in this system. Here, there is always an account restriction for the recipient. Today, many people may hold dozens of account numbers due to the frequent change of their banks for salaries, and they tend to work with different banks. Sharing these account details with the other party may not always be possible or may be difficult to do so. For international products, such as MoneyGram or Western Union or those where banks transfer funds via SWIFT, the recipient’s name and country are mandatory.Therefore, considering the studies and deficiencies included in the current technique, it is understood that there is a need for a system that provides a structure for the recipient to collect the funds transferred to the account of his choice according to his needs upon arrival of the wire transfer, sends the requested wire transfer to the recipient using only the country code and GSM number, e-mail, or Turkish ID number, and allows the recipient to collect the funds transferred to the account of his choice internationally in the same foreign currency.

[0006] The United States patent document no. US2013060689A1 -an application included in the state of the art- discloses a system for electronic fund transfers via a communication network. The said invention introduces techniques for the efficient transfer of funds between parties through the use of personal communication devices. The first user can transfer funds from an account assigned to the first user using the first communication device to the second user via a contact address linked to the second communication device of the second user. Even if the second user is not registered with a financial service provider linked to the account of the first user, the funds can be transferred from the first communication device to the second user via a message, e-mail, voicemail, etc. by using the Internet, mobile communication systems, or other communication technologies, whereby the second communication device may be notified of the funds. The first user can transfer funds using an account or a linked account with the financial service provider, and the second user can have the funds deposited into an account of his choice.

[0007] Summary of the Invention

[0008] The object of the present invention is to realize a system which is developed with the aim of accepting transfers to the same currency account of the recipient’s choice regardless of whether it is linked to a single IBAN or account number;assigning a different account for each currency, if desired; depositing the amount into the predetermined currency account without requiring any acceptance or rejection process in case of assignment; and linking it to not only a single account but also one account in each currency bring about address.

[0009] Another object of the present invention is to realise a system which is developed with the aim of minimising financial and legal risks and allowing the recipient to choose any account in any country / bank in the fund transfer world as soon as the money is transferred, preventing the recipient from receiving a fund transfer from an unknown source in terms of financial and legal risks, and avoiding an incorrect fund transfer for both the sender and the recipient.

[0010] Detailed Description of the Invention

[0011] “A System for The Transfer of Funds” realized to fulfd the objectives of the present invention is shown in the figure, in which:

[0012] Figure 1 is a schematic view of the inventive system.

[0013] The components illustrated in the figure are individually numbered, where the numbers refer to the following:

[0014] 1. System

[0015] 2. Electronic Device

[0016] 3. Mobile Banking Application

[0017] 4. Sender’s Financial Institution Server

[0018] 5. Recipient’s Financial Institution Server

[0019] 6. Central Database

[0020] 7. Central Server

[0021] A. Recipient UserG. Sender User

[0022] GV. Sender’s Financial Institution Database

[0023] AV. Recipient’s Financial Institution Database

[0024] The inventive system (1) which is developed with the aim of accepting transfers to the same currency account of the recipient’s choice regardless of whether it is linked to a single IBAN or account number; assigning a different account for each currency, if desired; depositing the amount into the predetermined currency account without requiring any acceptance or rejection process in case of assignment; and linking it to not only a single account but also one account in each currency to its address comprises:

[0025] at least one electronic device (2) which is configured to exchange data and run at least one application thereon by using any remote communication protocol;

[0026] at least one mobile banking application (2) which is configured to be run on an electronic device (3); to enable the sender user (G) to enter the necessary information on at least one interface to initiate the fund transfer; to select the account of the recipient user (A) on one interface for the acceptance of the transfer; and to declare the acceptance of the payment transaction;

[0027] at least one sender’s financial institution server (4) which is configured to transact in accordance with the instructions of its customers and preferred by its customers for sending or receiving funds; to store and keep confidential the data that people have shared when sending and receiving funds; to transmit the information contained in the orders placed by the sender users (G) through the mobile banking application (3);

[0028] at least one recipient’s financial institution server (5) which is configured to transact in accordance with the instructions of its customers and preferred by its customers for sending or receiving funds; to store and keep confidential the data that people have shared when sending and receiving funds; to transmit the information contained in recipient users (R);at least one central database (6) which is configured to record the information entered by the sender user (G) through the mobile banking application (3) therein;

[0029] at least one central server (7) which is configured to function as a data centre; to exchange data and information; to keep the accounts of all intermediary institutions in all foreign currencies; to account for fund transfers that it intermediates based on the debit / credit principle for each transaction among these accounts; to send and receive funds to and from customers of banks and insurance and investment companies; and to store and keep confidential the data sent and received by organizations and individuals.

[0030] The electronic device (2) included in the inventive system (1) is configured to exchange data by using any remote communication protocol. The electronic device (2) is a device such as mobile phone, tablet, desktop computer and / or a portable computer. The electronic device (2) is configured to run the mobile banking application (3) thereon. The electronic device (2) is configured to establish a connection with the sender’s financial institution server (4) and the recipient’s financial institution server (5) by using any remote communication protocol included in the state of the art.

[0031] The mobile banking application (3) included in the inventive system (1) is configured to be run on the electronic device (2). The mobile banking application (3) is made available through the sending financial institution server (4) and is configured to enable the sender user (G) to enter the necessary information on at least one interface to initiate the fund transfer. The mobile banking application (3) is configured to enable the sender user (G) to enter the information of the recipient user (R), such as the recipient country code, TRIN (Turkish ID No.) / TIN (Tax ID No.) / GSM (Global System for Mobile Communications) number, e-mail address, date of transaction, currency, payment type and amount on at least one interface. The mobile banking application (3) is configured to enable the senderuser (G) to enter information such as a description and a transaction code on at least one interface. The mobile banking application (3) is configured to enable the sender user (G) to enter information such as the purpose of the transfer on at least one interface. The mobile banking application (3) is configured to enable the sender user (G) to view notifications that the transaction has been completed, rejected, expired, and / or successfully terminated on at least one interface.

[0032] The mobile banking application (3) included in the inventive system (1) is made available through the recipient’s financial institution server (5) and is configured to display the transfer notifications transmitted through the recipient’s financial institution server (5). The mobile banking application (3) is configured to enable the recipient user (A) to access the transfer message transmitted through the recipient’s financial institution server (5). The mobile banking application (3) is configured to enable the recipient user (A) to accept or reject a fund transfer from any financial institution mobile application to any account of his choice through messages received from any financial institution mobile application on at least one interface.

[0033] The sender financial institution server (4) included in the inventive system (1) is configured to transact in accordance with the instructions of its customers and preferred by its customers for sending or receiving funds; to store and keep confidential the data that people have shared when sending and receiving funds; to transmit the information contained in the orders placed by the sender users (G) through the mobile banking application (3) to the central server (7). The sender’s financial institution server (4) is configured to record all transactions to which it accesses through the mobile banking application (3) on the sender’s financial institution database (SD). The sender’s financial institution server (4) is configured to transmit all transactions for which records have been created in the sender’s financial institution database (GV) to the central server (7). The sender’s financial institution server (4) is configured to include a customer dashboard that stores data such as customer number, channel information, contract validity,contract validity, and customer type for all customers, both legal and individual, who have registered with a product use contract. The sender’s financial institution server (4) is configured to include a transfer package table that reflects the package equivalent of all transfers; and keeps a unique record of the package that is the subject of the bulk transfer in the case of sending multiple transactions through channels, such as FTP, mobile, internet banking with the file through the function to be launched for corporate and commercial customers; and keeps the details of each record in the detailed transfer table. The sender’s financial institution server (4) is configured to include a detailed transfer table that stores records of customers who order fund transfers through channels for the related transaction; contains fields for the sender’s and recipient’s TRIN / VIN, date of transaction, currency, payment type and amount; contains a reference number for each transaction; contains information, such as the date and time of the order, and the status of the transaction; and changes the status for each transaction and updates it with the transfer reports. The sender’s financial institution server (4) is configured to contain a detailed transfer sub-table that contains the transactions that have already been recognized. The sender’s financial institution server (4) is configured to include a table of equivalents that keeps the equivalents of the abbreviated records held in the detailed transfer table; holds the equivalents of the columns, such as payment type, status, and result; holds the equivalents required in different domains within the institution; and holds transaction equivalents to be used in official reporting. The sender’s financial institution server (4) is configured to include a transfer service log that stores the XML-like codes of the data transfer of customer transactions made through the central server (7); is a unique value for each transaction that customers enter in the records of the central server (7) and the recipient financial institution server (5); provides “serviceLogld+bankCode” singularity in service log tables for all organizations; provides the singularity of each sent “serviceLogld”; stores a unique “serviceLogld” value; and keeps the order variable in a new row to update for each transaction. The sender’s financial institution server (4) is configured to establish a connection with the electronic device (2) by using any communicationprotocol included in the state of the art and to communicate with the mobile banking application (3) running on the electronic device (2) through that established connection. The sender’s financial institution server (4) is configured to connect with the central server (7) by using any communication protocol included in the state of the art. The sender’s financial institution server (4) is configured to share the information that the sender user (G) enters through the mobile banking application (3) with the central server (7). The sender’s financial institution server (4) is configured to access the information that the transaction date has elapsed or has been rejected via the central server (7), and to transmit that information to the mobile banking application (3) of the sender user (S). The sender’s financial institution server (4) is configured to access the information that the transaction has ended without being accepted via the central server (7) and transmit that information to the mobile banking application (3) of the sender user (S). The sender’s financial institution server (4) is configured to access information that the recipient user (A) has approved the acceptance of payment for the transfer on the central database (7) and, if necessary, to transmit that information to the mobile banking application (3) of the sender user (S).

[0034] The recipient’s financial institution server (5) included in the inventive system (1) is configured to transact in accordance with the instructions of its customers and preferred by its customers for sending or receiving funds; to store and keep confidential the data that people have shared when sending and receiving funds. The recipient’s financial institution server (5) is configured to access the transfer message transmitted via the central server (7) and to transmit that transfer message to the mobile banking application (3) of the recipient user (R). The recipient’s financial institution server (5) is configured to include a customer dashboard that stores data such as customer number, channel information, contract validity, contract validity, and customer type for all customers, both legal and individual, who have registered with a product use contract. The recipient’s financial institution server (5) is configured to include a detailed transfer table that stores the records of fund transfers transmitted by the central server (7); andcontains fields for the sender’s and recipient’s TRIN / VIN, date of transaction, currency, payment type and amount; has a reference number for each transaction; contains information, such as the date and time of the order, and the status of the transaction; changes the status for each transaction and updates it with the transfer reports; and contain a recipient’s financial institution database (AV) holding the code of the sender’s financial institution server (4). The recipient’s financial institution server (5) is configured to include an incoming transaction detail table that keeps records of transactions that have already been recognized, and the records related to recognition when a transfer record in the recipient financial institution database (AV) has been recognized by the recipient user (A) after acceptance by the recipient user (R). The recipient’s financial institution server (5) is configured to include a table of equivalents — a pairing table where the equivalents of abbreviated records kept in the Detailed Inflow Transaction table can be kept-that holds the equivalents of the columns, such as Payment Type, Status, and Result; holds the equivalents required in different domains within the institution; and holds transaction equivalents to be used in Official Reporting. The recipient’s financial institution server (5) is configured to include an incoming service log table — a the log table that stores the XML codes of the data transfer of the transactions of the recipient users (A) made through the central server (7) — that keeps records for each incoming transaction for the recipient user (A) with the unique “serviceLogld” value sent by the sender’s financial institution server (4) through the central server (7); creates a row with the same “serviceLogld” as the order value 2 when the recipient user (A) sends an acceptance or rejection to the central server (7) for the transaction for which the recipient user (A) has been accepted or rejected based on the order, while the order value of the record sent by the central server (7) is 1 ; either ignores the recognition even if the response from the record succeeds, waits for the message, “transfer can be done”, or creates a new value for the same “serviceLogld” as the order 3 when a response is approved or rejected; and allows for the recognition to be processed when the message, “transfer can be done” is received. The recipient’s financial institution server (5) is configured to establish a connection with the electronic device (2) byusing any communication protocol included in the state of the art and to communicate with the mobile banking application (3) running on the electronic device (2) through that established connection. The recipient’s financial institution server (5) is configured to connect with the central server (7) by using any communication protocol included in the state of the art. The recipient’s financial institution server (5) is configured to notify the electronic device (2) of the recipient user (A) of the transfer over all channels of the choice of the recipient user (R). The recipient’s financial institution server (5) is configured to access information that the recipient user (A) has approved the acceptance of payment for the transfer on the Mobile Banking Application (3) and transmit that information to the central server (7). The recipient’s financial institution server (5) is configured to transmit that information to the central server (7) if transfer rejection is instructed. The recipient’s financial institution server (5) is configured to access a message that the transaction has ended via the central server (7) The recipient’s financial institution server (5) is configured to access the message “transfer can be done” via the central server (7).

[0035] The central database (6) included in the inventive system (1) is configured to connect with the central server (7). The central database (6) is configured to record information entered by the sender user (G) through the mobile banking application (3) therein. The central database (6) is configured to keep the transaction records transmitted through the central server (7) therein. The central database (6) is configured to record the information that the recipient user (A) has approved the acceptance of payment for the transfer.

[0036] The central server (7) included in the inventive system (1) is configured to access the transaction records transmitted via the sender’s financial institution server (4) and store them on the central database (6). The central server (7) is configured to send the transfer message to all recipient’s financial institution servers (5) to which the recipient user (A) is registered. The central server (7) is configured to function as a data centre; to exchange data and information; to keep the accountsof all intermediary institutions in all foreign currencies; to account for fund transfers that it intermediates based on the debit / credit principle for each transaction among these accounts; to send and receive funds to and from customers of banks and insurance and investment companies; and to store and keep confidential the data sent and received by organizations and individuals. The central server (7) is configured to include a financial institution details table that holds bank details, such as bank code, the account details of the sender’s financial institution server (4) and the recipient’s financial institution server (5) that process the transfer transactions, the account details of the sender user (G) and recipient user (R), and the web service details. The central server (7) is configured to include a sender financial institution spreadsheet that contains the transaction details transmitted by the sender financial institution server (4); is used as a source table and queries whether the TRIN / TIN data of the recipient user (A) is available for each record; changes the status of the transaction when at least one positive response has been received; puts the transaction in final status and never queries it again in case it has received a negative response from all institutions; renews the status of the transaction based on the receipt of acceptance or rejection messages from the recipient financial institution server (5) in case the transaction is in progress; writes the codes on the equivalent tables of the messages, such as “New” in the status column when a transaction has arrived, “Transmitted to Recipient’s Financial Institution” when the transaction has been transmitted to the recipient’s financial institution server (5), “Transaction Accepted” by filling in the bank details transmitting the acceptance message with the earliest date and the code details of the recipient’s financial institution server (5) when the recipient’s financial institution server (5) has responded with an acceptance, “Transaction Rejected by the Recipient” if all recipient’s financial institution servers (5) have responded with a rejection, “Transaction has been legally blocked” if no bank has accepted the message in case of a banned customer. The central server (7) is configured to include a recipient’s financial institution spreadsheet that records the transaction details for each recipient financial institution server (5) that has responded positively to the existence of a customer; creates records forinstitutions that respond positively to the TRIN / TIN query; writes the codes on the equivalent tables of the messages, such as “New” in the status column when a transaction has arrived, “Transaction Accepted” by fdling in the bank details transmitting the acceptance message with the earliest date and the code details of the recipient’s financial institution server (5) when the recipient’s financial institution server (5) has responded with an acceptance, “Transaction Rejected by the Recipient” if all recipient’s financial institution servers (5) have responded with rejection, “Transaction is legally blocked” if no bank has accepted the message in case of a banned customer. The central server (7) is configured to contain an incoming transaction service log table that stores incoming and outgoing messages when the sender’s financial institution servers (4) and the recipient’s financial institution servers (5) report that transactions have been initiated and accepted / rejected. The central server (7) is configured to include an outgoing transaction service log table that queries the recipient user (A) data; sends transactions to the recipient’s financial institution server (5); and stores outgoing and incoming messages in cases where it informs the sender’s financial institution server (4) that transactions have ended and have returned. The Central Server (7) is configured to connect with the sender’s financial institution server (4) and the recipient’s financial institution server (5) using any remote communication protocol included in the state of the art. The central server (7) is configured to access the information entered through the sender user (G) via the mobile banking application (3) through the sender’s financial institution server (4); and to save that information on the central database (6) for its transmission to the recipient’s financial institution server (5). The central server (7) is configured to store order messages received via the sender’s financial institution server (4) and query the country code, TRIN / TIN / GSM No, e-mail address and currency type of the recipient user (A) once they are processed in the central database (6). The central server (7) is configured to access a response that the transfer can be received for the queried recipient user (R), provided that the recipient user (A) holds at least one account in the currencies related to the transfer that can be recognized. The central server (7) is configured to access information that therecipient user (A) has approved the acceptance of payment for the transfer through the recipient’s financial institution server (5); to process that information in the central database (6); to forward it to the sender’s financial institution server (4); and to process the transfer record kept in the central database (6) for the acceptance message. The central server (7) is configured to consider the first message bearing the date and time in case of an arrival of the acceptance message; to update the status of the transfer record; and to transmit an error message that the transaction has ended. The central server (7) is configured to access the rejection instruction for the transfer via the recipient’s financial institution server (5) and transmit a message to the recipient’s financial institution server (5) informing that the transaction has ended. The central server (7) is configured to transmit the message “transfer can be done” to the recipient’s financial institution server (5) that sent the first acceptance message. The central server (7) is configured to transmit the information that the transaction date has elapsed or has been rejected to the sender’s financial institution server (4) in case the transaction date has elapsed or has been rejected. The central server (7) is configured to send a message to the sender’s financial institution server (4) that the transaction has ended without being accepted, if no acceptance message has been received by the recipient’s financial institution server (5).

[0037] Industrial Application of the Invention

[0038] The inventive system (1) allows to accept transfers to the same currency account of the recipient’s choice regardless of whether it is linked to a single IBAN or account number; assigns a different account for each currency if desired; to deposit the amount into the predetermined currency account without requiring any acceptance or rejection process in case of assignment; and to link it to not only a single account but also one account in each currency to its address.Within these basic concepts; it is possible to develop various embodiments of the inventive “A System (1) for The Transfer of Funds”; the invention cannot be limited to examples disclosed herein and it is essentially according to claims.

Claims

CLAIMS1. A system (1) which is developed with the aim of accepting transfers to the same currency account of the recipient’s choice regardless of whether it is linked to a single IBAN or account number; assigning a different account for each currency, if desired; depositing the amount into the predetermined currency account without requiring any acceptance or rejection process in case of assignment; and linking it to not only a single account but also one account in each currency to its address; comprisingat least one electronic device (2) which is configured to exchange data and run at least one application thereon by using any remote communication protocol;- at least one mobile banking application (2) which is configured to be run on an electronic device (3); to enable the sender user (G) to enter the necessary information on at least one interface to initiate the fund transfer; to select the account of the recipient user (A) on one interface for the acceptance of the transfer; and to declare the acceptance of the payment transaction;- at least one sender’s financial institution server (4) which is configured to transact in accordance with the instructions of its customers and preferred by its customers for sending or receiving funds; to store and keep confidential the data that people have shared when sending and receiving funds; to transmit the information contained in the orders placed by the sender users (G) through the mobile banking application (3);- at least one recipient’s financial institution server (5) which is configured to transact in accordance with the instructions of its customers and preferred by its customers for sending or receiving funds; to store and keep confidential the data that people have shared when sending and receiving funds; to transmit the information contained in recipient users (R);- at least one central database (6) which is configured to record the information entered by the sender user (G) through the mobile banking application (3) therein;and characterized byat least one central server (7) which is configured to function as a data centre; to exchange data and information; to keep the accounts of all intermediary institutions in all foreign currencies; to account for fund transfers that it intermediates based on the debit / credit principle for each transaction among these accounts; to send and receive funds to and from customers of banks and insurance and investment companies; and to store and keep confidential the data sent and received by organizations and individuals.

2. A system (1) according to Claim 1; characterized by the electronic device (2) which is configured to exchange data by using any remote communication protocol; and is a device such as mobile phone, tablet, desktop computer and / or a portable computer.

3. A system (1) according to Claim 1 or 2; characterized by the electronic device (2) which is configured to run the mobile banking application (3) thereon.

4. A system (1) according to Claim 3; characterized by the electronic device (2) which is configured to establish a connection with the sender’s financial institution server (4) and the recipient’s financial institution server (5) by using any remote communication protocol.

5. A system (1) according to any one of the preceding claims; characterized by the mobile banking application (3) which is configured to be run on the electronic device (2).

6. A system (1) according to any one of the preceding claims; characterized by the mobile banking application (3) which is made available through the sending financial institution server (4) and is configured to enable the sender user (G) to enter the necessary information on at least one interface to initiate the fund transfer.

7. A system (1) according to any one of the preceding claims; characterized by the mobile banking application (3) which is configured to enable the sender user (G) to enter the information of the recipient user (R), such as the recipient country code, TCKN7 VKN / GSM number, e-mail address, date of transaction, currency, payment type and amount on at least one interface.

8. A system (1) according to any one of the preceding claims; characterized by the mobile banking application (3) which is configured to enable the sender user (G) to enter information such as a description and a transaction code on at least one interface.

9. A system (1) according to any one of the preceding claims; characterized by the mobile banking application (3) which is configured to enable the sender user (G) to enter information such as the purpose of the transfer on at least one interface.

10. A system (1) according to any one of the preceding claims; characterized by the mobile banking application (3) which is configured to enable the sender user (G) to view notifications that the transaction has been completed, rejected, expired, and / or successfully terminated on at least one interface.

11. A system (1) according to any one of the preceding claims; characterized by the mobile banking application (3) which is made available through therecipient’s financial institution server (5) and is configured to display the transfer notifications transmitted through the recipient’s financial institution server (5).

12. A system (1) according to any one of the preceding claims; characterized by the mobile banking application (3) which is configured to enable the recipient user (A) to access the transfer message transmitted through the recipient’s financial institution server (5).

13. A system (1) according to any one of the preceding claims; characterized by the mobile banking application (3) which is configured to enable the recipient user (A) to accept or reject a fund transfer from any financial institution mobile application to any account of his choice through messages received from any financial institution mobile application on at least one interface.

14. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to transact in accordance with the instructions of its customers and preferred by its customers for sending or receiving funds; to store and keep confidential the data that people have shared when sending and receiving funds; to transmit the information contained in the orders placed by the sender users (G) through the mobile banking application (3) to the central server (7).

15. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to record all transactions to which it accesses through the mobile banking application (3) on the sender’s financial institution database (SD).

16. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to transmit all transactions for which records have been created in the sender’s financial institution database (GV) to the central server (7).

17. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to include a customer dashboard that stores data such as customer number, channel information, contract validity, contract validity, and customer type for all customers, both legal and individual, who have registered with a product use contract.

18. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to include a transfer package table that reflects the package equivalent of all transfers; and keeps a unique record of the package that is the subject of the bulk transfer in the case of sending multiple transactions through channels, such as FTP, mobile, internet banking with the file through the function to be launched for corporate and commercial customers; and keeps the details of each record in the detailed transfer table.

19. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to include a detailed transfer table that stores records of customers who order fund transfers through channels for the related transaction; contains fields for the sender’s and recipient’s TRIN / VIN, date of transaction, currency, payment type and amount; contains a reference number for each transaction; contains information, such as the date and time of the order, and the status of the transaction; and changes the status for each transaction and updates it with the transfer reports.

20. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to contain a detailed transfer sub-table that contains the transactions that have already been recognized.

21. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to include a table of equivalents that keeps the equivalents of the abbreviated records held in the detailed transfer table; holds the equivalents of the columns, such as payment type, status, and result; holds the equivalents required in different domains within the institution; and holds transaction equivalents to be used in official reporting.

22. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to include a transfer service log that stores the XML-like codes of the data transfer of customer transactions made through the central server (7); is a unique value for each transaction that customers enter in the records of the central server (7) and the recipient financial institution server (5); provides “serviceLogld+bankCode” singularity in service log tables for all organizations; provides the singularity of each sent “serviceLogld”; stores a unique “serviceLogld” value; and keeps the order variable in a new row to update for each transaction.

23. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to establish a connection with the electronic device (2) by using any communication protocol included in the state of the art and to communicate with the mobile banking application (3) running on the electronic device (2) through that established connection.

24. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to connect with the central server (7) by using any communication protocol.

25. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to share the information that the sender user (G) enters through the mobile banking application (3) with the central server (7).

26. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to access the information that the transaction date has elapsed or has been rejected via the central server (7), and to transmit that information to the mobile banking application (3) of the sender user (S).

27. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to access the information that the transaction has ended without being accepted via the central server (7) and transmit that information to the mobile banking application (3) of the sender user (S).

28. A system (1) according to any one of the preceding claims; characterized by the sender financial institution server (4) which is configured to access information that the recipient user (A) has approved the acceptance of payment for the transfer on the central database (7) and, if necessary, to transmit that information to the mobile banking application (3) of the sender user (S).

29. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to transact in accordance with the instructions of its customers and preferredby its customers for sending or receiving funds; to store and keep confidential the data that people have shared when sending and receiving funds.

30. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to access the transfer message transmitted via the central server (7) and to transmit that transfer message to the mobile banking application (3) of the recipient user (R).

31. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to include a customer dashboard that stores data such as customer number, channel information, contract validity, contract validity, and customer type for all customers, both legal and individual, who have registered with a product use contract.

32. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to include a detailed transfer table that stores the records of fund transfers transmitted by the central server (7); and contains fields for the sender’s and recipient’s TRIN / VIN, date of transaction, currency, payment type and amount; has a reference number for each transaction; contains information, such as the date and time of the order, and the status of the transaction; changes the status for each transaction and updates it with the transfer reports; and contain a recipient’s financial institution database (AV) holding the code of the sender’s financial institution server (4).

33. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to include an incoming transaction detail table that keeps records oftransactions that have already been recognized, and the records related to recognition when a transfer record in the recipient financial institution database (AV) has been recognized by the recipient user (A) after acceptance by the recipient user (R).

34. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to include a table of equivalents a pairing table where the equivalents of abbreviated records kept in the Detailed Inflow Transaction table can be kept-that holds the equivalents of the columns, such as Payment Type, Status, and Result; holds the equivalents required in different domains within the institution; and holds transaction equivalents to be used in Official Reporting.

35. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to include an incoming service log table -a the log table that stores the XML codes of the data transfer of the transactions of the recipient users (A) made through the central server (7) - that keeps records for each incoming transaction for the recipient user (A) with the unique “serviceLogld” value sent by the sender’s financial institution server (4) through the central server (7); creates a row with the same “serviceLogld” as the order value 2 when the recipient user (A) sends an acceptance or rejection to the central server (7) for the transaction for which the recipient user (A) has been accepted or rejected based on the order, while the order value of the record sent by the central server (7) is 1; either ignores the recognition even if the response from the record succeeds, waits for the message, “transfer can be done”, or creates a new value for the same “serviceLogld” as the order 3 when a response is approved or rejected; and allows for the recognition to be processed when the message, “transfer can be done” is received.

36. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to establish a connection with the electronic device (2) by using any communication protocol included in the state of the art and to communicate with the mobile banking application (3) running on the electronic device (2) through that established connection.

37. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to connect with the central server (7) by using any communication protocol.

38. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to notify the electronic device (2) of the recipient user (A) of the transfer over all channels of the choice of the recipient user (R).

39. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to access information that the recipient user (A) has approved the acceptance of payment for the transfer on the Mobile Banking Application (3) and transmit that information to the central server (7).

40. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to transmit that information to the central server (7) if transfer rejection is instructed.

41. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to access a message that the transaction has ended via the central server (7).

42. A system (1) according to any one of the preceding claims; characterized by the recipient’s financial institution server (5) which is configured to access the message “transfer can be done” via the central server (7).

43. A system (1) according to any one of the preceding claims; characterized by the central database (6) which is configured to connect with the central server (7).

44. A system (1) according to any one of the preceding claims; characterized by the central database (6) which is configured to record information entered by the sender user (G) through the mobile banking application (3) therein.

45. A system (1) according to any one of the preceding claims; characterized by the central database (6) which is configured to keep the transaction records transmitted through the central server (7) therein.

46. A system (1) according to any one of the preceding claims; characterized by the central database (6) which is configured to record the information that the recipient user (A) has approved the acceptance of payment for the transfer.

47. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to access the transaction records transmitted via the sender’s financial institution server (4) and store them on the central database (6).

48. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to send the transfer message to all recipient’s financial institution servers (5) to which the recipient user (A) is registered.

49. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to function as a data centre; to exchange data and information; to keep the accounts of all intermediary institutions in all foreign currencies; to account for fund transfers that it intermediates based on the debit / credit principle for each transaction among these accounts; to send and receive funds to and from customers of banks and insurance and investment companies; and to store and keep confidential the data sent and received by organizations and individuals.

50. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to include a financial institution details table that holds bank details, such as bank code, the account details of the sender’s financial institution server (4) and the recipient’s financial institution server (5) that process the transfer transactions, the account details of the sender user (G) and recipient user (R), and the web service details.

51. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to include a sender financial institution spreadsheet that contains the transaction details transmitted by the sender financial institution server (4); is used as a source table and queries whether the TRIN / TIN data of the recipient user (A) is available for each record; changes the status of the transaction when at least one positive response has been received; puts the transaction in final status and never queries it again in case it has received a negative response from all institutions; renews the status of the transaction based on the receipt of acceptance or rejection messages from the recipient financial institution server (5) in case the transaction is in progress; writes the codes on the equivalent tables of the messages, such as “New” in the status column when a transaction has arrived, “Transmitted to Recipient’s FinancialInstitution” when the transaction has been transmitted to the recipient’s financial institution server (5), “Transaction Accepted” by filling in the bank details transmitting the acceptance message with the earliest date and the code details of the recipient’s financial institution server (5) when the recipient’s financial institution server (5) has responded with an acceptance, “Transaction Rejected by the Recipient” if all recipient’s financial institution servers (5) have responded with a rejection, “Transaction has been legally blocked” if no bank has accepted the message in case of a banned customer.

52. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to include a recipient’s financial institution spreadsheet that records the transaction details for each recipient financial institution server (5) that has responded positively to the existence of a customer; creates records for institutions that respond positively to the TRIN / TIN query; writes the codes on the equivalent tables of the messages, such as “New” in the status column when a transaction has arrived, “Transaction Accepted” by filling in the bank details transmitting the acceptance message with the earliest date and the code details of the recipient’s financial institution server (5) when the recipient’s financial institution server (5) has responded with an acceptance, “Transaction Rejected by the Recipient” if all recipient’s financial institution servers (5) have responded with rejection, “Transaction is legally blocked” if no bank has accepted the message in case of a banned customer.

53. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to contain an incoming transaction service log table that stores incoming and outgoing messages when the sender’s financial institution servers (4) and the recipient’sfinancial institution servers (5) report that transactions have been initiated and accepted / rejected.

54. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to include an outgoing transaction service log table that queries the recipient user (A) data; sends transactions to the recipient’s financial institution server (5); and stores outgoing and incoming messages in cases where it informs the sender’s financial institution server (4) that transactions have ended and have returned.

55. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to connect with the sender’s financial institution server (4) and the recipient’s financial institution server (5) using any remote communication protocol.

56. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to access the information entered through the sender user (G) via the mobile banking application (3) through the sender’s financial institution server (4); and to save that information on the central database (6) for its transmission to the recipient’s financial institution server (5).

57. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to store order messages received via the sender’s financial institution server (4) and query the country code, TRIN / TIN / GSM No, e-mail address and currency type of the recipient user (A) once they are processed in the central database (6).

58. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to access a response that thetransfer can be received for the queried recipient user (R), provided that the recipient user (A) holds at least one account in the currencies related to the transfer that can be recognized.

59. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to access information that the recipient user (A) has approved the acceptance of payment for the transfer through the recipient’s financial institution server (5); to process that information in the central database (6); to forward it to the sender’s financial institution server (4); and to process the transfer record kept in the central database (6) for the acceptance message.

60. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to consider the first message bearing the date and time in case of an arrival of the acceptance message; to update the status of the transfer record; and to transmit an error message that the transaction has ended.

61. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to access the rejection instruction for the transfer via the recipient’s financial institution server (5) and transmit a message to the recipient’s financial institution server (5) informing that the transaction has ended.

62. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to transmit the message “transfer can be done” to the recipient’s financial institution server (5) that sent the first acceptance message.

63. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to transmit the information that the transaction date has elapsed or has been rejected to the sender’s financial institution server (4) in case the transaction date has elapsed or has been rejected.

64. A system (1) according to any one of the preceding claims; characterized by the central server (7) which is configured to send a message to the sender’s financial institution server (4) that the transaction has ended without being accepted, if no acceptance message has been received by the recipient’s financial institution server (5).

Images