User management program, user management system, and user management method

Abstract

To provide a user management program, a user management system, and a user management method that can handle settlement processing in various situations.SOLUTION: A user management program causes a computer to function as: settlement means registration unit that receives, from a business operator system of a business operator that conducts transaction with a user, registration of settlement means information related to settlement means used by the user in settlement of first transaction between the user and the business operator; a settlement token registration unit that receives, from the settlement system that performs processing related to settlement of transaction, registration of settlement token information related to a settlement token corresponding to settlement means information; an identification information registration unit that registers user identification information that identifies the user; and a user management unit that generates user management information that associates the settlement means information, the settlement token information, and the user identification information.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a user management program, a user management system, and a user management method. [Background technology]

[0002] 2. Description of the Related Art Conventionally, there has been known a system that performs settlement processing for a transaction between a user and a business based on information registered in advance.

[0003] For example, Patent Document 1 describes a point system consisting of one or more point management systems. Each point management system has a point management server that stores a linking table that stores company IDs that identify companies that provide payment methods linked to its own point management system, and a payment terminal that makes payments using the payment method. When a payment is made using a payment method at the payment terminal, the point management server assigns points according to the payment amount to a customer ID that identifies the customer using the payment method, based on the linking table, if the payment method is linked to its own point management system. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-56107 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the point system described in Patent Document 1 is premised on the premise that the user's payment method is linked to the point management system in advance, and therefore does not take into consideration payments using payment methods that are not linked to the point management system.

[0006] Therefore, an object of the present invention is to provide a user management program, a user management system, and a user management method that can handle payment processing in various situations. [Means for solving the problem]

[0007] A user management program according to one embodiment of the present invention causes a computer to implement the following: a payment method registration unit that accepts registration of payment method information regarding the payment method used by a user in settling a first transaction between the user and a business from the business system of the business that conducts transactions with the user; a payment token registration unit that accepts registration of payment token information regarding a payment token corresponding to the payment method information from the payment system that processes the settlement of the transaction; an identification information registration unit that registers user identification information that identifies the user; and a user management unit that generates user management information that associates payment method information, payment token information, and user identification information.

[0008] A user management system according to one embodiment of the present invention comprises a payment method registration unit that accepts registration of payment method information relating to the payment method used by a user in settling a first transaction between the user and a business from the business system of the business that conducts transactions with the user; a payment token registration unit that accepts registration of payment token information relating to a payment token corresponding to the payment method information from the payment system that processes the settlement of the transaction; an identification information registration unit that registers user identification information that identifies the user; and a user management unit that generates user management information that associates the payment method information, payment token information, and user identification information.

[0009] A user management method according to one embodiment of the present invention involves a computer accepting registration of payment method information relating to the payment method used by the user in settling a first transaction between the user and the business from an operator system of a business that conducts transactions with the user, accepting registration of payment token information relating to a payment token corresponding to the payment method information from a payment system that processes the settlement of the transaction, registering user identification information that identifies the user, and generating user management information that associates the payment method information, payment token information, and user identification information.

[0010] In this invention, a "unit" does not simply mean a physical means, but also includes cases where the functions of the "unit" are realized by software. Furthermore, the functions of one "unit" or device may be realized by two or more physical means, devices, or software modules, and the functions of two or more "units" or devices may be realized by one physical means, device, or software module. [Effects of the Invention]

[0011] According to the present invention, it is possible to provide a user management program, a user management system, and a user management method that can handle payment processing in various situations. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram showing an overview of processing in a user management system 100 according to an embodiment of the present invention. [Figure 2] 1 is a diagram showing a configuration of a user management system 100 according to an embodiment of the present invention. [Figure 3] FIG. 2 is a diagram showing an example of payment method registration information stored in storage unit 105. [Figure 4] FIG. 2 is a diagram showing an example of payment token registration information stored in the storage unit 105. [Figure 5] 10 is a diagram showing an example of user identification registration information stored in a storage unit 105. FIG. [Figure 6] 10 is a diagram showing an example of user management information stored in a storage unit 105. FIG. [Figure 7] FIG. 10 is a diagram showing an example of payment processing information stored in storage unit 105. [Figure 8] 10 is a flowchart showing an example of processing in the user management system 100. [Figure 9] 10 is a flowchart showing an example of processing in the user management system 100. [Figure 10]10 is a flowchart showing an example of processing in the user management system 100. DETAILED DESCRIPTION OF THE INVENTION

[0013] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the present invention will now be described with reference to the accompanying drawings, in which: Figure 1 is a diagram showing an overview of processing in a user management system 100 according to an embodiment of the present invention;

[0014] The user management system 100 is an information processing system realized by a user management program, which accepts registration of payment method information, payment token information, and user identification information in accordance with a first transaction between a user and a business (first business), and generates user management information that associates the payment method information, payment token information, and user identification information.

