Information processing apparatus, program, and information processing method

Abstract

To improve convenience of user management by a member store while maintaining convenience in settlement of a user.SOLUTION: The payment management apparatus 101 includes a storage unit 1012 that stores first identification information for identifying a user and a payment means associated with the first identification information, an identification information acquisition unit 1013 that acquires the first identification information and second identification information for identifying the user by a member store that makes a payment with the user, an association unit 1014 that associates the second identification information with the payment means based on the first identification information, a payment information acquisition unit 1015 that acquires payment information including the second identification information and payment amount information indicating a payment amount, and a request unit 1016 that transmits a payment process request to an apparatus that executes a payment process by the payment means associated with the second identification information based on the payment information, in a system in which a user who makes a payment reads a predetermined code with a user terminal 201.SELECTED DRAWING: Figure 3

Description

[Technical Field]

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

[0002] Currently, payment services using 2D codes are being offered by many payment member stores. When making a payment at a store, users can operate their smartphone to launch the application for the payment service they want to use and perform the required operations to make the payment.

[0003] In payment services using two-dimensional codes, there is a method in which a two-dimensional code installed in a store or the like is read by a user's smartphone. There is also a system in which a store or the like that has contracts with multiple payment member stores allows a user to read a single two-dimensional code that can be read by each application provided by each payment member store, enabling payment with each payment member store. Patent Document 1 discloses a payment service that uses two-dimensional codes. [Prior art documents] [Patent documents]

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

[0005] When making a payment using a user terminal, the user can select a payment method, such as a credit card, to be used by the user. The payment method is stored in association with identification information that identifies the user by a payment service provider. During payment, the user makes the payment using a payment application or web page provided by the provider. In this case, the user can make the payment using a payment method that is pre-associated with the user's identification information, simplifying the input of payment method information. When a business uses identification information that identifies the user to make a payment, the identification information associated with the payment method is information that the business uses to manage the user. In this case, if a member store providing a product or service were to manage users using, for example, unique user identification information, it would be unable to register a payment method with the unique user identification information, reducing the convenience of customer management at the member store. Furthermore, registering a payment method for each member store each time a payment is made increases the operational burden on the user, reducing the convenience of user payments.

[0006] Therefore, an object of the present invention is to provide an information processing device, a program, and an information processing method that enable member stores to improve the convenience of user management while maintaining the convenience of user payments. [Means for solving the problem]

[0007] An information processing device according to one embodiment of the present invention is an information processing device in a system in which payments are made by reading a predetermined code using an application installed on a user terminal used by a user making a payment, and is equipped with: a memory unit that stores first identification information that identifies the user and a payment method associated with the first identification information; an identification information acquisition unit that acquires the first identification information and second identification information that identifies the user by an affiliated store that makes a payment with the user; an association unit that associates the second identification information with the payment method based on the first identification information; a payment information acquisition unit that acquires payment information including the second identification information and payment amount information indicating the amount of the payment; and a request unit that sends a request for payment processing to a payment execution device of the payment affiliated store that performs payment processing using the payment method associated with the second identification information based on the payment information.

[0008] According to this aspect, the information processing device can associate second identification information, which the affiliated store uses to identify the user, with a payment method based on the first identification information, which identifies the user. Then, payment processing is performed using the payment method associated with the second identification information based on payment information including the second identification information and payment amount information indicating the payment amount. This allows the user to make a payment using the second identification information instead of the first identification information associated with the payment method. Since the affiliated store can use the second identification information that it can manage, the convenience of customer management is improved. Furthermore, the convenience for the user is improved because payment can be made simply by associating the first identification information with the payment method.

[0009] In the above aspect, the identification information acquisition unit may further acquire user information that is used by the affiliated store to manage users and that is associated with the second identification information.

[0010] According to this aspect, the affiliated store can acquire user information about the user in addition to the second identification information, thereby improving the convenience of customer management for the affiliated store.

[0011] In the above aspect, the information processing device may further include a setting information acquisition unit that acquires setting information for setting input items of user information from the terminal of the affiliated store.

[0012] According to this aspect, the member store can individually set the user information that the member store acquires, thereby improving the convenience of customer management for the member store.

[0013] In the above aspect, the payment information acquisition unit may acquire payment information from a terminal of the affiliated store.

[0014] According to this aspect, the affiliated store can make a payment based on the second identification information through the affiliated store's terminal. For example, if an additional payment is required, the affiliated store can complete the payment without requiring any operation on the user's terminal, such as scanning a predetermined code. This improves convenience for the affiliated store and the user.

[0015] In the above aspect, the payment information may be information indicating a recurring payment to be made at a predetermined payment time.

[0016] By making it possible to register recurring payments, there is no need to operate the user terminal each time a payment is made, improving convenience for both affiliated stores and users.

[0017] In the above aspect, the information processing device may further include a setting information acquisition unit that acquires payment setting information including the payment timing of the recurring payment from the terminal of the affiliated store.

[0018] According to this aspect, the affiliated store can set the details of the recurring payment, thereby improving convenience for the affiliated store.

