JP5292056B2 - Personal remittance system and remittance management server - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a person-to-person money transfer system and a money transfer management server allowing easy money transfer from person to person. <P>SOLUTION: The person-to-person money transfer system for transferring money from a sender to a beneficiary includes: a first terminal 11 for transmitting a money transfer request such that the beneficiary is the recipient; and a money transfer management server 16 which receives the money transfer request from the first terminal 11, transmits a confirmation of reception based on the received money transfer request, for confirming the will to receive, to a second terminal 12 associated with the beneficiary, performs payment to the beneficiary upon receiving a notification of confirmation from the second terminal 12 in response to the confirmation of reception, and charges the sender or the beneficiary with the amount of money regarding the payment. <P>COPYRIGHT: (C)2010,JPO&amp;INPIT

Description

  The present invention relates to an inter-individual remittance system and a remittance management server, and relates to an inter-individual remittance system and a remittance management server for performing remittance from a first terminal to a second terminal.

Conventionally, when giving and receiving money between individuals, there are a method in which the persons meet each other and hand them over, or a method in which a bank transfer is made to the recipient's account in a bank. However, in the method of handing, the persons need to meet each other directly, and when making an account transfer, the sender needs to know the bank account number of the recipient.
On the other hand, when both the sender and the receiver are users of the mobile terminal device, electronic money obtained by converting monetary values into data is directly communicated from the sender's mobile terminal device to the receiver's mobile terminal device or via a network. The method of transmitting is considered (refer patent document 1). According to these methods, since the sender does not need to know the bank account number of the recipient, it is considered that money can be easily exchanged.
JP 2006-221295 A

  However, in this method, in response to the electronic money being transferred from the sender to the receiver, the amount of electronic money held by the sender is subtracted and the amount of electronic money held by the receiver is added. It is assumed that the environment in which the sender and the receiver exchange electronic money is prepared (that is, the electronic money of the sender and the receiver is managed by the server).

  Thus, in the past, it was difficult to transfer money as if the cash was handed over between the sender and the receiver.

  The present invention has been made in view of such a point, and an object thereof is to provide an inter-individual remittance system and a remittance management server capable of easily performing remittance between individuals.

The inter-individual remittance system according to the present invention is an inter-individual remittance system for performing remittance from a remittance source to a remittance destination, the first terminal for transmitting a remittance request with the remittance destination as the recipient, A receipt confirmation for confirming the intention of receipt is transmitted to the second terminal associated with the remittance destination based on the received remittance request, and the second confirmation for the receipt confirmation is received. with the case of receiving an acknowledgment from the terminal to execute the payment to the payee, the amount of the payment, charging for the transfer source or the transfer destination, transfer if it does not receive the acknowledgment characterized in that it comprises a and a remittance management server that holds point of for the data receiver.

  According to this configuration, the remittance management server performs payment to the remittance destination (recipient) and charges to the remittance source (sender) or remittance destination (recipient) without sending and receiving cash between the mobile terminal devices. Thus, it is possible to obtain the same result as when there is substantially cash transfer. Thereby, remittance can be easily performed between individuals.

In the inter-individual remittance system, the remittance management server stores remittance data each time based on the remittance request, and stores the remittance data when the confirmation notification is not received within a certain period. Is preferably pointed and held for the receiver.
Furthermore, in the inter-individual remittance system according to the present invention, the remittance management server issues a personal number of the remittance destination and recognizes a remittance request addressed to the issued personal number as a remittance request to the remittance destination. Is preferred. In this case, remittance can be performed with the personal information of the sender and the recipient's bank account numbers hidden, and remittance can be performed while maintaining confidentiality.

  In the inter-individual remittance system according to the present invention, it is preferable that the remittance management server holds a telephone number of the remittance destination and recognizes a remittance request to the telephone number as a remittance request to the remittance destination. In this case, the remittance can be easily performed by specifying the individual by the mobile phone number of the sender or receiver and performing the remittance. In particular, when a communication carrier performs an inter-individual remittance system, it becomes possible to recognize a sender and a receiver based on a telephone number, and a reliable remittance process can be performed.

  In the inter-individual remittance system according to the present invention, the remittance source or the remittance destination concludes in advance a contract for receiving a service provision using the first terminal or the second terminal, and the remittance management server It is preferable that an amount to be received by the billing is included in a consideration to be received from the remittance source or the remittance destination for the service provision. In this case, the remittance source or remittance will receive the provision of the inter-individual remittance service on the condition that the remittance source or remittance has in advance an agreement with the provider of the inter-individual remittance system. By doing so, when the service provider of the inter-individual remittance system makes payment to the remittance destination, it is possible to reliably charge the remittance source or remittance destination.

  In the inter-individual remittance system according to the present invention, it is preferable that the remittance source or the remittance destination is charged after execution of payment to the remittance destination. In this case, it is possible to charge the remittance source or the remittance destination as compensation for the service of payment (remittance) to the remittance destination.

  In the inter-individual remittance system according to the present invention, it is preferable that payment to the remittance destination is executed after charging to the remittance source or the remittance destination. In this case, after the remittance amount from the remittance source or remittance is confirmed, payment to the remittance destination can be performed, so that the remittance amount becomes difficult to collect from the remittance source or remittance destination. Can be prevented in advance.

  Further, according to the present invention, in the inter-individual remittance system, the payment to the remittance destination is a transfer to a designated account designated by the remittance destination or the remittance destination receives a predetermined service according to the designation by the remittance destination. It is preferred that any of the allocations for the points to be selected. In this case, since the remittance destination can select a method of receiving the remittance amount, the convenience of the remittance destination can be improved.

The remittance management server of the present invention is a remittance management server of an inter-individual remittance system that performs remittance from a remittance source to a remittance destination, and receives a remittance request from the first terminal as a recipient. based on the remittance sends said acknowledgment to confirm the intention of receiving the second terminal associated with the payee, upon receiving an acknowledgment from the second terminal to the confirmation preparative receiving and it executes the payment to the payee in the amount of the payment, charging for the transfer source or the transfer destination when not receiving the confirmation notification point the remittance data for said recipient It is characterized by holding .

  According to this configuration, the remittance management server performs payment to the remittance destination (recipient) and charges to the remittance source (sender) or remittance destination (recipient) without sending and receiving cash between the mobile terminal devices. Thus, it is possible to obtain the same result as when there is substantially cash transfer. Thereby, remittance can be easily performed between individuals.

