KR20230088178A - Electronic Funds Transfer Method based on Payee for Safety Transaction - Google Patents

Abstract

A recipient authentication-based electronic funds transfer method for safe transaction is disclosed. In this method, the service providing system performs electronic funds transfer according to the request of the sender, but prior to the transfer, the recipient is authenticated using text message or voice message. At least one trust procedure is performed between the confirmation procedure and the beneficiary consent procedure, and electronic funds transfer is performed only when reliability is secured through the result of the trust procedure.

Description

Electronic Funds Transfer Method based on Payee for Safety Transaction}

The present invention relates to a financial service, and more particularly, to an electronic funds transfer service through authentication of a beneficiary in a non-financial institution, which is a non-financial institution providing a fund transfer service.

The electronic funds transfer service has conventionally been to transfer funds from an account opened at a financial company to another account by electronic devices for the purpose of distributing funds between a sender and a recipient. , Naver, Kakao, Toss, etc.) through an account held by the sender, other than an account opened at a financial company, to an account opened at a financial company held by the recipient or an account at a service company by electronic device. do. In the transfer method provided by many service companies, unlike the existing electronic funds transfer method, when a sender requests transfer to a service company, the transfer is completed by requesting an account transfer using the recipient's ID or phone number rather than the recipient's account number. That is, only the sender is authenticated and the funds are transferred if there is no problem, but the transfer is made using the balance of the account, not the sender's account, or the sender withdraws from an account designated by the sender, and the transfer is made after charging. However, since the recipient's ID or phone number can be changed at any time depending on the recipient's circumstances, the changed phone number may be provided to the sender immediately or late in some cases, and also when remittance is made to the recipient's ID. There are various cases such as the phone number associated with the ID may be changed. In addition, if there is no problem by only authenticating the sender without authentication of the recipient, the transfer of funds is carried out. Therefore, it is difficult to prevent erroneous remittance due to mistaken remittance, phishing fraud, impersonation fraud, direct transaction fraud, etc., and it is also difficult to resolve monetary transaction disputes after the fact.

In the case of disputes over money transactions between individuals, there are cases where evidence is insufficient only with the transfer transaction details. In the past, the sender had to additionally manage individual evidence to prevent disputes in transfer transactions. In the case of direct transactions between individual accounts, fraud may occur due to the failure to identify the recipient (seller). In addition, there are many phishing accidents such as voice phishing and messenger phishing. To prevent this, the sender must follow the analog procedure of contacting the recipient (acquaintance) and then making the final transfer, but the reality is that it is not properly followed.

In addition, in the case of a real estate buyer, mistakes can also occur when transferring funds. For example, mistakes due to lack of communication between the real estate broker, the buyer, and the seller, such as mistakenly transferring the sales amount before final confirmation of the seller's prepared documents. that can happen

That is, it is required to improve the electronic fund transfer method due to various accidents not mentioned above.

Domestic Registered Patent Publication No. 10-2314749 (Announced on October 19, 2021)

An object of the present invention is to provide a method for preventing erroneous remittance that may be sent due to mistaken remittance, phishing fraud, impersonation fraud, direct transaction fraud, and the like.

In addition, the present invention prevents erroneous remittance that may be sent due to mistaken remittance, phishing fraud, impersonation fraud, direct transaction fraud, etc. It aims to provide more ways to prevent it.

In addition, an object of the present invention is to provide a method for preventing disputes after a financial transaction through electronic funds transfer.

In the recipient authentication-based electronic funds transfer method for safe transaction according to one aspect, the service providing system selects the transfer service selected according to the sender's remittance purpose from among a plurality of transfer services belonging to the transfer menu and transfer amount and recipient's account information from the sender. and receiving basic information including at least one of the recipient's phone number and deposit account number and additional information for non-face-to-face safe transaction, and the service providing system searches the recipient's name through the recipient information belonging to the basic information, Checking whether the additional information further includes a payee authentication request, and when the additional information further includes the payee authentication request is received, the service providing system converts the payee phone number and authentication additional information necessary for the payee authentication to the payee authentication. The steps of transmitting the text message to the system, the recipient authentication system generating a text message including the reply code for recipient authentication, and sending the generated text message to the recipient terminal to which the phone number has been assigned. After the received text message is displayed on the screen and the recipient checks it, the reply code is input from the recipient and sent to the recipient authentication system. The step of checking whether or not they match and replying to the service providing system, and the service providing system provides the transfer service received from the sender when it is confirmed that there is no error in the recipient's phone number according to the result of the recipient authentication procedure returned from the recipient authentication system. steps may be included.