[0019] In the above aspect, the identification information acquisition unit acquires the first identification information and third identification information by which a second affiliated store different from the first affiliated store identifies the user, the association unit associates the third identification information with a payment means based on the first identification information, the payment information acquisition unit acquires second payment information including the third identification information and second payment amount information indicating the amount of payment between the user and the second affiliated store, and the request unit may send a request for the second payment process to a second payment execution device of the second payment affiliated store, which executes the second payment process using the payment means associated with the third identification information, based on the second payment information.

[0020] According to this aspect, different member stores can associate payment methods with the second identification information or the third identification information used to identify users at each member store. Each member store can use identification information that it can manage, improving the convenience of customer management. Furthermore, for users, simply by associating a payment method with the first identification information, they can make payments at each of multiple member stores, improving user convenience.

[0021] In the above aspect, the identification information acquisition unit may acquire first user information used by the first affiliated store to manage users and associated with second identification information, and second user information used by the second affiliated store to manage users and associated with third identification information.

[0022] According to this aspect, each member store can acquire user information, thereby improving the convenience of customer management for member stores.

[0023] In the above aspect, the information processing device may further include a setting information acquisition unit that acquires first setting information for setting input items for first user information from a terminal of the first affiliated store, and acquires second setting information for setting input items for second user information from a terminal of the second affiliated store. According to this aspect, each member store can obtain the user information that it requires according to its own settings, thereby improving the convenience of customer management for member stores.

[0024] Another aspect of the present invention provides a program for a system in which payments are made by reading a predetermined code using an application installed on a user terminal used by a user making a payment, the program causing a computer to store first identification information that identifies the user and a payment method associated with the first identification information, obtain the first identification information and second identification information that identifies the user by an affiliated store making a payment with the user, associate the second identification information with the payment method based on the first identification information, obtain payment information including the second identification information and payment amount information indicating the amount of the payment, and send a request for payment processing to a payment execution device of the payment affiliated store that performs payment processing using the payment method associated with the second identification information based on the payment information.

[0025] Another aspect of the information processing method of the present invention is an information processing method in which payment is made by reading a predetermined code using an application installed on a user terminal used by a user making payment, and includes the steps of: a computer storing first identification information that identifies the user and a payment means associated with the first identification information; acquiring the first identification information and second identification information that identifies the user by an affiliated store making payment with the user; associating the second identification information with the payment means based on the first identification information; acquiring payment information including the second identification information and payment amount information indicating the amount of the payment; and sending a request for payment processing to a payment execution device of the payment affiliated store that performs payment processing using the payment means associated with the second identification information based on the payment information. [Effects of the Invention]

[0026] According to the present invention, it is possible to provide a program, a method, and an information processing device that can improve the convenience of user management for member stores while maintaining the convenience of payment for users. [Brief explanation of the drawings]

[0027] [Figure 1] FIG. 1 is a schematic diagram of a payment management system. [Figure 2] FIG. 2 illustrates an example of a hardware configuration of the payment management device. [Figure 3] FIG. 2 is a block diagram of each device or terminal in the payment management system. [Figure 4] FIG. 10 is a diagram illustrating information stored in the payment management device. [Figure 5] FIG. 10 is a diagram illustrating information stored in the payment management device. [Figure 6] FIG. 10 is a diagram illustrating information stored in the payment management device. [Figure 7] FIG. 1 is a diagram illustrating a processing flow in a payment management system. [Figure 8] FIG. 1 is a diagram illustrating a processing flow in a payment management system. [Figure 9] FIG. 1 is a diagram illustrating a processing flow in a payment management system. [Figure 10] FIG. 10 is a diagram showing an example of a payment information request screen in the payment management system. [Figure 11] FIG. 10 is a diagram showing an example of a payment information input screen in the payment management system. [Figure 12] FIG. 10 is a diagram showing an example of a payment result screen in the payment management system. [Figure 13] FIG. 10 is a diagram showing another example of a payment information input screen in the payment management system. [Figure 14] FIG. 10 is a diagram showing another example of a payment result screen in the payment management system. [Figure 15] FIG. 10 is a diagram illustrating another flow of processing in the payment management system. [Figure 16] FIG. 10 is a diagram showing another example of a payment information input screen in the payment management system. [Figure 17] FIG. 10 is a diagram illustrating another example of information stored in the payment management device in the payment management system. [Figure 18] FIG. 10 is a diagram showing another example of a payment information input screen in the payment management system. DETAILED DESCRIPTION OF THE INVENTION

[0028] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A preferred embodiment of the present invention will be described with reference to the accompanying drawings. In the drawings, components with the same reference numerals have the same or similar configurations.

[0029] Figure 1 shows a block diagram illustrating an overview of a payment management system 10 according to this embodiment. The payment management system 10 includes a payment management device 101, user terminals 201a, 201b, and 201c, payment execution devices 301a, 301b, and 301c, and an affiliated store terminal 401. Although there are multiple user terminals and payment execution devices, such as user terminals 201a, 201b, and 201c and payment execution devices 301a, 301b, and 301c, they will be simply referred to as user terminal 201 and payment execution device 301 when there is no need to distinguish between them. Furthermore, affiliated store terminal 401 is a terminal managed by each affiliated store, and multiple devices may exist.

