Information processing device, control method, and control program

Abstract

In code-based payment systems where payment functions are used by users other than the user themselves, the present invention provides an information processing device that enables secure use of payment functions by other users. [Solution] In a payment system, an information processing device 10 that issues a payment code for withdrawing a payment amount from the account of a first user to a second user terminal of a second user associated with the first user includes: an issuance request acquisition unit 132 that acquires a payment code issuance request from the second user terminal; a token transmission unit 134 that transmits a payment token for generating a payment code to the second user terminal when a first determination unit 133 determines that a first predetermined condition is met; a payment information acquisition unit 135 that acquires a payment token and payment information at the store from the store terminal; and a payment execution unit 137 that executes a payment based on the payment information when a second determination unit 136 determines that a second predetermined condition different from the first predetermined condition is met.

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, a control method, and a control program.

Background Art

[0002] Code settlement using two-dimensional barcodes such as QR Code (registered trademark) has become widespread (for example, Patent Document 1). On the other hand, there is a need to allow other users (members of a group such as family members or employees) to use one's own settlement function, and family cards are provided for credit cards.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In code settlement, the function of a family card is also required, and furthermore, new values that cannot be realized by a physical card are also required.

[0005] In view of the above background, an object of the present invention is to provide an information processing apparatus or the like that enables another user to use one's own settlement function in a safe manner in code settlement that allows another user other than oneself to use one's own settlement function.

Means for Solving the Problems

[0006] The present invention relates to an information processing device that issues a payment code for withdrawing a payment amount from an account managed by a first user to a second user terminal used by a second user associated with the first user, and comprises: an issuance request acquisition unit that acquires a request from the second user terminal for the second user to issue the payment code for making a payment at a store; a first determination unit that determines whether or not the first predetermined conditions corresponding to the second user, set by the first user, are met; a token transmission unit that, when the first determination unit determines that the first predetermined conditions are met, transmits a payment token for generating the payment code to the second user terminal; a payment information acquisition unit that acquires the payment token and the second user's payment information at the store from a store terminal that reads the payment code displayed by the second user terminal based on the payment token; a second determination unit that determines whether or not the second predetermined conditions, different from the first predetermined conditions, corresponding to the second user, are met, set by the first user; and a payment execution unit that, when the second determination unit determines that the second predetermined conditions are met, executes a payment based on the payment information received from the store terminal.

[0007] The present invention relates to a control method for an information processing device that issues a payment code for withdrawing a settlement amount from an account managed by a first user to a second user terminal used by a second user associated with the first user, and comprises: an issuance request acquisition step of obtaining a request from the second user terminal for the second user to issue the payment code for settlement at a store; a first determination step of determining whether or not a first predetermined condition corresponding to the second user, set by the first user, is met; a token transmission step of transmitting a payment token for generating the payment code to the second user terminal if the first determination step determines that the first predetermined condition is met; a settlement information acquisition step of obtaining the payment token and the second user's settlement information at the store from a store terminal that has read the payment code displayed by the second user terminal based on the payment token; a second determination step of determining whether or not a second predetermined condition, different from the first predetermined condition, corresponding to the second user, set by the first user, is met; and a settlement execution step of executing a settlement based on the settlement information received from the store terminal if the second determination step determines that the second predetermined condition is met.

[0008] The control program of the present invention is a control program for an information processing device that issues a settlement code for withdrawing a settlement amount from an account managed by a first user to a second user terminal used by a second user associated with the first user, and causes a computer to execute: an issuance request acquisition step of obtaining a request from the second user terminal for the issuance of the settlement code for the second user to make a settlement at a store; a first determination step of determining whether or not the first predetermined conditions corresponding to the second user, set by the first user, are met; a token transmission step of sending a settlement token for generating the settlement code to the second user terminal if the first determination step determines that the first predetermined conditions are met; a settlement information acquisition step of obtaining the settlement token and the second user's settlement information at the store from a store terminal that has read the settlement code displayed by the second user terminal based on the settlement token; a second determination step of determining whether or not the second predetermined conditions, different from the first predetermined conditions, corresponding to the second user, set by the first user, are met; and a settlement execution step of executing a settlement based on the settlement information received from the store terminal if the second determination step determines that the second predetermined conditions are met. [Effects of the Invention]

[0009] According to the present invention, in a code payment system that allows another user to use the payment function, it is possible to allow another user to use the payment function in a secure manner. [Brief explanation of the drawing]

[0010] [Figure 1] This is a diagram illustrating the overview of the payment system according to the first embodiment. [Figure 2] This figure shows the hardware configuration of the payment system according to the first embodiment. [Figure 3] This figure shows the functional configuration of the information processing device according to the first embodiment. [Figure 4] This figure shows an example of condition information related to the first embodiment. [Figure 5] This diagram shows the functional configuration of the first user terminal according to the first embodiment. [Figure 6] This figure shows an example of a settings screen for configuring issuance permission conditions and payment approval conditions. [Figure 7] This figure shows the functional configuration of the second user terminal according to the first embodiment. [Figure 8] This diagram shows the functional configuration of the store terminal according to the first embodiment. [Figure 9] This is a diagram illustrating the operation of the payment system. [Figure 10] This is a diagram illustrating the operation of the payment system. [Figure 11] This figure shows the functional configuration of the first user terminal according to the second embodiment. [Figure 12] This figure shows an example of a settings screen for requesting the generation of a second payment code. [Figure 13] This figure shows the functional configuration of the information processing device according to the second embodiment. [Modes for carrying out the invention]

[0011] The payment systems of each embodiment will be described below with reference to the drawings. Note that the following description is merely an example of a preferred embodiment and is not intended to limit the invention as described in the claims.

[0012] (First Embodiment) [Overview of Payment System S] Figure 1 is a diagram illustrating an overview of the payment system S according to the first embodiment. The payment system S is a system that, when a user purchases goods or services (hereinafter sometimes simply referred to as "goods") at a store, displays a payment code on the user terminal in response to a request from the user's terminal, and executes the payment process at the store when the payment code is read. The payment code is an image or text read by the store's terminal and is the code used at the time of payment.

[0013] The settlement system S according to this embodiment includes an information processing device 10, a first user terminal 20, a second user terminal 30, and a store terminal 40. The information processing device 10 is a computer that issues a settlement code for deducting a settlement amount from an account managed by a first user to a second user terminal used by a second user associated with the first user and executes settlement of the purchase amount. The first user terminal 20 is an information processing terminal used by the first user, such as a smartphone, a tablet, or a personal computer. The second user terminal 30 is an information processing terminal used by a second user associated with the first user, such as a smartphone, a tablet, or a personal computer. The store terminal 40 is, for example, a POS terminal. The first user and the second user are associated with each other by having a predetermined relationship. Hereinafter, the case where the first user is a parent and the second user is a child of the first user will be described as an example.

[0014] FIG. 1 is a diagram for explaining the flow until settlement is completed. The first user, who is the parent, uses the first user terminal 20 that he / she possesses to set predetermined conditions corresponding to the second user for restricting settlement using the settlement code by the second user, who is the child, in advance. The first user terminal 20 transmits a setting request for predetermined conditions corresponding to the second user for restricting code settlement to the information processing device 10 ((1) in FIG. 1). The predetermined conditions are, for example, an issuance permission condition for permitting the issuance of a settlement code and a settlement approval condition for approving settlement, and these are different conditions from each other. When the information processing device 10 receives the setting requests for the issuance permission condition and the settlement approval condition from the first user terminal 20, it sets the issuance permission condition and the settlement approval condition corresponding to the second user based on the received setting requests ((2) in FIG. 1). At this time, the information processing device 10 associates the first user ID as the first user identification information for identifying the first user with the second user ID as the second user identification information for identifying the second user.

