JP6871105B2 - Remittance support device, remittance support method, and remittance support program - Google Patents

Description

The present invention relates to a remittance support device, a remittance support method, and a remittance support program.

Conventionally, remittances have been made to a designated account by a user performing a predetermined procedure from a financial institution window or an ATM (Automated Teller Machine). In remittance, remittances that the sender does not intend may be performed, such as fraudulent deception (so-called transfer fraud). Transfer fraud is, for example, by pretending that the recipient (criminal) is a relative and requesting the sender (victim) to transfer money to the designated account, thereby deceiving the sender and sending the money to the designated account. It is a fraudulent act to make you.

As a related prior art, past transfer transaction information is accumulated for each transfer requester, and a warning is displayed when the transfer destination account of this transfer transaction is an account that has never made a transfer in the past. (See, for example, Patent Document 1 below).

JP-A-2007-102620

However, in the prior art, the remittance may not be performed unintentionally by the sender, so that the sender may not be able to remit with confidence. Specifically, remittances not intended by the sender may be caused not only by transfer fraud, but also by misunderstandings such as the sender making a mistake in the address or erroneous operations such as duplicate remittances.

The present invention solves the problems caused by the above-mentioned prior art, so that the remittance can send money with peace of mind. In particular, a remittance support device, a remittance support method, and a remittance support program that are effective as countermeasures against fraud that deceives relatives. The purpose is to provide.

In order to solve the above-mentioned problems and achieve the object, the remittance support device according to the present invention receives a request from a remittancer to send money to a recipient whose contact information is registered in advance. In response to the notification unit that notifies the recipient that the remittance will be made, the reception unit that accepts the consent of the remittance to be made by the notification from the recipient, and the consent received by the reception unit. The remittance control unit for executing the remittance is provided.

Further, the remittance support device according to the present invention is characterized in that, in the above invention, the consent includes the authentication of the recipient.

Further, in the above invention, the remittance support device according to the present invention receives the predetermined character string when the notification unit receives the request including the input of the predetermined character string indicating the remittance from the sender. It is characterized in that the above-mentioned notification including the above is given.

Further, in the remittance support device according to the present invention, in the above invention, when the remittance control unit does not receive the consent by the reception unit between the time when the notification is given and the time when a predetermined period elapses, or When the reception unit receives that the remittance is not to be performed, the request received from the remittance sender is canceled.

Further, the remittance support device according to the present invention is characterized in that, in the above invention, the notification unit notifies the remittance sender to that effect when the request is canceled by the remittance control unit. And.

Further, in the remittance support device according to the present invention, in the above invention, the notification unit requests the remittance to be performed to the remittance, and the contact information is registered in advance to the remittance's agent. When the remittance sender accepts the notification, the remittance control unit receives the consent from the agent by the notification, and the remittance control unit receives the notification to the agent. The remittance is executed to the recipient in response to the consent from the recipient.

Further, in the remittance support device according to the present invention, in the above invention, the notification includes the reception result of receiving one or more types of authentication to be performed by the recipient from among a plurality of types of authentication from the remittance sender, and the receipt. The person's authentication is characterized in that it is the type of authentication indicated by the reception result.

In addition, the remittance support method according to the present invention notifies the recipient that the remittance will be performed when the remittance receives a request from the sender to send the remittance to the recipient whose contact information is registered in advance. The computer executes the process of receiving the consent from the recipient to perform the remittance by the notification and executing the remittance in response to the received consent.

In addition, the remittance support program according to the present invention notifies the recipient that the remittance will be performed when the remittance receives a request from the sender to send the remittance to the recipient whose contact information is registered in advance. The remittance is performed, the consent to the remittance is received from the recipient by the notification, and the remittance is executed according to the received consent, and the computer is made to execute the process.

According to the remittance support device, the remittance support method, and the remittance support program according to the present invention, the remittance can send money with peace of mind, and it is particularly effective as a countermeasure against fraud that deceives relatives.

FIG. 1 is an explanatory diagram showing a system configuration example of the remittance support system 100 according to the embodiment. FIG. 2A is a block diagram showing an example of the hardware configuration of the bank server 111. FIG. 2B is a block diagram showing an example of the hardware configuration of the remittance terminal 121 and the recipient terminal 131. FIG. 3A is an explanatory diagram showing an example of the stored contents of the remittance sender information database (DB) 112. FIG. 3B is an explanatory diagram showing an example of the stored contents of the recipient information database (DB) 113. FIG. 3C is an explanatory diagram showing an example of the stored contents of the agent information database (DB) 114. FIG. 3D is an explanatory diagram showing an example of the stored contents of the transaction information database (DB) 115. FIG. 4 is an explanatory diagram showing a functional configuration of the bank server 111. FIG. 5 is an explanatory diagram showing an example of a display screen when a remittance request is made from the recipient 130 to the remittance sender 120 by e-mail. FIG. 6 is an explanatory diagram showing an example of a display screen when making a remittance request at the remittance sender terminal 121. FIG. 7 is an explanatory diagram showing an example of a display screen of a confirmation email displayed on the recipient terminal 131. FIG. 8 is an explanatory diagram showing an example of a display screen when accepting remittance consent from the recipient 130. FIG. 9 is an explanatory diagram showing an example of a display screen when receiving a comment input from the recipient 130. FIG. 10 is an explanatory diagram showing an example of a display screen of a notification of completion of the remittance procedure displayed on the recipient terminal 131. FIG. 11 is an explanatory diagram showing an example of a display screen of a remittance procedure completion notification displayed on the remittance sender terminal 121. FIG. 12 is an explanatory diagram showing an example of a display screen of a cancellation notice indicating that the remittance procedure displayed on the remittance sender terminal 121 has been cancelled. FIG. 13 is a sequence diagram showing an example (No. 1) of the remittance support processing procedure according to the present embodiment. FIG. 14 is a sequence diagram showing an example (No. 2) of the remittance support processing procedure according to the present embodiment. FIG. 15 is a sequence diagram showing an example (No. 3) of the remittance support processing procedure according to the present embodiment. FIG. 16 is a sequence diagram showing an example (No. 4) of the remittance support processing procedure according to the present embodiment. FIG. 17 is a flowchart showing an example of the remittance support processing procedure performed by the bank server 111.

Hereinafter, embodiments of the remittance support device, the remittance support method, and the remittance support program according to the present invention will be described in detail with reference to the drawings.

(System configuration of remittance support system)
First, a system configuration example of the remittance support system 100 according to the embodiment will be described. FIG. 1 is an explanatory diagram showing a system configuration example of the remittance support system 100 according to the embodiment. In FIG. 1, the remittance support system 100 includes a bank server 111, a remittance terminal 121, and a recipient terminal 131.

The bank server 111 is, for example, a server provided in the bank 110 and is an example of a remittance support device. The bank server 111 is a general-purpose computer device such as a personal computer that manages card information of a cash card for each user and deposits and withdrawals of an account. The bank server 111 has a CPU (Central Processing Unit), a memory, an interface, and the like.

Further, the bank server 111 has a sender information database (DB) 112, a recipient information database (DB) 113, an agent information database (DB) 114, and a transaction information database (DB) 115. The stored contents of the various DBs 112 to 115 will be described later with reference to FIGS. 3A to 3D.

