JP2023141166A - Remittance system, remittance method and program enabling remittance by account identifier set by recipient instead of account number - Google Patents

Abstract

To provide a remittance system, remittance method and program that enable a user to set an account identifier substituting for an account number when making a remittance request, and enable making the remittance to the designated account identifier.SOLUTION: In a remittance system, a remittance server 100 comprises: account identifier setting means 101; public identifier storage means 102; non-public identifier storage means 103; remittance destination identification means 104; account identifier search means 105; and SNS information acquisition means 106. The account identifier setting means 101 is configured to make a recipient input a combination of an arbitrary character string serving as an account identifier instead of an account number, and designate the input character string as a non-public identifier disclosing the input character string without restricting a disclosure destination, and/or a non-public identifier disclosing the input character string only to a restricted disclosure destination. Remittance implementation means 201 is configured to search for the public identifier or non-public identifier to uniquely identify the account number of the recipient, and implement a remittance.SELECTED DRAWING: Figure 2

Description

The present invention relates to a remittance system, remittance method, and program that allow remittance without specifying an account number.

Conventionally, when transferring money between accounts, the receiver can only confirm the name of the sender, and cannot confirm the purpose of the transfer. Additionally, when requesting a transfer to an account, it was necessary to provide personal information such as the store number and account number. Therefore, systems are known that allow remittance without knowing the account number of the recipient.

For example, Patent Document 1 discloses a financial transaction service system that allows bank transfer using a mobile phone number or an e-mail address corresponding to the mobile phone number instead of an account number. In addition, Patent Document 2 describes a proxy account that can be linked to an ID specified by the user so that the same account can be used even if the transfer destination is different, and that can be used directly for transfer processing to an account already opened at a financial institution. A proxy account management device, etc. to be opened is disclosed.

Japanese Patent Application Publication No. 2007-317173 Japanese Patent Application Publication No. 2009-110371

However, in the invention described in the above-mentioned patent document, it was not possible to use an account identifier freely selected by the user. That is, in the invention described in Patent Document 1, the account identifier is limited to a mobile phone number or email address, and in the invention described in Patent Document 2, the proxy account identifier is generated by the system by automatic numbering. Therefore, users cannot create account identifiers themselves.

Therefore, in consideration of the above-mentioned problems, the present invention allows a user to arbitrarily set an account identifier in place of the store number and account number when making a remittance request, and the remittance side to search for the account identifier. The purpose is to provide a remittance system that allows remittances to be made by uniquely identifying a remittance destination.

In order to solve the above problems, the present invention provides the following solution.

(1) A remittance system that allows the sender to send money without specifying the recipient's account number,
having the recipient input a combination of arbitrary character strings that will serve as an account identifier instead of the account number, and using the input character string as a public identifier to be made public without limiting the disclosure destination; and/or An account identifier setting means for setting the recipient as a private identifier to be disclosed only to a limited number of public persons, and a means for uniquely identifying the account number of the recipient by searching the public identifier or the private identifier. , and remittance execution means for executing the remittance.

(2) In the configuration of (1) above, the arbitrary character string is determined to have "meaning" based on a predetermined criterion.

(3) In the configuration of (1) or (2) above, when the arbitrary character string is used as the nickname of the recipient's account, the user group that includes the recipient or the user group that includes the remitter It is characterized by checking whether the nickname is unique based on shared information of the nickname, or displaying a new selectable nickname from the shared information if the nickname is not unique. do.

(4) In the configuration of (1) or (2) above, when the arbitrary character string is used as the nickname of the recipient's account, a user group that includes only the recipient or a user group that includes only the remitter , or checking whether the nickname is unique based on sharing information of the nickname in a user group including both the recipient and the sender; or, if the nickname is not unique, checking the shared nickname; It is characterized by displaying a new nickname that can be selected from the information.

