JP7552088B2 - Payment support system, payment support method, and payment support server - Google Patents

Description

The present invention relates to a payment support system, a payment support method, and a payment support server.

Conventionally, a payment support system capable of split payment has been known (see, for example, Patent Document 1). The payment support system described in Patent Document 1 includes a store terminal, a plurality of user terminals, a plurality of payment devices, and a payment support device. A different payment system is installed in each payment device. In response to a payment request from a facility user, the payment support device, as an intermediary between the user and the payment device, requests (requests) the payment device to make an electronic payment for the facility usage fee.
In the payment support system described in Patent Document 1, when multiple users who visit a store use their own user terminals to access the store management site and log in, each user terminal displays a QR code (registered trademark) that includes the user ID of each user.

In other words, with the technology described in Patent Document 1, when multiple users use a store to make electronic payments, it is necessary to prepare a different QR code for each user.
Since the task of preparing a different QR code for each user is cumbersome, the technology described in Patent Document 1 places a heavy burden on the system operator to prepare a different QR code for each user.
As a result, the technology described in Patent Document 1 is unable to sufficiently improve the convenience of the payment support system and is unable to promote use of the payment support system.

JP 2019-174943 A

In view of the above-mentioned problems, the present invention aims to provide a payment support system, a payment support method, and a payment support server that can improve convenience and promote usage.

One aspect of the present invention is a payment support system comprising a plurality of user terminals carried by a plurality of users, a code display unit that displays a payment code and a reference code read by the plurality of user terminals, and a payment support server, the code display unit being disposed in a store used by the plurality of users, the payment code and the reference code displayed on the code display unit being shared codes used by the plurality of users, the payment support server managing information on the total amount to be paid by the plurality of users using the store and on whether or not payment by the plurality of users has been completed, and the payment code being displayed on the code display unit being shared by the plurality of users using the store, When the reference code is read by any one of a plurality of user terminals, the user terminal that read the payment code accepts payment from the user carrying the user terminal that read the payment code, and the payment support server calculates an unpaid amount, which is the difference between the total amount and the paid amount, which is the amount accepted by the user terminal that read the payment code, based on the total amount and the paid amount, and when the reference code is read by any one of the plurality of user terminals, the user terminal that read the reference code displays the unpaid amount calculated by the payment support server.

In one aspect of the payment support system of the present invention, the multiple users include at least a first user and a second user, and the multiple user terminals include at least a first user terminal and a second user terminal, and after the first user terminal reads the payment code and accepts the payment by the first user, when the payment code is read by the second user terminal, the second user terminal may accept the payment by the second user.

In one aspect of the payment support system of the present invention, when the payment support server calculates the outstanding amount to be zero yen, the user terminal that reads the reference code may display zero yen as the outstanding amount, and the payment support server may update information regarding whether or not the payments by the multiple users have been completed to a status of paid.

In one aspect of the payment support system of the present invention, after the user terminal that read the payment code accepts a payment by a user carrying the user terminal that read the payment code, when the reference code is read by any of the multiple user terminals, the user terminal that read the reference code displays the outstanding amount, and when zero yen is displayed as the outstanding amount, the payment support server generates a store exit code and transmits data of the store exit code to the user terminal that read the reference code, and the user terminal that read the reference code becomes capable of displaying the store exit code.

The payment support system of one aspect of the present invention may include an exit code reader that reads the exit code, and an exit gate. When the exit code reader reads the exit code displayed on the user terminal that read the reference code, the exit gate opens, allowing the multiple users to leave the store.

The payment support system of one aspect of the present invention may include a receipt issuing unit that issues a receipt, and when the payment support server calculates the unpaid amount to be zero yen, the receipt issuing unit may be in a state where it is able to issue the receipt.

In one embodiment of the payment support system of the present invention, the payment code includes at least a first type of payment code and a second type of payment code, and when the first type of payment code is read by any one of the plurality of user terminals, the user terminal that read the first type of payment code may accept a first type of payment by a user carrying the user terminal that read the first type of payment code, and when the second type of payment code is read by any one of the plurality of user terminals, the user terminal that read the second type of payment code may accept a second type of payment by a user carrying the user terminal that read the second type of payment code.

In one embodiment of the payment support system of the present invention, when the reference code is read by any of the multiple user terminals, the user terminal that read the reference code requests reference screen data, which is data used to display a reference screen, from the payment support server, and the payment support server transmits the reference screen data to the user terminal that read the reference code, and the user terminal that read the reference code may display the reference screen including the unpaid amount based on the reference screen data transmitted by the payment support server.

In one aspect of the payment support system of the present invention, the code display unit may be a printed matter on which the payment code and the reference code are printed.

In one aspect of the payment support system of the present invention, the code display unit may be a terminal device capable of displaying the payment code and the reference code.

In one aspect of the payment support system of the present invention, when the reference code is read by one of the multiple user terminals, the user terminal that read the reference code displays the outstanding amount and accepts a request to display an order history from a user carrying the user terminal that read the reference code, the user terminal that accepts the request to display the order history requests information indicating the order history from the payment support server, the payment support server transmits the information indicating the order history to the user terminal that accepted the request to display the order history, and the user terminal that accepted the request to display the order history may display the order history based on the information indicating the order history transmitted by the payment support server.

In one embodiment of the payment support system of the present invention, the store may include multiple tables and may be equipped with a store management terminal that displays the payment status of each table.

In one aspect of the payment support system of the present invention, the payment support server may perform an overpayment determination, which is a determination of whether the paid amount is greater than the total amount.

