WO2018092948A1

WO2018092948A1 - Remittance method and system therefor

Info

Publication number: WO2018092948A1
Application number: PCT/KR2016/013323
Authority: WO
Inventors: 최원준
Original assignee: 라인 가부시키가이샤
Priority date: 2016-11-18
Filing date: 2016-11-18
Publication date: 2018-05-24
Also published as: CN109863528A; JP2019536142A

Abstract

Provided are a remittance method and a system therefor. The remittance method of a server comprises the steps of: receiving, from an electronic device of a sender, a remittance request including a remittance amount; generating a transaction link for accessing a transaction session corresponding to the received remittance request; providing the generated transaction link; providing, to an electronic device of a receiver accessing through the provided transaction link, an interface for inputting a receiving account number corresponding to the transaction session; acquiring, through the receiving account number inputted through the interface, the name of the owner of the account according to the receiving account number and confirming the acquired name of the owner; and processing the remittance of the remittance amount from the sending account of the sender to the account of the owner whose name has been confirmed.

Description

Remittance method and system

The following description relates to a remittance method and remittance system, and to a technique for determining a remittee recipient in a remittance service.

Various prior arts exist for remittance services on networks. In this prior art remittance service, the sender for remittance must directly input the receiver's account number and / or name to the server for remittance service. For example, Korean Patent Laid-Open No. 10-2013-0047338 discloses a remittance method and a remittance service system capable of remittance using only the recipient's name and a mobile phone number.

However, in the case of entering the recipient's account number, the sender has to inquire the recipient's account number after receiving the recipient's account number, which is not familiar to the sender. There is a problem that is exposed to. In addition, even when the name of the receiver is entered, it is inconvenient to know exactly the spelling of the name. For example, since there are many names with different spellings in the same pronunciation depending on the country, it is very inconvenient to obtain and enter a name of a receiver that the sender does not know well.

Reference: <PCT / KR / 2014/010167, US20140019540A1, US20130332543A1, US20130260893>

Receiving a remittance request based on the remittance amount from the sender of the remittance, generate and provide a link to the service page where the account number can be entered.When the receiver accesses the service page and enters the account number through the generated link, The present invention provides a remittance method and system that enables a sender to process a remittance without having to input the recipient's account number and name (the above-mentioned owner name) by checking the owner name of the account number.

A money transfer method of a server, comprising: receiving a money transfer request including a money transfer amount from an electronic device of a sender; Generating a transaction link for accessing a transaction session corresponding to the received remittance request; Providing the generated trading link; Providing an interface for inputting a receiving account number corresponding to the transaction session to an electronic device of a receiver accessing through the provided transaction link; Acquiring an owner name of an account according to the receiving account number through a receiving account number input through the interface, and confirming the obtained owner name; And processing the remittance of the remittance amount to the account whose owner name is confirmed in the sender's transmission account.

A remittance system of a server, comprising: at least one processor implemented to execute instructions readable by a computer, the at least one processor receiving a remittance request including a remittance amount from an electronic device of a sender, Create a trading link for accessing a trading session corresponding to a remittance request, provide the generated trading link, and enter a receiving account number corresponding to the trading session to an electronic device of a recipient accessing through the provided trading link. An interface for acquiring the owner name of the account according to the receiving account number through the receiving account number input through the interface, confirming the obtained owner name, and checking the owner name in the sender's sending account. The remittance of the transfer amount to the confirmed account, characterized in that It provides a transfer system.

A computer program coupled to an electronic device of a sender implemented in a computer and stored in a computer readable recording medium for executing a remittance method on a computer, the remittance method comprising the steps of: generating a user interface for receiving a remittance amount; Transmitting a remittance request including a remittance amount input through the user interface to a remittance server; Receiving a transaction link generated based on the remittance request from the remittance server, wherein the transaction link has an access function to an interface for the remittance server to receive a receiving account number in association with a transaction session corresponding to the remittance request; Including-; Transmitting the received transaction link to an electronic device of a receiver; And receiving and confirming the owner's name of the account according to the received account number from the remittance server.

Receiving a remittance request based on the remittance amount from the sender of the remittance, generate and provide a link to the service page where the account number can be entered.When the receiver accesses the service page and enters the account number through the generated link, By confirming the owner name of the account number and confirming with the sender, the sender can process the remittance without having to enter the recipient's account number and name (the owner name described above).

1 is a diagram illustrating an example of a network environment according to an embodiment of the present invention.

2 is a block diagram illustrating an internal configuration of an electronic device and a server according to an embodiment of the present invention.

3 is a diagram illustrating an example of a remittance process according to an embodiment of the present invention.

4 is a view showing another example of the remittance process in an embodiment of the present invention.

5 is a view showing another example of the remittance process in an embodiment of the present invention.

6 is a diagram illustrating an example of a remittance process using a messenger identifier according to an embodiment of the present invention.

7 is a diagram illustrating an example of a remittance process using a registered account according to one embodiment of the present invention.

8 is a diagram for one example of a screen for inputting information for a remittance request according to one embodiment of the present invention.

9 is a diagram illustrating an example of a screen for inputting an account number according to an embodiment of the present invention.

10 is a diagram illustrating an example of a screen for selecting a recipient according to one embodiment of the present invention.

11 is a diagram illustrating an example of a screen for transmitting money to a receiver subscribed to a messaging service according to one embodiment of the present invention.

12 is a diagram illustrating a screen example in which a receiver subscribed to a messaging service inputs a receiving account number according to an embodiment of the present invention.

FIG. 13 is a diagram illustrating an example of a screen in which a sender checks a name of a receiver according to one embodiment of the present invention.

14 is a diagram illustrating an example of a screen for transmitting money to a recipient subscribed to a money transfer service according to one embodiment of the present invention.

15 is a block diagram illustrating an example of components that may be included in a processor of a server according to an embodiment of the present invention.

16 is a flowchart illustrating an example of a remittance method that may be performed by a server according to an embodiment of the present invention.

17 is a block diagram illustrating an example of components that may be included in a processor of an electronic device according to an embodiment of the present invention.

18 is a flowchart illustrating an example of a remittance method that may be performed by an electronic device according to an embodiment of the present disclosure.

Hereinafter, exemplary embodiments will be described in detail with reference to the accompanying drawings.

The remittance system according to the embodiments of the present invention may be implemented through an electronic device and / or a server, which will be described later, and the remittance method according to the embodiments of the present invention may be performed through the aforementioned electronic device and / or a server. Can be. For example, a computer program (for example, an operating system or an application) according to an embodiment of the present invention may be installed and run on a server, and the computer device may be installed according to the control of the driven computer program. According to the remittance method. The computer program described above may be stored in a computer-readable recording medium in combination with the computer-implemented server to execute the remittance method on a computer. In this case, the electronic device may be a user terminal device of a sender and a receiver for remittance receiving a remittance service by communicating with a server executing a remittance method through a network.