(5) In the configuration of (1) or (2) above, when the sender sends money using the public identifier, if the public identifier is not unique, the sender uses a subkeyword set in advance by the recipient. The present invention is characterized by comprising a remittance destination specifying means for searching and uniquely identifying a remittance destination.

(6) In the configuration of (1) or (2) above, if the private identifier includes the name or date of the gathering among the limited disclosure destinations, the relevant A feature is that the name of the meeting or the date can be confirmed or transcribed.

(7) In the configuration of (1) or (2) above, the disclosure destination of the private identifier is characterized in that a character string designated as a representative among the plurality of public identifiers can be specified.

(8) In the configuration of (1) or (2) above, when the remitter searches for the public identifier, people with whom he or she has a relationship on SNS or who have made past transfers are displayed preferentially. It is characterized by

(9) In the configuration of (1) or (2) above, the remitter and the recipient can send messages, images, and stamps in a chat room linked to the account identifier.

(10) A remittance method that allows the sender to send money without specifying the recipient's account number, where the recipient inputs any combination of character strings that serve as an account identifier instead of the account number. and a step of causing the recipient to set the input character string as a public identifier to be disclosed without limiting disclosure destinations and/or as a private identifier to be disclosed only to limited disclosure destinations. A computer executes the steps of: uniquely identifying the recipient's account number from the public identifier or the private identifier and executing the remittance.

(11) A program that causes the computer to execute each step described in (10) above.

According to the present invention, when a user makes a remittance request, an account identifier can be arbitrarily set in place of the store number and account number, and the remitter can search for the account identifier and uniquely identify the remittance destination. It is possible to provide a remittance system that allows remittances to be made.

In the present invention, it is a diagram showing the concept of an account identifier (ID) used instead of an account number. 1 is a diagram showing a functional configuration of a remittance system in an embodiment of the present invention. It is a figure showing an example of a setting screen of an account identifier (public identifier). It is a figure showing an example of a setting screen of an account identifier (private identifier). FIG. 3 is a diagram illustrating the concept of searching for a public identifier. It is a figure showing the processing flow of a recipient terminal in an embodiment of the present invention. It is a figure showing the processing flow of a sender terminal in an embodiment of the present invention. FIG. 4 is a diagram illustrating an example of a screen viewed from the remittance side of a transfer request when a private identifier is specified. FIG. 7 is a diagram illustrating an example of a screen showing the history in the room from the recipient side. FIG. 4 is a diagram illustrating an example of a screen where the recipient, who is the organizer of the banquet, confirms the amount to be transferred and the people who have already and have not yet made the transfer from the room.

(overview)
FIG. 1 is a diagram showing the concept of an account identifier (ID) used in place of an account number in the present invention. As shown in the figure, when an individual user (``Japan A-ko'') requests a transfer, the receiver's account information (bank name ``ABC Bank'', branch number ``211'', account type ``Ordinary'', account Although it is necessary to inform the sender of the number "1234567", etc., the present invention uses an account identifier (ID) instead of account information.The account identifier can be set arbitrarily by the receiver, and can be disposable or indefinite. Here, the IDs that can be set include public identifiers (also called "Public ID") and private identifiers (also called "Private ID"), which the recipient can use depending on the purpose. can be set, and one or more can be set for each.

A public identifier is an ID that a recipient can set without limiting the recipients (remittance request recipients), and a private identifier is an ID that the recipient can set without limiting the recipients (for example, acquaintances or friends). ) This is the ID to be set. Since public identifiers are made public to an unspecified number of people, there is a possibility that the parties involved cannot uniquely identify them.To avoid this, use subkeywords to uniquely narrow down the public ID. This will be discussed later.

In the example in Figure 1, the public identifiers (Public ID) are "Neko Neko" and "Tanukichi", and the private identifiers (Private ID) are "2019 Japan Research Institute Synchronization Meeting" and "December 25th Basketball Club Year-end Party". It is said that it is. When used to collect money at a gathering, etc., setting the date, content of the gathering, etc. as a private identifier will make it easier to contact related parties.

