TW201640424A - Remittance method and system of transaction processing for direct remittance using user account and a non-transitory computer-readable recording medium - Google Patents

Abstract

Provided is transaction processing technology for direct remittance by using a user account. The remittance method implemented in a computer includes receiving, from a user terminal, remittance information comprising a remittance amount and, as information of a receiver who is a remittance target, a receiver name and a service account related to a remittance service; and transmitting, to a terminal of the receiver, the remittance information by using the service account after checking the name of the receiver used in the remittance service by using the service account and the receiver name.

Description

Transaction method and system for direct remittance using customer account, and non-transitory computer readable recording medium

One or more embodiments relate to a remittance mode for online money transfer operations over a network.

The present application is a priority of the Korean Patent Application No. 10-2015-0042369, filed on March 26, 2015, the disclosure of which is hereby incorporated by reference.

Often, customers transfer money from their bank account to someone else’s bank account to remit a specific amount to another person; at this point, money can be made via phone banking, internet banking, bank staff at the bank, or automatically A cash machine (ATM, Automated Teller Machine) is used for the transfer.

With the development of information and communication technologies applied to the financial sector, face-to-face financial transactions through bank windows are facing changes in non-face-to-face financial transactions using non-face-to-face verification of communication networks.

For example, KR 10-2000-0072625 (published on December 5, 2000) on "Online Systems for Remittances Using Internet Websites" reveals a technique for using Internet financial operations to transfer money to another bank.

One or more embodiments include a money transfer model that allows a customer to conveniently transfer the amount to the payee using the payee's service account and real name even if the customer's account number is not known.

One or more embodiments include a money transfer model that allows a customer to select a payee from a recent remittance history or a list of remittance friends set by the customer and remit the money to the payee.

One or more embodiments include a money transfer model that allows a customer to remit money to a payee by selecting a payee from a contact list stored by the user terminal.

One or more embodiments include a money transfer model that allows a customer to select a payee from a contact list stored by the application by connecting to the application to remit the money to the payee.

One or more embodiments include a money transfer model that allows the customer to not only selectively receive an amount from another person to the customer's bank account, but also convert the amount into electronic money, such as points.

Other aspects will be set forth in part in the description which follows.

According to one or more embodiments, a computer-implemented remittance method includes receiving remittance information from a user terminal, the remittance information including a remittance amount, a payee name and a service account of the remittance service as a remittance party payee information; And using the service account and the payee name to check the name of the payee used in the money transfer service, and using the service account to transmit the remittance information to the payee terminal.

In accordance with one or more embodiments, a non-transitory computer readable recording medium includes instructions for a computer system executing a money transfer operation, wherein the instructions utilize a money transfer method to control a computer system, the non-transitory computer readable recording medium comprising: a user The terminal device receives the remittance information, where the remittance information includes the remittance amount, the name of the payee and the service account of the remittance service as the payee information of the remittance; and the use of the service account and the payee name to check the After the payee name used by the remittance service, the remittance information is transmitted to the payee terminal by using the service account.

According to one or more embodiments, a money transfer system includes: a memory in which at least one program is loaded; and at least one processor, wherein at least one processor is controlled according to the at least one program to perform the following: Receiving remittance information from the user terminal, the remittance information including the remittance amount, the payee name and service account of the remittance service as the remittance information of the remittance object; and using the service account and the payee name to check After the payee name used by the money transfer service, the service information is used to transmit the money transfer information to the payee terminal.

DETAILED DESCRIPTION OF THE INVENTION Reference will now be made in detail to the preferred embodiments embodiments As used in this specification, the term "and/or" includes any and all combinations of one or more of the associated listed items. The expressions preceding the elements, such as "at least one of", are used to modify the entire listed elements and do not modify the individual elements listed.

One or more embodiments relate to a remittance mode for online remittance operations over a network, which is more systematic, and one that does not utilize a bank account number, but instead uses a customer identifier for the remittance service to perform a direct remittance operation between individuals. Methods, systems, and recording media.

1 is a diagram illustrating an example of a money transfer service environment in accordance with an embodiment. Figure 1 schematically illustrates a user terminal (101, 102) and a money transfer system (100). The arrows in Figure 1 indicate that data transfer between components can be made using the network (10).

The user terminal (101, 102) may perform at least one job that is configured to perform at least one of the features described in this specification. The user terminal (101, 102) can be any terminal device capable of accessing a web page (web)/action website of the money transfer system (100); or installing and executing a dedicated service application. In this specification, the user terminal (101, 102) can perform service operations such as constructing a service screen, inputting data, transmitting and receiving data, and storing data under the control of a webpage/action website or a dedicated service application.

Examples of the user terminal (101, 102) include a personal computer (PC, Personal Computer), a notebook computer, a laptop computer, a smart phone, a tablet personal computer (PC), and a wearable computer. But it is not limited to this.

The user terminal (101, 102) can be directly or indirectly connected to the network (10), such as the Internet or a regional network. For example, a personal computer (PC) and a laptop can be directly connected to the network via a wired network connection (10). The laptop can wirelessly connect to the network (10) via a wireless communication channel established between the Wireless Access Point (WAP) and the laptop. The smart phone can wirelessly connect to the network (10) via a wireless communication channel established between the cellular network/bridge and the smart phone. In the present specification, the network (10) can communicate with at least one auxiliary network (not shown), wherein the examples of the auxiliary network include a regional network, a wide area network, and a corporate network, but are not limited thereto.

The user terminal (101, 102) can interface with the money transfer system (100) through the aforementioned network (10).

The remittance system (100) operates as a service platform that provides remittance services to customers. The money transfer system (100) can perform at least one job that constitutes at least one feature described in this specification.

The remittance system (100) corresponds to a server computer, and examples of the server computer include a server computer device, a personal computer (PC), a server computer, a series of server computers, a computer, a host computer , but not limited to this. The server computer can be a decentralized system, and the operation of the server computer can be performed simultaneously and/or sequentially on at least one processor side.

