Payment system, payment method, and program

Abstract

To increase the convenience of a user.SOLUTION: Settlement request accepting means (101) of a settlement system (S) accepts a settlement request on a first user owning a plurality of settling means in which use conditions different from each other are set. Identifying means (108) identifies settling means meeting the use conditions from among the plurality of settling means when the settlement request is accepted. Settlement processing executing means (102) executes settlement processing on the priority of each of the plurality of settling means when the plurality of settling means are identified by the identifying means (108).SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present disclosure relates to a payment system, a payment method, and a program. [Background technology]

[0002] Conventionally, there are known techniques for setting terms of use for payment methods such as electronic money. For example, Patent Document 1 describes a technique in which a dedicated value, which can be used for a limited number of services, and a general-purpose value, which can be used for more services than the dedicated value, are recorded on a terminal, and the user's general-purpose value is converted into the dedicated value and then transferred to another user. Patent Document 2 describes a technique in which, when subsidies are provided to people on welfare, whether or not the electronic points match a predetermined purpose is determined at the time of use, and the purpose of use of the electronic points is limited in order to prevent the subsidies from being used for purposes other than the original purpose.

[0003] Patent Document 3 describes recording on an IC card general electronic money, which is not limited in terms of use purpose, such as usable stores, usable departments, product categories, or products, and specific electronic money, which is limited in terms of use purpose. Patent Document 4 describes validating only payments for the use purpose set for electronic money and restricting its use from being used for other purposes. Patent Document 5 describes closed money, which is used to purchase only specific products, and open money, which has no restrictions on the products that can be purchased. Patent Document 6 describes giving electronic money, which is limited in terms of use purpose, to a child when giving them pocket money. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-111564 [Patent Document 2] Japanese Patent Application Laid-Open No. 2015-097053 [Patent Document 3] Japanese Patent Application Publication No. 11-353397

Patent Document 4

Patent Document 5

Patent Document 6

Summary of the Invention

Problems to be Solved by the Invention

[0005] For payment means such as Patent Documents 1-6, various usage conditions can be defined. Assuming there are a plurality of payment means with different usage conditions defined, it may be possible to use multiple payment means at the store visited by the user. For example, assume there is a payment means available only for food, a payment means available only at a specific store, and a payment means available only during the daytime. When the user purchases food at a specific store during the daytime, all of these payment means are available.

[0006] However, if appropriate priorities are not assigned to individual payment means, there is a possibility that the user may use a payment means that the user does not want to use, so the convenience of the user cannot be improved. For example, in the above example, even if the user wanted to save without using the payment means available only for food, if this payment means is used, the convenience of the user will decrease. Conversely, if the user cannot use the payment means that the user wants to use, the convenience of the user will also decrease.

[0007] One of the objectives of the present disclosure is to improve the convenience of the user.

Means for Solving the Problems

[0008] The payment system according to the present disclosure includes a payment request receiving means for receiving a payment request regarding a first user who holds a plurality of payment means with different usage conditions, a specifying means for specifying, from among the plurality of payment means, the payment means that satisfies the usage conditions when the payment request is received, and a payment processing execution means for executing a payment process based on the priority order of each of the plurality of payment means specified by the specifying means.

Effect of the Invention

[0009] According to the present disclosure, the convenience for the user is enhanced.

Brief Description of the Drawings

[0010] [Figure 1] It is a diagram showing an example of the overall configuration of the payment system according to the first embodiment. [Figure 2] It is a diagram showing an example of the screen of the payment application. [Figure 3] It is a diagram showing an example of the screen of the payment application when store cash is granted. [Figure 4] It is a functional block diagram showing an example of the functions realized in the first embodiment. [Figure 5] It is a diagram showing an example of the user database. [Figure 6] It is a flowchart showing an example of the process executed in the first embodiment. [Figure 7] It is a diagram showing an example of the screen of the payment application in the second embodiment. [Figure 8] It is a functional block diagram showing an example of the functions realized in the second embodiment. [Figure 9] It is a flowchart showing an example of the process executed in the second embodiment. [Figure 10] It is a diagram showing an example of the screen of the payment application in the third embodiment. [Figure 11] It is a functional block diagram showing an example of the functions realized in the third embodiment. [Figure 12]FIG. 11 is a flowchart showing an example of processing executed in the third embodiment. [Figure 13] FIG. 10 is a diagram illustrating an example of functional blocks of a modified example according to the first embodiment. [Figure 14] FIG. 10 is a diagram illustrating an example of functional blocks of a modified example according to the second embodiment. [Figure 15] FIG. 11 is a diagram illustrating an example of functional blocks of a modified example according to the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] [1. First embodiment] A first embodiment, which is an example of an embodiment of a payment system according to the present disclosure, will be described.

[0012] [1-1. Overall configuration of the payment system] Figure 1 is a diagram showing an example of the overall configuration of a payment system according to the first embodiment. For example, the payment system S includes a server 10, a user terminal 20, and a store terminal 30. The network N is any network such as the Internet or a LAN. The payment system S is not limited to the example shown in Figure 1, as long as it includes at least one computer.

[0013] The server 10 is a server computer. The control unit 11 includes at least one processor. The storage unit 12 includes a volatile memory such as a RAM and a non-volatile memory such as a hard disk. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

[0014] The user terminal 20 is a user's computer. For example, the user terminal 20 is a smartphone, a tablet terminal, a wearable terminal, or a personal computer. The physical configurations of the control unit 21, the memory unit 22, and the communication unit 23 are the same as those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The operation unit 24 is an input device such as a touch panel. The display unit 25 is a liquid crystal display or an organic EL display.

[0015] The store terminal 30 is a computer of the store. For example, the store terminal 30 is a POS terminal, a personal computer, a tablet terminal, or a smartphone. The physical configurations of the control unit 31, the storage unit 32, the communication unit 33, the operation unit 34, and the display unit 35 are the same as those of the control unit 11, the storage unit 12, the communication unit 13, the operation unit 24, and the display unit 25, respectively. A reading device 36, which is a code reader, a reader / writer, or a camera, is connected to the store terminal 30. The reading device 36 may be included in the store terminal 30.

[0016] Note that the programs stored in each of the storage units 12, 22, and 32 may be supplied via the network N. Also, a program stored in a computer-readable information storage medium may be supplied via a reading unit (e.g., an optical disk drive or a memory card slot) for reading the information storage medium, or an input / output unit (e.g., a USB port) for inputting / outputting data to / from an external device.

[0017] [1-2. Overview of the First Embodiment] In the payment system S, a payment service is provided to each of a plurality of users. The payment service is a service that provides electronic payment. Electronic payment is sometimes called cashless payment. Each individual user has their own user terminal 20. The payment service is available at at least one store. When the payment service is available at a plurality of stores, each individual store has at least one store terminal 30.

[0018] In the first embodiment, a case will be described in which online electronic money called cash corresponds to the payment means. Therefore, the word "cash" can be read as "payment means." Payment means available in the payment service may be of any type, such as a credit card, a debit card, electronic money, points, a bank account, a wallet, virtual currency, or a combination thereof. A code such as a barcode or a two-dimensional code, or a coupon may also correspond to the payment means. That is, the payment service may be available with any type of payment means, including so-called prepaid payment means, postpaid payment means, or debit payment means. As will be described in detail later, in the first embodiment, the store payment means provided as a benefit to the user is not a coupon, but a prepaid payment means with a balance, such as cash.

[0019] In the first embodiment, a case where a payment service is used from a payment app installed on the user terminal 20 is described, but the payment service can be used from any medium other than the payment app. For example, the payment service may be used with an IC chip, IC card, or magnetic card included in the user terminal 20. In addition, for example, the payment service may be used only with biometric authentication such as facial recognition, without using the user terminal 20 or a card. For example, after completing a predetermined user registration from the payment app, the user can log in to the payment service by entering their user ID and password, and then become able to use the payment service.

[0020] 2 is a diagram showing an example of a payment app screen. When a user logs in to the payment service, a home screen G1 of the payment app is displayed on the display unit 25. The home screen G1 displays a code C10 for using the payment method set as the payment source. In the first embodiment, a case where cash is set as the payment source is described, but the payment source can be changed to another payment method such as a credit card or bank account.

[0021] For example, a payment app not only allows users to make payments using cash, but also allows users to send cash to other users. A user can switch between functions of the payment app by selecting buttons B11 and B12. In the first embodiment, a case where a user uses cash at a store is described, and therefore, in FIG. 2, button B11 is shown selected. The store is a member store of the payment service. The store may be of any type, for example, a retail store such as a convenience store, or a food service establishment such as a restaurant.

[0022] When paying at a store, the user displays the home screen G1 on the display unit 25. For example, when a store clerk reads the code C10 with the reading device 36, a predetermined payment process is executed between the store terminal 30 and the server 10. The payment process itself can use various known processes. In the first embodiment, cash is set as the payment source, so the payment process executes a process to reduce the cash balance.

[0023] When the payment process is complete, a payment completion screen G2 indicating that the payment process has been completed is displayed on the display unit 25. In FIG. 2, when individual payment completion screens G2 are to be distinguished, an alphabet is added to the end of the G2 symbol. This is the same for the other drawings. The payment completion screen G2A is displayed when the user pays at "XXX Mart." The payment completion screen G2B is displayed when the user pays at "YYY Store."

[0024] In the first embodiment, when a user makes a payment at a specific store, the user is granted cash for that store. For example, when a user makes a payment at "XXX Mart," cash for "XXX Mart" is granted. This cash can only be used at "XXX Mart." Hereinafter, cash for a specific store is referred to as store cash. General-purpose cash that can be used at all affiliated stores is referred to as general-purpose cash. When there is no distinction between store cash and general-purpose cash, they are simply referred to as cash.

[0025] For example, when a user uses a store during a campaign, the store cash of this store is given to the user. In the example of FIG. 2, "XXX Mart" is holding a campaign. When the user uses "XXX Mart" as shown in the payment completion screen G2A, the store cash of "XXX Mart" is given. On the other hand, "YYY Store" is not holding a campaign. Even if the user uses "YYY Store" as shown in the payment completion screen G2B, the store cash is not given. The store cash of "XXX Mart" can be used for the next shopping at "XXX Mart". The store cash may be given together with other benefits such as points.

[0026] FIG. 3 is a diagram showing an example of the screen of the payment application when the store cash is given. As shown in FIG. 3, on the home screen G1, the remaining balance of the general cash and the remaining balance of the store cash are displayed. In the first embodiment, for the sake of simplicity of explanation, the store cash of "XXX Mart" is taken as an example, but there may be store cash of other stores. In this case, in order to be able to specify which store's store cash remaining balance it is, a display such as "store cash of XXX Mart" or "store cash of ZZZ Cafe" may be made.

[0027] For example, when the user visits "XXX Mart" and the code C10 is read, as shown in the payment completion screen G2C, the payment process using the store cash is executed. In the first embodiment, in the store where the store cash can be used, the store cash is preferentially used over the general cash. When the store cash alone is not enough, the general cash is used in combination. The payment completion screen G2C shows the case where a product worth 800 yen is purchased with the remaining balance of the store cash being 100 yen. In this case, for the store cash, the full 100 yen is used, and for the shortage of 700 yen, the general cash is used.

[0028] When the user uses store cash at "XXX Mart," store cash from "XXX Mart" is again provided. As shown in payment completion screen G2D, when the user visits "YYY Store" and code C10 is read, store cash from "XXX Mart" cannot be used, so only general-purpose cash is used. Note that the user may be able to specify whether or not to use store cash at "XXX Mart," or whether or not to use both store cash and general-purpose cash.

[0029] As described above, in the first embodiment, when a user uses cash at a specific store, the user is given store cash for that store as a benefit. The store cash can only be used at the store where the user used the cash. Therefore, the user will visit the same store again to use the store cash given to them as a benefit. In other words, the user can be motivated to return to the store. Details of the first embodiment will be described below.

[0030] [1-3. Functions realized in the first embodiment] FIG. 4 is a functional block diagram showing an example of functions realized in the first embodiment.

[0031] [1-3-1. Functions realized by the server] The data storage unit 100 is realized mainly by the storage unit 12. Each of the payment request receiving unit 101, the payment processing execution unit 102, the use privilege granting unit 103, and the use restriction unit 104 is realized mainly by the control unit 11.

[0032] [Data storage section] The data storage unit 100 stores data necessary for providing payment services to users. For example, the data storage unit 100 stores a user database DB.

[0033] 5 is a diagram showing an example of a user database DB. The user database DB is a database that stores information about users. For example, the user database DB stores a user ID, password, user name, code ID, cache information, and usage history information. When a user completes usage registration, a new record is created in the user database DB, and information such as the user ID of this user is stored.

[0034] A user ID is an example of user identification information that can identify a user. Therefore, any reference to a user ID can be read as user identification information. The user identification information may be any information, and other information such as an email address or a phone number may be used. A user ID is sometimes called an account. The user ID and password are used to log in to the payment service.

[0035] In this embodiment, some kind of user identification information needs to be included in the code C10 to identify the user who requested the payment process. Although the user ID may be included in the code C10, this embodiment describes a case where the code ID is included in the code C10. The code ID is a type of user identification information. The code ID is information different from the user ID. For example, the code ID is expressed by numbers, characters, or a combination of these.

[0036] A code ID is issued at any timing. An expiration date may be set for the code ID. For example, a code ID is issued when the app is launched, when the expiration date has passed, or when the user instructs reissue. The method for issuing the code ID itself may be any method. The code ID is issued so that it does not overlap with other code IDs within the expiration date. For example, the code ID is issued randomly.

