Information processing system and information processing method

Abstract

To provide an information processing system and an information processing method for easily performing electronic settlement between two parties by using a sheet on which a code is printed.SOLUTION: In an information processing system 10 including a management server 12, a first user terminal 16 and a second user terminal 18, the first user terminal acquires a booklet ID and a sheet ID set in a two dimensional code printed on a sheet included in a booklet 22, and requests the management server to register payment information including a payment amount. The management server registers the deposit information in management information for managing the transfer of money between users using the sheet, and transmits the deposit information to the settlement server 20. The second user receives the sheet from the first user, acquires the book ID and the sheet ID set in the two dimensional code printed on the sheet by the second user terminal, transmits the settlement information to the settlement server, and instructs the execution of the settlement. The settlement server executes an electronic settlement process using the amount of payment included in the deposit information as a received amount.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing system and an information processing method, and more particularly to an information processing system and an information processing method that provide a new way of using electronic money, for example. [Background technology]

[0002] Nowadays, electronic money payments using payment codes such as QR codes (registered trademark) are being used in a variety of situations. For example, when buying beer from a beer vendor at a baseball stadium, the purchaser launches an electronic money payment application program installed on their own device, such as a smartphone, and uses the device's camera to read the payment code presented by the vendor. Alternatively, the purchaser may display the payment code on their device and then read the code on the vendor's device to complete the payment.

[0003] However, if the purchaser's seat is far from the aisle, there is a distance between them and the vendor in the aisle, and other spectators are sitting in between, so it is inconvenient for the purchaser to go to the vendor in person to make the payment. Therefore, it is common for the purchaser to hand their device to the spectator sitting next to them, and then pass the device through a bucket relay to the vendor in the aisle. After the vendor processes the payment, the purchaser's device is returned via the bucket relay along with the beer.

[0004] However, with this method, there is a risk that someone could drop and damage the terminal during the bucket relay. In some cases, both the terminal and the beer could be lost. Therefore, instead of passing the buyer's terminal around in a bucket relay, one option is to pass a piece of paper with a payment code printed on it to the vendor in a bucket relay.

[0005] For example, in the value transfer service system disclosed in Patent Document 1, a first user first purchases a paper medium on which a payment code is printed. Next, the first user reads the payment code on the paper medium using a device with a photographing function, such as a smartphone, and sets the amount of electronic money to be paid and the contact information (such as a telephone number) of the second user to be paid at the access destination indicated by the read payment code. The first user provides the paper medium on which the payment code is printed to the second user, and the second user reads the payment code on the provided medium with their own device, an access code is sent to their set contact information, and they can receive the set electronic money by performing a collection operation at the access destination indicated by the access code. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Patent No. 7441191 Summary of the Invention [Problem to be solved by the invention]

[0007] However, in the value transfer service system of Patent Document 1, the payer must input the contact information of the person to whom the electronic money is to be paid in advance. In other words, when buying beer from a beer vendor at a baseball stadium, it is necessary to ask for the vendor's contact information. If the payer and the vendor are far apart, it is difficult to ask for the vendor's contact information, and even if the vendor is nearby, asking for the vendor's contact information is a hassle.

[0008] Furthermore, in the value transfer service system of Patent Document 1, the first user is required to set not only the contact information of the second user, who is the payment counterparty, but also his own contact information every time he uses the service. For example, if a family of four goes shopping at a shopping mall and wants to unify the payment with Dad's electronic money payment, but each family member wants to buy something from a different store, Dad will need to set up the deposit, Dad's contact information, and the store's contact information on three pieces of paper with payment codes printed on them, which is very cumbersome.

[0009] Therefore, a primary object of the present invention is to provide a novel information processing system and information processing method.

[0010] Another object of the present invention is to provide an information processing system and an information processing method that allow easy electronic payment using a sheet on which a code is printed. [Means for solving the problem]

[0011] A first invention is an information processing system comprising two user terminals and a management server capable of communicating with the user terminals and managing the transfer of money between users using sheets on which money transfer codes are printed. Each of the user terminals comprises an operation unit, an identification information storage unit that stores user identification information identifying the user of the user, and an acquisition unit that acquires sheet identification information set in the money transfer code printed on the sheet. The first user terminal further comprises a payment amount registration request unit that requests the management server to register deposit information including the sheet identification information acquired by the acquisition unit, the user identification information stored in the identification information storage unit, and the payment amount set by the operation unit. The second user terminal further comprises a payment instruction unit that transmits payment information including the sheet identification information acquired by the acquisition unit and the user identification information stored in the identification information storage unit to the payment server and causes the payment server to execute a process of receiving online the payment amount included in the deposit information requested to be registered by the payment amount registration request unit. The management server includes a management information storage unit that stores management information that manages the transfer of money between users using the sheet, a deposit information transmission unit that transmits deposit information to the payment server, and a payment management unit that, when payment information is received from the payment server, registers payment completion in correspondence with the sheet identification information in the management information stored in the management information storage unit.

[0012] A second invention is according to the first invention, and the first user terminal further comprises a user setting request unit that requests the management server to register booklet identification information of a booklet including a sheet on which a registration code is printed and a plurality of sheets on which different money transfer codes are printed, in association with user identification information. The management server further comprises a management information registration unit that, in response to a request from the user setting request unit, registers the booklet identification information and the user identification information in association with each other in the management information stored in the management information storage unit.

[0013] A third invention is according to the second invention, and the deposit information further includes booklet identification information. The management server includes a first determination unit that, in response to a request from the payment amount registration request unit, determines whether the user identification information of the first user terminal that made the request matches the user identification information registered in association with the booklet identification information included in the deposit information in the management information stored in the management information storage unit, and, when the first determination unit determines that the two user identification information match, registers the payment amount included in the deposit information whose registration is requested by the payment amount registration request unit in association with the sheet identification information and the user identification information in the management information stored in the management information storage unit.