In the remittance management server, remittance data is stored each time based on the remittance request, and when the confirmation notification is not received within a certain period, the stored remittance data is pointed for the receiver. It is preferable to make it hold.
In the present invention, it is preferable that the remittance management server issues a personal number of the remittance destination and recognizes a remittance request addressed to the issued personal number as a remittance request to the remittance destination. In this case, remittance can be performed with the personal information of the sender and the recipient's bank account numbers hidden, and remittance can be performed while maintaining confidentiality.

  In the present invention, it is preferable that the remittance management server holds a telephone number of the remittance destination and recognizes a remittance request to the telephone number as a remittance request to the remittance destination. In this case, the remittance can be easily performed by specifying the individual by the mobile phone number of the sender or receiver and performing the remittance. In particular, when a communication carrier performs an inter-individual remittance system, it becomes possible to recognize a sender and a receiver based on a telephone number, and a reliable remittance process can be performed.

  According to the present invention, in the remittance management server, an amount to be received by the billing as a consideration to be received from the remittance source or the remittance destination for the service provided to the first terminal or the second terminal. It is preferable to include. In this case, on the condition that the remittance source or the remittance party has previously made a contract for providing any service with the provider of the inter-individual remittance system, the remittance source or the remittance destination provides the inter-individual remittance service. By accepting the payment, when the service provider of the inter-individual remittance system pays the remittance destination, it is possible to reliably charge the remittance source or the remittance destination.

  In the present invention, the remittance management server preferably charges the remittance source or the remittance destination after execution of payment to the remittance destination. In this case, it is possible to charge the remittance source or the remittance destination as compensation for the service of payment (remittance) to the remittance destination.

  In the present invention, the remittance management server preferably executes payment to the remittance destination after charging to the remittance source or the remittance destination. In this case, after the remittance amount from the remittance source or remittance is confirmed, payment to the remittance destination can be performed, so that the remittance amount becomes difficult to collect from the remittance source or remittance destination. Can be prevented in advance.

  Further, according to the present invention, in the remittance management server, the payment to the remittance destination is because the transfer to the designated account designated by the remittance destination or the remittance destination receives a predetermined service according to the designation by the remittance destination. It is preferable that any of the allocation to the points is selected. In this case, since the remittance destination can select a method of receiving the remittance amount, the convenience of the remittance destination can be improved.

  ADVANTAGE OF THE INVENTION According to this invention, the remittance system between individuals and the remittance management server which can perform remittance easily between individuals can be provided.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
