WO2016153170A1 - Transaction processing for direct remittance using user account - Google Patents

Abstract

Disclosed is a transaction processing technology for direct remittance using a user account. A remittance method may comprise the steps of: receiving, from a user terminal, remittance information including the amount of remittance, and a service account and a recipient name associated with a remittance service, as information on the recipient who will receive the remittance; and checking the name of the recipient, which is used in the remittance service, by using the service account and the recipient name, and then transmitting the remittance information to the recipient's terminal using the service account.

Description

Transaction processing for direct money transfer using user account

Embodiments of the present invention relate to a remittance model for processing online remittances over the Internet.

In general, in order to transfer a certain amount of money to others, money is transferred from one's own bank account to the other's bank account, which can be transferred in various forms such as telebanking, Internet banking, and the user using a bank clerk or an ATM at a bank. It is done.

As the development of information and communication technology has been applied to the financial field, financial transactions, which have been processed by face-to-face authentication by visiting bank counters, have recently been developed as non-face-to-face financial transactions that provide financial transactions through face-to-face authentication using a communication network.

For example, Korean Patent Application Publication No. 10-2000-0072625 (published December 05, 2000) discloses a technology for remitting money to another bank using Internet banking.

It provides a remittance model that allows easy remittance using the recipient's service account and real name without knowing the recipient's account number.

It provides a remittance model that can send money by selecting a recipient from a list of remittance friends with recent remittance history or set by a user.

The present invention provides a remittance model in which a recipient can be selected and remitted from an address book stored on a user terminal.

It provides a remittance model that allows users to select and send money from an address book on an application by linking with an application that has an address book.

It provides a remittance model that can selectively receive the amount received from others into the user's bank account, as well as convert to electronic money such as points.

A computer-implemented remittance method, comprising: receiving a service account associated with a remittance service and a recipient name from a user terminal as remittance information including a remittance amount and information of a recipient to which remittance is received; And confirming the name of the recipient used on the remittance service using the service account and the recipient name, and then transmitting the remittance information to the terminal of the recipient using the service account. .

A computer readable medium comprising an instruction for a computer system to perform a remittance processing process, the instruction comprising: a remittance information including a remittance amount from a user terminal and information of a recipient who is a remittance recipient and a service account associated with a remittance service; Receiving a recipient name; And checking the name of the recipient used on the money transfer service using the service account and the recipient name, and then transmitting the remittance information to the terminal of the recipient using the service account. A computer readable storage medium is provided for controlling a system.

A memory loaded with at least one program; And at least one processor, wherein the at least one processor is configured to provide a service account and a recipient name related to a remittance service as remittance information including a remittance amount from a user terminal and information of a recipient to which remittance is received under a control of the program. Receiving; And checking the name of the recipient used on the money transfer service using the service account and the recipient name, and then transmitting the remittance information to the terminal of the recipient using the service account. .

According to an embodiment of the present invention, by using the recipient's service account and real name transfer, even if the recipient's account number is not known, it is possible to process a direct transfer between individuals subscribed to the service.

According to an embodiment of the present invention, a recipient may be more easily inputted by providing a list of remittance friends having a recent remittance history or set by a user in a recipient selection process.

According to an embodiment of the present invention, a recipient may be more easily selected by providing an address book stored on a user terminal in a recipient selection process or by providing an address book on a corresponding application through linkage with an application having an address book.

According to an embodiment of the present invention, in addition to receiving the amount received from another person in the user's bank account, the user can receive the amount sent by the other person even if there is no account registered in the service by converting it to electronic money such as points.

1 is a view for explaining an example of a money transfer service environment according to an embodiment of the present invention.

2 is a block diagram illustrating an internal configuration of a money transfer system according to an embodiment of the present invention.

3 is a flowchart illustrating a method of registering an account for remittance according to an embodiment of the present invention.

4 to 8 exemplarily illustrate a user interface screen associated with an account registration procedure according to one embodiment of the present invention.

9 and 10 are flowcharts illustrating a remittance processing method according to an embodiment of the present invention.

11 to 15 illustrate examples of a user interface screen related to a remittance processing procedure according to one embodiment of the present invention.

16 is a flowchart illustrating a remittance receiving method according to an embodiment of the present invention.

17 exemplarily illustrates a user interface screen related to a remittance receiving procedure according to an embodiment of the present invention.

18 is a block diagram for explaining an example of an internal configuration of a computer system according to an embodiment of the present invention.

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

The present embodiments relate to a remittance model for processing online remittances over the Internet. More specifically, the present invention relates to a method, a system and a record capable of processing a direct remittance between individuals using a user identifier associated with a remittance service instead of a bank account number. It is about the medium.

1 is a view for explaining an example of a money transfer service environment according to an embodiment of the present invention. 1 shows user terminals 101 and 102 and a money transfer system 100. In FIG. 1, an arrow means that data may be transmitted and received between components using the wired / wireless network 10.

User terminals 101 and 102 may execute one or more processes configured to perform one or more of the features described herein. The user terminals 101 and 102 may refer to all terminal devices capable of accessing a web / mobile site related to the remittance system 100 or installing and executing a service-only application. In this case, the user terminals 101 and 102 may perform overall service operations such as service screen configuration, data input, data transmission, and data storage under the control of a web / mobile site or a dedicated application.

Examples of the user terminals 101 and 102 include a personal computer, a laptop computer, a laptop computer, a smart phone, a tablet, a wearable computer, and the like. Include, but are not limited to such.