[0030] In the payment management system 10, the user terminal 201, the payment management device 101, and the affiliated store terminal 401 are communicatively connected via network N1. Also, in the payment management system 10, the payment management device 101 and the payment execution device 301 are communicatively connected via network N2.

[0031] In the payment management system 10, a predetermined code (e.g., a two-dimensional code) presented by a store that is an affiliated store using the payment service provided by the payment management system 10 or a salesperson belonging to the affiliated store is read using a user terminal 201 to access the payment management device 101. The payment management device 101 accepts designation of the payment method to be used by the user from the user terminal 201, and accesses the payment execution device 301 of the designated payment affiliated store. The user terminal 201 or affiliated store terminal 401 transmits information necessary for payment to the payment execution device 301. The payment is executed by the payment execution device 301, and the payment result is transmitted to the payment management device 101. The payment management device 101 notifies the user terminal 201 or affiliated store terminal 401 that the payment has been completed, and completes the payment.

[0032] Here, transactions that are the subject of settlement include, but are not limited to, various transactions such as the provision of services such as cleaning, the use of amusement facilities, and the purchase of goods.

[0033] The payment management device 101 is a server device having a computer that performs predetermined processes by executing predetermined programs stored in a storage unit of the payment management device 101 .

[0034] The user terminal 201 is, for example, an information processing device used by a user, such as a smartphone, a tablet terminal, a personal computer, etc. The user terminal 201 has an imaging means such as a camera, and can acquire information from a two-dimensional code.

[0035] The payment execution device 301 is a server device having a computer that performs predetermined processing by executing predetermined programs stored in the memory unit of the payment execution device 301. The payment execution device 301 performs payment by communicating with the user terminal 201. The user terminal 201 may access the payment execution device 301 through the payment management device 101, or may access the payment execution device 301 by communicating directly with the payment execution device 301.

[0036] The affiliated store terminal 401 is an information processing device used by a user who is an affiliated store, and is a smartphone, tablet terminal, personal computer, etc. The affiliated store can access the payment management device 101 from the affiliated store terminal 401 to send payment information, grasp the payment status, manage sales, etc.

[0037] An example of the hardware configuration of the payment management apparatus 101 will be described with reference to Fig. 2. The payment management apparatus 101 has a processor 501 such as a CPU (Central Processing Unit) or GPU (Graphical Processing Unit), a storage device 502 such as a memory, an HDD (Hard Disk Drive) and / or an SSD (Solid State Drive), a communication IF (Interface) 503 for wired or wireless communication, an input device 504 for accepting input operations, and an output device 505 for outputting information. The input device 504 is, for example, a keyboard, a touch panel, or a mouse. The output device 505 is, for example, a display or a touch panel.

[0038] 3, we will explain each part of the payment management device 101, user terminal 201, payment execution device 301, and affiliated store terminal 401. Each part of the payment management device 101, user terminal 201, payment execution device 301, and affiliated store terminal 401 can be realized by a processor executing a program stored in a storage device in an information processing device having the above-mentioned hardware configuration.

[0039] The payment management device 101 has a communication unit 1011, a memory unit 1012, an identification information acquisition unit 1013, an association unit 1014, a payment information acquisition unit 1015, a request unit 1016, a setting information acquisition unit 1017, a payment result acquisition unit 1018, and a notification unit 1019.

[0040] The communication unit 1011 can be realized using the communication IF 503 included in the payment management apparatus 101. The storage unit 1012 can be realized using the storage device 502 included in the payment management apparatus 101. The identification information acquisition unit 1013, the association unit 1014, the payment information acquisition unit 1015, the request unit 1016, the setting information acquisition unit 1017, the payment result acquisition unit 1018, and the notification unit 1019 can be realized by the processor 501 of the payment management apparatus 101 executing a program stored in the storage device 502. The program can be stored in a storage medium. The storage medium storing the program may be a non-transitory computer-readable medium. The non-transitory storage medium is not particularly limited, and may be, for example, a storage medium such as a USB memory or a CD-ROM.

[0041] The communication unit 1011 controls communication between the payment management device 101 and devices external to the payment management device 101 , including the user terminal 201 , the payment execution device 301 , and the affiliated store terminal 401 .

[0042] The storage unit 1012 stores various types of information used in the processing of the payment management device 101. The storage unit 1012 has a payment method DB 10121, an affiliated store user DB 10122, and an affiliated store setting DB 10123.

[0043] The information stored in the payment method DB 10121 will be described with reference to Figure 4. The payment method DB 10121 stores "user-specific payment method identification information" and "payment method" in association with each other. "User-specific payment method identification information" is an ID used to identify a user in the payment management system 10, and is assigned to each user. "Payment method" is information indicating the payment method used by the user for payment. Furthermore, a user can log in to the payment website provided by the payment management device 101 after being authenticated by submitting "user-specific payment method identification information" and authentication information. When "user-specific payment method identification information" is generated, the payment management device 101 can obtain authentication information from the user. The payment management device 101 stores authentication information in association with "user-specific payment method identification information." Here, authentication information may be, for example, the user's biometric information (fingerprint, facial expression, etc.) or a password set by the user.