[0015] Then, the user management system 100 outputs payment processing information for processing the payment of the second transaction between the user and the business based on the payment request information, which includes at least one of payment method information, payment token information, and user identification information, and the user management information.

[0016] First, the business acquires payment method information from the user regarding the payment method that the user will use in settling a transaction (first transaction) with the user (S111). The user management system 100 accepts registration of the payment method information from the business (S112).

[0017] The user management system 100 provides, for example, payment method information to the payment system, requests the issuance of a payment token corresponding to the payment method information, and accepts registration of payment token information related to the payment token from the payment system (S113). The user management system 100 also accepts registration of user identification information that identifies a user, for example, from a business operator (S114). The user management system 100 then generates user management information that associates the payment method information, payment token information, and user identification information (S115).

[0018] In a second transaction between a user and a business, the business acquires payment request information from the user, including payment method information, payment token information, and user identification information (S121a, S121b), and the user management system 100 acquires the payment request information from the business (S122a, S122b). At this time, the user may conduct the second transaction with the same business (first business) as the first transaction (S121a, S122a), or may conduct the second transaction with a different business (second business) from the first transaction (S121b, S122b). The user management system 100 outputs payment processing information for processing the payment of the second transaction to the payment system based on the payment request information and user management information (S123). Then, processing for the payment of the second transaction is performed in the payment system.

[0019] 2 is a diagram showing the configuration of a user management system 100 according to one embodiment of the present invention. The user management system 100 is communicably connected to a business operator system 200 and a payment system 300 via a network such as the Internet. Details of the user management system 100 will be described later.

[0020] The business operator system 200 is, for example, an information processing system of a business operator that conducts transactions with users.

[0021] The business operator may be, for example, an affiliated store of the payment method used by the user for payment (e.g., a credit card affiliated store). The business operator system 200 may be an information processing system (e.g., a cash register terminal) of the store where the user purchases goods, etc., or may be an information processing system (e.g., a server managed by the business operator) that can be connected to the store's information processing system via a network such as the Internet.

[0022] The payment system 300 is, for example, an information processing system of a payment business operator that performs payment processing related to the settlement of transactions between users and businesses.

[0023] The payment system 300 may be an information processing system of a payment service provider that corresponds to the payment method used by the user for payment. That is, if the payment method used by the user for payment is a credit card, the payment system 300 may be an information processing system of a service provider that issues or manages the credit card, or if the payment method used by the user for payment is electronic money, the payment system 300 may be an information processing system of a funds transfer service provider that manages the electronic money.

[0024] The payment system 300 may be an information processing system incorporated into the user management system 100.

[0025] Also, in FIG. 2, one business operator system 200 and one payment system 300 are shown, but there may be a plurality of business operator systems 200 and a plurality of payment systems 300.

[0026] Next, details of the user management system 100 will be described. The user management system 100 includes a memory unit 105, a payment method registration unit 110, a token issuance request unit 115, a payment token registration unit 120, an identification information registration unit 125, a user management unit 130, a payment request information acquisition unit 135, a registration information extraction unit 140, a payment processing information generation unit 145, a payment processing information output unit 150, an identification information output unit 155, a preferential treatment management information acquisition unit 160, and a preferential treatment management information output unit 165. Each unit shown in Fig. 2 can be realized, for example, by using a memory area or by a processor executing a program stored in the memory area.

[0027] The storage unit 105 stores information processed in the user management system 100. The storage unit 105 can store, for example, payment method registration information, payment token registration information, user identification registration information, user management information, and payment processing information, which will be described later.

[0028] The payment method registration unit 110 accepts registration of payment method information relating to the payment method used by the user in the payment of the first transaction between the user and the business from the business system 200, and stores the payment method registration information in the storage unit 105.

[0029] Here, the payment method may be, for example, a credit card, electronic money, direct debit, token (for example, a token conforming to the EMV (Europay International, MasterCard, Visa) standard provided by a payment brand), etc. Furthermore, the payment method information may be, for example, a credit card number, ID information for electronic money, an account number for a debit account, token information for a token, etc.

[0030] First, when making a first transaction, the user provides payment method information to the business operator. At this time, for example, the user may provide a credit card to the business operator, and the business operator system 200 may obtain payment method information (e.g., credit card number) corresponding to the credit card, or the user may provide display information (e.g., one-dimensional or two-dimensional barcode) displayed on the user terminal to the business operator, and the business operator system 200 may read the display information using, for example, a predetermined device, and obtain payment method information (e.g., electronic money ID information) corresponding to the display information.

[0031] The business operator system 200 then provides the acquired payment method information to the user management system 100, and the payment method registration unit 110 accepts the registration of the payment method information.

