JP2025056798A - Deposit system, display control method, and program - Google Patents

Abstract

To improve convenience of users who operate payment terminals.SOLUTION: A user identification information receiving unit (102) of a payment system (1) receives user identification information enabling identification of a user who operates a payment terminal (20) disposed at a location where the user comes, the payment terminal (20) for receiving payment operations relating to payable settlement means. A receivable amount calculation unit (104) calculates a receivable payment amount according to the user's maximum payment amount and total receivable amount for a predetermined period based on the user identification information. A display control unit (106) causes the payment terminal (20) to display the receivable amount. A payment request receiving unit (107) receives a payment request from the payment terminal (20) after the receivable amount has been displayed. A payment execution unit (108) executes the receiving of money when the payment request is received by the payment request receiving unit (107).SELECTED DRAWING: Figure 5

Description

This disclosure relates to a deposit system, a display control method, and a program.

Conventionally, electronic payments (cashless payments) using payment methods that allow deposits have become widespread. Users can also instruct deposits from a deposit terminal located at a specified location. For example, Patent Literature 1 describes an information processing system that executes deposits based on the amount of cash inserted by a user into an ATM (Automatic Teller Machine), which is an example of a deposit terminal, and the deposit amount entered by the user into the ATM.

JP 2020-046820 A

For example, some payment methods have a maximum deposit amount set for a certain period of time. With such payment methods, the user operating the deposit terminal needs to be aware of the maximum deposit amount when instructing the deposit. However, the technology in Patent Document 1 does not allow the user operating the ATM to be aware of the maximum deposit amount, and therefore does not sufficiently improve user convenience. This point is the same for other conventional technologies other than Patent Document 1.

One of the objectives of this disclosure is to improve the convenience of users who operate deposit terminals.

The deposit system according to the present disclosure is a deposit terminal that accepts deposit operations related to payment methods that can accept deposits, and includes a user identification information receiving unit that receives user identification information that can identify the user operating the deposit terminal that is placed in a location visited by the user, a depositable amount calculation unit that calculates the depositable amount based on the user's deposit upper limit and total deposit amount for a specified period based on the user identification information, a display control unit that causes the deposit terminal to display the depositable amount, a deposit request receiving unit that receives a deposit request from the deposit terminal after the depositable amount is displayed, and a deposit execution unit that executes the deposit when the deposit request is received by the deposit request receiving unit.

This disclosure can, for example, increase the convenience of users who operate deposit terminals.

FIG. 2 is a diagram illustrating an example of a hardware configuration of the deposit system of the first embodiment. FIG. 13 is a diagram showing an example of a state in which a user performs a deposit operation on a deposit terminal. FIG. 13 is a diagram showing an example of a screen displayed on a deposit terminal. FIG. 13 is a diagram illustrating an example of a screen displayed on a user terminal. A figure showing an example of a function realized by the deposit system of the first embodiment. FIG. 4 is a diagram illustrating an example of a user database. FIG. 13 is a diagram showing an example of a deposit amount input screen when the total deposit amount reaches the deposit upper limit. FIG. 13 is a diagram showing an example of a deposit amount input screen when the deposit amount is about to reach the upper deposit limit. A figure showing an example of a display according to the relationship between the first depositable amount and the second depositable amount. A diagram showing an example of a process executed in the deposit system of the first embodiment. FIG. 13 is a diagram illustrating an example of an OEM code screen according to the second embodiment. A diagram showing an example of a process executed in the deposit system of the second embodiment. FIG. 11 is a diagram showing an example of functions realized in a modified example of the first embodiment. FIG. 11 is a diagram illustrating an example of functions realized in a modified example of the second embodiment. FIG. 13 is a diagram showing an example of an OEM code screen on which bonus information is displayed.

[1. First embodiment]
A first embodiment, which is an example of an embodiment of a deposit system, a display control method, and a program according to the present disclosure, will be described.

[1-1. Hardware configuration of the deposit system of the first embodiment]
FIG. 1 is a diagram showing an example of the hardware configuration of the deposit system of the first embodiment. For example, the deposit system 1 includes a server 10, a deposit terminal 20, and a user terminal 30. Each of the server 10, the deposit terminal 20, and the user terminal 30 is connected to a network N such as the Internet or a LAN. In the example of FIG. 1, one each of the server 10, the deposit terminal 20, and the user terminal 30 is shown, but at least one of the server 10, the deposit terminal 20, and the user terminal 30 may be present in a plurality of units.

The server 10 is a server computer managed by a payment service provider. The payment service provider is a business that provides users with payment services related to electronic payments (cashless payments). In the first embodiment, the payment service provider manages payment methods that can be used for deposits. Depositing money means increasing the balance of a payment method. Recharge or remittance are examples of deposits. The first embodiment takes as an example a case where recharge corresponds to a deposit. Therefore, the words "deposit" in the first embodiment can be read as "recharge."

The payment method to be used for depositing money may be any type used in known payment services. For example, the payment method may be online electronic money, IC card electronic money, other electronic money than online and IC card types, prepaid cards not called electronic money, online prepaid cards, bank accounts, securities accounts, accounts at financial institutions other than banks and securities companies, accounts other than accounts at financial institutions, or other names for the payment method.

For example, the server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The storage unit 12 includes at least one of a volatile memory such as a RAM and a non-volatile memory such as a flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

The deposit terminal 20 is a computer operated by the user when depositing funds into a payment method. The deposit terminal 20 is a different computer from the user terminal 30. The deposit terminal 20 is managed by someone other than the user. In the first embodiment, the OEM (Original Equipment Manufacturing) client of the payment business entity manages the deposit terminal 20. The OEM client is a party that partners with the payment business entity. The deposit terminal 20 is placed at the OEM client's location. The payment business entity uses its own payment service system to develop the OEM client's payment service system. For example, the name of the OEM client's payment service includes the OEM client's name.

In the first embodiment, an example is taken of a supermarket operating company being an OEM client. For example, when a user uses the OEM client's payment service when shopping at the OEM client, the point allocation rate given as a benefit is higher than when a user uses the payment service of the payment business operator or another payment service when shopping at the OEM client. The OEM client's payment service may generate benefits other than the point allocation rate. In this case, when a user uses the OEM client's payment service when shopping at the OEM client, a benefit specific to the OEM client is granted. This allows the OEM client to carry out unique sales promotion activities.

Note that the OEM client may be any entity. The OEM client is not limited to a supermarket. For example, the OEM client may be a convenience store, a drug store, a restaurant, an accommodation facility, a transportation facility, a beauty salon, a financial institution, a local government, a municipality, or any other entity. The deposit terminal 20 may be located in a location related to the OEM client (e.g., a store or shopping mall), or may be located in a location that is not particularly related to the OEM client. The deposit terminal 20 may be located in each of multiple locations.

For example, the deposit terminal 20 is a charge machine, a POS terminal, a self-checkout terminal, an ATM, a personal computer, a tablet, or a smartphone. The deposit terminal 20 includes a control unit 21, a memory unit 22, a communication unit 23, an operation unit 24, a display unit 25, an input unit 26, a storage unit 27, and an output unit 28. The hardware configurations of the control unit 21, the memory unit 22, and the communication unit 23 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The deposit terminal 20 may include a reading device (e.g., a camera, a code reader, or a reader/writer) capable of reading a code or an IC chip.

For example, the operation unit 24 is an input device such as a touch panel or a mouse. The display unit 25 is a display such as an LCD or an organic EL display. The insertion unit 26 is a device that accepts the insertion of cash. The storage unit 27 is a device that stores the cash inserted from the insertion unit. Each of the insertion unit 26 and the storage unit 27 may be of a known configuration. The storage unit 27 may detect the number of at least one of the bills and coins stored therein using a sensor such as an optical sensor, an ultrasonic sensor, or a magnetic sensor. The output unit 28 is a printer that outputs receipts. The output unit 28 prints characters on receipt paper stored therein and outputs it.

The user terminal 30 is a user's computer. For example, the user terminal 30 is a smartphone, a tablet, a personal computer, or a wearable terminal. For example, the user terminal 30 includes a control unit 31, a memory unit 32, a communication unit 33, an operation unit 34, a display unit 35, and a photographing unit 36. The hardware configurations of the control unit 31, the memory unit 32, the communication unit 33, the operation unit 34, and the display unit 35 may be similar to those of the control unit 11, the memory unit 12, the communication unit 13, the operation unit 24, and the display unit 25, respectively. The photographing unit 36 includes at least one camera. The user terminal 30 may include an IC chip on which data related to a payment method is recorded. The payment method on which data is recorded in the IC chip of the user terminal 30 may correspond to the payment method in the first embodiment.

The programs stored in the storage units 12, 22, 32 may be supplied to the server 10, the deposit terminal 20, or the user terminal 30 via the network N. At least one of a reading unit (e.g., a memory cart slot) that reads a computer-readable information storage medium and an input/output unit (e.g., a USB port) for inputting and outputting data to and from an external device may be included in the server 10, the deposit terminal 20, or the user terminal 30. For example, a program stored in an information storage medium may be supplied to the server 10, the deposit terminal 20, or the user terminal 30 via at least one of the reading unit and the input/output unit.

In addition, the deposit system 1 only needs to include at least one computer. The computers included in the deposit system 1 are not limited to the example in FIG. 1. For example, the deposit system 1 may include only the server 10. In this case, the deposit terminal 20 and the user terminal 30 exist outside the deposit system 1. The deposit system 1 may include only the server 10 and the deposit terminal 20. In this case, the user terminal 30 exists outside the deposit system 1. The deposit system 1 may include only the server 10 and the user terminal 30. In this case, the deposit terminal 20 exists outside the deposit system 1. The deposit system 1 may include only other computers not shown in FIG. 1.

[1-2. Overview of the deposit system according to the first embodiment]
In the first embodiment, a business payment app of a payment business operator that manages payment means and an OEM payment app of an OEM client of the payment business operator are each installed on a user terminal 30. The business payment app is an application that allows a user to use the payment service of the payment business operator. The OEM payment app is an application that allows a user to use the payment service of the OEM client. The payment business operator develops the OEM payment app at the request of the OEM client.

In the first embodiment, it is assumed that the user has registered to use both the business payment app and the OEM payment app. The user uses the business payment app when making payments at entities affiliated with the payment service of the payment business (e.g., stores or accommodation facilities). The user uses the OEM payment app when making payments at an OEM client. The OEM payment app may be available only at the OEM client, or may be available at other stores and the like other than the OEM client. Hereinafter, when there is no need to distinguish between the business payment app and the OEM payment app, they will simply be referred to as the payment app.

In the first embodiment, an example is given of a case where online electronic money corresponds to the payment means. Furthermore, an example is given of a case where the payment means used by the user from the business payment app is the same as the payment means used by the user from the OEM payment app. In other words, the user does not have two payment means balances, one for the business payment app and one for the OEM payment app, but rather a single common balance is used by both the business payment app and the OEM payment app.

For example, the user registers a deposit method to be used for depositing funds into the business payment app. The deposit method is the payment method that serves as the source of funds when depositing funds. For example, the deposit method may be a credit card, a bank account, cryptocurrency, sales proceeds from an online flea market, or another payment method. The user can operate the business payment app to deposit funds into the payment method. The flow of deposits from the business payment app may be a well-known flow. The user may deposit funds into the payment method from a browser, rather than from the business payment app.

In the first embodiment, an example is given of a case where no deposit means is registered in the OEM payment app. Furthermore, in order for a user to make a deposit into a payment means from the OEM payment app, the user must visit a location where a deposit terminal 20 is located. For example, when a user visits a location where a deposit terminal 20 is located and makes a deposit using the OEM payment app, a special benefit specific to the OEM is granted to the user. The user performs a deposit operation on the deposit terminal 20 to make a deposit.

Figure 2 is a diagram showing an example of a user performing a deposit operation on the deposit terminal 20. For example, when the deposit terminal 20 detects that a user is approaching the deposit terminal 20 using a known sensor such as a human presence sensor, it displays a deposit menu screen SC1, which corresponds to the top page of the deposit terminal 20, on the display unit 25. On the deposit menu screen SC1, a button B10 is displayed which allows the user to select a business payment app, and a button B11 is displayed which allows the user to select an OEM payment app.