User terminals 101 and 102 may be coupled directly or indirectly to network 10 (eg, the Internet or a local area network, etc.). For example, personal computers and notebook computers may be coupled directly to the network 10 via a wired network connection. The laptop computer may be wirelessly coupled to the network 10 through a wireless communication channel established between the laptop computer and a wireless access point (ie, WAP). The smartphone may be wirelessly coupled to the network 10 via a wireless communication channel established between the smartphone and the cellular network / bridge. In this case, the network 10 may communicate with one or more secondary networks (not shown), and examples of the secondary networks include a local area network, a wide area network, or an intranet. intranet), but is not limited to such.

The user terminals 101 and 102 may interface with the remittance system 100 through the network 10 described above.

The remittance system 100 serves as a service platform for providing a remittance service to a client. The money transfer system 100 may execute one or more processes configured to perform one or more of the features described herein.

Remittance system 100 corresponds to a server computer, examples of which may include, but are not limited to, server computing devices, personal computers, server computers, series of server computers, mini computers, and / or mainframe computers. It is not limited only. The server computer may be a distributed system, and the operations of the server computer may be executed simultaneously and / or sequentially on one or more processors.

In particular, the money transfer system 100 may process direct money transfer between individuals using a user identifier associated with the money transfer service. In the present specification, the user identifier may mean all information that can specify a recipient for remittance instead of an account number, and examples thereof may include, but are not limited to, a service account, a telephone number, an email, and the like. . In this case, the service account is a user ID registered in the remittance service, a user registered in another service (for example, portal service, integrated search service, shopping service, map service, community service, social network service, etc.) linked with the remittance service. ID may be included, but is not limited to such.

For example, the remittance system 100 may provide a remittance processing process for an individual, such as home banking when remitting between individuals. As another example, the remittance system 100 may also deposit the amount of money remitted to the mother account on the remittance service upon remittance between individuals and then transfer the remittance from the mother account to the recipient's account. In other words, the remittance processing unit 212 may perform remittance processing between individuals through firm banking using a mother account.

The remittance system 100 may interface with the bank company server 103 through the network 10 to perform one or more processes required in the remittance process. In this case, the remittance system 100 is composed of one system combined with the bank company server 103, or composed of a separate system from the bank company server 103 to interoperate with the bank company server 103 to transfer the money transfer service. The present invention is not limited thereto, and in some cases, the form or method of building the remittance system 100 may be changed. The money transfer system 100 may be configured such that a partial configuration of the money transfer system 100 resides on the bank company server 103 in accordance with a system implementation or service type when the money transfer system 100 is configured as a separate system from the bank company server 103. . In addition, the remittance system 100 may be constructed in a one-to-one system form for each bank company, or may be separately configured as an integrated system for a service for several bank companies.

The remittance system 100 may be implemented as one system or at least one service platform among services requiring a remittance function such as a portal service, an integrated search service, a shopping service, a map service, a community service, a social network service, or a separate system. Implemented as a system, it is possible to provide remittance service through linkage between services.

The money transfer system 100 may provide a web-based money transfer environment by itself, and may be implemented in a form included in a service platform that provides money transfer services in a client-server environment. As another example of an implementation of the money transfer system 100, the money transfer system 100 may be implemented in the form of a client device application, such as a mobile only application installed on the user terminals 101 and / or 102, but only as such. It is not limited.

2 is a block diagram illustrating an internal configuration of a money transfer system according to an embodiment of the present invention.

As shown in FIG. 2, the remittance system 200 according to the present embodiment may include a processor 210, a bus 220, a network interface 230, a memory 240, and a database 250. . The memory 240 may include an operating system 241 and a remittance processing routine 242. The processor 210 may include a register 211, a money transfer processor 212, and a reception processor 213. In other embodiments, the transfer system 200 may include more components than the components of FIG. 2.

The memory 240 is a computer-readable recording medium and may include a permanent mass storage device such as random access memory (RAM), read only memory (ROM), and a disk drive. In addition, the memory 240 may store program codes for the operating system 241 and the remittance processing routine 242. These software components may be loaded from a computer readable recording medium separate from the memory 240 using a drive mechanism (not shown). Such a separate computer-readable recording medium may include a computer-readable recording medium (not shown) such as a floppy drive, a disk, a tape, a DVD / CD-ROM drive, a memory card, and the like. In other embodiments, the software components may be loaded into the memory 240 via the network interface 230 rather than the computer readable recording medium.

The bus 220 may enable communication and data transmission between the components of the transfer system 200. The bus 220 may be configured using a high-speed serial bus, a parallel bus, a storage area network and / or other suitable communication technology.

The network interface 230 may be a computer hardware component for connecting the transfer system 200 to a computer network. The network interface 230 may connect the remittance system 200 to the computer network through a wireless or wired connection.

The database 250 stores and maintains all the information necessary to provide a remittance service. At this time, the database 250 is registered on the basic personal information (for example, name, gender, nationality, date of birth, etc.) for each user, the user identifier (service account, mobile number, e-mail, etc.) associated with the transfer service, the transfer service Personal information may be maintained, including account information, a history of remittances and / or receipts, electronic money on remittance services and a history of electronic money, and the like. In FIG. 2, although the database 250 is included in the remittance system 200, it is also possible to exist as an external database built on a separate system.

The processor 210 may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input / output operations of the remittance system 200. The instructions may be provided to the processor 210 by the memory 240 or the network interface 230 and via the bus 220. The processor 210 may be configured to execute program codes for the register 211, the remittance processor 212, and the receive processor 213. Such program code may be stored in a recording device such as memory 240.