[0014] A fourth invention is an information processing method for an information processing system including two user terminals and a management server that is communicable with the user terminals and manages the transfer of money between users using sheets on which money transfer codes are printed. One user terminal acquires sheet identification information set in the money transfer code printed on the sheet and requests the management server to register deposit information including the acquired sheet identification information, user identification information set for the user terminal or the user of the user terminal, and the payment amount. The management server registers the deposit information in the management information that manages the transfer of money between users using the sheet and transmits the deposit information to a payment server. The other user terminal acquires the sheet identification information set in the money transfer code printed on the sheet and transmits payment information including the acquired sheet identification information and user identification information set for the user terminal or the user of the user terminal to the payment server, causing the payment server to execute a process of receiving the payment amount included in the deposit information online. [Effects of the Invention]

[0015] According to this invention, electronic payment can be easily made using a sheet on which a code is printed.

[0016] The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description of the preferred embodiments with reference to the drawings. [Brief explanation of the drawings]

[0017] [Figure 1] 1 is a diagram illustrating an information processing system according to an embodiment of the present invention. [Figure 2] 2 is a block diagram showing an example of an electrical configuration of the management server shown in FIG. 1. FIG. [Figure 3] 2 is a block diagram showing an example of the electrical configuration of the user terminal shown in FIG. 1. FIG. [Figure 4] FIG. 2 is a diagram showing an example of specific contents of the booklet shown in FIG. [Figure 5] (A) is a diagram showing an example of a main menu screen displayed on the display device of the user terminal shown in Figure 1, (B) is a diagram showing an example of a user setting screen displayed on the display device of the user terminal shown in Figure 1, (C) is a diagram showing an example of a payment amount registration screen displayed on the display device of the user terminal shown in Figure 1, and (D) is a diagram showing an example of a payment screen displayed on the display device of the user terminal shown in Figure 1. [Figure 6] This is a diagram to explain part of an example of the processing flow of the first user terminal, the second user terminal, the management server, and the payment server when the payment amount registration process is performed using a sheet at the first user terminal and the payment process is performed at the second user terminal. [Figure 7] This is a diagram to explain another part of an example of the processing flow of the first user terminal, the second user terminal, the management server, and the payment server when the payment amount registration process is performed using a sheet at the first user terminal and the payment process is performed at the second user terminal. [Figure 8] 2 is a diagram showing an example of booklet management information managed by the management server shown in FIG. 1. FIG. [Figure 9] 3 is a diagram showing an example of a memory map of a RAM of the management server shown in FIG. 2; FIG. [Figure 10] 4 is a diagram showing an example of a memory map of a RAM of the user terminal shown in FIG. 3. FIG. [Figure 11] 3 is a flowchart showing an example of booklet management processing by a CPU of the management server shown in FIG. 2. FIG. [Figure 12] 4 is a flowchart showing an example of a user setting process of a CPU of the user terminal shown in FIG. 3. [Figure 13] 4 is a flow chart showing an example of payment amount registration processing of the CPU of the user terminal shown in FIG. 3. FIG. [Figure 14] 4 is a flowchart showing an example of a payment process by the CPU of the user terminal shown in FIG. 3. DETAILED DESCRIPTION OF THE INVENTION

[0018] 1, an information processing system 10 of this embodiment includes a management server 12, and the management server 12 is communicatively connected to a plurality of user terminals via a network 14. In this embodiment, the plurality of user terminals are a first user terminal 16 used by a first user and a second user terminal 18 used by a second user.

[0019] Hereinafter, in this specification, when there is no need to distinguish between the first user terminal 16 and the second user terminal 18, they will simply be referred to as "user terminals." Similarly, when there is no need to distinguish between the first user and the second user, they will simply be referred to as "users."

[0020] A payment server 20 is communicably connected to the network 14 of the information processing system 10. The payment server 20 is a server that provides a payment service using a two-dimensional code, and is already well known, so a detailed description thereof will be omitted.

[0021] Furthermore, the first user purchases and owns a booklet 22 used in the information processing system 10. As will be explained in detail later, the booklet 22 is a bundle of multiple recording media (hereinafter referred to as "sheets") on which two-dimensional codes are printed. A typical example of a recording medium is paper.

[0022] 1 is an example and is not limited to the information processing system 10. In this embodiment, two user terminals are shown, but in reality, three or more user terminals may be connected to the network 14.

[0023] The management server 12 is an information processing device that manages the transfer of money using the sheet 22b (see FIG. 4) included in the booklet 22 of this embodiment.

[0024] The network 14 is composed of an IP network (or IP network) including the Internet, and an access network (or access network) for accessing this IP network. The access network may be a public telephone network, a mobile phone network, a wired LAN, a wireless LAN, or a CATV (Cable Television) network.

[0025] The user terminal is another information processing device, such as a smartphone or tablet. In some cases, a PC or server with a built-in or connected camera can also be used as the user terminal. Furthermore, a terminal dedicated to payment can also be used as a user terminal that only performs payment.

[0026] The payment server 20 is a server that performs payment by reading a two-dimensional code (in this embodiment, a QR (Quick Response) code (registered trademark)) with a user terminal. In this embodiment, when one user pays money to another user, the first user reads the two-dimensional code printed on the sheet 22b using his / her own user terminal and registers the payment amount (deposit information) in the management server 12, which is the access destination associated with the two-dimensional code. The management server 12 transmits the payment amount (deposit information) to the payment server 20. The first user hands the sheet 22b with the payment amount set to the other user. The other user reads the two-dimensional code printed on the received sheet 22b using his / her own user terminal, accesses the payment server 20, and receives the payment amount pre-registered on the sheet 22b online. In other words, electronic payment is performed by transmitting and receiving data of electronic monetary value.

[0027] As shown in FIG. 2, the management server 12 includes a CPU 30, which is connected to a RAM 32, a communication interface (hereinafter referred to as "communication I / F") 34, and an input / output interface (hereinafter referred to as "input / output I / F") 36 via an internal bus.