[0037] Cache information is information about the cash held by a user. For example, the cache information includes the balance of general-purpose cash, the store ID of the store where the store cash can be used, and the balance of the store cash. The balance of the store cash is associated with the store ID of the store where the store cash can be used. The store ID is an example of store identification information that can identify a store. The store identification information may be information other than the store ID, such as the store's email address or phone number.

[0038] In the example of Figure 5, user "Yamada Taro" has 3,500 yen in general-purpose cash and 100 yen in store cash from a store identified by store ID "s00001." User "Kimura Hanako" in Figure 5 has 2,340 yen in general-purpose cash, 400 yen in store cash from a store identified by store ID "s00001," and 700 yen in store cash from a store identified by store ID "s00002." User "Suzuki Hideo" has 8,700 yen in general-purpose cash and no store cash.

[0039] In the examples of Figures 2 and 3, for the sake of simplicity, a single store cash is used as an example, but individual users, such as user "Kimura Hanako," can hold multiple store cashes. For example, an upper limit may be set for the number of store cashes a user can hold. For example, an upper limit may be set for the balance of each store cash. The upper limit may be a value common to all store cashes, or a value may be set for each store cash.

[0040] In the first embodiment, a case is described in which the store's cash balance increases when a payment service is used at a store, but the store's cash balance can be increased by any other method. For example, the store's cash balance may be increased as a bonus for visiting a store. The method for detecting a visit can be a known method, such as check-in using a code such as a barcode or two-dimensional code, check-in using short-range wireless communication, check-in using location information detected by GPS or the like, or check-in using biometric authentication such as facial recognition.

[0041] For example, it may be possible to charge store cash using other payment methods such as a credit card. In this case, it may be possible to charge store cash under more favorable conditions than charging general-purpose cash. For example, in the case of general-purpose cash, to charge 1,000 yen, a payment of the same amount of 1,000 yen using another payment method such as a credit card is required. In the case of charging store cash, even if 1,000 yen is charged, a bonus of 200 yen may be generated, allowing for a charge of 1,200 yen. The bonus may be a fixed amount or may be an amount depending on the payment amount.

[0042] For example, the balance of another payment method, such as electronic money or points, may be convertible into store cash. This conversion method itself can be any of various known methods, such as converting certain points into other points, converting points into electronic money, or converting electronic money into points. When converting the balance of another payment method into store cash, a bonus may be generated, or conversely, a predetermined fee may be generated. Additionally, for example, store cash may be provided as a benefit for using services other than payment services (e.g., e-commerce services, travel reservation services, communication services, or financial services).

[0043] Note that the cache information may include information other than the information illustrated in FIG. 5, and may include, for example, a cache ID. The cache ID is an example of cache identification information that can identify the cache. The cache identification information may be information other than the cache ID, and may be, for example, a cache number or the like. When a user has a plurality of caches, each cache is identified by the cache identification information. When a user has a general-purpose cache and a store-specific cache, the general-purpose cache and the store-specific cache are each identified by the cache identification information of the general-purpose cache and the cache identification information of the store-specific cache.

[0044] The usage history information is information related to the usage history of the payment service. For example, the usage history information includes the usage date and time, store identification information that can identify the store where the service was used, information that can identify the payment method used, and the usage amount. When the server 10 can obtain product information that can identify the products purchased by the user, the usage history information may include the product information. When a user uses the payment service, the usage history information of this user is updated.

[0045] Note that the information stored in the user database DB is not limited to the example in FIG. 5. For example, the user database DB may store payment method information related to payment methods other than caches. For example, when the payment method is a credit card, the payment method information includes the credit card number, expiration date, and cardholder information. When the payment method is electronic money, the payment method information includes an electronic money ID that can identify the electronic money and the balance of the electronic money. When the payment method is points, the payment method information includes a point ID that can identify the points and the balance of the points. Similarly, for other payment methods, the payment method information includes information that can identify the payment method. When a user can use a plurality of payment methods, it is assumed that the payment method information also includes information that can identify the payment method of the payer. The payment method of the payer can be changed by the user.

[0046] In addition, the data stored in the data storage unit 100 is not limited to the user database DB. For example, the data storage unit 100 may store a store database related to the store. The store database stores various information such as a store ID, a store name, an address, an area, a store terminal ID, whether a campaign is being held, and whether there is store cash. The store terminal ID is terminal identification information that can identify the store terminal 30. The terminal identification information may be other information such as an IP address or the individual identification information of the store terminal 30.

[0047] [Payment request reception unit] The payment request reception unit 101 receives a payment request for using cash at a store where cash can be used. Hereinafter, a store to which store cash is given is referred to as a first store. The first store is a store where store cash can be used. The first store is a store where the user has used the payment service. The cost for giving store cash may be borne by the first store or by the administrator of the payment service. In the first embodiment, the store that holds a campaign for giving store cash corresponds to the first store. The payment request is a notification for requesting the execution of payment processing. The payment request is made by transmitting data in a predetermined format.

[0048] In this embodiment, when the code C10 is read by the reading device 36, the store terminal 30 acquires the code ID included in the code C10. The store terminal 30 transmits a payment request including this code ID to the server 10. For example, the payment request includes a store ID, a code ID, and an amount used. The payment request reception unit 101 receives the payment request by receiving the payment request from the store terminal 30. The payment request reception unit 101 may receive the payment request via another computer other than the store terminal 30.

[0049] Note that the information included in the payment request is not limited to the example of the first embodiment. The payment request can include any information. For example, the payment request may include a store terminal ID. Instead of the store ID, the store terminal ID may be used to identify from which store the payment request is made. Additionally, for example, the payment request may include product information regarding the product the user intends to purchase or service information regarding the service the user intends to use.

[0050] [Payment Processing Execution Unit] When a payment request is received, the payment processing execution unit 102 executes payment processing. For example, when a payment request is received, the payment processing execution unit refers to the user database DB and acquires cache information associated with the code ID included in the payment request. The user identified by this code ID is the user who made the payment request (for example, the user who presented the code ID to the store clerk). The payment processing execution unit 102 executes payment processing based on this cache information. The payment processing execution unit 102 updates the usage history information associated with the code ID included in the payment request based on the execution result of the payment processing. The payment processing execution unit 102 transmits the execution result of the payment processing to the store terminal 30.

[0051] The payment processing of the first embodiment is a process of reducing the remaining balance of the cache. The payment processing can also be said to be a process of consuming the cache or a process of completing the payment using the cache. As described above, various known methods can be used for the payment processing itself. For example, as methods of using the payment service, there are a method of reading a code posted in the store with the user terminal 20 and a method of the user operating the user terminal 20 to select the store to use. In these cases, the user terminal 20, rather than the store terminal 30, transmits a payment request to the server 10. The payment processing execution unit 102 executes payment processing based on the payment request from the user terminal 20.

[0052] In the first embodiment, the use restriction unit 104, which will be described later, determines whether or not to permit the use of store cash. If a user identified by the code ID included in the payment request holds multiple store cashes, the use restriction unit 104 selects a store cash that is permitted for use from among the multiple store cashes. The use restriction unit 104 may not permit the use of all of the multiple store cashes.

[0053] If it is determined that the use of store cash is permitted, the payment processing execution unit 102 executes the payment processing so that at least the balance of store cash is reduced. If the use restriction unit 104 does not determine that the use of store cash is permitted, the payment processing execution unit 102 executes the payment processing so that the balance of store cash is not reduced and the balance of general-purpose cash is reduced.

[0054] The payment processing execution unit 102 can execute payment processing using both store cash and general-purpose cash. For example, when store cash alone is insufficient, the payment processing execution unit 102 executes payment processing so as to also use general-purpose cash. Using both store cash and general-purpose cash means reducing both the balance of store cash and the balance of general-purpose cash.

[0055] If the user identified by the code ID included in the payment request does not have store cash, the processing by the usage restriction unit 104 is omitted. In this case, the payment processing execution unit 102 executes the payment processing so as to reduce the balance of general-purpose cash held by the user. The payment processing execution unit 102 may determine whether the user has store cash based on the user's cache information. This determination may be executed by the usage restriction unit 104.

[0056] When it is determined that the store cash is to be used, the settlement processing execution unit 102 determines whether the balance of the store cash is sufficient based on the amount used included in the settlement request. When the settlement processing execution unit 102 determines that the balance of the store cash is sufficient, it executes the settlement processing so that the store cash decreases by the amount used. The process of decreasing the balance of the store cash itself may be the same as the process of decreasing the balance of the general-purpose cash. When the settlement processing execution unit 102 determines that the balance of the store cash is insufficient, it executes the settlement processing so as to use the general-purpose cash and the store cash in combination. For example, the settlement processing execution unit 102 executes the settlement processing so as to use all of the store cash and make up the shortfall with the general-purpose cash.

[0057] When it is not determined that the store cash is to be used, the settlement processing execution unit 102 may execute the settlement processing based on the general-purpose cash. This settlement processing is the same as the conventional method. If the balance of the general-purpose cash is insufficient, the settlement processing will result in an error. Similarly, when using the general-purpose cash and the store cash in combination, if the total balance of these is insufficient, the settlement processing will result in an error. When the total balance of the general-purpose cash and the store cash is insufficient, it may be possible to make a payment in combination with other settlement means such as electronic money or points. Even if the balance of the cash is sufficient, it may be possible to make a payment in combination with other settlement means. The use of other settlement means in this case is sometimes called appropriation.

[0058] Note that even if only the store cash is sufficient, the settlement processing execution unit 102 may execute the settlement processing using the store cash and the general-purpose cash in combination. For example, when the balance will be less than the threshold if the settlement processing is executed only with the store cash, the settlement processing execution unit 102 may execute the settlement processing using the store cash and the general-purpose cash in combination. Another example is that the settlement processing execution unit 102 may execute the settlement processing so as to use the store cash and the general-purpose cash in a predetermined ratio regardless of the balance of the store cash.

[0059] Furthermore, the payment processing execution unit 102 may execute the payment processing so that payment is completed using only general-purpose cash, even if the user has store cash. If the user does not have store cash, the payment processing execution unit 102 may execute the payment processing so that payment is completed using only general-purpose cash. If the user has store cash for each of multiple stores, the payment processing execution unit 102 may execute the payment processing so that the balance of store cash associated with the store ID included in the payment request is reduced.

[0060] [User Benefits Granting Department] The usage privilege granting unit 103 grants a store cash balance for a store as a privilege to a user who uses cash at a store. This balance is the balance of a payment method that can be used at that store. Granting a store cash balance includes both granting new store cash to a user who does not have store cash and increasing the store cash balance of a user who already has store cash. For example, the usage privilege granting unit 103 grants a privilege to a user by increasing the store cash balance for that store (adding value to the balance). Hereinafter, the user who requests payment processing is referred to as the first user. In the first embodiment, the user identified by the code C10 included in the payment request corresponds to the first user. The first user can also be said to be a user who receives store cash as a privilege.

[0061] Store cash is cash that can be used at a first store. Store cash is cash that cannot be used at a second store. A second store is a store that cannot use the store cash of a first store. A second store is a store that is different from the first store. For example, a second store is a store that is not affiliated with the first store. Even if the second store is a store that is different from the first store, a store that can use the store cash of a first store does not qualify as a second store. For example, a store that can use the store cash of a first store is an affiliated store in the same store group as the first store, or a store that is affiliated with the first store.

[0062] In the first embodiment, a case will be described in which the store cash is usable only at the first store. However, the store cash may also be usable at stores other than the first store. For example, store cash for "XXX Mart" may be usable not only at "XXX Mart" but also at "ZZZ Cafe," which is affiliated with "XXX Mart." In another example, store cash acquired by a user using "XXX Mart Store A" may be usable not only at "XXX Mart Store A" but also at "XXX Mart Store B," which is an affiliated store of the same store group. In this case, it is assumed that the store IDs of the first stores at which each store cash can be used are defined in the data storage unit 100. If one store cash can be used at multiple first stores, multiple store IDs are associated with one store cash.

[0063] When a payment process is executed, the usage benefit granting unit 103 grants store cash, which is cash for the first store, as a benefit to the first user who used the cash. Granting store cash means making the store cash available for use. For example, increasing the store cash balance held by the first user or granting new store cash to a first user who does not have store cash corresponds to granting store cash. Granting new store cash means associating information related to the store cash with a user ID or a code ID. This information may be any information related to the store cash, such as the store cash balance or the cache ID of the store cash.

[0064] For example, when the first user does not yet possess the store cash, the benefit granting unit 103 grants the store cash to the first user by adding the store ID and the remaining balance of the store cash to the cash information. When the first user already possesses the store cash, the benefit granting unit 103 grants the store cash to the first user by increasing the remaining balance of the store cash included in the cash information. The method of granting cash to the user itself can utilize various known methods and is not limited to these examples. For example, when using blockchain as in the modification example described later, the store cash may be granted by generating a new token, or the store cash may be granted by increasing the balance associated with an existing token.

[0065] Note that an example has been described in which when a user uses cash at a store, the store cash of this store is granted as a benefit to this user. However, the payment method used by the user at the store and the payment method granted as a benefit to this user may be of different types. For example, when a user uses a credit card at a store, the store cash of this store may be granted as a benefit to this user. That is, when a user uses a payment method other than cash, the store cash of this store may be granted as a benefit.

[0066] [Usage Restriction Unit] The usage restriction unit 104 restricts the use of the store cash at the second store. The second store is a store where the store cash cannot be used. The second store is a store different from the first store. For example, when a payment request is received from the store terminal 30 of the second store, the usage restriction unit 104 controls the payment processing execution unit 102 to execute the payment processing based on general-purpose cash instead of the store cash of the first store.