In the recipient authentication-based electronic funds transfer method for safe transaction according to another aspect, the service providing system determines the transfer amount from the sender and the recipient's account through a transfer service selected according to the sender's remittance purpose from among a plurality of transfer services belonging to the transfer menu. Receiving basic information including information and at least one of the recipient's phone number and deposit account number and additional information for non-face-to-face safe transaction, and the service providing system searches the recipient's name through the recipient information belonging to the basic information , checking whether the additional information further includes a payee authentication request, and when the additional information further includes the payee authentication request is received, the service providing system transmits the payee phone number and authentication additional information necessary for the payee authentication to the payee. Transmitting to an authentication system, the recipient authentication system generates a voice message including a reply code for recipient authentication, and calls the generated voice message to the recipient terminal to which the recipient's phone number is assigned to obtain a voice message through an ARS connection. and, after the recipient checks this, the reply code is input from the payee and transmitted to the payee authentication system, the payee authentication system checks whether the received reply code matches the authentication code included in the voice message provided to the payee terminal. Confirming and replying to the service providing system, and providing the transfer service received from the sender when the service providing system confirms that there is no error in the recipient's phone number according to the result of the recipient authentication procedure returned from the recipient authentication system. can

The service providing system transmits the inquired payee name, additional information received from the sender, and the transaction type identifier assigned to the transfer service selected by the sender to a third trusted intermediary institution system, and the third trusted intermediary institution system transmits the service providing system Confirming the transaction type identifier received from the third trust intermediary institution system with additional information according to the identified transaction type identifier and proceeding with at least one trust procedure among the recipient name confirmation procedure and the recipient consent procedure; The third trust intermediary system returns the trust procedure processing result to the service providing system, and the financial institution system receives the basic information received from the sender when the transfer trust is guaranteed according to the trust procedure processing result returned from the third trust intermediary system. Including the step of transferring using information, but in the trust procedure step, if the confirmed transaction type identifier is the first transaction type identifier, the recipient name verification procedure is performed, and the confirmed transaction type identifier is the second transaction type identifier In this case, the recipient consent procedure is carried out, and if the confirmed transaction type identifier is the third transaction type identifier, the recipient name confirmation procedure and the recipient consent procedure may be included.

In the transfer menu, there is a suspicious fraud transfer service with the 1st transaction type identifier assigned, a transfer service for real estate transaction with the 2nd transaction type identifier, a transfer service after multilateral agreement, a transfer service based on confirmation of request for acquaintances, and a transfer to prevent erroneous remittance. A transfer service requiring proof of transaction between service and individual, a transfer service for non-face-to-face direct transaction evidence with a third transaction type identifier, and a transfer service based on confirmation of the recipient's mobile phone name may include a recipient authentication request menu.

When receiving the reply code from the payee's terminal, it may include receiving a reply code input by the payee and sent as a text message or a reply code transmitted through an ARS connected to the payee's terminal.

The present invention classifies transactions requiring fraud prevention or proof of transaction in interpersonal electronic fund transfer transactions by type, and trust procedure (confirmation of whether the recipient's name and recipient's mobile phone name matches and / or electronic funds transfer By having the recipient agree to the transaction) and storing the transfer transaction data between the two parties, it is possible to detect and block fraudulent/suspicious transactions, and to prevent or prove post-money disputes.

In particular, detection of fraudulent/suspicious transactions by providing a safer and stronger authentication service by additionally performing authentication using text messages or ARS for recipients rather than authenticating only the sender in existing electronic financial transactions and create an effect that enables post-war dispute prevention.

1 is a block diagram of an electronic funds transfer system according to an embodiment.
2 is a flow chart of an electronic funds transfer method according to an embodiment.
3 is a diagram illustrating required input information for each transfer service belonging to the transfer menu.
Fig. 4 is a detailed flowchart of the process of authentication of a payee shown in Fig. 2 according to an embodiment.
Fig. 5 is a detailed flowchart of the trust procedure shown in Fig. 2 according to an embodiment.
6 is a flowchart for setting mobile carrier priorities in a third trusted intermediary system according to an embodiment.
7 is a flow chart of transfer transaction information inquiry according to an embodiment.

Hereinafter, the operating principle of a preferred embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the drawings shown below and the description to be described below relate to preferred implementation methods among various methods for effectively explaining the features of the present invention, and the present invention is not limited only to the drawings and description below.

In addition, in the following description of the present invention, if it is determined that a detailed description of a related known technology or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted. Terms to be described later are terms defined in consideration of functions in the present invention, and may vary according to intentions or customs of users or operators. Therefore, this definition should be made based on the contents throughout the present invention.