[0028] The CPU 30 is responsible for overall control of the management server 12. However, instead of the CPU 30, a SoC (System-on-a-chip) including multiple functions such as a CPU function and a GPU (Graphics Processing Unit) function may be provided.

[0029] RAM 32 is a main storage device and is used as a work area or buffer area for CPU 30. Although not shown, management server 12 is provided with a HDD and ROM as auxiliary storage devices. However, non-volatile memory such as an SSD may be used instead of or in addition to the HDD. Various software such as the operating system, middleware, and various application programs of management server 12 are stored in this auxiliary storage device.

[0030] The communication I / F 34 is a wired interface for transmitting and receiving control signals and data to and from external computers such as the user terminal and the payment server 20 via the network 14 under the control of the CPU 30. However, the communication I / F 34 may also be a wireless interface for connecting to a wireless LAN.

[0031] An input device 38 and a display device 40 are connected to the input / output I / F 36. The input device 38 is a keyboard and a computer mouse. A touch panel may also be provided. The display device 40 is, for example, a liquid crystal display device.

[0032] In addition, the input / output I / F 36 outputs operation data input from the input device 38 to the CPU 30, and also outputs image data generated by the CPU 30 to the display device 40, causing the display device 40 to display a screen or image corresponding to the image data.

[0033] The electrical configuration of the management server 12 shown in FIG. 2 is an example, and the management server 12 is not limited to this configuration.

[0034] As shown in FIG. 3, the user terminal includes a CPU 50, which is connected to a RAM 52, a communication I / F 54, and an input / output I / F 56 via an internal bus.

[0035] The CPU 50 is responsible for overall control of the user terminal. However, instead of the CPU 50, an SoC including multiple functions such as a CPU function and a GPU function may be provided.

[0036] The RAM 52 is a main storage device and is used as a work area or buffer area for the CPU 50. Although not shown, the user terminal is provided with a hard disk drive (HDD) and a read-only memory (ROM) as auxiliary storage devices. However, non-volatile memory such as an SSD may be used instead of or in addition to the HDD. This auxiliary storage device stores various software such as the user terminal's operating system, middleware, and various application programs.

[0037] The communication I / F 54 is a wireless interface for transmitting and receiving control signals and data to and from external computers such as the management server 12 and the settlement server 20 via the network 14 under the control of the CPU 50. However, a priority interface for connecting to a priority LAN can also be used as the communication I / F 54.

[0038] An input device 58, a display device 60, and a camera 62 are connected to the input / output I / F 56. The input device 58 is a keyboard and a computer mouse. A touch panel may also be provided. The display device 60 is, for example, a liquid crystal display device. The camera 62 is, for example, a CCD camera.

[0039] Furthermore, the input / output I / F 56 outputs operation data input from the input device 58 to the CPU 50, and also outputs image data generated by the CPU 50 to the display device 60, causing a screen or image corresponding to the image data to be displayed on the display device 60. The input / output I / F 56 also outputs a shooting instruction from the CPU 50 to the camera 62, and outputs captured image data input from the camera 62 to the CPU 50.

[0040] Note that the electrical configuration of the user terminal shown in Figure 3 is an example and is not limited to this configuration. The user terminal is typically a smartphone and therefore also has a calling function, but the calling function is not related to the present invention and is therefore not shown or described. Also, in this example, the first user terminal 16 and the second user terminal 18 are described as having the same configuration, but they may also have different configurations.

[0041] 4, booklet 22 is made up of sheet 22a for registering information about booklet 22 in management server 12 and multiple sheets 22b for transferring money by electronic settlement. Multiple sheets 22b can be separated from booklet 22 one by one.

[0042] A unique two-dimensional code is printed on each of the sheet 22a and the multiple sheets 22b. The two-dimensional code on the sheet 22a contains identification information for the booklet 22 (hereinafter referred to as a "booklet ID"). The two-dimensional code on the sheet 22b contains identification information for the sheet 22b (hereinafter referred to as a "sheet ID") in addition to the booklet ID.

[0043] In the information processing system 10 of this embodiment, money can be transferred online between two parties using the sheet 22b included in the booklet 22. Below, the transfer of money, i.e., electronic money, between two parties, i.e., the first user and the second user, will be described using an example in which a first user who owns the booklet 22 purchases a product sold by a second user and pays for it by electronic payment using the sheet 22b on which a two-dimensional code is printed.

[0044] When money is exchanged using sheet 22b of booklet 22 at first user terminal 16 and second user terminal 18, an application program for exchanging money (hereinafter referred to as the "money exchange program") is executed as an example of an information processing program in accordance with the operations of the first user and second user.

[0045] When the money transfer program is executed on the user terminal, a main menu screen 100 shown in FIG. 5(A) is displayed on the display device 60. The main menu screen 100 has four button images 102, 104, 106, and 108 arranged vertically. The button image 102 is an icon for registering the booklet 22 in the management server 12. The button image 104 is an icon for executing the payment amount registration process. The button image 106 is an icon for executing the payment process. The button image 108 is an icon for closing the main menu and hiding the main menu screen 100.

[0046] The first user registers the booklet 22 in the management server 12 in order to use the sheet 22b to exchange money. However, if the booklet 22 has already been registered, there is no need to register it again. When registering the booklet 22 in the management server 12, the first user turns on the button image 102 on the main menu screen 100. This starts the registration process for the booklet 22, turns on the camera 62 of the first user terminal 16, and the first user reads the two-dimensional code for user settings written on the sheet 22a of the booklet 22. The first user terminal 16 obtains the booklet ID by reading the two-dimensional code on the sheet 22a. This causes the display device 60 of the first user terminal 16 to display a user setting screen 150 shown in FIG. 5(B).

[0047] In the user setting screen 150, an input area 152 is provided at the top of the screen, and a character string 154 including a link is displayed below the input area 152. Furthermore, a button image 156 and a button image 158 are displayed side by side below the character string 154.