[0067] For example, when a settlement request is received, the usage restriction unit 104 refers to the user database DB and acquires cache information associated with the code ID included in the settlement request. The usage restriction unit 104 determines whether to use the store cache based on the store ID included in the settlement request and the acquired cache information. For example, if the acquired cache information stores the store ID included in the settlement request, it means that the user identified by the code ID included in the settlement request holds the store cache. Therefore, in this case, the usage restriction unit 104 determines to use the store cache.

[0068] Note that the method for determining whether to use the store cache is not limited to the above example. For example, the cache ID of the store cache held by the user may be included in code C10, and the usage restriction unit 104 may determine whether to use the store cache using the cache ID included in code C10. In this case, when the store terminal 30 reads code C10 with the reading device 36, it transmits a settlement request including the cache ID acquired from code C10 to the server 10.

[0069] If the store cache identified by the cache ID included in the settlement request belongs to the store identified by the store ID included in the settlement request, the usage restriction unit 104 determines to use the store cache. If the store cache identified by the cache ID included in the settlement request does not belong to the store identified by the store ID included in the settlement request, the usage restriction unit 104 does not determine to use the store cache. Even when the settlement request does not include the cache ID of the store cache, the usage restriction unit 104 does not determine to use the store cache.

[0070] The relationship between the cache ID of each store cache and the store that can use this store cache is defined in the data storage unit 100. The store ID may be incorporated into part of the cache ID, so that it is possible to identify which store's store cache it is from the cache ID alone. It is sufficient to be able to identify whether the cache the user is trying to use is a store cache or not, and which store the store cache belongs to.

[0071] Alternatively, for example, the code C10 may include the store ID of the store cash held by the user, and the usage restriction unit 104 may use the store ID included in the code C10 to determine whether or not to use the store cash. In this case, the store terminal 30 reads the code C10 with the reader 36 and transmits a payment request including the store ID obtained from the code C10 to the server 10. A match between the store ID of the store where the store terminal 30 is located and the store ID obtained from the code ID means that the store cash can be used. The usage restriction unit 104 may determine whether or not to use the store cash by determining whether or not they match.

[0072] The method of restricting the use of the cash may be any of various known methods and is not limited to the example of the first embodiment. For example, the usage restriction unit 104 may use the methods of Patent Documents 1-6 described above to restrict the use of the store cash at the second store.

[0073] [1-3-2. Functions realized on user terminals] The data storage unit 200 is mainly realized by the storage unit 22. The display control unit 201 is mainly realized by the control unit 21. The data storage unit 200 stores data necessary for providing payment services. For example, the data storage unit 200 stores a payment app, a code ID, and the expiration date of the code ID. In addition, for example, the data storage unit 200 may store the cash ID and balance of cash held by the user. The display control unit 201 displays a code C10 including the code ID on the home screen G1 based on the payment app. The display control unit 201 also displays other screens described in Figures 2 and 3.

[0074] [1-3-3. Functions realized by store terminals] The data storage unit 300 is realized mainly by the storage unit 32. The payment request transmission unit 301 is realized mainly by the control unit 31. The data storage unit 300 stores data necessary for providing payment services. For example, the data storage unit 300 stores the store ID of the store where the store terminal 30 is located and the store terminal ID of the store terminal 30. The data storage unit 300 also stores a program for acquiring the code ID included in the code C10.

[0075] The payment request sending unit 301 sends a payment request to the server 10. For example, when the reader 36 reads the code C10, the payment request sending unit 301 acquires the code ID included in the code C10. The payment request sending unit 301 sends a payment request including the store ID, the code ID, and the amount used to the server 10. The code ID does not have to be acquired optically, but may be acquired through communication. For example, the store terminal 30 may acquire the code ID using Wi-Fi (registered trademark), Bluetooth (registered trademark), or infrared communication, or may acquire the code ID using short-range wireless communication adopted in known IC cards. The code ID may be input from the operation unit 34 of the store terminal 30.

[0076] [1-4. Processing Executed in the First Embodiment] FIG. 6 is a flowchart showing an example of the processing executed in the first embodiment. The processing shown in FIG. 6 is executed by each of the control units 11, 21, and 31 operating according to a program stored in each of the storage units 12, 22, and 32. When the processing of FIG. 6 is executed, it is assumed that the first user has completed registration for using the payment service and has installed the payment application on the user terminal 20.

[0077] When the first user activates the payment application, the user terminal 20 executes a login process with the server 10 (S100). In the login process, input of a user ID and password may be requested, or information indicating that the user has logged in in the past may be recorded in the user terminal 20, and input of the user ID and password may be omitted using this information. When the login process is successful, the user terminal 20 receives a code ID issued by the server 10 and causes the display unit 25 to display a home screen G1 including the code C10 (S101).

[0078] In S101, for a user who holds store cash, the balance of the store cash is displayed on the home screen G1 together with the balance of the general-purpose cash. This display may be performed based on the cash information of the logged-in user. In the first embodiment, the processing when the button B11 is selected will be described. The processing when the button B12 is selected will be described in the second embodiment.

[0079] When the code C10 is read by the reading device 36 of the store terminal 30, the store terminal 30 transmits a payment request including the store ID of the store where it is located, the code ID obtained from the code C10, and the usage amount to the server 10 (S102). When the server 10 receives the payment request from the store terminal 30 (S103), it determines whether to use the store cash based on the received payment request (S104). In S104, the server 10 determines whether to use the store cash by determining whether the store ID included in the payment request is included in the cash information associated with the code ID included in the payment request.

[0080] If it is determined that store cash will be used (S104; Y), the server 10 executes the payment process so that at least store cash will be used (S105). In S105, if the balance of store cash is insufficient, payment process is executed using general-purpose cash in combination. On the other hand, if it is not determined in S104 that store cash will be used (S104; N), the server 10 executes the payment process so that general-purpose cash will be used (S106). The payment process in S106 is the same as conventional payment process.

[0081] When the payment process is completed, the server 10 determines whether or not to grant store cash as a benefit to the first user (S107). In S107, the server 10 determines whether or not to grant store cash by determining whether or not the store ID included in the payment request is the store ID of the store that is the target of the store cash (in the first embodiment, the store that is participating in the campaign). It is assumed that the store ID of the store that is the target of the store cash is defined in advance in the storage unit 12.

[0082] If it is determined in S107 that store cash should be granted (S107; Y), the server 10 grants store cash to the first user (S108). In S108, the server 10 grants store cash to the first user by updating the cache information associated with the code ID included in the payment request. The server 10 transmits the execution result of the payment process to the user terminal 20 and the store terminal 30 (S109), and this process ends. A payment completion screen G2 is displayed on the user terminal 20, and a similar screen is displayed on the store terminal 30.

[0083] According to the settlement system S of the first embodiment, when a settlement request for using cash at the first store is received and settlement processing is executed, store cash is given to the first user who used cash, and the use of the store cash at the second store is restricted. As a result, since the first user will visit the first store again to use the store cash, the first user can be motivated to visit the first store again. Also, when giving a coupon of the first store, it is possible to give an incentive to visit the first store again, but by giving store cash that can be generally used in the first store, it is possible to give a stronger incentive to visit the first store again. Since the first user can use the store cash for the favorite products or services of the first store, the convenience of the first user is also enhanced.

[0084] In addition, the settlement system S can execute settlement processing using both store cash and general-purpose cash. As a result, when the store cash alone is not sufficient, the general-purpose cash can be used to complete the settlement, thereby enhancing the convenience of the user.

[0085] [2. Second Embodiment] In the first embodiment, the case where when the first user uses cash at the first store, store cash of the first store is given to the first user as a privilege for the first user was explained. In the second embodiment, the case where when the first user sends the store cash of the first store to another user, store cash of the first store is given to the first user as a privilege for the first user will be explained. Hereinafter, the other user will be referred to as the second user. In addition, in the second embodiment, the description of the same points as in the first embodiment will be omitted.

[0086] The second user is a user who receives cash. The second user is a user different from the first user. For example, the second user may be a user whose contact information is registered in the phone book of the user terminal 20, or may be a user who the first user inputs user identification information such as contact information and user ID from the user terminal 20.

[0087] Sending cash can mean moving cash, transferring cash, or ceding cash. Here, "sending" includes remittance. The first user can send all or part of their own cash to the second user. When the first user sends cash to the second user, the balance of the first user's cash decreases, and the balance of the second user's cash increases.

[0088] [2-1. Overview of the Second Embodiment] FIG. 7 is a diagram showing an example of the screen of the settlement application in the second embodiment. When the first user selects the button B12 on the home screen G1, the display switches to a display for the first user to send cash to the second user, as shown in the home screen G1 of FIG. 7. In the second embodiment, a case where the first user can send either general-purpose cash or store-specific cash to the second user will be described. The first user may be able to send only general-purpose cash to the second user, or may be able to send only store-specific cash to the second user.

[0089] For example, when the first user selects the button B13, general-purpose cash can be sent to the second user. When the first user selects the button B14, store-specific cash can be sent to the second user. In the second embodiment, the case where the first user sends store-specific cash to the second user will be described, but the same process applies when the first user sends general-purpose cash to the second user. If the first user holds multiple store-specific cash, any store-specific cash designated by the first user can be sent.

[0090] When the first user selects button B14, a selection screen G3 for selecting the second user is displayed on the display unit 25. For example, on the selection screen G3, those registered in the phone book of the user terminal 20 are displayed as candidates for the second user. The first user may specify the second user to whom to send the cash this time from among the second users to whom the user has sent cash in the past. When the first user selects the second user from the selection screen G3, an input screen G4 for inputting the amount and message is displayed on the display unit 25. Input of the message may be optional. Charging may be possible from the input screen G4.

[0091] When the first user inputs the amount and message and selects button B40, a completion screen G5 indicating that the in-store cash has been sent from the first user to the second user is displayed on the display unit 25. On the completion screen G5, information such as the amount and message that the first user sent to the second user is displayed. When the first user sends in-store cash to the second user as in the completion screen G5, in-store cash is granted to the first user as a privilege for the first user.

[0092] In the example of FIG. 7, a case is shown where the first user has in-store cash worth 1500 yen and sends 1200 yen worth of in-store cash to the second user. A privilege corresponding to the amount that the first user sent to the second user may be granted to the first user, or a fixed privilege may be granted to the first user regardless of the amount. The first user can use the in-store cash granted as a privilege for shopping at the first store, or can also send it to another second user. In the second embodiment, by granting a privilege when the first user sends in-store cash to the second user, the first user is motivated to send in-store cash. Hereinafter, the details of the second embodiment will be described.

[0093] [2-2. Functions realized in the second embodiment] FIG. 8 is a functional block diagram showing an example of functions realized in the second embodiment. First, the differences in the functions of server 10 will be described. The settlement processing execution unit 102, the usage restriction unit 104, the sending request reception unit 105, the sending processing execution unit 106, and the sending privilege granting unit 107 are mainly realized by the control unit 11. In the second embodiment, the settlement request reception unit 101 and the usage privilege granting unit 103 described in the first embodiment may not be realized.

[0094] For example, even if the settlement request reception unit 101 is not realized, the settlement processing execution unit 102 may execute settlement processing without receiving a settlement request. In this case, when a predetermined date and time arrives, the settlement processing execution unit 102 may execute settlement processing so that the cash decreases by a predetermined amount. For example, such monthly settlement processing may be executed for a user who uses a subscription that pays a fixed amount every month. For example, even if the first user uses the first store without the usage privilege granting unit 103 being realized, the store cash of the first store may not be granted as a privilege to the first user. For example, after the campaign of the first store ends, or before the campaign of the first store starts, the store cash of the first store is not granted to the first user.

[0095] [Settlement Processing Execution Unit] The settlement processing execution unit 102 executes settlement processing when the usage conditions defined for the cash of the first user are satisfied. The usage conditions are the conditions under which the use of the cash is permitted. For the store cash described in the first embodiment, the available stores are defined as usage conditions. The usage conditions may be arbitrary conditions and are not limited to stores. For example, the usage conditions may be the time zone, day of the week, period, area, product, service, user, or a combination thereof during which the cash can be used.

[0096] Whether the usage conditions defined for the cash are met is determined by the usage restriction unit 104. The settlement processing execution unit 102 executes the settlement processing so that the cash for which the usage conditions are met is used. That is, the settlement processing execution unit 102 executes the settlement processing so that the cash for which the usage conditions are not met is not used. In the second embodiment, a case where the stores where the cash can be used correspond to the usage conditions is described. For this reason, the processing of the settlement processing execution unit 102 may be the same as that in the first embodiment.

[0097] [Usage Restriction Unit] The usage restriction unit 104 restricts so that the cash for which the usage conditions are not met is not used. In the second embodiment, since a case where the stores where the cash can be used correspond to the usage conditions is described, the processing of the usage restriction unit 104 is the same as that in the first embodiment. When other conditions are defined as the usage conditions, the usage restriction unit 104 may determine whether to permit the use of the cash based on the other conditions defined as the usage conditions. Note that the usage restriction unit 104 may be realized by a system external to the settlement system S. In this case, the settlement system S can omit the usage restriction unit 104.

[0098] For example, when the time zone in which the cash can be used is defined as the usage condition, the usage restriction unit 104 determines whether the current time is the time zone in which the cash can be used, and if the current time is the time zone in which the cash can be used, it may permit the use of the cash. For example, when the day of the week on which the cash can be used is defined as the usage condition, the usage restriction unit 104 determines whether the current day of the week is the day of the week on which the cash can be used, and if the current day of the week is the day of the week on which the cash can be used, it may permit the use of the cash.