For example, even if a user has not registered a deposit method with the business payment app, the user can make a deposit based on the business payment app by selecting button B10 and inserting cash into the deposit section 26. The deposit flow after the user selects buttons B10 and B11 is the same for both. Below, an example of the deposit flow when the user selects button B11 is explained. After selecting button B11, the user follows the instructions on the deposit terminal 20 to operate each of the deposit terminal 20 and the OEM payment app to carry out the deposit procedure.

Figure 3 is a diagram showing an example of a screen displayed on the deposit terminal 20. For example, when a user selects button B11 on the deposit menu screen SC1 in Figure 2, the deposit terminal 20 causes the display unit 25 to display a code reading screen SC2 including an authentication code C20 used for authentication when making a deposit, as shown in the upper part of Figure 3. The authentication code C20 is an image generated based on a predetermined standard. The authentication code C20 may be any code. For example, the authentication code C20 may be a barcode, a two-dimensional code, or a combination of these.

For example, the authentication code C20 is generated based on temporary information generated by the server 10. Hereinafter, this information is referred to as code information. The authentication code C20 may be generated based on a URL for accessing a computer such as the server 10. The authentication code C20 may be generated based on multiple pieces of information such as code information, a URL, terminal identification information capable of identifying the deposit terminal 20, and other information. For example, the user operates the user terminal 30 following the instructions on the code reading screen SC2.

Figure 4 is a diagram showing an example of a screen displayed on the user terminal 30. For example, when a user starts the user terminal 30, the user terminal 30 displays a user menu screen SC5, which corresponds to the top page of the user terminal 30, on the display unit 35, as shown in the upper left of Figure 4. The user menu screen SC5 displays an icon I50 of the business payment app and an icon I51 of the OEM payment app. When the user selects the icon I51, the user terminal 30 displays an OEM code screen SC6, which corresponds to the top page of the OEM payment app, on the display unit 35, as shown in the upper right of Figure 4. Note that immediately after starting the OEM payment app, a screen other than the OEM code screen SC6 (for example, a screen of a flyer or coupon from the OEM) may be displayed. When the user selects a payment menu from the other screen, the OEM code screen SC6 may be displayed on the display unit 35.

For example, the OEM code screen SC6 displays a payment code C60 for the user to use as a payment method. The payment code C60 is an image generated based on a predetermined standard. The payment code C60 may be any code. For example, the payment code C60 may be a barcode, a two-dimensional code, or a combination of these. The payment code C60 is generated based on information different from the authentication code C20. The payment code C60 may include a URL for accessing a computer such as the server 10.

For example, the payment code C60 is generated based on user identification information that can identify the user in the OEM payment app. The user identification information may be generated each time the payment code C60 is displayed, or may be fixed information that does not change each time it is displayed. When the payment code C60 is read by a payment terminal such as a POS terminal or self-checkout at the OEM, the payment terminal obtains the user identification information from the payment code C60 and sends it to the server 10. The server 10 executes the payment using the balance of the user's payment method based on the user identification information received from the payment terminal. The flow of the payment using the payment code C60 may be a known flow.

For example, when the user selects button B61, as shown in the lower left of FIG. 4, the user terminal 30 displays modal M62 on the OEM code screen SC6, which prompts the user to read the authentication code C20. The user terminal 30 activates the image capture unit 36. The image capture unit 36 continuously captures images to generate captured images. The user terminal 30 displays the captured images generated by the image capture unit 36 on modal M62 or another screen.

For example, the user terminal 30 reads the authentication code C20 based on the captured image to obtain the code information. The user terminal 30 transmits the user identification information of the OEM payment app and the code information obtained from the authentication code C20 to the server 10. The server 10 can identify which user read the authentication code C20 based on the user identification information. The server 10 can identify which deposit terminal 20's authentication code C20 was read based on the code information.

For example, the server 10 performs authentication to confirm the validity of the code information received from the user terminal 30. If the authentication based on the code information is successful, the user terminal 30 receives data from the server 10 indicating that the authentication was successful. The user terminal 30 displays a message in modal M62 prompting the user to select button B21 displayed on the code reading screen SC2 of the deposit terminal 20, as shown in the lower right of Figure 4.

Returning to FIG. 3, the user selects button B21 on the code reading screen SC2. As shown in the center of FIG. 3, the deposit terminal 20 communicates with the server 10 and causes the display unit 25 to display a deposit amount input screen SC3 that prompts the user to insert cash into the input unit 26. For example, the deposit amount input screen SC3 displays the amount of cash inserted, the amount that can be deposited into the payment method, and the current balance of the payment method. The amount that can be deposited into the payment method is determined based on a predetermined upper deposit limit. In the first embodiment, it is assumed that the upper deposit limit per transaction and the upper deposit limit for a specified period are predetermined.

The specified period is the period for which the deposit limit is calculated. In the first embodiment, the specified period is taken as an example to be a month. The specified period may be any length. The specified period is not limited to a month. For example, the specified period may be a day, a week, a year, or another period. The specified period repeats. The deposit limit for a specified period is the upper limit of the total deposit amount for the specified period. The total deposit amount is the total deposit amount in the specified period. The total deposit amount is reset when the specified period has elapsed. The deposit limit may be common to all users, or may differ depending on the user. The deposit limit may be user-specifiable, or may be fixed so that the user cannot specify it.

For example, when the server 10 receives user identification information of the OEM payment app from the user terminal 30, it calculates the depositable amount based on the deposit limit and total deposit amount for a specified period. The depositable amount is the amount that the user can deposit from the deposit terminal 20. The depositable amount may be calculated based on a predetermined formula. The depositable amount may be calculated by subtracting the total deposit amount from the deposit limit, or, if at least one of the deposit limit and minimum deposit amount per transaction is set, it may be calculated based on at least one of them.

For example, suppose the upper limit on deposits during a specified period is 100,000 yen. Suppose the total amount deposited during the specified period is 78,000 yen. Suppose the upper limit on deposits per transaction is 30,000 yen. In this case, 22,000 yen, obtained by subtracting the total amount deposited from the upper limit on deposits during the specified period, is lower than the upper limit on deposits per transaction of 30,000 yen. In this case, the deposit terminal 20 displays 22,000 yen, obtained by subtracting the total amount deposited from the upper limit, as the amount that can be deposited on the deposit amount input screen SC3.

For example, suppose the upper limit on deposits in a specified period is 100,000 yen. Suppose the total amount of deposits in the specified period is 20,000 yen. Suppose the upper limit on deposits per transaction is 30,000 yen. In this case, 80,000 yen, obtained by subtracting the total amount of deposits from the upper limit on deposits in the specified period, is higher than the upper limit on deposits per transaction of 30,000 yen. In this case, the deposit terminal 20 displays the upper limit on deposits per transaction of 30,000 yen on the deposit amount input screen SC3 as the amount that can be deposited.

For example, suppose the upper limit on deposits during a specified period is 100,000 yen. Suppose the total amount of deposits during the specified period is 99,500 yen. Suppose the minimum amount of deposits per transaction is 1,000 yen. In this case, the upper limit on deposits during the specified period minus the total amount of deposits, or 500 yen, is lower than the minimum amount of deposits per transaction of 1,000 yen. In this case, the deposit terminal 20 displays 0 yen on the deposit amount input screen SC3 as the available amount of deposits.

For example, a user inserts cash into the insertion unit 26 up to the amount that can be deposited. When the user inserts cash and selects button B30, the deposit terminal 20 sends a deposit request to the server 10. If the deposit request is accepted, the server 10 executes the deposit. When the deposit is complete, the deposit terminal 20 displays a deposit completion screen SC4 indicating that the deposit has been completed on the display unit 35, as shown at the bottom of Figure 3. When the user selects button B40, the screen returns to the deposit menu screen SC1. When the user selects button B41, the deposit terminal 20 outputs a receipt indicating that the deposit has been completed.

As described above, the deposit system 1 of the first embodiment calculates the depositable amount based on the upper deposit limit and the total deposit amount for a specified period. The deposit system 1 causes the deposit terminal 20 to display the calculated depositable amount. In this way, the deposit system 1 is able to increase the convenience of the user operating the deposit terminal 20. The details of the first embodiment will be described below.

[1-3. Functions realized by the deposit system of the first embodiment]
FIG. 5 is a diagram showing an example of functions realized by the deposit system 1 of the first embodiment.

[1-3-1. Functions realized by the server]
For example, the server 10 includes a data storage unit 100, a code information transmission unit 101, a user identification information reception unit 102, an authentication execution unit 103, a depositable amount calculation unit 104, a depositable amount comparison unit 105, a display control unit 106, a deposit request reception unit 107, and a deposit execution unit 108. The data storage unit 100 is realized by the memory unit 12. Each of the code information transmission unit 101, the user identification information reception unit 102, the authentication execution unit 103, the depositable amount calculation unit 104, the depositable amount comparison unit 105, the display control unit 106, the deposit request reception unit 107, and the deposit execution unit 108 is realized by the control unit 11.

In the first embodiment, the flow in which a user operates the deposit terminal 20 to make a deposit is the same for both the business payment app and the OEM payment app. Therefore, the processes of the user identification information receiving unit 102, the depositable amount calculation unit 104, the display control unit 106, the deposit request receiving unit 107, and the deposit execution unit 108 can be executed regardless of whether the user uses the business payment app or the OEM payment app. The processes of the code information sending unit 101, the authentication execution unit 103, and the depositable amount comparison unit 105 can also be executed regardless of whether the user uses the business payment app or the OEM payment app. Note that the server 10 does not have to include the code information sending unit 101, the authentication execution unit 103, and the depositable amount comparison unit 105.

[Data storage unit]
The data storage unit 100 stores data necessary for providing a payment service to a user. For example, the data storage unit 100 stores a user database DB. In the first embodiment, an example is given in which data for the payment service of the business payment and data for the payment service of the OEM client are managed in the same user database DB, but these data may be managed in separate databases.

Figure 6 is a diagram showing an example of a user database DB. The user database DB is a database that stores various data related to the payment methods of each of multiple users. For example, the user database DB stores user identification information of the business payment app (user identification information in the payment service of the payment business), user identification information of the OEM payment app (user identification information in the payment service of the OEM), the balance of the payment method, the upper limit of deposits in a specified period, the total amount of deposits in a specified period, the second depositable amount which is the amount that can be deposited per time, and deposit history data.

In the first embodiment, an example is given in which the user identification information of the business payment app and the user identification information of the OEM payment app are different from each other, but they may be the same. That is, common user identification information may be used in the business payment app and the OEM payment app. When the data of the business payment service and the OEM client's payment service are managed in separate databases, it is assumed that the balances of the payment methods in each database are consistent.

The user identification information of the business payment app and the user identification information of the OEM payment app may each be information entered by the user at login, or may be information temporarily issued by the server 10. For example, the user identification information of the business payment app and the user identification information of the OEM payment app may each be a phone number, an email address, or other information. The user identification information of the business payment app and the user identification information of the OEM payment app may each be information that is coded in the business payment app and the OEM payment app, or may be information that is not specifically coded.

The balance of a payment method decreases when the payment method is used. The balance of a payment method increases when a deposit is made into the payment method. In the first embodiment, the business payment app and the OEM payment app each use a common balance, so when a user uses a payment method in each of the business payment app and the OEM payment app, the server 10 decreases the balance of the common payment method. When a user performs a deposit operation in each of the business payment app and the OEM payment app, the server 10 increases the balance of the common payment method.

The upper limit on deposits during a specified period and the second depositable amount, which is the amount that can be deposited per transaction, do not have to be stored in the user database DB. The upper limit on deposits during a specified period and the second depositable amount, which is the amount that can be deposited per transaction, may be stored in a location other than the user database DB in the data storage unit 100. The upper limit on deposits during a specified period and the second depositable amount, which is the amount that can be deposited per transaction, do not have to be stored for each user.

The deposit history data is data related to the deposit history of the payment method. The deposit history can also be referred to as the actual deposit results. For example, the deposit history data indicates the deposit date and time, the deposit amount, and the deposit method. For example, the deposit method is cash inserted into the deposit terminal 20, or a payment method that is the source of funds registered in the business payment app. When the deposit execution unit 108 described below executes a deposit to a user's payment method, it updates the deposit history data associated with the user's user identification information so that it indicates the deposit date and time, the deposit amount, and the deposit method of the deposit. The deposit execution unit 108 also updates the user's total deposit amount for a specified period. The server 10 resets the total deposit amount when a specified period has passed. The total deposit amount becoming 0 corresponds to resetting the total deposit amount.