The registration unit 211, the remittance processing unit 212, and the reception processing unit 213 may be configured to perform the steps of the remittance method which will be described below.

3 is a flowchart illustrating a method of registering an account for remittance according to an embodiment of the present invention. In the account registration method according to the present invention, each step may be performed by the registration unit 211 described with reference to FIG. 2.

In operation 301, the registration unit 211 may perform user authentication for a user who requests a service subscription. At this time, the registration unit 211 may perform a self-authentication process through one or more authentication methods, such as a mobile phone authentication method, a real name authentication method, an authentication method using an authorized certificate, an authentication method using ARS.

4 is a diagram illustrating an example of a user authentication screen 400 displayed on a user terminal as a user interface related to a user authentication procedure of the register 211. For example, the user authentication screen 400 shows a user authentication screen according to a mobile phone authentication method, and may include a user interface for requesting input of personal information for mobile phone authentication. Thus, the registration unit 211 is a mobile phone authentication based on the personal information (for example, name, gender, nationality, date of birth, mobile phone number, communication company, etc.) input through the identity authentication screen 400 for the user to the user Verification procedures can be performed.

In steps 302 and 303, the registration unit 211 may limit the registration of the remittance service when the user authentication fails after determining whether the user authentication succeeds according to the user authentication result using the mobile phone authentication method or the like.

In steps 302 and 304, the registration unit 211 may perform a password registration procedure for registering the user's password if the user authentication is successful. At this time, the password is used for authentication in the transfer or payment using a registration account to be described below.

FIG. 5 illustrates an example diagram of a password input screen 500 displayed on a user terminal as a user interface associated with a password registration procedure of the register 211. As an example, the password input screen 500 may include a user interface for requesting input of a password used for authentication in money transfer, payment, and the like. The password input screen 500 may include a keypad area and a character input area into which a character (for example, a number, etc.) selected through the keypad is input, wherein the keypad area is automatically accessed when the password input screen 500 is approached. It can be configured as a security keypad that is exposed and changes the keyboard layout each time or presses the keyboard to convert the actual input value into a random number.

The registration unit 211 may register the input characters through the password input screen 500 as a password for authenticating the user. Furthermore, the registration unit 211 repeatedly requests the password to be re-entered at least once and all the same as the previously entered password. When a character is inputted, a method of registering the password can be applied.

In addition, the registration unit 211 may perform the agreement agreement procedure for using the remittance service before or after performing the password registration procedure. In this case, the terms of use may include all the conditions necessary for the use of the remittance service, for example, the terms of the remittance service member terms of use, the electronic financial transaction terms, the consent to the collection and use of personal information, and the payment information to a third party.

In steps 305, 306, 307, and 308, the registration unit 211 may perform an account registration procedure for registering an account to be used for remittance. For example, the registration unit 211 may register only one account in the form of one person and one account, and delete the existing registration account to change the account, and then register the new account. As another example, the registration unit 211 may register a plurality of accounts in the form of one N account without limiting the number of registered accounts.

For example, the registration unit 211 may perform an account registration procedure in the order of account information input-> withdrawal agreement of input account-> test deposit authentication-> registration completion. 6 illustrates an example diagram of an account input screen 600 displayed on a user terminal as a user interface associated with an account registration procedure of the register 211. For example, the account input screen 600 may include a user interface for requesting input of account information such as a bank and an account number. In a user interface requiring a bank selection, the bank may be exposed as a selection state when the bank is selected. When a character is input in addition to the number when the account number is input, an alert message (for example, 'only numbers can be input') may be exposed on the account input screen 600. The user's basic personal information (name, date of birth, mobile phone number, etc.) required for account registration is not entered separately, but the personal information pre-registered in the remittance service or other services related to the remittance service (e.g., portal service including remittance service). It may be utilized, and may be automatically exposed to the account input screen 600.

The registration unit 211 may perform an account name verification procedure for the input account to register only the account of the user's own name in the process of inputting the account information. If the account is not the user's account, an alert message (for example, 'Your account registration failed because it was not verified as your account.').

When the user requests an account registration for the input account, the registration unit 211 may perform a debit withdrawal consent procedure using ARS (305). 6 and 7, when the user inputs the account information on the account input screen 600 and then enters the registration button 601, the registration unit 211 accepts the debit withdrawal agreement through the ARS guide screen 710. In order to provide a guide for receiving an ARS call, and when the user requests the ARS guide on the ARS guide screen 710, the ARS phone can be connected to a mobile phone number included in the user's personal information. In this case, the ARS may provide a statement regarding a direct debit agreement for the account input by the user when the user receives a call.

The registrar 211, after confirming the user's intention to withdraw the debit through ARS (306), if the user does not agree to the debit withdrawal, an alert message (e.g. 'Do not accept direct debit) Account registration failed. ') Can be provided (307). On the other hand, the registration unit 211 registers the input account as a remittance account to be used for remittance when the user agrees to the debit withdrawal (308) and an alert message (for example, 'according to the debit withdrawal agreement upon completion of account registration) Registration is complete. ') In this case, the registration unit 211 may register a user's account by matching personal information including a user identifier.