[0044] In the example of Figure 4, for a user whose "user-specific payment method identification information" is "XXX1", "credit card A" is stored as the "payment method", and for a user whose "user-specific payment method identification information" is "XXX2", "credit card B" is stored as the "payment method". Here, credit card information specifically stores information necessary for card payments, such as card number and expiration date. Note that payment methods are not limited to credit cards, and for example, electronic money payment methods may also be stored. The process of updating the payment method DB10121 will be described later.

[0045] The information stored in the affiliated store user DB 10122 will be described with reference to Figure 5. The affiliated store user DB 10122 stores information used by each of multiple affiliated stores that use the payment management system 10 to manage users. The affiliated store user DB 10122 stores "affiliated store user identification information," "user information," "user payment method identification information," and "payment method" in association with each other.

[0046] "Affiliated store-specific user identification information" is an ID or the like that each affiliated store assigns to a user in order for the affiliated store to manage the user. "Affiliated store-specific user identification information" may be any information necessary for the affiliated store to identify the user, such as an email address or telephone number, and is information that each affiliated store can set as desired. "User information" is information that each affiliated store stores as user information in association with "affiliated store user identification information." As an example, "user information" is information that each affiliated store determines is necessary for user management, such as the user's name, telephone number, email address, and other notes.

[0047] In the example of Figure 5, three affiliated stores A, B, and C each store "affiliated store-specific user identification information," "user information," "user-specific payment method identification information," and "payment method." For example, affiliated store A stores "AAA1" as "affiliated store-specific user identification information," in association with "XXX1" as "user-specific payment method identification information," and "credit card A" as "payment method." Affiliated store B stores "XXX1" as "user-specific payment method identification information" and "credit card A" as "payment method," in association with "BBB1," which is different from "AAA1" as "affiliated store-specific user identification information" for affiliated store A. In this way, in affiliated store-specific user DB10122, affiliated store user identification information for each affiliated store is stored in association with user-specific payment method identification information and payment method.

[0048] The information stored in the member store setting DB 10123 will be described with reference to Figure 6. The member store setting DB 10123 stores information items that each of the multiple member stores that use the payment management system 10 has determined to be necessary to acquire as user information, as well as payment fee plan information. The member store setting DB 10123 stores information in the "user information setting items" and "recurring billing plan" fields.

[0049] The "user information setting items" store the type of information that each affiliated store wishes to acquire as user information. For example, the setting stored for affiliated store A is that the name and date of birth are to be acquired as user information. The payment management device 101 acquires user information based on the information stored in the "user information setting items." Similarly, the setting stored for affiliated store B is that the name and email address are to be acquired as user information, and the setting stored for affiliated store C is that the name and telephone number are to be acquired as user information.

[0050] The "recurring billing plan" stores information about the pricing plan that each affiliated store sets independently. The pricing plan information is, for example, information about recurring payments. While the name of each plan is shown in Figure 6, the specific information about recurring payments, such as the payment period and payment amount for each plan, is stored.

[0051] The identification information acquisition unit 1013 acquires user-specific payment method identification information (first identification information) and affiliated store-specific user identification information (second identification information). Specifically, the identification information acquisition unit 1013 acquires user-specific payment method identification information from the user terminal 201. The identification information acquisition unit 1013 may also acquire authentication information in addition to the user-specific payment method identification information. User authentication is performed based on the user-specific payment method identification information and the authentication information. The identification information acquisition unit 1013 also acquires affiliated store-specific user identification information from the user terminal 201 or the affiliated store terminal 401. The timing of acquiring each piece of identification information does not always need to be the same; for example, the identification information acquisition unit 1013 may acquire only one of the user-specific payment method identification information or the affiliated store-specific user identification information.

[0052] The associating unit 1014 associates the affiliated store user identification information with the payment method based on the user-specific payment method identification information. The associating unit 1014 references the affiliated store user DB 10122 based on the user-specific payment method identification information to identify the corresponding payment method. The associating unit 1014 associates the affiliated store user identification information with the identified payment method. The associating unit 1014 updates the affiliated store user DB 10122.

[0053] The payment information acquisition unit 1015 acquires payment information including affiliated store user identification information and payment amount information indicating the payment amount. For example, in response to reading a code by the user terminal 201, the payment information acquisition unit 1015 acquires from the user terminal 201 the affiliated store user identification information and payment amount information recorded in the code. In addition, in response to reading a predetermined code generated based on the payment amount information, the payment information acquisition unit 1015 acquires the affiliated store user identification information and payment amount information. Alternatively, the payment information acquisition unit 1015 generates input screen information for displaying on the user terminal 201 an input screen that accepts input of the affiliated store user identification information and payment amount information, and acquires the affiliated store user identification information and payment amount information from the user terminal 201 via the input screen. In addition, the payment information acquisition unit 1015 can acquire payment information from each of the affiliated store terminals of multiple affiliated stores.