[0032] At this time, the payment method registration unit 110 can accept registration of the payment method information obtained from the user by the business operator system 200 for the payment of the first transaction. That is, the business operator system 200 provides the payment method information obtained from the user to the user management system 100 for the purpose of processing the payment of the first transaction and registering the payment method information. This allows the user to register the payment method information in conjunction with the payment processing of the first transaction, without having to separately provide the payment method information to the business operator system 200 or the user management system 100 to register the payment method information, thereby reducing the user's workload.

[0033] When the business operator system 200 acquires payment method information from the user, it may also acquire consent for the registration of the payment method information in the user management system 100. This allows the payment method information to be registered with the user's consent.

[0034] 3 is a diagram showing an example of payment method registration information stored in memory unit 105. The payment method registration information stored in memory unit 105 includes, for example, a payment method registration ID and payment method information. The payment method registration ID is information that identifies the payment method registration information stored in memory unit 105.

[0035] The token issuance request unit 115 requests the payment system 300 to issue a payment token corresponding to the payment method information based on the payment method registration information.

[0036] A payment token is information that a user uses for payment. By using a payment token, a user can make a payment without disclosing payment method information (e.g., credit card number) to a transaction partner (e.g., a business such as an affiliated store), thereby enabling more secure payments.

[0037] The token issuance request unit 115 may request the issuance of a payment token based on authentication result information that authenticates that the payment method information accepted for registration is payment method information provided by a legitimate user to the business operator system 200. This allows the user management system 100 to request the issuance of a payment token corresponding to the payment method information provided by a legitimate user, thereby preventing fraudulent use of payment tokens.

[0038] Here, the authentication method is not particularly limited, but may be, for example, an authentication method based on information such as name, address, or identification, an authentication method using a specified public personal authentication service, or an authentication method using a specified eKYC (electronic Know Your Customer: electronic identity verification).

[0039] Furthermore, the authentication result information may be generated in the user management system 100 or in the business operator system 200. When the authentication result information is generated in the user management system 100, the user management system 100 may acquire information necessary for authentication, for example, from the business operator system 200, and perform authentication based on the acquired information. When the authentication result information is generated in the business operator system 200, the business operator system 200 may acquire information necessary for authentication from the user, and perform authentication based on the acquired information. Then, the user management system 100 acquires the authentication result information from the business operator system 200.

[0040] In response to a token issuance request from the token issuance request unit 115, the payment system 300 issues a payment token corresponding to the payment method information, and provides payment token information regarding the payment token to the user management system 100.

[0041] If the payment method is a token conforming to the EMV standard or the like, the payment token issued by the payment system 300 is different from the token of the payment method (a token conforming to the EMV standard or the like).

[0042] In addition, the payment system 300 may issue a payment token corresponding to the payment method information in response to a token issuance request if it is further authenticated based on the authentication result information that the payment method information has been provided to the operator system 200 by a legitimate user.

[0043] Furthermore, when the payment system 300 is an information processing system incorporated into the user management system 100, the payment token issuance request process and the payment token issuance process may be performed in the user management system 100 (particularly, the token issuance request unit 115 and the payment system 300 incorporated into the user management system 100). That is, in this case, the payment token may be a payment token managed by the user management system 100.

[0044] The payment token registration unit 120 accepts registration of payment token information from the payment system 300 and stores the payment token registration information in the memory unit 105.

[0045] 4 is a diagram showing an example of payment token registration information stored in the storage unit 105. The payment token registration information stored in the storage unit 105 includes, for example, a payment token registration ID and payment token information. The payment token registration ID is information that identifies the payment token registration information stored in the storage unit 105.

[0046] The identification information registration unit 125 registers user identification information for identifying a user, and stores the user identification registration information in the storage unit 105 .

[0047] Here, the user identification information may be any information that can identify the user, and may be, for example, biometric information about the user's living body, possession information about possessions held by the user, a telephone number, an account name such as an email address, a password, a sign or figure entered or selected by the user, etc. The biometric information may be, for example, information about the user's appearance, fingerprint, palm print, voiceprint, iris, etc. The possession information may be, for example, terminal identification information that identifies a user terminal (for example, an information terminal such as a smartphone) that is a possession held by the user.

[0048] Furthermore, the identification information registration unit 125 can register user identification information for identifying the user in the business operator system 200, which is acquired from the business operator system 200 when settling the first transaction.

[0049] In this case, the user identification information for identifying the user in the business operator system 200 may be, for example, a point card number or a membership card number managed in the business operator system 200. That is, when paying for the first transaction, the user provides payment method information (e.g., a credit card number) and user identification information (e.g., a point card number or a membership card number) to the business operator system 200. The business operator system 200 registers the acquired payment method information and user identification information in the user management system 100.

[0050] Furthermore, the identification information registration unit 125 may register user identification information generated in the user management system 100. In this case, the user identification information may be, for example, information that can identify a user in the user management system 100 (for example, a user ID).