The user database DB may store any data. The information stored in the user database DB is not limited to the example of FIG. 6. For example, the user database DB may store a password for a user to log in. The data stored in the data storage unit 100 is not limited to the above example. The data storage unit 100 can store any data. For example, the data storage unit 100 may store code information. The code information may be associated with the terminal identification information of the destination deposit terminal 20 and recorded in the data storage unit 100. The data storage unit 100 may store data (e.g., HTML data) required to display each screen of FIG. 4 on the user terminal 30.

[Code information transmission section]
The code information sending unit 101 sends code information to the deposit terminal 20. For example, when the user selects buttons B10 and B11 in FIG. 2, the deposit terminal 20 requests the server 10 to generate code information. When the server 10 accepts a request from the deposit terminal 20, it generates code information so that the code information does not overlap with code information sent to other deposit terminals 20. The code information may be in any format. For example, the code information may be letters, numbers, other symbols, or a combination of these. The code information may include terminal identification information that can identify the deposit terminal 20. An expiration date may be set for the code information. The server 10 records the code information and the terminal identification information of the destination deposit terminal 20 in association with each other in the data storage unit 100.

The program required to generate the code information is stored in the data storage unit 100. For example, the program may be a program for generating random numbers. The server 10 records the code information generated based on the program in the data storage unit 100. The code information transmission unit 101 transmits the code information to the deposit terminal 20. The server 10 may generate the code information before the user selects buttons B10 and B11. The code information transmission unit 101 may transmit the code information to the deposit terminal 20 before the user selects buttons B10 and B11.

[User Identification Information Receiving Unit]
The user identification information receiving unit 102 is a deposit terminal 20 that accepts deposit operations related to payment methods that can accept deposits, and receives user identification information that can identify a user operating the deposit terminal 20 that is located at a location visited by the user. A deposit operation is an operation performed for depositing money. The deposit operation accepted by the deposit terminal 20 may be any operation. In the example of Figures 2 and 3, the selection of buttons B10, B11, B21, B22, and B30 corresponds to a deposit operation. The deposit operation may be another operation. Note that in the example of the first embodiment, the deposit operation is performed not only on the deposit terminal 20 but also on the user terminal 30.

In the first embodiment, the user identification information receiving unit 102 receives user identification information and code information extracted from the authentication code C20 from the user terminal 30. The server 10 associates the user identification information and code information and records them in the data storage unit 100. For example, when a user reads the authentication code C20 with a business payment app, the user identification information receiving unit 102 receives from the user terminal 30 the user identification information of the business payment app and the code information extracted from the authentication code C20 read by the business payment app. When a user reads the authentication code C20 with an OEM payment app, the user identification information receiving unit 102 receives from the user terminal 30 the user identification information of the OEM payment app and the code information extracted from the authentication code C20 read by the OEM payment app.

The user identification information receiving unit 102 may receive user identification information from the deposit terminal 20. For example, the user may have the deposit terminal 20 read the payment code C60 displayed on the user terminal 30. In this case, the deposit terminal 20 transmits the user identification information extracted from the payment code C60 to the server 10. The user identification information receiving unit 102 receives the user identification information extracted from the payment code C60 from the deposit terminal 20. The deposit terminal 20 may read a code displayed on the business payment app and transmit the user identification information extracted from the code to the server 10. In these cases, the deposit terminal 20 does not need to display the authentication code C20. For this reason, the server 10 does not need to include the code information transmitting unit 101.

For example, the user may directly input user identification information to the deposit terminal 20 (e.g., manually or by voice input). The deposit terminal 20 transmits the user identification information input by the user to the server 10. The user identification information receiving unit 102 may receive the user identification information input by the user from the deposit terminal 20. As another example, the deposit terminal 20 may receive user identification information from the user terminal 30 by wireless communication. The deposit terminal 20 transmits the user identification information received from the user terminal 30 to the server 10. The user identification information receiving unit 102 may receive the user identification information received from the user terminal 30 from the deposit terminal 20.

[Authentication execution part]
The authentication execution unit 103 executes authentication based on the code information transmitted by the code information transmission unit 101. Authentication is a process of confirming the validity of the code information. In the first embodiment, the deposit terminal 20 displays an authentication code C20 based on the code information transmitted by the code information transmission unit 101. The authentication code C20 is read by the user terminal 30. The server 10 receives the code information from the user terminal 30, and the authentication execution unit 103 executes authentication based on the code information received from the user terminal 30.

For example, the authentication execution unit 103 executes authentication based on the code information transmitted by the code information transmission unit 101 and the code information received from the user terminal 30. If these pieces of code information match, the authentication execution unit 103 determines that the authentication has been successful. If these pieces of code information do not match, the authentication execution unit 103 determines that the authentication has failed. The success or failure of authentication may be determined based on other conditions than whether the code information matches. For example, if an expiration date is set for the code information, another condition may be that the code information is within the expiration date. Other conditions may also be present, such as, for example, variants 1-2 and 1-3 described below.

[Depositable amount calculation section]
The depositable amount calculation unit 104 calculates the depositable amount according to the user's upper limit and total deposit amount for a specified period based on the user identification information received by the user identification information receiving unit 102. For example, the depositable amount calculation unit 104 refers to the user database DB to obtain the deposit upper limit and total deposit amount associated with the user identification information. If the deposit upper limit is the same for all users, the deposit upper limit does not need to be stored in the user database DB. In this case, the depositable amount calculation unit 104 may refer to the deposit upper limit stored in a location other than the user database DB in the data storage unit 100. The depositable amount calculation unit 104 may calculate the depositable amount as the numerical value obtained by subtracting the total deposit amount from the deposit upper limit.

For example, if a deposit unit is set for deposits from the deposit terminal 20, the depositable amount calculation unit 104 may calculate the depositable amount as the quotient obtained by subtracting the total deposit amount from the upper deposit amount and dividing the result by the deposit unit. The quotient is an integer. In other words, any quotient after the decimal point is rounded down. The deposit unit is an amount that can be specified as the deposit amount. For example, if the deposit terminal 20 only accepts paper notes, the deposit unit is one thousand yen. If a deposit unit is set, deposits can be made in natural number multiples of the deposit unit. For example, suppose the deposit unit is one thousand yen. Suppose the upper deposit limit is one hundred thousand yen. Suppose the total deposit amount is ninety-five hundred yen. In this case, the value obtained by subtracting the total deposit amount from the upper deposit amount is nine thousand five hundred yen. Since the deposit unit is one thousand yen, the depositable amount is nine thousand yen.

[Depositable Amount Comparison Section]
The depositable amount comparison unit 105 compares the first depositable amount, which is the depositable amount calculated by the depositable amount calculation unit 104, with the second depositable amount, which is the amount that can be deposited from the deposit terminal 20 per time. For example, the depositable amount comparison unit 105 refers to the user database DB to obtain the second depositable amount. If the second depositable amount is the same for all users, the second depositable amount does not need to be stored in the user database DB. In this case, the depositable amount comparison unit 105 can refer to the second depositable amount stored in a location other than the user database DB in the data storage unit 100.

For example, the depositable amount comparison unit 105 determines which of the first depositable amount and the second depositable amount is lower. That is, the depositable amount comparison unit 105 determines which of the first depositable amount and the second depositable amount is lower. The depositable amount comparison unit 105 may also determine which of the first depositable amount and the second depositable amount is higher. Furthermore, if the second depositable amount is not specifically set, the server 10 does not include the depositable amount comparison unit 105. That is, there may be no upper limit set on the amount of deposit from the deposit terminal 20.

[Display control unit]
The display control unit 106 causes the deposit terminal 20 to display the available deposit amount calculated by the available deposit amount calculation unit 104. Displaying the available deposit amount means displaying information that allows the available deposit amount to be identified. The display control unit 106 may cause the deposit terminal 20 to display a numerical value that indicates the available deposit amount, or may cause the deposit terminal 20 to display an image such as an icon that allows the available deposit amount to be identified. The available deposit amount may be displayed in any manner that is visually identifiable by the user.

For example, the display control unit 106 causes the deposit terminal 20 to display the available deposit amount by transmitting data indicating the available deposit amount calculated by the available deposit amount calculation unit 104 to the deposit terminal 20. In the example of FIG. 3, the data is data necessary for displaying the deposit amount input screen SC3. The data may also indicate other information such as the current balance of the payment method. The data may be in any format as long as it is information that is used to display some information on the deposit terminal 20.

Figure 7 is a diagram showing an example of the deposit amount input screen SC3 when the total deposit amount reaches the deposit upper limit. When the total deposit amount reaches the deposit upper limit, it means that the total deposit amount becomes the same as the deposit upper limit. For example, when the total deposit amount reaches the deposit upper limit, the display control unit 106 causes the deposit terminal 20 to display that the total deposit amount has reached the deposit upper limit and the time when deposits will again be possible. In the example of Figure 7, the display control unit 106 causes the deposit terminal 20 to display a message indicating that the total deposit amount has reached the deposit upper limit. The display control unit 106 may also cause the deposit terminal 20 to display that the depositable amount is 0 yen, thereby displaying that the total deposit amount has reached the deposit upper limit.

The period during which deposits can be made is the next specified period following the specified period to which the current time belongs. For example, the display control unit 106 may display the first day of the next specified period following the specified period to which the current time belongs as the period during which deposits can be made. The display control unit 106 may display other days included in the period during which deposits can be made. If the specified period is a month as in the first embodiment, the period during which deposits can be made is the next month. For example, the display control unit 106 may display the first day of the next month as the period during which deposits can be made. If the specified period is a day, the period during which deposits can be made is the next day. If the specified period is a week, the period during which deposits can be made is the next week. The display control unit 106 causes the deposit terminal 20 to display these by transmitting data indicating that the total deposit amount has reached the upper deposit limit and the period during which deposits can be made to the deposit terminal 20.

Figure 8 is a diagram showing an example of the deposit amount input screen SC3 when the deposit amount is about to reach the deposit upper limit. The deposit amount is about to reach the deposit upper limit when the total deposit amount is less than the deposit upper limit and the value obtained by subtracting the total deposit amount from the deposit upper limit is less than a threshold. The threshold may be a predetermined value. For example, the threshold may be the same as the deposit unit. For example, the state in which the deposit amount has not reached the deposit upper limit but deposits cannot be made may correspond to the state in which the deposit amount is about to reach the deposit upper limit. The state in which the deposit amount has not reached the deposit upper limit and deposits are possible but only an amount less than the threshold may correspond to the state in which the deposit amount is about to reach the deposit upper limit.

For example, when the total deposit amount is less than the deposit upper limit and the deposit of the minimum deposit amount cannot be executed at the deposit terminal 20, the display control unit 106 causes the deposit terminal 20 to display that the total deposit amount has reached the deposit upper limit and the time when deposits will be possible again. The display control unit 106 causes the deposit terminal 20 to display that the total deposit amount has reached the deposit upper limit and the time when deposits will be possible again by transmitting data to the deposit terminal 20 indicating that the total deposit amount has reached the deposit upper limit and the time when deposits will be possible again. For example, if a user is able to make deposits in units of 1 yen from the business payment app, in the state of FIG. 8, the user cannot make deposits from the deposit terminal 20 but can make deposits from the business payment app.

Note that the meaning of the total deposit amount reaching the deposit upper limit in FIG. 8 and the total deposit amount reaching the deposit upper limit in FIG. 7 are different from each other. The total deposit amount reaching the deposit upper limit means that the total deposit amount has not reached the deposit upper limit at the present time, but there is a possibility that the total deposit amount will reach the deposit upper limit in the future. In the example of FIG. 8, the display control unit 106 causes the deposit terminal 20 to display a message indicating that the total deposit amount will reach the deposit upper limit. The display control unit 106 may also cause the deposit terminal 20 to display that the available deposit amount is 0 yen, thereby displaying that the total deposit amount has reached the deposit upper limit.

Figure 9 is a diagram showing an example of a display according to the relationship between the first and second depositable amounts. For example, the display control unit 106 causes the deposit terminal 20 to display the lower of the first and second depositable amounts based on the comparison results of the depositable amount comparison unit 105. In the example at the top of Figure 9, since the first depositable amount (e.g., 22,000 yen) is lower than the second depositable amount (e.g., 30,000 yen), the display control unit 106 causes the deposit terminal 20 to display the first depositable amount without displaying the second depositable amount.