The registration unit 211 may perform an authentication procedure using a test deposit for authentication of an input account. For example, the registration unit 211 may authenticate a user's input account by using a remittance identification number or some information (eg, transfer amount, date and time of transfer, summary, etc.) included in the deposit details of the corresponding account when the test deposit is made. As another example, the registration unit 211 may perform an account authentication procedure using processing information generated when the test deposit is completed. For example, the register 211 transfers a predetermined amount (for example, 1 won) to a corresponding account using a remittance information of a randomly generated remittance identification number for a test deposit into an account input by a user, and then remittance identification number. The user's input account can be authenticated using. The user can check the account deposit history provided by the bank company of the input account through SMS or ARS, and can authenticate the input account using some information based on this. Although the above account authentication procedure is limited to using a transfer related brief or separate processing information, it is not limited thereto.

8 illustrates an example of account authentication screens 810 and 820 displayed on a user terminal as a user interface related to a test deposit authentication procedure of the register 211. For example, the account authentication screen 810 may include a user interface for requesting a remittance identification number checked by the user in the test deposit history of the input account. As another example, the account authentication screen 820 may include a user interface for requesting input of a test deposit amount deposited in a user's input account. Therefore, the registration unit 211 is a case in which the remittance identification number input from the user matches the remittance identification number generated when the test deposit of the input account, or the amount input from the user matches the amount remitted when the test deposit into the input account The input account can be normally registered as a remittance account. In this case, the registration unit 211 may guide a path (for example, ARS phone number, etc.) for checking the deposit details of the test deposit through the account authentication screens 810 and 820, and for a predetermined time (for example, 24 hours). Once the remittance identification number is entered, the user can register the input account as a remittance account and cancel the account registration after a certain time.

9 and 10 are flowcharts illustrating a remittance processing method according to an embodiment of the present invention. In the remittance processing method according to the present invention, each step may be performed by the remittance processing unit 212 described with reference to FIG. 2.

In step 901, the money transfer processing unit 212 may determine whether a money transfer account is registered for the user when a service request for money transfer is received from the user terminal.

In operation 902, the money transfer processing unit 212 may request an account registration process for the user from the registration unit 211 to register the money transfer account first if the money transfer account is not registered.

In steps 903 to 907, the remittance processing unit 212 may perform a recipient selection procedure for receiving an identifier and a real name of a recipient for remittance from the user when the remittance account is already registered. Examples of identifiers may include service accounts, telephone numbers, e-mails, etc., as well as all information for specifying recipients. In the present specification, the real name may mean an actual name of the user, and the present invention is not limited thereto, and may include a name that the user actually uses in the remittance service, for example, a name registered in advance on the remittance service when the service is subscribed.

As an example, the money transfer processing unit 212 may receive a selection of a recipient using a service account of the recipient (for example, a user ID registered in the money transfer service, a user ID registered in another service linked with the money transfer service, etc.) ( 904). As another example, the remittance processing unit 212 may be selected by the recipient using the recipient's mobile phone number (905). The remittance processing unit 212 may receive a real name of the selected recipient after receiving a selection using a service account or a mobile phone number (906). In this case, the real name of the recipient may be input through a direct input method.

When the recipient is selected using the service account and the mobile phone number, the money transfer processing unit 212 may directly input the service account or the mobile phone number of the recipient by providing a direct input method. Alternatively, the money transfer processing unit 212 may expose an address book stored on the user terminal and receive a service account or a mobile phone number of a recipient selected from the corresponding address book. Alternatively, the remittance processing unit 212 exposes the address book on the address book app in conjunction with a separate application (hereinafter referred to as 'address book app') having an address book and inputs a service account or a mobile phone number of a recipient selected from the address book. I can receive it.

As another example, the remittance processing unit 212 may specify a recipient selected from the remittance friend list after exposing a remittance friend list having a recent remittance history or set by the user (907). To this end, the registration unit 211 automatically registers as a remittance friend including the user's service account and / or mobile phone number and real name of the person recently sent or received, or the user's service account directly input by the user in a pre-registration environment. And / or register as a transfer friend, including cell phone number and real name. In this case, when the recipient is selected using the remittance friend list, the remittance processing unit 212 may omit the real name input procedure because the real name is included in the remittance friend list.

FIG. 11 illustrates an example of a remittance information input screen 1100 displayed on a user terminal as a user interface related to a remittance processing procedure of the remittance processing unit 212. For example, the remittance information input screen 1100 may include a user interface for requesting input of remittance information including a recipient, a remittance amount, a remittance related message, and the like. Remittance information input screen 1100 may expose at least a portion of information about the remittance account registered by the user. In addition, the remittance information input screen 1100 may further include a user interface for requesting consent of the third party to provide personal information. The remittance processing unit 212 may provide a recipient selection page when inputting an interface for selecting a recipient on the remittance information input screen 1100.

FIG. 12 illustrates an exemplary view of a recipient selection screen 1200 for selecting a recipient as a user interface related to a remittance processing procedure of the remittance processing unit 212. For example, the recipient selection screen 1200 may include a first user interface for selecting a recipient using at least one of an identifier such as a service account, a mobile phone number, and an email.

When the first user interface is selected on the recipient selection screen 1200, the money transfer processing unit 212 inputs an input page for inputting a real name together with any one of identifiers such as a service account, a mobile phone number, and an e-mail as shown in FIG. 1310 and 1320 may be provided.

When the first user interface is selected on the recipient selection screen 1200, the remittance processing unit 212 accesses the address book on the user terminal or the address book on the address book app as shown in FIG. 14, and includes a selection page 1410. If a specific recipient is selected on the selection page 1410 after providing the information, an input page 1420 for inputting a real name of the corresponding recipient may be provided.