[0099] For example, when the available period for using the cash is defined as a usage condition, the usage restriction unit 104 determines whether the current date and time is within the available period for using the cash. If the current date and time is within the available period for using the cash, the usage of the cash may be permitted. For example, when the area where the cash can be used is defined as a usage condition, the usage restriction unit 104 determines whether the store that made the payment request is within a predetermined area. If this store is within the predetermined area, the usage of the cash may be permitted. Similarly, when other conditions are defined as usage conditions, the usage restriction unit 104 determines whether the usage conditions defined for the cash are satisfied. If the usage conditions are satisfied, the usage of the cash may be permitted.

[0100] [Send Request Reception Unit] The send request reception unit 105 receives a send request for sending cash from the first user to the second user. The send request is a notification for requesting the execution of the send process described later. The send request is made by transmitting data in a predetermined format. In the present embodiment, when the second user is selected from the selection screen G3 and the amount and message are input from the input screen G4 on the user terminal 20, the user terminal 20 transmits a send request including the user identification information of the first user, the user identification information of the second user, the amount, and the message to the server 10. The send request reception unit 105 receives the send request by receiving the send request from the user terminal 20.

[0101] Note that the send request can include arbitrary information. The information included in the send request is not limited to the example of the second embodiment. For example, the send request may include the cash ID of the cash selected by the first user. In this case, the cash ID can be used to identify which cash is the target. Also, the user identification information of the second user included in the send request may be arbitrary information such as a user ID, an email address, or a phone number. It is sufficient that the send request includes some information that can identify the first user and the second user. Further, the send request may include information that can identify whether to send a general cash or a store-specific cash with defined usage conditions.

[0102] [Forwarding Process Execution Unit] When a forwarding request is received, the forwarding process execution unit 106 executes a forwarding process. For example, when a forwarding request is received, the forwarding process execution unit 106 refers to the user database DB and acquires cache information associated with the user identification information of the first user included in the forwarding request and cache information associated with the user identification information of the second user included in the forwarding request. Based on this cache information, the forwarding process execution unit 106 executes a forwarding process. Based on the execution result of the forwarding process, the forwarding process execution unit 106 updates the usage history information of the first user and the usage history information of the second user. The forwarding process execution unit 106 transmits the execution result of the forwarding process to the user terminal 20. Various known methods can be used for the forwarding process itself.

[0103] For example, the forwarding process execution unit 106 executes a forwarding process by updating the cache information of the first user so that the remaining balance of the cache of the first user decreases based on the forwarding request and updating the cache information of the second user so that the remaining balance of the cache of the second user increases. The amount of decrease in the cache of the first user may be the same as the amount included in the forwarding request or may be an amount with a predetermined fee added. The amount of increase in the cache of the second user may be the same as the amount included in the forwarding request or may be an amount with a predetermined fee subtracted.

[0104] [Forwarding Privilege Granting Unit] When the sending process is executed, the sending privilege granting unit 107 grants a privilege to the first user. While the usage privilege granting unit 103 described in the first embodiment grants a privilege when the settlement process is executed, the sending privilege granting unit 107 grants a privilege when cash is sent from the first user to the second user. In the second embodiment, the sending privilege granting unit 107 will describe the case of granting store cash to the first user as a privilege, but the privilege granted to the first user may be other privileges and is not limited to store cash. For example, the sending privilege granting unit 107 may grant other settlement means such as electronic money, points, or coupons to the first user. Additionally, for example, the sending privilege granting unit 107 may grant information such as campaign notifications to the first user, or may grant an item that the first user can receive as a privilege.

[0105] For example, the sending privilege granting unit 107 may grant a privilege to the first user according to the usage conditions of the cash. The sending privilege granting unit 107 grants a privilege associated with the usage conditions defined for the cash to the first user. It is assumed that the relationship between the usage conditions of the cash and the privilege when sending this cash is stored in advance in the data storage unit 100. The sending privilege granting unit 107 grants a privilege associated with the usage conditions of the cash sent by the first user to the second user to the first user.

[0106] For example, as in the second embodiment, if a store is defined as a usage condition, the store cash of this store is defined as a privilege. When the first user sends the store cash of a certain store to the second user, the sending privilege granting unit 107 grants the store cash of this store to the first user as a privilege for the first user. In this case, the sending privilege granting unit 107 may grant the store cash of another store to the first user as a privilege, or may grant cash with other defined usage conditions.

[0107] For example, if a time period is defined as a usage condition, a time period cache, which is a cache for this time period, is defined as a privilege. When the sending privilege granting unit 107 determines that the first user has sent the time period cache of a certain time period to the second user, as a privilege to the first user, the store cache of this time period is granted. In this case, the sending privilege granting unit 107 may grant, as a privilege to the first user, the time period cache of another time period, or may grant a cache with other defined usage conditions.

[0108] For example, if an area is defined as a usage condition, an area cache, which is a cache for this area, is defined as a privilege. When the sending privilege granting unit 107 determines that the first user has sent the area cache of a certain area to the second user, as a privilege to the first user, the store cache of this area is granted. In this case, the sending privilege granting unit 107 may grant, as a privilege to the first user, the area cache of another area, or may grant a cache with other defined usage conditions.

[0109] Note that the sending privilege granting unit 107 may grant a privilege to the first user regardless of the usage conditions of the cache sent from the first user to the second user. The sending privilege granting unit 107 may grant a privilege randomly selected from a plurality of privileges to the first user. The sending privilege granting unit 107 may grant the privilege specified by the first user to the first user. The sending privilege granting unit 107 may determine the amount of the privilege based on the amount of the cache sent from the first user to the second user, or may grant an amount of privilege unrelated to this amount to the first user.

[0110] Furthermore, when a first user sends general-purpose cash to a second user, the sending reward granting unit 107 may grant store cash from a certain store as a reward to the first user. This store may be determined randomly, or may be a store that the first user regularly uses and that is identified based on the first user's usage history information. Alternatively, for example, this store may be a store that the first user has registered as a favorite store. Conversely, when a first user sends store cash to a second user, the sending reward granting unit 107 may grant general-purpose cash as a reward to the first user.

[0111] Furthermore, the functions of the user terminal 20 and the store terminal 30 are similar to those of the first embodiment, but the user terminal 20 includes a send request sending unit 202. The send request sending unit 202 is realized mainly by the control unit 21. The send request sending unit 202 sends a send request to the server 10 based on an operation by the first user. For example, the send request sending unit 202 sends a send request to the server 10 when the first user selects a second user from the selection screen G3 and inputs an amount and a message from the input screen G4.

[0112] [2-3. Processing performed in the second embodiment] Fig. 9 is a flow diagram showing an example of processing executed in the second embodiment. The processing shown in Fig. 9 is executed by the control units 11 and 21 operating in accordance with programs stored in the storage units 12 and 22, respectively. The processing in S200 and S201 is similar to the processing in S100 and S101. Here, the processing when the button B12 on the home screen G1 is selected will be described.

[0113] When the first user selects button B13 or button B14, the user terminal 20 causes the selection screen G3 to be displayed on the display unit 25 and accepts the selection of the second user (S202). The user terminal 20 causes the input screen G4 to be displayed on the display unit 25 and accepts the input of the amount and the message (S203). When button B40 is selected, the user terminal 20 transmits a sending request including the user identification information of the first user, the user identification information of the second user, the cash identification information of the cash to be sent, the amount, and the message to the server 10 (S204).

[0114] When the server 10 receives the sending request from the user terminal 20 (S205), it determines the type of cash indicated by the sending request (S206). When the sending request indicates the store cash (S206; store cash), the server 10 executes a money transfer process so that the store cash of the first user is sent (S207). The server 10 grants the store cash to the first user (S208), and this process ends. When the sending request indicates the general-purpose cash (S206; general-purpose cash), the server 10 executes a settlement process so that the general-purpose cash is sent (S209), and this process ends. In this case, it is assumed that no privilege is given to the second user, but some privilege may be given to the second user.

[0115] According to the payment system S of the second embodiment, when a request to send store cash is accepted and a sending process is executed, a benefit is granted to the first user. This can motivate the first user to send store cash to the second user. For example, instead of simply holding store cash that the first user does not plan to use in the near future, the first user can send it to the second user, encouraging the second user to use the store cash. As a result, the use of store cash in the payment service can be promoted. Even if the store can use store cash, the second user may use the store cash even if the first user does not use it, thereby increasing the effectiveness of attracting customers to the store. Since the first user will try to send store cash to the second user in order to receive the benefit, the sending of store cash from the first user to the second user can be promoted.

[0116] Furthermore, the payment system S grants a benefit to the first user according to the conditions for using the cash. This allows the first user to grant a benefit related to the conditions for using the cash sent to the second user, thereby providing the first user with a stronger motivation to send store cash to the second user. For example, if the first user sends store cash from a certain store to the second user, granting the store cash from that store to the first user prevents the first user's store cash from being completely depleted, thereby providing the first user with a stronger motivation to send store cash to the second user. Since the first user may visit the store again to use the store cash granted as a benefit, this can also increase the store's customer attraction effect.

[0117] In addition, the payment system S grants the first user a cash with the same usage conditions as the cash sent by the first user to the second user as a privilege for the first user. As a result, since it is possible to grant the first user a cash with the same usage conditions as the cash sent by the first user to the second user, it is possible to more strongly motivate the first user to send the store cash to the second user. For example, when the first user sends the store cash of a certain store to the second user, by granting the store cash of this store to the first user, it is possible to prevent the store cash of the first user from being completely depleted, so it is possible to more strongly motivate the first user to send the store cash to the second user. Since the first user may visit the store again to use the store cash granted as a privilege, it is also possible to enhance the customer attraction effect on the store.

[0118] In addition, the payment system S grants the first user the store cash as a privilege. As a result, it is possible to more strongly motivate the first user to send the store cash to the second user.

[0119] [3. Third Embodiment] In the first embodiment and the second embodiment, for the sake of simplicity of explanation, the case of mainly using or sending one store cash was mainly described. In the third embodiment, the case where there are a plurality of cashes with defined usage conditions will be described. The meaning of the usage conditions is as described in the second embodiment. In the third embodiment, as in the second embodiment, a store will be described as an example of the usage conditions. In the third embodiment, the description will be omitted for the same points as in the first embodiment or the second embodiment.

[0120] [3-1. Outline of the Third Embodiment] FIG. 10 is a diagram showing an example of a screen of a payment application in the third embodiment. When a first user uses Store A of "XXX Mart" as in the home screen G1A and the payment completion screen G2E of FIG. 10, a store cash available at Store A of "XXX Mart" and a store group cash available at all stores of "XXX Mart" are given to the first user. This store cash can be used only at Store A of "XXX Mart" and cannot be used at other stores of "XXX Mart" or stores other than "XXX Mart". The store group cash can be used at any store as long as it is a store named "XXX Mart". For example, the store group cash can also be used at Store B of "XXX Mart".

[0121] When the store cash and the store group cash are given to the first user, as in the home screen G1B, the balance of the general cash, the balance of the store cash, and the balance of the store group cash are displayed. When the first user visits Store A of "XXX Mart" again and the code C10 is read by the reading device 36, since both the store cash and the store group cash can be used, payment processing is executed based on a predetermined priority order.

[0122] In the third embodiment, the store cash of Store A of "XXX Mart" has a higher priority than the store group cash. That is, the store cash that can be used only at a specific store, Store A of "XXX Mart", has a higher priority than the store group cash that can be used at all stores of "XXX" Mart. As in the payment completion screen G2F, the store cash is preferentially used over the store group cash.

[0123] For example, suppose a first user has store cash worth 100 yen at store A of "XXX Mart" and store group cash worth 50 yen that can be used at all stores of "XXX Mart." If the first user makes a purchase worth 120 yen at store A of "XXX Mart," the store cash will be used first. The store group cash will be used to make up the remaining 20 yen of the store cash. In this way, in the third embodiment, priority is set for each of the multiple cashes held by the first user, thereby improving convenience for the first user. Details of the third embodiment will be described below.

[0124] [3-2. Functions realized in the third embodiment] 11 is a functional block diagram showing an example of functions realized in the third embodiment. The functions of the user terminal 20 and the store terminal 30 are the same as those in the first embodiment, so here, differences in the functions of the server 10 will be explained. The payment request receiving unit 101, payment processing execution unit 102, usage restriction unit 104, and identification unit 108 are mainly realized by the control unit 11. In the third embodiment, the usage privilege granting unit 103 described in the first embodiment may not be realized, and the sending request receiving unit 105, sending processing execution unit 106, and sending privilege granting unit 107 described in the second embodiment may not be realized.

[0125] [Payment request reception department] The payment request receiving unit 101 receives a payment request for a first user who holds multiple caches with different usage conditions. The payment request itself is as described in the first and second embodiments. In the third embodiment, as in the second embodiment, an example is given in which the usage conditions are the stores at which the cache can be used. For simplicity of explanation, two caches are used as an example: a store cache that can only be used at Store A of "XXX Mart" and a store group cache that can be used at all stores of "XXX Mart." However, the first user may hold three or more caches with different usage conditions.

[0126] For example, in addition to the two types of cash, the first user may have store cash that can only be used at "XXX Mart" store B, or store cash that can only be used at each "XXX Mart" store. Alternatively, the first user may have a mixture of cash with defined usage conditions, such as store group cash for other store groups, time period cash that can only be used at certain time periods, day of the week cash that can only be used on certain days of the week, and area cash that can only be used in a certain area. The cash balance displayed on the home screen G1 may be the total of general-purpose cash and multiple cashes with defined usage conditions.