1 is a diagram illustrating an example of a network environment according to an embodiment of the present invention. The network environment of FIG. 1 illustrates an example including a plurality of

electronic devices

110, 120, 130, and 140, a plurality of

servers

150 and 160, and a network 170. 1 is an example for describing the present invention, and the number of electronic devices or the number of servers is not limited as shown in FIG. 1.

The plurality of

electronic devices

110, 120, 130, and 140 may be fixed terminals or mobile terminals implemented as computer devices. Examples of the plurality of

electronic devices

110, 120, 130, and 140 include a smart phone, a mobile phone, a navigation device, a computer, a notebook computer, a digital broadcasting terminal, a personal digital assistant (PDA), and a portable multimedia player (PMP). Tablet PC). For example, although FIG. 1 illustrates the shape of a smart phone as an example of the electronic device 1 110, in the embodiments of the present invention, the electronic device 1 110 may use a wireless or wired communication method to substantially connect the network 170. It may mean one of various physical devices that can communicate with other

electronic devices

120, 130, 140 and / or

servers

150, 160.

The communication method is not limited, and may include not only a communication method using a communication network (for example, a mobile communication network, a wired internet, a wireless internet, a broadcasting network) that the network 170 may include, but also a short range wireless communication between devices. For example, the network 170 may include a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), and a broadband network (BBN). And one or more of networks such as the Internet. The network 170 may also include any one or more of network topologies, including bus networks, star networks, ring networks, mesh networks, star-bus networks, trees, or hierarchical networks, but It is not limited.

Each of the

servers

150 and 160 communicates with the plurality of

electronic devices

110, 120, 130, and 140 through the network 170 to provide a command, code, file, content, service, or the like. It may be implemented in devices. For example, the server 150 may be a system that provides a first service to a plurality of

electronic devices

110, 120, 130, and 140 connected through the network 170, and the server 160 may also have a network ( It may be a system that provides a second service to the plurality of

electronic devices

110, 120, 130, and 140 connected through the 170. As a more specific example, the server 150 may be a system that provides a remittance service to a plurality of

electronic devices

110, 120, 130, and 140 as a first service. In addition, the server 160 may be a system that provides a messaging service or a payment service as a second service to the plurality of

electronic devices

110, 120, 130, and 140.

2 is a block diagram illustrating an internal configuration of an electronic device and a server according to an embodiment of the present invention. 2 illustrates an internal configuration of the electronic device 1 110 and the server 150 as an example of the electronic device. In addition, the other

electronic devices

120, 130, 140, or the server 160 may also have the same or similar internal configuration as the aforementioned electronic device 1 110 or the server 150.

The electronic device 1 110 and the server 150 may include

memories

211 and 221,

processors

212 and 222,

communication modules

213 and 223, and input /

output interfaces

214 and 224. The

memories

211 and 221 are computer-readable recording media, and may include non-volatile permanent storage devices such as random access memory (RAM), read only memory (ROM), and disk drives. In this case, the non-volatile mass storage device such as a ROM and a disk drive may be included in the electronic device 1 110 or the server 150 as a separate permanent storage device that is separated from the

memories

211 and 221. In addition, the

memory

211, 221 includes an operating system and at least one program code (for example, a browser installed and driven in the electronic device 1 110 or an application installed in the electronic device 1 110 to provide a specific service). Code) can be stored. These software components may be loaded from a computer readable recording medium separate from the

memories

211 and 221. Such a separate computer-readable recording medium may include a computer-readable recording medium such as a floppy drive, a disk, a tape, a DVD / CD-ROM drive, a memory card, and the like. In other embodiments, software components may be loaded into the

memory

211, 221 through the

communication module

213, 223 rather than a computer readable recording medium. For example, the at least one program is based on a memory (based on a program (for example, the above-described application) installed by files provided through a network by a file distribution system that distributes installation files of developers or applications). 211, 221.

Processors

212 and 222 may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input / output operations. Instructions may be provided to the

processors

212, 222 by the

memory

211, 221 or the

communication modules

213, 223. For example, the

processors

212 and 222 may be configured to execute a command received according to a program code stored in a recording device such as the

memory

211 and 221.

The

communication modules