Here, account identifiers (referring to both public identifiers and private identifiers) are "character strings with meaning" (e.g., nicknames, terms that are only used among related parties and friends, etc.), and are not just numbers or meanings. A list of characters that does not have the same name cannot be set as an account identifier. Therefore, IDs that are automatically randomly assigned by the system are excluded. Further, as public identifiers, only one representative account identifier (referred to as "representative ID") is defined. The representative ID is an ID that permanently identifies the user's account, and other non-representative IDs are mainly used for temporary use, such as when making the account public for a limited time. It will be done. In the example shown in the figure, "NekoNeko" is the representative ID. Note that the representative ID is not set as the private identifier. Note that the method for setting the account identifier will be described later.

In this way, in the present invention, the remittance destination (remittance destination) can be identified using the account identifier instead of the account information, so the recipient can request and receive remittance without the other party knowing the account information. . Note that a transferee who is requested to make a remittance using an account identifier can also search for the account identifier and confirm the beneficiary's name from the account name.

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, modes for carrying out the present invention (hereinafter referred to as embodiments) will be described in detail with reference to the accompanying drawings. In the subsequent figures, the same numbers or symbols are given to the same elements throughout the description of the embodiments. Further, in the diagram of the functional configuration, arrows between functional blocks indicate the direction of data flow or the flow direction of processing.

(Functional configuration)
FIG. 2 is a diagram showing the functional configuration of a remittance system (hereinafter referred to as the present system) in an embodiment of the present invention. In this system, a depositor terminal 10, which is a terminal of a depositor who is a user, and a remitter terminal 20, which is a terminal of a remitter, are connected to a remittance server 100 operated by a financial institution via the Internet. The remittance server 100 has a function of allowing the depositor to set an account identifier, and a function of converting the set account identifier into an actual account number. The remittance server 100 is connected within the financial institution to an accounting system 200 that performs actual deposit and withdrawal processing.

The remittance server 100 includes an account identifier setting means 101, a public identifier storage means 102, a private identifier storage means 103, a remittance destination identification means 104, an account identifier search means 105, and an SNS information acquisition means 106 as functional blocks. The accounting system 200 has the core functions of a financial institution and includes various functions, but only the remittance execution means 201 and the remittance history storage means 202 that are directly related to the remittance server 100 are shown here. Note that the accounting system 200 includes those of other financial institutions. Each functional block will be explained in turn below.

The account identifier setting means 101 has a function of communicating with the depositor terminal 10 and allowing the depositor to set an account identification. Specifically, an ID setting screen as shown in FIGS. 3 and 4 is displayed on the depositor terminal 10, and the depositor is asked to enter the ID name (an arbitrary character string that is an account identifier) and the disclosure range (public identifier or non-public identifier). (distinction of public identifiers) etc. Here, the arbitrary character string serving as the account identifier is a character string determined to be "meaningful" according to a predetermined standard. This is because character strings that have "no meaning" are difficult to remember in people's memory and may cause input errors.

Here, the predetermined criteria may be that the string is not a character string consisting only of numbers, that it is not a string of alphanumeric symbols, and that at least one word is included in a dictionary. By doing this, it is possible to eliminate identifiers that are automatically numbered by the system. Also, for example, "neko" and "tanuki" are character strings that have meaning because they are found in dictionaries, but these alone are too simple and are not appropriate as identifiers, so "neko-neko" as shown by the ID in Figure 1 is used. , "Tanukichi" is preferable. Of course, in the end, any character string that the person who sets the account identifier determines to be "meaningful" and has identification ability may be sufficient.

FIG. 3 shows a setting screen for a public identifier. Here, "Cat/Neko" is selected as the ID name, and "Public" indicating that the ID is a public identifier is selected as the public range. The ID name may be a general-purpose character string, or a "meaningful" character string (for example, a unique ID name such as "Magical Happy Girl 2021") may be automatically generated on the system.