[0015] After that, when the second user purchases a product at the store, the second user launches the payment application software and performs an operation to display the payment code on the second user terminal 30. When the second user terminal 30 receives the operation to display the payment code, it transmits the second user ID of the second user and the issuance request for the payment code to the information processing device 10 (step (3) in FIG. 1).

[0016] The information processing device 10 receives the second user ID and the issuance request for the payment code from the second user terminal 30. When the information processing device 10 receives the issuance request for the payment code, it determines whether the issuance permission conditions set by the first user are satisfied (step (4) in FIG. 1). When the information processing device 10 determines that the issuance permission conditions are satisfied, it generates a payment token (step (5) in FIG. 1). The payment token is a data sequence used when the second user terminal 30 generates the payment code presented by the second user at the store. The information processing device 10 stores the generated payment token and the second user ID in association with each other in a storage medium (step (6) in FIG. 1).

[0017] The information processing device 10 transmits the generated payment token to the second user terminal 30 (step (7) in FIG. 1). The information processing device 10 may transmit the payment code itself instead of the payment token to the second user terminal 30.

[0018] The second user terminal 30 generates and displays a payment code based on the received payment token (step (8) in FIG. 1). The second user presents the payment code when settling the purchase price of the product at the store cashier. Then, for example, by the operation of the store clerk, the store terminal 40 reads the payment code displayed on the second user terminal 30 (step (9) in FIG. 1).

[0019] The store terminal 40 transmits to the information processing device 10 the settlement information including the settlement amount at the store indicating the total amount of the products purchased by the second user, the store type information indicating the type of the store, and the store ID identifying the store, and the payment token indicated by the read payment code (step (10) in FIG. 1).

[0020] The information processing device 10 determines whether the payment token received from the store terminal 40 matches the payment token sent to the second user terminal 30. If the information processing device 10 determines that the payment token received from the store terminal 4 matches the payment token sent to the second user terminal 30, it determines whether the payment authorization conditions set by the first user of the first user ID associated with the second user ID associated with the payment token are met (Figure 1, (11)). The information processing device 10 then executes a payment process to deduct the payment amount from the account of the first user of the first user ID associated with the second user ID associated with the payment token (Figure 1, (12)).

[0021] As described above, the payment system S operates in such a way that when a second user attempts to make a code payment, if at least one of the issuance permission conditions or payment approval conditions set by the first user is not met, the code payment will not be processed. This allows the payment system S to allow other users to use the payment function securely by performing different approval checks at the time of code issuance and payment approval. Furthermore, by performing two checks using different issuance permission conditions and payment approval conditions, the burden of the check processing at the time of payment can be reduced, the check processing can be sped up compared to when the check is performed only at the time of payment, and checkout lines can be reduced.

[0022] The following describes the detailed configuration of the information processing device 10, the first user terminal 20, the second user terminal 30, and the store terminal 40.

[0023] Figure 2 shows the hardware configuration of the information processing device 10, the first user terminal 20, the second user terminal 30, and the store terminal 40, which constitute the payment system S according to this embodiment. The information processing device 10 is connected to the first user terminal 20 and the second user terminal 30 so as to be able to communicate with them. The information processing device 10 is also connected to the store terminal 40 so as to be able to communicate with them.

[0024] Physically, the information processing device 10 is configured as a computer including a processor 101, memory 102, storage 103, communication device 104, input device 105, output device 106, and a bus connecting them. Each of these devices operates on power supplied from a battery (not shown). In the following description, the term "device" can be read as a circuit, device, unit, etc. The hardware configuration of the information processing device 10 may include one or more of the devices shown in Figure 2, or it may be configured with some devices omitted. Alternatively, multiple devices with different enclosures may be connected via communication to constitute the information processing device 10.

[0025] Each function in the information processing device 10 is realized by loading predetermined software (programs) onto hardware such as the processor 101 and memory 102, which allows the processor 101 to perform calculations, control communication by the communication device 104, and control at least one of the reading and writing of data in the memory 102 and storage 103.

[0026] The processor 101 controls the entire computer, for example, by running the operating system. The processor 101 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. Alternatively, a baseband signal processing unit or a call processing unit may be implemented by the processor 101.

[0027] The processor 101 reads programs (program code), software modules, data, etc., from at least one of the storage 103 and the communication device 104 into the memory 102 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described later. The functional blocks of the information processing device 10 are stored in the memory 102 and may be realized by control programs that run on the processor 101. Various processes may be executed by one processor 101, or they may be executed simultaneously or sequentially by two or more processors 101. The processor 101 may be implemented by one or more chips. The program may also be transmitted to the information processing device 10 via a telecommunications line.

[0028] Memory 102 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Memory 102 may also be called a register, cache, main memory, etc. Memory 102 can store executable programs (program code), software modules, etc., for carrying out the method according to this embodiment.

[0029] The storage 103 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The storage 103 may also be called an auxiliary storage device.

[0030] The communication device 104 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 104 enables communication with the first user terminal 20, the second user terminal 30, and the store terminal 40.

[0031] Each device, such as the processor 101 and memory 102, is connected by a bus for communicating information. The bus may be configured using a single bus, or different buses may be used for each device.

[0032] The information processing device 10 may include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and some or all of the functional blocks may be implemented by such hardware. For example, the processor 101 may be implemented using at least one of these hardware components.

[0033] Next, the hardware configuration of the first user terminal 20 will be described. The hardware configuration of the second user terminal 30 is the same as that of the first user terminal 20, so its description will be omitted. The first user terminal 20 is a computer such as a smartphone, mobile phone, tablet, or wearable device. Physically, the first user terminal 20 is configured as a computer device including a processor 201, memory 202, storage 203, communication device 204, input device 205, output device 206, and a bus connecting these. The processor 201, memory 202, and storage 203 are hardware similar to the processor 101, memory 102, and storage 103 of the information processing device 10.

[0034] The communication device 204 may include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antennas, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 204. The transmitting and receiving section may be physically or logically separated into a transmitting section and a receiving section.

[0035] The input device 205 is an input device that accepts input from an external source (e.g., a key, microphone, switch, button, sensor, etc.). The output device 206 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 205 and the output device 206 may be configured as an integrated unit (e.g., a touchscreen).

[0036] Next, the hardware configuration of the store terminal 40 will be described. The store terminal 40 is, for example, a POS terminal. Physically, the store terminal 40 is configured as a computer device including a processor 401, memory 402, storage 403, communication device 404, input device 405, output device 406, reader 407, and a bus connecting these. The processor 401, memory 402, and storage 403 are hardware similar to the processor 101, memory 102, and storage 103 of the information processing device 10.

[0037] The communication device 404 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, network controller, network card, communication module, etc. The communication device 404 enables communication with the information processing device 10.

[0038] The input device 405 is an input device that accepts input from an external source (e.g., a key, microphone, switch, button, sensor, touch panel, etc.). The output device 206 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 405 and the output device 406 may be configured as an integrated unit (e.g., a touchscreen).

[0039] The reading device 407 is, for example, a barcode reader and camera, which reads barcodes attached to products purchased by the user or payment codes displayed on the user's terminal.

[0040] [Functional configuration of the information processing device 10] Figure 3 shows the functional configuration of the information processing device 10. The information processing device 10 has a storage unit 12 and a control unit 13.

[0041] The storage unit 12 stores various types of data. For example, the storage unit 12 stores programs executed by the control unit 13. The storage unit 12 stores payment programs that cause the control unit 13 to function as a condition setting unit 131, an issuance request acquisition unit 132, a first determination unit 133, a token transmission unit 134, a payment information acquisition unit 135, a second determination unit 136, and a payment execution unit 137.