213 and 223 may provide a function for the electronic device 1 110 and the server 150 to communicate with each other through the network 170, and the electronic device 1 110 and / or the server 150 may communicate with each other. May provide a function for communicating with another electronic device (eg, electronic device 2 120) or another server (eg, server 160). For example, a request generated by the processor 212 of the electronic device 1 110 according to a program code stored in a recording device such as the memory 211 may be controlled by the server 170 through the network 170 under the control of the communication module 213. 150). Conversely, control signals, commands, contents, files, and the like provided according to the control of the processor 222 of the server 150 are transmitted to the communication module of the electronic device 1 110 via the communication module 223 and the network 170 ( It may be received by the electronic device 1110 through 213. For example, the control signal, command, content, file, etc. of the server 150 received through the communication module 213 may be transmitted to the processor 212 or the memory 211, and the content, file, etc. may be transferred to the electronic device 1. 110 may be stored as a storage medium (permanent storage described above) that may further include.

The input / output interface 214 may be a means for interfacing with the input / output device 215. For example, the input device may include a device such as a keyboard or a mouse, and the output device may include a device such as a display or a speaker. As another example, the input / output interface 214 may be a means for interfacing with a device in which functions for input and output are integrated into one, such as a touch screen. The input / output device 215 may be configured as one device with the electronic device 1110. In addition, the input / output interface 224 of the server 150 may be a means for interfacing with an apparatus (not shown) for input or output that may be connected to or included in the server 150. As a more specific example, the processor 212 of the electronic device 1110 uses data provided by the server 150 or the electronic device 2 120 in processing a command of a computer program loaded in the memory 211. The service screen or the content may be displayed on the display through the input / output interface 214.

Also, in other embodiments, the electronic device 1 110 and the server 150 may include more components than those of FIG. 2. However, it is not necessary to clearly show most of the prior art components. For example, the electronic device 1 110 may be implemented to include at least some of the above-described input / output devices 215 or other components such as a transceiver, a global positioning system (GPS) module, a camera, various sensors, a database, and the like. It may further include elements. More specifically, when the electronic device 1 110 is a smartphone, an acceleration sensor, a gyro sensor, a camera module, various physical buttons, a button using a touch panel, an input / output port, and vibration for a smartphone generally include Various components such as a vibrator may be implemented to be further included in the electronic device 1 110.

3 is a diagram illustrating an example of a remittance process according to an embodiment of the present invention. The server 150 shown in FIG. 3 may correspond to the remittance server apparatus for the present embodiment, and the sender 310 and the receiver 320 may be user terminals that substantially participate in the remittance service. Various arrows shown in FIG. 3 may mean that signals including data are transmitted and received between the remittance server apparatus and the user terminals.

In the embodiment of FIG. 3, it is assumed that the sender 310 is a member of a remittance service or a messaging service associated with a remittance service, and the receiver 320 is not a member of a remittance service or a messaging service associated with a remittance service.

1. The remittance request process (hereinafter, 'process 1') may be a process in which the sender 310 transmits a remittance request based on the remittance amount and the transaction title to the server 150. For example, the sender 310 accesses a remittance page provided by the server 150, inputs a remittance amount and a transaction title through a user interface provided by the remittance page, and presses a remittance button included in the remittance page to request a remittance request. Can be generated. As another example, the sender 310 may receive a remittance service from the server 150 through an application installed in a user terminal of the sender 310, input a remittance amount and a transaction title through a user interface provided by the application, A remittance request can also be issued by pressing the remittance button. Such an application may be a separate application for a remittance service or a function for remittance service may be added to a messenger application for a messaging service.

The input remittance amount may mean an amount that the sender 310 intends to remit to the receiver 320, and the input transaction title may refer to a name of a transaction session for remittance. At this time, the transaction title may include some or all of the name of the receiver 320, but the transaction title only serves as the name of the transaction session, and the server 150 is not used to identify the receiver 320. . The remittance request may further include text such as a message for the sender 310 to deliver to the receiver 320, and in some embodiments, the contact number of the receiver 320, such as a telephone number or an e-mail address of the receiver 320. It may further include.

2. The transaction link generation process (hereinafter, 'process 2') may be a process in which the server 150 generates a transaction link to a service page for receiving an account number from the receiver 320 in response to a transfer request. If the remittance request includes text such as a message for the sender 310 to deliver to the receiver 320, a message including a transaction link and text may be generated.

The generated transaction link or message may be delivered directly to the receiver 320 in some embodiments, or may be delivered to the receiver 320 via the sender 310. For an embodiment that delivers the generated transaction link or message directly to the recipient 320, the transfer request may further include a contact of the recipient 320, such as a telephone number or email address of the recipient 320, as described above. . In Figure 3 represented by a dashed line '3. The transaction link transmission process' shows an example in which the server 150 delivers a transaction link generated directly to the receiver 320. In addition, '3-1 transaction link transmission process' and '3-2 transaction link transmission process' represented by dotted lines in FIG. 3 transmit the transaction link generated by the server 150 to the sender 310 and the sender 310. Shows an example of delivering the received transaction link to the receiver 320.

3. The transaction link transmission process (hereinafter, 'process 3') may be a process of directly transmitting the generated transaction link to the receiver 320 as described above. For example, the server 150 transmits the transaction link to the receiver 310 through the short message service (SMS) or the multi-media message service (MMS) using the phone number of the receiver 310 included in the transfer request. Can be. If the data included in the remittance request is an email address of the receiver 310, a transaction link may be delivered to the email address of the receiver 310.

3-1. The transaction link transmission process (hereinafter, 'process 3-1') may be a process in which the server 150 transmits the generated transaction link to the sender 310. For example, when the sender 310 transmits a remittance request to the server 150 using an application for accessing the money transfer service of the server 150, the sender 310 receives the request from the server 150 through the application. May receive a trading link.

As a more specific example, the code for generating a transaction link in the server 150 and transmitting it to the sender 310 may be implemented with Table 1 below.

TABLE 1

@return http_url = createLink (Int amout, String transaction_title, String message)

Here, 'createLink ()' is a function for creating a transaction link according to the remittance request. The 'createLink ()' may generate a Uniform Resource Locator (URL) of a service page to which the link indicates, and as a parameter, the remittance amount 'amout' And a transaction title 'transaction_title', and a text such as a message for the receiver 320 may be included in the remittance request. The URL of the generated service page may be returned to the sender 310 as a transaction link.

In addition, the sender 310 may cancel the transaction session for this time, if necessary, at the time of receiving the transaction link. In this case, the transfer cancellation request may be transmitted to the server 150. In addition, the server 150 may cancel the transaction session when there is no connection through the transaction link for a certain period (for example, 3 days) even if a separate remittance cancellation request is not received.

3-2. The transaction link transmission process (hereinafter, 'process 3-2') may be a process of transmitting the transaction link received by the sender 310 that receives the transaction link from the server 150 to the sender 320. In this case, the sender 310 may transmit the transaction link to the sender 320 by SMS or MMS using the receiver 320's telephone number or the e-mail address using the email address to the sender 320 via email. have. If the sender 310 and the receiver 320 have a friend relationship in a specific messaging service among various messaging services, the transaction link may be transmitted using the corresponding messaging service. As such, the transmission of the transaction link by the sender 310 to the receiver 320 may be performed by any method for transferring the transaction link between the sender 310 and the receiver 320 regardless of the server 150. If necessary, a transaction link may be delivered via telephone call or direct face-to-face communication between sender 310 and receiver 320.

4. The service page access process (hereinafter, 'process 4') may be a process in which the receiver 320 requests access to the service page by using the URL included in the transaction link through the transaction link.

5. Service page provision process (hereinafter, 'process 5'), the server 150 provides a service page for receiving the account number (receipt account number) to the receiver 320 requesting access through the transaction link It can be a process. For example, in the user terminal of the receiver 320, a web browser may be driven to display a service page on the screen of the user terminal.

6. The account number transmission process (hereinafter, 'process 6') may be a process in which the receiver 320 inputs the account number through the service page and transmits the account number to the server 150.

7. In the receiver name transmission process (hereinafter, 'process 7'), the server 150 checks the owner name of the account according to the account number through the received account number, and confirms the confirmed owner name to the sender 310. It may be a process of transmitting to the sender 310 to receive.

8. The confirmation transmission process (hereinafter, 'process 8') may be a process in which the sender 310 confirms the owner name of the account according to the account number and confirms to the server 150 that the owner name is correct. The sender 310 may designate or change the account number (transfer account number) of the sender 310 to which the remittance is to be withdrawn in the process of checking the owner name. For example, after the receiving account number of the receiver 320 is determined, there is a need for the sender 310 to change the remittance account number in order to lower the fee generated between banks. Accordingly, the sender 310 may be provided with an opportunity to change the remittance account number after the receiver account number of the receiver 320 is determined.

9. The remittance process (hereinafter, 'process 9') may be a process in which the remittance amount requested by the sender 310 is remitted to the account number input by the receiver 320, and remittance is performed after a delay of a predetermined time. Can be processed. This delay may be set to be omitted by the sender 310 before step 8.

According to the present embodiment, the sender 310 inputs a remittance amount, a transaction title, and a message as required to request remittance to the server 150, and transmits a transaction link provided from the server 150 to the receiver 320. After that, since the remittance can be processed by checking the name of the receiver 320, the sender 310 directly enters the name or the account number of the receiver 320, and the sender 310 directly sends the name or the account. The transfer can be processed without the possibility of errors that can occur if you enter a number. From the perspective of the receiver 310 it is possible to safely receive the transfer without the risk of exposing the account number of the receiver 310.

On the other hand, when the sender 310 transfers the telephone number or email address of the receiver 310 together when the remittance request is sent, the server 150 delivers the transaction link to the receiver 320 using the telephone number or the email address. As a result, remittance may be easily performed except for a process in which the sender 310 directly transmits the transaction link to the receiver 320.

In another embodiment, the sender 310 is a receiver '6. You may not know the name of the owner of the account number you enter during the 'account number transfer process'. Alternatively, the server 150 may not check whether the sender 310 knows the owner name of the input account number. In this case, a process of confirming the owner name of the account number by the sender 310 may be omitted.

4 is a view showing another example of the remittance process in an embodiment of the present invention. '1 of FIG. Remittance request process ”to '6. Up to an account number transmission process, may correspond to process 1 to process 6 of FIG. The remittance process "may also correspond to process 9 of FIG. 3. However, as described above, whether the sender 310 does not know the owner name of the account number input from the receiver 320 or whether the sender 310 knows the owner name of the account number input from the receiver 320. There is also a case where the server 150 does not check. In this case, the server 150 may receive confirmation from the receiver 320 whether the owner is the recipient of the remittance of the remittance through the owner name of the input account number.

7. In the receiver name transmission process (hereinafter, process 7 of FIG. 4), the server 150 confirms the owner name of the corresponding account through the received account number, and sends the confirmed owner name to the receiver 320. It may be a process of transmitting to the receiver 320 for confirmation.

8. The confirmation transmission process (hereinafter, 'process 8' of FIG. 4) may be a process in which the receiver 320 confirms the owner name of the account according to the account number and confirms that the owner name is correct by the server 150. .

In another embodiment, the server 150 may require the server 150 to input the name of the receiver 320 together with the account number from the receiver 320 in steps 5 and 6 described above. In this case, the server 150 checks the owner name of the account corresponding to the account number in the bank through the received account number, and compares the confirmed owner name with the name of the receiver 320 received with the account number. Server 150 may also verify recipient 320.

In the above embodiments, it is assumed that the sender 310 is a member of the remittance service or the messaging service associated with the remittance service, and the receiver 320 is not a member of the remittance service or the messaging service associated with the remittance service. 5 and 6, it is assumed that the sender 310 is a member of a remittance service or a messaging service associated with a remittance service, and the receiver 320 is a member of a messaging service associated with a remittance service.

5 is a view showing another example of the remittance process in an embodiment of the present invention. 5 '1. Send money request process ”to“ 4. Service Page Access Process ”, and '6. The account number transmission process 'to 9. remittance process' may correspond to process 1 to process 4 of FIG. 3 and process 6 to process 9 of FIG. 3.

5. The messenger call process (hereinafter, process 5 of FIG. 5) is a messenger installed in the user terminal of the receiver 320 when the receiver 320 approaches the server 150 through a transaction link. It may be a process of calling the messenger to receive the account number by driving the. The called messenger may provide the receiver 320 with a user interface for receiving an account number according to a transaction session for the transfer, and the receiver 320 may input an account number for receiving the transfer through the provided user interface. The account number may be transmitted to the server 150 through a messenger.

6 is a diagram illustrating an example of a remittance process using a messenger identifier according to an embodiment of the present invention. 6 illustrates a remittance process when both the sender 310 and the receiver 320 are members of a messaging service associated with a remittance service. In addition, it is assumed that the receiver 320 is not yet a member of the remittance service.

1. The account verification request process may be a process in which the sender 310 requests confirmation from the server 150 whether an account (bank account) of the receiver 320 is registered in the server 150. In this case, the receiver 320 may be a member of a messaging service selected by the sender 310 based on a social relationship in the messaging service, and thus may be identified through a messenger identifier for the messaging service. For example, when the sender 310 selects the receiver 310 among messenger friends provided by the messaging service, the sender 310 confirms whether or not a registered account exists for the selected receiver 310. May be requested. In this case, the account verification request transmitted to the server 150 may include a messenger identifier of the receiver 320.

2. The account verification process may be a process in which the server 150 confirms to the sender 310 whether there is an account registered for the receiver 320 based on the messenger identifier of the receiver 320 requested to be confirmed. Since the embodiment of FIG. 6 assumes that the receiver 320 is not a member of the remittance service, the server 150 may inform the sender 310 that the registered receiver 320 does not exist. At this time, the sender 310 may cancel the process for the transfer.

3. In the remittance request process, the sender 310 transmits a remittance request including the messenger identifier of the receiver 320 to the server 150, and thus the server 150 transmits the remittance request to the receiver 320 identified through the messenger identifier. It may be a process of requesting input of an account number. The remittance request may include a remittance amount, a transaction title, and text input by the sender 310, and may further include a messenger identifier of the receiver 320 automatically added by an application associated with the remittance service. In addition, the server 150 may provide the receiver 320 with a command for controlling the messenger installed in the user terminal of the receiver 320 according to the transfer request. For example, the command may control the messenger of the receiver 320 to provide a user interface for input of an account number. In this process, the server 150 may further request the receiver 320 to join the money transfer service as necessary.

4. The account number transmission process may be a process in which the receiver 320 inputs an account number for the transfer. Depending on the needs of the receiver 320, the receiver 320 may subscribe to a member of the money transfer service.

6 '5. Recipient Name Transfer Process ”, '6. Confirmation Transfer Process ”and '7. The remittance process ”may correspond to process 7 to process 9 of FIG. 3.

In other words, in this embodiment, the sender 310 selects the receiver 320 through the messaging service to request a transfer without the server 150 having to create or transmit a separate transaction link, and the receiver 320 inputs the transfer. Just by checking the owner name of the account according to the account number, the remittance can be easily processed without having to enter the account number or the name of the recipient 320 (owner name of the account according to the account number).

Meanwhile, when the receiver 320 registers as a member of the remittance service and registers an account, the remittance may be more easily processed.

7 is a diagram illustrating an example of a remittance process using a registered account according to one embodiment of the present invention. In this case, it is assumed that both the sender 310 and the receiver 320 are members of both the remittance service and the messaging service associated with the remittance service.

2. The account and name verification process is performed by the server 150 whether the account of the receiver 320 is registered through the identifier of the receiver 320 included in the transfer request and the name of the receiver 320 (the name of the registered account). Owner name) may be a process of confirming to the sender 310.