Furthermore, in the setting screen 301 of this example, "AAA high school," "BB university," and "C circle" are set as "subkeywords." A subkeyword is a search keyword for narrowing down and uniquely identifying an account when the ID name of the public identifier alone cannot uniquely identify the account. Of course, if the account can be uniquely identified by the ID name alone, there is no need to set this, but if the account identifier cannot be uniquely identified by just using "Neko Neko" as shown in the figure, it can be uniquely identified by using sub-keywords. can do.

At this time, you can combine the ID name and subkeyword and use "NekoNeko AAA High School" as a public identifier, or you can use the two words "NekoNeko" and "AAA High School" as public identifiers. good. By doing this, for example, the ID name "Neko Neko" can be used as a term representing year-end party, and the sub-keyword can be used as a term representing a target gathering (university, high school, club, etc.). In other words, there are multiple subkeywords under one ID name. Note that combinations of ID names and subkeywords that have already been used are checked within the system, so it goes without saying that they cannot be used at the same time.

Further, the set deadline is the expiration date of an ID name, and in the case of a public identifier, it is usually desirable to set it as unlimited. Of course, an expiration date may be set depending on the purpose. Although not shown in FIG. 3, it may be possible to specify whether an ID name is a representative ID or not. However, the representative ID may automatically have an unlimited set time limit.

FIG. 4 shows a private identifier setting screen 302. Here, "December 25th Basketball Club Year-End Party" is selected as the ID name, and "Private" indicating that it is a private identifier is selected as the disclosure range. In the case of a private identifier, unlike a public identifier, a setting deadline must be specified and an ID name of the public addressee must be specified. Sub keywords do not necessarily need to be set. In this example, "2021/12/31" is specified as the setting deadline, and "Kametaro" and "Usagi" are specified as the "disclosure destination" where the non-account identifier is disclosed only to a limited number of parties. .

In principle, the "publication destination" of a private identifier is specified by the public ID of the representative of the other party, but it may be specified by a public ID that is not the representative. However, the publication destination must be uniquely set depending on the identifier (Kametaro, Usagi) registered as the publication destination. If the publication destination cannot be uniquely identified, it is necessary to uniquely identify it by combining sub-keywords or by the method described below.

The account identifier (public identifier and private identifier) only needs to be uniquely identified between the remittance requester and the sender, so for example, if the remittance requester's nickname is used as the account identifier (in other words, the nickname of the account ), shared information on nicknames that the remittance requester shares with a user group that includes the remittor (e.g., 50 people including the remittor), and/or shared information of the nickname that the remittance person shares with a user group that includes the remittance The shared nickname information shared with other user groups (for example, 30 other people including the remittance requester) is used. Further, based on the shared information, it may be checked whether the nickname input by the remittance requester can be uniquely identified. In addition, the scope of the shared information search at this time (a user group that includes the recipient or the sender, a user group that only includes the recipient, a user group that only includes the sender, or a user group that includes both the recipient and the sender) It is desirable to save a "search flag", which will be described later, to indicate the group.

Furthermore, if there is no shared nickname information or if it is insufficient, the system may accumulate shared information as the user progresses in using the system. In addition, in order to check whether a nickname can be uniquely identified, the search range performed by the account identifier search means 105 is limited to nicknames known to the remittance requester and the remitter, so that the system can be operated efficiently. It becomes possible to do so. Note that if the private identifier cannot be uniquely identified using this method, it is necessary to specify a sub-keyword in the same way as for the public identifier. Note that the nickname sharing information may be stored in the account identifier search means 105 or may be obtained from the SNS information acquisition means 106.

Furthermore, "Kametaro" and "Usagi" can be specified with a Private ID instead of a Public ID. This is because private IDs used by close friends are more likely to be used permanently and are suitable as key information for transmitting account information.