The remittance terminal 121 is a computer device used by the remittancer 120 who remits money to a designated account. For the remittance terminal 121, for example, a smartphone, a tablet-type PC (Personal Computer), or the like can be used. However, the sender terminal 121 is not limited to this, and may be, for example, a desktop PC, a notebook PC, a mobile phone, a PHS (Personal Handyphone System), an ATM (Automated Teller Machine) installed in a financial institution, or the like. Is. The remittance terminal 121 has a CPU, a memory, an interface, and the like.

The recipient terminal 131 is a general-purpose computer device such as a personal computer used by the recipient 130. For the recipient terminal 131, for example, a smartphone, a tablet-type PC, or the like can be used. However, the recipient terminal 131 is not limited to this, and a desktop PC, a notebook PC, a mobile phone, a PHS, or the like can also be used. The recipient terminal 131 has a CPU, a memory, an interface, and the like. Contact information such as the e-mail address and telephone number of the recipient terminal 131 shall be registered in the bank server 111 in advance.

In the remittance support system 100, the bank server 111, the remittance terminal 121, and the recipient terminal 131 are connected via a wired or wireless network 140. The network 140 includes, for example, the Internet, a mobile communication network, a LAN (Local Area Network), a WAN (Wide Area Network), and the like.

The remittance support program according to the present invention is installed in the bank server 111. The bank server 111 performs processing according to various requests from the remittance terminal 121 and the recipient terminal 131, and outputs various processing results to the remittance terminal 121 and the recipient terminal 131.

Here, the remittance support method according to the present embodiment will be described. As shown in FIG. 1 (1), the remittance terminal 121 makes a remittance request to the recipient 130 to the bank server 111 in response to the operation of the remittance 120. Specifically, the remittance terminal 121 receives a request from the sender 120 to send money to the recipient 130. The recipient 130 corresponds to the recipient terminal 131 whose contact information is registered in the bank server 111 in advance. For example, the remittance terminal 121 accepts a remittance destination indicating the recipient 130 and an amount to be remitted, as shown on the display screen 122.

Then, when the bank server 111 receives the remittance request from the sender terminal 121, the bank server 111 notifies the recipient terminal 131 that the remittance will be performed, as shown in (2). The notification that the remittance will be performed is a notification that the remittance will be performed from the sender 120 as shown on the display screen 132.

Then, as shown in (3), the recipient terminal 131 receives the consent from the recipient 130 that the remittance is to be performed, and transmits that fact to the bank server 111. Then, as shown in (4), the bank server 111 executes the remittance according to the consent received by the recipient terminal 131.

As described above, in the present embodiment, when the bank server 111 transfers the remittance from the sender 120 to the recipient 130, the bank server 111 executes the remittance after obtaining the consent of the recipient 130. Therefore, the bank server 111 can prevent the sender 120 from making an unintended remittance. As a result, the remittance person 120 can remit with confidence.

(Example of hardware configuration of bank server 111)
Next, an example of a specific configuration of the bank server 111 will be described. FIG. 2A is a block diagram showing an example of the hardware configuration of the bank server 111. In FIG. 2A, the computer device that realizes the bank server 111 includes a CPU 211, a memory 212, and a communication IF (Interface) 213. Each unit 211 to 213 included in the computer device is connected by a bus 210. The CPU 211 controls the entire computer device.

The memory 212 stores programs such as boot programs and data of various databases. In addition, the memory 212 stores various programs and data related to the provision of the remittance support service, such as a remittance support program and a part of data of various databases.

Further, the memory 212 is used as a work area of the CPU 211. The memory 212 can be realized by, for example, a ROM (Read-Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), an HD (Hard Disk), or the like.

The communication IF 213 is connected to the network 140 and controls an interface between the inside of the computer device and an external device such as a remittance terminal 121 or a recipient terminal 131. Specifically, the communication IF 213 controls the input / output of data between the inside of the computer device and the external device.

(Example of hardware configuration of remittance terminal 121 and recipient terminal 131)
Next, an example of the hardware configuration of the remittance terminal 121 and the recipient terminal 131 will be described. FIG. 2B is a block diagram showing an example of the hardware configuration of the remittance terminal 121 and the recipient terminal 131. Since the remittance terminal 121 and the recipient terminal 131 have the same configuration, the remittance terminal 121 will be described below, and the description of the recipient terminal 131 will be omitted.

In FIG. 2B, the remittance terminal 121 includes a CPU 221, a memory 222, an output device 223, an input device 224, and a communication IF 225. Further, each unit 221 to 225 included in the remittance terminal 121 is connected by a bus 220.

The CPU 221 controls the entire remittance terminal 121. The CPU 221 controls the entire remittance terminal 121 by using various programs and data stored in the memory 222. The memory 222 can be realized by a hard disk, a flash memory, or the like.

The output device 223 includes, for example, a display, a speaker, an audio output terminal, and the like. The display displays operation details, guidance information for the user, and the like. The display displays various operation screens related to the remittance support service. The display can be realized, for example, mainly by a liquid crystal display, an organic EL (Electro-Luminescence) display, or the like.

In addition, the speaker outputs voice, alarm sound, and the like. The audio output terminal is a terminal for connecting headphones or the like, and outputs audio, alarm sounds, or the like to the connected headphones or the like in the same manner as a speaker.

The input device 224 includes keys for inputting characters, numerical values, various instructions, and the like, and inputs data. The input device 224 can be realized by, for example, a touch panel or a keyboard. The input device 224 realized by a touch panel, a keyboard, or the like outputs a signal corresponding to an input operation to the input device 224 to the CPU 221.

When the input device 224 is realized by a touch panel, the touch panel is laminated on the display surface side of the display. When the touch panel detects that a writing member such as a finger or a pen has come into contact with the touch panel, the touch panel outputs an electric signal according to the contact position of the writing member with respect to the touch panel. As the touch panel, various known methods such as a resistance film method, a capacitance method, an acoustic pulse recognition method, an ultrasonic surface acoustic wave method, an infrared shading method, and an image recognition method can be used.

The input device 224 also includes a camera. The camera is controlled by the CPU 221 to capture an image to be imaged, generate image data, capture and input a two-dimensional code such as a barcode or QR code (registered trademark), and perform an OCR (Optical Character Reader) function. It is possible to convert the characters taken by using the data into data and input it.

The input device 224 also includes a microphone. The microphone converts the speaker's voice input as analog data into analog / digital and generates audio data in digital format. By using the microphone, the user can input characters and the like via the remittance terminal 121 instead of using the touch panel and the keyboard.

The communication IF 225 controls an interface between the inside of the remittance terminal 121 and an external device such as a bank server 111 or a recipient terminal 131. Further, the communication IF 225 may be connected to the telephone line network and used for voice communication.

In addition, although not shown, the remittance terminal 121 is provided with functions such as a call function including a speaker and a communication function, and a function as an information processing device such as a smartphone.

(Memory contents of various DBs 112 to 114)
Next, the stored contents of various DBs 112 to 114 included in the bank server 111 shown in FIG. 1 will be described with reference to FIGS. 3A to 3D. The various DBs 112 to 114 are realized by, for example, a storage unit such as a memory.