[0127] [Payment Processing Execution Unit] When multiple cash registers are identified by the identification unit 108 (described later), the payment processing execution unit 102 executes the payment processing based on the priority of each of the multiple cash registers. In the third embodiment, when multiple cash registers are identified by the identification unit 108, the payment processing execution unit 102 executes the payment processing based on the priority of each of the multiple cash registers, which is determined so that the fewer the number of available stores, the higher the priority.

[0128] For example, a store cache that can only be used by Store A of "XXX Mart" can be used by fewer stores than a store group cache that can be used by all stores of "XXX Mart." Therefore, this store cache has a higher priority than the store group cache. In other words, the lower the versatility of a cache with defined usage conditions, the higher the priority. The stricter the usage restrictions on a cache with defined usage conditions, the higher the priority. A store cache that can only be used by a specific store has a higher priority because it is less versatile and has stricter usage restrictions than a store group cache. The payment processing execution unit 102 executes payment processing so that a cache with a relatively higher priority is used preferentially over a cache with a relatively lower priority.

[0129] For example, the settlement processing execution unit 102 executes settlement processing by using a cache with a relatively high priority and not using a cache with a relatively low priority. For example, the settlement processing execution unit 102 may execute settlement processing such that the usage amount increases as the priority increases. In the example of FIG. 10, since the priority of the store cache is higher than the priority of the store group cache, the settlement processing execution unit 102 makes the usage amount of the store cache larger than the usage amount of the store group cache.

[0130] Note that the method of setting the priority may be an arbitrary method and is not limited to the example of the third embodiment. Contrary to the third embodiment, the priority may increase as the number of available stores increases. For another example, a cache whose available time zone is defined as a usage condition may have a higher priority than a cache with other defined usage conditions. For example, a cache whose available store is defined as a usage condition may have a higher priority than a cache with other usage conditions such as a time zone or an area. For example, the priority may increase as the remaining balance of the cache increases.

[0131] [Usage restriction unit] The usage restriction unit 104 is the same as in the second embodiment. Note that the usage restriction unit 104 may be realized by a system external to the settlement system S. In this case, the settlement system S can omit the usage restriction unit 104.

[0132] [Specific unit] When a payment request is received, the specific part 108 specifies a cache that meets the usage conditions from among a plurality of caches. The determination method for each usage condition is as described in the second embodiment. In the third embodiment, since the stores where the cache can be used correspond to the usage conditions, when a payment request is received, the specific part 108 specifies, as a cache that meets the usage conditions, a cache that can be used at the store corresponding to the payment request from among a plurality of caches. The specific part 108 may specify a cache that meets the usage conditions by obtaining the determination result of the usage restriction part 104. The specific part 108 may specify a cache that meets the usage conditions by executing the same processing as the usage restriction part 104.

[0133] For example, assume that the first user holds two caches: a store-specific cache that can be used only at store A of "XXX Mart" and a store-group cache that can be used at all stores of "XXX Mart". When the first user visits store A of "XXX Mart", the specific part 108 can specify, based on the store ID included in the payment request, that the payment request is from store A of "XXX Mart". Therefore, the specific part 108 specifies that these two caches are available as caches that can be used at store A of "XXX Mart". When the first user visits another store of "XXX Mart", the specific part 108 can specify, based on the store ID included in the payment request, that the payment request is from store B of "XXX Mart". Therefore, the specific part 108 specifies that only the store-group cache that can be used at all stores of "XXX Mart" is available.

[0134] [3-3. Processing Executed in the Third Embodiment] FIG. 12 is a flow diagram showing an example of processing executed in the third embodiment. The processing in FIG. 12 differs in part from the processing in FIG. 6. For example, the processing in S300 to S303 is the same as the processing in S100 to S103. The server 10 identifies caches held by the first user that satisfy the usage conditions (S304). In S304, the server 10 refers to the user database DB and acquires cache information associated with the code ID included in the payment request. Based on the cache information, the server 10 identifies caches held by the first user and identifies, from these caches, caches that can be used at the store indicated by the store ID included in the payment request.

[0135] If multiple caches that satisfy the usage conditions are identified (S304; multiple), the server 10 executes the payment process based on the priority of each of the multiple caches (S305). For example, if a first user holds a store cache for "XXX Mart" store A and a store group cache for "XXX Mart", and a payment request is accepted from the store terminal 30 of "XXX Mart" store A, the server 10 identifies these two caches in S304. In S305, the server 10 executes the payment process with the store cache as the first priority and the store group cache as the second priority.

[0136] If only one cache that satisfies the usage conditions is identified (S304; 1), the server 10 executes the payment process based on the identified cache (S306). The payment process in S306 is the same as the payment process in the first embodiment. If no cache that satisfies the usage conditions is identified (S304; none), the server 10 executes the payment process based on a general-purpose cache (S307). The subsequent processes in S308 to S310 may be the same as the processes in S107 to S109 described in the first embodiment.

[0137] According to the payment system S of the third embodiment, when a plurality of cash are specified as cash that satisfies the usage conditions, payment processing is executed based on the priority order of each of the plurality of cash. This prevents the situation where cash is used in a way unintended by the user, improving the convenience for the user. By raising the priority order of the cash that the user wants to use, this cash can be preferentially used.

[0138] In addition, the payment system S specifies, as cash that satisfies the usage conditions, the cash that is available at the store corresponding to the payment request from among the plurality of cash. As a result, even if there are a plurality of cash that are available at the store where the user is trying to use the payment service, by assigning a priority order among them, the cash can be used in the way intended by the user, further improving the convenience for the user.

[0139] In addition, when a plurality of cash are specified as cash that satisfies the usage conditions, the payment system S executes payment processing based on the priority order of each of the plurality of cash, which is determined such that the fewer the number of available stores, the higher the priority. As a result, for example, it is possible to preferentially use the cash that is available only at a specific store and store the general-purpose cash that is available at a plurality of stores, further improving the convenience for the user.

[0140] [4. Modification Example] Note that the present disclosure is not limited to the embodiments described above. It can be appropriately changed without departing from the spirit of the present disclosure.

[0141] [4-1. Modification Example According to the First Embodiment] FIG. 13 is a diagram showing an example of a functional block of a modification example according to the first embodiment. The granting restriction unit 109, the profit generation unit 110, the change processing execution unit 111, the first fee generation unit 112, the first withdrawal processing execution unit 113, the second withdrawal processing execution unit 114, the second fee generation unit 115, the first detection unit 116, and the second detection unit 117 are mainly realized by the control unit 11.

[0142] [Variation 1-1] For example, the store cash may be usable during a first time period associated with a first store. In Variation 1-1, not only the stores in which the store cash can be used but also the time periods in which the store cash can be used are set as usage conditions.

[0143] The first time slot is a time slot designated in advance. Variation 1-1 describes a case where the first time slot is a relatively quiet time slot. A first store being relatively quiet means that at least one of the number of users and the amount spent is relatively low. The first time slot may be any time slot in which there is at least one other time slot that is busier than the first time slot. The first time slot is sometimes called idle time. The first time slot may be tallied by a store staff member or based on usage history information. For example, the server 10 tallies at least one of the number of users and the total amount spent at the first store for each time slot based on the usage time, location, and amount spent included in the usage history information.

[0144] The time slots may be divided in any manner, for example, every three hours or every six hours. The length of each time slot may vary. For example, the nighttime may be divided into roughly defined segments, while the daytime may be divided into smaller segments. In Variation 1-1, the first time slot corresponds to the time slot with the fewest number of users and the smallest total amount of usage. However, a predetermined number of time slots may be designated as the first time slot in descending order of the number of users and the smallest total amount of usage. Furthermore, the first time slot may be any time slot associated with the first store and is not limited to a relatively quiet time slot. For example, the first time slot may be a time slot designated as a time slot for running a campaign, a time slot when the first store is relatively busy, a time slot when there are relatively many store staff at the first store, a time slot when specific tasks such as loading and displaying do not occur at the first store, or a time slot immediately after the specific tasks are completed.

[0145] The privilege granting unit 103 grants store cash set as one of the usage conditions for the first time period to the first user as a privilege. For example, if "XXX Mart" located in an office district is relatively empty from 14:00 to 17:00 when company employees rarely use it, the first time period is from 14:00 to 17:00. The privilege granting unit 103 grants store cash that can only be used at "XXX Mart" and only from 14:00 to 17:00 to the first user.

[0146] The usage restriction unit 104 restricts the store cash from being used at the second store and restricts the store cash from being used at the first store during the second time period. The second time period is the time period when the store cash of the first store cannot be used. The second time period is a different time period from the first time period. Note that the method of preventing the store cash from being used at the second store is as described in the first embodiment. The usage restriction unit 104 determines whether the current time is the second time period. If the current time is the second time period, the usage restriction unit 104 restricts the use of the store cash. If the current time is the first time period, the usage restriction unit 104 permits the use of the store cash.

[0147] According to Modification Example 1-1, the store cash can be used during the first time period associated with the first store, and is restricted so that the store cash cannot be used at the second store and cannot be used at the first store during the second time period. Thereby, the customer attraction effect during the first time period designated as the time when it is desired to increase customer attraction to the first store is enhanced. For example, by designating the time period when the first store is relatively empty as the first time period, the customer attraction effect during the time period when the first store is relatively empty is enhanced.

[0148] [Modification Example 1-2] For example, store cash may be usable at a first store and a third store located in a first area that includes the first store. The first area is an area that includes the location of the first store. The first area may be a prefecture or city, town, or village, or may be an area defined independently by the payment service. The third store may be an affiliated store of the same store group as the first store, or may be another store affiliated with the first store, but in variant example 1-2, the relationship between the third store and the first store is not important as long as it is located in the same area as the first store.

[0149] The third store is another store that belongs to the same first area as the first store. The third store is a store that the user has not visited when the store cache is granted. The store cache of variant 1-2 has a first area defined as a condition for use. Stores located in the first area are assumed to be predefined in the data storage unit 100. In other words, the first store and the third store that can use the store cache are assumed to be predefined in the data storage unit 100.

[0150] The usage benefit granting unit 103 grants, as a benefit to the first user, store cash in which the first area is set as one of the usage conditions. This store cash is cash for the first area, so it can also be called area cash. For example, if the area unit is a city, ward, town, or village, when the first user visits "XXX Mart" in Itabashi Ward, Tokyo, the usage benefit granting unit 103 grants to the first user store cash that can be used at the first store "XXX Mart" in Itabashi Ward and a third store in the same Itabashi Ward.

[0151] The usage restriction unit 104 restricts the use of the store cash at a second store located in the second area. The second area is an area where the store cash in the first area cannot be used. The second area is an area different from the first area. When the usage restriction unit 104 receives a payment request, it determines whether the area to which the store that sent the payment request belongs is the second area. If it is determined to be the second area, the usage restriction unit 104 restricts the use of the store cash. If it is not determined to be the second area, that is, if it is determined to be the first area, the usage restriction unit 104 allows the use of the store cash.

[0152] According to variant 1-2, the store cash can be used at a first store and a third store in a first area including the first store, but is restricted so that it cannot be used at a second store in a second area. This can motivate the first user to return to the first area. For example, when a campaign is held to promote a certain city, town, or village, cash exclusive to that city, town, or village can be issued.

[0153] [Variation 1-3] For example, by combining the first embodiment with some of the functions described in the second embodiment, a first user may send store cash, which has been granted as a reward for using a first store, to a second user. The payment system S of Modification 1-3 includes the sending request receiving unit 105 and the sending process executing unit 106 described in the second embodiment. The request receiving unit 105 and the sending process executing unit 106 are as described in the second embodiment. Modification 1-3 describes a case where the payment system S does not include the sending reward granting unit 107.

[0154] The usage restriction unit 104 restricts the second user from using the store cash at the second store. The second embodiment differs from the first embodiment only in that the store cash held by the second user is subject to the restriction, and the restriction method itself by the usage restriction unit 104 is the same as that described in the first embodiment.

[0155] According to Modification Examples 1-3, when a send request for sending store cash from a first user to a second user is received, a sending process is executed, and the second user is restricted from using the store cash at the second store. Even if the first user has no plan to use the store cash, by sending the store cash from the first user to the second user, the second user can use the store cash, and the store cash can be effectively utilized.

[0156] [Modification Example 1-4] For example, in Modification Example 1-3, a case where the settlement system S does not include the send privilege granting unit 107 has been described. However, by combining the first embodiment and the second embodiment, the settlement system S may include the send privilege granting unit 107. The send privilege granting unit 107 is as described in the second embodiment.

[0157] According to Modification Example 1-4, when the sending process is executed, store cash is granted as a privilege to the first user. Thereby, the first user can be motivated to send the store cash to the second user.

[0158] [Modification Example 1-5] For example, the settlement system S may include a granting restriction unit 109. The granting restriction unit 109 restricts the repeated granting of store cash by the send privilege granting unit 107 due to the repeated sending of store cash between the first user and the second user.

[0159] For example, even if the first user sends store cash to the second user and then the second user sends store cash to the first user, the granting restriction unit 109 restricts the granting of a privilege to the second user by the sending privilege granting unit 107. If the second user sends store cash to the first user after using all of the store cash received from the first user (after using store cash in an amount greater than the amount received), a privilege may be granted to the second user. As another example, if the second user sends store cash to the first user in an amount greater than the amount received from the first user, a privilege may be granted to the second user for the excess amount.

[0160] For example, if the first user sends a first store cash to the second user and the second user sends store cash to the first user, and then the first user sends a second store cash to the second user, the granting restriction unit 109 may restrict the granting of a benefit to the first user. In this case, if the first user sends a second store cash amount that is equal to or greater than the amount received from the second user, the first user may be granted a benefit for the excess amount.