Returning to FIG. 2, the public identifier storage means 102 is a storage means (database) that stores public identifiers of all users who subscribe to this service. The public identifier is linked to unique account information (bank code, branch number, account type, account number, name), and is set to have an unlimited expiration date by default, but you can change the expiration date depending on the purpose. may be provided. Furthermore, one representative ID may be set as the public identifier. Furthermore, as described above, subkeywords are set in the public identifier as necessary.

The private identifier storage unit 103 is a storage unit (database) that stores a user's private identifier. Private identifiers also come in two types, some with unlimited settings and others with restrictions. Note that the private identifier does not include a representative ID and subkeyword.

The remittance specifying means 104 receives a remittance request (transfer request) using an account identifier from the remitter terminal 20, and converts the account identifier into unique account information based on the public identifier storage means 102 or the private identifier storage means 103. It has the function of converting. Furthermore, when the recipient sets an account identifier, the remittance destination identifying means 104 also has the role of checking whether the account identifier has already been used and whether the account information can be uniquely identified from the account identifier. ing. At this time, if the shared information of the nickname is used to determine the uniqueness, a "search flag" indicating the search range of the shared information may be used at the time of nickname registration and remittance. For example, if the search flag is 1, the search range is the user group that includes the recipient or sender, and if the search flag is 2, the search range is the user group that includes only the recipient, and the search flag is 3. If the search flag is 4, the search range is the user group that includes senders only, if the search flag is 4, the search range is the user group that includes senders and recipients, and if the search flag is 0, the search range is to mean that there is no shared information. By doing this, the uniqueness of the nickname as an account identifier can be checked not only at the time of registration but also at the time of actual remittance.

The account identifier search means 105 is a means for the remitter to search for a public ID using a sub-keyword when the account identifier is a public ID. Note that the depositor may inform the remitter in advance whether the account identifier is a public identifier or a private identifier, but it can also be determined by the presence or absence of a sub-keyword without informing the remitter in advance.

When the remitter searches for a public ID, the SNS information acquisition means 106 preferentially displays people with whom the remitter has a relationship based on their SNS and past transfer records. An example of this is shown in FIG. This example shows how "Japan A-ko" requests "Souken B-ko" to transfer the membership fee etc. after the banquet. Here, "Japan A-ko" simply tells "December 25th basketball club year-end party" as the ID for the transfer destination, and "Souken B-ko" logs into her online banking and uses the ID search screen. When you enter the ID of the remittance destination and press the search button, "Japan A-ko" will be displayed as the remittance destination. After confirming the displayed remittance destination, "Souken B-ko" can execute the transfer by entering the remittance amount of "¥5,000" and pressing the confirm button. Note that the search screen may preferentially display people with whom you have a good relationship, such as those who have been registered as friends on SNS or who have made transfers in the past. This is to make the search more efficient.

The functional configuration of this system described above with reference to Figures 2 to 5 is just an example, and one functional block (database and functional processing unit) may be divided, or multiple functional blocks may be combined as one functional block. You can also configure it. Each functional processing unit uses a CPU (Central Processing Unit) built into the device to execute computer programs stored in storage devices such as ROM (Read Only Memory), flash memory, SSD (Sol identifier State Drive), and hard disk. It is realized by a computer program read out and executed by the CPU. In other words, each functional processing unit reads and writes necessary data such as tables from a database (DB) stored in a storage device or a storage area in memory, and in some cases, This is realized by controlling hardware (for example, input/output devices, display devices, communication interface devices). Further, the database (DB) in the embodiment of the present invention may be a commercial database, but it also means a simple collection of tables and files, and the internal structure of the database itself does not matter.

(Processing flow)
The details of the process at the depositor's terminal and the process at the sender's terminal will be described below with reference to FIGS. 6 and 7. In the following processing flow diagrams (flowcharts), the processing order of each step may be changed as long as the relationship between input and output of each step is not impaired.