FIG. 3A is an explanatory diagram showing an example of the stored contents of the remittance sender information database (DB) 112. In FIG. 3A, the remittance information DB 112 has fields for a remittance ID (Identification), a remittance name, an account number, and an e-mail address. By setting information in each field, a record of remittance sender information (for example, remittance sender information 300-1 to 300-3) is stored.

The remittance person ID indicates the identification information attached to each remittance person 120 (user). The name of the sender indicates the name of the holder of the account corresponding to the sender 120. The account number is a number assigned to each account and indicates the account number of the sender 120. The e-mail address indicates the e-mail address of the terminal corresponding to the remittance sender 120, and specifically, the e-mail address of the remittance sender terminal 121.

For example, the remittance information 300-1 indicates the remittance ID "A001", the remittance name "Soken Souko", the account number "0123456", and the e-mail address "○○@○○ .jp". Similarly, the remittance information 300-2 and 300-3 other than the user ID "A001" are also stored in the remittance information DB 112.

In FIG. 3A, for convenience of explanation, the information of each field shown in the sender information DB 112 is stored, but it may not have all the fields shown in FIG. 3A. For example, information in some fields (for example, an e-mail address) may be stored in another DB in association with a user ID. In this case, some fields are stored in another DB using the user ID. All you have to do is get the information.

FIG. 3B is an explanatory diagram showing an example of the stored contents of the recipient information database (DB) 113. In FIG. 3B, the recipient information DB 113 has fields for a sender ID, a recipient ID, a usual name, a recipient name, an account number, an email address, a password, and image data. By setting information in each field, a record of recipient information (for example, recipient information 310-1 to 10-3) is stored.

The remittance person ID indicates the identification information attached to each remittance person 120, is the same as the remittance person ID stored in the remittance person information DB 112 (see FIG. 3A), and is indicated by the remittance person ID of the remittance person information DB 112. It also corresponds to each remittance sender information 300. The recipient ID indicates identification information assigned to each recipient 130. The usual name is a nickname, regardless of kanji, English, katakana, etc. The beneficiary name indicates the name of the holder of the account corresponding to the beneficiary 130. The account number is a number assigned to each account and indicates the account number of the recipient 130. The e-mail address indicates the e-mail address of the terminal corresponding to the recipient 130, and specifically, indicates the e-mail address of the recipient terminal 131.

The password indicates a character string for authentication when the recipient 130 approves the remittance at the recipient terminal 131, and specifically, it is a number or a symbol, and also includes a secret word or the like. The image information data indicates the face image data of the recipient 130 for performing face authentication instead of the password.

For example, the recipient information 310-1 includes the sender ID "A001", the recipient ID "B001", the usual name "Taro", the recipient name "Sokentaro", the account number "12344567", and the email address "○○". ＠ ○○ .jp ”, password“ ○○○○ ”, and image data“ ○○○○ ”. Recipient information 310-2 and 310-3 other than the recipient ID "B001" are also stored in the recipient information DB 113 in the same manner.

Since the "usual name" can be stored in the recipient information DB 113, the sender 120 can select the "ordinary name" and remit to the recipient 130. The bank server 111 can send an e-mail requesting consent to the e-mail address associated with the "ordinary nickname" sent from the remittance terminal. In this way, the remittance sender 120 can identify the correct holder (recipient name) associated with the "ordinary nickname" by selecting the "ordinary nickname".

In FIG. 3B, for convenience of explanation, the information of each field shown in the recipient information DB 113 is stored, but it may not have all the fields shown in FIG. 3B. For example, information on some fields (for example, image data) may be stored in another DB in association with a user ID. In this case, some fields from the other DB may be stored using the user ID. All you have to do is get the information.

FIG. 3C is an explanatory diagram showing an example of the stored contents of the agent information database (DB) 114. In FIG. 3C, the agent information DB 114 has fields for a recipient ID, an agent name, an agent email address, and an agent password. By setting information in each field, a record of proxy information (for example, proxy information 320-1 to 320-3) is stored.

The recipient ID indicates identification information assigned to each recipient 130, is the same as the recipient ID stored in the recipient information DB 113 (see FIG. 3B), and is indicated by the recipient ID of the recipient information DB 113. It also corresponds to each sender information 310. The agent name is the name of the person representing the recipient 130, for example, the name of the spouse or child of the recipient 130. The agent e-mail address indicates the e-mail address of the agent terminal corresponding to the agent. The agent password indicates an authentication character string used when the agent approves the remittance to the recipient 130 at the agent terminal.

For example, the agent information 320-1 indicates the recipient ID "B001", the agent name "Soken Hanako", the agent email address "○○@○○ .jp", and the agent password "○○○○". .. Further, for example, the agent information 320-2 indicates that the agent is not registered, and specifically, regarding "Sokenjiro" (see FIG. 3B) corresponding to the recipient ID "B002". Indicates that the agent is not registered. Similarly, the agent information 320-3 is also stored in the agent information DB 114.

FIG. 3D is an explanatory diagram showing an example of the stored contents of the transaction information database (DB) 115. In FIG. 3D, the transaction information DB 115 has fields of transaction information ID, sender ID, recipient ID, remittance destination account number, amount, subject, authentication method, procedure date and time, and procedure completion status. By setting information in each field, a record of transaction information (for example, transaction information 330-1, 330-2) is stored.

The transaction information ID indicates identification information attached to each transaction information. The remittance sender ID indicates identification information attached to each remittance sender 120, and is the same as the remittance sender ID stored in the sender information DB 112 (see FIG. 3A) and the recipient information DB 113 (see FIG. 3B). The remittance ID also corresponds to each remittance information 300 indicated by the remittance ID of the remittance information DB 112 and each remittance information 310 indicated by the recipient ID of the recipient information DB 113.

The recipient ID indicates identification information attached to each recipient 130, and is the same as the recipient ID stored in the recipient information DB 113 (see FIG. 3B) and the agent information DB 114 (see FIG. 3C). is there. The recipient ID also corresponds to each remittance information 310 indicated by the recipient ID of the recipient information DB 113 and each agent information 320 indicated by the recipient ID of the agent information DB 114.

The remittance destination account number is the remittance destination account number, for example, the account number shown in FIG. 3B, but may be a designated account number other than this. The amount indicates the amount of money transferred from the sender 120 to the recipient 130. The subject indicates the subject of the mail sent from the bank server 111 in order for the recipient 130 to approve the remittance at the recipient terminal 131.

The authentication method is an authentication method used in the authentication performed when the recipient 130 approves the remittance at the recipient terminal 131, and indicates the authentication method specified by the sender 120. The procedure date and time indicates the date and time when the remittance sender 120 made the remittance request.

The state of completion of the procedure indicates whether or not the remittance request has been completed in response to the remittance request made by the sender 120. Specifically, the procedure is completed when the recipient 130 consents. , The incomplete state is maintained unless the recipient 130 consents.

For example, the transaction information 330-1 includes transaction information ID "X001", remittance ID "A001", recipient ID "B001", remittance account number "1234567", amount "5000 yen", subject "Sakura no Kai", and so on. Indicates the authentication method "password", the procedure date and time "○ month ○ day ○ hour ○ minute ○ second", and the procedure completion status "completed". Further, the transaction information 330-2 other than the transaction information ID "X001" is also stored in the transaction information DB 115 in the same manner.