As a result, the technical spirit of the present invention should be determined by the claims, and the following embodiments may be a means for efficiently explaining the technical spirit of the present invention to those skilled in the art to which the present invention belongs. only

As a result, the technical spirit of the present invention is determined by the claims, and the following examples are only means for efficiently explaining the technical spirit of the present invention to those skilled in the art to which the present invention belongs. .

1 is a block diagram of an electronic funds transfer system according to an embodiment. The sender terminal 100 and the recipient terminal 200 are communication terminals used by a sender who transfers electronic funds and a recipient who receives electronic funds, respectively, and may be PCs, smartphones, or automated devices. The sender terminal 100 can communicate with the service providing system 300 and the third trusted intermediary institution system 400, respectively, and the recipient terminal 200 can communicate with the payee authentication system 700 and the third trusted intermediary institution system 400. can communicate with one or more of And, when the sender terminal 100 is a mobile terminal, an application that works with the service providing system 300 may be installed and executed.

The recipient authentication system 700 may include one or more of a server for verifying that the electronic funds transfer requested by the sender is carried out accurately and safely for the recipient desired by the sender, a server for sending and receiving text messages, and an ARS server. there is.

The service providing system 300, the financial institution system 600, the third trusted intermediary institution system 400, and the mobile communication company system 500 are server systems each consisting of one or more servers. For example, the service providing system 300 includes a server in charge of electronic fund transfer processing in conjunction with the financial institution system 600 and a server in charge of checking whether a safe transaction is in conjunction with the third trusted intermediary institution system 400. It is composed of two parts. In addition, the financial institution system 600 may be composed of a server that supports electronic fund transfer processing in conjunction with the service providing system 300, and the third trusted intermediary institution system 400 checks whether the sender's electronic fund transfer is safe. It can be composed of a server for performing trust procedures, a server for sending and receiving text messages, and an ARS server.

The service providing system 300 is not a financial institution such as a bank that provides various services necessary for Internet use or remittance, but is operated by an institution that provides various financial services similar to a financial institution, and is operated under a web or app environment. Handle sender's request for electronic funds transfer. The financial institution system 600 is operated by a financial institution such as a bank, and serves to process a sender's electronic fund transfer request in association with the service providing system 300 . The third trust intermediary system 400 is operated by a third trust intermediary, not a financial institution, and plays a role in preventing fraud or transaction proof for electronic fund transfer by a sender in association with the service providing system 300. carry out As a third trusted intermediary institution, an institution trusted in electronic financial transactions such as the Korea Credit Bureau (KCB) may be cited as an example. In addition, the mobile communication service provider systems 500 are operated by different mobile communication service providers, and perform a role of querying and replying to corresponding information according to a search request of the third trust agency system 400 .

Here, the third trust intermediary institution system 400 is interlocked with a financial institution, not the service providing system 300, and can play a role for fraud prevention or transaction proof for a sender's electronic fund transfer.

The recipient authentication system 700, when a remittance request by a sender is received by the service providing system 300, either before the request for remittance is completed or before the remittance is made to the recipient by the request of the service providing system 300 At the time, it serves to authenticate the payee based on information about the sender entered by the payee, separately from the authentication procedure for the payee by the third trust intermediary system 400 for the payee.

Meanwhile, the electronic funds transfer system may include all of the components shown in FIG. 1, but may include only some of them. For example, the electronic funds transfer system includes a service providing system 300, a financial institution system 600, a payee authentication system 700, and a third trusted intermediary institution system 400 among the components shown in FIG. 1. . As another example, the electronic funds transfer system includes a service providing system 300, a financial institution system 600, a payee authentication system 700, a third trusted intermediary institution system 400, and a service app ( 110) are included. In addition, various types of system configurations are possible.

2 is a flow chart of an electronic funds transfer method according to an embodiment. The sender terminal 100 accesses the service providing system 300 and attempts remittance through the transfer menu. Here, the transfer menu includes a plurality of transfer services classified according to a plurality of transfer purposes, and the sender selects one of the plurality of transfer services according to the transfer purpose of the sender. In one embodiment, the transfer menu includes a suspected fraud transfer service, a transfer service for real estate transaction, a transfer service after multilateral agreement, a transfer service based on confirmation of request for an acquaintance, a transfer service for preventing mistaken remittance, and evidence of transaction between individuals. A necessary transfer service, a transfer service for proof of non-face-to-face direct transactions, and a transfer service based on confirmation of the recipient's mobile phone name are included. In addition, the sender may further request authentication of the recipient at the time of selecting one of a plurality of transfer services according to the purpose of the transfer.