In the lower example of FIG. 9, because the second depositable amount (e.g., 30,000 yen) is lower than the first depositable amount (e.g., 45,000 yen), the display control unit 106 causes the deposit terminal 20 to display the second depositable amount without displaying the first depositable amount. When the first depositable amount and the second depositable amount are the same amount, the display control unit 106 causes the deposit terminal 20 to display the amount that is both the first depositable amount and the second depositable amount.

The display control unit 106 may cause the deposit terminal 20 to display both the first depositable amount and the second depositable amount, regardless of whether the first depositable amount and the second depositable amount are higher or lower. In this case, the server 10 may not include the depositable amount comparison unit 105.

For example, if authentication by the authentication execution unit 103 is successful, the display control unit 106 causes the deposit terminal 20 to display the depositable amount. If authentication by the authentication execution unit 103 is unsuccessful, the display control unit 106 does not cause the deposit terminal 20 to display the depositable amount. Note that the display control unit 106 may cause the deposit terminal 20 to display the depositable amount regardless of whether authentication by the authentication execution unit 103 is successful or not.

[Deposit request receiving section]
The deposit request receiving unit 107 receives a deposit request from the deposit terminal 20 after the available deposit amount has been displayed. The deposit request is predetermined data for requesting execution of a deposit. The deposit request may be in a format defined by an API or the like. The deposit request may include any information. For example, the deposit request may include the deposit amount, terminal identification information of the deposit terminal 20, code information, or other information. Information such as the deposit amount may not be included in the deposit request, but may be information attached to the deposit request.

In the first embodiment, the case where the deposit from the deposit terminal 20 is made in cash is taken as an example, but the deposit from the deposit terminal 20 may be made in a form other than cash. For example, the deposit from the deposit terminal 20 may be made using a deposit means such as a credit card or a point card. In this case, the deposit terminal 20 includes a device that reads the deposit means such as a credit card or a point card. The user causes the deposit terminal 20 to read the deposit means such as a credit card or a point card. The deposit request may include information related to the deposit means such as a credit card or a point card (for example, a credit card number or a point card number). This information may be information that is not included in the deposit request, but is attached to the deposit request.

[Deposit Execution Department]
The deposit execution unit 108 executes a deposit when a deposit request is received by the deposit request receiving unit 107. The deposit execution unit 108 executes a deposit by increasing the balance of the payment means stored in the user database DB by the deposit amount included in the deposit request. By recording the user identification information and the code information in association with each other in the data storage unit 100, the server 10 can identify which user's payment means to deposit when a deposit request is received from which deposit terminal 20.

The deposit process can use publicly known processes. When a deposit method such as a credit card or a point card is used, the deposit execution unit 108 executes the settlement process for the deposit based on the deposit method such as the credit card or point card. The deposit execution unit 108 may also execute a deposit when the user instructs the deposit from the business payment app. This deposit can also use publicly known processes.

[1-3-2. Functions realized by the deposit terminal]
For example, the deposit terminal 20 includes a data storage unit 200, a transmission unit 201, a reception unit 202, and a display control unit 203. The data storage unit 200 is realized mainly by the storage unit 22. Each of the transmission unit 201, the reception unit 202, and the display control unit 203 is realized mainly by the control unit 21.

[Data storage unit]
The data storage unit 200 stores data necessary for depositing money. For example, the data storage unit 200 stores code information received from the server 10 and terminal identification information of the deposit terminal 20. The data storage unit 200 stores data necessary for displaying each screen of Fig. 2 and Fig. 3. The data storage unit 200 stores data indicating the amount of cash inserted from the insertion unit 26. In the first embodiment, a case is taken as an example in which the amount corresponds to the deposit amount, but the deposit amount may be input by the user from the operation unit 24 of the deposit terminal 20.

[Transmitter]
The transmitting unit 201 transmits a deposit request to the server 10. For example, the transmitting unit 201 specifies the amount of cash inserted through the insertion unit 26 as the deposit amount. The transmitting unit 201 transmits the deposit request including the deposit amount and terminal identification information to the server 10. The transmitting unit 201 may transmit data other than the deposit request to the server 10.

[Receiver]
The receiving unit 202 receives the code information from the server 10. The receiving unit 202 may receive data other than the code information from the server 10. For example, the receiving unit 202 may receive data from the server 10 indicating that the deposit has been completed.

[Display control unit]
The display control unit 203 causes a screen for accepting a deposit operation to be displayed on the display unit 25. For example, the display control unit 203 causes the display unit 25 to display each of the screens shown in Figs.

[1-3-3. Functions realized by user terminal]
For example, the user terminal 30 includes a data storage unit 300, an operation reception unit 301, and a display control unit 302. The data storage unit 300 is realized mainly by the storage unit 32. The operation reception unit 301 and the display control unit 302 are realized mainly by the control unit 31.

[Data storage unit]
The data storage unit 300 stores data necessary for deposit. For example, the data storage unit 300 stores a business operator payment app and an OEM payment app. Deposits can be made from either the business operator payment app or the OEM payment app. The data storage unit 300 may store user identification information of the business operator payment app and user identification information of the OEM payment app.

[Operation reception section]
The operation reception unit 301 receives various operations by the user. For example, when the user performs some operation on the business payment app or the OEM payment app, the operation reception unit 301 transmits data indicating the operation to the server 10.

[Display control unit]
The display control unit 302 causes various screens to be displayed on the display unit 35. For example, the display control unit 302 causes the display unit 35 to display each of a user menu screen SC5, an OEM code screen SC6, and a screen of a business payment application.

[1-4. Processing Executed in the Deposit System of the First Embodiment]
Fig. 10 is a diagram showing an example of a process executed in the deposit system 1 of the first embodiment. The control units 11, 21, and 31 execute programs stored in the storage units 12, 22, and 32, respectively, to execute the process in Fig. 10.

As shown in FIG. 10, the deposit terminal 20 displays the deposit menu screen SC1 on the display unit 25 (S1). Here, the process when the user selects the button B11 will be described. When the user selects the button B11, the deposit terminal 20 requests the server 10 to generate code information (S2). When the server 10 receives the request to generate code information (S3), it generates code information and sends it to the deposit terminal 20 (S4). The deposit terminal 20 receives the code information from the server 10 (S5). The deposit terminal 20 generates an authentication code C20 based on the code information, and displays a code reading screen SC2 including the authentication code C20 on the display unit 25 (S6).

When the user operates the user terminal 30 to start up the user terminal 30, the user terminal 30 displays a user menu screen SC5 on the display unit 35 (S7). When the user selects icon I51, the user terminal 30 starts the OEM payment app and, while communicating with the server 10, displays an OEM code screen SC6 including the payment code C60 on the display unit 35 (S8). In S8, the user terminal 30 may communicate with the server 10 to obtain new user identification information. When the user selects button B61, the user terminal 30 displays a modal M62 on the display unit 35 that prompts the user to read the authentication code C20 by following the instructions on the deposit terminal 20 (S9).

The user terminal 30 activates the photographing unit 36 and acquires the code information from the authentication code C20 (S10). The user terminal 30 transmits the user identification information stored in the memory unit 32 and the code information acquired in S10 to the server 10 (S11). The server 10 receives the user identification information and the code information from the user terminal 30 (S12). The server 10 performs authentication based on the code information generated in S4 and the code information received in S12 (S13). If authentication fails in S13 (S13: Failed), this process ends. In this case, an error message may be displayed on at least one of the deposit terminal 20 and the user terminal 30.

If authentication is successful in S13 (S13: Success), the server 10 executes processing between the user terminal 30 to control the display of modal M62 so as to prompt the user to select "Next" indicated by button B21 (S14). In S14, the server 10 transmits data indicating that authentication was successful to the user terminal 30. Upon receiving the data, the user terminal 30 displays the modal M62 indicating that the user is prompted to select button B21.

When the user selects button B21, the deposit terminal 20 sends a display request for the deposit amount input screen SC3 to the server 10 (S15). When the server 10 receives the display request from the deposit terminal 20 (S16), it calculates the depositable amount based on the user database DB (S17). The server 10 executes processing between the deposit terminal 20 and the server 10 to display the deposit amount input screen SC3 including the depositable amount (S18).

The deposit terminal 20 accepts the insertion of cash by the user (S19). When the user selects button B30, the deposit terminal 20 sends a deposit request to the server 10 (S20). When the server 10 receives the deposit request from the deposit terminal 20 (S21), it executes the deposit (S22). The server 10 executes processing between the deposit terminal 20 and the server 10 to display a deposit completion screen SC4 (S23), and this processing ends. When the user selects button B10, the same processing as S2 to S23 is executed, although it differs as to whether the authentication code C20 is read by the OEM payment app or the business payment app.

[1-5. Summary of the first embodiment]
The deposit system 1 of the first embodiment receives user identification information capable of identifying a user who operates the deposit terminal 20. The deposit system 1 calculates the depositable amount according to the user's deposit upper limit and total deposit amount for a predetermined period based on the user identification information. The deposit system 1 causes the deposit terminal 20 to display the depositable amount. After the depositable amount is displayed, the deposit system 1 receives a deposit request from the deposit terminal 20. When the deposit request is received, the deposit system 1 executes the deposit. This allows the deposit system 1 to improve the convenience of the user who operates the deposit terminal 20. For example, it is possible to prevent a user from attempting to deposit more than the depositable amount, resulting in an error in the deposit. It is possible to prevent a user from inserting cash into the deposit terminal 20 in excess of the depositable amount. Since it is possible to prevent unnecessary deposit requests that result in an error from being sent to the server 10, the server 10 does not execute unnecessary processing, and the processing load of the server 10 can be reduced.

In addition, when the total amount of deposits reaches the upper deposit limit, the deposit system 1 displays on the deposit terminal 20 that the total amount of deposits has reached the upper deposit limit, and the time when deposits will again be possible. This allows the deposit system 1 to let the user know that deposits are currently not possible and when the next deposit will be possible, thereby further improving user convenience.

In addition, when the total deposit amount is less than the upper deposit limit and the deposit of the minimum deposit amount at the deposit terminal is not possible, the deposit system 1 displays on the deposit terminal 20 that the total deposit amount has reached the upper deposit limit and the time when deposits will again be possible. This allows the user to understand that although the total deposit amount has not reached the upper deposit limit, deposits are currently not possible and when the next deposit will be possible, thereby further improving user convenience.

In addition, the deposit system 1 displays the lower of the first and second depositable amounts on the deposit terminal 20 based on the comparison result between the first depositable amount, which is the depositable amount calculated by the depositable amount calculation unit 104, and the second depositable amount per transaction possible from the deposit terminal. This allows the deposit system 1 to present the accurate depositable amount to the user, thereby further improving user convenience.

The deposit system 1 also receives user identification information and code information from the user terminal 30 that reads the authentication code C20 displayed on the deposit terminal 20. The deposit system 1 performs authentication based on the code information. If authentication is successful, the deposit system 1 causes the deposit terminal 20 to display the amount that can be deposited. This allows the deposit system 1 to prevent erroneous or fraudulent deposits to be made to the payment means of a third party other than the user operating the user terminal 30 that read the authentication code C20.

The deposit system 1 also transmits code information to the deposit terminal 20. The deposit terminal 20 displays an authentication code C20 based on the transmitted code information. The deposit system 1 performs authentication based on the transmitted code information and the code information received from the user terminal 30. When the deposit terminal 20 generates code information, there is a possibility that the code information may overlap with code information generated by other deposit terminals 20, resulting in erroneous authentication; however, by the deposit system 1 transmitting code information to the deposit terminal 20, erroneous authentication can be prevented.

In addition, the business operator payment app and the OEM payment app are each installed on the user terminal 30. The deposit terminal 20 is placed at the OEM's location. Deposits can be made from either the business operator payment app or the OEM payment app. The processes of the user identification information receiving unit 102, the depositable amount calculation unit 104, the display control unit 106, the deposit request receiving unit 107, and the deposit execution unit 108 can be executed regardless of whether the user uses the business operator payment app or the OEM payment app. As a result, the deposit system 1 allows the user to use either the business operator payment app or the OEM payment app of their choice when making a deposit from the deposit terminal 20, thereby further improving user convenience.