(First embodiment)
FIG. 1 is a diagram showing a schematic configuration for explaining an inter-individual remittance system (communication system) according to an embodiment of the present invention. The communication system shown in FIG. 1 connects mobile terminals 11 and 12 to a network 15 via a mobile communication network 13 and mobile terminals (first and second terminals) 11 and 12 that can be connected to a network 15 such as the Internet. And a P2P server (remittance management server) 16 connected to the network 15.

  The mobile terminals 11 and 12 include a plurality of communication system interfaces, for example, mobile communication interfaces. The mobile terminals 11 and 12 have an operating system (mobile device OS), and a browser function and other functions operate on the mobile device OS. Further, the mobile terminals 11 and 12 have a normal telephone function and a mail function.

  The mobile communication network 13 is a network between the mobile terminals 11 and 12 and the mobile communication center 14. The mobile communication network 13 includes a mobile packet communication network in addition to a normal mobile communication network. The mobile communication center 14 has, for example, an i-mode (registered trademark) server and the like, and has a gateway function for connecting the mobile communication network 13 to another network 15 such as the Internet. It has a distribution function, a mail transmission / reception function, and the like.

  FIG. 2 is a block diagram showing a schematic configuration of the mobile terminal 11 in the system shown in FIG. Note that the configuration shown in FIG. 2 is simplified for explaining the present invention, and it is assumed that the components mounted on a normal mobile terminal are provided. FIG. 2 shows the configuration of the mobile terminal 11, but the other mobile terminals 12 have the same configuration.

  The mobile terminal 11 includes a control unit 21 that controls the entire apparatus, a communication control unit 22 that communicates with the mobile communication center 14 (FIG. 1) via the mobile communication network 13, and various data. A display unit 23 for displaying, an operation unit 24 for performing various operations, a microphone 25 for inputting sound, a speaker 26 for outputting sound, an imaging unit 27 for capturing an image with a camera function, and imaging It mainly includes a storage unit 28 that stores data of an image captured by the unit 27, and an application control unit 29 that activates various applications that are installed in the device or downloaded.

  The communication control unit 22 communicates with the mobile communication center 14 via the mobile communication network 13 using a mobile communication interface. The communication control unit 22 sends an audio signal converted into an electric signal via the microphone 25 to the mobile communication center 14 via the mobile communication network 13 and receives it from the mobile communication center 14 via the mobile communication network 13. The sound signal thus output is output as sound through the speaker 26. Further, the communication control unit 22 displays the information received from the mobile communication center 14 via the mobile communication network 13 on the display unit 23. When an imaging command is input via the operation unit 24, the imaging unit 27 captures a subject image through a lens (not shown) provided in the housing of the mobile terminal 11, and the subject image is electrically converted by a photoelectric conversion element. Image data is obtained by converting the signal. This image data is stored in a storage unit 28 having, for example, a RAM (Random Access Memory) configuration. The application control unit 29 activates an application for uploading data that is installed in the device or downloaded.

  FIG. 3 is a block diagram showing a schematic configuration of the mobile communication center 14 in the system shown in FIG. The mobile communication center 14 includes a control unit 31 that controls the entire apparatus, a communication control unit 32 that performs communication by mobile communication with the mobile terminals 11 and 12 via the mobile communication network 13, and a communication service destination. A management database (DB) 34 to be managed and an information update unit 33 for updating information in the management database 34 are mainly configured.

  The communication control unit 32 communicates with the mobile terminals 11 and 12 via the mobile communication network 13 using a mobile communication interface.

  The management DB 34 has a table as shown in FIG. 4, for example. The table shown in FIG. 4 manages the communication service provider for each user. The items managed in the table are not limited to the items shown in FIG. 4 and can be changed as appropriate.

  Next, the P2P server 16 will be described. The P2P server 16 registers index information about each mobile terminal 11 and 12 as an application function for realizing peer-to-peer, and in response to a request from a certain mobile terminal 11 or 12, a desired Notify the location of information. The mobile terminals 11 and 12 that have received this notification need to communicate with other mobile terminals 11 and 12 directly by accessing an address indicating the location of the required information based on the notification. Information is exchanged directly.

  That is, FIG. 5 is a block diagram showing a schematic configuration of the P2P server 16. The P2P server 16 communicates with the mobile terminals 11 and 12 connected to the mobile communication network 13 by communicating with the mobile communication center 14 via the network 41 such as the Internet and the CPU 41 that controls the entire apparatus. A device 45, a storage device 44 for registering the location of each information (mobile terminals 11 and 12), a reading device 47 for reading information from a recording medium 48 in which various programs and data are recorded, and various operations depending on the operation of the operator. Are mainly composed of an input device 42 for inputting data and commands and a display device 46 for displaying the operating state of the system.

  In response to requests from the mobile terminals 11 and 12, the CPU 41 issues a unique personal number to each. This personal number is issued by making a request to the P2P server 16 from each mobile terminal 11, 12 when the mobile terminal 11, 12 (sender, receiver) wants to send money anonymously. Is. This personal number is notified to the issue request source (mobile terminals 11, 12) and is stored in the storage device 44.

  The transmission / reception device 45 communicates with the mobile communication center 14 via the network 15 by a network interface. The storage device 44 stores terminal information such as mobile phone numbers uploaded from the mobile terminals 11 and 12 via the mobile communication center 14. In this storage device 44, the above-mentioned personal number is stored in association with the mobile phone number of the mobile terminal 11 or 12 corresponding to the case where the personal number is issued. Along with the mobile phone number of the recipient of the remittance (including a personal number if necessary), the remittance request amount is stored in the recipient user database. Further, in the storage device 44, when the receiver desires “appropriation” to be described later as a receiving method, the amount allocated to the “appropriation” is stored in the receiver user allocation point database (described later).

  Next, processing for performing remittance between individuals between the mobile terminals 11 and 12 in the communication system 10 will be described. In the inter-individual remittance process according to the present embodiment, a sender as a remittance source (in the following description, the mobile terminal 11 is a sender) and a receiver as a remittance destination (in the following description, the mobile terminal 12 is connected). The remittance data transmitted from the sender is stored in the P2P server 16 as an “instruction”. The P2P server 16 is a server operated by a provider that provides a service related to the inter-individual remittance process. In this embodiment, the P2P server 16 corresponds to a communication carrier that operates the mobile communication center 14. The sender sends the remittance data to the P2P server 16, and the receiver holds the remittance data sent to the P2P server 16 as an “instruction” and processes this “instruction” within a certain period (cashing, appropriating , Reception rejection (details of which will be described later) can be made.

  “Cashing” means that the P2P server 16 transfers an amount corresponding to the remittance data from a specific bank account to the receiving bank account in response to a request for cashing from the receiving mobile terminal 12. The specific bank account is, for example, a bank account of a provider that provides a service related to the inter-individual remittance process, or an account of a service provider that provides a mobile communication service (an administrator of the mobile communication center 14). It is done.

  “Appropriation” means that the amount corresponding to the remittance data is allocated to the mobile phone usage fee of the mobile terminal 12 or so-called wallet payment, for example, in the P2P server 16 in response to an allocation request from the mobile terminal 12 as the receiver. It means to do. By the way, wallet mobile is a service that uses a mobile phone to make payments for shopping, etc. on the data and allows the payment amount to be paid later by bank withdrawal, etc. This means a service for making payments such as shopping.

  “Rejection rejection” means that the P2P server 16 treats the stored remittance data from the sender as reception rejection in response to a reception rejection request from the mobile terminal 12 that is the receiver. Here, the operation in which the mobile terminal 12 that is the receiver transmits a cashing request, an allocation request, or a reception rejection request to the P2P server 16 is referred to as “instruction” execution.

  If the receiver does not execute the “instruction” within a certain period, the P2P server 16 stores the remittance data as a point for the receiver. This point is used for various services for recipients. For example, it is used as a point for a service provided to a receiver by a telecommunications carrier providing this inter-individual remittance service.

  Next, the processing procedure of the personal remittance service according to the present embodiment will be described. In the case of performing anonymous remittance between the sender and the receiver, the P2P server 16 issues a personal number associated with the mobile phone number of the mobile terminal 12 of the receiver in advance and also carries the mobile terminal 11 of the sender. A personal number associated with the telephone number is issued, and the sender (mobile terminal 11) designates the personal number of the receiver (mobile terminal 12) and transfers the remittance data. On the other hand, when a remittance with a real name is performed between the sender and the receiver, the sender (mobile terminal 11) transmits the remittance data by designating the telephone number of the mobile terminal 12 of the receiver. In addition, when making a remittance anonymously between the sender and the receiver, for example, the sender and the receiver each access the auction site, exchange their personal numbers with each other anonymously, and send the auctioned amount. A case where the hand transmits to the receiver can be assumed. In this case, the sender and the receiver exchange the personal numbers of each other, and the auction site performs the remittance process on behalf of the sender and the receiver as the inter-individual money transfer service provider. On the other hand, when the sender and the receiver perform the remittance without being anonymous, when the other party's mobile phone number is known, the mobile phone number is used, and the inter-individual money transfer service provider is provided via the P2P server 16. To send money.

  FIG. 6 is a diagram for explaining the recipient's personal number issuing process by the P2P server 16 of the inter-individual remittance system provided by the communication carrier. As shown in FIG. 6, the receiver (mobile terminal 12) transmits a personal number confirmation request to the P2P server 16 (step ST11). This confirmation request uses an application held by the mobile terminal 12 that transmits this request or Web access to the P2P server 16. The P2P server 16 that has received the confirmation request issues a personal number to the receiver (mobile terminal 12) (step ST12), and the correspondence between the issued personal number and the mobile phone number of the receiver (mobile terminal 12) As a result, the storage device 44 (FIG. 5) creates a database (step ST13). Then, the P2P server 16 transmits the personal number issued to the receiver (mobile terminal 12) to the receiver (mobile terminal 12) (step ST14). As a result, the receiver (mobile terminal 12) can urge the sender (mobile terminal 11) to notify the receiver (mobile terminal 12) of the personal number of the receiver (mobile terminal 12), thereby prompting remittance specifying the personal number ( Step ST15). The personal number issued in the P2P server 16 is issued only once for each individual, and is not issued twice. This personal number can be confirmed at any time on the P2P server 16 or a web page dedicated to the charge information service of the mobile phone.

  In FIG. 7, the sender (mobile terminal 11) designates the personal number or mobile phone number of the receiver (mobile terminal 12), the sender (mobile terminal 11) transmits the remittance data to the P2P server 16, and the receiver (mobile terminal 11) The mobile terminal 12) is a diagram showing a processing procedure in the case where the amount specified in the remittance data is received (rejection is refused).

  As shown in FIG. 7, the recipient (mobile terminal 12), as described above with reference to FIG. 6, is in the state of having already issued his personal number to the sender (mobile terminal 11). A reminder mail is transmitted (step ST21). At this time, the receiver (mobile terminal 12) transmits his / her personal number or mobile phone number attached to the reminder mail.

  The sender (mobile terminal 11) designates the individual number or mobile phone number of the receiver in response to the reminder mail from the receiver, and transmits the amount to be transmitted to the P2P server 16 as remittance contact data (step ST22). . It is assumed that the sender (mobile terminal 11) has a contract with a communication carrier to receive a payment service using the above-described mobile phone called a wallet mobile phone.

  When the P2P server 16 receives the remittance contact data from the sender (mobile terminal 11), the P2P server 16 associates the amount included in the remittance contact data with the personal number or mobile phone number of the recipient in the storage device 44 (FIG. 5). Store (step ST23). As a result, a receiver user database associated with the receiver's personal number or mobile phone number is created in the storage device 44 of the P2P server 16. In this receiver user database, the amount of remittance data transmitted to the P2P server 16 with the receiver (user identified by personal number or mobile phone number) as the remittance destination is stored each time. If the recipient is within the accumulated amount, the recipient can specify a desired amount and pay it to the recipient (“cash”, “appropriate”). When the amount in the receiver user database is used for payment to the receiver, the amount is subtracted from the database.

  In step ST23, when the amount included in the remittance contact data from the sender is stored in the receiver database, the P2P server 16 transmits a receipt confirmation mail to the receiver (mobile terminal 12) (step ST24). This receipt confirmation mail includes the personal number or mobile phone number of the sender (mobile terminal 11). In this way, by transmitting information (personal number or mobile phone number) that can identify the sender together with the receipt confirmation mail, the receiver (mobile terminal 12) can confirm who the remittance source is. .

  The recipient (mobile terminal 12) that has received the receipt confirmation mail transmits the receipt method to the P2P server 16 as a receipt contact mail within a predetermined period (for example, N days) (step ST25). This receiving method includes “cashing”, “appropriation”, and “rejection refusal” as described above. The recipient selects one of these and sends it as a receipt contact mail. The P2P server 16 that has received the receipt contact mail from the receiver (mobile terminal 12) determines the method of processing the remittance amount according to the receipt method included in the receipt contact mail (step ST26). That is, when “cash” is designated, the remittance amount is transferred to a bank account registered in advance by the receiver. Note that, as described above, this transfer source is a bank account of a provider (such as a telecommunications carrier) that provides the inter-individual money transfer service. When “appropriate” is designated, the amount corresponding to the remittance data is stored in a receiver user appropriation point database (not shown) for appropriating the mobile phone usage fee of the mobile terminal 12. If “reception refusal” is designated, the remittance data is treated as a reception refusal. In addition, when the receiver does not transmit the receipt contact mail within a certain period (for example, N days) (that is, when the receiver does not execute “instruction”), the P2P server 16 receives the remittance data in the receiver user appropriation point database. By storing, it points and holds for the service to the recipient.

  When the remittance amount processing method is determined in this way, the P2P server 16 transmits the result to the sender (mobile terminal 11) as a remittance request result notification (step ST27). This remittance request result notification is sent to the sender up to N days after the remittance contact from the sender in consideration of the waiting period when the receiver does not send the receipt contact mail. Then, the P2P server 16 transmits a remittance request result notification to the sender (mobile terminal 11), and performs billing processing for the amount corresponding to the remittance amount to the receiver (step ST28). In the present embodiment, the case where the accounting process is performed on the sender (remittance source) is described. However, the present invention is not limited to this, and the accounting process is performed on the receiver (remittance destination). It can also be done. In this case, for example, the receiver (remittance destination) concludes a contract for receiving service using the mobile terminal 12 in advance, and the receiver (remittance destination) is charged for the service of payment (remittance) to the remittance destination. You just have to do it. In addition, if payment is made to the receiver (remittance destination) after the receiver (remittance destination) is charged, after the remittance amount from the receiver (remittance destination) is ensured, Therefore, it is possible to prevent inconvenience that it becomes difficult to collect the remittance amount from the remittance destination.

  FIG. 8 is a diagram showing a detailed processing procedure when the recipient wishes to “cash” as the receiving method in the receiving contact mail in step ST25 shown in FIG. As shown in FIG. 8, the recipient (mobile terminal 12) transmits a receipt intention contact mail designating “cashing” as the receipt method to the P2P server 16 (step ST31). This receipt intention communication mail includes the amount desired to be received by the input operation of the recipient. The P2P server 16 determines whether or not an amount equal to or greater than the amount corresponding to the database (receiver user database (DB)) in which the amount waiting for the receiver's receipt request is stored is stored. Transmits a remittance request result including the intention to receive and the receiving method to the sender (mobile terminal 11) (step ST32). In addition, the P2P server 16 performs the same amount of charging processing for the sender. As a result, when the recipient wishes to receive and sends a receipt intention contact mail, and the recipient user database pays the desired amount to the recipient, billing processing for that amount is executed for the sender (step ST33). ).

  Then, the P2P server 16 makes a transfer request from the bank account of the inter-individual remittance service provider (communication carrier etc.) to the recipient bank account (step ST34). Thereby, the transfer from the provider's bank account to the recipient's bank account (designated account) is performed (step ST35).

  In this way, when the recipient designates “cash”, the amount transmitted by designating the recipient from the sender (mobile terminal 11) is transferred to the recipient's bank account. The server 16 transfers the money to the recipient's bank account and cashes it.

  On the other hand, in the receipt notification mail in step ST25 shown in FIG. 7, when the recipient desires “appropriate” as the receipt method, it is transmitted from the sender in the above-mentioned step ST22 and stored in the recipient user database in step ST23. As described above in step ST26, the amount of money is stored in the receiver user allocation point database. When the recipient wishes, the allocation points stored in this receiver user allocation point database are moved from the receiver user allocation point database to the mobile phone fee site or the so-called wallet mobile site when the recipient's allocation is specified. It will be used for mobile phone charges or wallet payments.

  That is, FIG. 9 is a diagram showing a processing procedure for paying a mobile phone fee or purse carrying from the receiver user allocation point database in accordance with the receiver's instruction. As shown in FIG. 9, the receiver (mobile terminal 12) transmits to the P2P server 16 a reception request mail designating “appropriate” as the reception method (step ST41). This receipt request mail includes the amount desired to be received and the appropriation destination (cell phone fee or payment for purse wallet) by the input operation of the receiver. The P2P server 16 determines whether or not an amount equal to or greater than the amount corresponding to the database (receiver user allocation point database) in which the amount waiting for the receiver's receipt request is stored is stored. , Appropriate the money to the recipient specified by the recipient. For example, if the mobile phone charge is designated as the appropriation destination, the amount is transferred to the mobile phone charge site and used for payment of the mobile phone charge (step ST42). If the payment for the wallet mobile phone is designated as the appropriation destination, the amount is transferred to the wallet mobile phone site and used for the payment for the wallet mobile phone (step ST43).

  Alternatively, the receiver can access the mobile phone fee site (step ST44), move the amount of the receiver user appropriation point database to the mobile phone fee site, and use it for the mobile phone fee. Furthermore, the receiver can access the wallet mobile site (step ST45) and use the amount of the receiver user allocation point database to pay for the wallet mobile phone.

  In this way, the amount stored in the P2P server 16 for the sender to send money to the recipient is appropriated for the recipient's mobile phone fee or wallet payment when the recipient designates “appropriate”.

  FIG. 10 is a diagram showing a schematic procedure of the inter-individual money transfer service described above. As shown in FIG. 10, the sender transmits the remittance contact as a receipt confirmation mail to the receiver via the P2P server 16 (step ST51). The recipient who has received this receipt confirmation mail returns a receipt confirmation reply mail to the P2P server 16 together with the designation of the receipt method (step ST52).

  Then, in the P2P server 16, the receiving process (“cashing”, “appropriation”, etc.) is performed by the receiving method specified by the receiving confirmation reply mail from the receiver, and the receiving of the receiver is completed (step ST53). . When the receiving process is completed, a charge for the amount of the receiving process is transmitted from the P2P server 16 to the sender (step ST54). This request is sent to the sender as a request for carrying the wallet.

  Also, in the P2P server 16, when the amount is accumulated in the point allocation (the above-mentioned receiver user allocation point database), when the point digest request is transmitted from the receiver to the P2P server 16 (step ST55), the P2P The server 16 applies the amount designated by the request for digestion to the mobile phone fee or the payment of the wallet (step ST56).

  In this way, when transferring money from the sender to the receiver, the remittance data is transmitted to the P2P server 16 of the inter-individual settlement service provider (communication carrier), and the P2P server 16 responds to the request of the receiver. Payment (“cash”, “appropriate”, etc.) is made. That is, regardless of whether or not the sender has funds, the P2P server 16 as the inter-individual remittance service provider (telecom carrier) pays the receiver, and then sends it from the inter-individual remittance service provider (telecommunications carrier). For example, the hand is charged as a payment for carrying a wallet.

  In this way, transmission for remittance from the sender to the receiver is performed to the P2P server 16 which is a telecommunications carrier (individual money transfer service provider), and the P2P server 16 pays the receiver on behalf of the sender. By doing so, payment to the recipient is made without moving the sender's funds. After that, a charge (billing) is made to the sender from the communication carrier (inter-individual money transfer service provider). This billing (billing) is realized when the sender makes a contract for a specific service in advance with the communication carrier (inter-individual money transfer service provider). This specific service means that instead of paying cash when a contractor (sender) makes a purchase, such as carrying a wallet, the payment history is transferred to a specific server (for example, a mobile phone). P2P server 16) means a service for charging (charging) a contractor at a predetermined timing based on the stored history.

  Further, in the P2P server 16, when the amount of the recipient is accumulated to some extent, the collected amount is transferred from the bank account of the telecommunications carrier (inter-person remittance service provider) to the recipient's bank account according to the recipient's instruction. By doing so, the number of transfers can be reduced.

  Incidentally, FIG. 11 is a diagram showing the functions necessary for the P2P server 16 and the contents of the database in order to realize the inter-individual remittance service. As shown in FIG. 11, the P2P server 16 is provided with a personal number issuing function, and a personal number and a mobile phone number are associated with each other and stored in a database.

  When there is a remittance request from the sender, the P2P server 16 first stores data related to this remittance request in the corresponding recipient user database (DB) (step ST61) and manages it. For example, when the sender designates the receiver identified by the mobile phone number 090xxxxxxx and sends a remittance request of 3000 yen to the P2P server 16 on November 12, 2007, the P2P The server 16 stores this data in the recipient user database. In the example shown in FIG. 11, this remittance data is stored in association with the receipt number 23, for example.

  Then, based on the answer of the receiving method from the receiver (or when the time limit has passed), this amount is taken out from the receiver user database (step ST62), and any of “cashification”, “appropriation”, and “rejection rejection” is selected. Is selected (step ST63, step ST64, step ST65). When either of these processes is executed, the sender is charged for the amount (step ST66).

  FIGS. 12 to 15 are diagrams showing an operation image in the case where 5000 yen is transferred from the sender (child A) to the receiver (child B) and the child B receives the money. FIG. 12 is a diagram showing the display contents of the display units of the mobile terminals 11 and 12 when acquiring the personal number necessary for receiving the inter-individual remittance service. For example, when the sender (A child) requests the P2P server 16 to issue a personal number, the personal number issued to the A child (×) is displayed on the display unit 101A of the mobile terminal 11 of the sender (A child). Xxxx) is displayed. When this personal number is transmitted to the receiver (child B) by the operation of the sender (child A), the personal number (xxx) of the child A is displayed on the display unit 101B of the mobile terminal 12 of the receiver (child B). Xxx) is displayed. Similarly, when the receiver (B child) requests the P2P server 16 to issue a personal number, the personal number issued to the B child is displayed on the display unit 101B of the mobile terminal 12 of the receiver (B child). (XXXXXX1) is displayed. When this personal number is transmitted to the sender (child A) by the operation of the receiver (child B), the personal number (XX) of the child B is displayed on the display unit 101A of the mobile terminal 11 of the sender (child A). Xxx1) is displayed.

  FIG. 13 is a diagram showing the display contents of the display unit of the mobile terminals 11 and 12 when receiving the inter-individual remittance service. First, when the sender (mobile terminal 11) accesses the P2P server 16 (P2P site) (or activates the P2P application), an interpersonal remittance screen is displayed on the display unit 101A (step ST71). A screen for inputting necessary items is displayed on the display unit 101A (step ST72). The sender (A child) inputs information related to the remittance (the mobile phone number of the remittance destination (receiver: B child), the amount of remittance, comments, etc.) according to the display on the display unit 101A.

  When the input of information related to remittance is completed, the mobile terminal 11 performs various checks such as authentication of a personal identification number and credit check (step ST73). If the various checks are OK, a remittance request is made to the P2P server 16 (step ST74). Receiving this remittance request, the P2P server 16 confirms receipt by sending a receipt confirmation mail to the recipient (B child: mobile terminal 12) as the remittance destination (step ST75). On the display unit 101B of the recipient (B child: mobile terminal 12) that has received this receipt confirmation mail, information indicating that there has been a remittance request, the remittance requesting source (A child), a request for specifying a receiving method, and the like are displayed. Is done. When the recipient (child B) clicks the URL of this screen, the telephone number, the amount, and the comment of the remittance requester are displayed on the display unit 101B, and the receiving method is selected and displayed. In this way, when the recipient (child B) clicks on the URL to select and display the receiving method, the receiver (mobile terminal 12) notifies the P2P server 16 that the receipt confirmation mail has been received. As a result, the P2P server 16 completes the remittance request process (step ST76), and a remittance request completion notification is transmitted to the sender (child A: mobile terminal 11) (step ST77). As a result, on the display unit 101A of the sender (child A: mobile terminal 11), a message indicating that “the remittance procedure is in progress and the remittance is executed as soon as the receipt is approved” is displayed. Thereby, the sender (A child) can recognize that the remittance request has arrived at the receiver (B child).

  When the recipient (child B) transmits the receipt method to the P2P server 16 by the designated date, the P2P server 16 receives a reply of this receipt method (reply of the receipt confirmation mail) (step) ST78). In addition, when the receiver (child B) does not receive the reply of the receiving method by the due date (when the receiver does not select the receiving method by the due date), the P2P server 16 does not specify the receiving method. In this case, a specific process (for example, as described above, appropriate for the recipient's point) is performed. Then, the P2P server 16 executes remittance processing to the receiver by the receiving method designated by the receiver (B child) based on the reply of the received mail confirmation from the receiver (B child) (step ST79).

  When the remittance process is executed, the P2P server 16 notifies the sender (child A: mobile terminal 11) of the completion of remittance reception (step ST80). As a result, the display unit 101A of the mobile terminal 11 of the sender (A child) displays that the receiver has received it and that the amount received has been charged to the sender (A child). When the remittance process is executed, the P2P server 16 notifies the recipient (B child: mobile terminal 12) of the completion of remittance (step ST81). As a result, the amount of money sent from the sender (child A) is displayed on the display unit 101B of the mobile terminal 12 of the receiver (child B) by a method designated by the receiver (child B) (for example, transfer to a bank account). A message indicating that the transfer has been completed is displayed. As a result, the sender (A child) can recognize that the remittance to the receiver (B child) is completed, and the receiver (B child) can recognize the sender (A child). It is possible to recognize that the amount repaid from has been paid out by a method designated by the user (recipient: child B).

  Incidentally, FIG. 14 is a diagram showing a detailed procedure when the receipt (step ST75) is performed in the receiver (child B: mobile terminal 12). As shown in FIG. 14, for example, when the receiver (child B) selects “cash” and inputs bank account information to the display unit 101B of the mobile terminal 12 (step ST91), the content is the mobile terminal of the receiver. 12 is sent to the P2P server 16 as a receipt confirmation mail. When the P2P server 16 receives the reply to the receipt confirmation mail (step ST92 (corresponding to step ST78 in FIG. 13)), the P2P server 16 transmits the reception completion notification to the recipient (B child: mobile terminal 12), thereby moving the recipient. The terminal 12 completes the receipt of the receipt confirmation mail (step ST93), and the display unit 101B of the mobile terminal 12 displays that the remittance has been completed to the bank account of the receiver (child B).

  FIG. 15 is a diagram showing a detailed procedure when the payee (B child) selects “appropriate” as the receiving method and then designates the payment for carrying the wallet as the appropriating destination. As shown in FIG. 15, the recipient (B child: mobile terminal 12) accesses the P2P server 16 (or activates the application by Web access) (step ST101), and assigns it to the display unit 101B of the mobile terminal 12. (For example, payment for carrying a wallet or payment for mobile phone charges) and a screen for entering the amount are displayed. When the recipient (child B) selects the allocation destination and the allocation amount on this screen (step ST102), the selection content is transmitted from the mobile terminal 12 to the P2P server 12. When the P2P server 16 receives the selection transmitted from the receiver (mobile terminal 12) (step ST103), the P2P server 16 sets to perform the selected allocation process, and receives the reception completion notification as a completion mail. ). When the recipient (mobile terminal 12) receives the completion mail (step ST104), the display unit 101B of the mobile terminal 12 displays that the appropriation is to be performed.

  In the inter-individual remittance service described above, the amount of money sent by the sender to the receiver by making a wallet mobile phone contract with the carrier (inter-personal remittance service provider) in advance. The sender's billing for can be included in the sender's wallet payment. Thus, when the remittance is made from the sender to the receiver, the sender only needs to send the remittance data to the P2P server 16, and the P2P server 16 temporarily takes the payment form desired by the receiver ("cashing") on behalf of the sender. , “Appropriate”, etc.), and after that, the payment is included in the payment of the sender's wallet.

  As a result, there is no need to intervene a bank at the timing of remittance from the sender to the receiver, and as a result, there is no need to go to a bank counter or ATM for remittance. Further, there is no need for a bank transfer fee for the sender to transfer money from the sender to the receiver.

  Further, since the remittance process is performed using a personal number or a mobile phone number, there is no need to convey the account number of the receiver to the sender. In particular, when performing a remittance process using a personal number, the sender and the receiver can also perform the remittance anonymously without knowing each other.

  In addition, by using the mobile terminals 11 and 12 to transfer money, it is possible to transfer money without directly meeting the other party, and it is possible to transfer money simply by operating the mobile terminals 11 and 12, Compared to meeting directly and giving cash, it is possible to perform accurate settlement (remittance) without worrying about change or change.

  Instead of including the remittance amount in the payment of the sender's mobile phone, it is also possible to pay only the remittance amount by debiting the bank separately from the payment of the mobile phone.

  Thus, as shown in FIG. 16, when the sender and the receiver are acquainted with each other, the sender can send money to the receiver using each other's mobile phone number, and as shown in FIG. Thus, when the sender and the receiver are not acquainted with each other (when anonymity is desired), the sender can send money to the receiver using the personal number issued by the P2P server 16. Become. Note that the example shown in FIG. 17 shows a case where, for example, a user of an online auction serves as a sender and remits the price of an item that he / she has bid off as an exhibitor. In this case, the sender and the receiver can perform remittance without telling each other personal information.

  According to the inter-individual remittance system according to the present embodiment described above, the P2P server 16 pays to the receiver and sends the money to the sender without transmitting or receiving a monetary value equivalent to cash between the mobile terminals 11 and 12. By performing billing, the result is substantially the same as when cash is transferred. Thereby, even if the environment in which the mobile terminals 11 and 12 transmit and receive a monetary value such as electronic money is not prepared, cash can be exchanged between the sender and the receiver via the mobile terminals 11 and 12. It becomes possible. Further, the sender does not need to know the bank account number of the recipient, and it is possible to maintain the confidentiality of the recipient's personal information. Furthermore, it is not necessary for the sender and the receiver to meet directly to exchange cash, making it easy to exchange cash and maintaining the anonymity of each other.