[0042] Furthermore, the storage unit 12 stores condition information that associates the second user ID with information indicating the issuance permission conditions for authorizing the issuance of a payment code as a predetermined condition, and information indicating the payment approval conditions for approving the payment. Figure 4 shows an example of condition information. As shown in Figure 4, the second user ID is associated with the first user ID of the first user who has set the issuance permission conditions and payment approval conditions, as well as the issuance permission conditions and payment approval conditions.

[0043] As shown in Figure 4, the issuance permission conditions include, for example, obtaining (receiving) a request for issuance of a payment code from the second user terminal 30 at a predetermined time (for example, between 4 PM and 6 PM), and the location of the second user terminal 30 at the time of obtaining the request for issuance of the payment code being within a predetermined range (for example, within shopping street A). Furthermore, the issuance permission conditions are not limited to those shown in Figure 4, and may also include, for example, that the number of payments made by the second user terminal 30 within a predetermined period (for example, one week) is no more than a predetermined number (for example, 10 times), or that the total amount of payments made by the second user terminal 30 within a predetermined period (for example, one week) is no more than a predetermined amount (for example, 10,000 yen).

[0044] Furthermore, payment approval conditions include, for example, obtaining information indicating permission to execute the payment from the first user terminal 20, the store type included in the payment information meeting pre-set conditions (for example, the store type being either a restaurant or a convenience store), and the payment amount included in the payment information being less than or equal to a pre-set predetermined amount (for example, the payment amount being 1,000 yen or less). Obtaining information indicating permission to execute the payment from the first user terminal 20 means obtaining approval from the first user when executing the payment. In order to obtain information indicating permission to execute the payment from the first user terminal 20, the information processing device 10 transmits at least one of the store type information or payment amount information included in the payment information to the first user terminal 20 before determining whether the payment approval conditions are met. This allows the first user to confirm whether they should authorize the payment by the second user terminal 30.

[0045] Furthermore, the issuance authorization conditions are not limited to those shown in Figure 4; they may also include conditions such as the account balance from which the payment amount will be withdrawn being above a certain level, or a predetermined amount of time having elapsed since the payment was made by the second user terminal 30. Additionally, the payment approval conditions may include the first user unconditionally authorizing the issuance of the payment code.

[0046] Furthermore, the issuance authorization conditions and settlement approval conditions may be a combination of the multiple conditions described above.

[0047] The control unit 13 functions as a condition setting unit 131, an issuance request acquisition unit 132, a first determination unit 133, a token transmission unit 134, a settlement information acquisition unit 135, a second determination unit 136, and a settlement execution unit 137 by executing the settlement program stored in the storage unit 12. Details of the operation of each part of the control unit 13 will be described later.

[0048] [Functional configuration of the first user terminal 20] Figure 5 shows the functional configuration of the first user terminal 20. The first user terminal 20 has a storage unit 24 and a control unit 25. The control unit 25 has an operation reception unit 251, a setting request transmission unit 252, a display control unit 253 and an information acquisition unit 254.

[0049] The memory unit 24 stores the program that the control unit 25 will execute.

[0050] The control unit 25 functions as an operation reception unit 251, a setting request transmission unit 252, a display control unit 253, and an information acquisition unit 254 by executing a program stored in the storage unit 24.

[0051] The operation reception unit 251 identifies the operation content of the first user based on signals input from, for example, a touch panel provided on the surface of a display unit (not shown). If the identified operation content is an operation for setting issuance permission conditions and settlement approval conditions, the operation reception unit 251 notifies the setting request transmission unit 252 of the identified operation content.

[0052] When the operation reception unit 251 receives an operation to set the issuance permission conditions and payment approval conditions, the setting request transmission unit 252 displays a setting screen for setting the issuance permission conditions and payment approval conditions on the display unit, and accepts input of a second user ID to identify the second user, the issuance permission conditions, and the payment approval conditions.

[0053] The setting request transmission unit 252 may also accept input of second user identification information instead of a second user ID as information for identifying the second user. The second user identification information may include, for example, the second user's personal information such as name, gender, address, and date of birth, the telephone number corresponding to the second user terminal 30, or a combination thereof.

[0054] The configuration request transmission unit 252 transmits a configuration request to the information processing device 10, which includes the first user ID of the first user, the second user ID (or second user identification information), the issuance permission conditions, and the payment approval conditions.

[0055] When the display control unit 253 receives information regarding a code payment made by a second user from the information processing device 10, it displays the information on the display unit.

[0056] The information acquisition unit 254 receives information from the information processing device 10 regarding code payments made by a second user. This information regarding code payments made by a second user may include, for example, information indicating that a payment code could not be issued to the second user, information indicating that a code payment was made by the second user, error information indicating that the code payment by the second user failed, or payment information at the second user's store. The payment information includes information on the type of store, a store ID that identifies the store, or information on the payment amount.

[0057] Figure 6 shows an example of a settings screen for setting issuance permission conditions and payment approval conditions. Figure 6(a) shows an example of the issuance permission conditions setting screen, and Figure 6(b) shows an example of the payment approval conditions setting screen.

[0058] First, let's explain the screen for setting the issuance permission conditions using Figure 6(a). Item 601 specifies the time period during which requests for payment code issuance from the second user terminal 30 can be accepted. In the example in Figure 6(a), 16:00 to 18:00 is specified, meaning that requests for payment code issuance from the second user will only be accepted between 16:00 and 18:00. Therefore, even if the second user tries to issue a payment code at 19:00, for example, the payment code will not be issued. Note that in addition to specifying the time, you can also specify the day of the week, such as weekdays or holidays, to specify the date and time.

[0059] Item field 602 specifies the predetermined range (location for requesting payment code issuance) in which the second user terminal 30 should be located when a request for payment code is received. In the example in Figure 6(a), this predetermined range can be determined by specifying the range from a map. Alternatively, it can be determined by directly entering an address.

[0060] Item field 603 specifies the maximum number of payments that can be made by the second user terminal 30 within a predetermined period. In the example in Figure 6(a), the predetermined period is set to one week, and the maximum number of payments per week is set to 10.

[0061] Item field 604 specifies the maximum total amount of payments made by the second user terminal 30 within a predetermined period. In the example in Figure 6(a), the predetermined period is set to one week, and the maximum total amount of payments for that week is set to 10,000 yen.

[0062] The first user can proceed to the payment authorization conditions setting screen by tapping button 605 labeled "Next". Note that the issuance permission conditions are not limited to those shown in Figure 6(a); a password or secret word may also be specified. If the second user loses the second user terminal 30, another user who finds the lost second user terminal 30 will be prompted to enter the specified password or secret word when requesting the issuance of a payment code, thereby preventing other users from issuing payment codes without authorization.

[0063] Item 606 specifies whether permission from the parent (the first user) is required to execute the payment. In the example in Figure 6(a), "Required" is specified, indicating that permission from the parent is required to execute the payment.

[0064] Next, we will explain the payment approval condition setting screen using Figure 6(b). In item 607, you specify the store type included in the payment information. In the example in Figure 6(b), a list of store types has been created in advance, and you can select the store type for which you want to approve the payment from this list.

[0065] Item field 608 specifies the maximum payment amount included in the payment information. In the example in Figure 6(b), 1,000 yen is specified as the maximum amount.

[0066] The first user can return to the issuance permission conditions setting screen by tapping button 609 labeled "Back," and modify the issuance permission conditions. The first user can also finalize the issuance permission conditions and payment approval conditions by tapping the button labeled "Confirm."

[0067] [Functional configuration of the second user terminal 30] Figure 7 shows the functional configuration of the second user terminal 30. The second user terminal 30 has a storage unit 34 and a control unit 35. The control unit 35 has an operation reception unit 351, an issuance request transmission unit 325, a token acquisition unit 353 and a code generation unit 354.