[0054] The request unit 1016 transmits a request for payment processing to the payment execution device that executes payment processing using the payment means associated with the affiliated store user identification information based on the payment information. The request unit 1016 may relay information so that the user terminal 201 can access the payment execution device 301 via the payment management device 101, or may provide the user terminal 201 with information that enables the user terminal 201 to directly access the payment execution device 301.

[0055] The setting information acquisition unit 1017 acquires setting information for setting input items for user information from the member store terminal 401. The setting information acquisition unit 1017 updates the member store setting DB 10123 based on the acquired setting information. The setting information acquisition unit 1017 also acquires payment setting information including the payment timing for recurring payments from the member store terminal 401. The setting information acquisition unit 1017 updates the member store setting DB 10123 based on the acquired payment setting information. The setting information acquisition unit 1017 can acquire setting information or payment setting information from each of the member store terminals of multiple member stores.

[0056] The payment result acquisition unit 1018 acquires the processing result of the payment process from the payment execution device 301 corresponding to the specified payment affiliated store.

[0057] The notification unit 1019 notifies the terminal that sent the payment request, that is, the user terminal 201 or the affiliated store terminal 401, of the processing result of the payment process.

[0058] The user terminal 201 has a communication unit 2011, a storage unit 2012, a display unit 2013, and an input unit 2014. The communication unit 2011 controls communication between the user terminal 201 and external devices such as the payment management device 101 and the payment execution device 301. The storage unit 2012 stores programs and the like required for the operation of the user terminal 201. The display unit 2013 is, for example, a display, and presents a screen to the user operating the user terminal 201. The input unit 2014 controls the input of information to the user terminal 201. For example, the input unit 2014 accepts information input from the user via a screen displayed on the display unit 2013. The input unit 2014 also accepts input of image information via an imaging device of the user terminal 201. When a code is read as an image, the input unit 2014 extracts information based on the information contained in the code. Based on the extracted information, the user terminal 201 can communicate with the payment management device 101 and the like.

[0059] The payment execution device 301 is a server that performs payment processing, and includes a payment unit 3011. The payment execution device 301 also includes components necessary for various information processing, such as a communication unit and a memory unit. The payment unit 3011 obtains information necessary for settling the payment amount, such as credit card information and payment service account information, from the payment management device 101 or the user terminal 201, and performs payment processing. The payment execution device 301 transmits the payment result to the payment management device 101.

[0060] The affiliated store terminal 401 has a communication unit 4011, a memory unit 4012, a display unit 4013, and an input unit 4014. The communication unit 4011 controls communication between the affiliated store terminal 401 and external devices such as the payment management device 101. The memory unit 4012 stores programs and the like required for the operation of the affiliated store terminal 401. The display unit 4013 is, for example, a display, and presents a screen to the user operating the affiliated store terminal 401. The input unit 4014 controls the input of information to the affiliated store terminal 401.

[0061] The process of updating the payment method DB 10121 will be described with reference to Fig. 7. In step S701, the user terminal 201 reads a predetermined code.

[0062] In step S702, a request for a payment method input screen is sent from the user terminal 201 to the payment management device 101. In step S703, information on the payment method input screen is sent from the payment management device 101 to the user terminal 201. In step S704, the user sends payment method information, including information such as a credit card number and expiration date, and authentication information to the payment management device 101 as payment method information, via the payment method input screen displayed on the user terminal 201.

[0063] In step S705, the payment management device 101 generates user-specific payment method identification information for the user. In step S706, the payment management device 101 associates payment method information with the generated user-specific payment method identification information and updates the payment method DB 10121. At this time, authentication information is associated with the user-specific payment method identification information. In step S707, the payment management device 101 sends the generated user-specific payment method identification information to the user terminal 201. From the next time onwards, the user will be able to make payments by logging in to the website provided by the payment management device 101 based on the user-specific payment method identification information and authentication information.

[0064] The update process for the member store setting DB 10123 will be described with reference to Figure 8. In the following, it is assumed that the member store has logged in to the website provided by the payment management device 101 using its own account, and that the payment management device 101 is able to identify the member store. In step S801, the member store terminal 401 acquires setting information from the member store user. In step S802, the setting information acquisition unit 1017 acquires setting information from the member store terminal 401. In step S803, the setting information acquisition unit 1017 updates the member store setting DB 10123.

[0065] In step S804, the affiliated store terminal 401 acquires payment setting information from the user of the affiliated store. In step S805, the setting information acquisition unit 1017 acquires the payment setting information from the affiliated store terminal 401. In step S806, the setting information acquisition unit 1017 updates the affiliated store setting DB 10123. Note that the acquisition and update of the setting information do not need to be performed simultaneously with the acquisition and update of the payment setting information, and each process can be performed at any timing.

[0066] The payment processing in the payment management system 10 will be described with reference to Figures 9, 10, 11, and 12. Here, we will explain an example in which information about the affiliated store to which payment is made and information about the payment amount entered through the affiliated store terminal are embedded in the code. Note that the information about the payment amount may be obtained by inputting information through the user terminal 201 or may be obtained separately through inputting information through the affiliated store terminal 401.