[0161] Note that the restriction method by the granting restriction unit 109 is not limited to the above example. For example, the granting restriction unit 109 may restrict the granting of a benefit to at least one of the first user and the second user for a certain period of time after the first user sends store cash to the second user, even if store cash is sent between the first user and the second user. As another example, the granting restriction unit 109 may restrict the granting of a benefit to at least one of the first user and the second user, even if store cash is sent between the first user and the second user, until the second user uses up the store cash sent by the first user to the second user.

[0162] According to Modification Examples 1-5, by repeatedly sending store cash between the first user and the second user, it is restricted that store cash is repeatedly granted as a privilege. As a result, it is possible to prevent the first user and the second user from repeatedly obtaining privileges by sending without using the store cash.

[0163] [Modification Example 1-6] For example, in the second embodiment, Modification Examples 1-3, and Modification Example 1-4, the case where the first user sends the store cash held by himself / herself to the second user was described. The first user may convert the general-purpose cash held by himself / herself into store cash and then send it to the second user. The settlement system S of Modification Example 1-6 includes a usage restriction unit 104, a send request reception unit 105, and a send process execution unit 106, similar to Modification Examples 1-3 and 1-4. The usage restriction unit 104 and the send request reception unit 105 are the same as those in Modification Examples 1-3 and 1-4, but the usage restriction unit 104 and the send process execution unit 106 are different from those in Modification Examples 1-3 and 1-4.

[0164] When a send request is received, the send process execution unit 106 of Modification Example 1-6 executes a send process so that store cash is sent to the second user using general-purpose cash, which is a general-purpose settlement means. For example, the send process execution unit 106 converts the general-purpose cash held by the first user into store cash and then executes the send process. Converting general-purpose cash into store cash means decreasing the balance of the general-purpose cash and increasing the balance of the store cash. In Modification Example 1-6, the case where the decrease amount of the balance of the first user's general-purpose cash is the same as the increase amount of the second user's store cash is described, but as in Modification Example 1-7 described later, these may be different.

[0165] According to Modification Examples 1-6, the sending process is executed so that the store cash is sent to the second user by using the general-purpose cash. As a result, even if the store cash held by the first user is insufficient, the first user can deposit the store cash by using the general-purpose cash, which improves the convenience for the user.

[0166] [Modification Example 1-7] For example, the settlement system S may include a profit generation unit 110. The profit generation unit 110 generates at least one of the profits of the first user and the second user that does not occur when the sending process using the store cash is executed when the sending process using the general-purpose cash is executed. The sending process using the general-purpose cash is the sending process described in Modification Examples 1-6. The sending process using the store cash is the sending process described in the second embodiment, Modification Examples 1-3, and Modification Examples 1-4.

[0167] For example, when the sending process using the general-purpose cash is executed, the profit generation unit 110 may increase the benefits given to the first user more than when the sending process using the store cash is executed. For example, if a benefit of 10% of the amount sent is given to the first user when the sending process using the store cash is executed, then when the sending process using the general-purpose cash is executed, a benefit of 15% of the amount sent may be given to the first user.

[0168] For example, when the sending process using the general-purpose cash is executed, the profit generation unit 110 may reduce the amount of general-purpose cash required to send the same amount compared to when the sending process using the store cash is executed. For example, assume that 1000 yen worth of store cash is to be sent from the first user to the second user. When using the store cash held by the first user, 1000 yen worth of store cash is required, whereas when using the general-purpose cash held by the first user, assume that 800 yen worth of general-purpose cash is sufficient.

[0169] For example, when a sending process using general-purpose cash is executed, the profit generating unit 110 may increase the amount received for sending the same amount of cash compared to when a sending process using store cash is executed. For example, when a first user sends store cash worth 1,000 yen that the first user holds to a second user, the second user may receive store cash worth 1,000 yen, whereas when the first user sends general-purpose cash worth 1,000 yen that the first user holds to the second user, the second user may receive store cash worth 1,200 yen.

[0170] According to Modification 1-7, when a sending process using general-purpose cash is executed, a benefit is generated for at least one of the first user and the second user, which would not be generated when a sending process using store cash is executed. This can provide a stronger motivation for the first user to use general-purpose cash to send store cash to the second user.

[0171] [Variation 1-8] For example, as described in the first embodiment, the payment request may be a request to use store cash at a first store. In this case, the usage benefit granting unit 103 may grant store cash to the first user when payment processing is executed and store cash is used at the first store. In other words, the usage benefit granting unit 103 may grant store cash to the first user not only when general-purpose cash is used but also when store cash is used.

[0172] According to Modification 1-8, when a payment process is executed and store cash is used at the first store, store cash is provided to the first user, which can further motivate the first user to return to the store.

[0173] [Variation 1-9] For example, the cash may also be available at the second store. The second store is a franchise of the payment service and can utilize at least general-purpose cash. In this case, when cash is used at the first store, the benefit-granting unit 103 grants the first user the first-store cash, which is the cash for the first store. The first-store cash is the same as the store cash described in the first embodiment. The process for granting the first-store cash is as described in the first embodiment.

[0174] When cash is used at the second store, the benefit-granting unit 103 grants the first user the second-store cash, which is the cash for the second store. The second-store cash is cash that cannot be used at the first store. For example, if the first store is store A of "XXX Mart" and the second store is store B of "XXX Mart", the first-store cash for store A of "XXX Mart" cannot be used at store B of "XXX Mart". The second-store cash for store B of "XXX Mart" cannot be used at store A of "XXX Mart". The second-store cash is different from the first-store cash in that the available stores are different, but the method itself for granting the second-store cash to the second user is the same as the method for granting the first-store cash to the first user.

[0175] The usage restriction unit 104 restricts the use of the first-store cash at the second store and restricts the use of the second-store cash at the first store. The second-store cash is different from the first-store cash in that it is available at the second store and not available at the first store, but the method itself for restricting the use of the second-store cash at the first store is the same as the method for restricting the use of the first-store cash at the second store.

[0176] According to Modification Example 1-9, when cash is used at the first store, the first user is given first-store cash, which is cash for the first store, and when cash is used at the second store, the first user is given second-store cash, which is cash for the second store. Thereby, it is possible to give the first user an incentive to visit the first store again and an incentive to visit the second store again. That is, for each individual store, it is possible to give the first user an incentive to visit this store again.

[0177] [Modification Example 1-10] For example, in Modification Example 1-9, the first store and the second store may belong to the same store group. When cash is used at the first store or the second store, the usage privilege granting unit 103 may give the first user store-group cash having a balance for the store group. The store-group cash is as described in the third embodiment. In the third embodiment, the case where individual-store cash is also given was described, but in Modification Example 1-10, individual-store cash may not be given.

[0178] The store-group cash can be used at the first store and the second store. If there are other stores belonging to the same store group in addition to the first store and the second store, the store-group cash can also be used at those other stores. The flow of the settlement process when using the store-group cash is as described in the third embodiment.

[0179] According to Modification Example 1-10, when cash is used at the first store or the second store, the first user is given store-group cash, which is cash for the store group, and the store-group cash can be used at the first store and the second store. Thereby, the convenience of the user is enhanced.

[0180] [Modification Example 1-11] For example, the first embodiment and the third embodiment may be combined. In this case, the store cash described in the first embodiment is one of the plurality of caches described in the third embodiment. The settlement system S includes a specifying unit 108. The processes of the specifying unit 108 and the settlement processing execution unit 102 in Modifications 1-11 are the same as those in the third embodiment.

[0181] According to Modification 1-11, when a plurality of caches that satisfy the usage conditions are specified from among the plurality of caches, the settlement process is executed based on the priority order of each of the plurality of caches. Thereby, as in the third embodiment, the convenience for the user is enhanced.

[0182] [Modification 1-12] For example, the store cash may be changeable to general-purpose cash. Conversely, the general-purpose cash may be changeable to store cash. The settlement system S includes a change processing execution unit 111 and a first fee generation unit 112. The change processing execution unit 111 executes a change process for changing the store cash to general-purpose cash, which is general-purpose cache. The change process is a process of decreasing the balance of the store cash and increasing the balance of the general-purpose cash. The change process itself can use known processes. For example, the amount of decrease in the balance of the store cash and the amount of increase in the balance of the general-purpose cash may be the same or different.

[0183] The first fee generation unit 112 generates a predetermined fee when the change process is executed. The fee may be a fixed value regardless of the amount changed by the change process, or may be a value corresponding to the amount changed by the change process. For example, the first fee generation unit 112 may generate a fee such that the higher the amount by which the store cash is changed to general-purpose cash, the higher the fee. The fee may be deducted from the general-purpose cash or the store cash, or may be deducted from other settlement means such as electronic money or points. The fee may be billed using other settlement means such as a credit card.

[0184] According to Modification Examples 1-12, when a change process for changing the general-purpose cache to the store cache is executed, a predetermined fee is generated. Thereby, the convenience of the first user who does not plan to use the store cache is enhanced. Since a predetermined fee is also generated from the payment service, the profitability of the payment service is enhanced.

[0185] [Modification Example 1-13] For example, the general-purpose cache and the store cache may be cashable. The cash withdrawal itself may be made possible by a known method. For example, the cash withdrawal may be realized by transferring a predetermined amount to the user's bank account. The settlement system S includes a first cash withdrawal processing execution unit 113, a second cash withdrawal processing execution unit 114, and a second fee generation unit 115.

[0186] The first cash withdrawal processing execution unit 113 executes a first cash withdrawal process for withdrawing the general-purpose cache which is a general-purpose cache. For example, the first cash withdrawal processing execution unit 113 executes the first cash withdrawal process so that the general-purpose cache is withdrawn by the amount specified by the user. The first cash withdrawal processing execution unit 113 reduces the balance of the general-purpose cache by the amount specified by the user and executes the first cash withdrawal process so that the amount specified by the user is withdrawn. The first cash withdrawal processing execution unit 113 may execute the first cash withdrawal process so that the balance of the general-purpose cache is reduced by the amount specified by the user and the amount obtained by subtracting the fee from the amount specified by the user is withdrawn.

[0187] The second cash withdrawal processing execution unit 114 executes a second cash withdrawal process for withdrawing the store cache. For example, the second cash withdrawal processing execution unit 114 executes the second cash withdrawal process so that the store cache is withdrawn by the amount specified by the user. The second cash withdrawal processing execution unit 114 reduces the balance of the store cache by the amount specified by the user and executes the second cash withdrawal process so that the amount specified by the user is withdrawn. The second cash withdrawal processing execution unit 114 may execute the second cash withdrawal process so that the balance of the store cache is reduced by the amount specified by the user and the amount obtained by subtracting the fee from the amount specified by the user is withdrawn.

[0188] The second fee generating unit 115 generates a higher fee when the second withdrawal process is executed than when the first withdrawal process is executed. The method of generating the fee itself may be the same as that of the first fee generating unit 112. The fee for the first withdrawal process and the fee for the second withdrawal process may be defined in advance in the data storage unit 100. The difference between the fee for the first withdrawal process and the fee for the second withdrawal process may be a fixed value regardless of the amount, or the difference may increase or decrease as the amount increases. The fee may be deducted from general-purpose cash or from store cash. The fee may also be deducted from other payment methods such as electronic money or points.

[0189] According to Modification 1-13, when the second withdrawal process is executed to withdraw store cash, a higher fee is charged than when the first withdrawal process is executed to withdraw general-purpose cash. This increases convenience for first users who do not plan to use general-purpose cash or store cash. Since a predetermined fee is charged by the payment service, the profitability of the payment service is increased.

[0190] [Variation 1-14] For example, cash may be managed using tokens in a blockchain. A token is a unit of value issued on the blockchain. The data format of the token itself may be any of various data formats adopted by known blockchains.

[0191] A token is sent from one address to another. Any metadata can be associated with a token. Any metadata can also be associated with an address. Variation 1-14 describes a case where a token representing an individual cache is associated with a user address indicating the owner of the cache and the terms of use defined for the cache. The user address is one piece of user identification information.

[0192] In Modifications 1-14, as an example of the usage conditions included in the metadata of the token, the store described in the first embodiment will be described. The usage conditions may be other conditions described in the second embodiment. For the token corresponding to the store cash, information that can identify the store, such as a store ID or a store address that can identify the first store, is associated therewith. For example, in the case of the store cash of "XXX Mart", the user address of the user who owns this store cash and the store ID or store address of "XXX Mart" are associated with the token of this store cash. In the case of general-purpose cash, the user address of the user who owns the general-purpose cash is associated with the token of the general-purpose cash.

[0193] Note that any other arbitrary information can be associated with the token. For example, the remaining balance of the cash may be associated with the token. The cash and the token do not have to correspond one-to-one, and a plurality of cashes may be managed by one token. For example, a plurality of cashes owned by a certain user may be managed by one token. In this case, a certain token indicates a general-purpose cash and a store cash. For example, the remaining balance of the general-purpose cash and the remaining balance of the store cash may be associated with this token. The total value of the remaining balances of the plurality of cashes may be associated with this token.

[0194] The usage restriction unit 104 restricts the use of the store cash at the second store based on the store ID associated with the token. In Modifications 1-14, the usage restriction unit 104 uses the filtering function of the blockchain to restrict the use of the store cash at the second store. The usage restriction unit 104 uses the filtering function to restrict the transfer of the token corresponding to the store cash of the first user to the second store. The usage restriction unit 104 restricts the transfer of the token if the store ID of the first store associated with the token does not match the store ID specified as the transfer destination.