[2. Second embodiment]
Next, a second embodiment, which is an example of another embodiment according to the present disclosure, will be described. In the second embodiment, a case where a deposit is made in the same manner as in the first embodiment will be described as an example. However, in the second embodiment, a deposit may be made in a manner different from that in the first embodiment. This will be described later. In the second embodiment, a description of the same points as in the first embodiment will be omitted. Note that the deposit in the second embodiment may be not only a charge as in the first embodiment, but also a transfer between users. In other words, a display such as that in FIG. 11 described later may be displayed when a transfer between users is made, not just a charge.

Figure 11 is a diagram showing an example of the OEM code screen SC6 of the second embodiment. For example, when a deposit is made in the same manner as in the first embodiment, the user terminal 30 displays deposit execution information I63 indicating that the deposit has been completed on the OEM code screen SC6. In the example of Figure 11, the deposit execution information I63 is a message indicating that the deposit has been made. The deposit execution information I63 may be any information. For example, the deposit execution information I63 may be an icon, window, modal, push notification, or other image indicating that the deposit has been made.

The deposit execution information I63 may include information other than the message indicating that the deposit has been made. For example, the deposit execution information I63 may include the deposit amount, the benefits granted to the user as a result of the deposit, the deposit date and time, the deposit location, or a combination of these. The deposit execution information I63 does not have to include a message indicating that the deposit has been made. The deposit execution information I63 may be displayed on the same OEM code screen SC6 as the payment code C60. For example, when the payment code C60 is displayed on the OEM code screen SC6 and the user scrolls the OEM code screen SC6, the deposit execution information I63 may be displayed.

As described above, the deposit system 1 of the second embodiment displays the deposit execution information I63 on the same screen as the OEM code screen SC6 on which the payment code C60 is displayed. In the second embodiment, the OEM code screen SC6 is the screen that is displayed immediately after the OEM payment app is launched (the so-called first view screen), so it is a screen that is easy for the user to notice. With the notification function within the app (for example, a notification displayed from a bell-shaped icon), it may be difficult for the user to notice that a deposit has been made, but the deposit system 1 displays the deposit execution information I63 on such an OEM code screen SC6, making it easier for the user to notice that a deposit has been made. In this way, the deposit system 1 is designed to increase convenience for users who use the OEM payment app. Details of the second embodiment will be explained below.

[2-1. Functions realized by the deposit system of the second embodiment]
Hereinafter, an example will be given in which the functions of FIG. 5 are realized in the same manner as in the first embodiment. However, some of the individual functions are different from those in the first embodiment. Note that the deposit system 1 of the second embodiment may not include all or some of the functions described in the first embodiment. For example, the deposit system 1 of the second embodiment may include only the display control unit 106 and the deposit execution unit 108, and may not include other functions.

[2-1-1. Functions realized by the server]
For example, the data storage unit 100, the code information transmission unit 101, the depositable amount comparison unit 105, the authentication execution unit 103, and the depositable amount calculation unit 104 may be similar to those in the first embodiment.

In the second embodiment, as in the first embodiment, the flow in which a user operates the deposit terminal 20 to make a deposit is the same for both the business payment app and the OEM payment app. Therefore, the processing of the display control unit 106 and the deposit execution unit 108 can be executed regardless of whether the user uses the business payment app or the OEM payment app. The processing of other functions can also be executed regardless of whether the user uses the business payment app or the OEM payment app. For example, in the second embodiment, a deposit means may be registered in the OEM payment app. In this case, deposit from the OEM payment app may be completed simply by operating the user terminal 30.

The server 10 may not include the code information sending unit 101, the user identification information receiving unit 102, the authentication executing unit 103, the depositable amount calculating unit 104, the depositable amount comparing unit 105, and the deposit request receiving unit 107. For example, in the second embodiment, auto-charge may correspond to a deposit. In this case, the server 10 does not receive a deposit request from the deposit terminal 20 or the user terminal 30, so it may not include the deposit request receiving unit 107. A transfer between users may correspond to a deposit. In this case, instead of a deposit from the deposit terminal 20, a deposit is made from the user terminal 30 of a user other than the user receiving the transfer.

[Display control unit]
The display control unit 106 causes the OEM payment app installed in the user terminal 30 of the user to display a payment code C60 for payment based on a payment method that can receive the deposit. The display control unit 106 may also cause the business payment app to display a code for payment. That is, the display control unit 106 may cause the payment app to display a code for payment. Hereinafter, a process in which the display control unit 106 displays the OEM code screen SC6 will be given as an example, but the display control unit 106 may also display a screen of another payment app.

For example, the display control unit 106 causes the OEM payment app to display the payment code C60 by transmitting data for displaying the payment code C60 to the user terminal 30. The display control unit 106 causes the OEM payment app to display the OEM code screen SC6 by transmitting data for the OEM code screen SC6 including the payment code C60 to the user terminal 30. When a deposit is made, the display control unit 106 causes the OEM code screen SC6, on which the payment code C60 is displayed, to display deposit execution information I63 regarding the execution of the deposit. The data for the OEM code screen SC6 includes the deposit execution information I63.

OEM code screen SC6 is an example of a code screen of a payment app. Therefore, any part describing OEM code screen SC6 can be read as code screen. The code screen is a screen that includes a code generated based on information for payment. The code screen may be a screen of any payment app. The code screen is not limited to OEM code screen SC6. For example, the code screen may be a screen on which a code for payment is displayed in a business payment app. The code screen may be a screen of a payment app other than a business payment app and an OEM payment app.

For example, the display control unit 106 determines whether a new deposit has been made to a user based on the deposit history data stored in the user database DB. In the second embodiment, the deposit history data shows not only recharges but also the history of other deposits, such as transfers between users. That is, the server 10 updates the deposit history data even when other deposits, such as transfers between users, are made. Each deposit is associated with display presence/absence information that indicates whether the deposit execution information I63 has been displayed in the OEM payment app.

For example, when the display control unit 106 receives a display request for the OEM code screen SC6 from the user terminal 30, it determines whether or not there are any undisplayed deposits based on the display presence/absence information. If the display control unit 106 does not determine that there are any undisplayed deposits, it does not display the deposit execution information I63 on the OEM code screen SC6. If the display control unit 106 determines that there are any undisplayed deposits, it does not display the deposit execution information I63 on the OEM code screen SC6. If there are multiple undisplayed deposits, the display control unit 106 may display the deposit execution information I63 for all of the deposits on the OEM code screen SC6, or may display the deposit execution information I63 for only some of the deposits on the OEM code screen SC6.

The display control unit 106 may display the deposit execution information I63 indicating the deposit made from the business payment app on the OEM code screen SC6. Conversely, the display control unit 106 may display the deposit execution information I63 indicating the deposit made from the OEM payment app on a code screen including a code in the business payment app.

[User Identification Information Receiving Unit]
The user identification information receiving unit 102 receives user identification information from the OEM payment app that can identify a user who operates the deposit terminal 20 that accepts deposit operations related to deposits and is located at a place visited by the user. The user identification information may be received from a business payment app. The processing of the user identification information receiving unit 102 may be the same as that of the first embodiment. When remittance between users is performed, the user identification information receiving unit 102 may receive user identification information from the user terminal 30 of the remittance source user. In this case, the user identification information receiving unit 102 may receive user identification information of the remittance source user and user identification information of the remittance destination user from the user terminal 30.

[Deposit request receiving section]
The deposit request receiving unit 107 receives a deposit request from the deposit terminal 20. In the second embodiment, the deposit amount does not need to be displayed, so the deposit request receiving unit 107 can receive a deposit request from the deposit terminal 20 even if the deposit amount has not been displayed. In the second embodiment, the deposit request receiving unit 107 may receive a deposit request from the user terminal 30 or another computer. For example, when a transfer of money is made between users, the deposit request receiving unit 107 may receive a deposit request from the user terminal 30 of the user sending the money. In the case of auto-charge, a deposit may be made without a particular deposit request.

[Deposit Execution Department]
The deposit execution unit 108 executes the deposit. In the second embodiment, the deposit may be a transfer of the payment means instead of a charge to the payment means. For example, the deposit execution unit 108 executes a transfer of money from one user's payment means to another user's payment means as a deposit. The transfer process may be a known process. The deposit execution unit 108 executes the transfer by decreasing the balance of the payment means of the user who is the sender and increasing the balance of the payment means of the user who is the recipient. When auto-charge is executed, the auto-charge process may be a known process. It is assumed that the information necessary for auto-charge is stored in the user database DB.

For example, when a deposit request is received by the deposit request receiving unit 107, the deposit execution unit 108 executes a deposit to the payment means associated with the user identification information. The payment means associated with the user identification information is the payment means of the user indicated by the user identification information. For example, the payment means whose balance is stored in the same record as the user identification information in the user database DB corresponds to the payment means associated with the user identification information. For example, the deposit execution unit 108 may execute a deposit if authentication is successful. The authentication and other processes may be the same as those in the first embodiment.

[2-1-2. Functions realized by the deposit terminal]
The functions realized by the deposit terminal 20 may be similar to those in the first embodiment. In the second embodiment, remittance between users may be instructed from the deposit terminal 20.

[2-1-3. Functions realized by user terminal]
The functions realized by the user terminal 30 may be similar to those in the first embodiment. However, the user terminal 30 in the second embodiment may have a function for transferring money between users.

[2-2. Processing Executed in the Deposit System of the Second Embodiment]
Fig. 12 is a diagram showing an example of the process executed in the deposit system 1 of the second embodiment. The process of Fig. 12 is executed by the control units 11, 21, and 31 executing the programs stored in the storage units 12, 22, and 32, respectively. In the second embodiment, an example is given of the case where the same processes of S1 to S23 as in the first embodiment are executed. In Fig. 12, the process thereafter is shown.

For example, assume that the OEM payment app remains running on the user terminal 30 after processing similar to S1 to S23 has been executed. The server 10 transmits deposit execution data indicating deposit execution information I63 to the user terminal 30 (S24). When the user terminal 30 receives the deposit execution data from the server 10 (S25), it displays the deposit execution information I63 on the OEM code screen SC6 (S26), and this processing ends. If the OEM payment app is closed at the time the deposit is executed, processing similar to S24 to S26 can be executed when the OEM payment app is launched on the user terminal 30.

[2-3. Summary of the second embodiment]
In the second embodiment, when a deposit is made, the deposit system 1 displays the deposit execution information I63 on the OEM code screen SC6 on which the payment code C60 is displayed. This makes it easier for the user to notice the deposit, and therefore the convenience of the user who uses the OEM payment app can be improved. For example, if the OEM code screen SC6 is the first screen displayed when the OEM payment app is started (the so-called first view screen), the deposit execution information I63 is displayed on a screen that is particularly easy for the user to notice, so that the user can easily notice the deposit. For example, if the deposit is made by the user who owns the payment method to be deposited, such as a deposit from the deposit terminal 20, the user may remember the fact of the deposit, but the user may not easily notice deposits such as remittance from another user and auto-charge. Even if such a deposit is made, the deposit system 1 displays the deposit execution information I63 on the OEM code screen SC6, which is easy for the user to notice, so that the user can easily notice the deposit. For example, with the notification function within the app (e.g., notifications displayed from a bell-shaped icon), a deposit can be buried in other notifications and difficult for the user to notice, but the deposit system 1 makes it easier for the user to notice the deposit by deliberately displaying the OEM code screen SC6 deposit execution information I63, which is the same as the payment code C60.

The deposit system 1 also receives user identification information from the OEM payment app that can identify the user operating the deposit terminal 20. The deposit system 1 receives a deposit request from the deposit terminal 20. When the deposit request is received, the deposit system 1 executes a deposit to the payment method associated with the user identification information. This allows the user to execute a deposit using the deposit terminal 20 and the OEM payment app, thereby further improving user convenience.

The deposit system 1 also receives user identification information and code information from the user terminal 30 that reads the authentication code C20 displayed on the deposit terminal 20. The deposit system 1 performs authentication based on the code information. If authentication is successful, the deposit system 1 causes the deposit terminal 20 to display the amount that can be deposited. This allows the deposit system 1 to prevent erroneous or fraudulent deposits to be made to the payment means of a third party other than the user operating the user terminal 30 that read the authentication code C20.