When the electronic funds transfer service is performed on a web basis, the service providing system 300 provides a transfer menu to the sender terminal 100, and when the electronic funds transfer service is performed on an app basis, the service app 110 provides a transfer menu. It can be provided directly to the sender.

The sender terminal 100 receives information required for the transfer service selected by the sender and transmits it to the service providing system 300 and requests remittance (S100). Input information includes basic information essential for remittance and additional information for safe transactions. Basic information corresponds to cash according to the method of remittance by the sender, and information on the account where the cyber money previously accumulated by the sender through various means such as charging (can be omitted in some cases) and deposit account number (recipient's account number) or If information to identify the recipient, such as recipient account information or recipient's phone number, and deposit account number are included, cyber money (i.e., transfer amount) to be transferred with the depositing bank (recipient bank) is included. If you want to transfer money in a insufficient state, withdrawal account information (ie, withdrawal account number and withdrawal bank) and charge amount information necessary for charging cyber money are included, and the password of the withdrawal account for charging cyber money may also be included. Here, if information other than the deposit account number for identifying the recipient is included, the name of the recipient may be included.

And, the additional information includes at least one of recipient information and recipient consent request message. That is, according to the transfer service, only one of the recipient's phone number and the recipient's consent request message or both are required.

In one embodiment, in the suspected fraud transfer service, only the recipient's phone number is required as additional information, and in the non-face-to-face direct transaction proof transfer service and the recipient's mobile phone name confirmation-based transfer service, the recipient's phone number and the recipient's consent request message are additional information All are required, and only the recipient consent request message is required as additional information in the rest of the transfer service. For reference, information to be input by the sender for each transfer service is illustrated in FIG. 3 . In FIG. 3 , additional input items mean additional information, and additional input items required for each transfer service may be different as shown in FIG. 3 .

In addition, in the case where the beneficiary consent request message is entered and provided by the beneficiary in the electronic funds transfer service, if the beneficiary authentication process is included, the beneficiary consent request message can be used during the beneficiary authentication process. In this case, a third It may not be used in the course of a trust procedure for a transaction trust confirmation request through the trust intermediary institution system 400 .

The service providing system 300 requests the financial institution system 600 to inquire the beneficiary name for the deposit account number belonging to the basic information, and the financial institution system 600 retrieves the beneficiary name at the request of the service providing system 300. It is inquired and provided to the service providing system 300 (S105) (S110) (S115). If information other than the deposit account number (recipient's account information or recipient's phone number) is included, the recipient's name inquiry process can be omitted. Here, only the recipient's name inquiry process for the deposit account number is shown, but if the recipient's phone number is included in the basic information, it can be replaced with a process of making a name inquiry for the phone number through linkage with a telecommunications company. When the payee name is inquired, the service providing system 300 proceeds with the payee authentication process while transferring the payee phone number and authentication additional information to the payee authentication system 700 . Here, the service providing system 300 can proceed with subsequent procedures when it is confirmed that there is no error in the payee's phone number according to the result of the payee authentication process returned from the payee authentication system 700 .

When the payee name is inquired, the service providing system 300 proceeds with the payee authentication procedure while transferring the payee's phone number and authentication additional information to the payee authentication system 700 (S120). Here, the service providing system 300 can proceed with subsequent procedures when it is confirmed that there is no error in the payee's phone number according to the result of the payee authentication process returned from the payee authentication system 700 .

The service providing system 300 may perform the transaction trust confirmation procedure first before the payee authentication procedure, but for convenience of explanation, it is illustrated that the transaction trust confirmation procedure is performed after the payee authentication procedure is performed first.

If it is confirmed that there is no error in the recipient's phone number, the service providing system 300 transfers the recipient's name and additional information to the third trusted intermediary institution system 400 and requests transaction trust confirmation (S125). At this time, the service providing system 300 delivers a corresponding transaction type identifier according to the transfer service selected by the sender. For example, the transaction type identifier may be any one of the first transaction type identifier '1', the second transaction type identifier '2', and the third transaction type identifier '3', where '1' is the recipient's name and the recipient's phone number. It is a separator indicating that confirmation of identity of the name is required, '2' is a separator indicating that consent of the recipient is required, and '3' is a separator indicating that both of the above are required.

The third trusted intermediary institution system 400 checks the transaction type identifier received from the service providing system 300 (S130). Through this, the transaction type identifier can be identified as one of '1', '2', and '3'. The third trust intermediary institution system 400 proceeds with a corresponding trust procedure according to the identified transaction type classifier (S135). That is, if the transaction type identifier is '1', it is checked whether the name of the recipient and the name of the phone number of the recipient are identical. It checks whether it is the same and performs it as a recipient consent procedure. When the trust procedure is completed, the third trust agency system 400 notifies the service providing system 300 of the trust procedure processing result (S145).

The service providing system 300 performs account transfer according to basic information in association with the financial institution system 600 only when the transfer trust is guaranteed through the trust procedure processing result of the third trust intermediary system 400, and the transfer is performed. If trust is not guaranteed, the final process of canceling the transfer is performed (S150). That is, when the transaction type identifier is '1', the service providing system 300 transfers the account according to the basic information if the recipient's name and the recipient's phone number match, and otherwise cancels the transfer. If the transaction type identifier is '2', the account transfer is performed if the recipient agrees, otherwise the transfer is canceled. And, if the transaction type identifier is '3', the account transfer is performed if the name is matched and the recipient's consent is made, and if not, the transfer is canceled. Here, if the recipient's phone number is included in the basic information provided by the sender, and a name search for the recipient's phone number has already been performed, some of the trust procedure processing procedures of the third trust agency system 400 may be omitted. there is.

The service providing system 300 notifies the final processing result of the previous step to the third trust intermediary system 400 (S155). At this time, the sender's phone number may be delivered together. Alternatively, the sender's phone number may be delivered in advance when requesting confirmation of trust in the previous transaction. In one embodiment, when the final processing result is notified, it is performed only when the final processing is a transfer and is not performed when the transfer is canceled. When the third trusted intermediary system 400 is notified of the final processing result from the service providing system 300, it transmits the final processing result to the sender terminal 100 to which the sender's phone number is assigned (S160). In addition, the third trust intermediary system 400 may also send a text message of the final processing result to the recipient terminal 200, but this may be limited to the case where a transfer is made.

In addition, the third trust agency system 400 may store and store the corresponding information in a database according to the trust procedure processing result obtained through the trust procedure in the above process (S140). The stored information includes at least a part of the service name, sender's name, beneficiary's name, beneficiary's phone number, recipient's consent request message, and trust procedure processing results. In one embodiment, storing and storing in a corresponding database according to the trust procedure processing result is performed only when the trust procedure processing result is a result of allowing the transfer. Also, although not shown in FIG. 2 , the third trust intermediary system 400 may provide the information stored in the database (transfer transaction information) to the sender or recipient for a fee or free of charge according to the request of the sender or recipient. Here, the database may be a database linked to the trust intermediary system or a separate database operated externally. It is also possible to operate in the form of provided smart contracts.

On the other hand, storing and storing the corresponding information in the database according to the trust procedure processing result obtained through the trust procedure proceeding does not have to be performed before notifying the trust procedure processing result to the service providing system 300, and the corresponding trust procedure according to the transaction type classifier. It is sufficient as long as it is performed after the procedure. For example, storing and storing corresponding information in a database according to the trust procedure processing result obtained through the trust procedure progress may be performed after notifying the third trust intermediary institution system 400 of the final processing result. In addition, the information to be provided from the service providing system 300 among all the information to be stored by storing the corresponding information in the database according to the trust procedure processing result obtained through the trust procedure proceeding requires transaction trust confirmation while delivering the recipient name and additional information. It can be delivered all together, or it can be delivered separately. For example, some information is transmitted to the third trust broker system 400 when the third trust broker system 400 is notified of the final processing result, not when transaction trust confirmation is requested while transmitting the payee name and additional information. .

In the flowchart shown in FIG. 3, it is shown that the transaction trust confirmation request is made by the service providing system 300, but the transaction trust confirmation request is made in the service providing system 300, not the service providing system 300, in the financial institution system. It is also possible for the financial institution system 600 to perform the request by calling 600 .

In addition, in processing transfer, if the information provided by the sender is account information or phone number rather than the recipient's account information, a process of notifying the recipient that there is a remittance record and processing the transfer to the recipient's account may be added. In this case, it is also possible that the trust procedure proceeds at the time the money is deposited into the recipient's account.

Fig. 4 is a detailed flowchart of the process of authentication of a payee shown in Fig. 2 according to an embodiment. The service providing system 300 checks whether the account transfer request of the sender terminal 100 includes a recipient authentication request according to the flowchart shown in FIG. 3 (S300). If the recipient authentication request is not included, the service providing system 300 skips the recipient authentication procedure and proceeds with the account transfer request of the sender terminal 100 . If the recipient authentication request is included, the service providing system 300 transmits the recipient phone number and authentication additional information to the recipient authentication system 700 and requests recipient authentication (S210). Here, the authentication additional information may include a reply code promised in advance with the payee in the message requesting the consent of the payee between the sender and the payee.

The payee authentication system 700 generates a text message including a reply code for payee authentication and sends the generated text message to the payee terminal 200 to which the payee phone number is assigned (S220 and S230). Here, the reply code included in the generated text message is either used if there is a reply code agreed in advance between the sender and the receiver, or the reply code generated by the receiver authentication system 700 is provided to the receiver through a separate means. Alternatively, it is possible to be included in the text message and provided.

The payee terminal 200 displays the text message received from the payee authentication system 700 on the screen so that the payee can check it, and when a reply code is input from the payee, the text message is transmitted to the payee authentication system 700. (S240). The recipient authentication system 700 uses an authentication code included in a text message sent to the recipient terminal 200 to verify recipient authentication and a reply code entered by the recipient included in the text message transmitted from the recipient terminal 200. It compares and checks whether they match (S250) (S260). When verification is completed, the payee authentication system 700 transmits the payee authentication process result to the service providing system 300 (S270). Here, the payee authentication system 700 can further check whether the payee phone number received from the service providing system 300 matches the phone number received in the text message including the reply code.

In one embodiment, when the authentication code and the reply code match, the service providing system 300 is notified of the processing result of the recipient authentication procedure according to confirming that there is no error in the recipient's phone number provided by the sender, and the authentication code and If the reply code does not match or if the reply code is not received within a predetermined time after sending the text message containing the verification code, the service providing system 300 displays the result of the recipient authentication process informing that there is an error in the recipient's phone number provided by the sender. be notified by

In one embodiment, a method of receiving a reply code from a recipient is described as receiving the reply code using a text message for convenience in FIG. 4 , but it is also possible to receive the reply code using ARS. In this case, a text message including a reply code for authentication of the recipient is generated, and the generated text message is sent to the recipient's terminal 200 to which the recipient's phone number is assigned (S220) (S230) to send a voice message to guide the recipient. The created voice message is changed to provide a voice message through an ARS connection by making a call to the recipient terminal 200 to which the recipient's phone number is assigned, and the authentication code included in the voice message provided to the recipient terminal 200 It is changed to compare and confirm whether the response code transmitted through ARS from the recipient terminal 200 matches.

Here, the reply code received through the ARS can be transmitted by the recipient through a text message, and can also be received through the ARS after the reply code through the ARS is provided as a text message.

Meanwhile, FIG. 4 is a procedure performed when the sender requests authentication of the recipient in the recipient authentication system 700, and the trust procedure between the service providing system 300 and the third trusted intermediary institution system 400 is in progress as needed. It is possible that this is done if there is something wrong with the recipient's phone number.

Fig. 5 is a detailed flowchart of the trust procedure shown in Fig. 2 according to an embodiment. The third trusted intermediary system 400 transfers the recipient's phone number received from the service providing system 300 to the mobile communication company systems 500, requests a name inquiry for the recipient's phone number, and receives a response accordingly ( S300). Here, the third trust intermediary system 400 may sequentially request name inquiry to all the mobile communication service provider systems 500 instead of requesting name inquiry simultaneously. In this case, if the name is searched, the request for the next name search is stopped. In one embodiment, the third trusted intermediary system 400 sequentially requests a name inquiry to the corresponding mobile communication company system 500 according to the preset mobile communication company priority.

The third trust intermediary institution system 400 compares the payee's name with the name searched for when requesting account transfer, and checks whether they match (S310) (S320). If they do not match, the third trust agency system 400 transfers the trust procedure processing result that the recipient's name and the recipient's phone number do not match to the service providing system 300. If they match, the third trust intermediary system 400 generates a text message including a recipient consent request message included in the additional information and an authentication code, and sends the generated text message to the recipient's terminal 200 to which the recipient's phone number is assigned. ) (S330) (S340). Here, the authentication code may be randomly generated in the third trusted intermediary authority system 400 and may consist of only a predetermined number of digits.

The recipient terminal 200 displays the text message received from the third trusted intermediary institution system 400 on the screen so that the recipient can check it. 400) to transmit text (S350) (S360). The third trust intermediary system 400 uses the authentication code included in the text message sent to the recipient's terminal 200 to confirm the recipient's agreement and the recipient's input in the text message sent from the recipient's terminal 200. It is checked whether the reply codes match (S370). When the confirmation is completed, the third trust agency system 400 transmits the trust procedure processing result to the service providing system 300 . That is, when the authentication code and the reply code match, the service providing system 300 is notified of the trust procedure processing result indicating that the name of the recipient and the phone number of the recipient match and that the consent of the recipient has been completed, and the authentication code and the reply code do not match. If the service providing system 300 is notified of the trust procedure processing result indicating that the recipient's name and the recipient's phone number match but the recipient's consent has not been made, .