FIG. 6 is a diagram showing the processing flow of the recipient terminal in the embodiment of the present invention. The recipient terminal first displays an account identifier setting screen (ID setting screen in FIGS. 3 and 4) in step S10.
Subsequently, in steps S10a and S10b, it is determined based on a predetermined criterion whether the input ID name is a "meaningful" character string. As mentioned above, the predetermined criteria here are that the string is not a string of numbers only, that it is not a string of alphanumeric symbols, and that at least one word is included in the dictionary. may be determined by the inputter.

Next, in step S11, the disclosure range is checked, and if Public is specified as the disclosure range, the process advances to step S12. Here, it is checked whether the input ID name can be uniquely specified as an account identifier. At this time, a term dictionary (not shown) is referred to. Further, in order to check whether the ID name is already in use, the public identifier storage means 102 on the server side is referred to. Furthermore, when the recipient's nickname is used as the account identifier, as described above, it may be checked whether or not it is unique using shared nickname information between the recipient and the remitter.

If the ID name cannot be uniquely specified, a subkeyword is specified in step S13. Note that even if the keyword can be uniquely identified, a subkeyword may be input just in case.

Next, in step S14, the ID name and subkeyword are set as public identifiers.

Then, in step S15, it is checked whether the set ID name is designated as a representative ID, and if it is designated as a representative ID, in step S16, a representative flag is turned on for that ID, etc. Make it distinguishable from other IDs. Finally, after inputting all setting items, the user presses the setting button to save the settings and end the process.

In step S11, if the public designation is not made (step S11: N), the process moves to step S17, and the input ID name is recognized as a private identifier (private designation). Then, in step S18, it is determined whether or not the ID name can be uniquely identified from the perspective of the disclosure destination of the private identifier. At this time, if the recipient's nickname is used as an account identifier, as mentioned above, check whether it can be uniquely identified using the shared information of the nickname in the user group that includes the recipient and the sender. It's okay.
If it cannot be uniquely identified, in step S18a, the user is asked to input a sub-keyword, and the input ID name is rechecked.

Next, in step S19, a set deadline is registered. Next, in steps S19a and S19b, if the ID name includes the date or the name of the gathering (○○ meeting, ○○ celebration, ○○ gathering, etc.), the electronic calendar of the inputter (remittance requester) is You may check the name and date of the meeting. Conversely, by clicking on a specific date item on the electronic calendar, the ID name may be automatically input (transcribed). Finally, the ID of the user who will make the private identifier public is registered as the public addressee. Then, when the user presses the settings button, the settings are saved and the process ends.

FIG. 7 is a diagram showing the processing flow of the sender terminal in the embodiment of the present invention. In step S20, the sender terminal first checks whether the ID name designated by the recipient is Public, that is, a public identifier. You may ask the recipient to specify whether the specified ID name is a public identifier or a private identifier (Private), but if it is unclear, please refer to the public identifier storage means and register it there. If so, proceed with the following process as a public identifier.

If the ID name specified in step S20 is not Public, the process moves to step S28, but if it is a public identifier, it is checked in step S21 whether or not there is a subkeyword, and if there is a subkeyword, the ID name is searched for using sub-keywords (step S22), and the search results are displayed (step S23). At this time, the sender's past transfer history is searched, and if there is one with the same ID name, that one is displayed with priority. In addition, if the sender's SNS information (ID of the person registered in the friend list or mutual follow) can be obtained, that information is displayed with priority.

Then, in step S24, the sender waits for the sender to select one of the displayed search results, and when the selection is made, in step S25, the selected ID name and sub-keyword are used as the account identifier, and the beneficiary account information (account number, etc.) and execute the remittance (request the accounting system to execute the remittance).

Finally, in step S26, it is checked whether the remittance has been completed normally. If a remittance error occurs, in step S24, it is checked whether the ID name and sub-keyword are correct for the recipient. Send a message to the sender's terminal asking them to do so.