(Functional configuration of bank server 111)
FIG. 4 is an explanatory diagram showing a functional configuration of the bank server 111. In FIG. 4, the bank server 111 has a notification unit 401, a reception unit 402, and a remittance control unit 403. The notification unit 401, the reception unit 402, and the remittance control unit 403 realize their functions by, for example, causing the CPU 211 to execute a program stored in the memory 212 (see FIG. 2A) of the bank server 111.

When the notification unit 401 receives a request from the sender 120 to send a remittance to the recipient 130 whose contact information is registered in advance, the notification unit 401 notifies the contact of the recipient 130 that the remittance will be made. Do it. The contact information is a contact information corresponding to the recipient 130, and is an e-mail address or a telephone number. Specifically, the contact information may be the e-mail address or telephone number of the recipient terminal 131 for each recipient 130, or may be the e-mail address of a free e-mail or the telephone number of the home.

Pre-registration means that the remittance request has already been registered when the remittance request is received. For example, based on the time when the request for remittance (remittance request) is received, at least a predetermined period (for example, 1) It must have been registered more than a day ago. The recipient 130, whose contact information is registered in advance, is specifically a remittance destination that remits money at a predetermined frequency, and is, for example, a recipient of financial assistance such as a child, a parent, or a sibling.

Sending money to the recipient 130 means sending money to the recipient's account. Remittance is the transfer of funds to a designated account, for example, the transfer of funds between accounts, or the transfer of funds from a financial institution window or ATM to a designated account, specifically. , Transfer. The bank server 111 receives a request for remittance from the remittance sender 120 via the remittance terminal 121 or the ATM. The notification that the remittance will be made may be sent by e-mail, for example, but may also be sent by short message or telephone.

The reception unit 402 accepts from the recipient 130 the consent that the remittance will be made by the notification. The consent that the remittance will be made can be made because the recipient 130 knows in advance that the remittance will be made. In other words, if the recipient 130 does not remember it, the remittance will be obtained from the recipient 130. It will never be done.

In the present embodiment, as a premise for remittance, the remittance 130 knows in advance that the remittance will be performed by requesting the remittance from the remittance 120 from the remittance 130 or by making a regular remittance. Suppose you are.

Acceptance of consent by the reception unit 402 is performed by the recipient 130, for example, by accessing the predetermined address indicated in the e-mail message from the recipient terminal 131. However, the acceptance of consent by the reception unit 402 is not limited to this, and a blank e-mail may be replied to the transmitted e-mail or the like. In addition, when the contact information is called, consent may be accepted by, for example, an auto call.

The remittance control unit 403 executes the remittance in response to the consent received by the reception unit 402. Specifically, the remittance control unit 403 executes remittance to the recipient account when the reception unit 402 accepts the consent of the recipient 130, and when the reception unit 402 does not accept the consent of the recipient 130. Does not execute the remittance.

Also, in this embodiment, consent includes authentication of recipient 130. The authentication of the recipient 130 includes password authentication and biometric authentication performed by the recipient 130. Password authentication is authentication by performing a match determination of a predetermined character string. Biometric authentication includes fingerprint authentication, face authentication, blood vessel authentication, retina authentication, palm shape authentication, and the like. The authentication may be performed by the bank server 111, the recipient terminal 131, or another device.

In addition, the notification that the remittance will be performed includes the acceptance result of receiving one or more types of authentication from the sender 120 to be performed by the recipient 130 from among a plurality of types of authentication. The authentication performed by the recipient 130 is the type of authentication indicated by the acceptance result, that is, the type of authentication selected by the sender 120.

Specifically, in the present embodiment, the plurality of types of authentication include, for example, password authentication, face authentication, and fingerprint authentication. Of these, one or more types of authentication are accepted from the sender 120, and the recipient 130 authenticates by the received type of authentication. The number of types of authentication received from the sender 120 may be one type or a plurality of types.

In the present embodiment, the password authentication and the face authentication are performed by the bank server 111. Specifically, the bank server 111 acquires the password and the image data of the face from the recipient terminal 131, and authenticates each of them. Further, fingerprint authentication is performed by the recipient terminal 131. Specifically, fingerprint authentication is performed using the fingerprint authentication function of the recipient terminal 131.

However, the recipient 130 may select the type of authentication without selecting the type of approval by the sender 120. For example, if the recipient 130 is ill or serious and no agent is registered (see agent information 320-2 in FIG. 3C), a third party such as a colleague of the recipient 130 In some cases, the recipient terminal 131 is operated to request the remittance 120 to remit, and the consent of the remittance is obtained.

In this case, the third party captures image data of the face of the recipient 130 from the driver's license or the like of the recipient 130 by using, for example, the imaging function of the recipient terminal 131. Then, the captured image data is transmitted from the recipient terminal 131 to the bank server 111, and the bank server 111 succeeds in face authentication using the image data, so that the money can be transferred to the recipient account.

Further, in the present embodiment, when the notification unit 401 receives a request from the sender 120 including the input of a predetermined character string indicating the remittance, the notification unit 401 gives a notification including the predetermined character string. The predetermined character string is a character string used when the bank server 111 contacts the recipient terminal 131. Specifically, the predetermined character string is a keyword shared by the recipient 130 and the remittance person 120, and includes, for example, characters, symbols, numbers, and the like.

The predetermined character string tells the recipient 130 that the notification is related to the remittance before the recipient 130 confirms the content of the notification that the remittance will be performed, for example, when the notification is received. It is a character string that can be shown.

For example, a predetermined character string is used in the subject (title) attached to an e-mail. By using a predetermined character string in the subject of the e-mail, it is possible to indicate to the recipient 130 that the e-mail is not a mischievous e-mail or the like but an e-mail for consenting to remittance, and the e-mail is sent to the recipient 130. It can be opened (confirmed). As a result, the notification unit 401 can accept the consent that the remittance is performed.

It is also possible to use a predetermined character string as the telephone number of the financial institution associated with the bank server 111. In this case, when the short message is received, the telephone number is notified to the recipient 130 to notify the bank. It can be shown that it is a short message from the server 111. Therefore, the recipient 130 can open the short message with peace of mind. As a result, the notification unit 401 can accept the consent that the remittance is performed.

It is also possible to use a predetermined character string as the telephone number of the financial institution associated with the bank server 111. In this case, the bank is notified of the telephone number when the telephone is received. It can be shown that the call is from the server 111. Therefore, the recipient 130 can answer the call with confidence. As a result, the notification unit 401 can accept consent for the remittance to be made, for example, by autocall.

Further, in the present embodiment, the predetermined character string is notified at the time of requesting remittance from the recipient 130 to the sender 120, for example, before the remittance request to the bank server 111 by the sender 120. .. However, the present invention is not limited to this, and the predetermined character string may be determined by the sender 120 in the remittance request and notified from the sender 120 to the recipient 130.

Further, the remittance control unit 403 cancels the remittance request when the reception unit 402 does not accept the consent between the time when the notification that the remittance is performed and the time when the predetermined period elapses. The predetermined period is, for example, 24 hours. Cancellation is, for example, canceling everything, but is not limited to this, and may be resumed after being interrupted once.

Further, the remittance control unit 403 cancels the remittance request addressed to the recipient 130 when the reception unit 402 accepts that the remittance is not performed. The fact that a predetermined period has passed since the notification that the remittance will be made or that the remittance will not be made is accepted is, for example, when the recipient 130 does not request the remittance 120 to send the money. This can happen if the recipient 130 is an unintended remittance. Therefore, the remittance control unit 403 cancels the remittance request after a lapse of a predetermined period.