[0068] The memory unit 34 stores the program to be executed by the control unit 35. The memory unit 34 also stores the payment token received from the information processing device 10, and the payment code generated based on the payment token.

[0069] The control unit 35 functions as an operation reception unit 351, a issuance request transmission unit 352, a token acquisition unit 353, and a code generation unit 354 by executing a program stored in the storage unit 34.

[0070] The operation reception unit 351 identifies the operation content of the second user based on signals input from, for example, a touch panel provided on the surface of a display unit (not shown). If the identified operation content is an operation to display a payment code on the second user terminal 30, the operation reception unit 351 notifies the issuance request transmission unit 352 of the operation content. The issuance request transmission unit 352 identifies the location of the second user terminal 30 when the operation reception unit 351 has received an operation to display a payment code on the second user terminal 30. The issuance request transmission unit 352 then transmits the second user ID, terminal location information indicating the location of the second user terminal 30, and a request for issuance of a payment code to the information processing device 10. Here, the transmission of terminal location information is not always necessary. Terminal location information is used when the location for the payment code issuance request is specified as an issuance permission condition.

[0071] The token acquisition unit 353 acquires the payment token transmitted from the information processing device 10.

[0072] The code generation unit 354 generates a payment code based on the acquired payment token. The code generation unit 354 displays the generated payment code on the display unit.

[0073] [Functional Configuration of Store Terminal 40] Figure 8 shows the functional configuration of the store terminal 40. The store terminal 40 has a storage unit 45 and a control unit 46.

[0074] The memory unit 45 stores the program that the control unit 46 will execute. The memory unit 45 also stores a product database that associates product IDs with product prices.

[0075] The control unit 46 functions as a payment information generation unit 461, a token acquisition unit 462, and a payment information transmission unit 463 by executing a program stored in the storage unit 45.

[0076] The payment information generation unit 461 identifies the products to be paid for and generates payment information. Specifically, the payment information generation unit 461 identifies the products to be paid for by obtaining the product ID entered by the store clerk or the product ID read by the reader 407 from the barcode attached to the product. The payment information generation unit 461 refers to the product DB stored in the storage unit 45 and identifies the price of the product associated with the obtained product ID. The payment information generation unit 461 aggregates the prices of one or more products identified from the product ID. When the payment information generation unit 461 receives the payment operation from the store clerk, it determines the aggregated product prices as the payment amount. The payment information generation unit 461 generates payment information that includes the payment amount, store type information indicating the type of store, and store ID identifying the store.

[0077] The token acquisition unit 462 acquires a payment token, which is information extracted from the payment code, when the reader 407 reads the payment code displayed on the second user terminal 30.

[0078] The payment information transmission unit 463 transmits the payment information generated by the payment information generation unit 461 and the payment token acquired by the token acquisition unit 462 to the information processing device 10.

[0079] [Operation of each part of the control unit 13] Returning to Figure 3, the operation of each part of the control unit 13 of the information processing device 10 will be explained. The condition setting unit 131 sets the issuance permission conditions and payment approval conditions corresponding to the second user based on the setting request for issuance permission conditions and payment approval conditions corresponding to the second user transmitted from the first user terminal 20.

[0080] The condition setting unit 131 receives a setting request from the first user terminal 20, which includes the first user ID, the second user ID, the issuance permission conditions, and the payment approval conditions.

[0081] When the setting request transmission unit 252 of the first user terminal 20 transmits second user identification information instead of a second user ID, the condition setting unit 131 identifies the second user ID based on the received second user identification information. In this case, the storage unit 12 stores user information that associates the user IDs of multiple users who can use the code payment service with the user identification information of each user. The condition setting unit 131 refers to this user information and identifies the second user ID associated with the second user identification information included in the setting request. Note that the code payment service may be operated by, for example, a telecommunications carrier that provides a mobile phone network, and users who use services related to mobile phones may be able to use the code payment service. In other words, the user information for the code payment service may be the same as the user information for services related to mobile phones.

[0082] The condition setting unit 131 determines whether the first user corresponding to the first user ID included in the received setting request and the second user corresponding to the second user ID are associated due to a predetermined relationship. In this embodiment, the predetermined relationship is a parent-child relationship, but the predetermined relationship may also be, for example, that the first user and the second user are family members, or that the first user and the second user are in a superior-subordinate relationship. The user information stored in the storage unit 12 associates the user ID of a user with the user ID of other users who have a parent-child relationship, family relationship, or superior-subordinate relationship with that user. Therefore, the condition setting unit 131 determines whether the first user and the second user are associated with each other due to a predetermined relationship by referring to the user information. Note that if the first user and the second user do not have a predetermined relationship, the first user may choose the user for whom they want to set conditions as the second user and not perform the above determination.

[0083] When the condition setting unit 131 determines that the first user and the second user have a parent-child relationship, it sets the issuance permission conditions and payment approval conditions corresponding to the second user based on the received setting request. The condition setting unit 131 associates the first user ID, the second user ID, the issuance permission conditions, and the payment approval conditions and stores them as condition information in the storage unit 12. As a result, the issuance permission conditions and payment approval conditions corresponding to the second user are set.

[0084] The condition setting unit 131 sets, for example, the issuance permission conditions (first predetermined conditions) corresponding to the second user if: (i) the request for issuance of a payment code from the second user terminal 30 is obtained at a predetermined date and time; (ii) the location of the second user terminal 30 at the time the request for issuance of a payment code is obtained is within a predetermined range; (iii) the number of payments made by the second user terminal 30 within a predetermined period is less than or equal to a predetermined number; (iv) the total amount of payments made by the second user terminal 30 within a predetermined period is less than or equal to a predetermined amount; or (v) a combination of these conditions.

[0085] Furthermore, the condition setting unit 131 sets, for example, (i) information indicating permission to execute payment from the first user terminal 20, (ii) information indicating permission to execute payment from the first user terminal 20 of the first user who has confirmed at least one of the store type information or payment amount information included in the payment information, (iii) if the store type included in the payment information satisfies a pre-set condition, (iv) if the payment amount included in the payment information is less than or equal to a pre-set predetermined amount, or (v) a combination of these as payment approval conditions (second predetermined conditions) for the second user. It is also possible to set issuance permission conditions corresponding to the second user so that the issuance of a payment code to the second user is always prohibited or always permitted. It is also possible to set payment approval conditions corresponding to the second user so that the approval of payment to the second user is always prohibited or always permitted.

[0086] The issuance request acquisition unit 132 acquires (receives) the second user ID, terminal location information, and a request for the issuance of a payment code for the second user to make a payment at the store from the second user terminal 30.

[0087] When the issuance request acquisition unit 132 acquires a payment code issuance request, the first determination unit 133 refers to the condition information stored in the storage unit 12 and determines whether the issuance permission conditions corresponding to the second user, which were set by the first user associated with the second user corresponding to the received second user ID, are met.

[0088] For example, if the issuance permission condition associated with the second user ID in the condition information is to receive a payment code issuance request from the second user terminal 30 at a predetermined date and time, the first determination unit 133 determines whether or not the issuance permission condition is met based on the time the payment code issuance request is received.

[0089] Furthermore, if the issuance permission condition associated with the second user ID in the condition information is that the location of the second user terminal 30 is within a predetermined range, the first determination unit 133 determines whether or not the issuance permission condition is met based on the terminal location information received from the issuance request acquisition unit 132.

[0090] Furthermore, if the first determination unit 133 determines that the issuance permission conditions are not met, it notifies the second user terminal 30 of information indicating that it cannot issue a payment code. Alternatively, the first determination unit 133 may also notify the first user terminal 20 of information indicating that it cannot issue a payment code. In this case, the first determination unit 133 refers to the condition information stored in the storage unit 12, identifies the first user ID associated with the second user ID, and notifies the first user terminal 20 corresponding to that first user ID of information indicating that it cannot issue a payment code.