The money transfer processing unit 212 provides input pages 1310 and 1320 for inputting an identifier and a real name of a recipient in a money transfer environment through a web browser in consideration of a service providing environment, and a money transfer environment implemented as a mobile-only application. In FIG. 14, a selection page 1410 using an address book may be provided in association with an address book.

Referring to FIG. 12, when the transfer friend list exists, the recipient selection screen 1200 may further include a second user interface for selecting a recipient using the transfer friend list. A profile image, a service account, a real name, and the like may be exposed on the remittance friend list of the recipient selection screen 1200.

When the selection of the recipient is completed, the remittance processing unit 212 may expose the information of the recipient selected by the user on the remittance information input screen 1500 as shown in FIG. 15. In this case, the information of the recipient exposed on the remittance information input screen 1500 may include a real name input by the user and an identifier (service account, telephone number, e-mail, name, etc.) corresponding to the recipient selection method. .

In step 908, the remittance processing unit 212 may request the user to input the remittance amount, and may receive the remittance amount input by the user through the remittance information input screen 1500. For example, the remittance information input screen 1500 may include an area for directly inputting an amount of a unit of money and an amount button for automatically inputting a predetermined amount of money.

The following procedure after the remittance processing procedure described with reference to FIG. 9 will be described with reference to FIG. 10.

In step 1009, the transfer processing unit 212 may check the transfer limit per unit period of the user when the recipient selection and the transfer amount input from the user are completed and the transfer request is received. For example, the remittance limit per unit period may be automatically set by default or set by the user directly, for example, 500,000 won per 1ID per day. As another example, the remittance limit per unit period may be set differentially according to whether or not a minor, for example, an adult may be set to 500,000 won per 1ID per day, and a minor may be set to 100,000 won per 1ID per day. In addition to the remittance limit per unit period, the minimum remittance limit may also be preset to a certain amount (eg, 1,000 won).

In step 1010, the remittance processing unit 212 stops the remittance processing process and exceeds the limit when the combined amount exceeds the remittance limit per unit period by adding the remittance amount requested for the remittance to the existing remittance amount remitted in the unit period. You can provide a message.

In step 1011, the remittance processing unit 212 may check the balance of the mother account related to the remittance account when the remittance amount requested for the remittance is summed with the existing remittance amount remitted in the unit period and the combined amount does not exceed the remittance limit. The parent account balance limit can be set automatically or set by the user, for example, the balance limit can be set to 2 million won at the time of remittance.

The remittance processing unit 212 may add the remittance amount requested for the recent remittance with the remittance amount waiting to be received and provide an allot message indicating that the sum is exceeded when the sum exceeds the balance limit of the mother account (1010).

In operation 1012, the remittance processing unit 212 may request the user to input a password for authentication when the sum of money recently requested to be remitted is combined with the remittance amount waiting to be received and the combined amount does not exceed the balance limit of the mother account.

In operation 1013, the remittance processing unit 212 may compare the password input from the user with the previously registered password and check whether the password is matched. If the two passwords do not match, the remittance processing unit 212 may provide an alert message indicating a password error.

In step 1014, the transfer processing unit 212 may check the balance of the remittance account if the password input from the user matches the registered password.

In step 1015, the remittance processing unit 212 provides an alert message indicating that the balance is insufficient when the amount of money recently requested for remittance exceeds the balance of the remittance account, and to the recipient selected by the user if the balance of the remittance account is not exceeded. You can send the remittance details for the transfer amount.

In steps 1016 and 1017, the remittance processing unit 212 may provide a function for canceling the remittance before the recipient receives the remittance amount for the remittance waiting to be received, and the user requests to cancel the remittance while the user is waiting to receive the remittance. In this case, the transfer can be canceled.

In steps 1018 and 1017, the remittance processing unit 212 may cancel the remittance at the time when the remittance acceptance deadline has elapsed if the recipient does not receive the amount of money sent by the user within the predetermined remittance acceptance deadline. Remittance acceptance deadline (e.g., 3 days) may be set as a deadline for the recipient to receive the remittance amount, and the remittance acceptance deadline may be automatically set by default or set directly by the user who is the remitter. .

In steps 1019, 1020, and 1017, the remittance processing unit 212 may determine whether the real name entered by the user with the identifier matches the real real name corresponding to the identifier, and the real name entered by the user is different from the real real name. In this case, you can provide an alert message indicating the real name error and cancel the transfer.

The remittance processing unit 212 can verify the real name by comparing the real name and the identifier in the personal information registered in the database against the identifier of the recipient included in the remittance information and the real name, this real name verification process is a service account or mobile number It can be performed when the recipient is selected by using a message, and can be omitted when the recipient is selected in the remittance friend list.

Remittance processing unit 212 completes the remittance processing process by requesting the recipient to receive the money sent by the user within the remittance acceptance deadline and forwarding the amount to the recipient if the real name included in the user's remittance information matches the recipient's real name. can do.

In steps 1021, 1022, and 1023, the remittance processing unit 212 checks whether or not the user's original account issue at the time of remittance, and if there is no specific issue, returns the canceled amount to the original account and if a specific issue occurs, The amount of the canceled transfer can be returned to the set refund balance.

16 is a flowchart illustrating a remittance receiving method according to an embodiment of the present invention. In the remittance receiving method according to the present invention, each step may be performed by the receiving processing unit 213 described with reference to FIG. 2.