3. The remittance request process may be a process in which the sender 310 checks the name of the receiver 320 (owner name of the registered account), requests a remittance to the server 150 by inputting a remittance amount and a message, and the like. . In this case, the input of the transaction title may be omitted because the account, the owner name, and the account number of the receiver 320 are already confirmed. In addition, the sender 310 is' 3. In the remittance request process, a withdrawal account number for withdrawal can be designated or changed, and a delay can be determined.

4. The remittance process may be a process in which the remittance amount requested by the sender 310 is remitted to the registered account of the receiver 320.

In the present embodiment, the sender 310 simply selects the receiver 320 through a remittance service or a messaging service, inputs a remittance amount and a transaction title, requests a remittance, and then the name of the receiver 320 (the owner of the registered account). You can easily process the remittance simply by confirming your order). Still, the account number of the receiver 320 is not leaked, and the sender 310 does not need to directly enter the account number or name (owner name of the account) of the receiver 320.

8 is a diagram for one example of a screen for inputting information for a remittance request according to one embodiment of the present invention. 8 illustrates an example screen 800 of the electronic device 1110 as an example of a user terminal of the sender 310. The screen example 800 of FIG. 8 may be a screen provided by an application installed in the electronic device 1 110, and as described with reference to the embodiment of FIG. 3, the sender 310 needs to select the receiver 320. It may be a screen when there is no.