The deposit system 1 also transmits code information to the deposit terminal 20. The deposit terminal 20 displays an authentication code C20 based on the transmitted code information. The deposit system 1 performs authentication based on the transmitted code information and the code information received from the user terminal 30. When the deposit terminal 20 generates code information, there is a possibility that the code information may overlap with code information generated by other deposit terminals 20, resulting in erroneous authentication; however, by the deposit system 1 transmitting code information to the deposit terminal 20, erroneous authentication can be prevented.

In addition, in the deposit system 1, a business payment app of the payment business operator that manages the payment means and an OEM payment app of the payment business operator's OEM (Original Equipment Manufacturing) partner are each installed on the user terminal, deposits can be made from either the business payment app or the OEM payment app, and the processing of the display control unit 106 and the deposit execution unit 108 can be executed regardless of whether the user uses the business payment app or the OEM payment app. As a result, the deposit system 1 allows the user to use either the business payment app or the OEM payment app of their choice when making a deposit, thereby further improving user convenience.

3. Modifications
The present disclosure is not limited to the above-described embodiments. The present disclosure can be modified as appropriate without departing from the spirit and scope of the present disclosure.

[3-1. Modifications of the first embodiment]
First, a modification of the first embodiment will be described.

Figure 13 is a diagram showing an example of functions realized in a modified example of the first embodiment. As shown in Figure 13, the server 10 of the modified example of the first embodiment includes an output control unit 109, a first invalidation unit 110, a second invalidation unit 111, a feasibility determination unit 112, and an input possible information acquisition unit 113. Each of the output control unit 109, the first invalidation unit 110, the second invalidation unit 111, the feasibility determination unit 112, and the input possible information acquisition unit 113 is realized by the control unit 11.

[Modification 1-1]
For example, the payment means may have a first balance that can be withdrawn and a second balance that cannot be withdrawn. Withdrawals are made by transferring funds to an account such as a bank account, or by dispensing cash from an ATM. A publicly known method can be used as a withdrawal method for the payment means. Depending on the deposit means, deposits into the first balance are prohibited. For example, deposits using a credit card's shopping limit are made into the second balance, not the first balance. In this regard, too, a mechanism used in a publicly known payment service can be used.

The user database DB of variant 1-1 stores the first balance of the payment method, the second balance of the payment method, and identity verification information. Identity verification information is information regarding the presence or absence of identity verification. For example, identity verification is authentication using an identity verification document (identification card). For example, identity verification may be performed by eKYC (Electronic Know Your Customer). Identity verification may be performed by reading a physical card such as a credit card or personal number card by the user terminal 30 instead of an identity verification document.

The server 10 of variant 1-1 communicates with the user terminal 30 and performs identity verification. Identity verification may be performed by known processing. When the server 10 performs identity verification for a certain user, it updates identity verification information associated with the user identification information of the user so that the identity verification information indicates that identity verification has been completed. When identity verification is completed, the user becomes able to use the first balance. Until identity verification is completed, the user cannot use the first balance. The server 10 controls whether the first balance can be used based on the identity verification information.

In variant 1-1, the server 10 reduces the first balance of the payment means stored in the user database DB when the first balance of the payment means is used. For example, when a user uses the first balance of the payment means from a business payment app, the server 10 reduces the first balance of the payment means stored in the user database DB. For example, when a user uses the first balance of the payment means from an OEM payment app, the server 10 reduces the first balance of the payment means stored in the user database DB. The same process is performed when the second balance is used. Note that the same process is performed when the first balance is withdrawn.

In variant 1-1, the deposit execution unit 108 deposits the first balance if the user's identity has been verified, and deposits the second balance if the user's identity has not been verified. For example, when a deposit request for a user's settlement balance is received, the deposit execution unit 108 refers to the user's identity verification information. If the identity verification information indicates that the user's identity has been verified, the deposit execution unit 108 deposits the first balance. That is, the server 10 increases the first balance of the payment method. If the identity verification information indicates that the user's identity has not been verified, the deposit execution unit 108 deposits the second balance. That is, the server 10 increases the second balance of the payment method.

The deposit system 1 of the first modified example includes an output control unit 109. If the user's identity has been verified, the output control unit 109 causes the deposit terminal 20 to output a first receipt indicating that the deposit of the first balance has been completed, and if the user's identity has not been verified, the output control unit 109 causes the deposit terminal 20 to output a second receipt indicating that the deposit of the second balance has been completed. A message indicating that the deposit of the first balance has been completed is printed on the first receipt. A message indicating that the deposit of the second balance has been completed is printed on the second receipt.

For example, if user identity verification has been completed, the output control unit 109 instructs the deposit terminal 20 to output a first receipt after a deposit into the first balance has been made. The first receipt is output by transmitting data indicating that the deposit into the first balance has been completed. When the deposit terminal 20 receives an instruction to output the first receipt from the server 10, it outputs the first receipt from the output unit 28 based on the instruction. The content printed on the first receipt is assumed to be included in the instruction from the server 10. For example, the content may be a message indicating that the deposit into the first balance has been completed, the amount of the deposit, the date and time of the deposit, the balance after the deposit, or a combination of these.

For example, if user identity verification has not been completed, the output control unit 109 instructs the deposit terminal 20 to output a second receipt after a deposit into the second balance has been made. The second receipt is output by transmitting data indicating that the deposit into the second balance has been completed. When the deposit terminal 20 receives an instruction to output a second receipt from the server 10, it outputs the second receipt from the output unit 28 based on the instruction. The content printed on the second receipt is assumed to be included in the instruction from the server 10. For example, the content may be a message indicating that the deposit into the second balance has been completed, the amount of the deposit, the date and time of the deposit, the balance after the deposit, or a combination of these.

The deposit system 1 of variant 1-1 executes a deposit of the first balance if the user's identity has been verified, and executes a deposit of the second balance if the user's identity has not been verified. If the user's identity has been verified, the deposit system 1 causes the deposit terminal 20 to output a first receipt indicating that the deposit of the first balance has been completed, and if the user's identity has not been verified, the deposit system 1 causes the deposit terminal 20 to output a second receipt indicating that the deposit of the second balance has been completed. The deposit system 1 makes it easier for the user to know whether a deposit has been made into the first balance or the second balance.

[Modification 1-2]
For example, when a user selects button B22 on the code reading screen SC2 in Fig. 3, the output unit 28 of the deposit terminal 20 outputs a receipt on which the authentication code C20 is printed. Since the code reading screen SC2 may be reflected and it may be difficult for the user to read the authentication code C20 on the screen, the user may read the authentication code C20 printed on the receipt with the user terminal 30. In this case, when the user selects button B21 after the authentication code C20 is displayed on the code reading screen SC2 in Fig. 3, the authentication code C20 may be invalidated. In other words, even if the user selects button B21 and then reads the authentication code C20 printed on the receipt with the user terminal 30, the deposit may not be executed.

The deposit system 1 includes a first invalidation unit 110. The first invalidation unit 110 invalidates the authentication code C20 when the next screen is displayed after the authentication code C20 is displayed on the deposit terminal 20. In the example of FIG. 3, the next screen is the deposit amount input screen SC3. The next screen may be any screen that is displayed after the screen on which the authentication code C20 is displayed in the series of procedures for depositing money. For example, when the user selects button B21 to instruct the transition to the next screen, the deposit terminal 20 transmits data to the server 10 indicating that the transition to the next screen has been instructed. The server 10 detects the transition to the next screen by receiving the data from the deposit terminal 20.

To invalidate the authentication code C20 means to record invalidation data indicating that the authentication code C20 has been invalidated in the data storage unit 100, or to delete the code information from the data storage unit 100. For example, the first invalidation unit 110 invalidates the authentication code C20 by recording invalidation data indicating that the authentication code C20 has been invalidated in the data storage unit 100 in association with the code information coded in the authentication code C20. The first invalidation unit 110 invalidates the authentication code C20 by deleting the code information coded in the authentication code C20 from the data storage unit 100. As another example, the first invalidation unit 110 may invalidate the authentication code C20 by changing the value of information such as a flag indicating the validity of the authentication code C20.

The authentication execution unit 103 of variant 1-2 fails the authentication when it reads the authentication code C20 that has been disabled by the first disabling unit 110. The authentication execution unit 103 succeeds in the authentication when it reads the authentication code C20 that has not been disabled by the first disabling unit 110. For example, when disabling data is used, the authentication execution unit 103 determines whether or not disabling data is associated with the code information when a request for authentication based on the code information is received. If disabling data is not associated with the code information, the authentication execution unit 103 executes authentication in the same manner as in the first embodiment. If disabling data is associated with the code information, the authentication execution unit 103 determines that the authentication has failed.

For example, when the authentication code C20 is invalidated by deleting code information from the data storage unit 100, the authentication execution unit 103, upon receiving a request for authentication based on certain code information, determines whether the code information exists in the data storage unit 100. If it is determined that the code information exists in the data storage unit 100, the authentication execution unit 103 determines that the authentication has been successful. If it is determined that the code information does not exist in the data storage unit 100, the authentication execution unit 103 determines that the authentication has failed.

The deposit system 1 of variant 1-2 invalidates the authentication code C20 when the screen transitions to the next screen after the authentication code C20 is displayed on the deposit terminal 20. The deposit system 1 causes authentication to fail when the authentication code C20 invalidated by the first invalidation unit 110 is read. This allows the deposit system 1 to prevent deposits from being made to other users' payment methods. For example, the deposit system 1 can prevent fraudulent deposits.

[Modification 1-3]
For example, in the modified example 1-2, the authentication code C20 is invalidated when the user selects the button B21, but the authentication code C20 may be invalidated at another timing. The deposit system 1 of the modified example 1-3 includes a second invalidation unit 111. The second invalidation unit 111 invalidates the authentication code C20 when the authentication is successful. The authentication code C20 may be invalidated in the same manner as in the modified example 1-2. For example, the second invalidation unit 111 invalidates the authentication code C20 by recording invalidation data indicating that the authentication code C20 has been invalidated in the data storage unit 100, or by deleting the code information from the data storage unit 100, when the authentication is successful.

The authentication execution unit 103 of variant 1-3 fails the authentication when it reads the authentication code C20 that has been disabled by the second disabling unit 111. The authentication execution unit 103 succeeds in the authentication when it reads the authentication code C20 that has not been disabled by the second disabling unit 111. Variation 1-3 differs from variant 1-2 in that the authentication code C20 is disabled by the second disabling unit 111, but the process itself executed by the authentication execution unit 103 is the same as variant 1-2.

The deposit system 1 of variant 1-3 invalidates the authentication code C20 if authentication is successful. If an invalidated authentication code C20 is read, the deposit system 1 causes authentication to fail. This allows the deposit system 1 to prevent deposits from being made to other users' payment methods. For example, the deposit system 1 can prevent fraudulent deposits.

[Modification 1-4]
For example, after the deposit amount input screen SC3 is displayed, a deposit may be made to the user's payment means by a method other than the deposit terminal 20. In this case, the actual depositable amount may be less than the depositable amount displayed on the deposit amount input screen SC3. For this reason, when a deposit request is made, it may be possible to determine whether or not to allow the deposit based on the latest depositable amount.

The deposit system 1 of variant 1-4 further includes a possibility determination unit 112. When a deposit request is received by the deposit request receiving unit 107, the possibility determination unit 112 determines whether or not a deposit can be made based on the latest depositable amount. The latest depositable amount is calculated by the depositable amount calculation unit 104. The calculation method for the latest depositable amount may be the same as the calculation method used when displaying the deposit amount input screen SC3. The possibility determination unit 112 determines whether or not the deposit amount indicated by the deposit request is greater than the latest depositable amount. If the deposit amount is equal to or less than the latest depositable amount, the possibility determination unit 112 determines that a deposit is possible. If the deposit amount is greater than the latest depositable amount, the possibility determination unit 112 determines that a deposit is not possible.

The deposit execution unit 108 of variant 1-4 executes the deposit when a deposit request is received by the deposit request receiving unit 107 and the feasibility determination unit 112 determines that the deposit is possible. The deposit execution unit 108 does not execute the deposit when a deposit request is received by the deposit request receiving unit 107 and the feasibility determination unit 112 determines that the deposit is not possible. In this case, an error message indicating that the deposit has not been executed is displayed on at least one of the deposit terminal 20 and the user terminal 30.

When a deposit request is received by the deposit request receiving unit 107 and the feasibility determination unit 112 determines that a deposit is not possible, the deposit execution unit 108 may execute a deposit within the latest depositable amount. In this case, the deposit execution unit 108 may inquire of the user as to whether or not to execute a deposit within the latest depositable amount, and then execute a deposit within the latest depositable amount, or may execute a deposit within the latest depositable amount without any particular inquiry.