[0051] 5 is a diagram showing an example of user identification registration information stored in storage unit 105. The user identification registration information stored in storage unit 105 includes, for example, a user identification registration ID and user identification information. The user identification registration ID is information that identifies the user identification information stored in storage unit 105.

[0052] In the following description, the payment method information registered by the payment method registration unit 110, the payment token information registered by the payment token registration unit 120, and the user identification information registered by the identification information registration unit 125 are collectively referred to as registered information. In other words, unless otherwise specified, the registered information includes at least one of the registered payment method information, payment token information, and user identification information.

[0053] The user management unit 130 generates user management information that associates the payment method information, payment token information, and user identification information, and stores the information in the storage unit 105.

[0054] The user management information is information in which payment method information, payment token information, and user identification information are mutually associated. That is, for example, based on the user management information and payment method information, it is possible to extract payment token information and user identification information corresponding to the payment method information. Furthermore, based on the user management information and payment token information, it is possible to extract payment method information and user identification information corresponding to the payment token information, and based on the user management information and user identification information, it is possible to extract payment method information and payment token information corresponding to the user identification information.

[0055] In this way, by referencing the user management information, it is possible to extract other registered information based on any of the registered information. This allows the user to settle a transaction (e.g., a second transaction that occurs after a first transaction) by providing any of the registered information to the business operator system 200, thereby improving user convenience. In other words, the user can make a payment using a payment method (e.g., a credit card) and a membership card while enjoying benefits based on the membership card by presenting only one of the payment method and the membership card to the business operator, without presenting both.

[0056] In this regard, it is conceivable that the generation process of the user management information is performed in the business operator system 200. However, for example, if the business operator is a small or medium-sized business, it may be difficult for the business operator to manage and operate an information processing system that performs the generation process of the user management information. Therefore, the user management system 100, in a sense, performs user management, including the generation process of the user management information, on behalf of the business operator, thereby providing a payment system that is highly convenient for users.

[0057] Furthermore, the user management system 100 can provide highly convenient payments to users by generating user management information even in face-to-face transactions between users and businesses.

[0058] The user management unit 130 can generate user management information that further associates preferential treatment management information for managing preferential treatment for the user in accordance with the transaction, and store the generated user management information in the storage unit 105. The preferential treatment management information will be described later.

[0059] 6 is a diagram showing an example of user management information stored in storage unit 105. The user management information stored in storage unit 105 includes, for example, a management information ID, a payment method registration ID, a payment token registration ID, and a user identification registration ID. The management information ID is information that identifies the user management information stored in storage unit 105.

[0060] The user management information stored in the storage unit 105 may include payment method information, payment token information, and user identification information instead of the payment method registration ID, payment token registration ID, and user identification registration ID. The user management information stored in the storage unit 105 may further include preferential treatment management information.

[0061] The payment request information acquisition unit 135 acquires payment request information including at least one of payment method information, payment token information, and user identification information from the business system 200 in response to a second transaction between the user and the business.

[0062] Here, the second transaction is a transaction that is made after the user management information is generated in response to the first transaction. That is, the second transaction is a transaction that is made after the first transaction. Note that the second transaction may be made with the same business operator (first business operator) as the first transaction, or may be made with a business operator (second business operator) different from the first transaction.

[0063] When making a second transaction, the user provides the business with payment request information including at least one of payment method information, payment token information, and user identification information. The payment request information is information for requesting payment for the second transaction.

[0064] As the payment request information, the user may provide, for example, only payment method information (e.g., credit card number), only payment token information, or only user identification information (e.g., point card number managed by the business operator).The business operator system 200 then provides the payment request information acquired from the user to the user management system 100, and the payment request information acquisition unit 135 acquires the payment request information.

[0065] The payment request information may include transaction information regarding the second transaction (for example, the transaction amount, information regarding the product to be traded) in addition to at least one of the payment method information, payment token information, and user identification information.

[0066] The registration information extraction unit 140 extracts registration information corresponding to the payment request information based on the user management information and the payment request information acquired by the payment request information acquisition unit 135.

[0067] Specifically, when payment token information is not included in the payment request information, the registration information extraction unit 140 can extract payment token information corresponding to the payment request information (i.e., payment token information corresponding to at least one of the payment method information and user identification information included in the payment request information) based on the payment request information and user management information. Note that when payment token information is not included in the payment request information, for example, the payment request information includes only at least one of the payment method information and user identification information.

[0068] Furthermore, when the payment request information does not include user identification information, the registration information extraction unit 140 can extract user identification information corresponding to the payment request information (i.e., user identification information corresponding to at least one of the payment method information and payment token information included in the payment request information) based on the payment request information and user management information. Note that when the payment request information does not include user identification information, for example, the payment request information includes only at least one of the payment method information and payment token information.