The 'transaction title' shown in the first dotted line box 810 may represent a user interface for inputting the transaction title described with reference to FIG. 3, and the text content input by the sender 310 through the user interface 'transaction title' is displayed. It can be used to identify a trading session for that transfer. 8 illustrates an example in which the sender 310 inputs the name of the receiver 320 named 'stone', but the input text 'stone' is used only for identification of the transaction session and to identify the receiver 320. It is not used to

'Transfer amount' shown in the second dotted line box 820 may represent a user interface for inputting an amount for the sender 310 to transfer the money to the receiver 320.

The remittance account shown in the third dotted line box 830 may represent a user interface for displaying the account previously registered by the sender 310 in the remittance service. For example, in FIG. 8, "bank A" may mean that the sender 310 uses an account of bank A, which is registered in advance in the remittance service, as a remittance account. In other words, “bank A” shown in the third dotted line box 830 is not text input by the remitter 310, but defaults to information obtained by the application installed in the electronic device 1110 through communication with the server 150. It may be information indicated by. If necessary, the sender 310 may change the remittance account. For example, when the sender 310 selects an area corresponding to "Bank A" displayed as a remittance account (for example, touches a portion for inputting a remittance account in a touch screen environment), the sender 310 sends the remittance account to the sender 310. A user interface may be provided for specifying or changing the.

The message shown in the fourth dotted line box 840 may indicate a user interface for the sender 310 to input information to be transmitted to the receiver 320 in relation to the transfer.

'Send' shown in the fifth dotted line box 850 may represent a user interface for transmitting a transfer request to the server 150. If the user selects the area marked 'Send', 'River' entered in the user interface 'Transaction title', '15, 000 'entered in the user interface' Transfer amount 'and' Lunch value 'entered in the user interface' Message ' Corresponding to each of these items (transaction title, remittance amount, message) may be transmitted from the electronic device 1 (110) to the server 150 in the state included in the remittance request.

In this case, the server 150 may generate a trading link by inputting 15,000 ',' stone ', and' lunch value 'as parameters of the function' createLink () 'as described in Table 1, and the generated trading link May be returned to the electronic device 1110. The sender 310 can deliver the received transaction link to the receiver 320 in a variety of ways.

According to an embodiment, the screen example 800 of FIG. 8 may further include a user interface for receiving a contact number of the receiver 320 such as a phone number or an email address of the receiver 320. In this case, the contact information of the receiver 320 inputted may be transmitted from the electronic device 1 110 to the server 150 together with the request for remittance, and the server 150 may generate a transaction using the contact information of the sender 320. The link may also be forwarded directly to the sender 320.

9 is a diagram illustrating an example of a screen for inputting an account number according to an embodiment of the present invention. 9 illustrates a screen example 900 of the electronic device 2 120 as an example of a user terminal of the receiver 320. The screen example 900 of FIG. 9 may be a screen displaying a service page accessed by the electronic device 2 120 through a transaction link.

The first dotted line box 910 indicates a message indicating that the sender 320 has requested a remittance together with the name 'Won Joon Choi' of the sender 320.

The second dotted line box 920 represents the transfer amount '15, 000 'inputted by the sender 310 in FIG. 8, and the third dotted line box 930 represents the message' lunch value 'in which the sender 310 is inputted in FIG. 8. have.

The 'receipt account' shown in the fourth dotted line box 940 may represent a user interface for receiving an account number for receiving the remittance amount from the receiver 320. When the receiver 320 selects an input area of the user interface 'receipt account', a user interface for inputting numbers and letters may be provided to the receiver 320.

The 'send' shown in the fifth dotted line box 950 may represent a user interface for transmitting the account number input through the user interface 'receipt account' to the server 150. In other words, when the receiver 320 selects a user interface 'send', the input account number may be transmitted to the server 150. In this case, the server 150 may check the owner name of the corresponding account through the input account number, and transmit the confirmed owner name to the sender 310 to check the name of the receiver 320.

10 is a diagram illustrating an example of a screen for selecting a recipient according to one embodiment of the present invention. 10 illustrates an example screen 1000 of the electronic device 1 110 in which the sender 310 selects the receiver 320.

The first dotted line box 1010 may represent a user interface for directly receiving a receiving account number for remittance from the sender 310. When the sender 310 selects an area of the first dotted line box 1010, a field and a keyboard for inputting a receiving account number may be provided to the sender 310. Since the sender 310 directly inputs the account number of the receiver 320, a detailed description thereof will be omitted.

The second dotted line box 1020 shows an example of displaying information on users (messenger friends) who have established a social relationship with the sender 310 in the messaging service associated with the remittance service. At this time, the sender 310 may directly select a user to transfer the transfer. In Fig. 10, an example in which the user " stone " is selected as the sender 310 is shown.