One aspect of the present invention is a payment support method for a payment support system including a plurality of user terminals carried by a plurality of users, a code display unit that displays a payment code and a reference code read by the plurality of user terminals, and a payment support server, the code display unit being disposed in a store used by the plurality of users, the payment code and the reference code displayed on the code display unit being shared codes used by the plurality of users, the payment support server managing information on the total amount to be paid by the plurality of users using the store and on whether or not payment by the plurality of users has been completed, and the payment code being displayed on the code display unit being displayed on the code display unit being shared codes used by the plurality of users. This payment support method includes the steps of: when the reference code is read by one of the user terminals, the user terminal that read the payment code accepts payment by the user carrying the user terminal that read the payment code; the payment support server calculates an unpaid amount, which is the difference between the total amount and the paid amount, based on the total amount and the paid amount, which is the amount accepted for payment by the user terminal that read the payment code; and when the reference code is read by one of the multiple user terminals, the user terminal that read the reference code displays the unpaid amount calculated by the payment support server.

One aspect of the present invention is a payment support server provided in a payment support system that includes a plurality of user terminals carried by a plurality of users and a code display unit that displays a payment code and a reference code read by the plurality of user terminals, the code display unit being disposed in a store used by the plurality of users, the payment code and the reference code displayed on the code display unit being shared codes used by the plurality of users, the payment support server managing information on the total amount to be paid by the plurality of users using the store and whether or not payment by the plurality of users has been completed, and managing information on whether or not the payment code has been read by the plurality of users. When the reference code is read by any of the multiple user terminals, the user terminal that read the payment code accepts payment from the user carrying the user terminal that read the payment code, and the payment support server calculates an unpaid amount, which is the difference between the total amount and the paid amount, based on the total amount and the paid amount, which is the amount accepted for payment by the user terminal that read the payment code, and when the reference code is read by any of the multiple user terminals, the unpaid amount calculated by the payment support server is displayed by the user terminal that read the reference code.

The present invention provides a payment support system, a payment support method, and a payment support server that can improve convenience and promote usage.

1 is a diagram illustrating an example of a schematic configuration of a payment support system according to a first embodiment. FIG. 13 is a diagram showing an example of a payment code displayed on a code display unit. FIG. 13 is a diagram showing an example of a reference screen of a user terminal. FIG. 4 is a diagram showing an example of a screen of the user terminal when the "check order history" button shown in FIG. 3 is operated. 5 is a diagram showing an example of a screen of the user terminal when the "Credit card payment" button shown in FIG. 3 or the "Credit card payment" button shown in FIG. 4 is operated. FIG. FIG. 4 is a diagram showing a first example of a display screen of the store management terminal. FIG. 13 is a diagram showing a second example of a display screen of the store management terminal. 11 is a diagram for explaining an example of a data layout of a payment support server. FIG. 11 is a diagram for explaining an example of a data layout of a payment support server. FIG. A sequence diagram showing an example of processing executed when making a payment using a payment code (QR code) in the payment support system of the first embodiment and a payment service provider's system (external system). 11 is a sequence diagram showing an example of a process executed to confirm an unsettled amount (unpaid amount) in the payment support system of the first embodiment. FIG. A sequence diagram showing an example of processing executed at the time of credit card payment in the payment support system of the first embodiment and the payment service provider's system (external system). 11 is a flowchart for explaining an example of an overpayment determination, etc., performed when making a credit card payment in the payment support system of the first embodiment. 13 is a flowchart for explaining an example of an overpayment determination, etc., performed when a code payment other than a credit card payment is made in the payment support system of the first embodiment. FIG. 13 is a diagram showing an example of a screen of a code display unit (terminal device) of the payment support system of the second embodiment. A figure showing an example of a system to which the payment support system of the second embodiment and a payment service provider's system (external system) are applied.

First Embodiment
Hereinafter, embodiments of a payment support system, a payment support method, and a payment support server of the present invention will be described with reference to the accompanying drawings.

FIG. 1 is a diagram showing an example of a schematic configuration of a payment support system 1 according to the first embodiment.
In the example shown in Fig. 1, a payment support system 1 supports proactive payment (clearance processing) by a user who uses a store. The payment support system 1 includes a plurality of user terminals 11-1, 11-2 carried by a plurality of users, a store management unit 12, and a payment support server 13.
User terminals 11-1 and 11-2 are, for example, smartphones, and can be connected to payment support server 13 via a network (not shown).
The store management unit 12 includes a code display unit 12A, a store exit code reader 12B, a store exit gate 12C, a receipt issuing unit 12D, a store management terminal 12E, and a status notification unit 12F.
The code display unit 12A is placed in a store used by multiple users. The code display unit 12A displays a payment code 12A1 and a reference code 12A2 that are read by multiple user terminals 11-1 and 11-2. The payment code 12A1 and the reference code 12A2 displayed on the code display unit 12A are shared codes used by multiple users (for example, the payment code 12A1 and the reference code 12A2 prepared for each table).

FIG. 2 is a diagram showing an example of the payment code 12A1 displayed on the code display section 12A.
In the example shown in FIG. 2, the code display unit 12A is a printed matter on which a payment code 12A1 and a reference code (not shown in FIG. 2) are printed. The code display unit 12A is placed on a table used in a store by a user carrying the user terminal 11-1 and a user carrying the user terminal 11-2. The payment code 12A1 includes a first type of payment code 12A1-1, a second type of payment code 12A1-2, a third type of payment code 12A1-3, and a fourth type of payment code 12A1-4. The first type of payment code 12A1-1, the second type of payment code 12A1-2, the third type of payment code 12A1-3, and the fourth type of payment code 12A1-4 are, for example, a two-dimensional code such as a QR code (registered trademark), or a one-dimensional code such as a barcode, and are codes used for so-called code payment.
In the example shown in FIG. 2, the first type payment code 12A1-1 is used for a code payment service provided by a first payment service provider (e.g., Rakuten Pay). The second type payment code 12A1-2 is used for a code payment service provided by a second payment service provider (e.g., PayPay). The third type payment code 12A1-3 is used for a code payment service provided by a third payment service provider (e.g., LINE Pay). The fourth type payment code 12A1-4 is used for a code payment service provided by a fourth payment service provider (e.g., Merpay).
2, the payment code 12A1 includes four types of codes, but in other examples, the payment code 12A1 may include any natural number of codes other than 4. In other words, the payment code 12A1 may include only one type of code.