Specifically, the remittance system (100) can perform direct remittance operations between individuals by using the customer identifier of the remittance service. In this specification, a customer identifier may be any information that can detail the remittance payee rather than the account number, and examples of the customer identifier may include a service account, a phone number, and an e-mail address, but are not limited to this. In this specification, an example of a service account may include: a customer identification number (ID) registered in the money transfer service, a customer ID registered in another service interacting with the money transfer service, such as an portal service, an integrated inquiry service, a shopping service, a map. Service, community service or Social Network Service (SNS), but not limited to this.

For example, the money transfer system (100) may provide remittance operations for individuals (such as family finance) during remittances among individuals. As another example, the money transfer system (100) can provide the following operations: using the money transfer service to deposit the remittance amount to the original account; then, during the remittance period among the individuals, the remittance amount is transferred from the original account to the payee account. In other words, the remittance processing unit (212) shown in FIG. 2 can use the original account to conduct personal remittances through the financial company.

The money transfer system (100) can interface with a banking server (103) via the network (10) to perform at least one job required during the transfer. In this specification, the money transfer system (100) may be configured to incorporate one of the banking servers (103) or may constitute a separate system separate from the banking server (103) for interaction with the banking server (103). To provide remittance services. However, the money transfer system (100) is not limited thereto, and the form and method of forming the money transfer system (100) may vary. When the money transfer system (100) is constructed as a separate system separate from the bank server (103), certain components of the money transfer system (100) may constitute a structure or service type based on the money transfer system (100) to reside in the bank server ( 103). Moreover, the money transfer system (100) may constitute a one-to-one system or a set of integrated systems for several banks depending on the bank.

The remittance system (100) can provide a remittance service through service collaboration, which can be implemented as a system combining at least one service platform requiring remittance functions; or a separate system separated therefrom, such as an portal service platform, integrated query service Platform, shopping service platform, map service platform, community service platform, and SNS platform.

The service platform can provide a web-based (Web)-based remittance environment, and in the client-server environment, the remittance system (100) can be included in a service platform that provides remittance services. According to another embodiment, the money transfer system (100) can be implemented as a client device application, such as a dedicated mobile application installed on the user terminal (101) and/or the user terminal (102), although the specific embodiment does not. Limited to this.

2 is a block diagram of the internal structure of a money transfer system (200) in accordance with an embodiment.

As shown in FIG. 2, the money transfer system (200) according to an embodiment may include a processing unit (210), a bus bar (220), a network interface (230), a memory (240), and a data. Library (250). The memory (240) can include an operating system (241) and a money transfer routine (242). The processing unit (210) may include a registration unit (211), a money transfer processing unit (212), and a reception processing unit (213). According to a particular embodiment, the money transfer system (200) may include more components than those shown in FIG.

The memory (240) is a computer readable recording medium and may include a permanent mass storage device such as a random access memory (RAM), a read-only memory (ROM), or a magnetic memory. Disc player. Moreover, the memory (240) can store the code of the operating system (241) and the remittance routine (242). The software component can be loaded by a computer readable recording medium separated from the memory (240) by a drive mechanism (not shown). Examples of such separate computer readable recording media include floppy disk drives, magnetic disks, magnetic tapes, DVD/CD-ROM drives, and memory cards. According to another embodiment, the software component may not be readable by a computer readable recording medium, but instead is loaded into the memory (240) via the web interface (230).

The bus (220) allows communication and data transfer between components of the money transfer system (200). The bus bar (220) can be constructed using a high speed serial bus, a parallel bus, a storage area network (SAN), and/or another suitable communication technology.

The network interface (230) can be a computer hardware component for connecting the money transfer system (200) to the computer network. The network interface (230) can connect the money transfer system (200) to the computer network via a wireless or wired connection.

The database (250) stores and maintains any information necessary to provide remittance services. In this specification, the database (250) can store personal information, such as basic personal information (such as name, gender, nationality, and birthday), customer identifiers for remittance services (eg, service accounts, phone numbers, and Email address), account information registered in the remittance service, history of remittances and/or collections, electronic money using remittance services, and history of related electronic money. In Figure 2, the database (250) is included in the money transfer system (200), but (or), the database (250) can be used as an external database contained in another separate system.

The processing unit (210) can perform basic operations, logic operations, and input/output operations of the money transfer system (200) to process instructions of the computer program. The instructions are provided to the processing unit (210) via the bus (220), via the memory (240) or the network interface (230). The processing unit (210) may constitute a code for executing the registration unit (211), the money transfer processing unit (212), and the reception processing unit (213). Additionally, the code can be stored in a recording device, such as a memory (240).

The registration unit (211), the money transfer processing unit (212), and the reception processing unit (213) may constitute a remittance method operation to be described later.

3 is a flow chart of a method of registering a money transfer account, in accordance with an embodiment. The method shown in Fig. 3 can be performed by the registration unit (211) shown in Fig. 2.

At step (301), the registration unit (211) may perform self-authentication for the client requesting a service appointment. In this specification, the registration unit (211) can perform self-validation via at least one recognized verification method, such as mobile phone verification, real name verification, identity verification, and automatic response system (ARS, Automatic Response System) verification.

Figure 4 illustrates a self-validation of the registration unit (211), showing a self-validation screen (400) as a client interface at the user terminal. For example, the self-validation screen (400) is related to mobile phone authentication and may include a customer interface for requesting the customer to enter personal information for mobile phone verification. The registration unit (211) can then perform mobile phone verification (eg, name, gender, nationality, birthday, mobile phone number, and mobile communication operator) based on the personal information entered through the self-verification screen (400) to identify the customer.

At step (302, 303), the registration unit (211) may decide whether the client verification is successful based on the self-verification result using the mobile phone verification, and if the client verification fails, the registration unit (211) may restrict the registration of the money transfer service.

