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

Abstract

To improve the usability of electronic payment services. [Solution] The information processing device according to the present application has an identification information storage unit, a payment processing unit, a linkage confirmation processing unit, and a benefit granting unit. When the linkage confirmation processing unit confirms that a user who is the source of payment in a payment process is already linked to a second service as a member of the store that is the destination of payment in the payment process, the information processing device grants the user who is the source of payment a benefit that can be used only at the store where the payment was made.

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] For example, in relation to the granting of benefits in accordance with the use of electronic payment services, technologies have been proposed that allow users to purchase coupons in exchange for points awarded when making payments using electronic payment services, as well as technologies that grant stamps in accordance with users' orders in commercial transactions. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2014-071536 A [Patent Document 2] JP 2023-079883 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, the above-mentioned conventional techniques leave room for improvement in terms of improving the usability of electronic payment services.

[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 improve the usability of 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 a first service that provides cashless payment using code information, and includes an identification information storage unit, a payment processing unit, a linkage confirmation processing unit, and a benefit granting unit. The identification information storage unit stores identification information for identifying a user who is linked to a second service, which is different from the first service, as a member of a store that is an affiliated store that can use the first service, in a second service different from the first service, in association with a first user ID unique to each user in order to individually identify each user who uses the first service. In response to receiving a payment request related to the first service, the payment processing unit executes processing related to the payment corresponding to the payment request, and transmits a payment ID for identifying the payment to a terminal device used in the store where the payment is made. In response to receiving the payment request, the linkage confirmation processing unit acquires identification information from the identification information storage unit using the first user ID included in the payment request as a key, and transmits a confirmation request including the acquired identification information to another information processing device that performs processing related to the second service, thereby confirming whether or not the user who is the sender of the payment request is already linked to the second service as a member of the store. When the link confirmation processing unit confirms that the user who is the payer in the payment process is already linked to the second service as a member of the store to which the payment is made in the payment process, the benefit granting unit grants the paying user a benefit that can only be used at the store where the payment was made. Effect of the Invention

[0008] According to one aspect of the embodiment, it is possible to provide an effect of improving the usability of electronic payment services. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram for explaining an overview of processing that is a premise of information processing according to the embodiment. [Diagram 2] FIG. 2 is a diagram for explaining an overview of information processing according to the embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of the configuration of a payment service providing device according to an embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of cooperation information stored in a cooperation information storage unit according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of point information stored in a point information storage unit according to the embodiment. [Figure 6] FIG. 6 is a flowchart illustrating an example of a processing procedure of the association information registration processing executed by the payment service providing device according to the embodiment. [Figure 7] FIG. 7 is a flowchart illustrating an example of a processing procedure of a payment-related process executed by the payment service providing device according to the embodiment. [Figure 8] FIG. 8 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 described in detail 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.

[0012] As shown in FIG. 1, an information processing system according to an embodiment includes a user device 10, a message service providing device 30, and a payment service providing device 100. User device 10, message service providing device 30, and payment service providing device 100 are connected to a network N (e.g., see FIG. 6) by wire or wirelessly. User device 10, message service providing device 30, 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 shown in Fig. 1 is an example, and the information processing system may include more user devices 10 than those illustrated in Fig. 1, or may include other devices other than those illustrated in Fig. 1. For example, the other devices may include a store device 20 (see Fig. 2 and Fig. 6, for example) described later.

[0014] 1 is an information processing device that executes information processing according to an embodiment, and is operated and managed by a service provider that provides, for example, an electronic payment service using predetermined code information (hereinafter simply referred to as a "payment service"). 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.

[0015] The payment service (an example of a "first service") provided by the payment service providing apparatus 100 shown in FIG. 1 enables a user U of a user device 10, who is a service user who uses the payment service, to easily pay for a transaction object. For example, the 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.

[0016] 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.

[0017] 1 (an example of an "other information processing device") is an information processing device that executes information processing related to a message service (an example of a "second service") for realizing online communication, and is operated and managed by a service provider that provides the message service. When the message service providing device 30 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.

[0018] User device 10 shown in Fig. 1 is an information processing terminal used by a user U who is a service user who uses online services such as the above-mentioned payment service and the message service provided by message service providing device 30. User device 10 can be realized, for example, by a smartphone, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, a PDA (Personal Digital Assistant), or the like. User device 10 can display information distributed by message service providing device 30, payment service providing device 100, or the like, by a web browser or an application.

[0019] Furthermore, when user device 10 shown in Fig. 1 receives control information for realizing predetermined information processing from message service providing device 30, 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 30, payment service providing device 100, or the like may be regarded as control information.

[0020] (1-2. Payment Using User Device 10) Here, code payment will be described as an example of electronic payment executed using the user device 10. When the user device 10 is a smartphone, code payment executed using the user 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 user 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 user 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. In addition, 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.

[0021] 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 an application program (hereinafter referred to as a "payment app") that is pre-installed in the user 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 user 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 user 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."

[0022] When payment service providing device 100 accepts transaction information from user 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 user device 10. In such a case, user 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.

[0023] It should be noted that the payment using the user device 10 is not limited to the above-mentioned process. For example, the payment using the user device 10 may be made using a terminal device (hereinafter referred to as a "store terminal") installed in a specific store. Specifically, the user 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 user 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."

[0024] 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 user device 10. The store terminal or user 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.

[0025] Furthermore, the payment using the user 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 previously registered by the user U. In such a case, for example, the user 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.

[0026] Furthermore, settlement using user 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, user 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 user that the remittance has been completed by outputting a screen or a predetermined sound indicating that the remittance has been completed to user device 10 or the terminal device used by the remittance user.

[0027] Note that remittance using user device 10 is not limited to the above-mentioned process. For example, remittance using user 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 user device 10. To give a specific example, user device 10 accepts input of the telephone number or user ID of the remittance destination user 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.

[0028] 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, user device 10 accepts from user U the designation of a user (remittance destination) registered in the payment app and an input of the remittance amount to the user, and transmits to payment service providing device 100 the telephone number or user ID linked to the designated user, the remittance amount, and user identification information for identifying user U.

[0029] Furthermore, for example, remittance using user device 10 may be performed by providing link information for receiving the remittance amount to the remittance user. As a specific example, user 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 a terminal device 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.

[0030] The above-mentioned payment means and 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 payment services may have a function related to remittance between accounts held by multiple users. That is, the above-mentioned payment means and 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 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 controls 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 "settlement" 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.

[0031] (1-3.Premise) Conventionally, application programs (hereinafter referred to as "official store apps") created independently by stores that provide products and services are provided to general users for the purpose of reducing costs, increasing customer attraction rates, improving business efficiency, and the like. It is also assumed that a store user (e.g., user U shown in FIG. 1) who downloads and uses this official store app is a service user who uses a payment service. If a store that provides the official store app is an affiliated store that introduces a payment service, the store user can use the payment service to pay for a transaction at the store. In this case, in order for a store user to receive benefits through the official store app at an affiliated store, it is necessary to display not only the screen of the payment app on his / her own terminal (e.g., user device 10 shown in FIG. 1) but also the screen of the store app in order to make a payment. In this way, when a service user who uses a payment service makes a payment using the payment service at a store that provides the official store app, there is a considerable amount of work involved in launching each app and displaying the screen, and there is room for improvement in terms of usability.

[0032] Therefore, in order to address these problems, the present application implements the embodiment described below. An outline of the process that is the premise of the information processing according to the embodiment will be described below. FIG. 1 is a diagram for explaining the outline of the process that is the premise of the information processing according to the embodiment. FIG. 1 assumes, as the premise of the information processing according to the embodiment, a case in which a user U, who is a service user who uses a payment service and a message service, creates a membership card in the message service in order to link an official store app to the message service.

[0033] 1, the user U operates the user device 10 to send a membership card issuance request to the message service providing device 30 to request the issuance of a membership card (step S01-1). For example, the user U can use the user device 10 to read code information (hereinafter referred to as the "store installation code") installed at a store that is an affiliated store, thereby causing the user device 10 to display a predetermined procedure screen AG1 for carrying out the membership card issuance procedure. The procedure screen AG1 displays the conditions for issuing a membership card, and has a button OB1 for requesting the issuance of a membership card.

[0034] The user U can transmit a membership card issuance request to the message service providing device 30 through the procedure screen AG1. Specifically, when the user U operates a button OB1 for requesting issuance of a membership card provided on a predetermined procedure screen AG1, the user device 10 transmits the membership card issuance request to the message service providing device 30. In addition, for example, the user U can also cause the user device 10 to display the above-mentioned procedure screen AG1 from an official store app displayed on the user device 10.

[0035] The membership card issuance request sent from the user device 10 to the message service providing device 30 includes a store user ID (e.g., SU#001) unique to each store user, which is identification information for individually identifying the user U at the store that is the above-mentioned affiliated store, and a store ID (e.g., S#001) unique to each store, which is identification information for individually identifying the store that is an affiliated store in the message service and payment service.

[0036] When the message service providing device 30 receives a membership card issuance request from the user U through the above-mentioned procedure screen AG1, it requests input of a message service user ID (e.g., MSU#001) unique to each service user, which is identification information for individually identifying the user U in the message service, and executes identity verification processing for the user U. Then, if the identity verification processing is successful, the message service providing device 30 registers the above-mentioned message service ID, shop user ID, and shop ID in association with each other (step S01-2). Then, the message service providing device 30 transmits a membership card issuance notification to the user device 10 to notify the user U that the issuance of the membership card has been completed (step S01-3).

[0037] The user device 10 displays the membership card issuance notification sent from the message service providing device 30. The user device 10 also displays a membership card display screen AG2 displaying the membership card in response to an operation by the user U. As shown in Fig. 1, the user device 10 displays an image CG2 showing the latest membership card created this time in the foreground, superimposed on an image CG1 of an existing membership card that has already been created.

[0038] Furthermore, message service providing device 30 transmits the above-mentioned message service ID and shop ID together with user U's personal identification information to payment service providing device 100 as linking information (step S01-4).

[0039] When payment service providing device 100 receives the message service ID and store ID transmitted as association information from message service providing device 30, it identifies a payment service user ID (e.g., PSU#001) unique to each service user, which is identification information for individually identifying user U in the payment service, based on the identity verification information received together with the association information. Then, payment service providing device 100 associates and registers the identified payment service user ID with the message service ID and store ID received as association information (step S01-5).

[0040] In this way, payment service providing device 100 can manage in association with the payment service user ID, message service user ID, and store ID held by user U. That is, payment service providing device 100 uses the payment service user ID ("first user ID") included in the payment request as a key, associates the message service user ID and store ID with a payment service user ID unique to each user in order to individually identify each user who uses the payment service ("first service"), and holds the message service user ID and store ID as identification information for identifying a user who is linked to a message service as a member of a store that is an affiliated store in a message service ("second service") different from the payment service.

[0041] Note that payment service providing device 100 is not particularly limited to managing a message service user ID and a store ID as the identification information, and may manage identification information unique to each combination of a store and a member managed by the store as a customer as the identification information. In this case, payment service providing device 100 acquires identification information unique to each combination of a store and a member managed by the store as a customer from message service providing device 30 as association information, and manages the acquired identification information in association with a payment service user ID identified based on the identity verification information received together with the association information.

[0042] Furthermore, the information linkage of various IDs and the like executed between payment service providing device 100 and message service providing device 30 does not need to be particularly limited to the above example, and may be executed by existing ID linkage technology according to an instruction from user U. For example, payment service providing device 100 transmits a linkage request for account information related to the message service to user U through the payment app. Then, payment service providing device 100 has user U log in to the message app through the payment app. This allows payment service providing device 100 and message service providing device 30 to respectively link the payment service user ID and the message service user ID in advance. In this case, payment service providing device 100 can link the message service ID and the store ID provided as linkage information from message service providing device 30 based on the linkage between the payment service user ID and the message service user ID in advance. Alternatively, message service providing device 30 transmits a linkage request for account information related to the payment service to user U through the message app. Then, message service providing device 30 has user U log in to the payment app through the message app. This allows payment service providing device 100 and message service providing device 30 to respectively link the payment service user ID and the message service user ID in advance. In this case, payment service providing device 100 can link the message service ID and the store ID provided as linkage information from message service providing device 30, based on the prior linkage between the payment service user ID and the message service user ID.

[0043] (1-4. Overview of Information Processing According to the Embodiment) Hereinafter, an overview of information processing according to an embodiment will be described with reference to Fig. 2. Fig. 2 is a diagram for explaining an overview of information processing according to an embodiment. Fig. 2 shows an example of information processing that enables a user U who has been issued a membership card in a message service to receive a benefit corresponding to an official store app when making a payment using a payment service, without presenting a screen of the official store app to the store.

[0044] As shown in Fig. 2, a user U makes a payment using a payment service (e.g., code payment) to pay for a transaction at a store. When a store device 20 (an example of a "terminal device used in a store") reads predetermined code information displayed on a user device 10 by the user U, the store device 20 transmits a payment request including the read information to the payment service providing device 100 (step S1-1). Note that, although step S1-1 illustrates an example in which code payment is made using a store scan method, code payment may also be made using a user scan method.

[0045] In response to receiving the payment request, the payment service providing device 100 executes a payment process corresponding to the payment request (step S1-2). In addition, the payment service providing device 100 transmits a payment ID for identifying the payment corresponding to the payment request to the in-store device 20 where the payment was made (step S1-3).

[0046] In-store device 20 stores and manages the payment ID received from payment service providing device 100 in a predetermined database or the like (step S1-4).

[0047] In addition, upon completion of the payment processing, the payment service providing device 100 acquires the payment service user ID included in the payment request as a key for identification information, and sends a confirmation request including the acquired identification information to the message service providing device 30, thereby executing a linkage confirmation process to confirm whether user U, who is the source of payment in the payment processing, is linked to the message service as a member of the store to which the payment is made in the payment processing, i.e., whether the membership card is held in a valid state in the message service (step S1-5).

[0048] For example, the payment service providing device 100 acquires the payment service user ID and the store ID as identification information using the payment service user ID included in the payment request as a key, and transmits a confirmation request including the acquired payment service user ID and store ID to the message service providing device 30 to acquire a linkage flag (an example of "confirmation result information") indicating whether or not the user U, who is the source of payment in the payment process, is linked to the message service as a member of the store to which the payment is made in the payment process. If the linkage flag is "Yes", the payment service providing device 100 derives a confirmation result that the user U, who is the source of payment in the payment process, is linked to the message service as a member of the store to which the payment is made in the payment process, i.e., that the user U holds a membership card for the store to which the payment is made in the message service. On the other hand, if the linkage flag is "No", the payment service providing device 100 derives a confirmation result that user U, who is the source of payment in the payment processing, is not already linked to the message service as a member of the store to which the payment is made in the payment processing, that is, that user U holds a membership card for the store to which the payment is made in the message service.

[0049] Furthermore, payment service providing apparatus 100 may execute the linkage confirmation process of step S1-5 using an API (Application Programming Interface) provided by a service provider that operates the message service. For example, payment service providing apparatus 100 may use the API to access a membership card management system in which information related to membership cards is managed in message service providing apparatus 30, and confirm whether identification information linked to a payment service user ID is managed, thereby confirming whether user U, who is the source of payment in the payment process, is in a state of being linked to the message service as a member of the store that is the destination of payment in the payment process, i.e., whether the membership card is held in a valid state in the message service.

[0050] In addition, when the payment service providing device 100 derives the confirmation result that the user U, who is the source of payment in the payment processing, is already linked to the message service as a member of the store to which the payment is to be made in the payment processing, it sends a payment completion notification to the user device 10 (step S1-6).

[0051] Furthermore, the payment service providing device 100 provides payment information regarding the payment processing executed in response to the payment request to the message service providing device 30 (step S1-7). Specifically, the payment service providing device 100 transmits a payment ID for identifying the payment for which the payment processing was executed, and a message service user ID and a store ID linked to the payment service user ID as payment information to the message service providing device 30, thereby providing them to the message service.

[0052] Furthermore, the payment service providing device 100 executes a point granting process associated with the payment process (step S1-8). Specifically, the payment service providing device 100 grants a benefit that can be used only at the store where the payment is made to the user U who is the payer of the price in the payment process. For example, the payment service providing device 100 may grant points that can be used to pay the price of the transaction object provided by the store, or may grant a coupon that can be used only at the store where the payment is made. Furthermore, the payment service providing device 100 manages information regarding the benefit held by the service user in association with the payment service user ID.

[0053] When the message service providing device 30 receives the payment information from the payment service providing device 100, it identifies the affiliated store where the payment was made based on the received payment information, and converts the message service user ID included in the payment information into a store user ID (step S1-9). In addition, the message service providing device 30 provides information to the store by transmitting the payment ID and the store user ID to the store device 20 (step S1-10).

[0054] The in-store device 20 executes a point giving process to give points to the user U who is a member, in accordance with the contents of the information received from the message service providing device 30 (step S1-11).

[0055] As described above, according to the information processing of the embodiment, when a user U who has been issued a membership card in a message service makes a payment using a payment service, the payment service providing device 100 can provide the message service with information on the user U who made the payment using the payment service and the store where the payment was made, on the condition that a membership card for the store to which the payment is to be made has been issued in the message service by the user U. This allows the user U to receive benefits corresponding to the official store app without presenting the screen of the official store app to the store to which the payment is to be made, thereby improving usability.

[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. 3. Fig. 3 is a diagram showing an example of the configuration of payment service providing device 100 according to an embodiment. As shown in Fig. 3, 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 user device 10, the store device 20, and the message service providing device 30.

[0058] (Regarding the storage unit 120) The storage unit 120 is realized by, for example, a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. As shown in Fig. 6, the storage unit 120 has a link information storage unit 121 (an example of a "specification information storage unit") and a point information storage unit 122 (an example of a "benefit information storage unit").

[0059] (Regarding the collaboration information storage unit 121) The link information storage unit 121 stores link information provided by the message service providing device 30. An example of link information stored in the link information storage unit 121 will be described below with reference to Fig. 4. Fig. 4 is a diagram showing an example of link information stored in the link information storage unit 121 according to the embodiment.

[0060] 4, the association information stored in association information storage unit 121 has multiple items such as a "payment service user ID" item, a "message service user ID" item, and a "store ID" item. The information stored in these items of the association information is associated with each other.

[0061] The "Payment Service User ID" field stores unique identification information (e.g., PSU#001) for each service user who uses the payment service in the payment service. The payment service user ID allows the service user of the payment service (e.g., user U shown in FIG. 1) to be individually identified.

[0062] The "message service user ID" item stores the message service user ID linked from the message service providing device 30. The message service user ID is identification information (e.g., MSU#001) unique to each service user who uses the message service in the message service. The message service user ID makes it possible to individually identify a message service user (e.g., user U shown in FIG. 1).

[0063] The "Store ID" field stores the store ID linked from the message service providing device 30. The store ID is unique identification information (e.g., S#001) for each store that is an affiliated store that introduces the payment service. The store ID makes it possible to individually identify stores that are affiliated with the message service and payment service. The store ID is information that pairs with the message service user ID stored in the "Message Service User ID" field.

[0064] In addition, when the association information storage unit 121 obtains unique identification information from the message service providing device 30 for each combination of a store and a member managed by the store as a customer, the association information storage unit 121 may store this identification information as association information in the association information storage unit 121, in correspondence with the payment service user ID.

[0065] (Regarding the point information storage unit 122) The point information storage unit 122 stores point information related to points held by a service user who uses a payment service. An example of point information stored in the point information storage unit 122 will be described below with reference to Fig. 5. Fig. 5 is a diagram showing an example of point information stored in the point information storage unit 122 according to the embodiment.

[0066] 5, the point information stored in the point information storage unit 122 has multiple items such as a "payment service user ID" item, a "normal point balance" item, a "limited point balance / compatible store ID" item, etc. The information stored in these items of the point information is mutually associated.

[0067] The "Payment Service User ID" field stores unique identification information (e.g., PSU#001) for each service user who uses the payment service in the payment service. The payment service user ID allows the service user of the payment service (e.g., user U shown in FIG. 1) to be individually identified.

[0068] The "regular points balance" item stores information indicating the balance of regular points granted to a service user (such as user U shown in FIG. 1) according to the payment amount when a payment is made using a payment service. Regular points can be used to pay for a price, for example, with 1 point being 1 yen, regardless of the store where the payment is made, when making a payment using a payment service.

[0069] The "Limited points balance / compatible store ID" field stores information indicating the balance of limited points granted to a service user according to the payment amount when a payment is made using a payment service, and information indicating a store ID unique to a store where the limited points can be used. When making a payment using a payment service, the limited points can be used to pay for a purchase only at the store where the payment is made, for example, with 1 point being 1 yen.

[0070] (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).

[0071] As shown in Fig. 3, control unit 130 has payment processing unit 131, cooperation confirmation processing unit 132, provision unit 133, and benefit granting 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 Fig. 3 introduced in response to the expansion of various processes executed by payment service providing device 100.

[0072] (Regarding the payment processing unit 131) In response to receiving a payment request for a payment service, the payment processing unit 131 executes a payment process corresponding to the payment request based on the payment information included in the payment request, and transmits a payment ID for identifying the payment for which the payment process was executed to the store device 20, which is a terminal device used in the store where the payment was made, via the communication unit 110.

[0073] (Regarding the cooperation confirmation processing unit 132) Upon completion of the payment processing, the linkage confirmation processing unit 132 acquires a message service user ID and store ID (an example of "identification information") from the linkage information storage unit 121 using the payment service user ID (an example of a "first user ID") included in the payment request as a key, and sends a confirmation request including the acquired message service user ID and store ID to the message service providing device 30 (an example of an "other information processing device") that performs processing related to the message service (an example of a "second service"), thereby performing linkage confirmation processing to confirm whether the service user who is the source of payment in the payment processing is already linked to the message service as a member of the store to which the payment is made in the payment processing.

[0074] For example, the linkage confirmation processing unit 132 acquires a linkage flag (an example of "confirmation result information") indicating whether or not a service user who is the source of payment in the payment process (such as user U shown in FIG. 1) is already linked to the message service as a member of the store to which the payment is made in the payment process, from the message service providing device 30. If the linkage flag is "Yes", the linkage confirmation processing unit 132 derives a confirmation result that the service user who is the source of payment in the payment process is already linked to the message service as a member of the store to which the payment is made, that is, that the service user holds a membership card for the store to which the payment is made in the message service.

[0075] Furthermore, the linkage confirmation processing unit 132 may execute the linkage confirmation processing using an API (Application Programming Interface) provided by a service provider that operates the message service. For example, the linkage confirmation processing unit 132 may use the API to directly access a membership card management system in which information related to the membership card is managed in the message service providing device 30, and confirm whether or not identification information linked to the payment service user ID is managed, thereby directly confirming whether or not a service user (e.g., user U shown in FIG. 1) who is the source of payment in the payment processing is in a state of being linked to the message service as a member of the store to which the payment is made in the payment processing, that is, whether or not the membership card is held in a valid state in the message service.

[0076] (About the provider 133) When the providing unit 133 receives a response from the message service providing device 30 indicating that a service user (such as user U shown in Figure 1) who is the source of payment in the payment process is already linked to the message service as a member of the store to which the payment is made in the payment process, the providing unit 133 provides the payment ID and identification information to the message service by transmitting them to the message service providing device 30 via the communication unit 110.

[0077] For example, when the providing unit 133 obtains a confirmation result from the link confirmation processing unit 132 that the user is already linked to the message service as a member of the store to which the payment is made in the payment processing, the providing unit 133 transmits a payment ID for identifying the payment for which the payment processing was executed, and the message service user ID and store ID linked to the payment service user ID to the message service providing device 30 as payment information via the communication unit 110.

[0078] (Regarding the profit granting unit 134) When the link confirmation processing unit 132 confirms that the service user who is the source of payment in the payment process is already linked to the message service as a member of the store to which the payment is made in the payment process, the benefit granting unit 134 grants the service user who is the source of payment a benefit that can be used only at the store where the payment was made.

[0079] For example, when the payment processing unit 131 successfully completes the payment processing corresponding to a payment request, the profit awarding unit 134 awards limited points that can be used by the service user linked to the payment request to pay for the transaction item provided by the store only at the store where the payment was made.

[0080] The benefit granting unit 134 may grant a coupon that can be used only at the store where the payment is made to the service user who is the payer of the price in the payment process.

[0081] [3. Example of processing procedure] (3-1. Linkage information registration process) Hereinafter, the flow of the federation information registration processing executed by payment service providing device 100 according to an embodiment will be described with reference to Figure 6. Figure 6 is a flowchart showing an example of the processing steps of the federation information registration processing executed by payment service providing device 100 according to an embodiment. The processing steps shown in Figure 6 are executed by control unit 130 possessed by payment service providing device 100. Control unit 130 repeatedly executes the processing steps shown in Figure 6 while payment service providing device 100 is operating.

[0082] 6, the control unit 130 acquires the association information transmitted from the message service providing device 30 through the communication unit 110 (step S101). Specifically, the control unit 130 acquires the message service user ID and the store ID as the association information.

[0083] The control unit 130 identifies the payment service user ID corresponding to the federation information (step S102). For example, the control unit 130 may identify the payment service user ID corresponding to the federation information based on identity verification information acquired together with the federation information. Alternatively, the control unit 130 may identify the payment service user ID that is linked with the message service user ID included in the federation information by an ID federation process previously performed with the message service.

[0084] The control unit 130 associates the identified payment service user ID with the association information, registers it in the association information storage unit 121 (step S103), and ends the processing procedure shown in FIG.

[0085] (3-2. Payment-related processing) The flow of payment-related processing executed by payment service providing device 100 according to an embodiment will be described below with reference to Figure 7. Figure 7 is a flowchart showing an example of the processing procedure of payment-related processing executed by payment service providing device 100 according to an embodiment. The processing procedure shown in Figure 7 is executed by control unit 130 possessed by payment service providing device 100. Control unit 130 repeatedly executes the processing procedure shown in Figure 7 while payment service providing device 100 is operating.

[0086] As shown in FIG. 7, the payment processing unit 131 determines whether or not a payment request has been received through the communication unit 110 (step S201).

[0087] When it is determined that a payment request has been received (step S201: Yes), the payment processing unit 131 executes a payment process corresponding to the payment request based on the payment information included in the payment request (step S202).

[0088] In addition, the payment processing unit 131 transmits a payment ID for identifying the payment for which the payment processing was executed, to the in-store device 20, which is a terminal device used in the store where the payment was made, via the communication unit 110 (step S203).

[0089] The linkage confirmation processing unit 132 acquires a linkage flag from the message service providing device 30 for the service user who will be the payer of the payment process (step S204). Specifically, the linkage confirmation processing unit 132 acquires a message service user ID and a store ID from the linkage information storage unit 121 using the payment service user ID included in the payment request as a key, and transmits a confirmation request including the acquired message service user ID and store ID to the message service providing device 30 via the communication unit 110. Then, as a response to the confirmation request, the linkage confirmation processing unit 132 acquires from the message service providing device 30 a linkage flag indicating whether the service user who will be the payer of the payment process is already linked to the message service as a member of the store that will be the payee of the payment process.

[0090] The linkage confirmation processing unit 132 also determines whether the service user who is the payer of the payment process is already linked to the message service as a member of the store who is the payee of the payment process (step S205). Specifically, when the linkage flag is "Yes", the linkage confirmation processing unit 132 derives a determination result that the service user is already linked.

[0091] If the link confirmation processing unit 132 determines that the service user who is the source of payment in the payment processing is already linked to the message service as a member of the store to which the payment is to be made in the payment processing, it transmits the payment ID corresponding to the performed payment processing, the message service user ID linked to the payment service user ID included in the payment request, and the store ID to the message service providing device 30 via the communication unit 110 (step S206).

[0092] Furthermore, the cooperation confirmation processing unit 132 transmits a payment completion notification to the user device 10 of the service user who is the payer of the price in the payment processing through the communication unit 110 (step S207), and ends the processing procedure shown in FIG.

[0093] In the above-mentioned step S101, if the payment processing unit 131 determines that a payment request has not been received (step S201: No), the processing procedure shown in FIG. 7 ends.

[0094] 4. Modifications The information processing system according to the above-described embodiment (e.g., see FIG. 1, etc.) may be configured to include multiple servers in which the various processing functions possessed by the payment service providing device 100, including processing functions corresponding to payment processing related to electronic payment services, and processing functions for executing the information processing according to the embodiment (e.g., see FIG. 6 and FIG. 7, etc.), are functionally or physically distributed.

[0095] 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.

[0096] 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.

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

[0098] 5. Effects As described above, the payment service providing device 100 (an example of an "information processing device") according to the embodiment is an information processing device that performs processing related to a payment service (an example of a "first service") that provides a cashless payment performed using code information, and includes an association information storage unit 121 (an example of an "information for identification storage unit"), a payment processing unit 131, an association confirmation processing unit 132, and a benefit granting unit 134. The association information storage unit 121 stores association information (an example of "information for identification") for identifying a user who is associated with a message service (an example of a "second service") different from the payment service as a member of a store that is an affiliated store that can use the payment service, in association with a payment service user ID (an example of a "first user ID") unique to each user in order to individually identify each user who uses the payment service. In response to receiving a payment request related to the payment service, the payment processing unit 131 executes a payment process corresponding to the payment request, and transmits a payment ID for identifying the payment for which the payment process was executed to the store device 20 (an example of a "terminal device") used in the store where the payment was made. In response to the completion of the payment process, the linkage confirmation processing unit 132 acquires linkage information from the linkage information storage unit 121 using the payment service user ID included in the payment request as a key, and transmits a confirmation request including the acquired linkage information to the message service providing device 30 (an example of "another information processing device") that performs processing related to the message service, thereby confirming whether or not the user who will be the payer in the payment process has already been linked to the message service as a member of the store to which the payment will be made in the payment process. When the linkage confirmation processing unit 132 confirms that the user who will be the payer in the payment process has already been linked to the second service as a member of the store to which the payment will be made in the payment process, the benefit granting unit 134 grants the payer a benefit that can be used only at the store where the payment was made to the user who will be the payer.

[0099] The benefit granting unit 134 may grant the user, who is the payment source, points that can be used to pay for the price of the transaction object provided by the store only at the store where the payment is made.

[0100] The benefit granting unit 134 may also grant the user, who is the payer, a coupon that can be used only at the store where the payment is made.

[0101] In addition, the payment service providing device 100 according to the embodiment may have a point information storage unit (an example of a "benefit information storage unit") that stores information regarding the benefits held by each user of the payment service in correspondence with a payment service user ID.

[0102] In this way, the payment service providing device 100 according to the embodiment can provide a service user who uses a payment service with a benefit that can be used only at the store where the payment is made, for example, by having the service user link the account information of the official store app to the message service side (i.e., creating a membership card), thereby improving usability. On the other hand, the payment service providing device 100 according to the embodiment can provide a benefit that can be used only at the store where the payment is made in the payment process, thereby driving customers to the store and contributing to attracting customers to affiliated stores.

[0103] [6. Hardware Configuration] Furthermore, 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 8. Figure 8 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.

[0104] 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.

[0105] 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.

[0106] 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.

[0107] 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.

[0108] 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.

[0109] 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.

[0110] 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.

[0111] [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.

[0112] 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.

[0113] In addition, 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]

[0114] 10 User Device 20 Store equipment 30 Message service providing device 100 Payment service providing device 110 Communications Department 120 Storage section 121 Linkage information storage unit 122 Point information storage unit 130 Control section 131 Payment processing unit 132 Cooperation confirmation processing unit 133 Provision Department 134 Profit Granting Department

Claims

1. An information processing device that performs processing related to a first service that provides a cashless payment performed using code information, an identification information storage unit that stores identification information for identifying the user who uses the first service as a member of a store that is an affiliated store that can use the first service in a second service different from the first service, in association with a first user ID unique to each user in order to individually identify each user who uses the first service; a payment processing unit that, in response to receiving a payment request for the first service, executes a payment process corresponding to the payment request and transmits a payment ID for identifying the payment for which the payment process was executed to a terminal device used in the store where the payment was made; a linkage confirmation processing unit that, upon completion of the payment process, acquires the identification information from the identification information storage unit using the first user ID included in the payment request as a key, and transmits a confirmation request including the acquired identification information to another information processing device performing processing related to the second service, thereby confirming whether the user who is the source of payment in the payment process has already been linked to the second service as a member of the store who is the destination of payment in the payment process; a benefit granting unit that grants a benefit that can be used only at the store where the payment is made to the user who is the payer of the payment process, when the linkage confirmation processing unit confirms that the user who is the payer of the payment process is a member of the store that is the payee of the payment process and has already linked to the second service; 13. An information processing device comprising:

2. The profit providing unit is The user who is the payment source is given points that can be used to pay for the transaction provided by the store only at the store where the payment is made.

2. The information processing apparatus according to claim 1,

3. The profit providing unit is A coupon that can be used only at the store where the payment is made is given to the user who is the payment source.

2. The information processing apparatus according to claim 1,

4. An information processing method performed by a computer that executes a process related to a first service that provides a cashless payment performed using code information, a payment processing step of, in response to receiving a payment request for the first service, executing a payment process corresponding to the payment request and transmitting a payment ID for identifying the payment for which the payment process was executed to a terminal device used in a store that is an affiliated store where the first service is available and where the payment was made; a linkage confirmation processing step of acquiring, from a storage unit that stores identification information for identifying the user who is linked to the second service as a member of the store that is the affiliated store in a second service different from the first service, by using the first user ID included in the payment request as a key in response to completion of the payment processing, the identification information in association with a first user ID unique to each user in order to individually identify each user who uses the first service, and transmitting a confirmation request including the acquired identification information to another information processing device that performs processing related to the second service, thereby confirming whether the user who is the source of payment in the payment processing is already linked to the second service as a member of the store that is the destination of payment in the payment processing; a benefit granting step of granting the user who is the payer of the payment a benefit that can be used only at the store where the payment is made, when it is confirmed in the link confirmation processing step that the user who is the payer of the payment processing is in a state of being linked to the second service as a member of the store which is the payee of the payment processing; 13. An information processing method comprising:

5. A computer that executes a process related to a first service that provides a cashless payment performed using code information, a payment processing procedure for, in response to receiving a payment request for the first service, executing a payment process corresponding to the payment request and transmitting a payment ID for identifying the payment corresponding to the payment request to a terminal device used in a store that is an affiliated store where the first service is available and where the payment is made; a linkage confirmation processing step of acquiring, from a storage unit that stores identification information for identifying the user who is linked to the second service as a member of the store that is the affiliated store in a second service different from the first service, by correlating the identification information with a first user ID unique to each user in order to individually identify each user who uses the first service, the identification information, using the first user ID included in the payment request as a key, in response to completion of the payment processing, and transmitting a confirmation request including the acquired identification information to another information processing device that performs processing related to the second service, thereby confirming whether the user who is the source of payment in the payment processing is already linked to the second service as a member of the store that is the destination of payment in the payment processing; a benefit granting step of granting the user who is the payer a benefit that can be used only at the store where the payment is made to the user who is the payer when it is confirmed in the link confirmation processing step that the user who is the payer of the payment process is a member of the store that is the payee of the payment process and has already been linked to the second service; An information processing program characterized by causing the program to execute the above steps.

Images