(Second Embodiment)
In the first embodiment described above, the receiver holds the remittance data transmitted to the P2P server 16 as “instruction” and processes this “instruction” within a certain period (“cashing”, “appropriation”). , “Receiving refusal”) and then charging the sender according to the processing. Instead, the P2P server 16 returns the intention to receive to the P2P server 16 when the receiver returns the intention to receive. After charging the sender, it may wait for a request for a receiving method from the receiver (waiting for a receiving request).

  That is, in FIG. 18, in which parts corresponding to those in FIG. 7 are assigned the same reference numerals, the sender (mobile terminal 11) designates the personal number or mobile phone number of the receiver (mobile terminal 12), and the sender (mobile It is a figure which shows the process sequence in case a terminal 11) transmits remittance data to the P2P server 16, and a receiver (mobile terminal 12) receives the amount of money designated by this remittance data (reception refusal). The inter-individual remittance system (communication system) according to the present embodiment is realized by a configuration similar to the configuration shown in FIG.

  As shown in FIG. 18, as described above with reference to FIG. 6, the receiver (mobile terminal 12) sends money to the sender (mobile terminal 11) in the state where the personal number has already been issued. A reminder mail is transmitted (step ST121). At this time, the receiver (mobile terminal 12) transmits his / her personal number or mobile phone number attached to the reminder mail.

  In response to the reminder mail from the receiver, the sender (mobile terminal 11) designates the personal number or mobile phone number of the receiver and transmits the amount to be transmitted to the P2P server 16 as remittance contact data (step ST122). . It is assumed that the sender (mobile terminal 11) has a contract with a communication carrier to receive a payment service using the above-described mobile phone called a wallet mobile phone.

  When receiving the remittance contact data from the sender (mobile terminal 11), the P2P server 16 transmits a receipt intention confirmation mail to the receiver (mobile terminal 12) (step ST123). This receipt intention confirmation mail includes the personal number or mobile phone number of the sender (mobile terminal 11). In this way, by transmitting information (personal number or mobile phone number) that can identify the sender together with the receipt confirmation mail, the receiver (mobile terminal 12) can confirm who the remittance source is. .

  The receiver (mobile terminal 12) that has received the receipt confirmation mail transmits to the P2P server 16 whether or not there is an intention to receive the receipt confirmation mail (step ST124). The P2P server 16 that has received the receipt intention notification mail indicating that there is an intention to receive charges the sender and transmits a receipt intention notification to the sender indicating that the receiver is willing to accept (step). ST125).

  Then, the P2P server 16 stores the amount included in the remittance contact data from the sender (mobile terminal 11) in the storage device 44 (FIG. 5) in association with the personal number or mobile phone number of the recipient (step ST126). . As a result, a receiver user database associated with the receiver's personal number or mobile phone number is created in the storage device 44 of the P2P server 16. In this receiver user database, the amount of remittance data transmitted to the P2P server 16 with the receiver (user identified by personal number or mobile phone number) as the remittance destination is stored each time. If the recipient is within the accumulated amount, the recipient can specify a desired amount and pay it to the recipient (“cash”, “appropriate”). When the amount in the receiver user database is used for payment to the receiver, the amount is subtracted from the database. Thereafter, the recipient can specify the receiving method and receive the amount within the range of the amount stored in the database.

  In this way, in the inter-individual remittance system according to the present embodiment, when a remittance request is transmitted from the sender to the receiver, and the receiver intends to receive the money, the P2P server 16 charges the sender. At the same time, by setting a remittance amount in the receiver user database so that the receiver can receive the money on his / her own intention, a processing flow in which the receiver receives the charges after charging the sender can be realized.