[0069] Furthermore, when the payment request information does not include payment method information, the registration information extraction unit 140 can extract payment method information corresponding to the payment request information (i.e., user identification information corresponding to at least one of the payment token information and user identification information included in the payment request information) based on the payment request information and user management information. The case where the payment request information does not include payment method information is, for example, when the payment request information includes only at least one of the payment token information and user identification information.

[0070] The payment processing information generation unit 145 generates payment processing information for processing the payment of the second transaction in the payment system 300 based on the user management information and the payment request information, and stores the generated information in the storage unit 105.

[0071] Here, the payment processing information is, for example, information for processing the payment of the second transaction in the payment system 300, and includes, for example, payment token information.

[0072] The payment processing information may also include transaction information regarding the transaction (for example, amount information regarding the amount of the transaction, and product information regarding the product that is the subject of the transaction).

[0073] The payment system 300 performs processing related to the payment of the second transaction based on the payment processing information acquired from the user management system 100. When the processing related to the payment of the second transaction is completed, the payment system 300 may provide information indicating that the payment processing has been completed to the user management system 100. Then, the user management system 100 may provide information indicating that the payment processing has been completed to the business operator system 200.

[0074] Furthermore, the payment processing information generation unit 145 determines whether or not payment processing information should be generated based on the user management information, and if payment processing information should not be generated, it may not generate the payment processing information. Specifically, for example, depending on the usage status of the payment token information, if the use of the payment token information in the second transaction is inappropriate (for example, if the payment is abnormal or if the payment limit is exceeded), the payment processing information generation unit 145 may determine that payment processing information should not be generated and not generate the payment processing information.

[0075] If the use of the payment token information in the second transaction is inappropriate (for example, if the payment is abnormal), the user management system 100 may notify the business operator system 200 of this fact. Then, the business operator system 200 (or a person in charge at the business operator (for example, a store)) may obtain consent information from the user regarding the execution of the payment for the second transaction and provide the consent information to the user management system 100. Then, the payment processing information generation unit 145 may generate payment processing information further based on the consent information. This allows the user management system 100 to generate payment processing information more appropriately by confirming with the user and obtaining consent from the user.

[0076] 7 is a diagram showing an example of payment processing information stored in storage unit 105. The payment processing information stored in storage unit 105 includes, for example, a payment processing ID, payment token information, and transaction information. The payment processing ID is information that identifies the payment processing information stored in storage unit 105.

[0077] The payment processing information output unit 150 outputs the payment processing information generated by the payment processing information generation unit 145 to the payment system 300. That is, the payment processing information output unit 150 outputs the payment processing information to the payment system 300 based on the user management information and the payment request information.

[0078] If the payment request information does not include payment token information, the payment processing information output unit 150 can output payment processing information further based on the payment token information extracted by the registration information extraction unit 140. Specifically, first, the registration information extraction unit 140 extracts payment token information based on the payment request information and the user management information. Then, the payment processing information generation unit 145 generates payment processing information further based on the extracted payment token information, and the payment processing information output unit 150 outputs the generated payment processing information.

[0079] Furthermore, the payment processing information output unit 150 can output payment processing information further based on preferential treatment management information acquired by the later-described preferential treatment management information acquisition unit 160. Specifically, the payment processing information generation unit 145 generates payment processing information further based on the preferential treatment management information acquired by the preferential treatment management information acquisition unit 160, and the payment processing information output unit 150 outputs the generated payment processing information.

[0080] Furthermore, when the user management information is information associating payment method information, payment token information, user identification information, and preferential treatment management information, the payment processing information output unit 150 outputs payment processing information further based on the preferential treatment management information corresponding to the payment request information. Specifically, the registration information extraction unit 140 extracts the preferential treatment management information corresponding to the payment request information based on the payment request information and the user management information. Then, the payment processing information generation unit 145 generates payment processing information further based on the preferential treatment management information, and the payment processing information output unit 150 outputs the payment processing information.

[0081] The identification information output unit 155 outputs the user identification information extracted by the registration information extraction unit 140 to the business operator system 200 .

[0082] When making a second transaction with a business, the user may make a payment request without presenting user identification information (e.g., a point card number managed by the business). This may occur, for example, when the user attempts to make a payment without bringing the point card.

[0083] In this case, the registration information extraction unit 140 extracts user identification information based on the payment request information and user management information that do not include user identification information, and the identification information output unit 155 outputs the extracted user identification information to the business operator system 200.

[0084] This allows businesses to obtain the user identification information of a user who does not provide user identification information based on the user identification information provided by the user management system 100, and perform payment processing, for example, by awarding points depending on the transaction or utilizing preferential management information corresponding to the user identification information.