[0091] The token transmission unit 134 transmits a payment token to the second user terminal 30 based on the determination result of the issuance permission conditions in the first determination unit 133. Specifically, if the token transmission unit 134 determines in the first determination unit 133 that the issuance permission conditions are met, it generates a payment token for generating a payment code. Once the token transmission unit 134 generates a payment token, it associates the second user ID obtained by the issuance request acquisition unit 132 with the generated payment token and stores it in the storage unit 12. The token transmission unit 134 transmits the generated payment token to the second user terminal 30 that sent the payment code issuance request.

[0092] The payment information acquisition unit 135 receives payment information for the second user's store, including store type information, store ID, and payment amount at the second user's store, as well as a payment token, from the store terminal 40 which reads the payment code displayed by the second user terminal 30 based on the payment token transmitted by the token transmission unit 134.

[0093] When the payment information acquisition unit 135 receives payment information and a payment token, the second determination unit 136 determines whether the payment authorization conditions corresponding to the second user, which were set by the first user associated with the second user, are met. Specifically, when the payment information acquisition unit 135 receives payment information and a payment token, the second determination unit 136 determines whether a payment token matching the received payment token is stored in the storage unit 12. If the second determination unit 136 determines that a payment token matching the received payment token is stored in the storage unit 12, it identifies the second user ID stored in the storage unit 12 in association with that payment token. Then, the second determination unit 136 refers to the condition information stored in the storage unit 12 and determines whether the payment authorization conditions corresponding to the second user, which were set by the first user associated with the second user corresponding to the identified second user ID, are met.

[0094] For example, if the payment authorization condition associated with the second user ID in the condition information is to obtain information indicating permission to execute a payment from the first user terminal 20, the second determination unit 136 determines whether or not the payment authorization condition is met based on the information indicating permission to execute a payment from the first user terminal 20. In this case, when the information transmission unit 138 obtains the payment information, it sends a notification to the first user terminal 20 to ask the first user whether or not to approve the payment. In addition to the notification, the information transmission unit 138 may also transmit at least one of the store type information or payment amount information included in the payment information.

[0095] Furthermore, the second determination unit 136 determines whether the payment approval condition associated with the second user ID in the condition information is met, based on the store type information or payment amount information acquired by the payment information acquisition unit 135, if at least one of the following conditions is met: the store type included in the payment information satisfies a predetermined condition, or the payment amount included in the payment information is less than or equal to a predetermined amount.

[0096] Furthermore, if the second determination unit 136 determines that the payment approval conditions are not met, it notifies the first user terminal 20 of information indicating that payment will not be made. In this case, the second determination unit 136 refers to the condition information stored in the storage unit 12, identifies the first user ID associated with the second user ID, and notifies the first user terminal 20 corresponding to that first user ID of information indicating that payment will not be made. The information indicating that payment will not be made is, for example, information indicating that payment will not be made because the payment approval conditions are not met. In this way, the first user can understand that the second user was unable to purchase goods using code payment. Note that the second determination unit 136 notified the first user terminal 20 of information indicating that payment will not be made, but it is not limited to this, and may also notify the second user terminal 30 of information indicating that payment will not be made.

[0097] When the second determination unit 136 determines that the payment approval conditions are met, the payment execution unit 137 executes the payment process based on the payment information. Specifically, the payment execution unit 137 debits the payment amount included in the received payment information from the account of the first user corresponding to the first user ID associated with the second user ID identified by the second determination unit 136. The payment execution unit 137 also deposits the payment amount included in the received payment information into the account of the store identified by the store ID included in the received payment information.

[0098] When a payment is made based on the payment information, the payment execution unit 137 notifies the second user terminal 30 and the store terminal 40 of payment completion information indicating that the payment has been completed. The payment completion information may include information such as the date and time of payment completion, the name of the purchased product, the purchase amount, and store information. In addition, when a payment is made based on the payment information, the payment execution unit 137 notifies the first user terminal 20 of payment execution information indicating that the payment has been made by the second user. The payment execution information may include information such as the date and time of payment completion, the name of the purchased product, the purchase amount, and store information. The payment execution unit 137 may also notify the first user terminal 20 of payment completion information instead of payment execution information. In this way, the first user can understand what products the second user purchased, when, and where using code payment. Furthermore, by storing the payment execution information in the storage unit 24 of the first user terminal 20, the first user may be able to check the purchase history of the second user's products.

[0099] When the payment information acquisition unit 135 acquires payment information, the information transmission unit 138 sends a notification to the first user terminal 20 to ask the first user whether or not to approve the payment. In addition to the notification, the information transmission unit 138 also transmits at least one of the store type information or payment amount information included in the payment information.

[0100] [Operation Flow] Figures 9 and 10 illustrate the operation of the payment system S. Figure 10 is a diagram illustrating the operation of the payment system S, following Figure 9. In step S1, the first user who owns the first user terminal 20 performs the operation to set the issuance permission conditions and the payment approval conditions.

[0101] In step S2, the setting request transmission unit 252 transmits a setting request to the information processing device 10, which includes the first user ID of the first user, the second user ID, the issuance permission conditions, and the payment approval conditions. In step S2, the setting request transmission unit 252 may transmit second user identification information to the information processing device 10 instead of the second user ID.

[0102] In step S3, when the condition setting unit 131 of the information processing device 10 receives a request to set the issuance permission conditions and payment approval conditions from the first user terminal 20, it associates the second user ID, the first user ID included in the received setting request, the issuance permission conditions, and the payment approval conditions and stores them as condition information in the storage unit 12, thereby setting the issuance permission conditions and payment approval conditions corresponding to the second user. If, in step S2, the setting request transmission unit 252 transmits second user identification information to the information processing device 10 instead of the second user ID, then in step S3, the condition setting unit 131 identifies the second user ID based on the received second user identification information. The above describes the setting of the issuance permission conditions and payment approval conditions corresponding to the second user by the first user.

[0103] In step S4, the second user uses the second user terminal 30 at the store to display the payment code.

[0104] In step S5, the issuance request transmission unit 352 of the second user terminal 30 transmits a request for issuance of a payment code and the second user ID to the information processing device 10.

[0105] In step S6, when the issuance request acquisition unit 132 of the information processing device 10 acquires a payment code issuance request and a second user ID from the second user terminal 30, the first determination unit 133 determines whether the issuance permission conditions set by the first user associated with the second user corresponding to the received second user ID are met. If the first determination unit 133 determines that the issuance permission conditions are met, the flow proceeds to step S7. When it is determined that the issuance permission conditions are met, the first determination unit 133 may notify the first user terminal 20 of information (issuance permission information) indicating that the payment code can be issued because the issuance permission conditions have been met. If the first determination unit 133 determines that the issuance permission conditions are not met, it notifies the second user terminal 30 of information (issuance NG information) indicating that the payment code cannot be issued because the issuance permission conditions are not met. Furthermore, if the first determination unit 133 determines that the issuance permission conditions are not met, it may notify the first user terminal 20 of information indicating that a payment code cannot be issued because the issuance permission conditions are not met (issuance NG information). The first user terminal 20 may also store the notified issuance permission information and issuance NG information in the storage unit 24. This allows the first user to check the history of permission / denial of payment code issuance requests, as well as the transmission history of payment code issuance requests and the factors for success / failure.

[0106] If the first determination unit 133 determines in step S6 that the issuance permission conditions are met, then in step S7, the token transmission unit 134 generates a payment token for generating a payment code.

[0107] In step S8, the token transmission unit 134 associates the received second user ID with the generated payment token and stores it in the storage unit 12.

[0108] In step S9, the token transmission unit 134 transmits the generated payment token to the second user terminal 30 that sent the request for issuance of the payment code.