When a deposit request is received by the deposit request receiving unit 107, the deposit system 1 of variant 1-4 determines whether or not a deposit can be made based on the latest depositable amount. The deposit system 1 executes the deposit when a deposit request is received and the depositability determination unit 112 determines that the deposit is possible. This allows the deposit system 1 to prevent a deposit that exceeds the depositable amount from being made, even if the depositable amount has changed after it was displayed on the deposit terminal 20.

[Modification 1-5]
For example, the storage unit 27 of the deposit terminal 20 can detect the amount of cash inserted therein. The server 10 may determine the amount of cash that can be inserted by taking into consideration the amount of cash that can be stored in the storage unit 27. The deposit execution unit 108 of Modification 1-5 executes a deposit based on the cash inserted into the deposit terminal 20, in the same manner as in the first embodiment. The data storage unit 100 of Modification 1-5 may store data indicating the capacity of the storage unit 27 of the deposit terminal 20. The server 10 may calculate the difference between the amount of cash currently inserted in the storage unit 27 of the deposit terminal 20 based on the data, and determine how much more cash can be inserted.

The deposit system 1 of variant 1-5 includes a deposit-available information acquisition unit 113. The deposit-available information acquisition unit 113 acquires deposit-available information regarding cash that can be deposited into the deposit terminal. The deposit-available information may indicate the balance of cash that can be stored in the storage unit 27, or may indicate the total amount of cash stored in the storage unit 27. For example, the deposit terminal 20 transmits the deposit-available information to the server 10 based on the detection results of a sensor in the storage unit 27. The deposit-available information acquisition unit 113 receives the deposit-available information from the deposit terminal 20.

In variant 1-5, the depositable amount calculation unit 104 calculates the depositable amount further based on the depositable information. For example, the depositable amount calculation unit 104 compares the depositable amount calculated in a manner similar to the embodiment with the cash that can be stored in the storage unit 27 obtained based on the depositable information. The depositable amount calculation unit 104 calculates the lower of the depositable amount calculated in a manner similar to the embodiment and the cash that can be stored in the storage unit 27 obtained based on the depositable information as the final depositable amount. Subsequent processing may be the same as in the embodiment.

The deposit system 1 of variant 1-5 acquires deposit availability information regarding the cash that can be deposited into the deposit terminal 20. The deposit system 1 further calculates the depositable amount based on the deposit availability information. This allows the deposit system 1 to reliably prevent the capacity of the deposit terminal 20 from being exceeded.

[3-2. Modifications of the second embodiment]
Next, a modification of the second embodiment will be described.

Figure 14 is a diagram showing an example of functions realized in a variation of the second embodiment. As shown in Figure 18, the server 10 of the variation of the second embodiment includes a bonus granting unit 114. The bonus granting unit 114 is realized by the control unit 11. As explained in the second embodiment, the deposit system 1 of the second embodiment does not have to include the functions of the first embodiment. This point is shown in Figure 14.

[Modification 2-1]
For example, the authentication code C20 may be generated based on the code information and terminal identification information capable of identifying the deposit terminal 20. The terminal identification information may be any information. For example, the terminal identification information may be the terminal name of the deposit terminal 20, an IP address, temporary information generated by the server 10, or other information. The deposit terminal 20 of variant example 2-1 stores the terminal identification information. The deposit terminal 20 generates the authentication code C20 based on the code information and the terminal identification information.

The data storage unit 100 of variant example 2-1 stores a deposit terminal database in which terminal identification information and display data related to the deposit terminal 20 are associated. The display data indicates the content to be displayed in the OEM payment app. For example, the display data indicates the name of the deposit terminal 20, the location where the deposit terminal 20 is located, or other information. The display data may indicate information other than text, such as an image showing the appearance of the deposit terminal 20.

The display control unit 106 in variant example 2-1 causes the OEM payment app to display information about the deposit terminal 20 based on the terminal identification information. For example, the display control unit 106 causes the OEM payment app to display information about the deposit terminal 20 by sending display data associated with the terminal identification information to the deposit terminal 20. For example, the user terminal 30 causes the OEM payment app to display the name of the deposit terminal 20, the location where the deposit terminal 20 is located, or other information based on the display data received from the server 10.

The display control unit 106 may display information about the deposit terminal 20 on the OEM code screen SC6 of the OEM payment app, or may display information about the deposit terminal 20 on another screen of the OEM payment app. The display control unit 106 may display information about the deposit terminal 20 using a modal, window, or push notification of the OEM payment app. The display control unit 106 may display information about the deposit terminal 20 in the business payment app or another payment app.

The authentication code C20 in variant 2-1 is generated based on the code information and terminal identification information capable of identifying the deposit terminal 20. The deposit system 1 causes the OEM payment app to display information about the deposit terminal 20 based on the terminal identification information. This makes it easier for the deposit system 1 to allow the user to know which deposit terminal 20 is used to make the deposit.

[Modification 2-2]
For example, the user may read the authentication code C20 not by using the OEM payment app, but by using a reading function installed as a standard function of the user terminal 30. In this case, the user terminal 30 may start the OEM payment app by reading the authentication code C20. Note that the user terminal 30 may start the business operator payment app or another payment app by reading the authentication code C20.

The authentication code C20 in variant 2-2 is generated based on the code information and app identification information capable of identifying the OEM payment app. The app identification information may be any information capable of identifying the OEM payment app among applications installed on the user terminal 30. For example, the app identification information may be an ID assigned to the OEM payment app, the name of the OEM payment app, or other information. The deposit terminal 20 may store the app identification information in advance. The server 10 may transmit the app identification information to the deposit terminal 20 together with the code information.

In variant 2-2, the user terminal 30 launches the OEM payment app based on the app identification information when the authentication code C20 is read by a function other than the OEM payment app. The other function may be a standard function of the user terminal 30, or a function of an app other than the OEM payment app. The user terminal 30 determines whether the information obtained from the authentication code C20 includes app identification information. If it is determined that the app identification information is included, the user terminal 30 launches the OEM payment app. The OEM payment app may be launched by a method of automatically launching an application on a computer such as a smartphone, or by a method of bringing an already launched application back to the foreground.

The authentication code C20 in variant 2-2 is generated based on the code information and app identification information that can identify the payment app. When the authentication code C20 is read by a function other than the payment app, the user terminal 30 launches the OEM payment app based on the app identification information. This allows the deposit system 1 to save the user the trouble of launching the OEM payment app.

[Modification 2-3]
For example, the display control unit 106 may further display, on the OEM code screen SC6, bonus information regarding a bonus granted to the user upon making a deposit. A bonus is a benefit to a user. For example, a bonus may be points, an increase in the point grant rate, a coupon, a product voucher, a free service voucher, or other content. Bonus information is information indicating the content of the bonus. Variation example 2-3 takes as an example a case in which points according to the amount of a user's deposit correspond to the bonus.

Figure 15 is a diagram showing an example of an OEM code screen SC6 on which bonus information is displayed. In the example of Figure 15, bonus information is displayed in button B61. The data storage unit 100 of variant example 2-3 stores bonus content data indicating the content of the bonus. The display control unit 106 identifies the content of the bonus to be granted to the user based on the bonus content data. The display control unit 106 displays bonus information on the OEM code screen SC6 based on the content of the identified bonus. The bonus information may be a message, an icon, or other image.

The display control unit 106 may display bonus information on the OEM code screen SC6 together with the deposit execution information I63 in FIG. 11. In this case, the display control unit 106 displays bonus information indicating the bonus granted to the user as a result of the already-executed deposit, or the bonus that will be granted to the user as a result of the already-executed deposit, on the OEM code screen SC6. The display control unit 106 transmits data of the OEM code screen SC6 including the deposit execution information I63 and the bonus information to the user terminal 30, thereby causing the OEM code screen SC6 including these to be displayed on the user terminal 30.

The deposit system 1 of variant 2-3 further displays, on the OEM code screen SC6, bonus information regarding the bonus granted to the user upon making a deposit. The deposit system 1 makes it easier for the user to understand the bonus granted to the user upon making a deposit, thereby further enhancing user convenience.

[Modification 2-4]
For example, in variant example 2-3, the display control unit 106 may cause the OEM code screen SC6 to display bonus information regarding a bonus that will be granted when a deposit satisfies a predetermined condition. The predetermined condition is a condition that serves as a criterion for whether or not a bonus will be granted. The predetermined condition may be any condition for a known bonus. For example, the predetermined condition may be the amount of deposit, the number of deposits, the deposit location, the deposit method, or other conditions.

The bonus content data in variant 2-3 indicates a specified condition. The display control unit 106 identifies the specified condition based on the bonus content data. The display control unit 106 causes the OEM code screen SC6 to display the specified condition based on the identified specified condition. The specified condition may be a message, an icon, or other image. Variation 2-3 differs in that the specified condition is also displayed, but the method of displaying the OEM code screen SC6 is the same as variant 2-3.

The deposit system 1 of variant 2-4 displays on the OEM code screen SC6 bonus information about the bonus that will be granted if the deposit satisfies certain conditions. This allows the deposit system 1 to make it easier for the user to understand the bonus that will be granted to the user under certain conditions, thereby further improving user convenience.

[Modification 2-5]
For example, when a deposit based on the OEM payment app is executed, the display control unit 106 may not display the deposit execution information on the OEM code screen SC6 of the business payment app, but may display the deposit execution information on the OEM code screen SC6 of the OEM payment app. A deposit based on the OEM payment app includes not only a deposit made according to the flow of the first embodiment, but also other deposits such as a deposit made only by operations in the OEM payment app, a remittance made by specifying a user account of the OEM payment app, or an auto-charge executed based on settings in the OEM payment app.

The deposit history data stored in the user database DB of variant 2-5 includes information indicating whether or not a deposit is based on the OEM payment app. The display control unit 106 determines whether or not each deposit is based on the OEM payment app based on the information. When the display control unit 106 receives a request to display the OEM code screen SC6 from the user terminal 30, it determines whether or not a deposit based on the OEM payment app has been made based on the information. When it is determined that a deposit based on the OEM payment app has been made, the display control unit 106 causes the user terminal 30 to display the OEM code screen SC6 including the deposit execution information I63. When the display control unit 106 receives a request to display the business payment app screen from the user terminal 30, it does not execute this series of processes and does not cause the deposit execution information I63 to be displayed.

In variant example 2-5, when a deposit is made based on an OEM payment app, the deposit system 1 does not display the deposit execution information on the OEM code screen SC6 of the business payment app, but displays the deposit execution information on the OEM code screen SC6 of the OEM payment app. This makes it easier for the deposit system 1 to notice that a deposit has been made using the OEM payment app, thereby further improving convenience for users who use the OEM payment app.

[Modification 2-6]
For example, as described in the second embodiment, a deposit using the OEM payment app is made based on a deposit terminal installed at the OEM's location. The deposit system 1 of variant 2-6 includes a bonus granting unit 114. When a user makes a deposit using a deposit terminal and the OEM payment app, the bonus granting unit 114 grants the user a bonus that can be used at the OEM's location and that is better than a bonus that would be granted if the user made a deposit using the business payment app. Data indicating the bonus granted to the user is stored in the user database DB.

The quality of a benefit refers to the high benefit the user receives. For example, the quality of a benefit corresponds to the number of points the user earns, the high point award rate, the high discount rate of a coupon, the value of a product redeemed with a voucher, the value of a service received with a free voucher, or other benefits. For example, when a user makes a deposit using a deposit terminal and an OEM payment app, the benefit awarding unit 114 determines a benefit for the user that is available at the OEM's location and has a higher point award rate than when the user makes a deposit using a business payment app.

In variant example 2-6, the display control unit 106 displays on the OEM code screen SC6 of the OEM payment app that a bonus has been granted. For example, the display control unit 106 displays on the OEM code screen SC6, together with the deposit execution information I63, information indicating that the points grant rate is higher than if the user had made a deposit using the business payment app. The display control unit 106 displays on the OEM code screen SC6, together with the deposit execution information I63, information indicating that higher points have been granted or will be granted than if the user had made a deposit using the business payment app.