In the example shown in FIG. 1, the reference code 12A2 is, like the payment code 12A1, a two-dimensional code such as a QR code (registered trademark) or a one-dimensional code such as a barcode.
When the reference code 12A2 is read by, for example, the user terminal 11-1 of the multiple user terminals 11-1 and 11-2, the user terminal 11-1 requests reference screen data, which is data used to display the reference screen, from the payment support server 13. Next, the payment support server 13 transmits the reference screen data to the user terminal 11-1, and the user terminal 11-1 displays the reference screen based on the reference screen data transmitted by the payment support server 13.
The payment support server 13 manages the total amount to be paid by multiple users who use the store, information on whether or not payments by multiple users have been completed, and the like.

FIG. 3 is a diagram showing an example of the reference screen of the user terminal 11-1.
3, the reference screen of the user terminal 11-1 includes "Table Number: T01.""Table Number: T01" indicates that the number of the table being used in the store by the user of the user terminal 11-1 is "T01."
The reference screen of the user terminal 11-1 also includes a "Payment status: 'Unpaid.'" The "Payment status: 'Unpaid'" indicates that the payment by the users (users of the user terminal 11-1 and user terminal 11-2) at the store's table (table number: T01) has not yet been completed.
Furthermore, the reference screen of the user terminal 11-1 includes an "unsettled balance of '10,000 yen.'" The "unsettled balance of '10,000 yen'" indicates that a payment of 10,000 yen is required for the user of the store's table (table number: T01) to complete payment.

3, the reference screen of the user terminal 11-1 includes a "Check Order History" button, a "Check Payment History" button, and a "Credit Card Payment" button. In other words, the above-mentioned reference code 12A2 is also used for credit card payments by the user carrying the user terminal 11-1 (11-2).
The "Check Order History" button is operated (eg, pressed) by, for example, the user of user terminal 11-1 when a user at a table (table number: T01) in the store needs to check their order history.

FIG. 4 is a diagram showing an example of a screen displayed on the user terminal 11-1 when the "Check Order History" button shown in FIG. 3 is operated.
In the example shown in Figures 3 and 4, when the "Check Order History" button shown in Figure 3 is operated by, for example, the user of user terminal 11-1, user terminal 11-1 requests order history screen data, which is data used to display the order history screen shown in Figure 4, from payment support server 13. Next, payment support server 13 transmits the order history screen data to user terminal 11-1, and user terminal 11-1 displays the order history screen shown in Figure 4 based on the order history screen data transmitted by payment support server 13.

In the example shown in FIG. 4, the order history screen of the user terminal 11-1 includes "Table number: T01,""Unsettled balance '10,000 yen'," a "Credit card payment" button, and a "Back" button.
The "Back" button is operated (eg, pressed down) by, for example, the user of the user terminal 11-1 when the user of the user terminal 11-1 requests that the screen of the user terminal 11-1 be returned to the reference screen shown in FIG.
In the example shown in Figure 4, a user of user terminal 11-1 can confirm on the order history screen shown in Figure 4 that a patron at a table in the store (table number: T01) ordered three glasses of beer for 500 yen at 22:00, and one bottle of sake for 1,000 yen at 22:10.

In the example shown in Figures 3 and 4, the "Credit card payment" button is operated (e.g., pressed) by the user of user terminal 11-1 when the user of user terminal 11-1 makes a credit card payment.

FIG. 5 is a diagram showing an example of a screen of the user terminal 11-1 when the "Credit card payment" button shown in FIG. 3 or the "Credit card payment" button shown in FIG. 4 is operated.
In the example shown in Fig. 5, when the "Credit card payment" button shown in Fig. 3 or 4 is operated by the user of user terminal 11-1, user terminal 11-1 requests payment screen data, which is data used to display the payment screen shown in Fig. 5, from payment support server 13. Next, payment support server 13 transmits the payment screen data to user terminal 11-1, and user terminal 11-1 displays the payment screen shown in Fig. 5 based on the payment screen data transmitted by payment support server 13.

In the example shown in Figure 5, the payment screen of user terminal 11-1 includes "Payment destination: XX store", "Logos of international brands that can be used for payment", a credit card payment input field, a "Pay" button, and a "Back" button.
"Payment Destination: XX Store" indicates that the payment destination for this credit card payment is "XX Store."
The user of user terminal 11-1 can pay all or part of the "unsettled balance of 10,000 yen" shown in Figures 3 and 4 (make a credit card payment) by inputting the "card expiration date,""cardnumber,""securitycode,""card holder name," and "payment amount," and operating the "Pay" button.
In the above example, when the "Credit Card Payment" button shown in FIG. 3 or the "Credit Card Payment" button shown in FIG. 4 is operated, the screen of the user terminal 11-1 transitions to the payment screen shown in FIG. 5; however, in other examples, the screen of the user terminal 11-1 may transition to the payment screen shown in FIG. 5 when the user terminal 11-1 reads the reference code 12A2 shown in FIG. 1.

1, the store exit code reader 12B is installed in a store. The store exit code reader 12B reads a store exit code (not shown) displayed on the user terminal 11-1 or the user terminal 11-2 when the user of the user terminal 11-1 or the user of the user terminal 11-2 who has made a proactive payment leaves the store.
The exit gate 12C is located at the entrance of the store. The exit gate 12C is opened when the exit code reader 12B reads the exit code displayed on the user terminal 11-1 or the user terminal 11-2. As a result, the user of the user terminal 11-1 and the user of the user terminal 11-2 who have made the independent payment can leave the store.
The receipt issuing unit 12D issues a receipt to the person who made the active payment, such as the user of the user terminal 11-1.
The store management terminal 12E displays the status of each payment at multiple tables in the store. The store management terminal 12E is disposed, for example, at a cash register in the store.