(Other embodiments)
The present invention is not limited to the embodiment described above, and can be implemented with various modifications. As long as it does not deviate from the scope of the present invention, it is possible to appropriately change and implement the processing unit and the processing procedure. Other modifications can be made without departing from the scope of the present invention.

It is a figure which shows schematic structure for demonstrating the remittance system (communication system) between individuals concerning the 1st Embodiment of this invention. It is a block diagram which shows schematic structure of the mobile terminal in the communication system shown in FIG. It is a block diagram which shows schematic structure of the mobile communication center in the communication system shown in FIG. It is a figure which shows the table of the management database in the mobile communication center shown in FIG. It is a block diagram which shows schematic structure of the P2P server in the communication system shown in FIG. It is a figure which shows the issuing process procedure of the receiver's personal number by a P2P server. It is a figure which shows the process sequence in case a sender | sender designates a receiver's personal number or a mobile telephone number, a sender | sender transmits remittance data to a P2P server, and a receiver receives the money | number designated by this remittance data. . FIG. 9 is a diagram showing a detailed processing procedure when the recipient wishes to “cash” as the receiving method in the receipt notification mail in step ST25 shown in FIG. 7. It is a figure which shows the process sequence which pays a mobile telephone charge or a wallet mobile phone from a receiver user allocation point database by a receiver's instruction | indication. It is a figure which shows the schematic procedure of a remittance service between individuals. It is a figure which shows the function required for a P2P server, and the content of a database in implement | achieving a remittance service between individuals. It is a figure which shows the display content of the mobile terminal display part at the time of acquisition of the personal number required when receiving a remittance service between individuals. It is a figure which shows the display content of the display part of a mobile terminal at the time of receiving interpersonal money transfer service. It is a figure which shows the detailed procedure at the time of receiving confirmation in a receiver. It is a figure which shows the detailed procedure in the case of designating payment of a wallet mobile phone as an allocation destination, after a receiver selects "appropriation" as a receiving method. It is a figure where it uses for description of the example of remittance using a mobile telephone number. It is a figure where it uses for description of the example of remittance using a personal number. It is a figure for demonstrating the flow of the remittance process between individuals concerning 2nd Embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Communication system 11, 12 Mobile terminal 13 Mobile communication network 14 Mobile communication center 15 Network 16 P2P server 21, 31 Control part 22, 32 Communication control part 23 Display part 24 Operation part 25 Microphone 26 Speaker 27 Imaging part 28 Storage part 29 Application Control unit 33 Information update unit 34 Management database 41 CPU
42 Input Device 44 Storage Device 45 Transmission / Reception Device 46 Display Device 47 Reading Device 48 Recording Medium