[0195] According to Modification Examples 1-14, based on the store ID associated with the token corresponding to the store cash, the use of the store cash at the second store is restricted so that it cannot be used. As a result, it is possible to more reliably allow the use of the store cash only at the first store.

[0196] [Modification Example 1-15] In Modification Example 1-15, similar to Modification Example 1-14, the case where the cash is managed using tokens in the blockchain will be described. Transfer history information regarding the transfer history of the cash is associated with the token corresponding to the cash. The transfer history information is information corresponding to the usage history information described in the first embodiment. For example, the transfer history information includes the store ID of the store that used the payment service, the usage date and time, and the usage amount.

[0197] The payment system S includes a first detection unit 116. The first detection unit 116 detects the transfer of cash from the first user to the first store based on the transfer history information managed in the blockchain. Being managed in the blockchain means being managed in a blockchain system different from the payment service. The transfer history information may be recorded in a computer other than the server 10. For example, when the store ID of the first store is included in the transfer history information, the first detection unit 116 detects that the first user has used the cash at the first store. The first detection unit 116 may detect that the first user has used the cash at the first store a predetermined number of times based on the transfer history information.

[0198] When the transfer is detected by the first detection unit 116, the usage privilege granting unit 103 grants the first user the store cash. For example, the usage privilege granting unit 103 increases the balance of the store cash associated with the token corresponding to the first user by a predetermined amount.

[0199] Based on the transfer history information, store cash can be awarded as a reward for using the first store a certain number of times, or a discount can be offered when multiple subscriptions are applied. By referencing the date and time of use included in the transfer history information, store cash can also be awarded as a reward for using the store during idle time. If the transfer history information includes the reason for cash award, cash awarded as salary can be withdrawn without any fees.

[0200] According to Modification 1-15, a transfer of cash from a first user to a first store is detected based on transfer history information managed in the blockchain, and when the transfer is detected, store cash is granted to the first user. This makes it possible to more reliably grant store cash to the first user.

[0201] [Variation 1-16] In Variation 1-16, similar to Variation 1-14 and Variation 1-15, a case will be described in which cash is managed using tokens in a blockchain. The payment system S includes a second detection unit 117. The second detection unit 117 detects the use of cash at the first store based on usage history information relating to the usage history of cash managed outside the blockchain.

[0202] While Variation 1-15 detects the use of cash at the first store using transfer history information managed on the blockchain, Variation 1-16 uses usage history information managed outside the blockchain. The usage history information is as described in the first embodiment. When usage is detected by the second detection unit 117, the usage privilege granting unit 103 grants store cash to the first user. The processing of the usage privilege granting unit 103 differs in that the cash is managed as a token, but is otherwise similar to the first embodiment.

[0203] According to Modification 1-16, when the use of cash at the first store is detected based on the usage history information about the usage history of the cash managed outside the blockchain, the store cash is granted to the first user. This makes it possible to grant the store cash to the first user more reliably.

[0204] [4-2. Modifications of the Second Embodiment] 14 is a diagram showing an example of functional blocks of a modified example according to the second embodiment. The payment request receiving unit 101, the use benefit granting unit 103, the use restriction unit 104, the identification unit 108, the granting restriction unit 109, the first profit generating unit 110A, and the second profit generating unit 110B are realized mainly by the control unit 11.

[0205] [Variation 2-1] For example, in the second embodiment, a case has been described in which, when a first user sends a cache with defined usage conditions to a second user, the first user is given a benefit of the cache with the same defined usage conditions. The sending benefit giving unit 107 may give the first user a benefit different from the cache with defined usage conditions. This benefit may be cache with defined usage conditions different from the usage conditions defined for the cache sent from the first user to the second user, or may be cache with no defined usage conditions. Alternatively, for example, a benefit other than cash (e.g., a donation to a charity) may be given.

[0206] According to Variation 2-1, a benefit different from the cash with defined usage conditions is granted to the first user. This can motivate the first user to send the cash with defined usage conditions to the second user. For example, the first user may be able to specify the benefit that he or she is willing to receive. In this case, the first user can be more strongly motivated to send the cash with defined usage conditions to the second user.

[0207] [Variation 2-2] For example, when the usage conditions are for stores where cash can be used as in the second embodiment, the sending privilege granting unit 107 may grant a privilege unrelated to this store to the first user as a different privilege described in Modification Example 2-1. For example, the sending privilege granting unit 107 may grant store cash of another store as a privilege, or may grant general-purpose cash as a privilege. The sending privilege granting unit 107 may also grant other payment means such as electronic money or points as a privilege.

[0208] According to Modification Example 2-2, a privilege unrelated to the store is granted to the first user as a different privilege described in Modification Example 2-1. Thereby, it is possible to give the first user an incentive to send the cash with specified usage conditions to the second user.

[0209] [Modification Example 2-3] For example, the second embodiment and Modification Example 1-5 of the first embodiment may be combined. The payment system S of Modification Example 2-3 includes a granting restriction unit 109. The granting restriction unit 109 restricts the repeated granting of privileges by the sending privilege granting unit 107 by repeatedly sending cash between the first user and the second user. This restriction method is as described in Modification Example 1-5. In Modification Example 1-5, the case where the usage conditions are for a store was described, but in Modification Example 2-3, even for cash with usage conditions other than a store, it is subject to the restriction by the granting restriction unit 109. For example, the granting restriction unit 109 also restricts the repeated granting of privileges by the sending privilege granting unit 107 by repeatedly sending cash between the first user and the second user for cash with usage conditions such as time zone, day of the week, or area.

[0210] According to Modification Example 2-3, the repeated granting of privileges is restricted by repeatedly sending cash between the first user and the second user. Thereby, similar to Modification Example 1-5, it is possible to prevent the first user and the second user from obtaining privileges repeatedly.

[0211] [Modification Example 2-4] For example, the second embodiment and Modifications 1-6 of the first embodiment may be combined. The sending process execution unit 106 of Modifications 2-4 uses a general-purpose cache, which is a general cache, to execute a sending process so that a cache with defined usage conditions is sent to the second user. The sending process itself is as described in Modifications 1-6. In Modifications 1-6, the case where the usage condition is a store was described, but in Modifications 2-4, caches with usage conditions other than stores are also targets of the sending process. For example, the sending process execution unit 106 also executes a sending process to send a cache with defined usage conditions such as time zone, day of the week, or area, using the general cache.

[0212] When the sending process using the general cache is executed, the sending privilege granting unit 107 grants a privilege to the first user. Although it is different from the second embodiment in that the cache that is the basis of the sending process is a general cache, the method of granting the privilege itself is as described in the second embodiment.

[0213] According to Modifications 2-4, a sending process is executed using a general cache, which is a general-purpose cache, so that a cache with defined usage conditions is sent to the second user, and when the sending process using the general cache is executed, a privilege is granted to the first user. As a result, similar to Modifications 1-6, the convenience of the user is enhanced.

[0214] [Modification 2-5] For example, the second embodiment and Modifications 1-7 of the first embodiment may be combined. In Modifications 2-5, the benefits generated for the first user among the benefit generation units 110 of Modifications 1-7 will be described. The settlement system S of Modifications 2-5 includes a first benefit generation unit 110A. The first benefit generation unit 110A generates the benefits of the first user that do not occur when the sending process using a general-purpose cash is executed but occur when the sending process using a cash with defined usage conditions is executed. That is, the first benefit generation unit 110A has the function of generating benefits for the first user among the benefit generation units 110 described in Modifications 1-7. This function is as described in Modifications 1-7.

[0215] According to Modification 2-5, when the sending process using a general-purpose cash is executed, the benefits of the first user that do not occur when the sending process using a cash with defined usage conditions is executed are generated. Thereby, similar to Modifications 1-7, it is possible to give the first user an incentive to send the store cash to the second user.

[0216] [Modification 2-6] In Modification 2-6, the benefits generated for the second user among the benefit generation units 110 of Modifications 1-7 will be described. For example, the settlement system S of Modification 2-6 includes a second benefit generation unit 110B. The second benefit generation unit 110B generates the benefits of the second user that do not occur when the sending process using a general-purpose cash is executed but occur when the sending process using a cash with defined usage conditions is executed. That is, the second benefit generation unit 110B has the function of generating benefits for the second user among the benefit generation units 110 described in Modifications 1-7. This function is as described in Modifications 1-7.

[0217] According to Modification 2-6, when the sending process using a general-purpose cash is executed, the benefits of the second user that do not occur when the sending process using a cash with defined usage conditions is executed are generated. Thereby, similar to Modifications 1-7, it is possible to give the first user an incentive to send the store cash to the second user.

[0218] [Modification Example 2-7] For example, the sending request receiving unit 105 may repeatedly receive sending requests. Each time a sending request is received, the sending process execution unit 106 executes the sending process. Each time the sending process is executed, the sending privilege granting unit 107 may grant a privilege to the first user. The individual sending processes and the processes for granting privileges are as described in the second embodiment. For example, after the first user makes a sending request and the sending process is executed, when the first user makes a sending request again, the sending process execution unit 106 executes the sending process based on this sending request. The sending privilege granting unit 107 grants a privilege to the first user when the first sending process is executed, and also grants a privilege to the first user when the sending process is executed again.

[0219] According to Modification Example 2-7, each time a sending request is received, the sending process is executed, and each time the sending process is executed, a privilege is granted to the first user. Thereby, it is possible to more strongly motivate the first user to send the store cash to the second user.

[0220] [Modification Example 2-8] For example, the sending privilege granting unit 107 may grant a privilege to the first user based on the amount sent from the first user to the second user. For example, the sending privilege granting unit 107 grants a privilege to the first user such that the greater the amount sent from the first user to the second user, the greater the privilege. When the sending privilege granting unit 107 grants a plurality of privileges to the first user, the sending privilege granting unit 107 may grant a privilege to the first user such that the greater the amount sent from the first user to the second user, the greater the number of privileges.

[0221] According to Modification Example 2-8, a privilege is granted to the first user based on the amount sent from the first user to the second user. Thereby, it is possible to more strongly motivate the first user to send the store cash to the second user.

[0222] [Modification Example 2-9] For example, the first embodiment may be applied to the second embodiment. In Modification 2-9, the usage condition is a store where cash can be used. The settlement system S of Modification 2-9 includes a settlement request reception unit 101, a usage privilege granting unit 103, and a usage restriction unit 104. These functions are as described in the first embodiment.

[0223] According to Modification 2-9, similar to the first embodiment, it is possible to motivate the user to visit the first store again.

[0224] [Modification 2-10] For example, the second embodiment and Modification 1-1 of the first embodiment may be combined. The usage restriction unit 104 of Modification 2-10 restricts so that store cash cannot be used at the second store and so that store cash cannot be used at the first store during the second time period. This restriction method is as described in Modification 1-1. [[ID=(11)]]

[0225] According to Modification 2-10, similar to Modification 1-1, the customer attraction effect during the first time period when the first store is relatively empty is enhanced.

[0226] [Modification 2-11] For example, the second embodiment and Modification 1-2 of the first embodiment may be combined. The usage restriction unit 104 of Modification 2-11 restricts so that store cash cannot be used at the second store located in the second area. This restriction method is as described in Modification 1-2.

[0227] According to Modification 2-11, similar to Modification 1-2, it is possible to motivate the first user to visit the first area again.

[0228] [Modification 2-12] For example, the third embodiment may be applied to the second embodiment. In Modification 2-12, the first user holds a plurality of caches with different usage conditions defined for each. The payment system S of Modification 2-12 includes a specifying unit 108. The processing of the specifying unit 108 and the processing of the payment processing execution unit 102 when a plurality of caches are specified by the specifying unit 108 are as described in the third embodiment.

[0229] According to Modification 2-12, similar to the third embodiment, the convenience for the user is improved.

[0230] [4-3. Modifications according to the third embodiment] FIG. 15 is a diagram showing an example of a functional block of a modification according to the third embodiment. The usage privilege granting unit 103, the usage restriction unit 104, the sending request receiving unit 105, the sending processing execution unit 106, the sending privilege granting unit 107, the first determination unit 118, the second determination unit 119, and the designation receiving unit 120 are mainly realized by the control unit 11.

[0231] [Modification 3-1] For example, the usage conditions may include stores where the cache can be used and other conditions. The other conditions are as described in the second and third embodiments. When the specifying unit 108 specifies a first cache with a store defined as a usage condition and a second cache with other conditions defined as a usage condition, the payment processing execution unit 102 of Modification 3-1 executes payment processing based on the priority order of each of the first cache and the second cache.

[0232] For example, suppose a user has a store cache whose usage condition specifies a store, an area cache whose usage condition specifies an area, and a time period cache whose usage condition specifies a time period. If these three caches are available at a store the user visits, the payment process is executed based on the priority of these three caches. For example, if the time period cache has the highest priority, the store cache has the second highest priority, and the area cache has the lowest priority, the payment process execution unit 102 executes the payment process so that the time period cache is used preferentially.

[0233] According to Variation 3-1, when a first cache with a store specified as a condition for use and a second cache with other conditions specified as a condition for use are identified, the payment process is executed based on the respective priorities of the first cache and the second cache, thereby improving user convenience.

[0234] [Variation 3-2] For example, a priority may be set according to a user's usage history of the payment service. The payment system S of variant example 3-2 includes a first determination unit 118. The first determination unit 118 determines the priority based on usage history information relating to the usage history of the cash. For example, the first determination unit 118 determines the priority such that the higher the number of times, frequency of usage, or amount of usage of the cash, the higher the priority. The first determination unit 118 may also determine the priority such that the longer the usage period since the start of using the cash, the higher the priority.