Fig. 6 and Fig. 7 are diagrams showing examples of the display screen of the store management terminal 12E. In detail, Fig. 6 shows a first example of the display screen of the store management terminal 12E, and Fig. 7 shows a second example of the display screen of the store management terminal 12E.
In the example shown in Fig. 6, four tables T01, T02, T03, and T04 are arranged in a store. The store management terminal 12E indicates that the payment status of table T01 is "paid" (unpaid amount is zero yen), and that the payment status of table T02 is "unpaid" (unpaid amount is 10,000 yen). The store management terminal 12E also indicates that the payment status of table T03 is "overpaid" (the amount paid is 5,000 yen more than the total amount to be paid by the user of table T03). Furthermore, the store management terminal 12E indicates that table T04 is "vacant".
6, the store management terminal 12E refers to the payment status of tables T01 to T04 in the database (not shown) of the store management unit 12. The store management terminal 12E also displays the tables T01 to T04 in different colors according to the payment status of the tables T01 to T04. The store management terminal 12E displays table T01 with a payment status of "paid" in blue, for example, table T02 with a payment status of "unpaid" in red, table T03 with a payment status of "overpaid" in yellow, and table T04 with a "vacant seat" in green, for example.
In detail, the store management terminal 12E also displays the layout of tables T01, T02, T03, and T04 within the store.

In the example shown in FIG. 7, the store management terminal 12E displays the payment status of tables T01, T02, T03, T04, Table XX, ..., Table △△, ... located in the store using icons.

1, the status notification unit 12F is, for example, a lamp that displays the payment status of each of the multiple tables in the store. The status notification unit 12F is disposed, for example, near each of the multiple tables in the store.
The payment support server 13 generates the above-mentioned reference screen data, etc. That is, the payment support server 13 calculates the unsettled balance (unpaid amount) included in the reference screen shown in FIG.

Fig. 8 is a diagram for explaining an example of a data layout of the payment support server 13. In detail, Fig. 8(A) shows an example of a store ID table indicating the ID (Identification) of a store where payment support is performed by the payment support server 13, Fig. 8(B) shows an example of a payment status table indicating the payment status used at the store, Fig. 8(C) shows an example of a payment method table indicating the payment methods available at the store, and Fig. 8(D) shows an example of a payment-related table at the store (a table indicating payments made at the store).
In the example shown in FIG. 8A, the ID of the store where payment support is provided by the payment support server 13 is "MC123456".
In the example shown in Figure 8 (B), the payment statuses set in a table with table ID "T01" located in a store with store ID "MC123456" are "unpaid,""paid,""overpaid," and "vacant."
In the example shown in Figure 8 (C), "XXPay", "□□Pay", and "△△Pay" are set as payment methods available at the store with store ID "MC123456", the payment method ID of the payment method name "XXPay" is set to "P01", the payment method ID of the payment method name "□□Pay" is set to "P02", and the payment method ID of the payment method name "△△Pay" is set to "P03".
In the example shown in Figure 8 (D), in a table with table ID "T01" located in a store with store ID "MC123456," a sequence number of "0001" is set for two payments made on February 2, 2020, and the first payment (XXXX Pay) with payment method ID "P01" has a payment amount of "5,000 yen" recorded, and the second payment (△△XXXX) with payment method ID "P03" has a payment amount of "10,000 yen" recorded.

Fig. 9 is a diagram for explaining an example of the data layout of the payment support server 13. In detail, Fig. 9(A) shows an example of a product ID table showing the IDs of products provided to customers at a store with a store ID of "MC123456", and Fig. 9(B) shows an example of an order details table showing details of products ordered in a table with a table ID of "T01" located in the store with the store ID of "MC123456". Fig. 9(C) shows an example of the first type payment code 12A1-1, the second type payment code 12A1-2, and the reference code 12A2 located on each table T01, T02, and T03 in the store.
In the example shown in FIG. 9A, the unit price of "beer" with product ID "S0001" is set to "500 yen", and the unit price of "sake" with product ID "S0002" is set to "1000 yen".
In the example shown in Figure 9 (B), in a table with table ID "T01" located in a store with store ID "MC123456", a sequence number "0001" is set for n product orders placed on February 2, 2020, the order quantity of "3" for the first product with product ID "S0001" is recorded, the order quantity of "1" for the second product with product ID "S0010" is recorded, the order quantity of "1" for the third product with product ID "S0005" is recorded, and the order quantity of "m" for the nth product with product ID "S9999" is recorded.
In the example shown in FIG. 9C, in the table T1, “QR01” is arranged as the first type payment code 12A1-1 used for a code payment service (e.g., “PayPay”) provided by a first payment company, “QR06” is arranged as the second type payment code 12A1-2 used for a code payment service (e.g., “Rakuten Pay”) provided by a second payment company, and “QR13” is arranged as the reference code 12A2 (also used for credit card payments). In the blue card T2, "QR02" is arranged as the first type payment code 12A1-1, "QR08" is arranged as the second type payment code 12A1-2, and "QR19" is arranged as the reference code 12A2, and in the table T3, "QR03" is arranged as the first type payment code 12A1-1, "QR07" is arranged as the second type payment code 12A1-2, and "QR14" is arranged as the reference code 12A2, and the data shown in Figure 9 (C) which records these is managed by the payment support server 13.

1, a user of the user terminal 11-1 and a user of the user terminal 11-2 make a payment using the payment code 12A1 displayed on the code display section 12A. In other words, the payment code 12A1 displayed on the code display section 12A is shared by the user of the user terminal 11-1 and the user of the user terminal 11-2.
First, when the payment code 12A1 is read by the user terminal 11-1, the user terminal 11-1 that has read the payment code 12A1 accepts payment by the user carrying the user terminal 11-1.
In detail, when the first type payment code 12A1-1 of the payment code 12A1 is read by the user terminal 11-1, the user terminal 11-1 accepts code payment (first type payment) provided by the first payment provider by the user carrying the user terminal 11-1.
Based on the total amount to be paid by the user of user terminal 11-1 and the user of user terminal 11-2 (e.g., "10,000 yen") and the amount accepted for payment by user terminal 11-1 (paid amount) (e.g., "6,000 yen"), payment support server 13 calculates the difference between the total amount and the paid amount (unpaid amount) (e.g., "4,000 yen" (=10,000 yen - 6,000 yen)). When reference code 12A2 is read by user terminal 11-1, user terminal 11-1 displays the unpaid amount calculated by payment support server 13 (e.g., "4,000 yen").