[0048] A user ID is input into input area 152 in accordance with an operation by the first user. The user ID is identification information of a user (or the user terminal of that user) who has registered to use the money transfer program and booklet 22 to transfer money, and in this embodiment, is the same as the identification information of a user registered to use a payment service using payment server 20. Therefore, in this embodiment, the user ID is automatically set to the identification information of a user registered in payment server 20, etc., when registering user information on a web page for obtaining the money transfer program.

[0049] Character string 154 indicates that if user registration has not yet been completed, user registration should be carried out, and also includes a link to a web page for user registration.

[0050] As an example, in user registration, the user's name, contact information, and user ID are registered in the management server 12. User registration itself is a general matter and is not essential to the present invention, so a detailed description thereof will be omitted.

[0051] The button image 156 is an icon for executing settings for a user who will use the booklet 22. Specifically, when the button image 156 is turned on, a control signal, i.e., a command (hereinafter referred to as a "user setting command") instructing to set a user who will use the booklet 22, and user setting information including the booklet ID and user ID of the booklet 22 are transmitted to the management server 12. In response to receiving the user setting command and the user setting information, the management server 12 registers the user ID in booklet management information (see FIG. 8) in association with the booklet ID included in the user setting information.

[0052] The button image 158 is an icon for canceling the settings of the user who will use the booklet 22. Specifically, when the button image 158 is turned on, the settings of the user who will use the booklet 22 are canceled and the display returns to the main menu. Therefore, the user setting screen 150 is not displayed on the display device 60, and the main menu screen 100 is displayed.

[0053] The following describes the flow of a payment from a first user to a second user using sheet 22b, with reference to Figures 5(C), 5(D), 6, and 7. Figure 6 shows the process when a first user registers a payment amount, and Figure 7 shows the process when a second user makes a payment.

[0054] When the first user turns on button image 104 on main menu screen 100, the process of registering the payment amount for sheet 22b begins, and the camera 62 of first user terminal 16 is turned on and the first user reads the two-dimensional code for monetary transfer printed on sheet 22b. By reading the two-dimensional code on sheet 22b, first user terminal 16 obtains the booklet ID of booklet 22 including sheet 22b and the sheet ID of sheet 22b. Then, a payment amount registration screen 200 shown in FIG. 5(C) is displayed on display device 60 of first user terminal 16.

[0055] 5(C), payment amount registration screen 200 has input area 202 at the top of the screen. Character string 204 is displayed below input area 202. Furthermore, below character string 204, button image 206 and button image 208 are provided side by side.

[0056] Input area 202 is an area for inputting the payment amount to be set for sheet 22b. Character string 204 describes the expiration date of sheet 22b, i.e., the deadline for payment. The expiration date is set to the date on which the payment amount is registered plus a predetermined number of days, but may also be set arbitrarily by the user (here, the first user).

[0057] The button image 206 is an icon for registering the payment amount in the management server 12. Specifically, when the button image 206 is turned on, a command instructing to register the sheet 22b (hereinafter referred to as a "deposit command") and deposit information including the booklet ID, the sheet ID, and the payment amount are sent to the management server 12. In response to receiving the deposit command and the deposit information, the management server 12 registers the payment amount in the booklet management information in association with the booklet ID and the sheet ID included in the deposit information. In addition, the management server 12 sends the deposit information to the payment server 20. Therefore, the payment information is registered in the payment server 20.

[0058] When the user ID described in the booklet management information corresponding to the booklet ID included in the deposit information matches the user ID included in the deposit information, the management server 12 can know that the user (here, the first user) who owns the booklet 22 to which this booklet ID is set is attempting to register the payment amount. Therefore, when the user ID described in the booklet management information corresponding to the booklet ID included in the deposit information does not match the user ID included in the deposit information, the management server 12 can know that a user other than the user who owns the booklet 22 to which this booklet ID is set is mistakenly attempting to register the payment amount. In such a case, an error occurs, and the payment amount registration process is stopped. The management server 12 can also notify the user of the user terminal that sent the deposit command, etc., that the payment amount cannot be registered.

[0059] Button image 208 is an icon for canceling the registration of the payment amount. Although not shown in Fig. 6, when button image 208 is turned on, the registration of the payment amount is canceled and the screen returns to the main menu. Therefore, the payment amount registration screen 200 is hidden on the display device 60, and the main menu screen 100 is displayed.

[0060] After registering sheet 22b on which the payment amount is set, the first user hands sheet 22b on which the payment amount is set to the party who is to receive the payment amount (here, the second user). The second user executes the money transfer program using second user terminal 18, opens main menu screen 100, and turns on button image 108 on main menu screen 100.

[0061] When the second user turns on the button image 108 on the main menu screen 100, the payment process using the sheet 22b starts, the camera 62 of the second user terminal 18 is turned on, and the second user reads the two-dimensional code for monetary transfer printed on the sheet 22b received from the first user. By reading the two-dimensional code on the sheet 22b, the second user terminal 18 obtains the booklet ID of the booklet 22 that includes the sheet 22b and the sheet ID of the sheet 22b.

[0062] The second user terminal 18 transmits payment information including the acquired booklet ID, sheet ID, and user ID to the payment server 20. The payment server 20 then notifies the second user terminal 18, which is the sender of the payment information, of the payment amount stated in the deposit information having the same booklet ID and sheet ID as the booklet ID and sheet ID included in the payment information as the amount to be received. When the second user terminal 18 receives the notification of the amount to be received, a payment screen 250 shown in FIG. 5(D) is displayed on the display device 60 of the second user terminal 18.

[0063] In addition, if the user ID included in the payment information does not match the user ID included in the deposit information having the same booklet ID and sheet ID as the booklet ID and sheet ID included in the payment information, the payment server 20 can determine that a user (basically a second user) other than the user who registered the payment amount (here, the first user) is attempting to make the payment. Therefore, if the user ID included in the payment information matches the user ID included in the deposit information having the same booklet ID and sheet ID as the booklet ID and sheet ID included in the payment information, the payment server 20 can determine that the user who registered the payment amount is attempting to make the payment by mistake. In such a case, an error occurs and the payment process is stopped. The payment server 20 can also notify the user terminal that sent the payment information that the payment process has been stopped.