In the embodiments of FIG. 6 and FIG. 7, an embodiment of processing the transfer using the messenger identifier of the selected messenger friend has been described. In addition, even in the embodiment of FIG. 5, a message transfer process may be performed by selecting a specific messenger friend without using a messenger identifier.

11 is a diagram illustrating an example of a screen for transmitting money to a receiver subscribed to a messaging service according to one embodiment of the present invention. 11 illustrates a screen example 1100 of the electronic device 1 110 in which the sender 310 inputs a remittance amount, a transaction title, and a message for a remittance request. In this case, the first dotted line box 1110 shows information on the receiver 320 selected by the sender 310 among the messenger friends as shown in FIG. 10. When the sender 310 presses send, the embodiment described with reference to FIG. 5 or the embodiment described with reference to FIG. 6 may proceed.

12 is a diagram illustrating a screen example in which a receiver subscribed to a messaging service inputs a receiving account number according to an embodiment of the present invention. 12 illustrates an example screen 1200 of the electronic device 2 120 as an example of a user terminal of the receiver 320, and illustrates an example of a messenger screen called through a transaction link in the electronic device 2 120. The screen example 1200 of FIG. 12 is similar to the screen example 900 of FIG. 9 in that it displays a remittance amount, a message, and provides a user interface for receiving a receiving account number.

However, the screen example 1200 of FIG. 12 is not a screen connected to a service page, but a messenger screen, provides information about a messenger friend like the first dotted box 1210, and a second dotted box 1220. 9 is different from the screen example 900 of FIG. 9 in that a user interface for inducing a subscription to a remittance service is provided.

The first dotted line box 1210 shows not only the name of the sender 310 but also the profile image 1211 and the nickname "Horror eye" used in the messenger.

The second dotted line box 1220 illustrates a user interface for requesting to register an input account at the same time as subscribing to the remittance service. When the receiver 320 responds to the request (when the checkbox 1221 is checked in FIG. 12), the receiver 320 transmits the account number to the server 150 and then subscribes the receiver 320 to the money transfer service. The procedure may proceed.

FIG. 13 is a diagram illustrating an example of a screen in which a sender checks a name of a receiver according to one embodiment of the present invention. FIG. 13 shows an example screen 1300 of electronic device 1 110 for the sender 310 to verify the name (owner name of the account) of the receiver 320. For example, the screen example 1300 is described with reference to '7. Recipient Name Resolution Process ”and '8. It may be a screen provided between the confirmation transmission process.

The first dotted line box 1310 represents the owner name 'Hong Seok-ju' of the account corresponding to the account number inputted by the receiver 320 and transmitted through the server 150 and some of the corresponding account number. When the user confirms the owner name 'Hong Seok-ju' of the receiving account and presses the confirmation button of FIG. 13, a signal for notifying that the owner name is confirmed from the electronic device 1 110 to the server 150 may be transmitted.

The second dotted line box 1320 represents a fee for receiving a receiver account of the receiver 320 and a user interface for changing a remittance account according to the fee.

14 is a diagram illustrating an example of a screen for transmitting money to a recipient subscribed to a money transfer service according to one embodiment of the present invention. FIG. 14 illustrates a screen example 1400 of the electronic device 1 110 in which the sender 310 inputs a remittance amount, a message, and the like for a remittance request. As shown in FIG. 10, when the sender 310 selects the receiver 320 from the messenger friend, the electronic device 1 110 may request the server 150 to confirm a registered account for the selected receiver 320. . For example, '1. Account verification request process may proceed. In addition, the '2. As the 'account and name verification process' proceeds, the owner name of the receiving account transmitted from the server 150 may be verified in the electronic device 1110.

The first dotted line box 1410 may indicate the messenger information of the receiver 320 selected from the messenger friends.

The second dotted line box 1420 shows an example of checking the owner name 'Hong Seok-ju' of the receiving account transmitted from the server 150. In some embodiments, some of the bank name and / or account number may be further displayed. When the sender 310 inputs a remittance amount and a message and selects a send button, the sender 310 may determine '3. Remittance request process.

Meanwhile, in FIG. 14, 'LN Pay' may be a name of a remittance service. In this embodiment, both the sender 310 and the receiver 320 may be members of a remittance service, and a basic service (for example, a receiver 310 in a registered account of the sender 310) for remittance between members in the remittance service. Remittance to a registered account). In this case, the receiver 320 may receive a message indicating that the transfer has been received without a process of inputting an account number, and in some embodiments, sets the account of the registered receiver 320 as a default receiving account. This may proceed further.

FIG. 15 is a block diagram illustrating an example of a component that may be included in a processor of a server according to an embodiment of the present invention, and FIG. 16 is a diagram of a remittance method that may be performed by a server according to an embodiment of the present invention. It is a flowchart which shows an example.

The server 150 may implement a remittance server according to embodiments of the present invention. As shown in FIG. 15, the processor 222 of the server 150 is a component for implementing a remittance server. 1510, a transaction link generation unit 1520, a transaction link providing unit 1530, an interface providing unit 1540, an owner name checking unit 1550, and a remittance processing unit 1560. The processor 222 and the components of the processor 222 may control the server 150 to perform steps 1610 to 1660 included in the transfer method of FIG. 16. In this case, the processor 222 and the components of the processor 222 may be implemented to execute an instruction according to a code of an operating system included in the memory 221 or a code of at least one program. Here, the components of the processor 222 may be representations of different functions of the processor 222 performed by the processor 222 according to a control command provided by a code stored in the server 150. . For example, the transfer request receiver 710 may be used as a functional representation of the processor 222 that controls the server 150 so that the processor 222 receives the transfer request according to the above-described control command.

In operation 1610, the remittance request receiver 1510 may receive a remittance request including a remittance amount from the sender's electronic device. The transfer request may further include at least one of a transaction title for identification of the transaction session and a message for the sender to send to the recipient in connection with the transaction session, the information for identifying the receiving account number and the receiving account, according to an embodiment. It may not include information to identify the owner name of the account by number. As described above, the transaction title may include at least some of the recipient's name, but the transaction title is used as the name of the transaction session to allow the sender or receiver to identify the transaction session, but not the account holder or owner of the account. It is not used as information for identifying names.

In operation 1620, the transaction link generation unit 1520 may generate a transaction link for accessing a transaction session corresponding to the received remittance request. The transaction link may be generated based on the amount of money included in the transfer request. According to an embodiment, a transaction link may be generated using at least one of a transaction title and a message which may further include a transfer request.