On the other hand, FIG. 4 is a procedure performed when the transaction type identifier is '3' when the transaction type identifier is confirmed in the third trust intermediary institution system 400. Only the name comparison process for the recipient's phone number can be performed, and if the transaction type identifier is '2', only the authentication code and reply code comparison process can be performed to confirm the consent of the recipient.

FIG. 6 is a flow chart for setting mobile carrier priorities in the third trusted intermediary system 400 according to an embodiment. The third trusted intermediary system 400 checks the number of subscribers for each mobile communication company (S400). In one embodiment, the third trust intermediary system 400 checks the number of subscribers for each mobile communication service provider by querying the number of subscribers to each mobile communication service provider system 500 periodically, such as on a weekly or monthly basis, and receiving a response. do. When the number of subscribers for all mobile communication companies is confirmed in the third trust intermediary system 400, the third trust intermediary system 400 sorts the mobile communication companies in order of priority from the highest to the lowest number of subscribers, and the sorting The prioritized information is stored and stored in the database. That is, the third trusted intermediary system 400 sets and manages the priorities of mobile communication companies according to the number of subscribers (S410) (S420).

According to another embodiment, the third trust intermediary system 400 infers the number of subscribers for each mobile carrier according to the frequency of requests to each mobile carrier system 500 periodically, such as daily, weekly, or monthly. It is also possible to check.