[0235] When multiple caches are identified by the identification unit 108, the payment processing execution unit 102 executes the payment processing based on the priority of each of the multiple caches determined by the first determination unit 118. Although the method of determining the priority differs from that of the third embodiment, the payment processing itself based on the priority is as described in the third embodiment.

[0236] According to Modification 3-2, the payment process is executed based on the priority of each of the multiple cashes determined based on the usage history information related to the usage history of the cashes. This allows the priority to be set according to the user's usage history, improving user convenience.

[0237] [Variation 3-3] For example, the cache priority may be determined using machine learning. The machine learning itself may use various known methods, such as supervised learning, semi-supervised learning, or unsupervised learning. In Variation 3-3, supervised learning is used as an example. The payment system S of Variation 3-3 includes a second determination unit 119. The second determination unit 119 determines the priority of the first user based on a learning model in which the relationship between feature information regarding the features of other first users and the priority is learned, and on the feature information of the first user.

[0238] The characteristic information may be information relating to any characteristic of a user. For example, the characteristic information may include all or part of the usage history information. The characteristic information may be so-called demographic information, such as the user's name, age, gender, occupation, or annual income. In the learning model, pairs of various user characteristic information and the priority of cashes designated by the user are learned as training data. The priority included in the training data may be determined based on the usage history information, as in Variation 3-2, or may be designated by the administrator of the payment service. For example, if the training data is a pair of characteristic information of a relatively young heavy user and a priority that gives a higher priority to cashes with a specified store as a usage condition, if the characteristic information of a first user indicates that the user is young and frequently uses the service, the priority will be such that a higher priority is given to cashes with a specified store as a usage condition.

[0239] When a plurality of caches are identified by the identification unit 108, the settlement processing execution unit 102 executes settlement processing based on the priority order of each of the plurality of caches determined by the second determination unit 119. Although the method for determining the priority order is different from that of the third embodiment, the settlement processing itself based on the priority order is as described in the third embodiment.

[0240] According to Modification Example 3-3, based on the learning model in which the relationship between the feature information regarding the features of other first users and the priority order is learned, and the feature information of the first user, the settlement processing is executed based on the priority order of each of the plurality of caches determined thereby. As a result, even if the user has little usage history, a priority order that is highly convenient for this user can be estimated, thereby enhancing the convenience for the user.

[0241] [Modification Example 3-4] For example, when a plurality of caches are identified by the identification unit 108, the settlement processing execution unit 102 may execute settlement processing such that a cache with a relatively lower priority order is used when the balance of the cache with a relatively higher priority order becomes zero. When the balance of the cache with the highest priority order is equal to or greater than the usage amount included in the settlement request, the settlement processing execution unit 102 executes settlement processing so that the settlement is completed using only this cache. When the balance of the cache with the highest priority order is less than the usage amount included in the settlement request, the settlement processing execution unit 102 executes settlement processing so as to use in combination the balance of the cache with the second highest priority order. If using in combination the cache with the second highest priority order is still insufficient, the settlement processing execution unit 102 executes settlement processing so as to also use in combination caches with the third and subsequent priority orders.

[0242] According to Modification Example 3-4, settlement processing is executed such that a cache with a relatively lower priority order is used when the balance of the cache with a relatively higher priority order becomes zero. As a result, the cache with a relatively higher priority order can be utilized to the maximum extent, thereby enhancing the convenience for the user.

[0243] [Modification Example 3-5] For example, when a plurality of caches are specified by the specifying unit 108, the settlement processing execution unit 102 may execute settlement processing such that the usage amount of the cache with a relatively higher priority among the plurality of caches is greater than the usage amount of the cache with a relatively lower priority. In Modification 3-5, as in Modification 3-4, all of the balance of the cache with a relatively higher priority may be used, but a certain amount of the balance shall be left. For example, the settlement processing execution unit 102 executes settlement processing such that a plurality of caches are used in combination at a ratio corresponding to the priority. For example, assuming that three available caches are specified, the settlement processing execution unit 102 executes settlement processing such that the cache with the highest priority is used at 50%, the cache with the second highest priority is used at 30%, and the cache with the lowest priority is used at 20%.

[0244] According to Modification 3-5, settlement processing is executed such that the usage amount of the cache with a relatively higher priority is greater than the usage amount of the cache with a relatively lower priority. Thereby, since the cache with a relatively higher priority can be used more, the convenience for the user is enhanced.

[0245] [Modification 3-6] For example, the first user may specify the priority of the cache by himself / herself. The settlement system S of Modification 3-6 includes a designation reception unit 120. The designation reception unit 120 receives the designation of the priority by the first user. For example, a list of a plurality of caches held by the first user may be displayed on the user terminal 20, and the designation reception unit 120 may receive the designation of the priority of the cache from this list. The priority designated by the first user may be stored in the user database DB.

[0246] When a plurality of caches are specified by the specifying unit 108, the settlement processing execution unit 102 executes settlement processing based on the priority of each of the plurality of caches designated by the first user. Although the method of determining the priority is different from that of the third embodiment, the settlement processing based on the priority itself is as described in the third embodiment.

[0247] According to Modification Example 3-6, settlement processing is executed based on the priority of each of the plurality of caches specified by the first user. Thereby, since the first user can specify the priority order desired by himself / herself, the convenience of the first user is enhanced.

[0248] [Modification Example 3-7] For example, when the user specifies the priority of the cache by himself / herself as in Modification Example 3-6, the designation reception unit 120 may receive the designation of the priority for each store. For example, the user terminal 20 may display a list of a plurality of stores available to the first user, and the designation reception unit 120 may receive the designation of the store for which the priority is to be designated and the priority of the cache in this store from among this list. The store and the priority designated by the first user may be stored in the user database DB in an associated manner.

[0249] The settlement processing execution unit 102 executes settlement processing based on the priority associated with the store corresponding to the settlement request. This priority is the priority associated with the store indicated by the store ID included in the settlement request. Although the method for determining the priority is different from that of the third embodiment, the settlement processing itself based on the priority is as described in the third embodiment.

[0250] According to Modification Example 3-7, for each store, the designation of the priority is received, and settlement processing is executed based on the priority associated with the store corresponding to the settlement request. Thereby, since the first user can specify the priority desired for each store by himself / herself, the convenience of the first user is enhanced.

[0251] [Modification Example 3-8] For example, also in the third embodiment, as described in the first embodiment, the settlement processing execution unit 102 may be capable of executing settlement processing that combines a cache with defined usage conditions and a general-purpose cache that is a general cache. The settlement processing that combines these is as described in the first embodiment.

[0252] According to Modification Example 3-8, it is possible to execute a payment process that combines a cash with defined usage conditions and a general-purpose cash, which is a general-purpose cash. As a result, the convenience for the user is enhanced.

[0253] [Modification Example 3-9] For example, the first embodiment may be applied to the third embodiment. In Modification Example 3-9, the usage condition is a store where the cash can be used. The payment system S of Modification Example 3-9 includes a usage privilege granting unit 103 and a usage restriction unit 104. These functions are as described in the first embodiment.

[0254] According to Modification Example 3-9, similar to the first embodiment, it is possible to motivate the user to visit the first store again.

[0255] [Modification Example 3-10] For example, the third embodiment and Modification Example 1-1 of the first embodiment may be combined. The usage restriction unit 104 of Modification Example 3-10 restricts so that the store cash cannot be used at the second store and cannot be used at the first store during the second time zone. This restriction method is as described in Modification Example 1-1.

[0256] According to Modification Example 3-10, similar to Modification Example 1-1, the customer attraction effect during the first time zone when the first store is relatively empty is enhanced.

[0257] [Modification Example 3-11] For example, the third embodiment and Modification Example 1-2 of the first embodiment may be combined. The usage restriction unit 104 of Modification Example 3-11 restricts so that the store cash cannot be used at the second store located in the second area. This restriction method is as described in Modification Example 1-2.

[0258] According to Modification Example 3-11, similar to Modification Example 1-2, it is possible to motivate the first user to visit the first area again.

[0259] [Modification Example 3-12] For example, the second embodiment may be applied to the third embodiment. In Modification 3-12, the settlement system S includes a sending request receiving unit 105, a sending process execution unit 106, and a sending privilege granting unit 107. These functions are as described in the second embodiment.

[0260] According to Modification 3-12, similar to the second embodiment, it is possible to give the first user an incentive to send the store cash to the second user.

[0261] [4-4. Other Modifications] For example, the above-described modifications may be combined.

[0262] For example, the stores available for the settlement service are not limited to actual stores and may be online stores. For example, although the case where the main functions are realized by the server 10 has been described, each function may be shared by a plurality of computers. For example, the functions described as being realized by the server 10 may be realized by the user terminal 20, the store terminal 30, or other computers. The data described as being stored in the server 10 may be stored in other computers such as a database server.

Explanation of Reference Numerals

[0263] S Settlement system, N Network, 10 Server, 11, 21, 31 Control unit, 12, 22, 32 Storage unit, 13, 23, 33 Communication unit, 20 User terminal, 24, 34 Operation unit, 25, 35 Display unit, 30 Store terminal, 36 Reading device, B11, B12, B13, B14, B40 Button, C10 Code, DB User database, G1 Home screen, G2, G2A, G2B, G2C, G2D Settlement completion screen, G3 Selection screen, G4 Input screen, G5 Completion screen, 100 Data storage unit, 101 Settlement request receiving unit, 102 Settlement processing execution unit, 103 Privilege granting unit for use, 104 Usage restriction unit, 105 Request reception unit, 106 Processing execution unit, 107 Privilege granting unit, 108 Identification unit, 109 Granting restriction unit, 110 Benefit generation unit, 111 Change processing execution unit, 112 First fee generation unit, 113 First withdrawal processing execution unit, 114 Second withdrawal processing execution unit, 115 Second fee generation unit, 116 First detection unit, 117 Second detection unit, 118 First decision unit, 119 Second decision unit, 120 Designation reception unit, 200 Data storage unit, 201 Display control unit, 300 Data storage unit, 301 Settlement request transmission unit.

Claims

1. A payment request receiving means for receiving a payment request regarding a user who holds a plurality of payment means with different usage conditions, When the payment request is received, a specifying means for specifying the payment means that satisfies the usage condition from among the plurality of payment means, When a plurality of the payment means are specified by the specifying means, based on a ratio according to the priority of each of the plurality of payment means, among the plurality of payment means, the usage amount of the payment means with a relatively higher priority is higher than the usage amount of the payment means with a relatively lower priority. A payment processing execution means for calculating these usage amounts and executing a payment process so as to be, A payment system including.

2. A payment request receiving means for receiving a payment request regarding a user who holds a plurality of payment means with different usage conditions, where a time zone when available stores are relatively vacant is defined as the different usage conditions, When the payment request is received, a specifying means for specifying, as the payment means that satisfies the usage condition, the payment means among the plurality of payment means in which the current time is included in the relatively vacant time zone, When a plurality of the payment means are specified by the specifying means, a payment processing execution means for executing a payment process based on the priority of each of the plurality of payment means, A payment system including.

3. When a plurality of the payment means are specified by the specifying means, the payment processing execution means executes a payment process based on the priority of each of the plurality of payment means, which is defined such that the priority becomes higher as the number of available stores is smaller. The payment system according to Claim 1 or 2.

4. The payment system further includes a second determination means for determining the priority of the user based on a learning model in which the relationship between the feature information regarding the characteristics of other users and the priority is learned, and the feature information of the user, When a plurality of the payment means are specified by the specifying means, the payment processing execution means executes the payment process based on the priority of each of the plurality of payment means determined by the second determination means. The payment system according to any one of Claims 1 to 3.

5. The payment processing execution means is capable of executing the payment process using both the payment means for which the usage condition is defined and a general-purpose payment means that is a general-purpose payment means. The settlement system according to any one of claims 1 to 4.

6. The usage conditions are stores where the settlement means can be used, The settlement system, When the settlement process is executed, a usage privilege granting means for granting the user store settlement means, which is the settlement means for the store corresponding to the settlement request; Usage restriction means for restricting the use of the store settlement means in the second store; The settlement system according to any one of claims 1 to 5, further comprising:

7. The store settlement means can be used during a first time period when the first store is relatively empty, The usage restriction means restricts the use of the store settlement means in the second store and restricts the use of the store settlement means in the first store during a second time period. The settlement system according to claim 6.

8. The store settlement means can be used in the first store and a third store located in a first area including the first store, The usage restriction means restricts the use of the store settlement means in the second store located in a second area. The settlement system according to claim 6 or 7.

9. A computer performs: A settlement request receiving step of receiving a settlement request regarding a user who has a plurality of settlement means with different usage conditions; A specifying step of specifying the settlement means that satisfies the usage conditions from among the plurality of settlement means when the settlement request is received; When a plurality of the settlement means are specified by the specifying step, a settlement process execution step of calculating the usage amounts of these settlement means based on a ratio corresponding to the priority of each of the plurality of settlement means so that the usage amount of the settlement means with a relatively higher priority is more than the usage amount of the settlement means with a relatively lower priority, and executing a settlement process; A settlement method.

10. Settlement request receiving means for receiving a settlement request regarding a user who has a plurality of settlement means with different usage conditions, Specifying means for specifying the settlement means that satisfies the usage conditions from among the plurality of settlement means when the settlement request is received, When a plurality of the payment means are specified by the specific means, based on a ratio corresponding to the priority of each of the plurality of payment means, among the plurality of payment means, the utilization amount of the payment means with a relatively higher priority is calculated so as to be larger than the utilization amount of the payment means with a relatively lower priority, and a payment processing execution means for executing payment processing by calculating these utilization amounts; A program for causing a computer to function as such.

Images