In operation 1630, the transaction link provider 1530 may provide the generated transaction link. As already described, the transaction link may be provided directly to the recipient or via the sender to the recipient. For example, the transfer request may further include the recipient's phone number or email address. In this case, the transaction link providing unit 1530 may provide a transaction link generated through a short message service (SMS) or a multi-media message service (MMS) using a phone number to the recipient's electronic device, or use an email address. Through the generated transaction link can be provided to the receiver's electronic device. As another example, the transaction link provider 1530 may transmit the generated transaction link to the sender's electronic device so that the generated transaction link may be delivered to the receiver through the sender. Here, the sender's electronic device may correspond to the electronic device 1 110 described above, and the receiver's electronic device may correspond to the electronic device 2 120 described above.

In operation 1640, the interface provider 1540 may provide an interface for inputting a receiving account number corresponding to a transaction session to an electronic device of a receiver accessing through the provided transaction link. For example, the interface provider 1540 provides a service page including an interface for inputting a receiving account number to an electronic device of a receiver accessing through a provided transaction link, and provides the receiving account number through an interface of the service page. Can be input. As another example, when the receiver is a member of a messenger service associated with a remittance service, the interface provider 1540 may send a command for calling a messenger installed in the receiver's electronic device to the receiver's electronic device accessed through the provided transaction link. The mobile terminal may transmit and provide an interface for inputting a receiving account number through a messenger driven by the receiver's electronic device.

In operation 1650, the owner name checking unit 1550 may acquire the owner name of the account according to the receiving account number through the receiving account number input through the interface, and confirm the obtained owner name. For example, the owner name checking unit 1550 may transmit the obtained owner name to the electronic device of the sender or the receiver, and confirm the owner name according to the owner name confirmation signal received from the electronic device of the sender or the receiver. As another example, the owner name checking unit 1550 may receive the name of the recipient along with the receiving account number through the interface, and may check the owner name by comparing the owner name obtained through the receiving account number with the received recipient name.

In operation 1660, the remittance processing unit 1560 may process remittance of the remittance amount to the account whose owner name is confirmed in the sender's transmission account. Therefore, the sender can send money without entering the name of the recipient (for the recipient who is not a member of the money transfer service) and / or the receiving account number, and the recipient can send money without exposing the receiving account number. I can receive it.

17 is a block diagram illustrating an example of a component that may be included in a processor of an electronic device according to an embodiment of the present invention, and FIG. 18 is a remittance that may be performed by an electronic device according to an embodiment of the present invention. A flowchart illustrating an example of the method.

The electronic device 1 110 may implement the sender's electronic device according to embodiments of the present invention. As shown in FIG. 17, the processor 212 of the electronic device 1 110 may implement the sender's electronic device. The components may include a user interface generator 1710, a remittance request transmitter 1720, a transaction link receiver 1730, a transaction link transmitter 1740, and an owner name checker 1750. The processor 212 and the components of the processor 212 may control the electronic device 1110 to perform steps 1810 to 1850 included in the transfer method of FIG. 18. In this case, the processor 212 and the components of the processor 212 may be implemented to execute instructions according to code of an operating system included in the memory 211 or code of at least one program. Here, the components of the processor 212 may be representations of different functions of the processor 212 performed by the processor 212 according to a control command provided by a code stored in the electronic device 1110. Can be.

In operation 1810, the user interface generator 1710 may generate a user interface for receiving a remittance amount. The generated user interface may be provided to the sender. For example, a screen including a user interface as shown in FIG. 8 or 11 may be provided to the sender. In such embodiments, the user interface generator 1710 may receive at least one of a transaction title for identifying a transaction session and a message for a sender to transmit to a receiver in association with the transaction session.

In operation 1820, the remittance request transmitter 1720 may transmit a remittance request including the remittance amount input through the user interface to the remittance server. The remittance server may be implemented via the server 150 described above, and the remittance request may further include at least one of a transaction title for identification of the transaction session and a message for the sender to send to the recipient in association with the transaction session, according to an embodiment. It may include, and may not include information for identifying the receiving account number and information for identifying the owner name of the account according to the receiving account number.

In operation 1830, the transaction link receiving unit 1730 may receive a transaction link generated based on the transfer request from the transfer server. In this case, the transaction link may include an access function to an interface for the remittance server to receive a receiving account number in association with a transaction session corresponding to the remittance request. The preferred transaction link may be generated based on the transfer amount included in the transfer request. According to an embodiment, a transaction link may be generated using at least one of a transaction title and a message which may further include a transfer request.

In operation 1840, the transaction link transmitter 1740 may transmit the received transaction link to the electronic device of the receiver. At this time, in one embodiment the remittance server provides a service page including an interface for inputting the receiving account number to the electronic device of the recipient to access through the transaction link, and the receiving account number through the interface of the service page It may be implemented to obtain the owner name of the account according to the received account number. In another embodiment, the remittance server transmits a command for calling a messenger installed in the receiver's electronic device to the receiver's electronic device accessed through the transaction link, and inputs the receiving account number through the messenger driven in the receiver's electronic device. It provides an interface for receiving the receiving account number through the interface can be implemented to obtain the owner name of the account according to the receiving account number.

In operation 1850, the owner name checking unit 1750 may receive and confirm the owner name of the account according to the receiving account number from the remittance server. Information for informing that the owner name has been confirmed may be transmitted to the remittance server, and the remittance server may transfer the remittance amount according to the remittance request from the sender's account (pre-registered account) to the recipient's account (account according to the received receiving account number). To send money.

As described above, according to the embodiments of the present invention, when receiving a remittance request based on the remittance amount from the sender of the remittance, generates and provides a link to the service page that can enter the account number, and through the generated link to the receiver Accesses the service page, enters the account number, confirms the owner name of the entered account number, and confirms with the sender, thereby processing the remittance without the sender having to enter the recipient's account number and name (the above-mentioned owner name). can do.

The system or apparatus described above may be implemented as a hardware component, a software component or a combination of hardware components and software components. For example, the devices and components described in the embodiments are, for example, processors, controllers, arithmetic logic units (ALUs), digital signal processors, microcomputers, field programmable gate arrays (FPGAs). Can be implemented using one or more general purpose or special purpose computers, such as a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to the execution of the software. For convenience of explanation, one processing device may be described as being used, but one of ordinary skill in the art will appreciate that the processing device includes a plurality of processing elements and / or a plurality of types of processing elements. It can be seen that it may include. For example, the processing device may include a plurality of processors or one processor and one controller. In addition, other processing configurations are possible, such as parallel processors.