Further, when the remittance request to the recipient 130 is canceled by the remittance control unit 403, the notification unit 401 notifies the remittance sender 120 to that effect. Specifically, the notification unit 401 notifies the remittance terminal 121 that the remittance request addressed to the recipient 130 has been cancelled.

Further, the notification unit 401 notifies the remittance request addressed to the remittance 130 and the notification to the remittance 130's agent (for example, the e-mail address of the agent) to which the contact information is registered in advance from the remittance 120. Upon acceptance, we will notify the agent that the remittance will be made. The agent is, for example, a person who has a close relationship with the recipient 130, specifically, a spouse or a child of the recipient 130.

The reception unit 402 accepts the consent from the agent that the remittance will be made by notifying that the remittance will be made. The remittance control unit 403 executes the remittance to the recipient 130 in response to the consent from the agent that the remittance will be performed. Specifically, the remittance control unit 403 executes the remittance to the recipient account when the acceptance of the agent is accepted by the reception unit 402.

(Example of display screen of remittance terminal 121 and recipient terminal 131)
FIG. 5 is an explanatory diagram showing an example of a display screen when a remittance request is made from the recipient 130 to the remittance sender 120 by e-mail. The display screen 500 of FIG. 5 shows an e-mail composition screen. Specifically, as shown on the display screen 500, the bank server 111 requests the remittance of 5,000 yen to the predetermined title, the destination of the sender 120 (Soken Souko), by the operation of the recipient 130. It is input that the subject of the mail sent to 121 is "Sakura no Kai". When the transmission button 501 is operated by the recipient 130 on the display screen 500, the recipient terminal 131 transmits the content shown on the display screen 500 to the bank server 111.

FIG. 6 is an explanatory diagram showing an example of a display screen when making a remittance request at the remittance sender terminal 121. The display screen 600 of FIG. 6 shows a remittance content input screen that can be displayed by accessing the bank server 111. Specifically, as shown on the display screen 600, each item of the remittance destination account number, the usual name, the recipient's name, the remittance amount, the subject, the authentication type, and the agent is input by the operation of the remittance sender 120. To.

On the display screen 600, the remittance destination account number is entered in "Remittance destination account number". For example, when the drop-down button 601a is selected by the sender 120, the pre-registered account number is displayed in a selectable manner. It is also possible to directly enter a number that is not registered in advance in the "remittance destination account number".

On the display screen 600, the nickname of the recipient 130 (for example, "Taro") is entered in the "ordinary name". For example, when the drop-down button 601e is selected by the sender 120, a pre-registered nickname is displayed in a selectable manner.

In addition, instead of the item of "usual name", the item of "for whom" may be used. The item "for whom" may simply replace the notation name of "ordinary name", that is, in the example of the display screen 600, it is possible to display the same tallow as the nickname. However, the item "for whom" can be, for example, the name of another person or the nickname of another person who can recall the recipient 130 to the sender 120.

In this way, even if the item is set to "for whom", it is possible to send an e-mail requesting consent to the e-mail address associated with the item "for whom" considered by the sender 120. Specifically, even if the remittance destination is an unexpected (first time) account, it is possible to send an e-mail requesting consent for remittance to the e-mail address associated with the selection result in the "For whom" item. it can.

When any one of the drop-down buttons 601a, 601b, and 601e is operated to select a value, the other two values may be determined according to the selection. Specifically, for example, if "Taro" is selected in the drop-down button 601e among the drop-down buttons 601a, 601b, and 601e, the bank server 111 refers to the recipient information DB 113 to "usually". Each of the recipient name "Sokentaro" and the account number "12345467" associated with "Taro" of the "call name" may be determined.

On the display screen 600, the name of the remittance destination is entered in the "recipient name". For example, when the drop-down button 601b is selected by the sender 120, the names of the pre-registered recipients 130 are displayed in a selectable manner.

On the display screen 600, the amount to be remitted is entered in "Remittance amount". The amount to be remitted can be arbitrarily determined by the sender 120. On the display screen 600, the title attached to the e-mail is input in the "subject".

One of password authentication, face authentication, and fingerprint authentication is entered in the "authentication type". For example, when the sender 120 selects the drop-down button 601c, one of them is input. However, in the "authentication type", the item "not selected" may be displayed so as to be selectable. When the "Do not select" item is selected, a specific authentication type (for example, password authentication) may be selected in advance, or the recipient 130 can arbitrarily select the authentication type. May be.

On the display screen 600, either "not specified" or "registered agent" is input as the "agent". For example, when the sender 120 selects the drop-down button 601d, one of them is input. If "Not specified" is selected, the recipient will be notified that the remittance will be made, and the recipient's consent will be required for the remittance. On the other hand, when "registered agent" is selected, the agent is notified that the remittance will be performed, and the consent of the agent is required for the remittance.

When the execution button 602 is operated by the remittance sender 120 on the display screen 600, the content shown on the display screen 600 is transmitted to the bank server 111. As a result, the operation performed on the remittance sender 120 side is completed. Although the case where the remittance request is made from the sender terminal 121 has been described, the remittance request can be made not only from the sender terminal 121 but also from the ATM. When making a remittance request from an ATM, the remittance request can be made from the same display screen as in FIG.

FIG. 7 is an explanatory diagram showing an example of a display screen of a confirmation email displayed on the recipient terminal 131. The display screen 700 of FIG. 7 shows a text screen of received mail. Specifically, the display screen 700 shows a notification 710 that the remittance to the recipient 130 will be performed. The notification 710 indicates that the recipient 130 can accept the consent of the remittance by accessing the site indicated by the URL (Uniform Resource Locator) 711.

Further, the display screen 700 shows an alarm 720. The alarm 720 indicates that the recipient 130 can accept that the remittance is not performed by accessing the site indicated by the URL 721. In addition, by accessing the site indicated by URL 721, it is possible to notify that a remittance that is unfamiliar to the person is about to be performed. As a result, for example, it is possible to prevent transfer fraud and provide information that leads to the identification of a criminal, and it is possible to take an appropriate initial response.

FIG. 8 is an explanatory diagram showing an example of a display screen when accepting remittance consent from the recipient 130. The display screen 800 of FIG. 8 shows a password input screen that can be displayed by accessing the site indicated by URL 711. When the recipient 130 inputs the password and the send button 801 is operated, the bank server 111 performs password authentication.

The display screen 800 shows a case where password authentication is performed. However, when face authentication is specified by the sender 120, the face is faced using the face image data of the recipient 130 transmitted from the recipient terminal 131. Authentication is done. When fingerprint authentication is specified by the sender 120, fingerprint authentication is performed on the recipient terminal 131, and the result is transmitted from the recipient terminal 131.

FIG. 9 is an explanatory diagram showing an example of a display screen when receiving a comment input from the recipient 130. When the comment is input by the recipient 130 and the send button 901 is operated on the display screen 900 of FIG. 9, the content of the comment is transmitted to the remittance terminal 121 via the bank server 111. On the other hand, when the end button 902 is operated, the process ends as it is.