In operation 1601, the reception processor 213 may provide a reception notification to the user together with the remittance details when the remittance details of the sender are received. As an example, the reception processing unit 213 may send a text message including a remittance reception history (sender information, remittance date, remittance amount, etc.) to a corresponding user terminal through a text service (for example, SMS) for a remittance of a user. Can be transmitted. As another example, the reception processing unit 213 may expose the remittance reception details through the notification page of the user associated with the remittance service for the remittance to the user. As another example, the reception processing unit 213 may simultaneously apply the above two types of remittance reception notification methods. The remittance reception notification may include a link for moving to a remittance reception detail screen that allows the sender to receive the remittance amount.

Furthermore, the reception processing unit 213 may determine the remittance reception notification method according to the recipient selection method by the sender. For example, if a sender selects a recipient by using a mobile phone number, the sender can be notified by text message. When a sender is selected by using a service account, the sender can be notified by a notification page related to the remittance service. If you select a recipient using the remittance friend list, you can use both a text message and a notification page to notify you of the remittance.

The reception processing unit 213 may provide a remittance reception notification through a text message even if the user selected as the recipient is not a registered member in the remittance service (or another service linked with the remittance service), and then proceed with the remittance reception step. In order to do so, you may proceed with the necessary procedures for receiving the remittance, including the procedure for signing up for membership and agreeing with the terms for using the remittance service.

In steps 1602 and 1603, the reception processing unit 213 may cancel the transfer of the transfer if the transfer cancellation request is received from the sender before the user receives the transfer of the sender, and the text service and / or the transfer to the user A notification page associated with the service may provide a remittance cancellation notice indicating that the remittance has been canceled by the sender.

In steps 1604 and 1603, if the user does not receive the sender's remittance within the predetermined remittance acceptance period, the reception processing unit 213 similarly cancels the remittance and sends the user a notification page associated with the text service and / or the remittance service. Can be used to provide remittance cancellation notices indicating that remittances have been canceled due to the lapse of time.

In steps 1605, 1606, and 1603, the reception processing unit 213 may check whether the real real name of the user who has received the remittance reception notification regarding the sender's remittance matches the real name included in the remittance details of the sender. In other cases, you can provide an alert message indicating a blindness error and cancel the transfer. The real name verification procedure may be performed when the sender selects a recipient using a service account or a mobile phone number, and may be omitted when the recipient is selected from the transfer friend list.

In step 1607, the reception processing unit 213 may perform the selection procedure of the transfer method when the user requests to receive the money sent from the sender within the time limit for remittance acceptance and the real name authentication is normally processed.

FIG. 17 is a diagram illustrating an example of a remittance reception detail screen 1700 displayed on a user terminal as a user interface related to a remittance reception procedure of the reception processing unit 213. For example, the detailed information on the remittance receiving screen (1700) exposes the sender's remittance details (for example, the sender's name, remittance date, remittance amount, remittance-related message, etc.), and the remittance receiving method for receiving the remittance amount sent by the sender. A user interface may be included that requires the selection of. Accordingly, the user may select the remittance receiving method to receive the money remitted by the sender after checking the remittance detailed information exposed on the remittance receiving detail screen 1700.

Remittance receiving methods may include, but are not limited to, receiving by bank account and receiving by electronic money (eg, points) related to the remittance service. In order to receive a bank account, it is necessary to register an account on the remittance service. In the case of electronic money such as points, it is possible to receive a remittance without a registered account.

In operation 1608 and 1609, when the user selects a method of receiving a bank account as a method of receiving a transfer, the reception processor 213 may check whether a bank account registered on the transfer service exists for the user.

In steps 1610 and 1611, the reception processing unit 213 requests the user to proceed with the account registration process if the user's account registered on the money transfer service does not exist, and receives the money transfer if the user does not proceed with the account registration process. You can provide an alert message indicating an error. In this case, when the user does not proceed with the account registration process, the reception processing unit 213 may suspend the transmission of the corresponding case or request reselection of the remittance reception method.

In steps 1609, 1610, and 1612, the reception processing unit 213 determines whether the status of the registered account is in a normal state when the user's account registered on the money transfer service already exists or registers a new account through the account registration procedure. You can check. At this time, the reception processing unit 213 provides an allot message indicating a remittance reception error when the user's registered account is not in the state of receiving a remittance, and when the user's registered account is in a normal state, the sender's remittance amount is deposited to the corresponding account. Thereby completing the remittance receiving process.

In steps 1613 and 1614, the reception processor 213 may check the balance limit of the electronic money of the user when the user selects a method of depositing the electronic money as a money transfer reception method. The electronic money balance limit may be set automatically or set by the user, for example, the point balance limit may be set to 2 million won.

Receiving processing unit 213 adds the transfer amount received from the sender and the current balance of the user's electronic money, if the combined amount does not exceed the balance limit, the transfer amount of the sender is converted to electronic money to be credited to the user The receiving process can be completed.

The reception processing unit 213 may perform a user authentication procedure using an authentication password registered on the money transfer service. However, the reception processing unit 213 may omit the authentication procedure using the password.

Meanwhile, the reception processing unit 213 may add the remittance amount received from the sender and the current balance of the user's electronic money to provide an allot message indicating a remittance reception error when the combined amount exceeds the balance limit. In this case, when the combined amount exceeds the predetermined electronic money balance limit, the reception processing unit 213 may suspend receiving the transfer or request reselection of the transfer method.