The software may include a computer program, code, instructions, or a combination of one or more of the above, and configure the processing device to operate as desired, or process it independently or collectively. You can command the device. Software and / or data may be any type of machine, component, physical device, virtual equipment, computer storage medium or device in order to be interpreted by or to provide instructions or data to the processing device. It may be embodied permanently or temporarily. The software may be distributed over networked computer systems so that they may be stored or executed in a distributed manner. Software and data may be stored on one or more computer readable recording media.

The method according to the embodiment may be embodied in the form of program instructions that can be executed by various computer means and recorded in a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the media may be those specially designed and constructed for the purposes of the embodiments, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks, such as floppy disks. Magneto-optical media, and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like.

Although the embodiments have been described by the limited embodiments and the drawings as described above, various modifications and variations are possible to those skilled in the art from the above description. For example, the described techniques may be performed in a different order than the described method, and / or components of the described systems, structures, devices, circuits, etc. may be combined or combined in a different form than the described method, or other components. Or even if replaced or substituted by equivalents, an appropriate result can be achieved.

Therefore, other implementations, other embodiments, and equivalents to the claims are within the scope of the claims that follow.

Claims

In the transfer method of the server,

Receiving a transfer request including a transfer amount from an electronic device of a sender;

Generating a transaction link for accessing a transaction session corresponding to the received remittance request;

Providing the generated trading link;

Providing an interface for inputting a receiving account number corresponding to the transaction session to an electronic device of a receiver accessing through the provided transaction link;

Acquiring an owner name of an account according to the receiving account number through a receiving account number input through the interface, and confirming the obtained owner name; And

Processing the remittance of the remittance to the account of the owner name in the sender's sending account;

Remittance method comprising a.
The method of claim 1,

The transfer request does not include information for identifying the receiving account number and information for identifying the owner name of the account according to the receiving account number.
The method of claim 1,

The transfer request further comprises at least one of a transaction title for identification of the transaction session and a message for the sender to convey to the recipient in association with the transaction session,

The transaction link is generated using at least one of the transaction title and the message and the remittance amount.
The method of claim 1,

The transfer request further includes the recipient's telephone number or email address,

Providing the generated trading link,

Providing the generated transaction link to the electronic device of the recipient through a short message service (SMS) or a multi-media message service (MMS) using the phone number or the generated transaction link through an e-mail using the e-mail address. Remittance method characterized by providing to the electronic device of the receiver.
The method of claim 1,

Providing the generated trading link,

Transmitting the generated transaction link to the sender's electronic device so that the generated transaction link can be delivered to the receiver via the sender.
The method of claim 1,

Providing an interface for the input of the receiving account number,

Remittance service characterized in that it provides a service page including an interface for inputting the receiving account number to the electronic device of the recipient to access through the provided transaction link, and receives the receiving account number through the interface of the service page Way.
The method of claim 1,

Providing an interface for the input of the receiving account number,

Sending a command for calling a messenger installed in the electronic device of the receiver through the provided transaction link, and for inputting the receiving account number through the messenger driven in the electronic device of the receiver. Remittance method characterized by providing an interface.
The method of claim 1,

Confirming the obtained owner name,

Transmitting the obtained owner name to the electronic device of the sender or receiver, and confirming the owner name according to the owner name confirmation signal received from the electronic device of the sender or receiver.
The method of claim 1,

Confirming the obtained owner name,

Receiving the name of the recipient with the receiving account number via the interface, the transfer method characterized in that the owner name obtained by comparing the owner name obtained through the receiving account number and the received recipient name to confirm the owner name .
In the transfer system of the server,

At least one processor implemented to execute computer-readable instructions

Including,

The at least one processor,

Receive a transfer request including a transfer amount from the sender's electronic device,

Create a trading link for accessing a trading session corresponding to the received remittance request,

Provide the generated trading link,

Providing an interface for inputting a receiving account number corresponding to the transaction session to an electronic device of a receiver accessing through the provided transaction link,

Acquiring the owner name of the account according to the receiving account number through the receiving account number input through the interface, confirming the obtained owner name,

Processing the remittance of the remittance to the account in which the owner's name is identified in the sender's sending account;

Remittance system characterized in that.
The method of claim 10,

The remittance request does not include information for identifying the receiving account number and information for identifying the owner name of the account according to the receiving account number.
The method of claim 10,

The transfer request further comprises at least one of a transaction title for identification of the transaction session and a message for the sender to convey to the recipient in association with the transaction session,

The transfer link is generated using at least one of the transaction title and the message and the remittance amount.
The method of claim 10,

The transfer request further includes the recipient's telephone number or email address,

The at least one processor is configured to provide the generated transaction link,

Providing the generated transaction link to the electronic device of the recipient through a short message service (SMS) or a multi-media message service (MMS) using the phone number or the generated transaction link through an e-mail using the e-mail address. Remittance system, characterized in that for providing to the recipient's electronic device.
The method of claim 10,

The at least one processor is configured to provide the generated transaction link,

Transmitting the generated transaction link to the sender's electronic device so that the generated transaction link can be delivered to the receiver via the sender.
A computer program coupled to an electronic device of a sender implemented by a computer, the computer program stored in a computer-readable recording medium for executing a remittance method to a computer

The remittance method,

Generating a user interface for receiving a remittance amount;

Transmitting a remittance request including a remittance amount input through the user interface to a remittance server;

Receiving a transaction link generated based on the remittance request from the remittance server, wherein the transaction link has an access function to an interface for the remittance server to receive a receiving account number in association with a transaction session corresponding to the remittance request; Including-;

Transmitting the received transaction link to an electronic device of a receiver; And

Receiving and confirming the owner name of the account according to the receiving account number from the transfer server

Computer program comprising a.
The method of claim 15,

The remittance request does not include information for identifying the receiving account number and information for identifying the owner name of the account according to the receiving account number.
The method of claim 15,

The user interface for receiving the remittance amount further receives at least one of a transaction title for identification of the transaction session and a message for the sender to deliver to the recipient in association with the transaction session,

And the transaction link is generated at the remittance server using at least one of the transaction title and the message and the remittance amount.
The method of claim 15,

The remittance server,

Providing a service page including an interface for inputting the receiving account number to an electronic device of a receiver accessing through the transaction link, receiving the receiving account number through an interface of the service page, Implemented to obtain the account holder's name

A computer program featuring.
The method of claim 15,

The remittance server,

Send an instruction for calling a messenger installed in the receiver's electronic device to the receiver's electronic device accessing through the transaction link, and input an interface for inputting the receiving account number through the messenger driven in the receiver's electronic device. And receiving the receiving account number through the interface to obtain an owner name of an account according to the receiving account number.

Computer program characterized in that.