Next, when the payment code 12A1 is read by the user terminal 11-2, the user terminal 11-2 that has read the payment code 12A1 accepts payment by the user carrying the user terminal 11-2.
In detail, the user terminal 11-2 can read any payment code (e.g., the first type payment code 12A1-1, the second type payment code 12A1-2, the third type payment code 12A1-3, the fourth type payment code 12A1-4, etc.). For example, when the second type payment code 12A1-2 of the payment code 12A1 is read by the user terminal 11-2, the user terminal 11-2 accepts code payment (second type payment) provided by the second payment service provider by the user carrying the user terminal 11-2.
The payment support server 13 calculates the difference (unpaid amount) (e.g., "0 yen" (= 4000 yen - 4000 yen)) based on the amount to be paid by the user of user terminal 11-2 (e.g., "4000 yen") and the amount accepted for payment by user terminal 11-2 (paid amount) (e.g., "4000 yen").
When the reference code 12A2 is read by, for example, the user terminal 11-2, the user terminal 11-2 displays the unpaid amount calculated by the payment support server 13 (for example, "0 yen").
For example, when the payment support server 13 calculates the outstanding amount to be "0 yen," the user terminal 11-2 that reads the reference code 12A2 displays "0 yen" as the outstanding amount. Furthermore, when the payment support server 13 calculates the outstanding amount to be "0 yen," the payment support server 13 updates the information on whether the user of the user terminal 11-1 and the user of the user terminal 11-2 have completed payment to a status of "paid" (see FIG. 8(B)).
1, by sharing the payment code 12A1 for payments by multiple users, it is possible to avoid the hassle of preparing a payment code 12A1 for each user, and to promote the use of the payment support system 1. In addition, since it is not necessary to use multiple different payment codes for payments by multiple users, it is possible to improve user convenience.

1, after the user terminal 11-2 that reads the payment code 12A1 accepts a payment by the user carrying the user terminal 11-2, when the reference code 12A2 is read by, for example, the user terminal 11-2 of the user terminals 11-1 and 11-2, the user terminal 11-2 that read the reference code 12A2 displays the outstanding amount. When zero yen is displayed as the outstanding amount, the payment support server 13 generates a store exit code and transmits the data of the store exit code to the user terminal 11-2. As a result, the user terminal 11-2 becomes able to display the store exit code.
Next, when the store exit code reader 12B reads the store exit code displayed on the user terminal 11-2, the store exit gate 12C opens, allowing the users of the user terminals 11-1 and 11-2 to leave the store.
Furthermore, when the payment support server 13 calculates the unpaid amount as "0 yen", the receipt issuing unit 12D enters a state in which a receipt can be issued.
Furthermore, in the example shown in FIG. 1, the payment support server 13 executes an overpayment determination, which is a determination as to whether or not the paid amount is greater than the total amount.
In another example, the store management unit 12 does not have to include the store exit code reader 12B, the store exit gate 12C, the receipt issuing unit 12D, the store management terminal 12E, and the status notification unit 12F.

In the example shown in Figure 1, the payment support server 13 performs processing to manage the total amount to be paid by the user of user terminal 11-1 and the user of user terminal 11-2 who use the store, and information on whether or not payment by the user of user terminal 11-1 and the user of user terminal 11-2 has been completed.
When the payment code 12A1 is read by, for example, the user terminal 11-1 of the user terminals 11-1 and 11-2, the user terminal 11-1 that has read the payment code 12A1 performs a process of accepting payment by the user carrying the user terminal 11-1.
The payment support server 13 performs a process of calculating the difference between the total amount to be paid by the user of user terminal 11-1 and the user of user terminal 11-2 and the amount accepted for payment by user terminal 11-1 (paid amount) and the difference between the total amount and the paid amount (unpaid amount).
When the reference code 12A2 is read by the user terminal 11-1, the user terminal 11-1 performs a process of displaying the outstanding amount calculated by the payment support server 13.

FIG. 10 is a sequence diagram showing an example of a process executed when making a payment using payment code 12A1 (QR code) in payment support system 1 of the first embodiment and a payment service provider's system (external system).
10, in step S11, a user carrying user terminal 11-1 launches a payment application on user terminal 11-1. That is, in step S11, user terminal 11-1 launches the payment application.
Next, in step S12, the user terminal 11-1 goes into a Merchant Presented Mode (MPM), i.e., in step S12, the user terminal 11-1 becomes a device that reads the store's settlement code 12A1 (QR code).

Next, in step S13, the user reads the payment code 12A1 (QR code) using an application on the user terminal 11-1. That is, in step S13, the user terminal 11-1 reads the payment code 12A1 (QR code).
In step S14, the code display unit 12A displays the payment code 12A1 (QR code). In detail, in step S14, the code display unit 12A presents the payment code 12A1 (QR code) for stand-alone payment.

Next, in step S15, the user terminal 11-1 acquires store information by accessing the address indicated by the payment code 12A1 (QR code).
Next, in step S16, the user terminal 11-1 displays a payment screen (not shown).
Next, in step S17, the user inputs the payment amount. That is, in step S17, the user terminal 11-1 accepts input of the payment amount.
Next, in step S18, the user presses a "Pay" button (not shown). That is, in step S18, the user terminal 11-1 accepts the operation of the "Pay" button.