[0109] In step S10, the code generation unit 354 of the second user terminal 30 generates a payment code based on the payment token acquired (received) by the token acquisition unit 353, and displays the generated payment code on the display unit of the second user terminal 30.

[0110] In step S11, when the second user presents the payment code displayed on the second user terminal 30 at the store, the reader unit 42 of the store terminal 40 reads the payment code, and the token acquisition unit 462 acquires the payment token contained in the payment code.

[0111] In step S12, the payment information generation unit 461 identifies the price of the product based on the product ID entered by the store clerk or the product ID read by the reading unit 42 from the barcode attached to the product, and calculates the payment amount.

[0112] In step S13, the payment information transmission unit 463 transmits the calculated payment amount, the store type, the store ID, and the acquired payment token to the information processing device 10.

[0113] In step S14, when the payment information acquisition unit 135 of the information processing device 10 receives payment information and a payment token from the store terminal 40, the second determination unit 136 identifies the second user ID associated with the payment token if the received payment token matches the payment token stored in the storage unit 12.

[0114] In step S15, the second determination unit 136 determines whether the payment approval conditions corresponding to the second user, which were set by the first user associated with the second user corresponding to the identified second user ID, are met. If the second determination unit 136 determines that the payment approval conditions are met, the flow proceeds to step S16. When it is determined that the payment approval conditions are met, the second determination unit 136 may notify the first user terminal 20 of information indicating that payment will be made because the payment approval conditions have been met (approval permission information). If the second determination unit 136 determines that the payment approval conditions are not met, it notifies the first user terminal 20 of information indicating that payment will not be made because the payment approval conditions are not met (approval NG information). Furthermore, if the second determination unit 136 determines that the payment approval conditions are not met, it may notify the second user terminal 30 of information indicating that payment will not be made because the payment approval conditions are not met (approval NG information). Furthermore, the first user terminal 20 may store the notified approval / permission information and approval / rejection information in the storage unit 24. This allows the first user to check the history of payment approval / rejection, and also to check the factors that led to the success or failure of payment approval.

[0115] In step S16, the settlement execution unit 137 executes the settlement process. Specifically, the settlement execution unit 137 debits the settlement amount included in the settlement information from the account of the first user corresponding to the first user ID associated with the second user ID identified by the second determination unit 136. The settlement execution unit 137 also deposits the settlement amount included in the received settlement information into the account of the store identified by the store ID included in the received settlement information.

[0116] In step S17, the settlement execution unit 137 notifies the second user terminal 30 of settlement completion information indicating that the settlement has been completed.

[0117] In step S18, the payment execution unit 137 notifies the first user terminal 20 of payment execution information indicating that a payment has been made by the second user.

[0118] As described above, the payment system S can allow different users to use the payment function securely by performing different approval checks at the time of code issuance and at the time of payment approval. Furthermore, by performing two checks using different issuance permission conditions and payment approval conditions, the burden of the check process at the time of payment can be reduced, the check process can be sped up compared to when the check is performed only at the time of payment, and checkout lines can be reduced.

[0119] (Second Embodiment) In the first embodiment, if at least one of the issuance permission conditions or the payment approval conditions was not met, the second user could not make a code payment. In the first embodiment, routine payment actions such as a middle school student buying lunch or bread at the school store during lunchtime on a weekday can be safely performed. However, in the first embodiment, there are cases where the second user (the child) cannot make a payment when they want to perform a payment action that is different from the usual. For example, if an irregular plan arises, such as suddenly deciding to go out to eat at a restaurant with friends after school or after cram school, and the issuance permission conditions are not met because there is a limit set on the total amount of payments for the week, and furthermore, the payment approval conditions are not met because the restaurant is not of the specified store type, the second user (the child) will not be able to pay for the meal with a code payment, and if they do not have any other payment method, they will not be able to go out to eat with their friends.

[0120] Therefore, in the second embodiment, a payment system Sa capable of issuing a special payment code to a second user terminal 30 that can be used even if at least one of the issuance permission conditions or the payment approval conditions is not met will be described. In the following, a payment system Sa capable of issuing a special payment code to a second user terminal 30 that can be used even if both the issuance permission conditions and the payment approval conditions are not met will be described as an example.

[0121] The payment system Sa according to the second embodiment, like the payment system S according to the first embodiment, comprises an information processing device 10a, a first user terminal 20a, a second user terminal 30, and a store terminal 40. The configurations of the second user terminal 30 and the store terminal 40 are the same as in the first embodiment, so their descriptions are omitted.

[0122] Figure 11 shows the functional configuration of the first user terminal 20a according to this embodiment. The first user terminal 20a according to this embodiment has a generation request transmission unit 255 in addition to the functional configuration of the first user terminal 20 according to the first embodiment.

[0123] The generation request transmission unit 255 transmits a request to the information processing device 10a to generate a second payment code, which is a special payment code that can be used even if at least one of the issuance permission conditions or payment approval conditions is not met. The first user operates the first user terminal 20a to issue the second payment code to the second user and transmits a request to the information processing device 10a to generate the second payment code.

[0124] Specifically, the operation reception unit 251 notifies the generation request transmission unit 255 of the identified operation details when the operation performed by the first user is a specific operation for requesting the generation of a second payment code.

[0125] When the operation reception unit 251 receives an operation request to generate a second payment code, the generation request transmission unit 255 displays a setting screen for requesting the generation of a second payment code on the display unit and accepts input of a second user ID to identify the second user and the usage conditions for the second payment code. The setting of the usage conditions for the second payment code includes specifying whether or not to check the issuance permission conditions and whether or not to check the payment approval conditions. The setting of the usage conditions for the second payment code also includes specifying, for example, the number of payments and the payment amount that can be settled with the second payment code. For example, the first user can set the number of payments to 1 and the payment amount to 5,000 yen, or set the number of payments to 3 and the payment amount for each payment to 1,000 yen, or set the number of payments to 2 and the total payment amount to 3,000 yen (without specifying the payment amount for each payment). Figure 12 shows an example of a setting screen for requesting the generation of a second payment code. Note that the usage conditions do not have to be set.

[0126] The generation request transmission unit 255 may also accept second user identification information instead of a second user ID as information for identifying the second user. The second user identification information may include, for example, personal information such as the second user's name, gender, address, and date of birth, a telephone number corresponding to the second user terminal 30, or a combination thereof.

[0127] The generation request transmission unit 255 transmits a request to the information processing device 10a to generate a second payment code, which includes the first user ID of the first user, the second user ID (or second user identification information), and the usage conditions for the second payment code.

[0128] Alternatively, a screen for setting the usage conditions for the second payment code, as shown in Figure 12, may be displayed on the second user's terminal 30, allowing the second user to set the desired usage conditions for the second payment code. In this case, the first user may be notified that the second user wants to issue such a second payment code, and a screen may be displayed on the first user's terminal 20 requesting that the first user only approve or deny issuing a second payment code that meets the usage conditions. The first user's terminal 20 may also be configured to display an editing screen that allows the second user to change the usage conditions set by the second user. When the second user performs an approval operation (for example, by tapping a button labeled "Approve"), a request to generate a second payment code may be sent to the information processing device 10.

[0129] Figure 13 shows the functional configuration of the information processing device 10a according to this embodiment. The information processing device 10a according to this embodiment has a generation request acquisition unit 139 in addition to the functional configuration of the information processing device 10 according to the first embodiment.

[0130] The generation request acquisition unit 139 acquires a generation request from the first user terminal 20a for a second payment code, which is a special payment code that can be used even if at least one of the issuance permission conditions or payment approval conditions is not met. Specifically, the generation request acquisition unit 139 acquires (receives) a generation request from the first user terminal 20a that includes the first user ID, the second user ID, and the usage conditions for the second payment code.