[0064] 5(D), payment screen 250 has character string 252 at the top of the screen. Below character string 252, another character string 254 is displayed. Furthermore, below character string 254, button image 256 and button image 258 are provided side by side.

[0065] The amount to be received, i.e., the payment amount set on the sheet 22b, is written in the character string 252. The expiration date of the sheet 22b, i.e., the deadline for payment, is written in the character string 254.

[0066] The button image 256 is an icon for executing payment, i.e., for receiving the payment amount. Specifically, when the button image 256 is turned on, a command instructing execution of payment (hereinafter referred to as a "payment command") and the user ID of the second user are transmitted to the payment server 20. In response to receiving the payment command, the payment server 20 executes a process of paying the payment amount stated in the deposit information including the same booklet ID and sheet ID as the booklet ID and sheet ID included in the payment information including the same user ID as the user ID received together with the payment command, from the first user to the second user of the second user terminal 18 that sent the payment command, and further transmits the payment information to the management server 12. Upon receiving the payment information, the management server 12 registers the completion of payment for the corresponding booklet ID and sheet ID in the booklet management information and notifies the first user terminal 16 used by the first user with the corresponding user ID of the payment amount. Upon receiving the notification of the payment amount, the first user terminal 16 displays the payment and the payment amount on the display device 60 to notify the first user.

[0067] Button image 258 is an icon for canceling payment. Although not shown in Fig. 7, when button image 258 is turned on, payment is not made and the display returns to the main menu. Therefore, payment screen 250 is hidden on display device 60, and main menu screen 100 is displayed instead.

[0068] As shown in FIG. 8, the booklet management information describes a user ID and a sheet ID corresponding to a booklet ID. The booklet ID, user ID, and sheet ID are as described above. In the example shown in FIG. 8, the booklet ID is indicated using the letter "T" and a number. The user ID is indicated using the letter "U" and a number. The sheet IDs are Sheet 1, Sheet 2, ..., Sheet n, and are indicated using the character string "sheet" and a number. The numbers correspond to the arrangement order of the sheets 22b in the booklet 22. However, n is a natural number, and the maximum value of n is the total number of sheets 22b. Furthermore, the booklet ID, user ID, and sheet ID shown in FIG. 8 are merely examples and should not be considered limiting. The booklet ID, user ID, and sheet ID may be numbers, letters, symbols, or a combination thereof.

[0069] In the booklet management information, a horizontal line means that it is not registered. Therefore, no user settings have been made for booklet IDs T2, T3, etc. For booklet ID T1, a user setting has been made, and for sheet 1, the payment amount is 800 yen, indicating that payment has been completed. For sheet 2, the payment amount is 1500 yen, indicating that payment has not been completed. As mentioned above, sheet n is not registered (or unused). Sheets 3 to n-1 are omitted, but are similar to sheets 1, 2, and n.

[0070] The reason why each sheet 22b of each booklet 22 is managed so that it can be distinguished between unregistered, unpaid, and paid is to prevent a sheet 22b for which payment has been completed from being used by mistake, or a sheet 22b with a payment amount set from being registered by mistake again. However, if the user ID is the same, it may be possible to register the payment amount again, assuming that this is a correction to the payment amount. In such a case, the amount once registered is updated.

[0071] Although not shown in the figure, for sheets 22b on which payment amounts are set, the expiration date is managed individually in correspondence with the sheet ID. Therefore, even if payment is not completed, payment processing is not executed for sheets 22b whose expiration date has passed. In this case, instead of "unpaid," "expired" may be written in correspondence with the sheet ID.

[0072] 9, the RAM 32 includes a program storage area 302 and a data storage area 304. The program storage area 302 stores an information processing program executed by the management server 12 of this embodiment.

[0073] The information processing programs executed by the management server 12 include a main processing program 302a, a communication program 302b, and a booklet management program 302c.

[0074] The main processing program 302a is a program for executing the main routine of information processing in the management server 12 of this embodiment.

[0075] The communication program 302b is a program for communicating with external devices, in this embodiment, the user terminal and the payment server 20.

[0076] The booklet management program 302c is a program for managing booklet management information and updating the booklet management information in response to communication with the user terminal and the settlement server 20.

[0077] Although not shown, the program storage area 302 stores application programs required to execute the information processing program of this embodiment.

[0078] The data storage area 304 stores booklet management information data 304a, user setting information data 304b, deposit information data 304c, settlement information data 304d, and the like.

[0079] The booklet management information data 304a is data on the booklet management information shown in FIG.

[0080] The user setting information data 304b is data that is transmitted from a user terminal when a user who uses the booklet 22 is set and registered in the management server 12, and includes a booklet ID and a user ID.

[0081] The deposit information data 304c is data on deposit information including the sheet ID, booklet ID, user ID, and payment amount, which is sent from the user terminal together with a deposit command when registering the sheet 22b on which the payment amount is set to the management server 12. However, this user ID is the user ID of the user of the user terminal that registers the sheet 22b on which the payment amount is set to the management server 12.

[0082] The payment information data 304d is transmitted from the user terminal together with the payment command when a payment is made, and is data on payment information including the sheet ID, booklet ID, and user ID, where the user ID is the user ID of the user of the user terminal making the payment.

[0083] Although not shown, the data storage area 304 stores other data required to execute information processing, and is provided with a timer (counter) and flags required to execute information processing.

[0084] 10, the RAM 52 includes a program storage area 402 and a data storage area 404. The program storage area 402 stores a money transfer program, which is an example of an information processing program executed by the user terminal of this embodiment.

[0085] The money transfer program executed on the user terminal includes a main processing program 402a, a communication program 402b, an operation detection program 402c, a screen display program 402d, a code reading program 402e, a user setting program 402f, a deposit program 402g, and a settlement program 402h.