Here, the comment may include the personal information of the recipient 130, and if the password and the personal information are associated and stolen, there is a risk of damage such as skimming. In the present embodiment, the comment and the password are not transmitted at the same time, but are transmitted separately.

Specifically, first, only the password will be sent, and then the comment will be sent. As a result, the password can be transmitted as simple character string data. Therefore, it is possible to prevent the password and personal information from being associated and stolen.

FIG. 10 is an explanatory diagram showing an example of a display screen of a notification of completion of the remittance procedure displayed on the recipient terminal 131. The display screen 1000 of FIG. 10 shows a screen to the effect that the remittance has been completed. As a result, the recipient 130 can know that the remittance procedure has been completed.

FIG. 11 is an explanatory diagram showing an example of a display screen of a remittance procedure completion notification displayed on the remittance sender terminal 121. The display screen 1100 of FIG. 11 shows a screen indicating that the remittance has been completed. As a result, the remittance sender 120 can know that the remittance procedure has been completed.

FIG. 12 is an explanatory diagram showing an example of a display screen of a cancellation notice indicating that the remittance procedure displayed on the remittance sender terminal 121 has been cancelled. The display screen 1200 of FIG. 12 shows a screen to the effect that the remittance has been canceled. For example, if the consent of the recipient 130 is not obtained within 24 hours, or if the recipient 130 accepts that the remittance will not be performed, the remittance procedure will be cancelled. The display screen 1200 allows the remittance sender 120 to know that the remittance procedure has been completed.

(Example of remittance support processing procedure according to this embodiment)
Next, an example of the remittance support processing procedure according to the present embodiment will be described with reference to FIGS. 13 to 16. FIG. 13 is a sequence diagram showing an example (No. 1) of the remittance support processing procedure according to the present embodiment.

In the sequence diagram of FIG. 13, the recipient terminal 131 requests the remittance terminal 121 for remittance (step S1301). An example of a remittance request screen is the display screen 500 shown in FIG. In the remittance request, the recipient terminal 131 transmits to the remittance terminal 121, for example, that a remittance of 5,000 yen is requested and that the subject of the e-mail sent from the bank server 111 is "Sakura no Kai".

Then, the remittance terminal 121 makes a remittance request to the bank server 111 (step S1302). As an example of the remittance request screen, for example, the display screen 600 shown in FIG. 6 can be mentioned. In the remittance request, the remittance terminal 121 transmits, for example, the remittance amount of 5,000 yen, the subject of the e-mail to be "Sakura no Kai", the authentication type, and the like to the bank server 111.

Then, the bank server 111 deposits an amount (5,000 yen) corresponding to the remittance amount into the separate account 1310 (step S1303). The separate account 1310 is an account within the financial period that is temporarily stored before the remittance procedure is completed. The funds stored in the separate account 1310 will be remitted to the designated account when certain conditions such as a predetermined date are met. No fee will be charged when transferring funds to another account 1310.

Then, the bank server 111 sends a confirmation email to the recipient terminal 131 indicating that the remittance will be performed (step S1304). The subject of the confirmation email is "Sakura no Kai". As a result, the recipient 130 can confirm that the e-mail contains the contents related to the remittance procedure without opening the e-mail. Therefore, the recipient 130 knows that the e-mail is not junk e-mail or the like, and can open the e-mail with peace of mind. As an example of the confirmation mail screen, the display screen 700 shown in FIG. 7 can be mentioned.

Then, the recipient terminal 131 accesses the bank server 111 to the predetermined site, and authentication is performed (step S1305). For example, as an example of the screen for performing authentication, the display screen 800 shown in FIG. 8 can be mentioned. In addition, a comment may be accepted from the recipient 130 in association with the authentication (see the display screen 900 in FIG. 9). As a result, the recipient can thank the sender and the sender can confirm that the remittance was successful from the comment of the sender.

Next, if the authentication is successful, the bank server 111 remits 5000 yen from the separate account 1310 to the recipient account (step S1306). A fee will be charged when transferring funds from the separate account 1310 to the recipient account. Then, the bank server 111 transmits a completion notification to the remittance terminal 121 and the recipient terminal 131 (step S1307). This completes a series of remittance support processes.

An example of the completion notification screen displayed on the recipient terminal 131 is the display screen 1000 shown in FIG. An example of the completion notification screen displayed on the remittance terminal 121 is the display screen 1100 shown in FIG.

In this way, since the remittance is executed with the consent of the recipient 130 whose contact information is registered in advance, the remittance to a stranger can be suppressed, and the remittance 120 can make a mistake in the address, duplicate remittances, etc. Remittances that the recipient 130 does not intend can be suppressed.

FIG. 14 is a sequence diagram showing an example (No. 2) of the remittance support processing procedure according to the present embodiment. The remittance support processing procedure shown in FIG. 14 differs from the remittance support processing procedure shown in FIG. 13 in that the remittance destination account number is not a pre-registered account number. In the following description, the same parts as those in FIG. 13 are designated by the same reference numerals, and the description thereof will be omitted.

In FIG. 14, for example, it is assumed that the recipient 130 makes a remittance request to an account that is not registered in advance. Specifically, it is assumed that the recipient 130 makes a remittance request such as "I want you to remit to the company account urgently".

In the sequence diagram of FIG. 14, the recipient terminal 131 registers a new account with the bank server 111 (step S1401). Then, the recipient terminal 131 requests the remittance terminal 121 to transfer money to the new account (step S1402).

Then, the remittance terminal 121 makes a remittance request to the new account to the bank server 111 (step S1403). The remittance request is made, for example, on the display screen 600 shown in FIG. 6, and the “remittance destination account number” is a newly designated number on the display screen 600.

Next, if the authentication is successful as shown in step S1305, the bank server 111 remits 5000 yen from the separate account 1310 to the new account (step S1404). As a result, according to the present embodiment, it is possible to transfer money to a new account. Therefore, even if the recipient 130 requests remittance to an account that is not registered in advance, the remittance person 120 can remit to the account with peace of mind.

FIG. 15 is a sequence diagram showing an example (No. 3) of the remittance support processing procedure according to the present embodiment. The remittance support processing procedure shown in FIG. 15 is different from the remittance support processing procedure shown in FIG. 13 in that the recipient terminal 131 is not used and the agent terminal 1500 is used. In the following description, the same parts as those in FIG. 13 are designated by the same reference numerals, and the description thereof will be omitted.

In FIG. 15, for example, it is assumed that the recipient 130 cannot request the remittance or approve the remittance, and the agent does the remittance. Specifically, for example, it is assumed that the recipient 130 is unconscious due to an illness or an accident, and the agent requests the remittance to remittance and approves the remittance.

In the sequence diagram of FIG. 15, the agent terminal 1500 requests the remittance terminal 121 to remit (step S1501). An example of the remittance request display screen is the display screen 500 shown in FIG. 5, but the sender is not the recipient 130 but an agent. In the remittance request, the agent terminal 1500 transmits to the remittance terminal 121, for example, that a remittance of 5,000 yen is requested and that the subject of the e-mail sent from the bank server 111 is "Sakura no Kai".

Then, the bank server 111 transmits a confirmation mail indicating that the remittance will be performed to the agent terminal 1500 after depositing the amount (5000 yen) corresponding to the remittance amount to the separate account 1310 (step S1303). (Step S1502). The subject of the confirmation email is "Sakura no Kai".