7 is a flow chart of transfer transaction information inquiry according to an embodiment. The user terminal makes an ARS phone connection to the third trust intermediary system 400, and makes an ARS phone connection using a representative phone number for transfer transaction information inquiry (S500). Here, the user may be the sender or the recipient terminal 200 . The third trust intermediary institution system 400 requests input of an account number corresponding to the transfer transaction information to be inquired from the user terminal connected to the phone through voice guidance (S510). Accordingly, the user inputs his or her account number used in the transfer transaction to be inquired, and the user terminal transmits the input account number to the third trusted intermediary institution system 400 (S520).

The third trust intermediary institution system 400 sends a text message to the user terminal with a URL link for transfer transaction inquiry, and provides voice guidance for related contents (S530). When the voice guidance ends, the third trusted intermediary system 400 may automatically terminate the phone connection. When the user clicks the text message received URL link, the user terminal accesses the URL to the third trust agency system 400 (S540). Accordingly, the third trusted intermediary institution system 400 provides a mobile web page for searching transfer transaction information to the user terminal and displays it on the screen. Through the mobile web, the third trust agency system 400 requests the user to input an inquiry period (S550). For example, the 3rd Trust Brokerage System (400) says “Customer Hong*Dong, the contents of transaction evidence in 2019 are (5 cases in total). Please enter the year/month/day of the transaction for which you need to search and download evidence." The user terminal transfers the inquiry period input from the user to the third trust broker system 400, and the third trust broker system 400 retrieves all transfer transaction information (transfer confirmation) corresponding to the inquiry period from the database. and provide it to the user terminal. Transfer transaction information may be provided for simple inquiry or may be downloadable (S560) (S570).