[0085] The preferential treatment management information acquisition unit 160 acquires, from the business operator system 200, preferential treatment management information for managing preferential treatment according to a transaction, which corresponds to the output user identification information.

[0086] Here, the preferential treatment management information may be information indicating the content of the preferential treatment (for example, the presence or type of preferential treatment) such as points, electronic money, coupons, prizes, cashback, or the right to enter a lottery to obtain special benefits, or the preferential treatment management information may be information indicating the user's membership rank or membership grade. The content of the preferential treatment may vary depending on the membership rank or membership grade, etc. Furthermore, the membership rank or membership grade, etc. may be determined depending on transaction performance such as the number of points held or transaction amount, for example.

[0087] The preferential treatment management information may be, for example, information that is generated and managed in the business operator system 200 or the payment system 300 in response to a transaction, and provided to the user management system 100 by the business operator system 200 or the payment system 300. The preferential treatment management information may also be, for example, information that is generated in the user management system 100 in response to a transaction.

[0088] When the preferential treatment management information is information generated and managed in the business operator system 200 in response to a transaction, first, the identification information output unit 155 outputs user identification information to the business operator system 200. Next, the business operator system 200 provides preferential treatment management information corresponding to the user identification information to the user management system 100 based on the user identification information, and the preferential treatment management information acquisition unit 160 acquires the preferential treatment management information. Then, the payment processing information generation unit 145 generates payment processing information further based on the preferential treatment management information acquired by the preferential treatment management information acquisition unit 160, and the payment processing information output unit 150 outputs the generated payment processing information.

[0089] In this case, if the preferential treatment management information is information indicating the content of the preferential treatment, the payment processing information generation unit 145 may, for example, generate payment processing information that reflects the content of the preferential treatment. Also, if the preferential treatment management information is information indicating a member rank or a member grade, the payment processing information generation unit 145 may, for example, generate payment processing information that reflects the preferential treatment corresponding to the member rank or member grade, based on information that associates the member rank or member grade with the content of the preferential treatment and that is stored in advance.

[0090] When the preferential treatment management information is information generated in the user management system 100 in response to a transaction, the user management unit 130 generates user management information to which the preferential treatment management information is further associated. Then, the payment processing information generation unit 145 generates payment processing information further based on the preferential treatment management information corresponding to the user management information, and the payment processing information output unit 150 outputs the generated payment processing information.

[0091] The preferential treatment management information output unit 165 outputs preferential treatment management information to the business operator system 200. In particular, when the preferential treatment management information is information generated in the user management system 100 in response to a transaction, the preferential treatment management information output unit 165 outputs, to the business operator system 200, the preferential treatment management information generated or managed in the user management system 100 in response to the transaction.

[0092] This allows the business operator system 200 to provide, for example, a predetermined service to the user based on the preferential treatment management information acquired from the preferential treatment management information output unit 165. Specifically, for example, if the preferential treatment management information is information indicating the user's membership rank or membership grade, the business operator using the business operator system 200 can provide a service according to the membership rank or membership grade (for example, an increase in the point award rate, a discount, the provision of a free gift, or preferential treatment over other users, etc.).

[0093] The output processing of the preferential management information by the preferential management information output unit 165 may be performed at the same timing as the output processing of the identification information by the identification information output unit 155, or may be performed at a different timing.

[0094] Fig. 8 is a flowchart showing an example of processing in the user management system 100. The flowchart shown in Fig. 8 is a flowchart showing an example of processing for generating user management information.

[0095] First, the user requests payment for a first transaction between the user and the business by providing, for example, payment method information to the business system 200 (not shown). The payment method registration unit 110 accepts registration of payment method information from the business system 200 (S801).

[0096] The token issuance request unit 115 requests the payment system 300 to issue a payment token corresponding to the payment method information (S802). The payment system 300 issues a payment token in response to the token issuance request, and the payment token registration unit 120 accepts registration of the payment token information (S803).

[0097] The identification information registration unit 125 accepts registration of user identification information from, for example, the business operator system 200 (S804).

[0098] Then, the user management unit 130 generates user management information that associates the payment method information, payment token information, and user identification information (S805).

[0099] In addition, the registration process of user identification information by the identification information registration unit 125 may be performed before or at the same time as the registration process of payment method information by the payment method registration unit 110, and may also be performed before the token issuance request process by the token issuance request unit 115 or before the registration process of payment token by the payment token registration unit 120.

[0100] Fig. 9 is a flowchart showing an example of processing in the user management system 100. The flowchart shown in Fig. 9 is a flowchart showing an example of processing when payment token information is not included in the payment request information (for example, when only user identification information is acquired as the payment request information).