As a result, the agent can determine that the e-mail is related to remittance by the subject (title) of the e-mail, and can open the e-mail. An example of the confirmation mail screen is the display screen 700 shown in FIG. 7, but the recipient is not the recipient 130 but an agent.

Next, the agent terminal 1500 accesses the bank server 111 to a predetermined site, and authentication is performed (step S1503). For example, as an example of the screen for performing authentication, the display screen 800 shown in FIG. 8 can be mentioned, and the password of the agent is input as the password. In addition, comments may be accepted from an agent in connection with the authentication.

Then, if the authentication of the agent is successful, the bank server 111 remits 5000 yen from the separate account 1310 to the recipient account (step S1306), and in addition to the sender terminal 121 and the recipient terminal 131, the agent terminal A completion notification is also transmitted to 1500 (step S1504). This completes a series of remittance support processes.

In this way, even if the recipient 130 and the sender 120 cannot directly contact each other, such as when the recipient 130 is seriously ill or in critical condition, the recipient 130's agent accepts the remittance consent and receives the remittance. Remittance can be sent to person 130. Therefore, even if the agent requests remittance, the sender 120 can remit the remittance to the recipient 130 with peace of mind.

FIG. 16 is a sequence diagram showing an example (No. 4) of the remittance support processing procedure according to the present embodiment. The remittance support processing procedure shown in FIG. 16 is different from the remittance support processing procedure shown in FIG. 13 in that the authentication of the recipient 130 fails. In the following description, the same parts as those in FIG. 13 are designated by the same reference numerals, and the description thereof will be omitted.

In the sequence diagram of FIG. 16, as shown in step S1304, when a confirmation email is sent to the recipient terminal 131, the recipient terminal 131 accesses the bank server 111 to a predetermined site to perform authentication. However, it is assumed that the authentication fails (step S1601). Specifically, failure in authentication means that the recipient 130 makes a mistake in the password, the recipient 130 does not consent to the remittance, or the specified time (within 24 hours) after the confirmation email is sent. Includes no access to the site.

When the authentication fails in this way, the bank server 111 returns 5,000 yen from the separate account 1310 to the remittance sender account (step S1602). No fee will be charged when returning funds from the separate account 1310 to the remittance sender's account. Therefore, if the authentication fails, the money will not be sent to the recipient's account and no fee will be charged.

Here, once the remittance is sent to the remittance destination account that is not intended for the remittance sender 120, it may be troublesome or difficult to return the transferred funds, but in the present embodiment, the recipient Since the funds are not transferred to the designated account until the authentication of 130 is successful, the funds can be easily returned from the separate account 1310 to the remittance account if the authentication of the recipient 130 fails.

Then, the bank server 111 transmits a cancellation notice to the remittance terminal 121 (step S1603). This completes a series of remittance support processes. An example of the cancellation notification screen displayed on the remittance terminal 121 is the display screen 1200 shown in FIG.

In this way, if the authentication fails, the remittance request is canceled, so that the remittance 130 unintentional, such as a transfer fraud, can be suppressed. In addition, if the authentication fails, a cancellation notice is given, so that the remittance sender 120 can be made aware of that fact. As a result, it is possible to take a prompt initial response to crimes such as transfer fraud.

(Remittance support processing procedure performed by bank server 111)
FIG. 17 is a flowchart showing an example of the remittance support processing procedure performed by the bank server 111. In the flowchart of FIG. 17, the bank server 111 determines whether or not the remittance request (see FIG. 6) has been accepted from the remittance terminal 121 (step S1701). The bank server 111 waits until the remittance request is received from the remittance terminal 121 (step S1701: No).

Then, when the bank server 111 receives the remittance request from the remittance terminal 121 (step S1701: Yes), the bank server 111 deposits the remittance amount into another account (step S1702). Then, it is determined whether or not the remittance request from the remittance terminal 121 is designated as an agent (step S1703). When no agent is specified (step S1703: No), the bank server 111 refers to the recipient information DB 113 (see FIG. 3B) and acquires the email address of the recipient 130 (step S1704).

When the agent is designated (step S1703: Yes), the bank server 111 refers to the agent information DB 114 (see FIG. 3C) and acquires the agent's e-mail address (step S1705). Then, the bank server 111 sends a confirmation email (see FIG. 7) to the acquired email address (step S1706).

Next, the bank server 111 determines whether or not the authentication (see FIG. 8) is successful (step S1707). The authentication referred to here includes the consent of the recipient 130 in addition to the authentication such as password authentication. If the authentication is not successful (step S1707: No), the bank server 111 determines whether or not a predetermined time (for example, 24 hours from the transmission of the confirmation email) has elapsed (step S1708).

When the predetermined time has not elapsed (step S1708: No), the bank server 111 determines whether or not it is the re-request timing (step S1709). The re-request timing is, for example, an hourly timing. By re-requesting, the recipient 130 can be urged to read the confirmation email and consent to the remittance.

If it is not the re-request timing (step S1709: No), the bank server 111 proceeds to step S1707. When it is the re-request timing (step S1709: Yes), the bank server 111 proceeds to step S1706.

When the predetermined time has elapsed (step S1708: Yes), the bank server 111 returns the remittance amount from the separate account to the sender account (step S1710), and sends a cancellation notice (see FIG. 12) to the sender terminal 121 (see FIG. 12). Step S1711), the series of processes according to this flowchart is completed.

When the bank server 111 succeeds in authentication (step S1707: Yes), specifically, when the authentication such as password authentication is successful and the consent of the recipient 130 is obtained, the remittance amount is transferred from the account to the recipient. It is transferred to the account (step S1712), a completion notification (see FIGS. 10 and 11) is transmitted to the sender terminal 121 and the recipient terminal 131 (step S1713), and a series of processes according to this flowchart is completed.

As described above, when the bank server 111 according to the present embodiment receives a remittance request from the sender 120 to the recipient 130 whose contact information is registered in advance, the remittance received from the recipient 130 is received. It was decided to carry out the remittance in response to the consent to be made.

As a result, it is possible to transfer money only to a person whose contact information is registered in advance, but not to a person whose contact information is not registered in advance. Therefore, since it is possible to prevent remittances to strangers, it is possible to suppress remittances that the sender 120 does not intend, and it is particularly effective as a countermeasure against fraud that deceives relatives (so-called transfer fraud).

Further, according to the bank server 111 according to the present embodiment, it is considered that the recipient 130 whose contact information is registered and the recipient 130 who actually receives the remittance are the same person, and the consent of the recipient 130 is obtained. You can get and transfer money. Therefore, it is possible to suppress an unintended remittance by the recipient 130, which may occur due to a misunderstanding that the sender 120 makes a mistake in the destination or an erroneous operation such as duplicate remittance.

As a result, the bank server 111 can suppress remittances that are unintended for both the recipient 130 and the sender 120. Therefore, according to the present embodiment, remittance can be performed with peace of mind, and a sound remittance service can be provided.

Further, according to the bank server 111 according to the present embodiment, since the consent includes the authentication performed by the recipient 130, the recipient 130 whose contact information is registered and the recipient 130 who actually receives the remittance. It is possible to improve the accuracy of confirmation that the items are the same (identity verification). As a result, according to the bank server 111, remittances to strangers can be prevented, and remittances that the recipient 130 does not know, such as transfer fraud, can be suppressed.