As described above, the transfer confirmation certificate may include at least a part of the transfer service name, sender's name, recipient's name, recipient's phone number, recipient's consent request message, and trust procedure processing result. In addition, the transfer confirmation certificate may be stamped with the seal of a third trusted intermediary institution to ensure its reliability, and may include a QR code for verifying file forgery. In addition, the transfer confirmation may be sent to a fax designated by the user without being provided to the user terminal. When the user is a sender, the user may obtain transfer transaction information through the service providing system 300 .

Meanwhile, the service providing system 300 does not obtain the recipient's phone number from the sender, but when the recipient information provided by the sender is the account number of the recipient, it can be acquired through linkage with the corresponding financial institution.

That is, in the case where the sender wants to remit money is the recipient's account number, the service providing system 300 directly connects the financial institution of the recipient's deposit account or the financial institution system 600 linked with the service providing system 300. In this case, the recipient's phone number may be acquired in the preliminary transaction process. Accordingly, when the additional information provided from the sender includes only the recipient's phone number, only basic information may be provided from the sender and additional information may not be separately provided.

So far, the present invention has been looked at with respect to its preferred embodiments. Those skilled in the art to which the present invention pertains will be able to understand that the present invention may be implemented in a modified form without departing from the essential characteristics of the present invention. Therefore, the disclosed embodiments should be considered from an illustrative rather than a limiting point of view. The scope of the present invention is shown in the claims rather than the foregoing description, and all differences within the equivalent scope will be construed as being included in the present invention.