[0067] In step S901, the user terminal 201 reads the code provided by the affiliated store.

[0068] In step S902, the user terminal 201 sends a request for a payment information input screen to the payment management apparatus 101. The request for the payment information input screen is made via a payment information request screen 1001 shown in FIG. 10. The payment information request screen 1001 has a payment destination display field 10011 in which information about the payment is displayed based on a predetermined code, and a method selection button 10012. When the user selects the method selection button 10012, a request is sent to the payment management apparatus 101.

[0069] In step S903, the payment management device 101 sends an authentication request to the user terminal 201. In step S904, the identification information acquisition unit 1013 acquires user-specific payment method identification information and authentication information from the user terminal 201. If the user authentication is successful, the subsequent processing proceeds.

[0070] In step S905, the identification information acquisition unit 1013 acquires user-specific payment method identification information corresponding to the authentication result based on the authentication result. The identification information acquisition unit 1013 identifies the payment method corresponding to the user-specific payment method identification information.

[0071] In step S906, the identification information acquisition unit 1013 transmits information on the payment method confirmation screen to the user terminal 201. In step S907, the user terminal 201 displays a payment information input screen.

[0072] FIG. 11 shows an example of a payment method confirmation screen 1101. The payment method confirmation screen 1101 has a payment information display area 11011, selection buttons 11012a and 11012b, and a proceed button 11013. The payment information display area 11011 displays information about the payment based on a predetermined code. In the example of FIG. 11, it is displayed that a payment of 5,000 yen will be made at affiliated store A. The payment method confirmation screen 1101 displays information about the payment method corresponding to the user-specific payment method identification information. By selecting selection buttons 11012a and 11012b, the user can select a registered payment method or register a new payment method. Note that multiple payment methods may be registered. For example, if the user wants to change the payment method, they can select 11012b and enter information about the new payment method. By selecting the proceed button 11013, the user sends the payment method selection result to the payment management device 101 in step S908.

[0073] In step S909, the identification information acquisition unit 1013 generates information for an affiliated store user identification information input screen. The identification information acquisition unit 1013 generates information for an affiliated store user identification information input screen in accordance with the setting information set in the affiliated store setting DB 10123.

[0074] In step S910, the identification information acquisition unit 1013 transmits to the user terminal 201 information on the member store-specific user identification information input screen.

[0075] In step S911, a member store-specific user identification information input screen is displayed on the user terminal 201.

[0076] 12 shows, as an example, an affiliated store-specific user identification information input screen 1201. The affiliated store-specific user identification information input screen 1201 has a payment information display area 12011, a user information input field 12012, a user information input field 12013, a user information input field 12014, and a proceed button 12015.

[0077] Payment information display area 12011 displays information related to the payment. Identification information input field 12012 displays an input field for inputting affiliated store-specific user identification information. User information input fields 12013 and 12014 display input fields for inputting user information. Identification information input field 12012 displays an input field for a member ID as affiliated store-specific user identification information. User information input field 12013 displays an input field for a name. User information input field 12014 displays an input field for a date of birth. Each piece of information is input via user terminal 201. In the example of FIG. 12, "AAA1", which is affiliated store-specific user identification information managed by affiliated store A, the payment recipient, is input as the member ID. In addition, the information of "name" and "date of birth" set by affiliated store A in affiliated store-specific setting DB 10123 is input. At this time, the member ID information is input by, for example, being communicated to the user by a member store staff member, and the user inputs the communicated information.

[0078] When the proceed button 12015 is selected, in step S912, the payment information acquisition unit 1015 acquires payment information including the member store-specific user identification information and payment amount information. At this time, the identification information acquisition unit 1013 also acquires user information.

[0079] In step S913, the associating unit 1014 associates the payment method with the member store user identification information based on the user-specific payment method identification information that has already been acquired. The associating unit 1014 updates the member store user DB 10122. When the information shown in FIG. 12 is acquired, the associating unit 1014 updates the member store user DB 10122 by associating the member store user identification information "AAA1" with "XXX1" and "Credit card A" as the user-specific payment method identification information and payment method.

[0080] In step S914, the request unit 1016 sends a request for payment processing of the payment amount to the payment execution device 301 based on the payment method associated with the affiliated store user identification information. For example, in the example of Figure 12, a payment is being made by a user with member ID "AAA1", so payment is made using "credit card A" as the payment method. The request unit 1016 identifies the payment execution device 301 that will make the payment using "credit card A", and sends a request to the identified payment execution device 301.

[0081] In step S915, the payment unit 3011 performs payment processing. At this time, the payment execution device 301 may obtain information necessary for payment, such as a password or passcode for credit card payment, from the user terminal 201 as necessary.

[0082] In step S 916 , the settlement result acquisition unit 1018 acquires the settlement result from the settlement execution device 301 .

[0083] In step S917, the notification unit 1019 notifies the user terminal 201 of the settlement result.

