Information processing device, information processing method, and information processing program

The information processing device in electronic payment services identifies and prevents fraudulent transactions by using user ID comparisons and flag information to block unauthorized transfers, enhancing security in electronic payment systems.

JP7583203B1Active Publication Date: 2024-11-13PAYPAY CO LTD

Patent Information

Application Number
JP2024008297
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2024-01-23
Publication Date
2024-11-13
Estimated Expiration
2044-01-23

AI Technical Summary

Technical Problem

Conventional electronic payment services lack effective measures to prevent fraudulent acts such as stealing electronic money through unauthorized transfers.

Method used

An information processing device that includes a storage unit for user identification information, an acquisition unit to gather remittance destination user IDs, and an estimation unit to compare these IDs with stored flag information to identify potential fraudulent users, thereby preventing unauthorized transactions.

Benefits of technology

The solution effectively prevents fraudulent acts in electronic payment services by identifying and suspending transactions to suspected users, thereby protecting against unauthorized money transfers.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007583203000001_ABST
    Figure 0007583203000001_ABST
Patent Text Reader

Abstract

Prevent fraudulent activities in electronic payment services. [Solution] The information processing device according to the present application has a flag information storage unit, an acquisition unit, and an estimation unit. The storage unit stores in advance flag information indicating whether or not the user is suspected of fraud, in association with identification information assigned to a user suspected of fraud, which is identification information assigned to identify each user in an electronic payment service. The acquisition unit acquires the identification information of the remittance destination user transmitted from a device used by the remittance destination user in association with an operation of the remittance destination user on link information. The estimation unit compares the identification information of the remittance destination user acquired by the acquisition unit with the identification information stored in the flag information storage unit, and estimates that the remittance destination user is a user suspected of fraud when flag information indicating that the user is suspected of fraud is associated with the identification information of the remittance destination user.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an information processing device, an information processing method, and an information processing program. [Background technology]

[0002] Traditionally, electronic payment services that are conducted online using terminal devices such as smartphones owned by individual users have become widespread among consumers, particularly due to their convenience, and users may be given special benefits in accordance with their use of the electronic payment services.