100: sender terminal 110: service app
200: receiver terminal 300: service providing system
400: 3rd trusted intermediary system 500: mobile communication company system
600: Financial institution system 700: Recipient authentication system

Claims (5)

The service providing system provides basic information including at least one of the transfer amount from the sender, the recipient's account information, and the recipient's phone number and deposit account number through a transfer service selected according to the sender's remittance purpose from among a plurality of transfer services belonging to the transfer menu. and receiving additional information for non-face-to-face safe transactions;
The service providing system searches for a payee name through payee information belonging to the basic information and checks whether a payee authentication request is further included in the additional information;
When the additional information further including the payee authentication request is received, the service providing system transmits the payee phone number and authentication additional information necessary for the payee authentication to the payee authentication system;
The payee authentication system generates a text message including a reply code for payee authentication, and sends the generated text message to the payee terminal to which the phone number has been assigned;
The text message received from the recipient authentication system is displayed on the screen, and the recipient checks it. Then, the recipient authenticates the reply code and sends it to the recipient authentication system. The recipient authentication system includes the received reply code and the text message sent to the recipient's terminal. Checking whether the received authentication codes match and returning the result to the service providing system; and
The service providing system provides the transfer service received from the sender when it is confirmed that there is no error in the recipient's phone number according to the recipient authentication procedure processing result returned from the recipient authentication system; transfer method. The service providing system provides basic information including at least one of the transfer amount from the sender, the recipient's account information, and the recipient's phone number and deposit account number through a transfer service selected according to the sender's remittance purpose from among a plurality of transfer services belonging to the transfer menu. and receiving additional information for non-face-to-face safe transactions;
The service providing system searches for a payee name through payee information belonging to the basic information and checks whether a payee authentication request is further included in the additional information;
When the additional information further including the payee authentication request is received, the service providing system transmits the payee phone number and authentication additional information necessary for the payee authentication to the payee authentication system;
The recipient authentication system generates a voice message including a reply code for authentication of the recipient, calls the generated voice message to the recipient's terminal to which the recipient's phone number is assigned, and provides the voice message through ARS connection;
After the payee confirms this, when the reply code is entered from the payee and sent to the payee authentication system, the payee authentication system checks whether the received reply code and the authentication code included in the voice message provided to the payee terminal match, and returns to the service providing system. replying; and
The service providing system provides the transfer service received from the sender when it is confirmed that there is no error in the recipient's phone number according to the recipient authentication procedure processing result returned from the recipient authentication system. transfer method. According to claim 1 or 2,
The service providing system transmits the inquired payee's name, additional information received from the sender, and a transaction type identifier assigned to the transfer service selected by the sender to a third trusted intermediary institution system;
verifying, by the third trusted intermediary institution system, the transaction type identifier received from the service providing system;
performing at least one trust procedure among a recipient name confirmation procedure and a recipient agreement procedure with additional information according to the identified transaction type identifier;
the third trust intermediary system returning a trust procedure processing result to the service providing system; and performing a transfer by the financial institution system using basic information received from the sender when transfer trust is guaranteed according to the trust procedure processing result returned from the third trust intermediary institution system.
In the step of trust procedure, if the confirmed transaction type identifier is the first transaction type identifier, the recipient name verification procedure is performed, and if the confirmed transaction type identifier is the second transaction type identifier, the recipient consent procedure is performed, and the confirmed transaction type is processed. Electronic funds transfer method for safe transaction that proceeds with the recipient's name confirmation procedure and recipient consent procedure when the identifier is the third transaction type identifier. According to claim 1 or 2,
In the transfer menu, there is a suspicious fraud transfer service with the 1st transaction type identifier assigned, a transfer service for real estate transaction with the 2nd transaction type identifier, a transfer service after multilateral agreement, a transfer service based on confirmation of request for acquaintances, and a transfer to prevent erroneous remittance. Transfer service that requires proof of transaction between service and individual, transfer service for proof of non-face-to-face direct transaction with a 3rd transaction type identifier, transfer service based on confirmation of the recipient's mobile phone name, and recipient authentication-based electronic for safe transaction including recipient authentication request menu How to transfer funds. 3. The method of claim 1 or 2, wherein the step of returning to the service providing system comprises:
When receiving the reply code from the beneficiary terminal, receiving a reply code input by the beneficiary and sent as a text message, or receiving a reply code transmitted through ARS connected to the beneficiary terminal; Recipient authentication-based electronic fund transfer for safe transaction, including method.

Images