[0086] The main processing program 402a is a program for executing the main routine for processing money transfers in the user terminal of this embodiment.

[0087] The communication program 402b is a program for communicating with external devices, in this embodiment, the management server 12 and the settlement server 20.

[0088] The operation detection program 402c is a program for detecting a user operation.

[0089] The screen display program 402d is a program for displaying various screens (main menu screen 100, user setting screen 150, payment amount registration screen 200, settlement screen 250, etc.) on the display device 60 using the screen data 404b.

[0090] The code reading program 402e is a program for reading information set or stored in a two-dimensional code from an image of the two-dimensional code captured by the camera 62 in accordance with a user's operation.

[0091] The user setting program 402f is a program for setting a user who will use the booklet 22 and registering the user in the management server 12 in accordance with the user's operation.

[0092] The deposit program 402g is a program for setting the payment amount on the sheet 22b and registering it in the management server 12 in accordance with the user's operation.

[0093] The settlement program 402h is a program for accessing the settlement server 20 in accordance with the user's operation, executing settlement processing, and receiving the payment amount set on the sheet 22b online as the amount to be received.

[0094] Although not shown in the figure, the program storage area 402 stores application programs required to execute the money transfer program of this embodiment.

[0095] The data storage area 404 stores operation data 404a, screen data 404b, user ID data 404c, user setting information data 404d, deposit information data 404e, settlement information data 404f, and the like.

[0096] The operation data 404a is data about a user's operation detected according to the operation detection program 402c.

[0097] The screen data 404b is image data for displaying various screens.

[0098] The user ID data 404c is identification information of the user who exchanges money using the booklet 22, that is, data of the user ID, and the user ID is, for example, a mobile phone number.

[0099] The user setting information data 404d is data on user setting information including the user ID of the user who uses the booklet 22, that is, the user ID indicated by the user ID data 404c, and the booklet ID of this booklet 22.

[0100] The deposit information data 404e is data regarding deposit information including the sheet ID of the unused sheet 22b on which the payment amount is set and registered, the booklet ID of the booklet 22 containing this sheet 22b, the user ID of the user registering the payment amount, i.e., the user ID indicated by the user ID data 404c, and the set payment amount.

[0101] The payment information data 404f is data regarding payment information including the sheet ID of the unpaid sheet 22b for which the payment amount has been set and registered, the booklet ID of the booklet 22 that includes this sheet 22b, and the user ID of the user making the payment, i.e., the user ID indicated by the user ID data 404c.

[0102] Although not shown in the figure, the data storage area 404 stores other data necessary for executing the money transfer process, and is provided with a timer (counter) and flags necessary for executing the money transfer process.

[0103] Fig. 11 is a flow diagram showing an example of information processing by the CPU 30 of the management server 12 shown in Fig. 2. The symbols starting with "S" shown in the figure are symbols given to identify each step (processing), and in the following explanation, each step (processing) will be represented by a symbol.

[0104] 11, when data is received from an external device, the CPU 30 starts information processing, and in S1 determines whether the setting is for the user who will use the booklet 22. That is, the CPU 30 determines whether a user setting command and user setting information data have been received. If "NO" in S1, that is, if the setting is not for the user who will use the booklet 22, the process proceeds to S7.

[0105] On the other hand, if the answer is "YES" in S1, that is, if the setting is for a user who will use the booklet 22, then in S3 it is determined whether the user has already been registered. Here, the CPU 30 refers to the booklet management information data 304a and determines whether a user ID has already been set or registered in correspondence with the booklet ID included in the user setting information data 304b.

[0106] If the answer is "YES" in S3, that is, if the booklet ID has already been registered, the information processing ends. In this case, the user terminal that sent the user setting command or the like may be notified that the user who will use the booklet 22 has already been set.

[0107] On the other hand, if the answer is "NO" in S3, that is, if the booklet ID has not already been registered, in S5, the user ID contained in the user setting information data 304b is registered in the booklet management information in correspondence with the booklet ID contained in the user setting information data 304b, and the information processing is terminated.

[0108] In S7, it is determined whether or not deposit information is to be registered. That is, the CPU 30 determines whether or not a deposit command and deposit information data have been received. If the answer is "YES" in S7, that is, if deposit information is to be registered, then in S9 it is determined whether or not the user ID matches. Here, the CPU 30 determines whether or not the booklet ID and user ID included in the deposit information data 304c match the booklet ID included in the deposit information data 304c and the user ID stored in association with this booklet ID in the booklet management information, respectively.

[0109] If S9 is "NO," that is, if the user IDs do not match, the information processing ends. At this time, the CPU 30 may notify an error to the user terminal that sent the deposit command, etc. On the other hand, if S9 is "YES," that is, if the user IDs match, in S11 it is determined whether the deposit or settlement has been completed for the corresponding sheet 22b.

[0110] If S11 is "YES", that is, if the deposit or settlement has been completed for the corresponding sheet 22b, the information processing is terminated. On the other hand, if S11 is "NO", that is, if the deposit or settlement has not been completed for the corresponding sheet 22b, in S13, the payment amount included in the deposit information data 304c is registered in the booklet management information in correspondence with the sheet ID, booklet ID, and user ID included in the deposit information data 304c, and in S15, the deposit information is sent to the settlement server 20, and the information processing is terminated.

[0111] Also, if S7 is "NO", that is, if payment information is being registered, in S17, payment completion is registered in the booklet management information corresponding to the booklet ID and sheet ID included in the payment information data 304d, and in S19, the payment amount is notified to the user terminal of the user ID corresponding to the booklet ID and sheet ID included in the payment information corresponding to the payment information data 304d, and information processing is terminated.