[0131] When the generation request acquisition unit 139 acquires a generation request for the second payment code, the token transmission unit 134, if the second payment code is usable even if the issuance permission conditions are not met, generates a second payment token for generating the second payment code without undergoing a determination of the issuance permission conditions by the first determination unit 133, and transmits the generated second payment token to the second user terminal 30 of the second user corresponding to the second user ID. Alternatively, the token transmission unit 134 may transmit a second payment token for issuing the second payment code to the second user terminal 30 when the issuance request acquisition unit 132 acquires an issuance request for the second payment code from the second user terminal 30.

[0132] If the second payment code is usable even if the payment approval conditions are not met, the payment execution unit 137 executes the payment process based on the payment information received from the store terminal 400 without undergoing a determination of the payment approval conditions by the second determination unit 136. Specifically, the payment execution unit 137 executes a process to debit the payment amount included in the received payment information from the account of the first user corresponding to the first user ID associated with the second user ID. The payment execution unit 137 also executes a process to deposit the payment amount included in the received payment information into the account of the store identified by the store ID included in the received payment information.

[0133] When a payment is made based on the payment information, the payment execution unit 137 notifies the second user terminal 30 and the store terminal 40 of payment completion information indicating that the payment has been completed. In addition, when a payment is made based on the payment information, the payment execution unit 137 notifies the first user terminal 20 of payment execution information indicating that the payment has been made by the second user. The payment execution unit 137 may also notify the first user terminal 20 of payment completion information instead of payment execution information. In this way, the first user can find out what products the second user purchased, when and where, etc., using code payment with the second payment code.

[0134] [Other embodiments] Although the payment system of the present invention has been described above with reference to each embodiment, the payment system of the present invention is not limited to the above embodiments. Various modifications to the configuration and details of the present invention can be made, as can be understood by those skilled in the art within the technical scope of the present invention. Furthermore, any system or device that combines the separate features included in each embodiment is also within the technical scope of the present invention.

[0135] In the embodiments described above, a configuration in which a second user receives a payment code from one first user has been explained. However, a second user may receive payment codes from multiple first users. For example, a second user who is a child can receive payment codes from both their father and mother, who are both first users. In this case, the second user only needs to first select from which of the multiple first users they want to receive the payment code from. To facilitate the second user's selection from multiple first users, it is preferable to make each of the multiple first users identifiable by assigning them a name or nickname, or associating them with an image or avatar.

[0136] Furthermore, although the above embodiments were described using examples where the first user is the parent and the second user is the child, the first user may be the administrator of a group such as a corporation, and the second user may be a member of that group. In this case, the first user can check the payment code issuance permission history, payment approval history, usage history, etc., for each or all of the multiple second users.

[0137] Furthermore, in each of the above embodiments, an example was described in which the information processing device 10 issues a payment code for withdrawing the payment amount from one account managed by the first user to a second user terminal 30 used by the second user associated with the first user, and executes the payment of the purchase amount. However, the first user may manage multiple accounts, and the first user may be able to manage the linking of multiple accounts to the second user. Specifically, the first user can specify the account to link to the second user (i.e., the account linked to the payment code) from among the multiple accounts that they manage. For example, the first user can specify a points account or an electronic money account as the account to link to the second user, and allow the second user to use the payment method using the payment code according to each of the above embodiments within the limits of the accumulated points or charged electronic money.

[0138] The following additional notes are provided regarding the embodiments described above. [Note 1] The information processing device described in Appendix 1 is an information processing device that issues a settlement code for withdrawing a settlement amount from an account managed by the first user to a second user terminal used by the second user associated with the first user, An issuance request acquisition unit obtains a request from the second user terminal to issue the payment code for the second user to make a payment at the store, A first determination unit that determines whether or not a first predetermined condition corresponding to the second user, set by the first user, is met, When the first determination unit determines that the first predetermined condition is met, a token transmission unit transmits a payment token for generating the payment code to the second user terminal, A payment information acquisition unit acquires the payment token and the payment information of the second user at the store from a store terminal that reads the payment code displayed by the second user terminal based on the payment token, A second determination unit that determines whether a second predetermined condition, which is different from the first predetermined condition, is met, which is set by the first user and corresponds to the second user, When the second determination unit determines that the second predetermined condition is met, a payment execution unit executes a payment based on the payment information received from the store terminal, An information processing device having

[0139] This configuration allows different users to use the payment function securely by performing different approval checks at the time of code issuance and payment authorization. Furthermore, by performing two checks using two different predetermined conditions, the burden of the check process at the time of payment is reduced, the check process is faster compared to when the check is performed only at the time of payment, and checkout lines are reduced.

[0140] [Note 2] In the information processing device described in Appendix 1, The first determination unit, (i) If the request for issuance of the payment code from the second user terminal was obtained at a predetermined date and time, (ii) When the location of the second user terminal is within a predetermined range at the time of obtaining the request for issuance of the payment code, (iii) If the number of payments made by the second user terminal within the specified period is less than or equal to the specified number, (iv) If the total amount of payments made by the second user terminal within the specified period is less than or equal to the specified amount, The first predetermined condition is determined to be satisfied in at least one of the following cases.

[0141] This configuration allows the above case to be set as the first predetermined condition, enabling another user to use the payment function in a secure manner.

[0142] [Note 3] In the information processing device described in Appendix 1 or 2, The second determination unit determines that the second predetermined condition is met when it obtains information indicating permission to execute the payment from the first user terminal used by the first user.

[0143] This configuration requires approval from the first user to authorize the payment process, thus allowing other users to use the payment function securely.

[0144] [Note 4] In the information processing device described in Appendix 1 or 2, The information processing device transmits at least one of the store type information or payment amount information included in the payment information to the first user terminal used by the first user. The second determination unit determines that the second predetermined condition is met when it obtains information from the first user terminal indicating permission to execute the payment.

[0145] This configuration requires approval from a first user who has verified at least one piece of information included in the payment information—either the store type or the payment amount—before authorization to execute a payment, thus allowing other users to use the payment function securely.

[0146] [Note 5] In the information processing device described in Appendix 1 or 2, The second determination unit, (i) If the store type included in the payment information satisfies the conditions set in advance, (ii) If the payment amount included in the payment information is less than or equal to a predetermined amount, It is determined that the second predetermined condition is met in at least one of the cases.

[0147] This configuration requires that the transaction be of a specific store type and below a specified amount to be authorized for payment execution, thus allowing other users to use the payment function securely.

[0148] [Note 6] In any of the information processing devices described in Appendix 1 to 5, The system further includes a generation request acquisition unit that acquires a generation request for a second payment code, which can be used even if at least one of the first predetermined conditions or the second predetermined conditions is not met, from a first user terminal used by the first user. The token transmission unit, when the generation request acquisition unit acquires the generation request for the second payment code from the first user terminal, If the second payment code is usable even if the first predetermined condition is not met, the second payment token for generating the generated second payment code is transmitted to the second user terminal without the first determination unit determining the first predetermined condition. The settlement execution unit, if the second settlement code is usable even if the second predetermined condition is not met, Without undergoing determination of the second predetermined condition by the second determination unit, the payment is executed based on the payment information received from the store terminal.

[0149] This configuration allows a second payment code to be sent to a second user terminal that can be used even if the first predetermined condition is not met, or even if both the first and second predetermined conditions are not met, enabling the second user to make code payments even in irregular situations.

[0150] [Note 7] In the information processing device described in Appendix 6, When the token transmission unit obtains a request for issuance of the second payment code from the second user terminal, the token transmission unit transmits the second payment token for issuing the second payment code to the second user terminal.

[0151] This configuration allows a second user to obtain a second payment code at their own convenience, whenever needed.