[0084] Another example screen in the payment management system 10 will be described with reference to Figures 13 and 14. Here, a case is shown in which a user whose per-user payment method identification information is "XXX1" makes a payment at affiliated store B. It is assumed that the user reads the code provided by affiliated store B using the user terminal 201. In the case of affiliated store B, the processing from step S901 to step S908 is the same as the processing described above for affiliated store A.

[0085] FIG. 13 shows the payment method confirmation screen 1301 displayed by the processing of step S907. On the payment method confirmation screen 1301, information that the payment is made to affiliated store B and information on the payment amount are displayed in the payment information display area 13011. At this time, the credit card information corresponding to selection button 13012a is displayed as in the payment method confirmation screen 1101, and the information for "Credit card A" corresponding to the affiliated store user identification information in the affiliated store user DB 10122 is displayed. It is also possible to update the card information by selecting selection button 13012b. When proceed button 13013 is selected, the confirmation result is sent to the payment management device 101.

[0086] FIG. 14 shows an affiliated store user identification information input screen 1401 that is displayed on the user terminal 201 by the processing from step S909 to step S911.

[0087] On affiliated store-specific user identification information input screen 1401, payment information display area 14011 displays information related to payment. Identification information input field 14012 displays an input area for inputting affiliated store-specific user identification information. User information input fields 14013 and 14014 display input areas for inputting user information. Identification information input field 14012 displays an input field for member ID as affiliated store-specific user identification information. User information input field 14013 displays an input field for name. User information input field 14014 displays an input field for email address. Each piece of information is input via user terminal 201. In the example of Figure 14, "BBB1", which is affiliated store-specific user identification information managed by affiliated store B, the payment recipient, is input as the member ID. In addition, the information of "name" and "email address" set by affiliated store B in affiliated store-specific setting DB 10123 is input.

[0088] When the proceed button 14015 is selected, in step S912, the payment information acquisition unit 1015 acquires payment information including affiliated store-specific user identification information and payment amount information. At this time, the setting information acquisition unit 1017 also acquires user information.

[0089] In step S913, the associating unit 1014 associates the payment method with the affiliated store user identification information based on the user-specific payment method identification information already acquired. The associating unit 1014 updates the affiliated store user DB10122. When the information shown in FIG. 14 is acquired, the associating unit 1014 updates the affiliated store user DB10122 by associating the affiliated store user identification information "BBB1" with "XXX1" and "Credit card A" as the user-specific payment method identification information and payment method. Thereafter, the same payment process is executed.

[0090] In this way, the payment management device 101 allows each member store to manage its own user identification information, while still being able to associate a common payment method.

[0091] The payment process based on the member store-specific user identification information will be described with reference to Figures 15 to 18. Here, we will explain an example in which the member store terminal 401 of member store A sends a payment request to the payment management device 101 and payment processing is carried out. It is assumed that the member store terminal 401 has logged in to the website provided by the payment management device 101 using its own ID and password, for example.

[0092] In step S1501 of FIG. 15, the payment information acquisition unit 1015 acquires a request for a payment information input screen from the affiliated store terminal 401. Here, it is assumed that a request for a payment information input screen for setting up a payment related to a recurring payment has been sent. In step S1502, the payment information acquisition unit 1015 generates information for the payment information input screen. In step S1503, the payment information acquisition unit 1015 transmits the information for the payment information input screen to the affiliated store terminal 401.

[0093] 16 shows an example of a payment information input screen 1601. The payment information input screen 1601 has an identification information input field 16011, a payment information input field 16012, and a confirm button 16013. In step S1504, payment information is acquired by entering information in the identification information input field 16011 and the payment information input field 16012.

[0094] Affiliated store-specific user identification information is entered in the identification information input field 16011. Payment information is entered in the payment information input field 16012. In the example of FIG. 16, the member ID "AAA1", which is affiliated store-specific user identification information managed by affiliated store A, is entered. "Plan A", which is the recurring billing plan set by affiliated store A in the affiliated store-specific setting DB 10123, is entered in the payment information input field 16012. The recurring billing plan is entered, for example, by directly entering the plan or by selecting a plan from a list of multiple set billing plans. When the confirm button 16013 is selected, in step S1505 the payment information acquisition unit 1015 acquires the payment information.

[0095] In step S1506, the payment information acquisition unit 1015 updates the affiliated store user DB 10122 based on the billing plan included in the payment information. Figure 17 shows an example of the updated affiliated store user DB 10122. In the example of Figure 17, "Plan A" is associated with the affiliated store user identification information "AAA1" of affiliated store A as recurring payment information.

[0096] In step S1507, the request unit 1016 refers to the affiliated store user DB 10122 and identifies the payment method. In the example of Figure 17, "Credit card A" is identified as the payment method. The request unit 1016 identifies the payment execution device 301 that will execute the payment using "Credit card A" and sends a request to the identified payment execution device 301.

[0097] In step S1509, the settlement unit 3011 performs settlement processing. In step S1510, the settlement result acquisition unit 1018 acquires the settlement result from the settlement execution device 301. In step S1511, the notification unit 1019 notifies the user terminal 201 of the settlement result.