In the above description, it is described that the sender receives the full amount of money sent to the bank account or electronic money, but the present invention is not limited thereto. For example, it is possible to provide a complex receiving method for receiving and receiving a remittance by dividing it into a bank account and an electronic money, which allows a user to selectively divide the remittance amount into a bank account and the rest to an electronic money. It is also possible to receive.

The remittance system 200 of the above configuration can provide a payment environment that can be used directly as a payment for online commerce (for example, Internet shopping) after the user receives the money sent by the sender as an account or electronic money. have.

The remittance method may include shorter operations or additional operations based on the details of the remittance system described with reference to FIGS. 1 to 17. Also, two or more operations may be combined and the order or location of the operations may be changed.

4 to 8, 11 to 15, and 17 are exemplary screens for helping understanding of the invention and for convenience of description. The configuration and order of the screens may be changed.

18 is a block diagram for explaining an example of an internal configuration of a computer system according to an embodiment of the present invention. Computer system 1800 includes at least one processor 1810, memory 1820, peripheral interface 1830, I / O subsystem 1840. , At least, a power circuit 1850 and a communication circuit 1860. In this case, the computer system 1800 may correspond to a user terminal.

The memory 1820 may include, for example, high-speed random access memory, a magnetic disk, an SRAM, a DRAM, a ROM, a flash memory, or a nonvolatile memory. have. The memory 1820 may include software modules, instruction sets, or other various data necessary for the operation of the computer system 1800. In this case, accessing the memory 1820 from another component such as the processor 1810 or the peripheral interface 1830 may be controlled by the processor 1810.

Peripheral interface 1830 may couple input and / or output peripherals of computer system 1800 to processor 1810 and memory 1820. The processor 1810 may execute a software module or a set of instructions stored in the memory 1820 to perform various functions and process data for the computer system 1800.

Input / output subsystem 1840 may couple various input / output peripherals to peripheral interface 1830. For example, the input / output subsystem 1840 may include a controller for coupling a peripheral device such as a monitor or keyboard, a mouse, a printer, or a touch screen or sensor, as needed, to the peripheral interface 1830. According to another aspect, input / output peripherals may be coupled to peripheral interface 1830 without passing through input / output subsystem 1840.

The power circuit 1850 may supply power to all or part of the components of the terminal. For example, the power circuit 1850 may be a power management system, one or more power sources such as batteries or alternating current (AC), charging systems, power failure detection circuits, power converters or inverters, power status indicators or power sources. It can include any other components for creation, management, distribution.

The communication circuit 1860 may enable communication with other computer systems using at least one external port. Alternatively, as described above, the communication circuit 1860 may include an RF circuit to transmit and receive an RF signal, also known as an electromagnetic signal, to enable communication with another computer system.

This embodiment of FIG. 18 is only one example of computer system 1800, and computer system 1800 may include some components shown in FIG. 18, or may include additional components not shown in FIG. It may have a configuration or arrangement that combines two or more components. For example, the computer system for a communication terminal in a mobile environment may further include a touch screen or a sensor, in addition to the components shown in FIG. 18, and various communication schemes (WiFi, 3G, LET) in the communication circuit 1860. , Bluetooth, NFC, Zigbee, etc.) may include a circuit for RF communication. Components included in the computer system 1800 may be implemented in hardware, software, or a combination of both hardware and software, including integrated circuits specialized for one or more signal processing or applications.

As described above, according to an exemplary embodiment of the present invention, direct money transfer can be performed between individuals subscribed to the service even if the recipient's account number is not known by remittance using the recipient's service account and real name. In addition, according to an embodiment of the present invention, a recipient may be more easily inputted by providing a list of remittance friends having a recent remittance history or set by a user in a recipient selection process. In addition, according to an embodiment of the present invention, by providing an address book stored on the user terminal in the recipient selection process or by providing an address book on the application through interworking with the application that holds the address book, it is easier to input the recipient for remittance Can be. Furthermore, according to an embodiment of the present invention, in addition to receiving the amount received from another person in the user's bank account, the user can receive the amount sent by the other person even if there is no account registered in the service by converting to electronic money such as points.

Methods according to an embodiment of the present invention may be implemented in program instruction form that can be executed by various computer systems and recorded in a computer readable medium.

The program according to the present embodiment may be configured as a PC-based program or an application dedicated to a mobile terminal. App related to the transfer service in the present embodiment is implemented in the form of a program that operates independently, or in-app (in-app) form of a specific application (for example, portal service app, search service app, etc.) It may be implemented to enable operation on a specific application.

In addition, the method according to an embodiment of the present invention can be performed by the application associated with the server system for providing a transfer service by controlling the user terminal. As one example, such an application may execute one or more processes configured to perform one or more of the features described herein. In addition, such an application may be installed in the user terminal through a file provided by the file distribution system. For example, the file distribution system may include a file transmitter (not shown) for transmitting the file at the request of the user terminal.

The apparatus described above may be implemented as a hardware component, a software component, and / 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. Or may be permanently or temporarily embodied in a signal wave to be transmitted. 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. The hardware device described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

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.

Embodiments of the present invention can be used in a remittance model for processing online remittances over the Internet.

Claims (22)

1. In the computer-implemented remittance method,

   Receiving a service account and a recipient name related to the remittance service from the user terminal as remittance information including the remittance amount and information of a recipient to which the remittance is received; And

   Confirming the name of the recipient used on the remittance service using the service account and the recipient name, and then transmitting the remittance information to the terminal of the recipient using the service account;

   Remittance method comprising a.