In addition, if it is determined in step S21 that there is no sub-keyword, in step S28, only the specified ID name is converted into the recipient's account identification information, and the remittance is executed (the remittance is executed in the accounting system). ).

Also, if the specified ID name is Private instead of Public in step S20, the specified ID name is converted into the recipient's account identification information in step S28, and the remittance is executed (the remittance is sent to the accounting system). ). In either case, it is similarly checked in step S26 whether there is a remittance error.

(Other screen examples)
Below, other functions of this system will be explained using FIGS. 8 to 10.

FIG. 8 is a diagram illustrating an example of a screen viewed from the side that sends a remittance request when a private identifier is specified. The screen 304 in this example shows a list of transfer destinations that have received transfer requests using the Private ID. A different Private ID is used for each transfer destination, but the account holder of the transfer destination and the remittance status are displayed. Also, a screen 305 shows a conversation with the remittance recipient on the "room". A "room" (also referred to as a "talk room") is a user interface similar to a chat room on an existing SNS, and is a virtual room that allows talk (conversation) between senders and recipients. It is. Rooms are created for each Private ID, and you can also talk with multiple parties. Of course, in addition to text, you can also use images, stamps, etc. The room may be constructed within this system, or an existing SNS chat room may be used.

FIG. 9 is a diagram showing an example of a screen showing the history in the room from the recipient side. The recipient will be able to manage the published transfer requests in a list. That is, the recipient can check the history in the room for each account identifier (ID) after logging in using the store number and account number of his or her account from the screen 306. Here, the ID may be a public ID or a private ID, as shown in screen 307. When the recipient selects a specific ID column (in this case, "December 25th Basketball Club Year-end Party") from screen 307, the contents of that ID (in this case, the fact that the remittance was received from the person who requested the remittance) will be displayed on screen 308. It will be displayed as follows. By doing this, the recipient will be able to check the account holder who has already sent money, the amount of money sent, and the details from this room. For example, as shown in screen 309 in FIG. 10, if the recipient is the organizer of a banquet, the recipient can check from the room who has made the transfer/unpaid, the amount of each transfer, the total amount of the transfer, etc. can do.

(Effects of embodiment)
According to this system, the recipient sets an arbitrary combination of character strings that will serve as an account identifier in place of the account number and notifies the sender of the account number, so it is possible to request a remittance without informing the sender of the account number information. I can do it. Furthermore, account identifiers include public identifiers that do not limit disclosure destinations and private identifiers that are disclosed only to limited disclosure destinations, so they can be used depending on the purpose.

In addition, it is possible to determine whether a given character string that is an account identifier is a "meaningful" character string based on predetermined criteria, and a "meaningful" character string can be used as an account identifier. This makes it easier to remember and reduces input errors.

Furthermore, when a sender sends money using a public identifier, if the public identifier is not unique, the recipient can uniquely identify the recipient by searching using sub-keywords set in advance.

Furthermore, when using the nickname of the recipient's account as an account identifier, whether or not the nickname can be uniquely identified is checked based on sharing information of the nickname in a user group that includes the recipient and/or the sender. At that time, the checks are limited to nicknames known to the recipient and sender, making it possible to operate the system efficiently.

In addition, if the non-public identifier includes the name of a meeting or the date of a meeting that is limited to public disclosure, the name of the meeting or the date can be confirmed or transcribed from the recipient's electronic calendar. This makes it easier to input the identifier, and also makes it easier to associate the contents of the gathering.

Furthermore, by specifying a character string designated as a representative among a plurality of public identifiers, it becomes easier to specify the destination to which a private identifier is to be disclosed.

Furthermore, when a sender searches for a public identifier, by preferentially displaying people with whom the remitter has a relationship on SNS or a person who has made past transfers, it becomes easier to find the uniqueness of the public identifier.