[0098] The processing up to this point makes it possible to perform payment without reading a code through the user terminal 201. In the case of a recurring payment, the processing from step S1507 onwards is executed according to the settings for the recurring payment.

[0099] Furthermore, the affiliated store terminal 401 may be configured to perform payment on a case-by-case basis via a payment information input screen 1801 as shown in Fig. 18. Payment can be executed based on affiliated store-specific user identification information entered in an identification information input field 18011 on the payment information input screen 1801 and the payment amount entered in a payment information input field 18012, and managed by an order ID entered in a management information input field 18013. When the confirm button 18014 is selected, the processing from step S1507 onwards is performed, and the payment can be executed.

[0100] As described above, payments are made through the payment management system 10. The payment management system 10 allows multiple member stores to manage users using their own member store-specific user identification information, and by associating the member store-specific user identification information with a payment method associated with the user-specific payment method identification information, payments can be made using the member store-specific user identification information. This makes it possible to improve the convenience of user management by member stores while maintaining the convenience of user payments.

[0101] The above-described embodiments are intended to facilitate understanding of the present invention and are not intended to limit the present invention. The elements of the embodiments, as well as their arrangement, conditions, shape, size, etc., are not limited to those exemplified and can be modified as appropriate. [Explanation of symbols]

[0102] 10...payment management system, 101...payment management device, 201...user terminal, 301...payment execution device, 401...member store terminal, 1013...identification information acquisition unit, 1014...association unit, 1015...payment information acquisition unit, 1016...request unit, 1017...setting information acquisition unit

Claims

1. An information processing device in a system in which a payment is made by reading a predetermined code with an application installed on a user terminal used by a user making the payment, a storage unit that stores first identification information that identifies the user and a payment method associated with the first identification information; an identification information acquisition unit that acquires the first identification information and second identification information that identifies the user by an affiliated store that performs payment with the user; an association unit that associates the second identification information with the payment means based on the first identification information; a payment information acquisition unit that acquires payment information including the second identification information and payment amount information indicating the amount of the payment; An information processing device comprising: a request unit that sends a request for the payment processing to a payment execution device of a payment affiliated store that executes the payment processing using the payment means associated with the second identification information based on the payment information.

2. 2. The information processing device according to claim 1, The identification information acquisition unit further acquires user information that is used by the affiliated store to manage the user and that is associated with the second identification information.

3. 3. The information processing device according to claim 2, The information processing device further comprises a setting information acquisition unit that acquires setting information for setting input items of the user information from the terminal of the affiliated store.

4. 2. The information processing device according to claim 1, The payment information acquisition unit acquires the payment information from a terminal of the affiliated store.

5. 5. The information processing device according to claim 4, An information processing device, wherein the payment information is information indicating a recurring payment to be made at a predetermined payment time.

6. 6. The information processing device according to claim 5, The information processing device further includes a setting information acquisition unit that acquires payment setting information including the payment timing of the recurring payment from the terminal of the affiliated store.

7. 2. The information processing device according to claim 1, the identification information acquisition unit acquires the first identification information and third identification information by which a second affiliated store different from the first affiliated store that is the affiliated store identifies the user; the associating unit associates the third identification information with the payment means based on the first identification information; the payment information acquisition unit acquires second payment information including the third identification information and second payment amount information indicating an amount of payment between the user and the second affiliated store; The request unit sends a request for the second payment processing to a second payment execution device of a second payment affiliated store that executes the second payment processing using the payment means associated with the third identification information based on the second payment information.

8. 8. The information processing device according to claim 7, The identification information acquisition unit acquires first user information used by the first affiliated store to manage the user and associated with the second identification information, and second user information used by the second affiliated store to manage the user and associated with the third identification information.

9. 9. The information processing device according to claim 8, The information processing device further includes a setting information acquisition unit that acquires first setting information that sets input items of the first user information from the terminal of the first affiliated store, and acquires second setting information that sets input items of the second user information from the terminal of the second affiliated store.

10. In a system in which a payment is made by reading a predetermined code with an application installed on a user terminal used by the user making the payment, On the computer, storing first identification information that identifies the user and a payment method associated with the first identification information; Acquiring the first identification information and second identification information that identifies the user by an affiliated store that performs a settlement with the user; Associating the second identification information with the payment means based on the first identification information; acquiring payment information including the second identification information and payment amount information indicating an amount of the payment; A program that executes the process of sending a request for the payment processing to a payment execution device of a payment affiliated store that executes the payment processing using the payment means associated with the second identification information based on the payment information.

11. An information processing method in which a payment is made by reading a predetermined code with an application installed on a user terminal used by a user making the payment, The computer storing first identification information that identifies the user and a payment method associated with the first identification information; Acquiring the first identification information and second identification information that identifies the user by an affiliated store that performs a settlement with the user; Associating the second identification information with the payment means based on the first identification information; acquiring payment information including the second identification information and payment amount information indicating an amount of the payment; An information processing method including: sending a request for the payment processing to a payment execution device of a payment affiliated store that executes the payment processing using the payment means associated with the second identification information based on the payment information.

Images