2. The method of claim 1,

   Managing a service account having a remittance history and a recipient name with respect to the user terminal as a remittance friend list;

   More,

   The receiving step,

   Providing the remittance friend list to the user terminal; And

   Receiving a selection of a specific destination included in the remittance friend list from the user terminal;

   Remittance method comprising a.
3. The method of claim 1,

   The receiving step,

   Providing the address book by accessing an address book stored in the user terminal in a recipient selection process; And

   Receiving a selection of a specific object included in the address book from the user terminal;

   Remittance method comprising a.
4. The method of claim 1,

   The receiving step,

   Providing the address book in association with an application for managing an address book associated with the user terminal in a recipient selection process; And

   Receiving a selection of a specific object included in the address book from the user terminal;

   Remittance method comprising a.
5. The method of claim 1,

   Checking the name of the recipient,

   Comparing the name registered in the service account with the recipient name received with the recipient information;

   Remittance method characterized in that.
6. The method of claim 1,

   The transmitting step,

   Delivering a notification message including the remittance information through at least one of a notification page related to the remittance service and a text service (SMS);

   Remittance method characterized in that.
7. The method of claim 1,

   Receiving an acceptance request for the remittance information from the terminal of the recipient; And

   Remitting the transfer amount through the service account according to the acceptance request

   Remittance method comprising more.
8. The method of claim 7, wherein

   The remittance process,

   A remittance method for remitting the remittance amount to an account linked to the service account, a remittance method for converting the remittance amount to electronic money associated with the service account, the remittance amount divided by remitting a portion of the remittance amount to the account and the rest Remittance by any one of the remittance method to convert to the telephone currency

   Remittance method characterized in that.
9. The method of claim 7, wherein

   Receiving the transfer request is,

   Providing a menu for selecting a reception method for the remittance amount to the terminal of the recipient and receiving a selection of a specific reception method included in the menu together with the acceptance request from the terminal of the recipient;

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

    Canceling the remittance waiting to be received by the recipient according to the cancellation request of the user terminal;

    Remittance method comprising more.
11. The method of claim 1,

    Canceling the pending transfer if the recipient does not accept the transfer within a certain period of time

    Remittance method comprising more.
12. The method of claim 1,

    Steps to register an account associated with the user

    More,

    The registering step,

    Processing a test deposit for account verification into the account; And

    Performing authentication processing on the account using the deposit processing information of the account according to the test deposit;

    Remittance method comprising a.
13. A computer readable medium comprising instructions for a computer system to perform a remittance processing process,

    The command is

    Receiving a service account and a recipient name related to the remittance service from the user terminal as remittance information including the remittance amount and information of a recipient to which the remittance is received; And

    Confirming the name of the recipient used on the remittance service using the service account and the recipient name, and then transmitting the remittance information to the terminal of the recipient using the service account;

    And control the computer system by a method comprising: a computer readable storage medium.
14. A memory loaded with at least one program; And

    At least one processor

    Including,

    The at least one processor, according to the control of the program,

    Receiving a service account and a recipient name related to the remittance service from the user terminal as remittance information including the remittance amount and information of a recipient to which the remittance is received; And

    Confirming the name of the recipient used on the remittance service using the service account and the recipient name, and then transmitting the remittance information to the terminal of the recipient using the service account;

    Remittance system to process.
15. The method of claim 14,

    The at least one processor, according to the control of the program,

    Managing a service account with a remittance history and a recipient name in relation to the user terminal as a remittance friend list;

    To process

    The receiving process,

    Receiving a selection of a specific object included in the remittance friend list from the user terminal after providing the remittance friend list to the user terminal;

    Remittance system characterized in that.
16. The method of claim 14,

    The receiving process,

    Receiving a selection of a specific object included in the address book from the user terminal after providing the address book in connection with an application for accessing an address book stored in the user terminal or managing an address book associated with the user terminal in a recipient selection process;

    Remittance system characterized in that.
17. The method of claim 14,

    Checking the name of the recipient,

    Performing recipient authentication by comparing a recipient name received with the recipient information with a name registered in the service account;

    Remittance system characterized in that.
18. The method of claim 14,

    The at least one processor, according to the control of the program,

    Receiving a request for acceptance of the remittance information from the terminal of the recipient; And

    Remittance of the transfer amount through the service account according to the acceptance request

    Remittance system to process.
19. The method of claim 18,

    The remittance process,

    A remittance method for remitting the remittance amount to an account linked to the service account, a remittance method for converting the remittance amount to electronic money associated with the service account, the remittance amount divided by remitting a portion of the remittance amount to the account and the rest Remittance by any one of the remittance method to convert to the telephone currency

    Remittance system characterized in that.
20. The method of claim 18,

    Receiving the transfer request is,

    Providing a menu for selecting a reception method for the remittance amount to the terminal of the recipient and receiving a selection of a specific reception method included in the menu together with the acceptance request from the terminal of the recipient;

    Remittance system characterized in that.
21. The method of claim 14,

    The at least one processor, according to the control of the program,

    Canceling a remittance waiting to be received by the recipient according to a cancellation request of the user terminal, or canceling a remittance waiting to be received if the recipient does not accept the remittance within a predetermined period of time;

    Remittance system to process.
22. The method of claim 14,

    The at least one processor, according to the control of the program,

    The process of registering an account associated with a user

    To process

    The registration process,

    Processing a test deposit for account verification into the account; And

    Performing authentication processing on the account using the deposit processing information of the account according to the test deposit;

    Remittance system comprising a.

Images