[0003] Furthermore, some of the above-mentioned electronic payment services provide services that enable users to easily transfer digital money, such as electronic money or virtual currency, between users (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-157715 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the above-mentioned conventional techniques have room for improvement in terms of preventing fraudulent activities in electronic payment services. For example, the conventional techniques need to eradicate fraudulent activities such as having other users transfer electronic money in order to steal the electronic money.

[0006] The present application has been made in consideration of the above, and aims to provide an information processing device, an information processing method, and an information processing program that can prevent fraudulent activities in electronic payment services. [Means for solving the problem]

[0007] The information processing device according to the present application is an information processing device that performs processing related to an electronic payment service that allows electronic money to be transferred between users using link information provided from a remittance source user, who is the source of electronic money, to a remittance destination user, who is the destination of electronic money, in order to transfer electronic money, and has a storage unit, an acquisition unit, and an estimation unit. The storage unit stores in advance flag information indicating whether the user is suspected of fraud, in association with identification information assigned to a user suspected of fraud, which is identification information assigned to identify each user in the electronic payment service. The acquisition unit acquires the identification information of the remittance destination user transmitted from a device used by the remittance destination user in association with an operation of the remittance destination user on the link information. The estimation unit compares the identification information of the remittance destination user acquired by the acquisition unit with the identification information stored in the storage unit, and estimates that the remittance destination user is a user suspected of fraud when flag information indicating that the user is suspected of fraud is associated with the identification information of the remittance destination user. Effect of the Invention

[0008] According to one aspect of the embodiment, it is possible to prevent fraudulent activities in electronic payment services. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram for explaining an overview of information processing according to the embodiment. [Diagram 2] FIG. 2 is a diagram showing a screen display example (part 1) according to the embodiment. [Diagram 3] FIG. 3 is a diagram showing a screen display example (part 2) according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of the configuration of a payment service providing device according to an embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an overview of the setting information stored in the setting information storage unit according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of flag information stored in the flag information storage unit according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a receipt history stored in a receipt history storage unit according to the embodiment. [Figure 8] FIG. 8 is a flowchart showing an example of a processing procedure of a remittance process executed by the payment service providing device according to the embodiment. [Figure 9] FIG. 9 is a flowchart showing an example of a processing procedure of the fraudulent user inferring process executed by the payment service providing device 100 according to the embodiment. [Figure 10] FIG. 10 is a hardware configuration diagram showing an example of a computer that realizes the functions of the payment service providing device according to the embodiment or the modification. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, the information processing device, the information processing method, and the information processing program according to the present application will be described in detail with reference to the drawings. Note that the information processing device, the information processing method, and the information processing program according to the present application are not limited to the embodiments. In addition, the same parts in the following embodiments are given the same reference numerals, and duplicated descriptions are omitted.

[0011] 1. Embodiment (1-1. System Configuration) The information processing according to the embodiment will be specifically described below. First, before describing the information processing according to the embodiment, an example of the configuration of an information processing system including a payment service providing device 100, which is an example of an information processing device according to the embodiment, will be described with reference to Fig. 1. Fig. 1 is a diagram for explaining an overview of the information processing according to the embodiment.

[0012] As shown in Figure 1, information processing system SYS according to an embodiment is configured to include terminal device 10-1, terminal device 10-2, message service providing device 20, and payment service providing device 100. Terminal device 10-1, terminal device 10-2, message service providing device 20, and payment service providing device 100 are connected to network N (see Figure 4, for example) by wire or wirelessly. Terminal device 10-1, terminal device 10-2, message service providing device 20, and payment service providing device 100 can communicate with other devices via network N. Network N is, for example, a WAN (Wide Area Network) such as the Internet.

[0013] Note that the configuration of the information processing system SYS shown in Fig. 1 is an example, and may include more terminal devices 10 than those illustrated in Fig. 1, and may include other service providing devices other than the message service providing device 20 illustrated in Fig. 1. In the following description, when there is no need to particularly distinguish between the terminal device 10-1 and the terminal device 10-2, they will be collectively referred to as the terminal device 10.

[0014] Terminal device 10-1 shown in Fig. 1 is an information processing terminal used by user U-1, who is a service user who uses online services such as the message service provided by message service providing device 20 and the electronic payment service provided by payment service providing device 100. Similarly, terminal device 10-2 shown in Fig. 1 is an information processing terminal used by user U-2, who is a service user who uses online services such as the above-mentioned message service and electronic payment service. In the following description, unless there is a need to particularly distinguish between user U-1 and user U-2, they will be collectively referred to as user U.

[0015] The terminal device 10 may be realized by, for example, a smartphone, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, a PDA (Personal Digital Assistant), or the like. The terminal device 10 also includes a display device such as a liquid crystal display (LCD) or an organic electro-luminescent display (OLED), and can display information distributed by the message service providing device 20, the payment service providing device 100, or the like, using a web browser or an application. The display device may be a touch screen display. In this case, the terminal device 10 receives various operations from the user U on content such as images displayed on a screen of the touch screen display by the user U using a finger, a stylus, or the like, and executes processing in accordance with the various operations.

[0016] Furthermore, when terminal device 10 receives control information for realizing predetermined information processing from message service providing device 20, payment service providing device 100, or the like, it realizes the information processing in accordance with the control information. Here, the control information may be described in, for example, a script language such as JavaScript (registered trademark), a style sheet language such as CSS (Cascading Style Sheets), a programming language such as Java (registered trademark), or a markup language such as HTML (HyperText Markup Language). Note that a predetermined application itself delivered from message service providing device 20, payment service providing device 100, or the like may be regarded as control information.

[0017] Terminal device 10 also has a communication function unit for communicating with other devices, and transmits and receives information to and from other devices such as message service providing device 20 and payment service providing device 100. Terminal device 10 may have, as the communication function unit, a communication unit for connecting to network N via a wireless communication network such as LTE (Long Term Evolution), 4G (4th Generation), or 5G (5th Generation: 5th generation mobile communication system), or via short-range wireless communication such as Bluetooth (registered trademark) or wireless LAN (Local Area Network).

[0018] By operating the terminal device 10, the user U can access a predetermined website managed by the message service providing device 20 and use a message service on the predetermined website by using information transmitted and received between the terminal device 10 and the message service providing device 20. Note that the terminal device 10 may be pre-installed with a dedicated application program (hereinafter referred to as a "message app") created to realize various processes related to the message service in cooperation with the message service providing device 20. In this case, the terminal device 10 can execute various processes related to the message service by using functions provided by the message app.

[0019] Furthermore, user U can operate terminal device 10 to access a predetermined website managed by payment service providing device 100, and can use electronic payment services on the predetermined website using information transmitted and received between payment service providing device 100. Terminal device 10 may be pre-installed with a dedicated application program (hereinafter referred to as a "payment app") created to realize various processes related to the electronic payment service in cooperation with payment service providing device 100. In this case, terminal device 10 can execute various processes related to the electronic payment service using functions provided by the payment app.

[0020] 1 is an information processing device that executes information processing related to a message service that allows service users to send and receive messages to each other to realize online communication. A service provider that manages the message service providing device 20 operates, for example, a platform service that provides service users with a usage environment for utilizing online communication between the service users. When the message service providing device 20 is configured as a server device, it may be realized by a single server device, or may be realized by a cloud system in which a plurality of server devices and a plurality of storage devices operate in cooperation with each other.

[0021] The message service providing device 20 may function as a distribution device that distributes control information to a terminal device 10 used by a user U who is a service user. Here, the control information may be described in, for example, a script language such as JavaScript (registered trademark) or a style sheet language such as CSS (Cascading Style Sheets). Note that the application itself distributed from the message service providing device 20 may be regarded as the control information.

[0022] The message services provided by the message service providing device 20 may include any service capable of exchanging various messages in, in addition to SMS (Short Message Service) and SNS (Social Networking Service), an electronic commerce service, an electronic payment service, an online game, an online banking service, an online trading service, an accommodation reservation service, a ticket reservation service, a video distribution service, a music distribution service, a news distribution service, a map information service, a route search service, a route guidance service, a line information service, an operation information service, a weather information service, etc. Furthermore, the message services provided by the message service providing device 20 may include not only general text messages but also various services capable of posting rich text using HTML, various links, images, videos, etc.

[0023] Payment service providing device 100 shown in Fig. 1 is an information processing device that executes information processing according to an embodiment. A service provider that manages payment service providing device 100 operates a platform service that provides service users with an environment for using an electronic payment service (hereinafter simply referred to as a "payment service") that uses predetermined code information. When payment service providing device 100 is configured as a server device, it may be realized by a single server device, or may be realized by a cloud system in which multiple server devices and multiple storage devices operate in cooperation with each other.

[0024] Payment service providing apparatus 100 may function as a distribution device that distributes control information to terminal apparatus 10 used by user U, who is a service user. Here, the control information may be described in, for example, a script language such as JavaScript (registered trademark) or a style sheet language such as CSS (Cascading Style Sheets). Note that the application itself distributed from payment service providing apparatus 100 may be regarded as control information.

[0025] The electronic payment service provided by payment service providing apparatus 100 enables user U, a service user who uses the payment service, to easily pay for a transaction object. For example, payment service providing apparatus 100 manages electronic money accounts (also called "electronic wallets") of providers of transaction objects and users to whom transaction objects are provided, and realizes various types of payments by transferring electronic money between accounts in response to a payment request from a service user. Note that electronic money may be, for example, points or currency used independently by various companies, or it may be electronically tradable currency provided by a country, such as Japanese yen or dollars.

[0026] In addition, the electronic payment service provided by the payment service providing device 100 can provide service users with, as part of the service, a function for sending and receiving direct text messages between service users who have registered each other as friends, for example, via a payment app.

[0027] The information processing according to the embodiment executed by payment service providing device 100 will be described in detail later with reference to the drawings.

[0028] (1-2. Payment using terminal device 10) Here, code payment will be described as an example of electronic payment executed using the terminal device 10. When the terminal device 10 is a smartphone, code payment executed using the terminal device 10 is also called "smartphone payment". In the following description, for example, a two-dimensional code (QR code (registered trademark)) placed in a specific store and indicating store identification information that identifies the specific store is used to perform a payment using the terminal device 10 by a user U (see, for example, FIG. 1, etc.) who is a service user who receives a transaction object from a specific store. The code payment described below is also applicable to a case where an arbitrary user uses an arbitrary terminal device 10 to perform a payment at an arbitrary store. The two-dimensional code indicating the store identification information may be not only a QR code but also a barcode, a predetermined mark, a number, etc. The two-dimensional code is not limited to an example that is physically configured by a printed matter printed on a medium such as paper, and may be configured by image information displayed on an arbitrary terminal.

[0029] For example, when a user U makes a payment for the purchase or use of a transaction object such as various products or services at a specific store, the user U starts a payment app pre-installed in the terminal device 10 to use code payment. The user U can use various functions related to code payment through the payment app. Then, the user U photographs a two-dimensional code installed at the specific store through the payment app. In such a case, the terminal device 10 displays a screen for inputting the price of the transaction object, and accepts input of the payment amount from the user U or a clerk at the specific store. Then, the terminal device 10 transmits transaction information including user identification information for identifying the user U, store identification information (or information indicated by the store identification information, i.e., information indicating the specific store (for example, a store ID)), and the payment amount to the payment service providing device 100. Note that such a payment method is also called a "user scan method."

[0030] When payment service providing device 100 accepts transaction information from terminal device 10, it transfers electronic money equivalent to the payment amount from the account of user U indicated by the user identification information to the account of a specific store indicated by the store identification information. At this time, payment service providing device 100 may transfer the electronic money to the account of the specific store after subtracting a specific fee to be charged to the specific store from the electronic money equivalent to the payment amount. Then, payment service providing device 100 transmits a notification that the transaction has been completed to terminal device 10. In such a case, terminal device 10 notifies user U that the electronic money transaction has been completed by outputting a screen or a specific sound indicating that the transaction has been completed. Alternatively, payment service providing device 100 may withdraw electronic money equivalent to the payment amount from the account of user U indicated by the user identification information, manage it as sales information of the specific store, and transfer cash equivalent to the sales at a specific timing to a bank account held by the specific store. In this case, payment service providing device 100 may notify user U that the transaction using electronic money has been completed at the time when electronic money equivalent to the payment amount has been withdrawn from user U's account.

[0031] It should be noted that the payment using the terminal device 10 is not limited to the above-mentioned process. For example, the payment using the terminal device 10 may be made using a terminal device (hereinafter referred to as a "store terminal") installed in a specific store. Specifically, the terminal device 10 first displays code information indicating user identification information for identifying the user U on a screen. In such a case, the store terminal reads the user identification information from the code information displayed on the terminal device 10, and transmits transaction information including the read user identification information (or information indicated by the user identification information, i.e., information indicating the user U (e.g., user ID)), the payment amount, and information identifying the specific store to the payment service providing device 100. It should be noted that such a payment method is also referred to as a "store scan method."

[0032] When payment service providing device 100 receives transaction information from the store terminal, it transfers electronic money equivalent to the payment amount from the account of user U indicated by the user identification information to the account of the specified store. Then, payment service providing device 100 transmits a notification that the transaction has been completed to the store terminal or terminal device 10. The store terminal or terminal device 10 notifies user U that the electronic money transaction has been completed by outputting a screen or a specified sound indicating that the transaction has been completed. In addition, payment service providing device 100 may withdraw electronic money equivalent to the payment amount from the account of user U indicated by the user identification information, manage it as sales information of the specified store, and transfer cash equivalent to the sales amount to a bank account held by the specified store at a specified timing. In this case, payment service providing device 100 may notify a store clerk or user U that the electronic money transaction has been completed at the time when electronic money equivalent to the payment amount is withdrawn from user U's account.

[0033] Furthermore, the payment using the terminal device 10 may not only be a process of transferring electronic money from an account to which the user U has previously charged electronic money to an account of a specific store, but may also be, for example, a payment using a credit card registered in advance by the user U. In such a case, for example, the terminal device 10 may transfer electronic money in an amount indicated by the payment amount to the account of the specific store, and may also bill the operating company of the user U's credit card for the amount indicated by the payment amount.

[0034] Furthermore, settlement using terminal device 10 may not only be a process of transferring electronic money from user U's account to an account of a specific store, but may also be, for example, a settlement of transferring electronic money from user U's account to another user's account (i.e., remittance between users). For example, terminal device 10 used by user U who is the sender of the remittance reads user identification information identifying the remittance user (for example, user identification information displayed on a terminal device used by the remittance user), accepts input of the remittance amount from user U, and transmits information indicating the read identification information, the remittance amount, and the user identification information identifying user U to payment service providing device 100. In such a case, payment service providing device 100 may transfer electronic money in an amount indicated by the remittance amount from user U's account to the remittance user's account, and notify the completion of the remittance by outputting a screen or a predetermined sound indicating that the remittance has been completed to terminal device 10 or to terminal device 10 used by the remittance user.

[0035] It should be noted that remittance using terminal device 10 is not limited to the above-mentioned process. For example, remittance using terminal device 10 may be performed by inputting the telephone number of the remittance destination user or information indicating the remittance destination user (e.g., a user ID) into terminal device 10. To give a specific example, terminal device 10 accepts input of the remittance destination user's telephone number or user ID and the remittance amount from user U, and transmits the input telephone number or user ID, the remittance amount, and user identification information identifying user U to payment service providing device 100. Then, payment service providing device 100 transfers electronic money in an amount indicated by the remittance amount from user U's account to the account of the user linked to the transmitted telephone number or user ID.

[0036] Here, the telephone number or user ID of the remittance destination user may be linked to information about the user and registered in advance in the payment app. In this case, the terminal device 10 accepts from the user U the designation of the user (remittance destination) registered in the payment app and an input of the remittance amount to the user, and transmits to the payment service providing device 100 the telephone number or user ID linked to the designated user, the remittance amount, and user identification information that identifies the user U.

[0037] Furthermore, for example, remittance using terminal device 10 may be performed by providing link information for receiving the remittance amount to the remittance user. As a specific example, terminal device 10 accepts input of the remittance amount from user U, generates link information for receiving the remittance amount, and provides the link information to terminal device 10 used by the remittance user by sending an email including the link information or posting information including the link information on a social networking service (SNS). Then, when the remittance user selects the link information and performs a receiving operation, payment service providing device 100 transfers electronic money in an amount indicated by the remittance amount from the account of user U to the account of the remittance user.

[0038] The above-mentioned payment means and electronic payment services are not limited to those for providing a price (settlement of debt) for purchasing a product or providing a service. For example, as described above, the payment means and electronic payment services may have a function related to remittance between accounts held by multiple users. That is, the above-mentioned payment means and electronic payment services may be services that control the transmission and reception of electronic money between accounts of any owner linked to the owner of electronic money, such as a user or a store. That is, the payment means and electronic payment services according to the embodiment may be provided in any form as long as they are transaction means and transaction services that execute various controls for realizing the exchange of electronic money (not only various inter-account remittance controls via electronic money, but also control related to exchanges between electronic money accounts and bank accounts, various claim processes such as installments and processes associated with bonus payments, and various controls related to the exchange of assets including electronic money). In addition, the various controls realized by such transaction means and transaction services may include both control related to payment and control related to remittance, or only one of them. That is, a "transaction" is a concept that includes not only "payment" related to electronic money, but also "remittance" of electronic money and various other processes. In other words, payment service providing apparatus 100 may be an information processing apparatus that realizes a transaction means for controlling the exchange of electronic money between any owners.

[0039] (1-3. Overview of Information Processing According to the Embodiment) In recent years, electronic payment services have provided a function that allows anyone to easily and quickly transfer electronic money by providing a user on the receiving side, who is the remittance destination, with link information for transferring electronic money as part of the service. On the other hand, taking advantage of this opportunity, there have been many cases of fraudulent acts in which a user pretends to transfer the price of a transaction object, obtains link information for receiving electronic money from another user, and steals electronic money. When transferring electronic money through link information, electronic money is transferred regardless of the identity of the user on the receiving side, so it is difficult to prevent fraudulent acts of stealing electronic money. Therefore, hereinafter, as information processing according to an embodiment of the present application, information processing for preventing fraudulent acts in electronic payment services by estimating whether a user on the receiving side who receives electronic money using link information is a user suspected of fraudulently stealing electronic money by misusing the electronic payment service will be described.

[0040] In the following description, the user U-2 shown in FIG. 1 is assumed to be a user suspected of misusing the electronic payment service to steal electronic money from other users. In the following description, the misuse of the electronic payment service may be misused to steal electronic money from other users in violation of public order and morals, but may also refer to any act that violates the terms of use of the electronic payment service. In the following description, the terminal device 10-1 may be referred to as the user U-1. In other words, the user U-1 may be read as the terminal device 10-1. Similarly, in the following description, the terminal device 10-2 may be referred to as the user U-2. In other words, the user U-2 may be read as the terminal device 10-2.

[0041] As shown in FIG. 1, user U-1 operates terminal device 10-1 and sends a message to user U-2 through a message service, which describes link information LK-1 for transferring electronic money to user U-2. An example of a situation in which user U-1 sends link information LK-1 to user U-2 is when viewing a post by user U-2 on a bulletin board of an SNS. Examples of the content of the post include a post about transferring an item that is not actually owned for a fee, and a case in which SNS account information specified for exchanging messages and a user ID of an electronic payment service are also written. When user U-1 wishes to purchase an item posted by user U-2, user U-1 uses the SNS account information posted by user U-2 to register user U-2 as a contact, thereby preparing in advance so that messages can be exchanged between user U-2 and user U-2. User U-1 may prepare in advance to use the user ID of user U-2 in the electronic payment service included in the post to register the user ID in the electronic payment service as a contact for the electronic payment service, and to be able to exchange messages with user U-2 using direct messages in the electronic payment service. User U-1 then sends to user U-2 a message describing link information LK-1 for transferring the purchase price of the item to user U-2 in electronic money.

[0042] Terminal device 10-2 displays message M-1 received from terminal device 10-1 on message display screen SG of the message service. When terminal device 10-2 detects an operation by user U-2 on link information LK-1 described in message M-1 displayed on message display screen SG, terminal device 10-2 transmits an electronic money receive request to payment service providing device 100 (step S1). The receive request may include the user ID of user U-2 who is the sender of the receive request, the user ID of user U-1 who is the sender of the remittance who created the corresponding link information LK-1, information indicating the remittance amount, information indicating the creation date and time of link information LK-1, and the like. User U-2 may also return message M-2 to reply to message M-1.

[0043] When payment service providing apparatus 100 receives a receipt request from terminal apparatus 10-2, it executes fraudulent user inference processing (step S-2). Specifically, payment service providing apparatus 100 has flag information storage unit 122 that stores in advance flag information indicating whether or not a user is suspected of fraud, in association with a user ID (one example of "identification information") that is assigned to identify each user in an electronic payment service. Note that, although an example in which payment service providing apparatus 100 stores in advance flag information indicating whether or not a user is suspected of fraud will be described below, this example is not limiting. For example, payment service providing apparatus 100 may determine whether or not user U-2 corresponds to a user suspected of fraud at the time when the above-mentioned link information LK-1 is opened by user U-2.

[0044] An example of a method for setting flag information will be described. For example, in a function for transmitting and receiving direct messages between users, payment service providing device 100 can determine whether a user is suspected of fraud based on setting information related to a block that is set for each sender / receiver of a direct message from another user. Setting information related to a block is an example of "information related to reception refusal setting". For example, if a user has received electronic money remittance from another user within a predetermined period and then set to refuse reception of direct messages from the user a predetermined number of times or more, payment service providing device 100 determines that the user is suspected of fraud. Then, payment service providing device 100 sets flag information indicating that the user is suspected of fraud in association with the user ID of the user. Payment service providing device 100 may also determine whether a user is suspected of fraud based on a remittance receipt history. Specifically, if a user has received more than a predetermined number of remittances from other users within a specified period, or if the amount received within a specified period exceeds a predetermined amount, the payment service providing device 100 may determine that the user who owns the user account for the electronic payment service corresponding to the receiving history is a user suspected of fraud.

[0045] Furthermore, payment service providing device 100 acquires the user ID of user U-2 through a receipt request sent from terminal device 10-2 (an example of a "device used by a remittance destination user") in response to an operation by user U-2 (an example of a "remittance destination user") on link information LK-1. Furthermore, payment service providing device 100 compares the user ID of user U-2 acquired from the receipt request with the user IDs stored in flag information storage unit 122, and if flag information indicating that the user is a suspected fraudster is associated with the user ID of user U-2, it presumes that user U-2 is a suspected fraudster.

[0046] In this way, the payment service providing device 100 of the embodiment obtains the user ID of the user (for example, user U-2) to whom the electronic money is to be sent from the receipt request sent in conjunction with an operation on link information LK-1 for transferring electronic money to another user, and can estimate whether the user to whom the electronic money is to be sent is a user suspected of fraud by checking whether the obtained user ID is associated with flag information in the flag information storage unit 122 indicating that the user is suspected of fraud.

[0047] In addition, if the payment service providing device 100 estimates that the remittance destination user is a suspected fraudulent user, it sends an approval request for the remittance to the remittance destination user, and executes the remittance process to the remittance destination user on the condition that an approval response approving the remittance to the remittance destination user is obtained from the remittance source user.

[0048] The flow up to when the payment service providing device 100 performs the remittance process will be explained. When the payment service providing device 100 estimates that the remittance destination user is a suspected fraudulent user, it transmits a receipt hold screen to the device used by the remittance destination user to notify that receipt of the remittance will be temporarily held. An example of the receipt hold screen according to the embodiment will be explained with reference to Fig. 2. Fig. 2 is a diagram showing a screen display example (part 1) according to the embodiment.

[0049] For example, if the payment service providing device 100 presumes that the user U-2 who sent the receipt request is a suspected fraudulent user, the payment service providing device 100 displays a receipt pending screen AG-1 via a payment application running on the terminal device 10-2, as shown in Figure 2. The receipt pending screen AG-1 displays a message M-3 indicating that the receipt of the remittance corresponding to the receipt request of user U-2 is temporarily pending.

[0050] Furthermore, for example, if the payment service providing device 100 is presumed to be a fraudulent user who has sent the receipt request, it sends a warning screen to notify a warning regarding the remittance to the terminal device 10-1 (an example of a "device used by the remittance user") of the remittance source user U-1 who provided the link information LK-1 for transferring electronic money to user U-2. An example of the warning screen according to the embodiment will be described with reference to Figure 3. Figure 3 is a diagram showing a screen display example (part 2) according to the embodiment.

[0051] Furthermore, for example, if payment service providing device 100 presumes that user U-2, who has sent the receipt request, is a suspected fraudulent user, it displays a warning screen AG2 via the payment app running on terminal device 10-1, as shown in Figure 3. Warning screen AG2 is provided with a button OB-1 for sending a remittance request to payment service providing device 100, a button OB-2 for sending a remittance cancellation request to payment service providing device 100, and a button OB-3 for contacting the remittance destination user.

[0052] For example, button OB-1 may be enabled to be operable on the condition that a checkbox "confirm the above contents and send" is checked. In the case shown in FIG. 3, when terminal device 10-1 accepts operation of button OB-1 by user U-1, it transmits a remittance request corresponding to the pending receipt request to payment service providing device 100. The remittance request functions as an approval response to approve the remittance to the remittance destination user. When payment service providing device 100 receives the remittance request from terminal device 10-1, it releases the hold on the receipt request so that user U-2 can perform the receipt operation. Then, payment service providing device 100 executes the remittance process corresponding to the receipt request in accordance with the receipt operation of user U-2.

[0053] Also, in the case shown in FIG. 3, when terminal device 10-1 accepts operation of button OB-2 by user U-1, it sends a remittance cancellation request to payment service providing device 100, requesting cancellation of the remittance corresponding to the pending receipt request. When payment service providing device 100 receives the remittance cancellation request from terminal device 10-1, it cancels the remittance corresponding to the pending receipt request. Then, as shown in FIG. 2, payment service providing device 100 sends a remittance cancellation screen AG1-2 to terminal device 10-2 used by user U-2, the remittance destination user, to notify that the remittance has been canceled by user U-1, the remittance source user. On remittance cancellation screen AG1-2, a message M-4 is displayed to the effect that the remittance corresponding to the pending receipt request has been canceled.

[0054] 3, when terminal device 10-1 accepts operation of button OB-3 by user U-1, it executes processing for sending a direct message to remittance destination user U-2, using a function of the payment app. For example, if remittance destination user U-2 is not registered as a friend in the payment app, terminal device 10-1 may display a confirmation notification for whether or not to register user U-2 as a friend. If remittance destination user U-2 is registered as a friend in the payment app, terminal device 10-1 may display a message sending screen.

[0055] Furthermore, warning screen AG2 shown in Figure 3 is provided with link information LK-2 for displaying information showing past remittance cases by users suspected of fraud. When terminal device 10-1 accepts an operation of link information LK-2 by user U-1, it sends a request to payment service providing device 100 to obtain information showing past remittance cases by users suspected of fraud. When payment service providing device 100 receives a request to obtain information showing past remittance cases from terminal device 10-1, it sends information showing past remittance cases by users suspected of fraud to terminal device 10-1. Terminal device 10-1 displays the information showing past remittance cases by users suspected of fraud received from payment service providing device 100.

[0056] 2. Configuration of payment service providing device 100 An example of the functional configuration of payment service providing device 100 according to an embodiment will be described below with reference to Fig. 4. Fig. 4 is a diagram showing an example of the configuration of payment service providing device 100 according to an embodiment. As shown in Fig. 4, payment service providing device 100 has a communication unit 110, a storage unit 120, and a control unit 130.

[0057] (Regarding communication unit 110) The communication unit 110 is realized by, for example, a network interface card (NIC) etc. The communication unit 110 is connected to the network N by wire or wirelessly, and transmits and receives information to and from other devices such as the terminal device 10 and the message service providing device 20.

[0058] (Regarding the storage unit 120) The storage unit 120 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk or an optical disk. As shown in FIG. 4, the storage unit 120 has a setting information storage unit 121, a flag information storage unit 122, and a receiving history storage unit 123.

[0059] (Regarding the setting information storage unit 121) When refusing to receive a direct message, the setting information storage unit 121 stores setting information (an example of "information related to reception refusal settings") related to blocks set by a service user of an electronic payment service for each service user who is a recipient of a direct message. Below, an overview of the setting information stored in the setting information storage unit 121 according to the embodiment will be described with reference to FIG. 5. FIG. 5 is a diagram showing an overview of the setting information according to the embodiment. Note that FIG. 5 shows an example of the setting information according to the embodiment, and information other than that shown in FIG. 5 may be included.

[0060] 5, the setting information stored in the setting information storage unit 121 has a number of items such as a "user ID" item, a "partner ID" item, a "block status" item, and a "block date and time" item. The information stored in these items of the setting information is associated with each other.

[0061] The "user ID" field stores a user ID, which is identification information unique to each service user in the electronic payment service. The user ID can be used to individually identify a service user of the payment service (e.g., user U shown in FIG. 1).

[0062] The "other user ID" field stores the user ID of another service user who has been registered as a friend by the service user in the electronic payment service.

[0063] The "block status" field contains information indicating whether or not direct messages from other service users who are registered as friends are refused, i.e., whether or not they are blocked. In the example shown in Fig. 5, when "blocked" is stored in the "block status" field, it indicates that direct messages from the service user are refused.

[0064] The "Block Date and Time" field stores information indicating the date and time when the service user set up the service to block receiving direct messages.

[0065] (Regarding the flag information storage unit 122) The flag information storage unit 122 stores flag information indicating whether or not a service user of an electronic payment service is a user suspected of fraud. Below, an overview of the flag information stored in the flag information storage unit 122 will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of flag information stored in the flag information storage unit 122 according to the embodiment. Note that Fig. 6 shows an example of flag information according to the embodiment, and information other than that shown in Fig. 6 may be included.

[0066] 6, the flag information stored in the flag information storage unit 122 has a plurality of items such as a “user ID” item and “flag information.” The information stored in these items of the flag information is associated with each other.

[0067] The "User ID" field stores a user ID, which is unique identification information for each service user in the electronic payment service. The user ID stored in the "User ID" field is the same as the user ID included in the setting information.

[0068] The "flag information" field stores flag information indicating whether or not the service user is a user suspected of fraud. In the example shown in FIG. 6, when the "flag information" field stores a value of "ON", it indicates that the user is suspected of fraud, and when the "flag information" field stores a value of "OFF", it indicates that the user is not suspected of fraud. The initial value of the "flag information" may be "OFF".

[0069] For example, the flag information storage unit 122 may store flag information indicating that the user is suspected of fraud, in association with the user ID of a user who has, within a specified period of time, set the setting to refuse to receive direct messages from another user after receiving a remittance from that user a specified number of times or more.

[0070] Furthermore, the content of the flag information stored in flag information storage unit 122 may be determined based on the result of a judgment of suspected fraud based only on the remittance receipt history. Specifically, when payment service providing device 100 has received remittances from other users a predetermined number of times or more within a predetermined period, or when the amount received within a predetermined period exceeds a predetermined amount, payment service providing device 100 may set flag information indicating that the user is suspected of fraud in flag information storage unit 122, in association with the user ID of the user who is the owner of the user account for the electronic payment service corresponding to the receipt history.

[0071] (Regarding the receipt history storage unit 123) The receipt history storage unit 123 stores the receipt history of electronic money received from other service users. Below, an overview of the receipt history stored in the receipt history storage unit 123 will be described with reference to Fig. 7. Fig. 7 is a diagram showing an example of a receipt history stored in the receipt history storage unit 123 according to the embodiment. Note that Fig. 7 shows an example of a receipt history according to the embodiment, and information other than that shown in Fig. 7 may be included.

[0072] 7, the receipt history stored in the receipt history storage unit 123 has multiple items such as a "user ID" item and a "receive history." The information stored in these items of the receipt history is associated with each other.

[0073] The "User ID" field stores a user ID, which is unique identification information for each service user in the electronic payment service. The user ID stored in the "User ID" field is the same as the user ID included in the setting information.

[0074] The "receiving history" item includes information such as the user ID corresponding to the service user who sent the electronic money, the amount of the received electronic money, and the receiving date and time.

[0075] In addition, the memory unit 120 is not particularly limited to storing information stored in the setting information memory unit 121, the flag information memory unit 122, and the receipt history memory unit 123, and may also store information indicating past cases of remittances by users suspected of fraud.

[0076] (Regarding the control unit 130) Control unit 130 is a controller, and is realized, for example, by a CPU (Central Processing Unit) or MPU (Micro Processing Unit) executing various programs stored in a storage device inside payment service providing apparatus 100 using RAM as a working area. Control unit 130 can also be realized, for example, by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

[0077] As shown in Figure 4, control unit 130 has setting unit 131, acquisition unit 132, estimation unit 133, and remittance processing unit 134, and each of these units realizes or executes the functions and actions of information processing described below. Note that control unit 130 may have new functional units different from the units shown in Figure 4 introduced in response to the expansion of various processes executed by payment service providing device 100.

[0078] (Regarding the setting unit 131) The setting unit 131 sets flag information based on the setting information stored in the setting information storage unit 121 and the receipt history stored in the receipt history storage unit 123. For example, based on the information on the block status and the blocked date and time included in the setting information and the information on the receipt date and time included in the receipt history, if the number of times that the user has set to refuse to receive direct messages from another user within a predetermined period of time after receiving remittances from the other user is equal to or greater than a predetermined number of times, the setting unit 131 determines that the user is a user suspected of fraud. Then, the setting unit 131 updates the setting of the flag information stored in the flag information storage unit 122 so that the flag information associated with the user ID of the user determined to be a user suspected of fraud is set to "ON".

[0079] Furthermore, the setting unit 131 may determine whether a user is suspected of fraud based only on the receipt history. For example, if a user has received remittances from other users a predetermined number of times or more within a predetermined period, or if the amount of remittances within a predetermined period exceeds a predetermined amount, the setting unit 131 may determine that the user, who is the owner of a user account for the electronic payment service corresponding to the receipt history, is a user suspected of fraud.

[0080] Furthermore, the setting unit 131 may determine whether or not the remittance destination user (for example, user U2 shown in FIG. 1 and FIG. 2) who operated the link information (for example, link information LK-1 shown in FIG. 1) is a user suspected of fraud at the timing when the link information is opened, and set the flag information based on the determination result. For example, when the setting unit 131 acquires, via the communication unit 110, a receipt request transmitted from the terminal device 10 used by the remittance destination user in association with the operation of the remittance destination user on the link information, the setting unit 131 acquires the setting information on the above-mentioned block corresponding to the remittance destination user or the above-mentioned receipt history. Then, the setting unit 131 judges whether or not the remittance destination user is a user suspected of fraud based on the acquired setting information on the block or the receipt history. The judgment method is the same as the above-mentioned example. When the setting unit 131 judges that the remittance destination user is a user suspected of fraud, the setting unit 131 sets flag information indicating that the remittance destination user is a user suspected of fraud in the flag information storage unit 122 in association with the user ID of the remittance destination user.

[0081] (Regarding the acquisition unit 132) The acquisition unit 132 acquires the user ID of the remittance destination user through a receipt request transmitted from a device used by the remittance destination user in response to an operation of the remittance destination user on the link information. For example, the acquisition unit 132 acquires the user ID of the remittance destination user who is the sender of the receipt request in response to a receipt request for electronic money. The acquisition unit 132 passes the acquired user ID to the estimation unit 133.

[0082] (Regarding the estimation unit 133) The estimation unit 133 compares the user ID of the remittance destination user acquired by the acquisition unit 132 with the user ID stored in the flag information storage unit 122, and if flag information indicating that the remittance destination user is a user suspected of fraud is associated with the user ID of the remittance destination user, it estimates that the remittance destination user is a user suspected of fraud. In other words, if flag information indicating that the remittance destination user is a user suspected of fraud is associated with the user ID of the remittance destination user, the estimation unit 133 considers the remittance destination user to be a user suspected of fraud. The estimation unit 133 passes the processing result indicating that the remittance destination user is a user suspected of fraud to the remittance processing unit 134.

[0083] (Regarding the remittance processing unit 134) When the estimation unit 133 estimates that the remittance destination user is a user suspected of fraud, the remittance processing unit 134 sends an approval request for the remittance to the remittance destination user, and executes the remittance process for the remittance destination user on the condition that an approval response approving the remittance to the remittance destination user is obtained from the remittance source user.

[0084] In addition, if the estimation unit 133 determines that the remittance destination user is a user suspected of fraud, the remittance processing unit 134 sends a receipt hold screen (see, for example, Figure 2) to the terminal device 10 used by the remittance destination user to notify that receipt of the remittance will be temporarily held.

[0085] In addition, if the remittance processing unit 134 estimates that the remittance destination user is a user suspected of fraud, it sends a warning screen (see, for example, Figure 3) to the terminal device 10 used by the remittance source user to notify the user of a warning regarding the remittance prior to sending an approval request.

[0086] In addition, if the remittance processing unit 134 receives an approval response from the remittance source user via the warning screen, it executes the remittance process for the remittance destination user, and if it receives a request to cancel the remittance to the remittance destination user, it cancels the remittance to the remittance destination user.

[0087] In addition, when the remittance processing unit 134 cancels the remittance process for the remittance destination user in accordance with a remittance cancellation request, it sends a remittance cancellation screen (see, for example, Figure 2) to the terminal device 10 used by the remittance destination user to notify the user that the remittance has been canceled by the remittance source user.

[0088] [3. Example of processing procedure] (3-1. Remittance Processing) The flow of the remittance processing executed by the payment service providing apparatus 100 according to an embodiment will be described below with reference to Figure 8. Figure 8 is a flowchart showing one example of the processing procedure of the remittance processing executed by the payment service providing apparatus 100 according to an embodiment. The processing procedure shown in Figure 8 is executed by the control unit 130 possessed by the payment service providing apparatus 100. The control unit 130 repeatedly executes the processing procedure shown in Figure 8 while the payment service providing apparatus 100 is operating.

[0089] As shown in FIG. 8, the acquisition unit 132 acquires the user ID of the remittance destination user who is the sender of the electronic money receive request (step S101).

[0090] Furthermore, the estimation unit 133 executes a fraudulent user estimation process for the remittance destination user (step S102).

[0091] Furthermore, the remittance processing unit 134 judges whether or not the remittance destination user is presumed to be a suspected fraudulent user in the fraudulent user presumption process (step S103).

[0092] If the remittance processing unit 134 determines, as a result of processing by the estimation unit 133, that the remittance destination user is estimated to be a user suspected of fraud (step S103; Yes), it sends a receipt hold screen to the remittance destination user's terminal device 10 to notify that the remittance will be temporarily held (step S104).

[0093] Furthermore, the remittance processing unit 134 transmits a warning screen to the terminal device 10 of the remittance source user to notify the terminal device 10 of a warning regarding the remittance (step S105).

[0094] Furthermore, the remittance processing unit 134 determines whether or not a remittance request has been received from the remittance source user (step S106).

[0095] When the remittance processing unit 134 determines that a remittance request has been accepted from the remittance source user (step S106; Yes), it executes remittance processing in response to the receipt request (step S107) and ends the processing procedure shown in FIG.

[0096] On the other hand, if the remittance processing unit 134 determines that a remittance request has not been accepted from the remittance source user (step S106; No), it determines whether or not a remittance cancellation request has been accepted from the remittance source user (step S108).

[0097] If the remittance processing unit 134 determines that a remittance cancellation request has not been accepted from the remittance sending user (step S108; No), it determines whether a predetermined time has passed since the creation of the link information corresponding to the receipt request, based on information indicating the creation date and time of the link information included in the receipt request (step S109).

[0098] When the remittance processing unit 134 determines that a predetermined time has elapsed since the creation of the link information corresponding to the receipt request (step S109; Yes), it cancels the remittance corresponding to the receipt request (step S110).

[0099] Furthermore, the remittance processing unit 134 transmits a remittance cancellation screen to the terminal device 10 of the remittance destination user to notify the user that the remittance has been cancelled (step S111), and ends the processing procedure shown in FIG.

[0100] Furthermore, in step S109, if the remittance processing unit 134 determines that a predetermined time has not elapsed since the link information corresponding to the receipt request was created (step S109; No), the process proceeds to step S106.

[0101] Furthermore, in step S108, if the remittance processor 134 determines that a remittance cancellation request has been received from the remittance source user (step S108; Yes), the process proceeds to step S110.

[0102] Also, in the above step S103, if the remittance processing unit 134 determines that the remittance destination user is not estimated to be a user suspected of fraud as a result of processing by the estimation unit 133 (step S103; No), it proceeds to the processing procedure of the above step S107.

[0103] The processing procedures shown in FIG. 8 do not necessarily have to be executed in the order shown in FIG. 8. For example, the processing procedures corresponding to step S105 may be executed before the processing procedures corresponding to step S104. In this manner, the processing procedures that can be executed in any order may be rearranged as appropriate and executed in an order different from the example shown in FIG. 8.

[0104] (3-2. Fraudulent User Presumption Processing) Hereinafter, the flow of the fraudulent user inference process executed by the payment service providing device 100 according to the embodiment will be described with reference to Fig. 9. Fig. 9 is a flowchart showing an example of the processing procedure of the fraudulent user inference process executed by the payment service providing device 100 according to the embodiment. The processing procedure shown in Fig. 9 is executed by the control unit 130 possessed by the payment service providing device 100. The control unit 130 repeatedly executes the processing procedure shown in Fig. 9 while the payment service providing device 100 is operating.

[0105] As shown in FIG. 9, the estimation unit 133 refers to the flag information associated with the user ID of the remittance destination user, and determines whether the flag information associated with the user ID of the remittance destination user is a flag indicating that the user is suspected of fraud (step S201).

[0106] If the estimation unit 133 determines that the flag information associated with the user ID of the remittance destination user indicates that the user is suspected of fraud (step S201; Yes), it derives a processing result that infers that the remittance destination user is a user suspected of fraud (step S202), and terminates the processing procedure shown in Figure 9.

[0107] If the estimation unit 133 determines that the flag information associated with the user ID of the remittance destination user is not a user suspected of fraud (step S201; No), it derives a processing result that infers that the remittance destination user is not a user suspected of fraud (step S203), and terminates the processing procedure shown in Figure 9.

[0108] 4. Modifications (4-1. About message service rejection settings) In the above embodiment, an example has been described in which payment service providing device 100 infers a user suspected of fraud based on setting information related to a setting for refusing to receive direct messages that allow direct communication with other users through a payment app. Payment service providing device 100 does not need to be particularly limited to this example, and may infer a user suspected of fraud using, for example, a message blocking status in a message service. In this case, it is assumed that a user ID for identifying a user in each service is linked in advance between the electronic payment service and the message service.

[0109] Payment service providing apparatus 100 (for example, setting unit 131) periodically obtains, for a service user of the electronic payment service, a second user ID in the message service linked to a first user ID in the electronic payment service, and requests information regarding the settings for refusing to receive messages in the message service by the obtained user ID from message service providing apparatus 20. Payment service providing apparatus 100 also references the block date and time from the message blocking status included in the information regarding the settings for refusing to receive messages provided by message service providing apparatus 20. Then, payment service providing apparatus 100 compares the block date and time with the date and time of the electronic money receiving history by the corresponding user, to identify a user who has been blocked after receiving electronic money as a user suspected of fraud, and sets a flag in flag information storage unit 122.

[0110] (4-2. System configuration, etc.) The information processing system SYS according to the above-described embodiment (see, for example, Figure 1) may be configured to include multiple servers in which the processing functions corresponding to payment processing related to electronic payment services and the processing functions for executing the information processing according to the embodiment (see, for example, Figures 9 and 10) among the various processing functions possessed by the payment service providing device 100 are functionally or physically distributed.

[0111] In addition, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, and conversely, all or part of the processes described as being performed manually can be performed automatically by a known method. In addition, the information including the processing procedures, specific names, various data and parameters shown in the above documents and drawings can be changed arbitrarily unless otherwise specified. For example, the various information shown in each drawing is not limited to the illustrated information.

[0112] In addition, each component of each device shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit according to various loads, usage conditions, etc.

[0113] Furthermore, the above-described embodiments can be appropriately combined as long as the processing contents are not contradictory.

[0114] 5. Effects As described above, the payment service providing device 100 according to the embodiment is an information processing device that performs processing related to an electronic payment service that allows electronic money to be transferred between users using link information provided from a remittance source user (e.g., user U-1 shown in FIG. 1) who is a remittance source of electronic money to transfer electronic money to a remittance destination user (e.g., user U-2 shown in FIG. 1) who is a remittance destination of electronic money, and has a flag information storage unit 122, an acquisition unit 132, and an estimation unit 133. The flag information storage unit 122 stores in advance flag information indicating whether or not a user is suspected of fraud, in association with identification information given to identify each user in the electronic payment service. The acquisition unit 132 acquires the identification information (e.g., user ID) of the remittance destination user that is transmitted from a device used by the remittance destination user (e.g., terminal device 10-2 shown in FIG. 1) in association with an operation of the remittance destination user on the link information. The estimation unit 133 compares the identification information of the destination user acquired by the acquisition unit 132 with the identification information stored in the flag information storage unit 122, and if flag information indicating that the user is suspected of fraud is associated with the identification information of the destination user, it estimates that the destination user is a user suspected of fraud.

[0115] For this reason, the payment service providing device 100 of the embodiment can estimate whether a receiving user who receives electronic money using link information is a fraudulent user suspected of misusing the electronic payment service to steal electronic money, and can prevent fraudulent activities in electronic payment services.

[0116] Furthermore, payment service providing device 100 according to the embodiment further has a setting unit 131. When a receipt request is acquired, setting unit 131 acquires information regarding the reception refusal setting of direct messages corresponding to the remittance user or the reception history of the remittance, and determines whether or not the remittance destination user is a user suspected of fraud based on the acquired information regarding the reception refusal setting or the reception history, and sets flag information based on the determination result. This allows payment service providing device 100 to set appropriate flag information.

[0117] Moreover, the payment service providing apparatus 100 according to the embodiment further includes a remittance processing unit 134. When the remittance destination user is estimated by the estimation unit 133 to be a user suspected of fraud, the remittance processing unit 134 transmits an approval request for remittance to the remittance destination user, and executes remittance processing for the remittance destination user on the condition that an approval response to the effect of approving the remittance to the remittance destination user is obtained from the remittance source user. In this way, the payment service providing apparatus 100 can be expected to provide the remittance source user with an opportunity to confirm before remittance, and to prevent remittances against the remittance source user's will.

[0118] In addition, if the estimation unit 133 estimates that the remittance destination user is a user suspected of fraud, the remittance processing unit 134 may send a receipt hold screen (for example, the receipt hold screen AG1-1 shown in Figure 2) to the device used by the remittance destination user to notify that receipt of the remittance will be temporarily held.

[0119] In addition, if the estimation unit 133 estimates that the remittance destination user is a user suspected of fraud, the remittance processing unit 134 may send a warning screen (for example, warning screen AG2 shown in Figure 3) to the device used by the remittance source user to notify the user of a warning regarding the remittance prior to sending an approval request.

[0120] Furthermore, the remittance processing unit 134 may transmit, via the warning screen, information indicating past cases of remittances by users suspected of fraud to the device used by the remittance source user.

[0121] In addition, if the remittance processing unit 134 receives an approval response from the remittance source user via the warning screen, it executes the remittance process for the remittance destination user, and if it receives a request from the remittance source user to cancel the remittance to the remittance destination user, it may cancel the remittance to the remittance destination user.

[0122] In addition, when the remittance processing unit 134 cancels a remittance to a remittance destination user in accordance with a remittance cancellation request, the remittance processing unit 134 may send a remittance cancellation screen (for example, the remittance cancellation screen AG1-2 shown in Figure 2) to a device used by the remittance destination user to notify the user that the remittance has been canceled by the remittance source user.

[0123] Furthermore, setting unit 131 may refer to information regarding reception refusal settings, and if the number of times that the user has set the setting to refuse reception of direct messages from another user after receiving remittance from that user within a predetermined period of time is equal to or greater than a predetermined number, determine that the user is a user suspected of fraud. This allows payment service providing device 100 to appropriately determine whether a user is suspected of fraud.

[0124] Furthermore, setting unit 131 may refer to the receipt history and determine that a user is suspected of fraud if the user has received remittances from other users a predetermined number of times or more within a predetermined period, or if the amount received within a predetermined period exceeds a predetermined amount. This allows payment service providing device 100 to appropriately determine whether a user is suspected of fraud.

[0125] In this way, payment service providing device 100 can be expected to be effective in preventing damage caused by fraudulent activities by the processes executed by each of the above-mentioned units, or any combination of the processes executed by each unit.

[0126] [6. Hardware Configuration] Moreover, payment service providing apparatus 100 according to the above-described embodiment or modification is realized, for example, by a computer 1000 having a configuration as shown in Figure 11. Figure 11 is a hardware configuration diagram showing an example of a computer that realizes the functions of payment service providing apparatus 100 according to the embodiment or modification.

[0127] The computer 1000 is connected to an output device 1010 and an input device 1020, and has a configuration in which an arithmetic unit 1030, a primary storage device 1040, a secondary storage device 1050, an output IF (Interface) 1060, an input IF 1070, and a network IF 1080 are connected via a bus 1090.

[0128] The arithmetic device 1030 operates based on programs stored in the primary storage device 1040 and the secondary storage device 1050 and programs read from the input device 1020, and executes various processes. The primary storage device 1040 is a memory device, such as a RAM, that temporarily stores data used by the arithmetic device 1030 for various calculations. The secondary storage device 1050 is a storage device in which data used by the arithmetic device 1030 for various calculations and various databases are registered, and is realized by a ROM (Read Only Memory), HDD, flash memory, etc.

[0129] The output IF 1060 is an interface for transmitting information to be output to an output device 1010 that outputs various types of information, such as a monitor or a printer, and is realized by a connector conforming to a standard such as USB (Universal Serial Bus), DVI (Digital Visual Interface), or HDMI (High Definition Multimedia Interface), a registered trademark. The input IF 1070 is an interface for receiving information from various input devices 1020, such as a mouse, keyboard, and scanner, and is realized by a USB, for example.

[0130] The input device 1020 may be a device that reads information from an optical recording medium such as a CD (Compact Disc), a DVD (Digital Versatile Disc), or a PD (Phase change rewritable Disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. The input device 1020 may also be an external storage medium such as a USB memory.

[0131] The network IF 1080 receives data from other devices via the network N and sends it to the arithmetic device 1030, and also transmits data generated by the arithmetic device 1030 to other devices via the network N.

[0132] The arithmetic unit 1030 controls the output device 1010 and the input device 1020 via the output IF 1060 and the input IF 1070. For example, the arithmetic unit 1030 loads a program from the input device 1020 or the secondary storage device 1050 onto the primary storage device 1040 and executes the loaded program.

[0133] For example, when computer 1000 functions as payment service providing apparatus 100 according to an embodiment or modification, arithmetic device 1030 of computer 1000 realizes functions similar to those of control unit 130 by executing a program (e.g., an information processing program) loaded onto primary storage device 1040. That is, arithmetic device 1030 realizes the processing by payment service providing apparatus 100 according to the embodiment or modification in cooperation with a program (e.g., an information processing program) loaded onto primary storage device 1040.

[0134] [7. Other] Although some of the embodiments of the present application have been described in detail above with reference to the drawings, these are merely examples, and the present invention can be embodied in other forms that incorporate various modifications and improvements based on the knowledge of those skilled in the art, including the forms described in the Disclosure of the Invention section.

[0135] Further, the configuration of payment service providing apparatus 100 described above can be flexibly changed, for example, by calling an external platform or the like using an API (Application Programming Interface) or network computing, depending on the function.

[0136] Furthermore, the term "unit" in the claims may be read as "means" or "circuit," etc. For example, a control unit may be read as control means or a control circuit. [Explanation of symbols]

[0137] 10-1, 10-2 Terminal equipment 20 Message service providing device 100 Payment service providing device 110 Communications Department 120 Storage section 121 Setting information storage unit 122 Flag information storage unit 123 Receipt history memory unit 130 Control section 131 Setting section 132 Acquisition Department 133 Estimation Department 134 Remittance Processing Unit

Claims

1. An information processing device that performs processing related to an electronic settlement service that allows transfer of electronic money between users using link information provided from a remittance source user who is a remittance source of electronic money to a remittance destination user who is a remittance destination of electronic money in order to transfer the electronic money, comprising: a flag information storage unit that stores in advance flag information indicating whether or not a user is suspected of fraud in association with identification information given to identify each user in an electronic payment service; an acquisition unit that acquires, in response to an operation performed by the remittance destination user, remittance destination identification information, which is the identification information for identifying the remittance destination user who operated the link information, through a receipt request transmitted from a device used by the remittance destination user, for the link information linking information linking information on the remittance amount designated by the remittance source user with remittance source identification information, which is the identification information for identifying the remittance source user; an estimation unit that compares the remittance destination identification information acquired by the acquisition unit with the identification information stored in the flag information storage unit, and infers that the remittance destination user is the user suspected of fraud if the identification information that matches the remittance destination identification information is associated with the flag information indicating that the user is suspected of fraud; a remittance processing unit that, when the estimation unit estimates that the remittance destination user is the user suspected of fraud, sends to the remittance source user a request for approval of the remittance to the remittance destination user based on the remittance source identification information included in the receipt request, and executes a remittance process for the remittance destination user on condition that an approval response to the effect that the remittance to the remittance destination user is approved is obtained from the remittance source user; 13. An information processing device comprising:

2. a setting unit that, when acquiring the receipt request, acquires information regarding the reception refusal setting of the direct message corresponding to the remittance destination user or a receipt history of the remittance, determines whether the remittance destination user is a user suspected of fraud based on the acquired information regarding the reception refusal setting or the receipt history, and sets the flag information based on the determination result.

2. The information processing apparatus according to claim 1, further comprising:

3. The remittance processing unit is When the estimation unit estimates that the remittance destination user is a user suspected of fraud, the estimation unit transmits a receipt hold screen to notify the remittance destination user that receipt of the remittance corresponding to the receipt request will be temporarily held, via a payment application running on a device used by the remittance destination user.

2. The information processing apparatus according to claim 1,

4. The remittance processing unit is If the estimation unit estimates that the remittance destination user is a user suspected of fraud, a warning screen is sent to a device used by the remittance source user prior to the approval request, to notify the remittance source user of a warning.

2. The information processing apparatus according to claim 1,

5. The remittance processing unit is Through the warning screen, information indicating past cases of remittances by the suspected fraudulent user is transmitted to a device used by the remittance source user.

5. The information processing apparatus according to claim 4.

6. The remittance processing unit is When the approval response is received from the remittance source user via the warning screen, a remittance process for the remittance destination user is executed, and when a cancellation request for the remittance to the remittance destination user is received from the remittance source user, the remittance to the remittance destination user is cancelled.

5. The information processing apparatus according to claim 4.

7. The remittance processing unit is When the remittance to the remittance destination user is cancelled in accordance with the remittance cancellation request, a remittance cancellation screen is sent to a device used by the remittance destination user to notify the remittance destination user that the remittance has been cancelled by the remittance source user.

2. The information processing apparatus according to claim 1,

8. The setting unit is The information regarding the reception refusal setting is referred to, and if the number of times that the user has set the reception refusal setting to refuse reception of direct messages from the other user after receiving remittance from the other user within a predetermined period of time is equal to or exceeds a predetermined number, the user is determined to be a user suspected of fraud.

3. The information processing apparatus according to claim 2.

9. The setting unit is By referring to the receipt history, if a user has received remittances from other users a predetermined number of times or more within a predetermined period, or if the amount of remittances within a predetermined period exceeds a predetermined amount, the user is determined to be a user suspected of fraud.

3. The information processing apparatus according to claim 2.

10. The link information is Provided from the remittance source user to the remittance destination user through a service different from the electronic payment service 10. The information processing device according to claim 1,

11. 1. An information processing method executed by a computer that performs processing related to an electronic settlement service that enables transfer of electronic money between users using link information provided from a remittance source user who is a remittance source of electronic money to a remittance destination user who is a remittance destination of electronic money in order to transfer the electronic money, comprising: an acquisition step of acquiring, with respect to the link information linking information on the remittance amount designated by the remittance source user with remittance source identification information which is identification information for identifying the remittance source user, remittance destination identification information which is identification information for identifying the remittance destination user who operated the link information through a receipt request transmitted from a device used by the remittance destination user in response to an operation performed by the remittance destination user; an estimation step of comparing the remittance destination identification information acquired in the acquisition step with identification information stored in a flag information storage unit that stores in advance flag information indicating whether the user is suspected of fraud, in association with the identification information given to identify each user in the electronic payment service, and estimating that the remittance destination user is the user suspected of fraud if the flag information is associated with the identification information that matches the remittance destination identification information; a remittance processing step of, when the remittance destination user is estimated to be the user suspected of fraud by the estimation step, sending to the remittance source user an approval request for the remittance to the remittance destination user based on the remittance source identification information included in the receipt request, and executing a remittance process for the remittance destination user on condition that an approval response to the effect that the remittance to the remittance destination user is approved is obtained from the remittance source user; 13. An information processing method comprising:

12. A computer that performs processing related to an electronic settlement service that enables transfer of electronic money between users using link information provided from a remittance source user who is a remittance source of electronic money to a remittance destination user who is a remittance destination of electronic money in order to transfer the electronic money, an acquisition step of acquiring, through a receipt request transmitted from a device used by the remittance destination user in response to an operation performed by the remittance destination user, remittance destination identification information, which is identification information for identifying the remittance destination user who operated the link information, for link information linking information on the remittance amount designated by the remittance source user with remittance source identification information, which is identification information for identifying the remittance source user; an estimation step of comparing the remittance destination identification information acquired by the acquisition step with identification information stored in a flag information storage unit that stores in advance flag information indicating whether the user is suspected of fraud, in association with the identification information assigned to identify each user in the electronic payment service, and estimating that the remittance destination user is the user suspected of fraud if the flag information is associated with the identification information that matches the remittance destination identification information; a remittance processing procedure for, when the remittance destination user is estimated to be the user suspected of fraud by the estimation procedure, sending to the remittance source user an approval request for remittance to the remittance destination user based on the remittance source identification information included in the receipt request, and executing a remittance process for the remittance destination user on condition that an approval response to the effect that the remittance to the remittance destination user is approved is obtained from the remittance source user; An information processing program characterized by causing the program to execute the above steps.

Citation Information

Patent Citations

  • Target user group determination method and device

    CN111242763A

  • Transaction management system, automatic equipment, transaction management method, and account host

    JP2008234300A

  • Automatic transaction device

    JP2009157594A

  • Method and apparatus for improving security of toll charging

    JP2017526317A

  • Provision device, provision method, and provision program

    JP2021157715A

Cited By

  • Application programs and service delivery systems

    JP2026132106A

  • Monitoring device, monitoring method, and program

    JP2026156312A

  • Monitoring device, monitoring method, and program

    JP2026159485A

  • Monitoring device, monitoring method, and program

    JP7789973B1