[0101] First, the user provides user identification information to the business operator system 200 to request payment for a second transaction between the user and the business operator (not shown). The payment request information acquisition unit 135 acquires the payment request information (user identification information in this case) from the business operator system 200 (S901). The registration information extraction unit 140 extracts payment token information corresponding to the payment request information (user identification information in this case) based on the user management information and the payment request information (user identification information in this case) (S902).

[0102] The payment processing information generation unit 145 generates payment processing information based on the payment request information and the extracted payment token information (S903). The payment processing information output unit 150 outputs the payment processing information to the payment system 300 (S904).

[0103] In this way, even if a user provides only user identification information (e.g., a point card or membership card) (i.e., without providing payment token information), the user can make a payment using the payment token information. Furthermore, when a user conducts a second transaction with a second business operator different from the business operator of the first transaction (first business operator), the user management system 100 can perform the payment process for the second transaction with the second business operator without performing the user management information generation process again in the transaction with the second business operator, and the user can easily conduct the second transaction with the second business operator different from the first business operator.

[0104] Fig. 10 is a flowchart showing an example of processing in the user management system 100. The flowchart shown in Fig. 10 is a flowchart showing an example of processing when user identification information is not included in the payment request information (for example, when only payment token information is acquired as the payment request information).

[0105] First, the user provides payment token information to the business operator system 200 to request payment for a second transaction between the user and the business operator (not shown). The payment request information acquisition unit 135 acquires the payment request information (in this case, payment token information) from the business operator system 200 (S1001). The registration information extraction unit 140 extracts user identification information corresponding to the payment request information (in this case, payment token information) based on the user management information and the payment request information (in this case, payment token information) (S1002).

[0106] The identification information output unit 155 outputs the user identification information to the business operator system 200 (S1003). The preferential treatment management information acquisition unit 160 acquires preferential treatment management information from the business operator system 200 (S1004).

[0107] The payment processing information generation unit 145 generates payment processing information based on the payment request information and the preferential treatment management information (S1005). The payment processing information output unit 150 outputs the payment processing information to the payment system 300 (S1006).

[0108] The user may provide payment method information, instead of payment token information, to the business operator system 200. In this case, the payment token information in the flowchart shown in Fig. 10 may be appropriately replaced with payment method information.

[0109] In this way, even if the user provides only payment token information or payment method information (i.e., does not provide user identification information), payment processing can be performed based on the preferential management information corresponding to the user identification information. Furthermore, when the user conducts a second transaction with a second business operator different from the business operator of the first transaction (first business operator), the user management system 100 can perform payment processing for the second transaction with the second business operator without performing user management information generation processing again in the transaction with the second business operator, and the user can easily conduct the second transaction with the second business operator different from the first business operator based on the preferential management information.

[0110] The above describes one embodiment of the present invention. The user management system 100 accepts registration of payment method information, payment token information, and user identification information in response to a first transaction between a user and a business, and generates user management information that associates the payment method information, payment token information, and user identification information. This allows the user management system 100 to handle payment processing in a variety of situations.

[0111] Furthermore, the user management system 100 can acquire payment request information from the business system 200 in response to a second transaction between the user and the business, and output payment processing information for processing the payment of the second transaction to the payment system 300 based on the user management information and the payment request information. This allows the user management system 100 to work in cooperation with the business system 200 and the payment system 300 to perform the payment processing of the second transaction.

[0112] Furthermore, when the payment request information does not include payment token information, the user management system 100 can extract payment token information corresponding to the payment request information based on the user management information, and output payment processing information for processing the payment of the second transaction using the payment token indicated by the payment token information, further based on the extracted payment token information. This allows the user to make a payment using the payment token indicated by the payment token information, even if the user does not provide the payment token information to the business operator system 200 when making a payment for the second transaction.

[0113] Furthermore, when the payment request information does not include user identification information, the user management system 100 can extract user identification information corresponding to the payment request information based on the user management information and output the extracted user identification information to the business operator system 200. This allows the business operator to obtain user identification information from the user management system 100 even when the business operator does not obtain user identification information from the user at the time of payment of the second transaction. This also allows the user to receive benefits (e.g., points) based on the user identification information, even when the user does not provide the user identification information to the business operator system 200.

[0114] Furthermore, the user management system 100 can generate user management information that further associates the preferential treatment management information, and output payment processing information based on the preferential treatment management information that corresponds to the payment request information. This allows the user to receive payment processing based on the preferential treatment management information when settling the second transaction.

[0115] Furthermore, the user management system 100 can acquire preferential treatment management information from the business operator system 200 and output payment processing information based on the acquired preferential treatment management information. This allows the user to receive payment processing based on the preferential treatment management information when settling the second transaction, even if the business operator system 200 manages the preferential treatment management information.

[0116] Furthermore, the user management system 100 can accept registration of user identification information, acquired from the business operator system 200, for identifying a user in the business operator system 200. This allows the user management system 100 to generate user management information that associates the user identification information for identifying a user in the business operator system 200 with payment method information and payment token information.