Note that the number of OEMs is not limited to one. There may be multiple OEMs. For example, assume that there are two OEMs, a first OEM and a second OEM. When a user makes a deposit using a deposit terminal 20 located at the location of the first OEM and a first OEM payment app that is the payment app of the first OEM, the bonus granting unit 114 may grant the user a bonus that is available at the location of the first OEM and is better than a bonus that would be available if the user made the deposit using the business payment app. Similarly, when a user makes a deposit using a deposit terminal 20 located at the location of the second OEM and a second OEM payment app that is the payment app of the second OEM, the bonus granting unit 114 may grant the user a bonus that is available at the location of the second OEM and is better than a bonus that would be available if the user made the deposit using the business payment app. There may be three or more OEMs.

In variant 2-6, when a user makes a deposit using the deposit terminal 20 and the OEM payment app, the deposit system 1 grants the user a bonus that can be used at the OEM's location and that is better than a bonus that would be given if the user made the deposit using the business payment app. The deposit system 1 displays on the OEM code screen SC6 of the OEM payment app that a bonus has been granted. This allows the deposit system 1 to inform the user that they can get a good bonus by using the OEM payment app, thereby promoting the use of the OEM's payment service.

[3-3. Other Modifications]
For example, the modified example of the first embodiment and the modified example of the second embodiment may be combined.

For example, the payment method used by the user from the business payment app may be different from the payment method used by the user from the OEM payment app. That is, different balances may be used when the user uses the business payment app and when the user uses the OEM payment app. For example, if the user selects button B23 on the code reading screen SC2 or button B31 on the deposit amount input screen SC3, the deposit may be canceled. In this case, the authentication code C20 may be invalidated. The authentication code C20 may be invalidated in the same manner as in variants 1-2 and 1-3. The authentication code C20 may be invalidated if the user does not perform any operation on the deposit terminal 20 for a certain period of time after the code reading screen SC2 is displayed.

For example, the process described as being executed by the server 10 may be executed by the deposit terminal 20 or the user terminal 30. The process described as being executed by the deposit terminal 20 may be executed by the server 10 or the user terminal 30. The process described as being executed by the user terminal 30 may be executed by the server 10 or the deposit terminal 20. The process described as being executed by the server 10, the deposit terminal 20, or the user terminal 30 may be shared among multiple computers.

[4. Notes]
For example, the deposit system can be configured as follows:

[4-1. Supplementary notes regarding the deposit system of the first embodiment]
(1-1)
A deposit terminal that accepts deposit operations related to payment means that can accept deposits, the deposit terminal being disposed in a location visited by the user, and a user identification information receiving unit that receives user identification information that can identify the user operating the deposit terminal;
a depositable amount calculation unit that calculates a depositable amount according to the upper deposit limit and total deposit amount of the user in a predetermined period based on the user identification information;
A display control unit that causes the deposit terminal to display the depositable amount;
a deposit request receiving unit for receiving a deposit request from the deposit terminal after the depositable amount is displayed;
a deposit execution unit that executes the deposit when the deposit request is received by the deposit request receiving unit;
Including the deposit system.
(1-2)
When the total deposit amount reaches the upper deposit limit, the display control unit causes the deposit terminal to display the fact that the total deposit amount has reached the upper deposit limit and the time when deposits will be possible again.
A deposit system as described in (1-1).
(1-3)
When the total deposit amount is less than the deposit upper limit amount and the deposit of the minimum deposit amount at the deposit terminal is not possible, the display control unit causes the deposit terminal to display that the total deposit amount has reached the deposit upper limit amount and the time when the deposit will be possible again.
A deposit system according to (1-1) or (1-2).
(1-4)
The deposit system further includes a depositable amount comparison unit that compares a first depositable amount, which is the depositable amount acquired by the depositable amount calculation unit, with a second depositable amount, which is a depositable amount per transaction possible from the deposit terminal,
the display control unit causes the deposit terminal to display the lower of the first depositable amount and the second depositable amount based on a comparison result of the depositable amount comparison unit.
A deposit system according to any one of (1-1) to (1-3).
(1-5)
the payment means has a first balance that is withdrawable and a second balance that is not withdrawable;
the deposit execution unit executes the deposit of the first balance if identity verification of the user has been completed, and executes the deposit of the second balance if identity verification of the user has not been completed;
The deposit system described in any of (1-1) to (1-4) further includes an output control unit which, if identity verification of the user has been completed, causes the deposit terminal to output a first receipt indicating that the deposit of the first balance has been completed, and, if identity verification of the user has not been completed, causes the deposit terminal to output a second receipt indicating that the deposit of the second balance has been completed.
(1-6)
The deposit terminal displays an authentication code,
The authentication code is read by a user terminal of the user;
the user identification information receiving unit receives, from the user terminal, the user identification information and code information extracted from the authentication code;
The deposit system further includes an authentication execution unit that executes authentication based on the code information,
The display control unit causes the deposit terminal to display the depositable amount when the authentication is successful.
A deposit system according to any one of (1-1) to (1-5).
(1-7)
The deposit system further includes a code information transmission unit that transmits the code information to the deposit terminal,
The authentication code is displayed on the deposit terminal based on the code information transmitted by the code information transmission unit,
The authentication execution unit executes the authentication based on the code information transmitted by the code information transmission unit and the code information received from the user terminal.
A deposit system as described in (1-6).
(1-8)
The deposit system further includes a first invalidation unit that invalidates the authentication code when a transition is made to a next screen after the authentication code is displayed on the deposit terminal,
the authentication execution unit causes the authentication to fail when the authentication code invalidated by the first invalidation unit is read.
A deposit system according to (1-6) or (1-7).
(1-9)
The deposit system further includes a second invalidation unit that invalidates the authentication code when the authentication is successful,
the authentication execution unit causes the authentication to fail when the authentication code invalidated by the second invalidation unit is read.
A deposit system according to any one of (1-6) to (1-8).
(1-10)
The deposit system further includes an availability determination unit that, when the deposit request is received by the deposit request receiving unit, determines whether the deposit can be made based on the latest depositable amount,
the deposit execution unit executes the deposit when the deposit request is received by the deposit request receiving unit and the possibility determination unit determines that the deposit is possible;
A deposit system according to any one of (1-1) to (1-9).
(1-11)
A business payment app of a payment business that manages the payment means and an OEM payment app of an OEM (Original Equipment Manufacturing) partner of the payment business are installed on a user terminal of the user,
the deposit terminal is located at the OEM's location;
The deposit can be made from each of the business payment app and the OEM payment app,
The processes of the user identification information receiving unit, the depositable amount calculation unit, the display control unit, the deposit request receiving unit, and the deposit execution unit can be executed regardless of whether the user uses the business payment app or the OEM payment app.
A deposit system according to any one of (1-1) to (1-10).
(1-12)
The deposit execution unit executes the deposit based on the cash inserted into the deposit terminal,
The deposit system further includes an available deposit information acquisition unit that acquires available deposit information regarding cash that can be deposited into the deposit terminal,
The depositable amount calculation unit calculates the depositable amount further based on the depositable information.
A deposit system according to any one of (1-1) to (1-11).

[4-2. Supplementary notes regarding the deposit system of the second embodiment]
(2-1)
A display control unit that displays a payment code for a payment based on a payment means that can be used for depositing, on a payment application installed on a user terminal of the user;
A deposit execution unit that executes the deposit;
Including,
the display control unit, when the deposit is executed, displays deposit execution information regarding the execution of the deposit on a code screen of the payment application on which the payment code is displayed,
Deposit system.
(2-2)
The deposit system includes:
A user identification information receiving unit that receives, from the payment application, user identification information that can identify the user who operates the deposit terminal that is located at a place visited by the user, and that accepts a deposit operation related to the deposit;
A deposit request receiving unit that receives a deposit request from the deposit terminal;
Further comprising:
the deposit execution unit executes the deposit to the payment means associated with the user identification information when the deposit request is received by the deposit request receiving unit.
A deposit system as described in (2-1).
(2-3)
The deposit terminal displays an authentication code,
The authentication code is read by the user terminal;
the user identification information receiving unit receives, from the payment application, the user identification information and code information extracted from the authentication code;
The deposit system further includes an authentication execution unit that executes authentication based on the code information,
The deposit execution unit executes the deposit if the authentication is successful.
A deposit system as described in (2-2).
(2-4)
The deposit system further includes a code information transmission unit that transmits the code information to the deposit terminal,
The authentication code is displayed on the deposit terminal based on the code information transmitted by the code information transmission unit,
The authentication execution unit executes the authentication based on the code information transmitted by the code information transmission unit and the code information received from the payment application.
A deposit system as described in (2-3).
(2-5)
The authentication code is generated based on the code information and terminal identification information capable of identifying the deposit terminal,
The display control unit causes the payment application to display information related to the deposit terminal based on the terminal identification information.
A deposit system according to (2-3) or (2-4).
(2-6)
The authentication code is generated based on the code information and application identification information capable of identifying the payment application,
When the authentication code is read by a function other than the payment application, the user terminal starts the payment application based on the application identification information.
A deposit system according to any one of (2-3) to (2-5).
(2-7)
The display control unit further displays, on the code screen, benefit information regarding a benefit to be granted to the user as a result of the deposit.
A deposit system according to any one of (2-1) to (2-6).
(2-8)
the display control unit causes the code screen to display the benefit information regarding the benefit that will be granted when the deposit satisfies a predetermined condition.
A deposit system as described in (2-7).
(2-9)
A business payment app of a payment business that manages the payment means and an OEM (Original Equipment Manufacturing) payment app of an OEM of the payment business are installed on the user terminal,
The deposit can be made from each of the business payment app and the OEM payment app,
The processes of the display control unit and the deposit execution unit can be executed regardless of whether the user uses the business payment app or the OEM payment app.
A deposit system according to any one of (2-1) to (2-8).
(2-10)
When the deposit based on the OEM payment app is executed, the display control unit does not display the deposit execution information on the code screen of the business payment app, and displays the deposit execution information on the code screen of the OEM payment app.
A deposit system as described in (2-9).
(2-11)
The deposit using the OEM payment app is performed based on a deposit terminal installed at the OEM's location,
The deposit system further includes a benefit granting unit that grants to the user, when the user executes the deposit using the deposit terminal and the OEM payment app, a benefit that can be used at the OEM's location, the benefit being better than the benefit when the user executes the deposit using the business payment app;
The display control unit displays, on the code screen of the OEM payment app, that the benefit has been granted.
A deposit system according to (2-9) or (2-10).

1 Deposit system, 10 Server, 11, 21, 31 Control unit, 12, 22, 32 Memory unit, 13, 23, 33 Communication unit, 20 Deposit terminal, 24, 34 Operation unit, 25, 35 Display unit, 26 Insert unit, 27 Storage unit, 28 Output unit, 30 User terminal, 36 Photography unit, 100 Data storage unit, 101 Code information transmission unit, 102 User identification information reception unit, 103 Authentication execution unit, 104 Depositable amount calculation unit, 105 Depositable amount comparison unit, 106 Display control unit, 107 Deposit request reception unit, 108 Deposit execution unit, 109 Output control unit, 110 First invalidation unit, 111 Second invalidation unit, 112 Possibility determination unit, 113 Deposit possible information acquisition unit, 114 Benefit granting unit, 200 Data storage unit, 201 Transmission unit, 202 Receiving unit, 203 display control unit, 300 data storage unit, 301 operation reception unit, 302 display control unit, B10, B11, B21, B22, B23, B30, B31, B40, B41, B61 button, C20 authentication code, C60 settlement code, DB user database, I50, I51 icon, I63 deposit execution information, M62 modal, N network, SC1 deposit menu screen, SC2 code reading screen, SC3 deposit amount input screen, SC4 deposit completion screen, SC5 user menu screen, SC6 OEM code screen.

Claims (1)

A deposit terminal that accepts deposit operations related to payment means that can accept deposits, the deposit terminal being disposed in a location visited by the user, and a user identification information receiving unit that receives user identification information that can identify the user operating the deposit terminal;
a depositable amount calculation unit that calculates a depositable amount according to the upper deposit limit and total deposit amount of the user in a predetermined period based on the user identification information;
A display control unit that causes the deposit terminal to display the depositable amount;
a deposit request receiving unit for receiving a deposit request from the deposit terminal after the depositable amount is displayed;
a deposit execution unit that executes the deposit when the deposit request is received by the deposit request receiving unit;
Including the deposit system.

Images