[0152] [Note 8] The control method described in Appendix 8 is a control method for an information processing device that issues a settlement code for withdrawing a settlement amount from an account managed by the first user to a second user terminal used by the second user associated with the first user, A request for issuance step of obtaining a request for issuance of the payment code for the second user to make a payment at the store from the second user terminal, A first determination step of determining whether or not a first predetermined condition corresponding to the second user, set by the first user, is met, If the first determination step determines that the first predetermined condition is met, a token transmission step is performed to send a payment token for generating the payment code to the second user terminal. A payment information acquisition step involves obtaining the payment token and the payment information of the second user at the store from a store terminal that has read the payment code displayed by the second user terminal based on the payment token, A second determination step to determine whether a second predetermined condition, different from the first predetermined condition, is met, which is set by the first user and corresponds to the second user. If the second determination step determines that the second predetermined condition is met, a payment execution step is performed to execute a payment based on the payment information received from the store terminal, A control method having

[0153] This configuration produces the same effects as the information processing device described in Appendix 1.

[0154] [Note 9] The control program in Appendix 9 is a control program for an information processing device that issues a settlement code for withdrawing a settlement amount from an account managed by the first user to a second user terminal used by the second user associated with the first user, and is configured on a computer. A request for issuance step of obtaining a request for issuance of the payment code for the second user to make a payment at the store from the second user terminal, A first determination step of determining whether or not a first predetermined condition corresponding to the second user, set by the first user, is met, If the first determination step determines that the first predetermined condition is met, a token transmission step is performed to send a payment token for generating the payment code to the second user terminal. A payment information acquisition step involves obtaining the payment token and the payment information of the second user at the store from a store terminal that has read the payment code displayed by the second user terminal based on the payment token, A second determination step to determine whether a second predetermined condition, different from the first predetermined condition, is met, which is set by the first user and corresponds to the second user. If the second determination step determines that the second predetermined condition is met, a payment execution step is performed to execute a payment based on the payment information received from the store terminal, A control program that executes the command.

[0155] This configuration produces the same effects as the information processing device described in Appendix 1. [Explanation of symbols]

[0156] 10 Information Processing Devices 13 Control Unit 131 Condition Setting Section 132 Issuance Request Acquisition Department 133 1st Judgment Department 134 Token transmission unit 135 Payment Information Acquisition Department 136 Second Judgment Section 137 Payment Execution Department 138 Information Transmission Section 139 Generation request acquisition unit 20. First User Terminal 25 Control Unit 251 Operation Reception Section 252 Setting Request Transmission Unit 253 Display Control Unit 254 Information Acquisition Department 255 Generation request transmitter 30 Second User Terminal 35 Control Unit 351 Operation Reception Section 352 Issuance Request Transmission Unit 353 Token Acquisition Section 354 Code Generation Unit 40 store terminals 46 Control Unit 461 Payment Information Generation Department 462 Token Acquisition Section 463 Payment Information Transmission Department

Claims

1. An information processing device that issues a settlement code for withdrawing a settlement amount from an account managed by the first user to a second user terminal used by the second user associated with the first user, An issuance request acquisition unit obtains a request from the second user terminal to issue the payment code for the second user to make a payment at the store, A first determination unit that determines whether or not a first predetermined condition corresponding to the second user, set by the first user, is met, When the first determination unit determines that the first predetermined condition is met, a token transmission unit transmits a payment token for generating the payment code to the second user terminal, A payment information acquisition unit acquires the payment token and the payment information of the second user at the store from a store terminal that reads the payment code displayed by the second user terminal based on the payment token. A second determination unit that determines whether a second predetermined condition, which is different from the first predetermined condition, is met, which is set by the first user and corresponds to the second user, When the second determination unit determines that the second predetermined condition is met, a payment execution unit executes a payment based on the payment information received from the store terminal, An information processing device having

2. The first determination unit is, (i) When the request for issuance of the payment code from the second user terminal is obtained at a predetermined date and time, (ii) When the location of the second user terminal is within a predetermined range at the time of obtaining the request for issuance of the payment code, (iii) If the number of payments made by the second user terminal within a predetermined period is less than or equal to a predetermined number, (iv) If the total amount of payments made by the second user terminal within the specified period is less than or equal to the specified amount, The information processing apparatus according to claim 1, which determines that the first predetermined condition is satisfied in at least one of the following cases.

3. The information processing device according to claim 1, wherein the second determination unit determines that the second predetermined condition is met when it obtains information indicating permission to execute the payment from the first user terminal used by the first user.

4. The system further includes an information transmission unit that transmits at least one of the store type information or payment amount information included in the payment information acquired from the store terminal to a first user terminal used by the first user. The information processing device according to claim 1, wherein the second determination unit determines that the second predetermined condition is met when it obtains information from the first user terminal indicating permission to execute the payment.

5. The second determination unit described above is: (i) If the store type included in the payment information satisfies the conditions set in advance, (ii) If the payment amount included in the payment information is less than or equal to a predetermined amount, The information processing apparatus according to claim 1, which determines that the second predetermined condition is satisfied in at least one of the cases.

6. The system further includes a generation request acquisition unit that acquires a generation request for a second payment code that can be used even if at least one of the first predetermined conditions or the second predetermined conditions is not met, from a first user terminal used by the first user. The token transmission unit, when the generation request acquisition unit acquires the generation request for the second payment code from the first user terminal, If the second payment code is usable even if the first predetermined condition is not met, the second payment token for generating the generated second payment code is transmitted to the second user terminal without the first determination unit determining the first predetermined condition. The settlement execution unit, if the second settlement code is usable even if the second predetermined condition is not met, The information processing device according to claim 1, which performs the payment based on the payment information received from the store terminal without receiving a determination of the second predetermined condition by the second determination unit.

7. The information processing apparatus according to claim 6, wherein the token transmission unit transmits the second payment token for issuing the second payment code to the second user terminal when the issuance request acquisition unit acquires an issuance request for the second payment code from the second user terminal.

8. A control method for an information processing device that issues a payment code for withdrawing a payment amount from an account managed by the first user to a second user terminal used by the second user associated with the first user, The process includes an issuance request acquisition step, which involves obtaining a request from the second user terminal to issue the payment code for the second user to make a payment at the store, A first determination step of determining whether or not a first predetermined condition corresponding to the second user, set by the first user, is met, If the first determination step determines that the first predetermined condition is met, a token transmission step is performed to send a payment token for generating the payment code to the second user terminal. A payment information acquisition step involves obtaining the payment token and the payment information of the second user at the store from a store terminal that has read the payment code displayed by the second user terminal based on the payment token, A second determination step to determine whether a second predetermined condition, which is different from the first predetermined condition and corresponds to the second user, set by the first user, is met, If the second determination step determines that the second predetermined condition is met, a payment execution step is performed to execute a payment based on the payment information received from the store terminal, A control method having

9. A control program for an information processing device that issues a settlement code for withdrawing a settlement amount from an account managed by the first user to a second user terminal used by the second user associated with the first user, wherein the computer... The process includes an issuance request acquisition step, which involves obtaining a request from the second user terminal to issue the payment code for the second user to make a payment at the store, A first determination step of determining whether or not a first predetermined condition corresponding to the second user, set by the first user, is met, If the first determination step determines that the first predetermined condition is met, a token transmission step is performed to send a payment token for generating the payment code to the second user terminal. A payment information acquisition step involves obtaining the payment token and the payment information of the second user at the store from a store terminal that has read the payment code displayed by the second user terminal based on the payment token, A second determination step to determine whether a second predetermined condition, which is different from the first predetermined condition and corresponds to the second user, set by the first user, is met, If the second determination step determines that the second predetermined condition is met, a payment execution step is performed to execute a payment based on the payment information received from the store terminal, A control program that executes the command.

Images