Next, in step S19, the server of the external system (the server of the payment service provider's system) accepts the payment.
Next, in step S20, the server of the external system transmits the amount paid by the user terminal 11-1 (accepted amount) to the payment support server 13.

Next, in step S21, the payment support server 13 receives (acquires) the amount (accepted amount) transmitted in step S20.
Next, in step S22, the payment support server 13 subtracts the amount already paid by the user terminal 11-1 (accepted amount) from the total amount to be paid by the user of the user terminal 11-1 and the user of the user terminal 11-2. That is, in step S22, the payment support server 13 calculates the difference between the total amount and the amount already paid (unpaid amount).

Next, the above-mentioned steps S11 to S22 are also executed for the payment made by the user terminal 11-2.
When the difference between the total amount and the paid amount (unpaid amount) becomes "0 yen", in step S23, the payment support server 13 ends the payment.

FIG. 11 is a sequence diagram showing an example of a process executed to confirm an unsettled amount (unpaid amount) in payment support system 1 of the first embodiment.
In the example shown in FIG. 11, in step S31, a user carrying the user terminal 11-1 launches a reference code reading application on the user terminal 11-1.
Next, in step S32, the reference code reading application of the user terminal 11-1 is started.

Next, in step S33, the user reads the reference code 12A2 (QR code) using a reference code reading application of the user terminal 11-1. That is, in step S33, the user terminal 11-1 reads the reference code 12A2 (QR code).
Also, in step S34, the code display unit 12A displays the reference code 12A2 (QR code).
Furthermore, in step S35, the user terminal 11-1 reads the address indicated by the reference code 12A2 (QR code).

Next, in step S36, the user terminal 11-1 accesses the address indicated by the reference code 12A2 (QR code).
Next, in step S37, the user terminal 11-1 requests the payment support server 13 for order history screen data, which is data used to display the order history screen including the outstanding amount.
Next, in step S38, the payment support server 13 transmits the order history screen data (contents) to the user terminal 11-1.
Next, in step S39, the user terminal 11-1 displays the order history screen.

FIG. 12 is a sequence diagram showing an example of a process executed at the time of credit card payment in payment support system 1 of the first embodiment and a payment service provider's system (external system).
In the example shown in Fig. 12, in step S41, the user of user terminal 11-1 selects a credit card to be used for credit card payment and operates the "Credit card payment" button (see Figs. 3 and 4). That is, in step S41, user terminal 11-1 requests payment screen data, which is data used to display the payment screen (see Fig. 5), from payment support server 13.
Next, in step S42, the payment support server 13 transmits payment screen data to the user terminal 11-1.
Next, in step S43, the user terminal 11-1 displays a payment screen.

Next, in step S44, the user of user terminal 11-1 inputs the information necessary for credit card payment. That is, in step S44, user terminal 11-1 accepts the input of the information necessary for credit card payment.
Specifically, in step S45, the user of user terminal 11-1 inputs the payment amount (see FIG. 5) In other words, in step S45, user terminal 11-1 accepts input of the payment amount.

Next, in step S46, the user presses the "Pay" button (see FIG. 5). That is, in step S46, the user terminal 11-1 accepts the operation of the "Pay" button.
Next, in step S47, the server of the external system (the server of the payment service provider's system) accepts the payment.
Next, in step S48, the server of the external system transmits the amount paid by the user terminal 11-1 (accepted amount) to the payment support server 13.
Next, in step S49, the payment support server 13 receives (acquires) the amount (accepted amount) transmitted in step S48.
Next, in step S50, the payment support server 13 subtracts the amount already paid by the user terminal 11-1 (accepted amount) from the total amount to be paid by the user of the user terminal 11-1 and the user of the user terminal 11-2. That is, in step S50, the payment support server 13 calculates the difference between the total amount and the amount already paid (unpaid amount).
When the difference between the total amount and the paid amount (unpaid amount) becomes "0 yen", in step S51, the payment support server 13 ends the payment.
Next, in step S52, the payment support server 13 may transmit a completion notification to the user terminal 11-1.

FIG. 13 is a flowchart for explaining an example of an overpayment determination and the like executed at the time of credit card payment in the payment support system 1 of the first embodiment.
In the example shown in Fig. 13, in step S51, the payment support server 13 judges the total amount. If the total amount is zero yen or more (if the unpaid amount is zero yen or more), the process proceeds to step S52. On the other hand, if the total amount is less than zero yen (i.e., if there is an overpayment), the process proceeds to step S58.
In step S58, the payment support server 13 determines that an error has occurred, and performs error processing (processing to deal with the error).

In step S52, the payment support server 13 causes the user terminal 11-1 to display a payment screen (see FIG. 5), and the user terminal 11-1 accepts input of the payment amount.
Next, in step S53, the payment support server 13 performs an overpayment determination. If the unpaid amount is equal to or greater than the payment amount input to the user terminal 11-1 (i.e., there is no overpayment), the process proceeds to step S54. On the other hand, if the unpaid amount is less than the payment amount input to the user terminal 11-1 (i.e., there is an overpayment), the process returns to step S52 and requests the user to re-input the payment amount.

In step S54, the payment support server 13 performs a subtraction process (a process of calculating the unpaid amount, which is the difference between the total amount and the paid amount).
Next, in step S55, the payment support server 13 performs an unpaid amount determination. If the unpaid amount is zero yen, the process proceeds to step S56. On the other hand, if the unpaid amount is greater than zero yen, the process proceeds to step S59.
In step S59, the payment support server 13 causes the unpaid amount to be displayed on the user terminal 11-1.

In step S56, the payment support server 13 performs processing to complete the payment, and the payment support server 13 changes the payment status from "unpaid" (see Figure 8 (B)) to "paid" (see Figure 8 (B)).
Next, in step S57, the table is cleared, and the payment support server 13 changes the payment status from "paid" to "vacant" (see FIG. 8(B)).

Figure 14 is a flowchart for explaining an example of an overpayment determination, etc., that is performed when a code payment other than a credit card payment is made in the first embodiment of the payment support system 1 (i.e., when the first type payment code 12A1-1, the second type payment code 12A1-2, the third type payment code 12A1-3 or the fourth type payment code 12A1-4 is read).
In the example shown in FIG. 14, in step S61, the payment support server 13 receives the payment amount (paid amount) made by the user terminal 11-1.
Next, in step S62, the payment support server 13 calculates the unpaid amount, which is the difference between the total amount to be paid by the user of the user terminal 11-1 and the amount paid by the user terminal 11-1 (amount already paid).

Next, in step S63, the payment support server 13 performs a payment determination (overpayment determination, underpayment determination).
If the unpaid amount is greater than zero yen, the process returns to step S61, and the payment support server 13 receives the payment amount (paid amount) made by the user terminal 11-2.
If the unpaid amount is zero yen, the process proceeds to step S64.
If the unpaid amount is less than zero yen (i.e., if there is an overpayment), the process proceeds to step S66.

In step S64, the payment support server 13 performs processing to complete the payment, and changes the payment status from "unpaid" to "paid."
Next, in step S65, the table is cleared, and the payment support server 13 changes the payment status from "paid" to "vacant."

In step S66, the payment support server 13 performs a refund process for the user terminal 11-1. Also in step S66, the payment support server 13 changes the payment status from "unpaid" to "overpaid" (see FIG. 8 (B)).

Second Embodiment
A second embodiment of the payment support system, the payment support method and the payment support server of the present invention will be described below.
Except for the points described below, the payment support system 1 of the second embodiment is configured similarly to the payment support system 1 of the first embodiment described above. Therefore, the payment support system 1 of the second embodiment can achieve the same effects as the payment support system 1 of the first embodiment described above, except for the points described below.

As described above, in payment support system 1 of the first embodiment, code display unit 12A is a printed matter on which payment code 12A1 and reference code 12A2 are printed.
On the other hand, in the payment support system 1 of the second embodiment, the code display unit 12A is a terminal device capable of displaying the payment code 12A1 and the reference code 12A2. The code display unit 12A as a terminal device is arranged in a store used by multiple users. In detail, the code display unit 12A as a terminal device is arranged, for example, at each table in the store used by multiple users.

FIG. 15 is a diagram showing an example of a screen of the code display unit 12A (terminal device) of the payment support system 1 of the second embodiment.
In the example shown in FIG. 15, the code display unit 12A displays a payment code 12A1 and a reference code 12A2 that can be read by a plurality of user terminals 11-1 and 11-2.
In the example shown in Fig. 15, the screen of the code display section 12A includes "Table number: T01". The screen of the code display section 12A also includes "Payment status: 'Unpaid'". The screen of the code display section 12A also includes "Unsettled balance: '10,000 yen'".
The screen of the code display section 12A also includes a "Check Order History" button and a "Check Payment History" button.

15 , when code display unit 12A receives a request to display the order history (i.e., when it receives an operation of the "Check Order History" button), it requests information indicating the order history from payment support server 13. Next, payment support server 13 transmits the information indicating the order history to code display unit 12A, and code display unit 12A displays the order history based on the information indicating the order history transmitted by payment support server 13.
That is, in the second embodiment of the payment support system 1, the order history as shown in FIG. 4 can be displayed not only on the user terminals 11-1 and 11-2, but also on the code display unit 12A (terminal device) located on each table in the store.

The payment support system 1 of the first or second embodiment can realize cashierless payment (reduced labor required for cash register operations) in a store without imposing a burden on a store such as a restaurant (i.e., at low cost), and can also realize cashless payment and split payment at each table.
In addition, in the payment support system 1 of the first or second embodiment, the store user can proactively perform the payment (clearance process), thereby reducing the time required for store operations. Furthermore, the store user can use a split payment function that is not dependent on a specific payment service (i.e., across multiple payment services).
In the above example, the payment support system 1 of the first or second embodiment is applied to splitting the bill among two people, but it is also possible to apply the payment support system 1 of the first or second embodiment to splitting the bill among three or more people.

FIG. 16 is a diagram showing an example of a system to which payment support system 1 of the second embodiment and a payment service provider's system (external system) are applied.
The "store terminal (tablet, etc.)" shown in Figure 16 corresponds to code display unit 12A of payment support system 1 of the second embodiment, the "payment system" shown in Figure 16 corresponds to payment support server 13 of payment support system 1 of the second embodiment, the "payment provider SV" shown in Figure 16 corresponds to the server of the payment provider's system (external system), the "user terminal" shown in Figure 16 corresponds to user terminal 11-1 of payment support system 1 of the second embodiment, the "QR code (for reference)" shown in Figure 16 corresponds to reference code 12A2 of payment support system 1 of the second embodiment, and the "QR code (compatible with multiple payments)" and "QR code (for single payment)" shown in Figure 16 correspond to first type payment code 12A1-1, second type payment code 12A1-2, etc. of code display unit 12A of payment support system 1 of the second embodiment.

Although the above describes the form for carrying out the present invention using the embodiments, the present invention is not limited to these embodiments in any way, and various modifications and substitutions can be made without departing from the scope of the present invention. The configurations described in the above-mentioned embodiments and examples may be combined as appropriate.

In addition, all or part of the functions of each unit of the payment support system 1 in the above-mentioned embodiment may be realized by recording a program for realizing these functions on a computer-readable recording medium, and reading and executing the program recorded on the recording medium into a computer system. Note that the "computer system" here includes hardware such as the OS and peripheral devices.
Furthermore, "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage units such as hard disks built into computer systems. Furthermore, "computer-readable recording medium" may also include those that dynamically hold a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and those that hold a program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in such cases. Furthermore, the above program may be one that realizes part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

1...Payment support system, 11-1...User terminal, 11-2...User terminal, 12...Store management unit, 12A...Code display unit, 12A1...Payment code, 12A1-1...First type of payment code, 12A1-2...Second type of payment code, 12A1-3...Third type of payment code, 12A1-4...Fourth type of payment code, 12A2...Reference code, 12B...Store exit code reader, 12C...Store exit gate, 12D...Receipt issuing unit, 12E...Store management terminal, 12F...Status notification unit, 13...Payment support server

Claims (15)

A payment support system comprising: a plurality of user terminals carried by a plurality of users; a code display unit that displays a payment code and a reference code read by the plurality of user terminals; and a payment support server,
the code display unit is arranged in a store used by the plurality of users,
the payment code and the reference code displayed on the code display unit are shared codes used by the multiple users,
the payment support server manages a total amount to be paid by the plurality of users who use the store and information on whether or not payment by the plurality of users has been completed;
When the payment code is read by any one of the plurality of user terminals,
The user terminal that reads the payment code accepts payment by a user carrying the user terminal that read the payment code,
the payment support server calculates an unpaid amount, which is the difference between the total amount and the paid amount, based on the total amount and the paid amount, which is the amount accepted for payment by the user terminal that read the payment code;
When the reference code is read by any one of the plurality of user terminals,
The user terminal that reads the reference code displays the unpaid amount calculated by the payment support server.
Payment support system. The plurality of users includes at least a first user and a second user;
The plurality of user terminals includes at least a first user terminal and a second user terminal;
After the first user terminal reads the payment code and accepts the payment by the first user,
When the payment code is read by the second user terminal,
The second user terminal accepts payment by the second user.
The payment support system according to claim 1. When the payment support server calculates the unpaid amount as zero yen,
The user terminal that reads the reference code displays zero yen as the unpaid amount,
The payment support server updates information on whether or not the payments by the multiple users have been completed to a status of "paid."
The payment support system according to claim 1. After the user terminal that reads the payment code accepts a payment by a user carrying the user terminal that read the payment code,
When the reference code is read by any one of the plurality of user terminals,
The user terminal that reads the reference code displays the outstanding amount,
If the unpaid amount is displayed as zero yen,
The payment support server generates a store exit code and transmits data of the store exit code to the user terminal that reads the reference code;
The user terminal that reads the reference code is then able to display the store exit code.
The payment support system according to claim 3. A store exit code reader that reads the store exit code;
Equipped with an exit gate,
When the store exit code reader reads the store exit code displayed on the user terminal that read the reference code,
The exit gate opens, allowing the multiple users to leave the store.
The payment support system according to claim 4. A receipt issuing unit is provided for issuing receipts,
When the payment support server calculates the unpaid amount as zero yen,
the receipt issuing unit is in a state where it is able to issue the receipt;
The payment support system according to claim 3. The payment code includes at least a first type payment code and a second type payment code,
When the first type payment code is read by any one of the plurality of user terminals, the user terminal that read the first type payment code accepts the first type payment by a user carrying the user terminal that read the first type payment code,
When the second type payment code is read by any one of the plurality of user terminals, the user terminal that reads the second type payment code accepts the second type payment by the user carrying the user terminal that read the second type payment code.
The payment support system according to claim 1. When the reference code is read by any one of the plurality of user terminals,
The user terminal that reads the reference code requests reference screen data, which is data used to display a reference screen, from the payment support server;
The payment support server transmits the reference screen data to the user terminal that reads the reference code,
The user terminal that reads the reference code displays the reference screen including the unpaid amount based on the reference screen data transmitted by the payment support server.
The payment support system according to claim 1. The code display unit is a printed matter on which the payment code and the reference code are printed.
The payment support system according to claim 1. The code display unit is a terminal device capable of displaying the payment code and the reference code.
The payment support system according to claim 1. When the reference code is read by any one of the plurality of user terminals,
the user terminal that reads the reference code displays the outstanding amount and accepts a request to display an order history from a user carrying the user terminal that read the reference code;
The user terminal that has received the display request for the order history requests information indicating the order history to the payment support server;
the payment support server transmits information indicating the order history to the user terminal that has accepted the request to display the order history;
the user terminal that has accepted the request to display the order history displays the order history based on the information indicating the order history transmitted by the payment support server.
The payment support system according to claim 10. The establishment includes a plurality of tables;
Equipped with a store management terminal that displays the payment status of each table;
The payment support system according to claim 1. The payment support server executes an overpayment determination, which is a determination as to whether the paid amount is greater than the total amount.
The payment support system according to claim 1. A payment support method for a payment support system including a plurality of user terminals carried by a plurality of users, a code display unit that displays a payment code and a reference code read by the plurality of user terminals, and a payment support server, comprising:
the code display unit is arranged in a store used by the plurality of users,
the payment code and the reference code displayed on the code display unit are shared codes used by the multiple users,
the payment support server managing information on a total amount to be paid by the plurality of users who use the store and whether or not the payment by the plurality of users has been completed;
When the payment code is read by any one of the plurality of user terminals, the user terminal that read the payment code accepts a payment by a user carrying the user terminal that read the payment code;
the payment support server calculates an unpaid amount, which is a difference between the total amount and the paid amount, based on the total amount and the paid amount, which is an amount accepted for payment by the user terminal that read the payment code;
and when the reference code is read by any one of the plurality of user terminals, the user terminal that reads the reference code displays the unpaid amount calculated by the payment support server.
Payment assistance methods. A payment support server provided in a payment support system including a plurality of user terminals carried by a plurality of users and a code display unit that displays a payment code and a reference code read by the plurality of user terminals,
the code display unit is arranged in a store used by the plurality of users,
the payment code and the reference code displayed on the code display unit are shared codes used by the multiple users,
the payment support server manages a total amount to be paid by the plurality of users who use the store and information on whether or not payment by the plurality of users has been completed;
When the payment code is read by any one of the plurality of user terminals, the user terminal that read the payment code accepts payment by a user carrying the user terminal that read the payment code,
the payment support server calculates an unpaid amount, which is the difference between the total amount and the paid amount, based on the total amount and the paid amount, which is the amount accepted for payment by the user terminal that read the payment code;
When the reference code is read by any one of the plurality of user terminals, the unpaid amount calculated by the payment support server is displayed by the user terminal that read the reference code.
Payment support server.

Images