In addition, the recipient 130 notifies that the remittance will be performed to the other recipient terminal 131 for which the contact is not registered because the recipient terminal 131 for which the contact is registered has broken down. It is assumed that the sender 120 has a request for the request. In this case, the notification destination may be changed to another recipient terminal 131 by the operation of the remittance sender 120.

In this case, by including the authentication performed by the recipient 130 when accepting the remittance, the recipient 130 having another recipient terminal 131 whose contact information is not registered and the recipient who actually receives the remittance. It is possible to confirm that the 130 is the same (identity verification). Therefore, even when the recipient 130 uses another recipient terminal 131 for which no contact information is registered, it is possible to suppress remittances that the recipient 130 does not know, such as transfer fraud.

Further, according to the bank server 111 according to the present embodiment, a predetermined character string (for example, "Sakura no Kai") is used for the remittance request addressed to the recipient 130, and a notification including the predetermined character string is given. did. Thereby, it is possible to indicate to the recipient 130 that the notification is related to the remittance before the recipient 130 confirms the notification, for example, when the notification is received.

Specifically, the bank server 111 can indicate that the e-mail has the content related to remittance by using the character string in the subject of the e-mail without having the recipient 130 open the e-mail. Therefore, the recipient 130 knows that the e-mail is not junk e-mail or the like, and can open the e-mail with peace of mind. Therefore, according to the bank server 111, it is possible to prevent the confirmation email from being unopened and consent not being obtained.

In addition, the bank server 111 according to the present embodiment receives a remittance request from the sender 120 when consent is not accepted within a predetermined period (for example, 24 hours) after the notification is given. I decided to cancel. As a result, the bank server 111 can cancel the remittance request by regarding the recipient 130 as having no intention of receiving the remittance after the lapse of a predetermined period, and can suppress the remittance unintended by the recipient 130.

Further, the bank server 111 according to the present embodiment cancels the remittance request received from the remittance sender 120 when it is received that the remittance is not performed. As a result, the bank server 111 can prevent the recipient 130 from making an unintended remittance.

In addition, since the sender 120 has an intention of remittance and the recipient 130 has no intention of receiving it, it is suspected that there is a possibility of a crime such as transfer fraud. For this reason, the designated account of the remittance destination can be alerted that it may be used for a crime, and measures can be taken to prevent the crime.

Further, when the remittance request is canceled, the bank server 111 according to the present embodiment notifies the remittance sender terminal 121 to that effect. As a result, the remittance sender 120 can know that the remittance request has been cancelled. For this reason, the remittance sender 120 can confirm with the remittance recipient 130 regarding the remittance and take a prompt initial response to a crime such as a transfer fraud, and in some cases, make a remittance request again and remittance. Can be done.

Further, when the bank server 111 according to the present embodiment receives the remittance request, it notifies the contact information of the agent that the remittance will be performed, and executes the remittance by receiving the consent from the agent. It was possible. Therefore, the bank server 111 can equate the agent whose contact information is registered with the recipient 130, and execute the remittance to the recipient 130 with the consent of the agent.

As a result, according to the bank server 111, even if the recipient 130 and the remittance 120 cannot be directly contacted, for example, when the recipient 130 is seriously ill or in critical condition, the agent of the recipient 130 Since the remittance consent can be accepted and the remittance can be sent to the recipient 130, the convenience of the remittance support method according to the present embodiment can be improved.

Further, the bank server 111 according to the present embodiment uses one or more types of authentication received from the sender 120 among a plurality of types of authentication for the authentication used when accepting the remittance. In this way, by letting the sender 120 select the authentication type without letting the recipient 130 select the authentication type, for example, when a transfer fraud is assumed, the sender 120 selects the authentication type. If the authentication differs from the authentication provided by the criminal, the criminal cannot succeed in the authentication. As a result, the security of authentication can be strengthened, and transfer fraud can be suppressed.

The remittance support method described in the present embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation.

The remittance support program includes hard disk, flexible disk, CD (Compact Disk) -ROM (Read Only Memory), MO (Magnet-Optical disk), DVD (Digital Versaille Disk), USB (Universal Personal Computer Bus), etc. It is stored on a possible storage medium and executed by being read from the storage medium by a computer. In addition, the remittance support program may be distributed via a network such as the Internet.

As described above, the remittance support device, the remittance support method, and the remittance support program according to the present invention are useful for the remittance support device, the remittance support method, and the remittance support program. Suitable for remittance support devices, remittance support methods, and remittance support programs that send money to registered recipients 130.

100 Remittance support system 110 Bank 111 Bank server 112 Remittance sender information database (DB)
113 Recipient Information Database (DB)
114 Representative Information Database (DB)
115 Transaction Information Database (DB)
120 Sender 130 Recipient 121 Sender terminal 131 Recipient terminal 140 Network 211,221 CPU
212,222 Memory 213,225 Communication IF
223 Output device 224 Input device 210, 220 Bus 401 Notification unit 402 Reception unit 403 Remittance control unit

Claims (8)

When a request to make a remittance with the subject of the email sent from the recipient terminal to the recipient whose contact information is registered in advance is accepted as the title, the remittance will be made to the recipient. Notification section that notifies
The reception department that accepts the consent of the remittance to be made by the notification from the recipient, and
A remittance control unit that executes the remittance in response to the consent received by the reception unit, and
A remittance support device characterized by being equipped with. The consent includes the authentication of the recipient.
The remittance support device according to claim 1. The notification unit, when received from the sending a request money who comprising an input of a predetermined character string indicating the transfer, performs the notification containing the predetermined character string,
The remittance support device according to claim 1 or 2. The remittance control unit has received a notification that the consent is not accepted by the reception unit or that the remittance is not performed by the reception unit between the time when the notification is given and the time when the predetermined period elapses. in the case, to cancel the request received from the sending gold's,
The remittance support device according to any one of claims 1 to 3, wherein the remittance support device is characterized. The notification unit, and the request to the effect that performing the remittance addressed to the recipient, in advance contact was registered, in the case where the received from the recipient of gold who sent the effect that a notice to the agent, The agent is notified and the agent is notified.
The reception unit receives the consent from the agent by the notification, and receives the consent.
The remittance control unit executes the remittance to the recipient in response to the consent from the agent.
The remittance support device according to any one of claims 1 to 4, wherein the remittance support device is characterized. The notification includes a reception result received from gold's feeding one or more authentication to be performed by the recipient from the plurality of types of authentication,
The certification is the type of certification indicated by the reception result.
The remittance support device according to any one of claims 1 to 5, wherein the remittance support device is characterized. When a request to make a remittance with the subject of the email sent from the recipient terminal to the recipient whose contact information is registered in advance is accepted as the title, the remittance will be made to the recipient. Notify
Accepting the consent from the recipient that the remittance will be made by the notification,
Execute the remittance according to the received consent.
A remittance support method characterized by a computer performing processing. When a request to make a remittance with the subject of the email sent from the recipient terminal to the recipient whose contact information is registered in advance is accepted as the title, the remittance will be made to the recipient. Notify
Accepting the consent from the recipient that the remittance will be made by the notification,
Execute the remittance according to the received consent.
A remittance support program characterized by having a computer perform processing.

Images