At step (302, 304), when it is determined that the client authentication is successful, the registration unit (211) may perform a password registration for registering the client password. In this manual, the password is verified during the remittance or payment using the registered account, which will be described later.

Figure 5 schematically illustrates the password registration associated with the registration unit (211), displayed on the user terminal as a password input screen (500) for the customer interface. For example, the password entry screen (500) can include a customer interface to request the customer to enter a verification password during remittance, payment, and the like. The password entry screen (500) can include a keypad area and a character input area for inputting characters (e.g., numbers) selected through the keyboard. At this time, when the password input screen (500) is displayed, the keypad area can be automatically displayed, and can constitute a security keypad, wherein the configuration of the keyboard can be changed each time or the actual input value can be changed to a random number.

The registration unit (211) can temporarily store the characters that are treated as passwords through the password input screen (500). In addition, the client can be requested to re-enter the same character at least once, and the characters are registered as passwords only when the same character is input. .

In addition, the registration unit (211) may perform a terms and conditions agreement procedure for the customer to use the money transfer service before or after the password registration. In this specification, the terms and conditions may include all terms and conditions required to use the remittance service, such as the terms and conditions of the members of the remittance service, the terms and conditions of the electronic financial transaction, the consent to collect and use personal information, and the payment Information to the third party's consent.

At steps (305-308), the registration unit (211) may perform an account registration for registering an account used during the transfer. For example, the registration unit (211) can register only one account per person and change the account, and can register a new account after deleting the existing registered account. As another example, the registration unit (211) does not limit the number of registered accounts, and can register a plurality of accounts per person.

For example, the registration unit (211) may perform account registration by using account information input, a withdrawal agreement for entering an account, test deposit verification, and registration completion. Figure 6 schematically illustrates an account registration with respect to the registration unit (211), displayed on the user terminal as an account input screen (600). For example, the account entry screen (600) can include a customer interface for requesting customer input of account information, such as bank and account numbers. When requesting the customer to select the bank's customer interface, when selecting a bank, the selected bank can be displayed in a selected state. When entering an account number, if you enter a character other than a number, the account input screen (600) can display a reminder message (for example, "Please enter only numbers"). The customer's basic personal information (name, date of birth, or mobile phone number) required during account registration is not individually received and can be pre-registered in the remittance service or other services related to the money transfer service (for example, the portal containing the money transfer service) Basic personal information. At this point, basic personal information is automatically displayed on the account entry screen (600).

The registration unit (211) can perform an account name confirmation of the input account, so that when the account information is input, only the account opened in the name of the customer is registered. When the input account is not based on the customer's name, an alert message can be provided based on the account registration failure (for example, "Account is not your name and registration failed").

At step (305), when the client requests registration of the input account, the registration unit (211) may use the ARS to execute the automatic withdrawal protocol program. Referring to Figures 6 and 7, when the customer enters account information on the account input screen (600) and then selects a registration button (601), the registration unit (211) can provide an automatic withdrawal protocol via the ARS guide screen (710). ARS call guide. When a customer requests an ARS guide via the ARS Guide Screen (710), the ARS call can make a customer mobile phone call based on the customer's personal information. In this manual, when a customer responds to an ARS call, a guide to the automatic withdrawal agreement for entering the account can be provided.