[0117] It should be noted that the present embodiment is provided to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit thereof, and equivalents thereof are also included in the present invention. [Explanation of symbols]

[0118] 100 User management system, 105 Memory unit, 110 Payment method registration unit, 115 Token issuance request unit, 120 Payment token registration unit, 125 Identification information registration unit, 130 User management unit, 135 Payment request information acquisition unit, 140 Registration information extraction unit, 145 Payment processing information generation unit, 150 Payment processing information output unit, 155 Identification information output unit, 160 Preferential treatment management information acquisition unit, 165 Preferential treatment management information output unit, 200 Business operator system, 300 Payment system

Claims

1. On the computer, a payment method registration unit that receives, from a business system of a first transaction between a user and a business that conducts a face-to-face transaction with the user, registration of payment method information related to a payment method used by the user in the payment of the first transaction, the payment method information being acquired at the time of the payment of the first transaction between the user and the business, the business system being a business system of the first transaction; a payment token registration unit that receives registration of payment token information related to a payment token issued at the time of payment of the first transaction, the payment token information corresponding to the payment method information, from a payment system that performs processing related to the payment of the transaction; an identification information registration unit that registers user identification information that identifies the user; a user management unit that generates user management information that associates the payment method information, the payment token information, and the user identification information; A user management program that makes this possible.

2. The computer includes: a payment request information acquisition unit that acquires, from the business system in response to a second transaction between the user and the business, payment request information including at least one of the payment method information, the payment token information, and the user identification information; a payment processing information output unit that outputs, to the payment system, payment processing information for processing the payment of the second transaction based on the user management information and the payment request information; 2. The user management program according to claim 1, further comprising:

3. A user management program as described in claim 1 or 2, wherein the payment method registration unit registers the payment method information further based on consent information regarding the user's consent regarding the registration of the payment method information.

4. A user management program as described in Claim 3, wherein the payment method registration unit registers the payment method information further based on the consent information acquired when acquiring the payment method information.

5. The computer further includes a payment processing information generation unit configured to generate the payment processing information based on the user management information, the payment request information, and consent information regarding the user's consent to the generation of the payment processing information, The payment processing information output unit outputs the generated payment processing information.

3. The user management program according to claim 2.

6. The computer includes: and further realizing a registration information extraction unit that extracts the payment token information corresponding to the acquired payment request information based on the user management information when the payment token information is not included in the acquired payment request information; The payment processing information output unit outputs, to the payment system, the payment processing information for processing a payment of the second transaction using the payment token indicated by the extracted payment token information, further based on the extracted payment token information.

3. The user management program according to claim 2.

7. The computer includes: a registration information extraction unit that extracts the user identification information corresponding to the acquired payment request information based on the user management information when the user identification information is not included in the acquired payment request information; an identification information output unit that outputs the extracted user identification information to the business system; 7. The user management program according to claim 2, further comprising:

8. the user management unit generates the user management information further associated with preferential treatment management information for managing preferential treatment for the user in response to the transaction; The user management program according to claim 2 or 6, wherein the payment processing information output unit outputs the payment processing information further based on the preferential treatment management information corresponding to the acquired payment request information.

9. The computer includes: a privilege management information acquisition unit that acquires privilege management information for managing privileges for the user according to a transaction from the business operator system, the privilege management information corresponding to the output user identification information; The payment processing information output unit outputs the payment processing information further based on the acquired preferential treatment management information.

8. The user management program according to claim 7.

10. 3 . The user management program according to claim 1 , wherein the identification information registration unit registers the user identification information, which is obtained from the business operator system upon settlement of the first transaction, for identifying the user in the business operator system.

11. a payment method registration unit that receives, from a business system of a first transaction between a user and a business that conducts a face-to-face transaction with the user, registration of payment method information related to a payment method used by the user in the payment of the first transaction, the payment method information being acquired at the time of the payment of the first transaction between the user and the business, the business system being a business system of the first transaction; a payment token registration unit that receives registration of payment token information related to a payment token issued at the time of payment of the first transaction, the payment token information corresponding to the payment method information, from a payment system that performs processing related to the payment of the transaction; an identification information registration unit that registers user identification information that identifies the user; a user management unit that generates user management information that associates the payment method information, the payment token information, and the user identification information; A user management system comprising:

12. The computer accepting registration of payment method information relating to a payment method used by the user in a payment for a first transaction between a user and a business conducting a face-to-face transaction with the user from a business system of the business; accepting registration of payment token information related to a payment token issued at the time of payment of the first transaction, the payment token corresponding to the payment method information, from a payment system that performs processing related to the payment of the transaction; registering user identification information for identifying the user; generating user management information that associates the payment method information, the payment token information, and the user identification information; How to manage users.

Images