In addition, senders and recipients can send messages, images, and stamps in a chat room linked to their account identifier, allowing them to confirm and have other conversations with the other party using the same user interface as existing SNS chat rooms. It can be carried out.

Although the present invention has been described above using the embodiments, it goes without saying that the technical scope of the present invention is not limited to the range described in the above embodiments. It will be apparent to those skilled in the art that various changes or improvements can be made to the embodiments described above. Furthermore, it is clear from the claims that forms with such changes or improvements may also be included within the technical scope of the present invention.

In the above embodiment, a cash remittance system in a bank was particularly described, but the present invention can also be applied to remittances in other financial institutions. Further, in the embodiments described above, the present invention is described as a product invention and a remittance system, but the present invention can also be regarded as an invention of a remittance method or an invention of a program that causes a computer to execute remittance processing.

10 depositor terminal 20 remitter terminal 100 remittance server 101 account identifier setting means 102 public identifier storage means 103 private identifier storage means 104 remittance destination identification means 105 account identifier search means 106 SNS information acquisition means 200 accounting system 201 remittance execution means 202 Remittance history storage means 301, 302 Account identifier setting screen 303 to 309 Other screens

Claims (11)

A remittance system that allows a sender to send money without specifying the recipient's account number,
having the recipient enter an arbitrary combination of character strings that will serve as an account identifier instead of the account number;
Account identifier setting means for causing the recipient to set the input character string as a public identifier to be disclosed without limiting disclosure destinations and/or as a private identifier to be disclosed only to limited disclosure destinations; and,
remittance execution means for searching the public identifier or the private identifier to uniquely identify the recipient's account number and executing the remittance;
A remittance system characterized by comprising: 2. The remittance system according to claim 1, wherein the arbitrary character string is determined to have a meaning based on a predetermined criterion. When the arbitrary character string is used as the nickname of the recipient's account,
checking whether the nickname is unique based on sharing information of the nickname in a user group including the recipient or a user group including the remitter;
Alternatively, if the specified nickname is not unique, displaying a new selectable nickname from the shared information;
The remittance system according to claim 1 or 2, characterized by: When the arbitrary character string is used as the nickname of the recipient's account,
Whether the nickname is unique based on sharing information of the nickname in a user group that includes only the recipient, a user group that only includes the sender, or a user group that includes both the recipient and the sender. to check,
Alternatively, if the specified nickname is not unique, displaying a new selectable nickname from the shared information;
The remittance system according to claim 1 or 2, characterized by: When the sender sends remittance using the public identifier, if the public identifier is not unique, the remittance specifying means searches using a sub-keyword set in advance by the receiver to uniquely identify the remittance destination. The remittance system according to claim 1 or 2, further comprising: If the non-public identifier includes the name of a gathering or the date of the gathering among the limited disclosure destinations, the name of the gathering or the date can be confirmed or transcribed from the recipient's electronic calendar. The remittance system according to claim 1 or 2. 3. The remittance system according to claim 1 or 2, wherein a character string designated as a representative among the plurality of public identifiers can be specified as the public identifier of the private identifier. 3. The remittance system according to claim 1 or 2, wherein when the remitter searches for the public identifier, the remittance system preferentially displays people with whom the remitter has a relationship on SNS or who has a past record of remittances. . 3. The remittance system according to claim 1, wherein the remitter and recipient can send messages, images, and stamps in a chat room linked to the account identifier. A remittance method that allows the sender to send money without specifying the recipient's account number,
having the recipient input an arbitrary combination of character strings as an account identifier instead of the account number;
having the recipient set the input character string as a public identifier to be disclosed without limiting disclosure destinations and/or as a private identifier to be disclosed only to limited disclosure destinations;
Uniquely identifying the recipient's account number from the public identifier or the private identifier and executing the remittance;
A remittance method characterized by being executed by a computer. A program that causes the computer to execute each step according to claim 10.