In step (306), when it is determined that the customer does not agree to perform automatic withdrawal through the ARS call, in step (307), the registration unit (211) may provide a reminder message according to the account registration failure (for example, "because there is no agreement for automatic withdrawal" registration failed"). Meanwhile, in step (306), when it is determined that the client agrees to perform automatic withdrawal through the ARS call, in step (308), the registration unit (211) may register the input account as the remittance account used during the remittance, and according to whether the account is registered or not Complete to provide a reminder message (for example, "Agree to Automated Withdrawal to Complete Registration"). In this specification, the registration unit (211) can conform to and register the personal information entered into the account and the customer identifier containing the customer.

The registration unit (211) can perform verification using a test deposit for entering an account verification. For example, the registration unit (211) may verify the input account during the test deposit using the remittance ID number or some information (eg, transfer amount, transfer date, or remark) included in the deposit details of the input account. As another example, the registration unit (211) may utilize account information generated when the test deposit is completed to perform account verification. For example, the registration unit (211) may use the remittance ID number arbitrarily generated by the test deposit regarding the input account as the remitter information, thereby remitting the specific amount (for example, 1 Korean won) to the input account, and then using the remittance ID. Number to verify the entry into the account. Customers can check the deposit details by entering the SMS or ARS of the account bank and use the information on the deposit details to verify the entry. Information about transfer notes or individual jobs can be used for account verification as described above, but any other information can be used.

Figure 8 illustrates a test deposit verification relating to the registration unit (211), showing an account verification screen (810, 820) as a customer interface at the user terminal. For example, the account verification screen (810) can include a customer interface for requesting the customer to enter the money transfer ID number checked by the customer from the test deposit details of the input account. As another example, the account verification screen (820) can include a customer interface for requesting the customer to enter a test deposit amount to deposit in the input account. Therefore, the registration unit (211) can register the input account only when the remittance ID number checked by the customer meets the remittance ID number generated during the test deposit period, or when the test deposit amount entered by the customer meets the amount remitted during the test deposit period. Become a remittance account. At this time, the registration unit (211) can guide the client through the account verification screen (810, 820) for checking the test deposit details (for example, ARS phone number), and when input within a certain time (for example, within 24 hours) When you transfer the ID number, you can register the input account as a remittance account, and after a certain time, you can cancel the account registration.

9 and 10 are flow diagrams of a method of remittance operations in accordance with an embodiment. The operation of the money transfer operation method according to a specific embodiment can be performed using the money transfer processing unit (212) shown in FIG. 2.

At step (901), the money transfer processing unit (212) may determine whether to register the customer's money transfer account when receiving the service request for the money transfer from the user terminal.

When it is determined that the remittance account is not registered, the remittance processing unit (212) may request the registration unit (211) to perform account registration so that the customer first registers the remittance account.

In steps (903) through (907), when it is determined that the money transfer account has been registered, the money transfer processing unit (212) may perform a payee selection to receive the payee identifier and the real name for the money transfer from the customer. Examples of identifiers include a service account, a phone number, and an email address, and may include any information for specifying a payee. In the present specification, the real name may be the real name of the customer, but a specific embodiment is not limited thereto, and may be the name actually used in the money transfer service, for example, the name of the money transfer service is registered in advance during the reservation.

For example, at step (904), the money transfer processing unit (212) may utilize the payee's service account to receive the payee's selection, such as a customer ID registered at the money transfer service, or another interaction with the money transfer service. The customer ID registered by the remittance service. As another example, at step (905), the money transfer processing unit (212) can utilize the payee's mobile phone number to receive the payee's selection. At step (906), the money transfer processing unit (212) may also receive the payee's real name after selecting the payee using the service account or mobile phone number. At this time, the real name of the payee can be received via the direct input method.

When the payee is selected using the service account and the mobile phone number, the money transfer processing unit (212) can directly receive the service account or mobile phone number via the direct input method. Alternatively, the remittance processing unit (212) may display a contact list stored in the user terminal and receive a service account or mobile phone number from the contact list to select the payee. Alternatively, the remittance processing unit (212) can display the contact list stored in the individual application (hereinafter referred to as the contact list application) storing the contact list by connecting the contact list application, and then receiving the contact list selection. The service account or mobile phone number of the payer.

As another example, at step (907), the money transfer processing unit (212) may display a list of remittance friends of the most recent remittance history or a list of remittance friends set by the customer, and then specify the payee selected in the remittance friend list. In order to prepare a list of remittance friends, the registration unit (211) can automatically register the current remittance or deposit customer's personnel service account and/or mobile phone number, and the real name as a remittance friend, or can directly input the pre-registration environment into the customer's account. Personnel service account and/or mobile phone number, registered with real name to become a remittance friend. At this time, when the money transfer processing unit (212) uses the money transfer friend list to receive the payee's choice, the payee's real name is included in the money transfer friend list, so the job of receiving the real name may not be performed.

Fig. 11 is a view schematically showing a remittance operation program for displaying the remittance processing unit (212), and displaying a remittance information input screen (1100) as a client interface on the user terminal. For example, the remittance information input screen (1100) may include a customer interface for requesting the customer to input remittance information, including the payee, the amount of the remittance, and the remittance related information. The Remittance Information Entry Screen (1100) can at least partially display information about the customer's registered remittance account. In addition, the remittance information input screen (1100) may further include a customer interface for requesting the customer to agree to the third party's personal information terms. The remittance processing unit (212) may provide a payee selection page if the customer selects an interface for selecting a payee from the remittance information input screen (1100).

Figure 12 is a schematic illustration of a money transfer operating program for the money transfer processing unit (212), as a screen for selecting a payee's payee selection screen (1200). For example, the payee selection screen (1200) can include a first customer interface that utilizes at least one identifier (such as a service account, a mobile phone number, and an email address) to select a payee.

When the first customer interface is selected on the payee selection screen (1200), the money transfer processing unit (212) can provide an input page (1310, 1320) for entering the real name, along with any identifier, such as a service account, action The phone number and email address are shown in Figure 13.

When the first customer interface is selected on the payee selection screen (1200), the money transfer processing unit (212) can provide a selection page (1410) containing the contacts stored in the user terminal or by accessing the stored contact list. A contact list obtained by the manifest application; then, an input page (1420) is provided for entering the payee's real name when the payee is selected on the selection page (1410), as shown in FIG.

The remittance processing unit (212) can provide an input page (1310, 1320), which can input the payee identifier and the real name in the remittance environment of the web browser, as shown in FIG. 13; and provide a contact list. The selection page (1410) interacts with the contact list as shown in FIG. 14 in a remittance environment implemented by the action-specific application by considering the service providing environment.

Referring to FIG. 12, when having a remittance friend list, the payee selection screen (1200) may further include a second customer interface for selecting a payee using the remittance friend list. The payee selects the list of remittance friends on the screen (1200) to display the facial image, service account, and real name of the person.

After the payee is selected, the remittance processing unit (212) can display information about the selected payee by the customer on the remittance information input screen (1500), as shown in FIG. In this specification, the payee information displayed on the remittance information input screen (1500) may include the customer entering the real name of the payee, corresponding to how the payee's identifier (service account, mobile phone number, email address) is selected. , name, etc.).

At step (908), the remittance processing unit (212) may request the customer to enter the remittance amount, and thus, the remittance amount input by the customer via the remittance information input screen (1500) may be received. For example, the remittance information input screen (1500) may include: an input area that uses a Korean currency unit to directly input the amount; and an amount button to automatically input a specific amount.

Some programs after the money transfer operation program shown in Fig. 9 will now be described with reference to FIG.

After selecting the payee, entering the remittance amount and receiving the request for remittance amount from the customer, in step (1009), the remittance processing unit (212) may determine the remittance limit of the customer during each unit period. For example, the remittance limit per unit period can be automatically set to a preset value, or can be directly set by the customer, and for example, the remittance limit can be set to 500,000 won per ID per day. As another example, the remittance limit per unit period may be set differently based on whether the customer is a minor. For example, an adult's remittance limit can be 5,000,000 won per ID per day, and a minor's remittance limit can be 100,000 won per ID per day. Together with the remittance limit per unit period, the minimum remittance limit can also be preset to a specific amount, for example, 1,000 won.

In step (1010), the remittance processing unit (212) may increase the remittance amount recently requested to be remitted, and the amount of the existing remittance remitted during the unit time period, and may stop the remittance operation when the increase amount exceeds the remittance limit per unit period And provide a reminder message to exceed the limit.

In step (1011), the remittance processing unit (212) may increase the remittance amount recently requested to be remitted and the remittance amount remitted during the unit time period, and may check the remittance account when the increase amount does not exceed the remittance limit per unit period. The original account balance. The balance limit of the original account can be set automatically or directly by the customer, and for example, the balance limit during the remittance period can be set to 2,000,000 won.

In step (1010), the remittance processing unit (212) may increase the remittance amount and the remittance remittance amount that are recently requested to be remitted, and may provide an alert message to inform the over quota when the increase amount exceeds the balance limit of the original account.

The remittance processing unit (212) may increase the remittance amount and the remittance remittance amount that are recently requested to be remitted, and when the increased amount does not exceed the balance limit of the original account, in step (1012), the client may be requested to input the verification password.

In step (1013), the remittance processing unit (212) may compare the input password entered by the customer with the pre-registered password, and if the entered password and the pre-registered password do not match each other, an alert message may be provided to inform the password error.

At step (1014), if the entered password and the pre-registered password match each other, the remittance processing unit (212) may check the balance of the remittance account.

When the remittance amount recently requested to be remitted exceeds the remittance amount balance, in step (1015), the remittance processing unit (212) provides a reminder message to inform that the balance is insufficient, and if the remittance amount recently requested to be remitted does not exceed the remittance amount balance, the remittance The processing unit (212) can transmit the remittance details regarding the remittance amount to the selected payee of the customer.

In step (1016, 1017), the remittance processing unit (212) provides cancellation of the remittance function before the payee receives the remittance amount for the remittance remittance, and if the customer requests cancellation of the remittance remittance, the remittance processing unit (212) may cancel the remittance payment. money transfer.

In step (1018, 1017), when the payee does not accept the amount of the customer's remittance within the remittance receiving time, the remittance processing unit (212) may cancel the remittance after the remittance acceptance period. The remittance acceptance period is the period during which the payee receives the remittance amount and can be set to 3 days. In this manual, the remittance acceptance period can be automatically set to a preset value or set directly by the remitter's customer.

In step (1019, 1020, 1017), the remittance processing unit (212) may determine whether the real name and the identifier entered by the customer meet the actual real name of the corresponding identifier, and if the real name entered is different from the actual real name, A reminder message can be provided to inform the real name and cancel the remittance.

The remittance processing unit (212) compares the identifier of the payee included in the remittance information having the identifier with the real name included in the personal information registered in the database to check the real name, and utilizes the service account or action When the phone number is selected as the payee, the real name can be checked, and when the payee list is selected in the remittance friend list, the real name may not be checked.

When the payee requests to receive the remittance amount remitted by the customer within the remittance acceptance period, the remittance processing unit (212) may determine whether the real name and the actual real name included in the remittance information match each other, and when the real name and the actual real name are in each other When it is met, transfer the remittance amount to the payee to complete the remittance operation.

In step (1021-1023), when the remittance is canceled, the remittance processing unit (212) may determine whether there is a problem with the original account of the customer, and if there is no problem, return the remittance amount to the original account, and if there is a problem, return the remitted remittance amount to the preset. Refund account.

16 is a flow chart of a method of receiving money in accordance with an embodiment. The operation of the money transfer receiving method according to the present embodiment can be performed by the receiving processing unit (213) shown in FIG. 2.

At step (1601), at the remitter receiving the remittance details, the receiving processing unit (213) may provide the remittance details to the customer, together with the remittance receipt notification. For example, the receiving processing unit (213) may transmit a text message including the remittance receiving details (remitter information, remittance date, and remittance amount) to the user terminal through a text service (for example, SMS) regarding the remittance of the target customer. As another example, the receiving processing unit (213) may display the remittance receipt details via a customer notification page regarding the remittance service of the target customer remittance. As another example, the receiving processing unit (213) can perform the two methods of the aforementioned notification of remittance reception. The remittance receipt notification may include a remittance receipt detail screen linked to the remittance amount received by the remitter.

In addition, the receiving processing unit (213) may determine a method of notifying the receipt of the money transfer based on how the remitter selects the payee. For example, when the remitter uses the mobile phone number to select the payee, the remittance can be received through a text message. When the remitter uses the service account to select the payee, the remittance can be notified through the notification page of the remittance service, and when The remitter uses the remittance friend list to select the payee, and can notify the remittance reception through both the text message and the notification message.

The receiving processing unit (213) can provide a remittance receiving notification through the text message, even if the remitter selects the customer as the payee is not a member of the remittance service (or a remittance service interactive service), and can additionally perform the program required for remittance reception ( Includes member registration procedures and terms and conditions agreement procedures for the use of remittance services for remittance reception.

In step (1602, 1603), the receiving processing unit (213) may cancel the remittance when receiving the remittance cancellation request from the remitter before the customer accepts the remittance. At this time, the text service and/or notification page of the remittance service may be accessed. To provide a customer remittance cancellation notice to inform the customer that the remittance has cancelled the remittance.

In step (1604, 1603), when the customer does not accept the remittance of the remittance during the remittance acceptance period, the receiving processing unit (213) may cancel the remittance and provide a remittance cancellation notification through the text service and/or notification page of the remittance service. To the customer, to inform the customer that the remittance was cancelled due to overdue.

In steps (1605, 1606, 1603), the receiving processing unit (213) may determine whether the actual real name of the customer receiving the remittance receiving notification and the real name included in the remittance remittance details are consistent with each other, and when the actual real name and the real name are actual Different from each other, you can provide a reminder message to tell your real name and cancel the remittance. When the remitter uses the service account or mobile phone number to select the payee, the actual real name will be compared with the real name, and when the remitter selects the payee in the remittance friend list, no comparison will be made.

At step (1607), when the client requests to receive the remittance amount from the remitter within the remittance acceptance period, the reception processing unit (213) executes a program for selecting the remittance receiving method, and normally processes the real name verification.

Figure 17 is a diagrammatic view showing a remittance reception detail screen (1700) displayed on the user terminal as a client interface by the remittance receiving program executed by the receiving processing unit (213). For example, the Remittance Receiving Detail Screen (1700) can display the remittance details of the remitter (eg, the name of the remitter, the date of the remittance, the amount of the remittance, and the remittance related information), and includes a customer interface to request the customer to choose to receive the remitter. The method of receiving remittances for the remittance amount. The customer can then check the remittance details displayed on the Remittance Details screen (1700) and select the remittance method.

Examples of the remittance receiving method include a method of receiving a remittance through a bank account, and a receiving remittance method in the form of an electronic money (for example, a point) relating to the remittance service, but is not limited thereto. In order to receive the remittance amount through the bank account, the remittance service is required to register the account, and in order to receive the remittance amount (such as points) in the form of electronic money, no bank account can be used for remittance.

In step (1608, 1609), when the client selects the method of receiving the remittance through the bank account as the remittance receiving method, the receiving processing unit (213) may determine whether the remittance service registers the customer's bank account.

In step (1610, 1611), when the remittance service does not register the customer's bank account number, the receiving processing unit (213) may request the client to perform account registration, and when the client does not perform the account registration, provide an alert message to inform the customer of the remittance receiving error. At this time, when the client does not perform account registration, the receiving processing unit (213) may delay the remittance reception or request the client to reselect the remittance receiving method.

In step (1609, 1610, 1612), when the money transfer service has registered the customer's bank account or registered the new bank account through the account number, the receiving processing unit (213) may determine whether the registered account is in a normal state. At this time, when the registered account is not in the normal state of receiving the remittance, the receiving processing unit (213) may provide an alert message to inform the customer of the remittance reception error. When the registered account is in a normal state, the receiving processing unit (213) may deposit the remittance amount of the remitter in the registered account to complete the remittance receiving process.

At step (1613, 1614), when the customer selects the payment method of the electronic money as the remittance receiving method, the receiving processing unit (213) may determine the balance limit of the customer's electronic money. The balance limit can be set automatically or directly by the customer, and for example, the balance limit can be 2,000,000 won.

The receiving processing unit (213) can increase the remittance amount remitted by the remitter and the current balance of the customer's electronic money, and when the increased amount does not exceed the balance limit, the remittance amount can be converted into electronic money and the electronic money can be remitted to the customer to complete the remittance. Receive the program.

The receiving processing unit (213) can perform the client authentication using the verification password registered in the money transfer service, but the client cannot be authenticated using the password during the money transfer receiving process.

Meanwhile, when the increased amount exceeds the balance limit, the receiving processing unit (213) may provide an alert message to inform the customer of the remittance reception error. At this time, when the added amount exceeds the balance limit, the receiving processing unit (213) may delay the remittance reception or request the customer to reselect the remittance receiving method.

As mentioned above, the remittance amount remitted by the remitter is completely received through the bank account or in the form of electronic money, but the specific embodiment is not limited thereto, and the remittance receiving method may be changed or expanded. For example, the amount of the remittance can be split and received in the form of a bank account and electronic money. Therefore, the customer can selectively split the remittance amount and receive certain remittance amounts from the bank account and the remaining remittance amount in the form of electronic money.

The aforementioned remittance system (200) can provide a payment environment from the remitter to the bank account, allowing the customer to receive the remittance amount or electronic money, and then immediately use the remittance money as the settlement fee for online e-commerce (for example, online shopping).

The foregoing remittance method may include more or less operations based on a detailed description of the remittance system with reference to FIGS. 1 through 17. Further, at least two operations may be combined or the order of operations may be changed.

The screens shown in Figures 4 to 8, 11 to 15, and 17 are merely examples for convenience of description, and thus the configuration and sequence of the screen can be changed.

18 is a block diagram of the internal structure of a computer system (1800) in accordance with an embodiment. The computer system (1800) can include at least one processor (1810), a memory (1820), a peripheral interface (1830), an input/output (I/O, Input/Output) subsystem (1840), and a A power circuit (1850), and a communication circuit (1860). In this specification, the computer system (1800) can be a user terminal.

The memory (1820) may include a high speed random access memory, a magnetic disk, a static random access memory (SRAM), a dynamic random access memory (DRAM), a read only memory (ROM), a flash memory, Or non-volatile memory. The memory (1820) may include a software module, an instruction set, or other various types of data required to operate the computer system (1800). At this point, the processor (1810) can control another component to access the memory (1820), such as the processor (1810) or the peripheral interface (1830).

The peripheral interface (1830) can be connected to the input and/or output peripheral devices of the computer system (1800) to the processor (1810) and the memory (1820). The processor (1810) can execute a software module or a set of instructions stored in the memory (1820) to perform various functions and processing of the computer system (1800).

The I/O subsystem (1840) can connect various I/O peripherals to the peripheral interface (1830). For example, the I/O subsystem (1840) can include a controller for combining the peripheral interface (1830) to peripheral devices such as a monitor, keyboard, mouse, printer, touch screen, or sensor. According to another embodiment, the I/O peripheral device can be connected to the peripheral interface (1830) without having to use the I/O subsystem (1840).

The power circuit (1850) can supply power to all or part of the computer system (1800) components. For example, the power circuit (1850) can include a power management system, at least one power source, such as a battery or alternating current (AC), charging system, power failure detection circuit, power converter or inverter, power status indicator And other components used to generate, manage, and distribute power.

The communication circuit (1860) allows the computer system (1800) to communicate with another computer system using at least one external port. Alternatively, as previously described, the communication circuit (1860) may include a radio frequency (RF) circuit to transmit and receive RF signals, also referred to as electromagnetic signals, by the computer system (1800) communicating with other computer systems.

The computer system (1800) shown in Figure 18 is only an example, and the computer system (1800) may include more or less components as shown in Figure 18, or at least two components of the component computer system (1800). For example, the computer system (1800) of the communication terminal for the mobile environment may further include a touch screen or a sensor, and the components shown in FIG. 18, and the communication circuit (1860) may include various types of communication. RF circuits such as wireless local area network (WiFi), third generation wireless communication technology (3G), long term evolution (LTE), Bluetooth, near field communication (NFC) and wireless sensing networks (Zigbee) . The computer system (1800) includes components that may include hardware, software, or a combination of hardware and software, including integrated circuitry that is particularly related to at least one signal processing or an application.

As described above, according to a specific embodiment, by using the payee's service account and the real name to remit the remittance amount, the remittance service can be used to make a direct remittance between individuals, even if the payee's account number is not known. Further, according to a specific embodiment, when the payee is selected, the remittance payee can be conveniently entered by providing a list of remittance friends of the most recent remittance history set by the customer. Moreover, according to a specific embodiment, when the payee is selected, it is convenient to input the payee of the money transfer by connecting the application by providing a contact list stored in the user terminal or stored in the application's contact list. Moreover, according to a specific embodiment, the amount received from another person is received not only by the bank account, but also by electronic money, such as points, so the amount may not be received using the account registered in the money transfer service. .

Program instructions executable by various computer systems may be embodied in accordance with one or more embodiments of the method and recorded on a non-transitory computer readable recording medium.

A program according to a specific embodiment may constitute a PC-based program or a mobile terminal-specific application. The money transfer service related application according to a specific embodiment may be implemented as a stand-alone program, or may be like some applications (eg, an portal service application or a search service application) operating in a specific application. The application is implemented in-house.

Additionally, when an application for a server system providing a money transfer service is used to control a user terminal, a method in accordance with an embodiment may be performed. For example, the application can execute at least one job that constitutes at least one feature described in this specification. In addition, the application can be installed on the user terminal through the file provided by the file distribution system. For example, the file distribution system can include a file transfer unit for transferring files according to a request from a user terminal.

The apparatus described in this specification can be embodied as at least one hardware component, at least one software component, and/or a combination of a hardware and a software component. For example, devices and components in accordance with one or more embodiments can be implemented by at least one general purpose computer or special purpose computer (such as a processor, controller, Arithmetic Logic Unit (ALU)), digital signal. A processor, a microcomputer, a Field Programmable Gate Array (FPGA), a Programmable Logic Unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. A processing device can execute an operating system (OS) and at least one software application executed on the OS. In addition, the operating device can access, store, manipulate, process, and generate data in response to execution of the software. For ease of description, the present description uses a processing device, but it should be understood by those skilled in the art that the processing device can include a plurality of processing elements and/or a plurality of types of processing elements. For example, a processing device can include a plurality of processors or a processor, and a controller. Alternatively, another processing configuration can be used, such as a parallel processor.

The software may include computer programs, code, program instructions, or a combination thereof, and may constitute a processing device to operate as desired, or the processing device may be controlled independently or entirely. The software and/or materials may be permanently or temporarily implemented by any of the following types: machines, components, physical devices, virtual devices, computer storage media or devices, or signal waveforms interpreted by the processing device; or instructions for processing the device or data. The software can be distributed over a computer system connected via a network and can be stored or executed in a decentralized manner. The software and materials can be stored on at least one non-transitory computer readable recording medium.

The foregoing method can record a non-transitory computer readable recording medium realized by executing a computer program using various computers. The non-transitory computer readable recording medium can include at least one of a program command, a data file, and a data structure. Program commands recorded on non-transitory computer readable recording media can be specially designed by those skilled in the computer software field. Examples of the non-transitory computer readable recording medium include read only memory (ROM), random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like. Examples of computer commands include mechanical code compiled by a compiler, and a high-level programming language executed by a computer that utilizes an interpreter. The hardware device can be configured to operate as at least one software module to perform the methods, or vice versa.

It should be understood that the specific embodiments described herein are illustrative and not restrictive. Descriptions of features or aspects in each particular embodiment are generally considered as other similar features or aspects that may be used in other specific embodiments.

Although one or more specific embodiments have been described with reference to the drawings, it is understood that various modifications of the form and details may be made without departing from the spirit and scope of the inventive concept as defined in the appended claims. .

10‧‧‧Network
100‧‧‧Remittance system
101‧‧‧User terminal
102‧‧‧User terminal
103‧‧‧Bank server
200‧‧‧Remittance system
210‧‧‧Processing unit
211‧‧‧Registration unit
212‧‧‧Remittance Processing Unit
213‧‧‧Receive processing unit
220‧‧‧ busbar
230‧‧‧Internet interface
240‧‧‧ memory
241‧‧‧ operating system
242‧‧‧Remittance routine
250‧‧‧Database
301~308‧‧‧Steps
400‧‧‧ self-verification screen
500‧‧‧ password input screen
600‧‧‧ account input screen
601‧‧‧ Registration button
710‧‧‧ARS Guide Screen
810‧‧‧ account verification screen
820‧‧‧ account verification screen
901~908‧‧‧Steps
1009~1014‧‧‧Steps
1016~1023‧‧‧Steps
1100‧‧‧Remittance information input screen
1200‧‧‧ Payee chooses the screen
1310‧‧‧ Input page
1320‧‧‧ Input page
1410‧‧‧Select page
1420‧‧‧ Input page
1500‧‧‧Remittance information input screen
1601~1614‧‧‧Steps
1700‧‧‧Remittance reception details screen
1800‧‧‧ computer system
1810‧‧‧ processor
1820‧‧‧ memory
1830‧‧‧ peripheral interface
1840‧‧‧Input/Output Subsystem
1850‧‧‧Power circuit
1860‧‧‧Communication circuit

These and/or other aspects will become more apparent from the following detailed description of the embodiments of the drawings, wherein: FIG. 1 is a diagram for describing an example of a money transfer service environment in accordance with an embodiment. 2 is a block diagram of an internal structure of a money transfer system in accordance with an embodiment; FIG. 3 is a flow chart of a method for registering a money transfer account in accordance with an embodiment; FIGS. 4 through 8 schematically illustrate an embodiment in accordance with an embodiment of the present invention A customer interface screen for account registration; Figures 9 and 10 are flow diagrams of a method of money transfer operations in accordance with an embodiment; Figures 11 through 15 illustrate a client interface screen relating to a money transfer program in accordance with an embodiment; A flow chart of a method of receiving money in accordance with an embodiment. Figure 17 is a schematic illustration of a customer interface screen relating to a money transfer receiving program in accordance with an embodiment; Figure 18 is a block diagram of the internal structure of a computer system in accordance with an embodiment.

212‧‧‧Remittance Processing Unit

901~908‧‧‧Steps

Claims (22)

A remittance method implemented in a computer, the remittance method comprising: receiving, from a user terminal, a remittance information including a remittance amount, a payee name and a service account of a remittance service as a remittance information of the remittance object; and utilizing the service After the account and the payee name are checked for the payee name used in the money transfer service, the money transfer information is transmitted to the payee terminal using the service account. The remittance method of claim 1, further comprising managing a service account and a payee name as a remittance friend list, having a remittance history about the user terminal, wherein the receiving the job comprises: providing the remittance friend list to the a user terminal; and receiving, from the user terminal, a selection of a particular object included in the money transfer friend list. The remittance method of claim 1, wherein the receiving the job comprises: accessing the contact list to provide a contact list stored in the user terminal when the payee is selected; and receiving from the user terminal The contact list contains a selection of specific objects. The remittance method of claim 1, wherein the receiving the job comprises: providing a contact list of the user terminal by connecting an application managing the contact list when the payee is selected; and from the user terminal Receive a selection of the specific object contained in the contact list. The method of remittance according to claim 1, wherein the payee's name is checked by comparing the name of the payee as the payee information with the name registered in the service account. The remittance method of claim 1, wherein the transmission operation comprises transmitting a notification message containing the remittance information through at least one of a notification page of the remittance service and a text service (SMS). The method of remittance according to claim 1 is: receiving a request from the payee terminal to accept the remittance information; and transmitting the remittance amount through the service account according to the request. The method of remittance according to claim 7, wherein the remittance operation is performed by remitring the remittance amount to an account relating to the service account; converting the remittance amount into electronic money relating to the service account; or , split the remittance amount and remit part of the remittance amount to the account; and convert the remaining remittance amount into electronic money. The remittance method of claim 7, wherein the receiving the receiving request comprises providing a menu to the payee terminal for selecting a method for receiving the remittance amount, and then, together with the accepting request, from the payee terminal The machine receives the selection of the particular receiving method contained in the menu. The method of remittance according to claim 1 further includes canceling the remittance that is not accepted by the payee according to the cancellation request of the user terminal. The method of remittance described in claim 1 further includes canceling the remittance if the payee does not accept the remittance within a certain time. The method of remittance according to claim 1 further includes registering an account of the client, wherein the registration operation comprises: processing a deposit test of the account for account verification; and verifying the account by using account deposit operation information according to the test deposit. A non-transitory computer readable recording medium, comprising computer system instructions for performing a money transfer operation, wherein the instructions use a money transfer method to control the computer system, including: receiving remittance information from a user terminal, including the amount of the remittance and the remittance The payee name and service account of the remittance service of the subject payee information; and using the service account and the payee name to check the payee name used in the remittance service, using the service account to remit the remittance information Transfer to the payee terminal. A money transfer system comprising: a memory loaded with at least one program; and at least one processor, wherein the at least one processor is controlled according to the at least one program to perform the following: receiving a remittance from a user terminal The remittance information of the amount, the name and service account of the payee related to the remittance service as the remittance information of the remittance; and the use of the service account and the payee name to check the name of the payee used in the remittance service After that, the remittance information is transmitted to the payee terminal by using the service account. The money transfer system of claim 14, wherein the at least one processor is operative to perform the following according to the control of the at least one program: managing a service account and a payee name as a list of remittance friends, having a user terminal The remittance history of the machine, wherein the receiving operation includes providing the remittance friend list to the user terminal, and then receiving, from the user terminal, a selection of a specific object included in the remittance friend list. The money transfer system of claim 14, wherein the receiving job comprises: accessing the contact list stored at the user terminal when the payee is selected; or connecting to manage the user terminal An application that contacts the list; and then receives a selection of the particular object contained in the contact list from the user terminal to provide the contact list to the user terminal. The money transfer system of claim 14, wherein the payee name is checked by comparing the received payee name as the payee information with the name registered in the service account to verify the payee. The remittance system of claim 14, wherein the at least one processor is operative to perform the following according to the control of the at least one program: receiving an acceptance request for the remittance information from the payee terminal; and receiving the request according to the The remittance amount is remitted through the service account. The remittance system of claim 18, wherein the remittance operation is performed by remitring the remittance amount to an account relating to the service account; converting the remittance amount into electronic money relating to the service account; or , split the remittance amount, and remit part of the remittance amount to the account, and convert the remaining remittance amount into electronic money. The remittance system of claim 18, wherein the receiving an acceptance request comprises providing a menu to the payee terminal for selecting a method of receiving the remittance amount and then receiving from the payee terminal a particular one included in the menu The selection of the receiving method, along with the accepting request. The money transfer system of claim 14, wherein the at least one processor is operative to perform the following according to the at least one program: according to the cancellation request of the user terminal, or if the payee does not accept within a certain time Remittance, cancel the remittance that is not accepted by the payee. The remittance system of claim 14, wherein the at least one processor is operative to register an account related to the customer according to the control of the at least one program, wherein the registration operation comprises: processing a deposit test of the account for account verification; And use the account deposit job information based on the test deposit to verify the account.