[0112] FIG. 12 is a flow diagram showing an example of user setting processing by the CPU 50 of a user terminal (here, the first user terminal 16). As described above, when the button image 102 is turned on on the main menu screen 100, as shown in FIG. 12, the CPU 50 starts the user setting processing, activates the camera 62, and reads the two-dimensional code on the sheet 22a in S101. In S101, in accordance with the operation of the first user, an image of the two-dimensional code on the sheet 22a is photographed, and the booklet ID is extracted from the two-dimensional code. Note that once the two-dimensional code image is photographed, the camera 62 is turned off. Furthermore, if the two-dimensional code on the sheet 22b is read, an error is notified.

[0113] In the next S103, the user setting screen 150 is displayed on the display device 60. In the next S105, it is determined whether or not an operation has been performed. Here, the CPU 50 determines whether or not operation data 404a has been detected. If the determination in S105 is "NO," that is, if there has been no operation, the process returns to S105. On the other hand, if the determination in S105 is "YES," that is, if there has been an operation, it is determined in S107 whether or not the operation is a user setting operation. Here, the CPU 50 determines whether or not the button image 156 has been turned on with the user ID entered in the input area 152.

[0114] If "YES" in S107, that is, if it is a user setting operation, in S109, the user setting request is sent to the management server 12, and the user setting process is terminated. In S109, the user setting command and the user setting information data 404d are sent to the management server 12.

[0115] On the other hand, if "NO" in S107, that is, if it is not a setting operation by the user, it is determined in S111 whether or not it is a cancellation. Here, the CPU 50 determines whether or not the button image 158 is turned on.

[0116] If "YES" in S111, that is, if it is a cancellation, the user setting process ends. On the other hand, if "NO" in S111, that is, if it is not a cancellation, in S113, a process according to another operation is executed, and the process returns to S105. In S113, a process such as inputting a user ID into the input area 152 according to the user's operation is executed.

[0117] Fig. 13 is a flow diagram showing an example of the deposit processing of the CPU 50 of a user terminal (here, the first user terminal 16). The deposit processing will be explained using Fig. 13, but the same content as that explained in Fig. 12 will be explained briefly or omitted.

[0118] As described above, when the button image 104 is turned on on the main menu screen 100, the CPU 50 starts the deposit process, activates the camera 62, and reads the two-dimensional code on the sheet 22b in S201, as shown in Fig. 13. In S201, an image of the two-dimensional code on the sheet 22b is captured in accordance with the operation of the first user, and the booklet ID and sheet ID are extracted from the two-dimensional code. Note that if the two-dimensional code on the sheet 22a is read, an error is notified.

[0119] In the next S203, the payment amount registration screen 200 is displayed on the display device 60. In the next S205, it is determined whether or not an operation has been performed. If the determination in S205 is "NO", the process returns to S205. On the other hand, if the determination in S205 is "YES", it is determined in S207 whether or not the operation is to register the payment amount. Here, the CPU 50 determines whether or not the button image 206 has been turned on with the payment amount entered in the input area 202.

[0120] If "YES" in S207, that is, if it is a payment amount registration operation, a payment amount registration request is sent to the management server 12 in S209, and the deposit process is terminated. In S209, a deposit command and deposit information data 404e are sent to the management server 12.

[0121] On the other hand, if "NO" in S207, that is, if the operation is not a payment amount registration operation, it is determined in S211 whether or not the operation is a cancellation. Here, the CPU 50 determines whether or not the button image 208 is turned on.

[0122] If "YES" in S211, the deposit process is terminated. On the other hand, if "NO" in S211, in S213, a process according to another operation is executed, and the process returns to S205. In S213, a process is executed in which the payment amount is input into the input area 202 according to the user's operation.

[0123] Figure 14 is a flow diagram showing an example of payment processing by the CPU 50 of a user terminal (here, the second user terminal 18). The payment processing will be explained using Figure 14, but the same content as that explained in Figures 12 and 13 will be explained briefly or omitted.

[0124] As described above, when the button image 106 is turned on on the main menu screen 100, the CPU 50 starts the payment process, activates the camera 62, and reads the two-dimensional code on the sheet 22b in S301, as shown in FIG.

[0125] In the next S303, the payment information data 404f is sent to the payment server 20. The payment server 20 notifies the user terminal (here, the second user terminal 18) that is the sender of the payment information data 404f of the payment amount stated in the deposit information that includes the same booklet ID and sheet ID as the booklet ID and sheet ID included in the payment information corresponding to the payment information data 404f as the received amount.

[0126] Returning to Fig. 14, in the next step S305, it is determined whether or not there has been a notification of the amount received from the settlement server 20. If "NO" in S305, that is, if there has been no notification of the amount received, the process returns to S305.

[0127] If the payment amount is not set corresponding to the booklet ID and sheet ID or if the payment is complete, a message to that effect is sent to the inquired second user terminal 18. In this case, the CPU 50 of the second user terminal 18 notifies the user of an error and ends the payment process.

[0128] On the other hand, if the answer is "YES" in S305, that is, if the amount to be received has been notified, the payment screen 250 is displayed on the display device 60 in S307. In the next S309, it is determined whether a payment operation has been performed. Here, the CPU 50 determines whether the button image 256 has been turned on.

[0129] If S309 is "YES", that is, if a payment operation has been performed, in S311 the payment server 20 is instructed to execute the payment, and the payment processing ends. In S311, a payment command and the user ID are sent to the payment server 20. The payment server 20 executes electronic payment processing to pay the amount deposited by the first user to the user of the second user terminal 18 who issued the payment instruction, based on the payment information including the user ID received together with the payment command, and sends a notification that the payment has been executed to the management server 12. Therefore, as described above, the management server 12 registers the completion of the payment in the booklet management information corresponding to the booklet ID and sheet ID included in the payment information, and notifies the first user terminal 16 of the completion of the payment and the payment amount.

[0130] On the other hand, if "NO" in S309, that is, if there is no settlement operation, it is determined in S313 whether or not to stop the settlement. Here, the CPU 50 determines whether or not the button image 258 is turned on.

[0131] If "YES" in S313, that is, if the payment is to be stopped, the payment process ends. On the other hand, if "NO" in S313, that is, if the payment is not to be stopped, that is, if no operation is performed, the process returns to S309.