Claims (16)

An inter-individual money transfer system that transfers money from a source to a destination,
A first terminal for transmitting a remittance request to the remittance destination;
The remittance request is received from the first terminal, and based on the received remittance request, a receipt confirmation for confirming the intention of receipt is transmitted to the second terminal associated with the remittance destination. and executes the payment to the remittance destination when receiving an acknowledgment from the second terminal to the confirmation, the amount of the payment, charging for the transfer source or the transfer destination, the acknowledgment A remittance management server that stores remittance data as a point for the recipient if not received ,
An inter-individual remittance system comprising: The remittance management server
Store remittance data each time based on the remittance request,
The inter-individual remittance system according to claim 1, wherein when the confirmation notification is not received within a predetermined period, the stored remittance data is stored as a point for the receiver. The remittance management server
2. The inter-individual remittance system according to claim 1, wherein the remittance destination personal number is issued and a remittance request addressed to the issued personal number is recognized as a remittance request to the remittance destination. The remittance management server
The inter-individual remittance system according to claim 1, wherein the remittance destination telephone number is held and a remittance request to the telephone number is recognized as a remittance request to the remittance destination. The remittance source or the remittance destination concludes in advance a contract to receive service provision using the first terminal or the second terminal,
The inter-individual remittance system according to claim 1, wherein the remittance management server includes an amount to be received by the billing in a consideration to be received from the remittance source or the remittance destination for the service provision. Interindividual transfer system according to claim 1 or claim 5, wherein the transfer source or charging to the remittee is carried out after the execution of the payment to the payee. The inter-individual remittance system according to claim 1 or 5 , wherein payment to the remittance destination is executed after charging to the remittance source or the remittance destination.   For payment to the remittance destination, either transfer to a designated account designated by the remittance destination or appropriation to a point for the remittance destination to receive a predetermined service is selected according to the designation of the remittance destination. The inter-individual remittance system according to claim 1. A remittance management server of an inter-individual remittance system that transfers money from a remittance source to a remittance destination,
Receipt confirmation for receiving a remittance request from the first terminal as a recipient of the remittance destination and confirming the intention of receipt to the second terminal associated with the remittance destination based on the received remittance request sends, billing and executes the payment to the remittance destination when receiving an acknowledgment from the second terminal to the confirmation preparative receiving, the amount of the payment, the remittance source or the transfer destination If the confirmation notification is not received , the remittance management server stores the remittance data as a point for the recipient . Store remittance data each time based on the remittance request,
10. The remittance management server according to claim 9, wherein when the confirmation notification is not received within a certain period, the stored remittance data is stored as a point for the receiver. 10. The remittance management server according to claim 9 , wherein the remittance destination personal number is issued and a remittance request addressed to the issued personal number is recognized as a remittance request to the remittance destination. The remittance management server according to claim 9 , wherein the remittance destination telephone number is held and a remittance request to the telephone number is recognized as a remittance request to the remittance destination. The consideration to be received from the transfer source or the transfer destination to the service provided to the first terminal or the second terminal, in claim 9, characterized in that the inclusion of amounts to be received by the billing The described remittance management server. The remittance management server according to claim 9 or 13 , wherein the remittance source or the remittance destination is charged after execution of payment to the remittance destination. 14. The remittance management server according to claim 9 or 13 , wherein payment is made to the remittance destination after charging to the remittance source or the remittance destination. As for payment to the remittance destination, either transfer to a designated account designated by the remittance destination or appropriation to a point for the remittance destination to receive a predetermined service is selected according to the designation by the remittance destination. The remittance management server according to claim 9 .

Images