[0132] According to this embodiment, one user sets the payment amount on a sheet with a two-dimensional code printed on it, passes the sheet with the payment amount set on it to the other user who will receive the payment amount, and the other user receives the payment amount using the sheet they received, making electronic payment between two parties easy.

[0133] So, for example, when buying beer at a baseball stadium, a spectator uses their own device to set the payment amount on a sheet and hands it to a vendor, who then receives the payment by reading the 2D code printed on the sheet with their own device and serves the beer to the spectator. If the vendor is located away from the spectator, the seat is passed on to the vendor via several other spectators, and the beer is passed on to the spectator via several other spectators. In other words, the spectator's device is not passed on via a bucket relay, and even when a bucket relay is used to pass the seat on, there is no need to ask the vendor for the phone number of the device they are using.

[0134] In this embodiment, in order to transfer money using a sheet in a booklet owned by a user, when depositing the payment amount, it is determined whether the user ID registering the payment amount matches the user ID corresponding to the booklet ID, that is, whether the payment amount has been registered by the user who owns the booklet, but this is not limited to this. When the payment server makes the payment, the two users who transfer money are identified by their respective user IDs, and payment is not made by the owner of the booklet through operations on a third party's terminal, so the owner of the booklet and the person making the payment do not need to be the same person.

[0135] In this embodiment, the management server is configured to register a user ID identical to the identification information of a user registered to use a payment service using the payment server. However, a different user ID may also be registered. In such a case, when a user ID is registered in the management server, the identification information of the user registered to use the payment service linked to the user ID is also registered. Then, when deposit information is sent to the payment server, the identification information of the user registered to use the payment service linked to the user ID is also sent. In this way, at the time of payment, the management server can notify the payment server of the deposited amount corresponding to the identification information of the user to use the payment service, and the payment server can also execute the payment using the identification information of the user to use the payment service. In this case, even if the terminal executing the payment, i.e., the terminal receiving the payment amount, does not have a transfer program stored therein, the payment amount set on the sheet can be received by reading the two-dimensional code printed on the sheet and sending a payment command and the identification information of the user to use the payment service to the payment server.

[0136] Furthermore, in this embodiment, a case where a QR code (registered trademark) is used as an example of a two-dimensional code has been described, but this is not limited thereto, and other two-dimensional codes such as Data Matrix and VeriCode can also be used.

[0137] Furthermore, in this embodiment, a two-dimensional code is used, but a one-dimensional code such as a bar code can also be used.

[0138] Furthermore, the order of the steps in the flowchart shown in this embodiment can be changed if the same results are obtained.

[0139] Furthermore, the various screens and specific numerical values ​​shown in this specification and drawings are merely examples and can be changed as needed. [Explanation of symbols]

[0140] 10. Information Processing Systems 12...Administration Server 14...Network 16...First user terminal 18...Second user terminal 20...Payment server 30, 50...CPU 32, 52...RAM 34, 54...Communication I / F 36, 56... Input / output I / F 38, 58...input device 40, 60...display device 62...Camera

Claims

1. An information processing system comprising: two user terminals; and a management server that is communicable with the user terminals and manages the transfer of money between users using a sheet on which a money transfer code is printed, Each of the user terminals An operation unit; an identification information storage unit that stores user identification information that identifies the user of the device; an acquisition unit that acquires sheet identification information set in the money transfer code printed on the sheet; the first user terminal further comprises a payment amount registration request unit that requests the management server to register deposit information including the sheet identification information acquired by the acquisition unit, the user identification information stored in the identification information storage unit, and the payment amount set by the operation unit; The second user terminal further includes a payment instruction unit that transmits payment information including the sheet identification information acquired by the acquisition unit and the user identification information stored in the identification information storage unit to a payment server, and causes the payment server to execute a process of receiving online the payment amount included in the deposit information requested to be registered by the payment amount registration request unit, The management server a management information storage unit that stores management information for managing the transfer of money between users using the sheet; a deposit information transmitting unit that transmits the deposit information to the payment server; An information processing system comprising a payment management unit that, when payment information is received from the payment server, registers payment completion in correspondence with the sheet identification information in the management information stored in the management information storage unit.

2. the first user terminal further comprises a user setting request unit that associates the user identification information with booklet identification information of a booklet that includes a sheet on which a registration code is printed and a plurality of sheets on which different money transfer codes are printed, and requests the management server to register the user identification information; The information processing system of claim 1, wherein the management server further includes a management information registration unit that registers the booklet identification information and the user identification information in association with each other in the management information stored in the management information storage unit in response to a request from the user setting request unit.

3. The deposit information further includes the booklet identification information, The information processing system of claim 2, wherein the management server includes a first judgment unit that, in response to a request from the payment amount registration request unit, determines whether the user identification information of the first user terminal that made the request matches the user identification information registered in the management information stored in the management information storage unit in correspondence with the booklet identification information included in the deposit information, and when the first judgment unit determines that the two pieces of user identification information match, registers the payment amount included in the deposit information requested to be registered by the payment amount registration request unit in correspondence with the sheet identification information and the user identification information in the management information stored in the management information storage unit.

4. 1. An information processing method for an information processing system including two user terminals and a management server that is communicable with the user terminals and manages the transfer of money between users using a sheet on which a money transfer code is printed, the method comprising: One of the user terminals acquires sheet identification information set in the money transfer code printed on the sheet, and requests the management server to register the acquired sheet identification information, user identification information set for the user terminal or the user of the user terminal, and deposit information including the payment amount; the management server registers the deposit information in management information that manages the transfer of money between users using the sheet, and transmits the deposit information to a settlement server; An information processing method in which the other user terminal acquires sheet identification information set in the money transfer code printed on the sheet, sends payment information including the acquired sheet identification information and user identification information set for the user terminal or the user of the user terminal to the payment server, and causes the payment server to execute a process to receive the payment amount included in the deposit information online.

Images