Payment system, method and program

Abstract

To provide a technique for properly performing payment processing using a payment tool.SOLUTION: The present invention relates to a payment system (1) that lets a second person make payment by the use of a payment tool that a first person owns, and the payment system comprises an acquisition part (121) which acquires determination information to be used to determine whether to allow the payment tool to be used, a determination part (122) which determines whether to allow payment by the payment tool according to the determination information meets predetermined conditions, and a payment part (123) which makes payment according to the determination part at a request for payment using the payment tool.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to technology for a payment system using a payment tool. [Background technology]

[0002] In recent years, payments using payment tools other than cash, such as prepaid cards, credit cards, and electronic money, have become widespread, and further improvements are being made to payment technologies using payment tools. For example, Patent Document 1 discloses a prepaid card management system that can be implemented at low installation cost, can assign money or points by specifying the purpose of use, and can prevent the money or points from being used for purposes other than those intended. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-224499 Summary of the Invention [Problem to be solved by the invention]

[0004] However, Patent Document 1 only discloses that money or points can be awarded by specifying the purpose of use and that the money or points cannot be used for purposes other than those intended, but does not disclose payment technology that allows people other than the owner of the payment tool to use the payment tool. Therefore, there is room for further study on payment technology that allows people other than the owner of the payment tool to use the payment tool.

[0005] The non-limiting embodiments of the present disclosure have been made in view of the above background, and contribute to providing technology for more appropriately processing payments using payment tools. [Means for solving the problem]

[0006] A payment system according to one embodiment of the present disclosure is a payment system for allowing a second person to use a payment tool owned by a first person to make a payment, and includes an acquisition unit that acquires judgment information used to determine whether to allow use of the payment tool, a judgment unit that determines whether payment can be made using the payment tool depending on whether the judgment information satisfies specified conditions, and a payment unit that, when a request for payment using the payment tool is received, executes the payment depending on the judgment result by the judgment unit.

[0007] A method according to one aspect of the present disclosure includes an acquisition step using a payment system for allowing a second person to use a payment tool owned by a first person to make a payment, acquiring judgment information used to determine whether or not to allow use of the payment tool; a judgment step for determining whether or not payment can be made using the payment tool depending on whether or not predetermined conditions are met for the judgment information; and a payment step for executing payment depending on the judgment result by the judgment unit when a request for payment using the payment tool is received.

[0008] A computer program according to one aspect of the present disclosure is a program for causing a computer to function as the above-described payment system, and causes the computer to function as each of the above-described units.

[0009] These comprehensive or specific aspects may be realized as a system, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium. [Effects of the Invention]

[0010] According to one aspect of the present disclosure, a technology for more appropriately processing payments using a payment tool can be provided.

[0011] Further advantages and benefits of certain aspects of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some of the embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 2 is a block diagram showing an example of the functional configuration of the payment system. [Figure 2] 10 is a flowchart illustrating an example of the operation of the payment system. [Figure 3] 10 is a flowchart illustrating an example of the operation of the payment system. [Figure 4] 10 is a flowchart illustrating an example of the operation of the payment system. [Figure 5] 10 is a flowchart illustrating an example of the operation of the payment system. [Figure 6] FIG. 10 is a diagram illustrating an example of a table storing an availability flag of a payment tool. [Figure 7] FIG. 10 is a diagram illustrating an example of a table storing predetermined conditions under which payment can be made. [Figure 8] FIG. 2 is a block diagram illustrating the physical configuration of each computer that constitutes the payment system. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, an embodiment of the present disclosure will be described in detail with appropriate reference to the drawings. However, more detailed description than necessary may be omitted. For example, detailed description of already well-known matters or redundant description of substantially identical configurations may be omitted. This is to avoid unnecessary redundancy in the following description and to facilitate understanding by those skilled in the art. Note that the accompanying drawings and the following description are provided to enable those skilled in the art to fully understand the present disclosure, and are not intended to limit the subject matter described in the claims.

[0014] [Embodiment] <<Overview of Payment System 1>> First, an overview of the payment system 1 according to this embodiment will be described. The payment system 1 according to this embodiment is a payment system in which a first person makes a payment by having a second person use a payment tool owned by the first person.

[0015] As an example, the payment system 1 can be suitably introduced in a care provider that provides care services to people who need care (care recipients), such as the elderly. In this case, an example of the first person is the care recipient himself / herself, a family member, or an adult ward (including the actual caretaker and decision-maker in the care), and an example of the second person is a helper belonging to the care provider.

[0016] Furthermore, as an example of a payment tool, a prepaid card may be considered, but other than prepaid cards, payment tools using various electronic money, credit cards, smartphones, etc. may also be used, and are not particularly limited.

[0017] The payment system 1 is suitable for example for a case where a helper (second person) does shopping for a person receiving home care (first person). The payment system 1 can also be used by a family member acting as the first person, requesting a helper to do shopping for the person receiving care.

[0018] In other words, the payment system 1 can be suitably used when the person receiving care or their family entrusts their prepaid card (payment tool) to a helper and requests them to make a purchase, and the helper uses the prepaid card to make the purchase as requested.

[0019] The type of care is not limited to home care. For example, the payment system 1 may be used in cases where a person is receiving care at a facility, and a prepaid card is left at the facility, and a caregiver or other employee working at the facility uses the prepaid card as a second person to make purchases in accordance with requests from the resident (person receiving care) or their family or the contents of a contract.

[0020] Furthermore, the payment system 1 may be used in services other than nursing care providers, such as private housekeeping services or shopping services, which handle shopping on behalf of others at their request, and the application scenarios are not particularly limited.

[0021] <<Configuration of Payment System 1>> The payment system 1 according to this embodiment will be described in detail below with reference to the drawings. FIG. 1 is a block diagram showing an example of the functional configuration of the payment system 1. The payment system 1 is an information processing system made up of information processing devices. The payment system 1 may be made up of one device or multiple devices. Furthermore, when an information processing device is made up of multiple devices, the devices do not need to be installed in the same space such as the same room, but may be installed in different rooms, different buildings, different regions, etc., and are not particularly limited.

[0022] 1, payment system 1 includes server 10 and user terminals 20A, 20B, and 20C. Server 10 is an example of an information processing device in the present disclosure. Server 10 and user terminals 20A, 20B, and 20C are communicatively connected via network N1. Network N1 connecting server 10 and user terminals 20 is a wired local area network (LAN), a wireless LAN, the Internet, a public line network, a mobile data communication network, or a combination thereof.

[0023] Here, user terminal 20A is a terminal device (such as a store cash register or POS terminal) of a store that uses payment system 1. User terminal 20B is a terminal device (such as a smartphone or PC terminal) owned by a care provider that uses payment system 1 or a care helper that belongs to that provider. User terminal 20C is a terminal device (such as a smartphone or PC terminal) owned by a care recipient or their family that uses payment system 1. User terminals 20A, 20B, and 20C may be collectively referred to as user terminals 20.

[0024] (Configuration of user terminals 20A, 20B, 20C) 1, user terminals 20A, 20B, and 20C include storage units 21A, 21B, and 21C, and control units 22A, 22B, and 22C, respectively. Control units 22A, 22B, and 22C acquire various information (input information) input via an input device by a user of payment system 1. Input by a user via an input device may be simply referred to as "input by a user."

[0025] Furthermore, the control units 22A, 22B, and 22C present various pieces of information (output information) transmitted from the server 10 in response to the transmission of information input by the user to the user by displaying them on a display device. Presenting information to the user by displaying it on a display device may be simply referred to as "presenting information to the user." Furthermore, the storage units 21A, 21B, and 21C store information transmitted and received between the server 10.

[0026] (Server 10 configuration) The server 10 includes a storage unit 11 and a control unit 12. The storage unit 11 stores information to be transmitted and received between the server 10 and the user terminal 20, as well as information to be transmitted and received between the server 10 and other devices communicably connected via the network N1.

[0027] The control unit 12 includes an acquisition unit 121, a determination unit 122, a settlement unit 123, a setting unit 124, and a balance display unit 125.

[0028] Note that this is merely an example of the functional configuration of the payment system 1, and it is not necessary for all functional blocks to be included. For example, if there are functions that do not need to be provided depending on the user's needs, the configuration may include only the necessary combination of functional blocks.

[0029] Furthermore, the configuration in which all the functional blocks included in the control unit 12 are arranged in one server 10 is merely an example, and each functional block may be distributed and arranged in multiple information processing devices, and is not particularly limited. Furthermore, each functional block is not limited to a configuration in which it is realized by one integrated program, and may be a configuration in which it is realized by multiple programs, and is not particularly limited.

[0030] <<Payment Processing>> The following describes functions related to the payment process by the payment system 1 according to this embodiment.

[0031] As described above, payment system 1 is suitable as an information processing system for allowing a second person to use a payment tool owned by a first person to make a payment. Acquisition unit 121 acquires determination information used to determine whether to permit use of the payment tool. Determination unit 122 determines whether payment can be made using the payment tool depending on whether the determination information satisfies a predetermined condition. Then, when payment unit 123 receives a request for payment using the payment tool, it executes the payment depending on the determination result by determination unit 122.

[0032] (Acquisition part 121) The acquisition unit 121 acquires, for example, determination information used to determine whether or not to permit use of a prepaid card (an example of a payment tool). The determination information may be, for example, information on the date, time, or day of the week when the determination is about to be made (e.g., the date, time, or day of the week when the prepaid card is about to be used), or specific input information via the user terminal 20A or 20B, and is not particularly limited as long as it is information used to determine whether or not to permit use of a payment tool such as a prepaid card. Furthermore, the acquisition unit 121 may be configured to acquire the determination information from the user terminal 20A or 20B, or may be configured to read out the determination information temporarily stored in the storage unit 11, and is not particularly limited.

[0033] (Judgment unit 122) The determination unit 122 determines whether or not payment can be made using the payment tool depending on whether or not the determination information satisfies predetermined conditions. The determination unit 122 receives, for example, information on the date, time, and day of the week when the determination is about to be made (for example, the date, time, and day of the week when the prepaid card is about to be used) as determination information from the acquisition unit 121, and determines whether or not payment can be made depending on whether or not the date, time, day, etc. satisfy predetermined conditions.

[0034] When the determination information received from the acquisition unit 121 satisfies a predetermined condition, the determination unit 122 determines that payment can be made with the target prepaid card. For example, the determination result by the determination unit 122 may be stored in the storage unit 11 as determination result information (such as ON / OFF information of a payment tool usable flag) in association with the identification information of the target prepaid card. Alternatively, the determination unit 122 may be configured to pass the determination result to the payment unit 123, which will be described later, and is not particularly limited.

[0035] (Payment Department 123) When the payment unit 123 receives a request for payment using a payment tool, it executes the payment in accordance with the determination result by the determination unit 122. For example, when the payment unit 123 receives a request for payment using a prepaid card, it executes the payment if the determination unit 122 determines that payment using the prepaid card is possible. On the other hand, when the payment unit 123 receives a request for payment using a prepaid card, it rejects the payment request without executing the payment if the determination unit 122 determines that payment using the prepaid card is impossible.

[0036] For example, if the judgment unit 122 has previously judged whether or not payment can be made with the target prepaid card, and judgment result information (such as ON / OFF information for the payment tool's usable flag) is stored in the memory unit 11, the payment unit 123 may be configured to read out the judgment result information for the target prepaid card from the memory unit 11, and if the content of the judgment result information indicates that payment is possible, execute the payment.

[0037] Alternatively, the determination unit 122 may immediately determine whether or not payment can be made with the target prepaid card, and the payment unit 123 may receive the determination result from the determination unit 122, and if the determination result indicates that payment is possible, may execute the payment; this is not particularly limited.

[0038] <<Triggers for when payment tools become available>> Below, as an example, we will explain an example of a trigger that causes a caregiver to be able to use a payment tool (prepaid card) when the care recipient or their family member entrusts the caregiver with a request to go shopping, and the caregiver goes shopping at a store in accordance with the request.

[0039] (Use of payment tools on specific days or times) The acquisition unit 121 may acquire, as the judgment information, at least one piece of information such as the day, day of the week, or time when the judgment by the judgment unit is about to be made (for example, the day, day of the week, or time when payment is about to be made using the payment tool).

[0040] For example, a caregiver is entrusted with a prepaid card by a care recipient or their family member and asked to go shopping, and when the caregiver follows the request and goes shopping at a store, the caregiver will use the prepaid card to make payment at the store's cash register (user terminal 20A).

[0041] At that time, the information on the prepaid card is read by the user terminal 20A, and in the payment system 1, information such as the date, time, day of the week, etc. at that time (i.e., the date, time, day of the week, etc. on which the payment was to be made) is sent from the user terminal 20A to the server 10 along with the identification information of the prepaid card.

[0042] Then, in the server 10, the acquisition unit 121 acquires, for example, information on the date, time, and day of the week when payment using the prepaid card was attempted as determination information. The acquisition unit 121 may associate the information on the date, time, and day of the week acquired as determination information with the identification information of the prepaid card and store it in the storage unit 11. Alternatively, the acquisition unit 121 may pass the information on the date, time, and day of the week acquired as determination information to the determination unit 122 together with the identification information of the prepaid card.

[0043] When the judgment unit 122 receives judgment information (information on the date, time, and day of the week) from the acquisition unit 121 (or reads it from the memory unit 11), it determines whether the prepaid card to be used for payment can be used or not, depending on whether the judgment information satisfies certain conditions.

[0044] For example, a predetermined condition may be that a prepaid card can be used on a particular day of the week or during a particular time period, and the condition may be stored in memory unit 11 in association with the identification information of the prepaid card.

[0045] Alternatively, the predetermined conditions may be, for example, that the prepaid card can be used on specific dates and times, such as the date and time or day of the week when the care helper makes a service visit, and the conditions may be stored in memory unit 11 in association with the identification information of the prepaid card, but the predetermined conditions are not limited to this.

[0046] For example, the judgment unit 122 reads out the specified conditions stored in the memory unit 11 for the target prepaid card based on the identification information of the prepaid card, compares it with the date and time information received from the acquisition unit 121, and judges whether the specified conditions are met, and if the specified conditions are met, judges that the target prepaid card is eligible for payment.

[0047] Furthermore, the determination unit 122 determines that payment is not possible for the target prepaid card if the date and time information received from the acquisition unit 121 does not satisfy predetermined conditions. The determination unit 122 may store the determination result in the storage unit 11, for example, in association with the identification information of the prepaid card, or may pass it to the payment unit 123.

[0048] When the settlement unit 123 receives a settlement request using a prepaid card, it receives the determination result from the determination unit 122 (or reads it from the storage unit 11) and executes the settlement according to the determination result.

[0049] (Reading two-dimensional code) The acquisition unit 121 may acquire, as the determination information, information regarding reading of a predetermined identification code by a terminal device owned by the second person. A typical example of the identification code is, for example, a two-dimensional code, but it may also be a one-dimensional barcode or another identification code, and is not particularly limited.

[0050] For example, when a care recipient or their family requests a care helper to do some shopping, the care helper reads a predetermined identification code (two-dimensional code) managed by the care recipient or their family using the user terminal 20B owned by the care helper.

[0051] For example, in the case of a care recipient receiving home care services, a piece of paper with a predetermined two-dimensional code printed on it is kept in the care recipient's home and is under the care of the care recipient and their family. For example, the piece of paper with the predetermined two-dimensional code printed on it may be attached to a refrigerator or placed next to the care recipient's pillow.

[0052] For example, in the case of a care recipient receiving nursing care services at a facility, a predetermined two-dimensional code may be left in the management office of the nursing care facility, etc. Then, when a nursing care helper receives a shopping request from the care recipient or their family, the nursing care helper is permitted to read the predetermined two-dimensional code.

[0053] Alternatively, the predetermined two-dimensional code does not have to be printed on paper, but may be displayed on a terminal device such as a smartphone owned by the care recipient or their family, etc. Furthermore, the two-dimensional code displayed on the smartphone does not have to be the same each time, and may be a one-time code generated each time, and is not particularly limited.

[0054] When the care helper reads the predetermined two-dimensional code with the user terminal 20B, for example, a predetermined web page of the URL represented by the two-dimensional code is accessed from the user terminal 20B. At this time, in the payment system 1, for example, information indicating that the predetermined two-dimensional code has been read may be transmitted from the user terminal 20B to the server 10 together with the date and time when the predetermined two-dimensional code was read (the date and time when the predetermined web page was accessed).

[0055] Then, in the server 10, the acquisition unit 121 acquires information indicating that the predetermined two-dimensional code has been read as the determination information. The acquisition unit 121 may also acquire information on the date and time when the predetermined two-dimensional code was read (an example of information related to the reading of the predetermined identification code) as one piece of the determination information. Alternatively, if the predetermined two-dimensional code is a one-time code, the acquisition unit 121 may acquire information indicating that the two-dimensional code has been read and information on the expiration date of the two-dimensional code (an example of information related to the reading of the predetermined identification code) as one piece of the determination information.

[0056] Furthermore, the acquisition unit 121 may acquire, as one of the pieces of judgment information, information indicating that the prepaid card has become usable as a result of reading a specified two-dimensional code and information indicating the elapsed time since that state was reached (an example of information regarding the reading of a specified identification code), and is not particularly limited as long as it is information regarding the reading of a specified identification code that can be used as judgment information.

[0057] The acquisition unit 121 may then associate the information relating to the reading of the predetermined two-dimensional code acquired as the determination information with the identification information of the prepaid card and store it in the storage unit 11. Alternatively, the acquisition unit 121 may pass the information relating to the reading of the predetermined two-dimensional code acquired as the determination information to the determination unit 122 together with the identification information of the prepaid card.

[0058] When the judgment unit 122 receives the judgment information from the acquisition unit 121 (or reads it from the memory unit 11), it determines whether the prepaid card to be used for payment can be used or not depending on whether the judgment information satisfies certain conditions.

[0059] For example, the predetermined condition may be that the prepaid card can be used within a certain time period after a predetermined two-dimensional code is read or within the validity period of the two-dimensional code, but the predetermined condition is not limited to this. Furthermore, the condition may be stored in the storage unit 11 in association with the identification information of the prepaid card.

[0060] Thereafter, the determination unit 122 determines whether or not the determination information received from the acquisition unit 121 for the target prepaid card satisfies a predetermined condition, for example, based on the identification information of the prepaid card, and determines that payment is possible for the target prepaid card if the predetermined condition is satisfied, and determines that payment is not possible for the target prepaid card if the predetermined condition is not satisfied. The determination unit 122 may store the determination result in the storage unit 11, for example, in association with the identification information of the prepaid card, or may pass it to the payment unit 123.

[0061] When the settlement unit 123 receives a settlement request using a prepaid card, it receives the determination result from the determination unit 122 (or reads it from the storage unit 11) and executes the settlement according to the determination result.

[0062] (Press the button to declare the use of a prepaid card) The acquisition unit 121 may acquire, as the determination information, information relating to the declaration of use of a prepaid card (payment tool) input from the user terminal 20B (terminal device) owned by the care helper (second person).

[0063] For example, application software (hereinafter referred to as the app) linked to the prepaid card used in the payment system 1 may be installed on the user terminal 20B of the care helper, the care helper's name and other user information may be registered, and a button (declaration button) for declaring the use of the prepaid card may be provided within the app. Note that the declaration button is just one example, and a configuration may also be adopted in which, for example, text information expressing the intention to use the prepaid card is entered and the content thereof is recognized on the payment system 1 side.

[0064] When a care recipient or their family member requests a care helper to do some shopping, the care helper clicks the declaration button on the user terminal 20B owned by the care helper, and information indicating which user clicked the declaration button for the target prepaid card, along with the date and time when the declaration button for use was clicked (i.e., information indicating that the care helper is declaring the use of the prepaid card), may be sent from the user terminal 20B to the server 10.

[0065] As a result, when the declaration button is clicked, the caregiver who clicked the declaration button is identified, and when the prepaid card is subsequently used, it is known who previously declared the use of the prepaid card. In such a situation, the possibility of the prepaid card being used fraudulently is low, and fraudulent use is suppressed.

[0066] Then, in the server 10, the acquisition unit 121 acquires, as the determination information, information indicating which user clicked the report button. The acquisition unit 121 may also acquire, as one piece of the determination information, information on the date and time when the report button was clicked (or the time elapsed after the click, etc.) (an example of information related to the report of the use of the payment tool).

[0067] Then, the acquisition unit 121 may associate the information regarding the click of the report button acquired as the determination information with the identification information of the prepaid card and store it in the storage unit 11. Alternatively, the acquisition unit 121 may pass the information regarding the click of the report button acquired as the determination information to the determination unit 122 together with the identification information of the prepaid card.

[0068] When the judgment unit 122 receives the judgment information from the acquisition unit 121 (or reads it from the memory unit 11), it determines whether the prepaid card to be used for payment can be used or not depending on whether the judgment information satisfies certain conditions.

[0069] For example, the predetermined condition may be that the prepaid card can be used if a certain time has passed since the declaration button was clicked, but the predetermined condition is not limited to this. The condition may also be stored in the storage unit 11 in association with the identification information of the prepaid card. The subsequent processing by the determination unit 122 and the settlement unit 123 is similar to the configuration described above, and therefore will not be described again.

[0070] (Entering attendance information by caregivers) The acquisition unit 121 may acquire, as the determination information, information regarding the start of services by a care helper, which is input from a user terminal 20B (terminal device) owned by the care recipient or their family (first person) or the care helper (second person).

[0071] For example, an application for managing nursing care services may be installed on a user terminal owned by the care recipient, their family, or the care helper. When the care helper arrives at the home care destination, attendance information (information regarding the start of nursing care services) indicating that the care helper has arrived at work may be input via the application. Note that the input of this information may be input by the care recipient or their family, or may be input by the care helper, and is not particularly limited.

[0072] Then, when information indicating that the care helper has come to work is input, information for identifying the care recipient and the work schedule, together with the date and time when the work attendance information was input, may be transmitted from the user terminal 20B to the server 10. Furthermore, for example, the work schedule information of the care helper may be stored in the storage unit 11 in a state that can be read by the acquisition unit 121, and is not particularly limited.

[0073] Then, in the server 10, the acquisition unit 121 acquires, as the determination information, information indicating that the care helper has come to work, together with information on the prepaid card of the care recipient. The acquisition unit 121 may also acquire information on the work schedule (an example of information related to the start of care service) as one piece of the determination information.

[0074] Then, the acquisition unit 121 may associate the information regarding the start of the nursing care service acquired as the determination information with the identification information of the prepaid card and store it in the storage unit 11. Alternatively, the acquisition unit 121 may pass the information regarding the start of the nursing care service acquired as the determination information to the determination unit 122 together with the identification information of the prepaid card.

[0075] When the judgment unit 122 receives the judgment information from the acquisition unit 121 (or reads it from the memory unit 11), it determines whether the prepaid card to be used for payment can be used or not, depending on whether the judgment information satisfies certain conditions.

[0076] For example, the predetermined condition may be that the prepaid card can be used if it is within working hours after the nursing care service has started (after the nursing care helper has arrived at work), but the predetermined condition is not limited to this. The condition may also be stored in the storage unit 11 in association with the identification information of the prepaid card. The subsequent processing by the determination unit 122 and the settlement unit 123 is the same as that described above, and therefore will not be described again.

[0077] (Permission for use by the care recipient and their family) The acquisition unit 121 may acquire, as the determination information, information regarding permission to use a prepaid card (payment tool) input by the care receiver or his / her family member (first person).

[0078] For example, application software (hereinafter referred to as an app) linked to the prepaid card used in the payment system 1 may be installed on the user terminal 20C of the care receiver or his / her family member, and a button (license button) for authorizing use of the prepaid card may be provided within the app. Note that the license button is just one example, and a configuration may also be adopted in which, for example, text information expressing the intention to authorize use is entered and the content thereof is recognized on the payment system 1 side.

[0079] When a care recipient or their family member requests a care helper to do some shopping for them, the care recipient or their family member may click the permission button on their user terminal 20C, and information indicating that the permission button for use of the target prepaid card has been clicked (i.e., information indicating permission to use the prepaid card) and information on the date and time permission was granted may be sent from the user terminal 20C to the server 10.

[0080] In the server 10, the acquisition unit 121 may acquire, as the determination information, information indicating that the license button for the target prepaid card has been clicked. The acquisition unit 121 may also acquire, as one piece of the determination information, information on the date and time when the license was granted (or the time elapsed after the click, etc.) (an example of information related to the license for use of the payment tool).

[0081] The acquisition unit 121 may then associate the information regarding the click of the license button acquired as the determination information with the identification information of the prepaid card and store it in the storage unit 11. Alternatively, the acquisition unit 121 may pass the information regarding the click of the license button acquired as the determination information to the determination unit 122 together with the identification information of the prepaid card.

[0082] When the judgment unit 122 receives the judgment information from the acquisition unit 121 (or reads it from the memory unit 11), it determines whether the prepaid card to be used for payment can be used or not, depending on whether the judgment information satisfies certain conditions.

[0083] For example, the predetermined condition may be that the prepaid card can be used if a certain time has passed since the license button was clicked, but the predetermined condition is not limited to this. The condition may also be stored in the storage unit 11 in association with the identification information of the prepaid card. The subsequent processing by the determination unit 122 and the settlement unit 123 is the same as that described above, and therefore will not be described again.

[0084] <<Triggers that cause the payment tool to become unusable>> (A specified time has passed) The determination unit 122 may determine whether or not payment can be made using a payment tool, such as a prepaid card, based on the amount of time that has passed since the use of the payment tool became possible.

[0085] As described above, payment tools such as prepaid cards can be used for payments when various triggers are triggered. That is, as described above regarding the triggers that enable a prepaid card to be used, the prepaid card can be used when certain conditions are met. In payment system 1, information on the date and time when the certain conditions were met, information on the time elapsed since then, and the like may be stored in storage unit 11 in association with the identification information of the prepaid card.

[0086] The prepaid card can be used, for example, on a specific day of the week or time period, when the two-dimensional code is read, when the caregiver clicks the prepaid card use notification button, when work attendance information is entered, when the care recipient's family clicks the approval button, etc. Note that these are merely examples, and the prepaid card may be usable at other times.

[0087] The determination unit 122 may read information specifying the timing from the memory unit 11, or may be configured to receive information specifying the timing acquired by the acquisition unit 121 from the acquisition unit 121, and is not particularly limited.

[0088] Then, for example, the determination unit 122 calculates the elapsed time since the target prepaid card became usable from information on the timing at which the card became usable, and determines whether a predetermined time has passed. For example, the period during which the prepaid card remains usable after it becomes usable (i.e., validity period) may be predetermined and stored in the storage unit 11 in association with the identification information of the prepaid card. By reading the validity period information from the storage unit 11, the determination unit 122 can determine whether payment can be made with the prepaid card depending on whether the predetermined time has passed. In other words, if the determination unit 122 determines that the usable period of the prepaid card has passed, it determines that payment cannot be made with the prepaid card.

[0089] The determination unit 122 may store the determination result in the storage unit 11, for example, in association with the identification information of the prepaid card, or may pass it to the settlement unit 123. When the settlement unit 123 receives a payment request using a prepaid card, and receives from the determination unit 122 (or reads from the storage unit 11) a determination result that the payment is not possible, the settlement unit 123 will reject the payment request.

[0090] In this case, the prepaid card is no longer usable, but for example, the determination unit 122 (or the settlement unit 123) may be configured to set a flag indicating that the prepaid card is in an unusable state in association with the identification information of the prepaid card and store this in the storage unit 11. When the settlement unit 123 receives a payment request, it may refer to this unusable flag and reject the payment request.

[0091] (Exceeding the specified number of payments) The determination unit 122 may determine whether or not payment can be made using a payment tool such as a prepaid card based on the number of payments that have been made since the use of the payment tool became possible.

[0092] As described above, the payment tool becomes usable for payment due to various triggers, and the timing at which the tool becomes usable can be identified. For example, the payment unit 123 may count the number of payments made from the time the payment tool newly becomes usable for payment, associate the number of payments with the identification information of the prepaid card, and store the number in the storage unit 11. Alternatively, the payment unit 123 may associate information on the date and time at which the payment was made with the identification information of the prepaid card, and store the information in the storage unit 11.

[0093] Then, for example, the determination unit 122 reads from the storage unit 11 the number of payments that have been made with the target prepaid card since it became usable. Alternatively, the determination unit 122 may read information on the date and time when a payment was made from the storage unit 11, and count the number of payments that have been made since the payment tool became usable. The determination unit 122 then determines whether the number of payments that have been made since the payment tool became usable has exceeded a predetermined number of payments.

[0094] For example, the number of times a prepaid card can be used for payments after it has become usable (a predetermined number of payments) may be predetermined and stored in the storage unit 11 in association with the identification information of the prepaid card. The determination unit 122 reads information on the predetermined number of payments for the target prepaid card from the storage unit 11, and determines whether or not payment can be made with the prepaid card depending on whether or not the predetermined number of payments will be exceeded by the current payment. In other words, if the determination unit 122 determines that the number of times the prepaid card can be used for payments has been exceeded, it determines that payment with the prepaid card is not permitted.

[0095] The determination unit 122 may store the determination result in the storage unit 11, for example, in association with the identification information of the prepaid card, or may pass it to the settlement unit 123. When the settlement unit 123 receives a payment request using a prepaid card, and receives from the determination unit 122 (or reads from the storage unit 11) a determination result that the payment is not possible, the settlement unit 123 will reject the payment request.

[0096] In this case, the prepaid card is no longer usable, but for example, the determination unit 122 (or the settlement unit 123) may be configured to set a flag indicating that the prepaid card is in an unusable state in association with the identification information of the prepaid card and store this in the storage unit 11. When the settlement unit 123 receives a payment request, it may refer to this unusable flag and reject the payment request.

[0097] (Exceeding the specified settlement amount) The determination unit 122 may determine whether or not payment can be made using a payment tool, such as a prepaid card, based on the amount of payment made after the use of the payment tool has become possible.

[0098] As described above, a payment tool becomes usable for payment due to various triggers, and the timing at which the tool becomes usable can be identified. For example, the payment unit 123 may calculate the total amount of payments made from the time the payment tool newly becomes usable for payment, associate the total amount with the identification information of the prepaid card, and store the total amount in the storage unit 11. Alternatively, the payment unit 123 may store information on each payment amount together with the date and time at which the payment was made in the storage unit 11, associating the information with the identification information of the prepaid card.

[0099] The determination unit 122 then reads information on the total amount of payments made after the target prepaid card became usable from the storage unit 11. Alternatively, the determination unit 122 may read information on the date and time of the payments and the amount of each payment from the storage unit 11, and calculate the total amount of payments made after the prepaid card became usable. The determination unit 122 then determines whether the total amount of payments made after the prepaid card became usable exceeds a predetermined payment amount.

[0100] For example, the total amount that can be paid after a prepaid card becomes usable (predetermined payment amount) may be determined in advance and stored in the storage unit 11 in association with the identification information of the prepaid card. The determination unit 122 reads information on the predetermined payment amount for the target prepaid card from the storage unit 11, and determines whether or not payment can be made with the prepaid card depending on whether or not the current payment will exceed the predetermined payment amount. In other words, if the determination unit 122 determines that the total amount that can be used on the prepaid card has been exceeded, it determines that payment with the prepaid card is not permitted.

[0101] The determination unit 122 may store the determination result in the storage unit 11, for example, in association with the identification information of the prepaid card, or may pass it to the settlement unit 123. When the settlement unit 123 receives a payment request using a prepaid card, and receives from the determination unit 122 (or reads from the storage unit 11) a determination result that the payment is not possible, the settlement unit 123 will reject the payment request.

[0102] In this case, the prepaid card is no longer usable, but for example, the determination unit 122 (or the settlement unit 123) may be configured to set a flag indicating that the prepaid card is in an unusable state in association with the identification information of the prepaid card and store this in the storage unit 11. When the settlement unit 123 receives a payment request, it may refer to this unusable flag and reject the payment request.

[0103] (Payment at designated stores) The determination unit 122 may determine whether or not payment can be made using a payment tool, such as a prepaid card, based on information about the store where a request for payment using the payment tool is being made.

[0104] When shopping at the request of a care recipient or their family, it is expected that shopping will be done at nearby stores within a certain range from the care recipient's home or facility. Therefore, for example, a list of stores where a prepaid card can be used (a whitelist) may be stored in advance in memory unit 11 in association with the identification information of the prepaid card. Alternatively, a list of stores where the use of a prepaid card is prohibited (a blacklist) may be stored in memory unit 11 in advance in association with the identification information of the prepaid card.

[0105] When the acquisition unit 121 receives a request for payment using a prepaid card, it acquires the identification information of the store where the payment is being requested, along with the identification information of the prepaid card, from the user terminal 20A (store cash register terminal) of the store where the payment is being requested.

[0106] When the judgment unit 122 receives the identification information of the prepaid card and the identification information of the store from the acquisition unit 121, it reads out from the memory unit 11 the information of the list of stores (whitelist or blacklist) stored in association with the target prepaid card.

[0107] For example, when a whitelist is used for management, the determination unit 122 determines that a payment request from a store listed on the whitelist is possible, whereas the determination unit 122 determines that a payment request from a store not listed on the whitelist is impossible.

[0108] Furthermore, for example, when management is performed using a blacklist, the determination unit 122 determines that payment is not possible when the payment request is from a store that is on the blacklist, whereas the determination unit 122 determines that payment is possible when the payment request is from a store that is not on the blacklist.

[0109] The determination unit 122 may store the determination result in the storage unit 11, for example, in association with the identification information of the prepaid card, or may pass it to the settlement unit 123. When the settlement unit 123 receives a payment request using a prepaid card, and receives from the determination unit 122 (or reads from the storage unit 11) a determination result that the payment is not possible, the settlement unit 123 will reject the payment request.

[0110] In this case, the prepaid card's usable state is terminated, and for example, the determination unit 122 (or the settlement unit 123) may be configured to set a flag indicating that the prepaid card is in an unusable state in association with the identification information of the prepaid card and store the flag in the storage unit 11. When the settlement unit 123 receives a payment request, it may refer to the unusable flag and reject the payment request.

[0111] (Stopped by the care recipient or their family) The acquisition unit 121 may acquire, as the determination information, information regarding the suspension of use of a prepaid card (payment tool) input by the care receiver or the family member (first person).

[0112] For example, as described above, an app linked to the prepaid card used in the payment system 1 is installed on the user terminal 20C of the care recipient or their family member, and a button for stopping use of the prepaid card (stop use button) may be provided within the app. Note that the stop use button is just one example, and a configuration may also be adopted in which, for example, text information expressing the intention to stop use is entered and the content of the information is recognized on the payment system 1 side.

[0113] If the person being cared for or their family, for example, drops a prepaid card and realizes this, the person being cared for or their family can click the stop use button on their user terminal 20C, and information indicating that the stop use button has been clicked for the target prepaid card (i.e., information indicating that use of the prepaid card will be stopped) and information on the date and time of suspension of use may be sent from the user terminal 20C to the server 10.

[0114] Then, in the server 10, the acquisition unit 121 acquires information indicating that the disable button has been clicked on the target prepaid card, as well as information on the date and time of the suspension (or the time elapsed since the click, etc.) (an example of information regarding the suspension of use of the payment tool).

[0115] Then, the acquisition unit 121 may associate the information related to the click of the disable button with the identification information of the prepaid card and store it in the storage unit 11. Alternatively, the acquisition unit 121 may pass the acquired information related to the click of the disable button to the determination unit 122 together with the identification information of the prepaid card.

[0116] When the determination unit 122 receives a payment request, it determines whether the prepaid card to be used for payment can be used, depending on whether the information regarding suspension of use indicates that the use of the prepaid card will be suspended. For example, when the determination unit 122 receives a payment request, it reads information regarding suspension of use for the target prepaid card from the storage unit 11, and if the information indicates that the use of the prepaid card will be suspended, it determines that the payment is not possible.

[0117] The determination unit 122 may store the determination result in the storage unit 11, for example, in association with the identification information of the prepaid card, or may pass it to the settlement unit 123. When the settlement unit 123 receives a payment request using a prepaid card, and receives from the determination unit 122 (or reads from the storage unit 11) a determination result that the payment is not possible, the settlement unit 123 will reject the payment request.

[0118] In this case, the prepaid card is no longer usable, but for example, the determination unit 122 (or the settlement unit 123) may be configured to set a flag indicating that the prepaid card is in an unusable state in association with the identification information of the prepaid card and store this in the storage unit 11. When the settlement unit 123 receives a payment request, it may refer to this unusable flag and reject the payment request.

[0119] <<Setting up stores that use payment tools>> At the time when the judgment unit 122 judges that payment can be made with a prepaid card (an example of a payment tool), the setting unit 124 may set stores where the prepaid card can be used or stores where the prepaid card cannot be used, based on input from the care recipient or their family (a first person or the family of the first person), or a care helper (a second person).

[0120] As described above, the payment tool can be used for payment by various triggers. That is, as described above regarding the triggers that enable the payment tool to be used, the payment tool can be used when certain conditions are met, and in the payment system 1, when the certain conditions are met, the setting unit 124 sets stores where the prepaid card can be used and stores where it cannot be used, in accordance with input from the care recipient, their family, or the care helper.

[0121] For example, when a care recipient, their family, or a care helper inputs information from their respective user terminals 20B, 20C to add or delete a store from the whitelist or blacklist, the setting unit 124 updates the information on the whitelist or blacklist stored in the storage unit 11 according to the information input from the user terminals 20B, 20C. Then, when a payment request is received, the determination unit 122 reads the updated whitelist or blacklist from the storage unit 11 and determines whether or not payment can be made with the target prepaid card.

[0122] <<View Balance>> (Viewing balances from terminal devices of care providers, etc.) The balance display unit 125 may display the balance when a request to view the balance of the prepaid card is received from the user terminal of the care helper or the user terminal 20B managed by the care provider to which the care helper belongs.

[0123] For example, as mentioned above, an app that is linked to the prepaid card used in the payment system 1 is installed on the user terminal 20B of the care helper. For example, the app may have a function for viewing the balance of the prepaid card, and a request to view the balance of the prepaid card may be made to the balance display unit 125 via the app.

[0124] As an example, a request to view the balance may be made by reading a specific two-dimensional code for viewing the balance via the above-mentioned app. That is, when the two-dimensional code for viewing the balance is read in the user terminal 20B of the care helper, the balance display unit 125 may be configured to display a web page or app screen for viewing the balance on the user terminal of the care helper.

[0125] Alternatively, when the care provider logs in to a website provided by the business that manages the payment system 1 (such as a prepaid card management company) from their PC (personal computer) terminal, a specified operation screen provided by the prepaid card management company is displayed, allowing the user to view the balance of the prepaid card on that display screen.

[0126] The balance of each prepaid card may be stored in the storage unit 11 in association with the identification information of each prepaid card. When a prepaid card is charged or when a payment is made using a prepaid card, the balance stored in the storage unit 11 is updated.

[0127] <<Example of processing flow in payment system 1>> An example of the operation of the payment system 1 configured as above will be described with reference to Figures 2 to 5. Note that the flowcharts shown in Figures 2 to 5 are merely an example of the processing flow, and are not particularly limited, and for example, other steps may be included in response to a user request, the same steps may be executed repeatedly, the order of steps may be changed, or some steps may not be executed.

[0128] Fig. 2 is a flowchart illustrating an example of the operation of the payment system 1. Using Fig. 2, the flow of processing when whether or not a payment tool (such as a prepaid card) can be used is determined in advance will be described.

[0129] In step S101, the acquisition unit 121 acquires determination information in the server 10. For example, the acquisition unit 121 sequentially acquires information such as the date, day of the week, and time as the determination information. The acquisition unit 121 may also acquire information on the system time, for example.

[0130] In step S102, for example, if the determination unit 122 determines that the payment tool is available on a predetermined day, day of the week, time, etc. based on information such as the date, day of the week, and time acquired by the acquisition unit 121, the determination unit 122 may turn on the available flag for the payment tool.

[0131] In step S101, the acquisition unit 121 of the server 10 may acquire, as the determination information, for example, information that a specific two-dimensional code has been read by the care helper's user terminal 20B in relation to the payment tool in question, information that a button to declare the use of the payment tool has been pressed, information indicating that the care helper has started the service, or information indicating that the care recipient or their family has approved the use of the payment tool.

[0132] Then, in step S102, the judgment unit 122 judges, for example, whether a specific two-dimensional code has been read, whether a button to declare the use of a payment tool has been pressed, whether a care helper has started the service, whether the use of the payment tool has been approved by the care recipient or their family, etc., and if the judgment is Yes, it may turn on the usable flag of the target payment tool, assuming that the specified conditions are met.

[0133] Note that information on the payment tool availability flag (ON / OFF information) may be stored in memory unit 11, for example, in association with the identification information of the payment tool. Figure 6 is a diagram showing an example of a table that stores flags indicating whether a payment tool can be used. As shown in Figure 6, this table stores flags indicating whether a payment tool can be used, in association with the identification information of the payment tool. Note that the table shown in Figure 6 is merely an example, and the structure of the table and the information stored therein are not particularly limited. For example, information other than the flag indicating whether a payment tool can be used may also be stored.

[0134] Furthermore, the predetermined conditions for payment may be stored in storage unit 11, for example, in association with the identification information of the payment tool. FIG. 7 is a diagram showing an example of a table storing the predetermined conditions for payment. As shown in FIG. 7, this table stores conditions for determining whether or not a payment tool can be used, in association with the identification information of the payment tool. Note that the table shown in FIG. 7 is merely an example, and the structure of the table and the information stored therein are not particularly limited. Furthermore, the conditions for determining whether or not a payment tool can be used may be configured to be included in a program.

[0135] In step S103, the identification information of the payment tool is read in order to make a payment using the payment tool. For example, when a caregiver is asked to do some shopping for a care recipient or their family and pays at a store, the caregiver inserts a prepaid card into the store's cash register terminal (user terminal 20A), and the cash register terminal reads the identification information of the payment tool.

[0136] In step S104, a payment request using the payment tool is sent from the cash register terminal to the server 10 of the payment system 1.

[0137] In step S105, in the server 10, the payment unit 123 executes the payment according to the available flag (i.e., the determination result by the determination unit 122) for the payment tool to be used for the payment. For example, if the available flag is ON, the payment unit 123 accepts the payment request by that payment tool and executes the payment process. Also, for example, if the available flag is OFF, the payment unit 123 rejects the payment request by that payment tool and does not execute the payment process.

[0138] This completes the operation of the payment system 1. As mentioned above, the flowchart shown in Figure 2 merely explains one example of the operation of the payment system 1, and the operation of the payment system 1 is not limited to this.

[0139] Figure 3 is a flowchart illustrating an example of the operation of payment system 1. In the flowchart shown in Figure 3, in step S201, for example, a predetermined two-dimensional code is read by user terminal 20B (a terminal device owned by a care helper), and information related to the reading of the two-dimensional code is transmitted as determination information to server 10. The contents of the processes in the subsequent steps S202 to S206 are similar to the contents of the processes in the respective steps S101 to S105 in Figure 2 described above, and therefore will not be described repeatedly.

[0140] In step S201, in addition to reading the predetermined two-dimensional code, the pressing of a button to declare the use of a payment tool, information on the start of care services, and the like may be transmitted to the server 10 as determination information.

[0141] It should be noted that the flowchart shown in FIG. 3 merely explains one example of the operation of the payment system 1, and the operation of the payment system 1 is not limited to this.

[0142] Fig. 4 is a flowchart illustrating an example of the operation of payment system 1. In the flowchart shown in Fig. 4, in step S301, for example, information for approving use of the payment tool is input by user terminal 20C (a terminal device owned by the care receiver or his / her family), and the information regarding the approval of use of the payment tool is transmitted as determination information to server 10. The contents of the processes in each of the subsequent steps S302 to S306 are similar to the contents of the processes in each of the steps S101 to S105 in Fig. 2 described above, and therefore description thereof will not be repeated.

[0143] It should be noted that the flowchart shown in FIG. 4 merely explains one example of the operation of the payment system 1, and the operation of the payment system 1 is not limited to this.

[0144] Fig. 5 is a flowchart illustrating an example of the operation of the payment system 1. Using Fig. 5, we will explain the flow of processing when determining whether a payment tool (such as a prepaid card) can be used when a payment request is made.

[0145] In step S401, the identification information of the payment tool is read to perform payment using the payment tool. For example, when a caregiver is asked to do some shopping for a care recipient or their family and pays at a store, the caregiver inserts a prepaid card into the store's cash register terminal (user terminal 20A), and the cash register terminal reads the identification information of the payment tool.

[0146] In step S402, a payment request using the payment tool is sent from the cash register terminal to the server 10 of the payment system 1.

[0147] In step S403, the acquisition unit 121 of the server 10 acquires determination information. For example, the acquisition unit 121 acquires information such as the date, day of the week, and time when the payment request was received as the determination information. The acquisition unit 121 may also acquire information on the system time, for example.

[0148] In step S404, for example, the determination unit 122 compares the information such as the date, day of the week, time, etc. acquired by the acquisition unit 121 with the available days, days of the week, times, etc. predetermined for the payment tool, and if it determines that the available days, days of the week, times, etc. are available, it determines that payment is possible using that payment tool.

[0149] In step S403, the acquisition unit 121 of the server 10 may acquire, as the determination information, for example, information that a specific two-dimensional code has been read by the care helper's user terminal 20B in relation to the payment tool in question, information that a button to declare the use of the payment tool has been pressed, information indicating that the care helper has started the service, or information indicating that the care recipient or their family has approved the use of the payment tool.

[0150] Then, in step S404, the judgment unit 122 judges, for example, whether a specific two-dimensional code has been read, whether a button to declare the use of a payment tool has been pressed, whether the care helper has started the service, whether the use of the payment tool has been approved by the care recipient or their family, etc., and if the answer is Yes, it determines that the specified conditions have been met and that payment can be made using that payment tool.

[0151] In step S405, in the server 10, the payment unit 123 executes the payment for the payment tool to be used for the payment, depending on the determination result by the determination unit 122 in step S404. For example, if the determination result indicates that the payment is possible, the payment unit 123 accepts the payment request made by that payment tool and executes the payment process. Also, for example, if the determination result indicates that the payment is not possible, the payment unit 123 rejects the payment request made by that payment tool and does not execute the payment process.

[0152] This completes the operation of the payment system 1. As mentioned above, the flowchart shown in Figure 5 merely explains one example of the operation of the payment system 1, and the operation of the payment system 1 is not limited to this.

[0153] [Software implementation example] The control block of the server 10 may be realized by a logic circuit (hardware) formed on an integrated circuit (IC chip) or the like, or may be realized by software. In the latter case, each of the server 10 and the user terminals 20 (user terminals 20A, 20B, 20C) is configured using, for example, a computer (electronic calculator).

[0154] (Physical configuration of server 10) FIG. 8 is a block diagram illustrating the physical configuration of a computer used as the server 10 and the user terminal 20 (user terminals 20A, 20B, 20C).

[0155] 8, the server 10 can be configured by a computer including a bus 110, a processor 101, a main memory 102, an auxiliary memory 103, and a communication interface 104. The processor 101, the main memory 102, the auxiliary memory 103, and the communication interface 104 are connected to each other via the bus 110.

[0156] The processor 101 may be, for example, a CPU (Central Processing Unit), a microprocessor, a digital signal processor, a microcontroller, or a combination of these.

[0157] The main memory 102 may be, for example, a semiconductor RAM (random access memory).

[0158] For example, a flash memory, a hard disk drive (HDD), a solid state drive (SSD), or a combination of these may be used as the auxiliary memory 103. The auxiliary memory 103 stores a program for causing the processor 101 to execute the above-described operations of the server 10. The processor 101 loads the program stored in the auxiliary memory 103 onto the main memory 102 and executes each instruction included in the loaded program.

[0159] The communication interface 104 is an interface that connects to the network N1.

[0160] In this example, the processor 101 and the communication interface 104 are examples of hardware elements that realize the control unit 12. The main memory 102 and the auxiliary memory 103 are examples of hardware elements that realize the storage unit 11.

[0161] (Physical configuration of user terminal 20) 8, the user terminal 20 can be configured by a computer including a bus 210, a processor 201, a main memory 202, an auxiliary memory 203, a communication interface 204, and an input / output interface 205. The processor 201, the main memory 202, the auxiliary memory 203, the communication interface 204, and the input / output interface 205 are connected to one another via the bus 210. An input device 206 and an output device 207 are connected to the input / output interface 205.

[0162] The processor 201 may be, for example, a CPU, a microprocessor, a digital signal processor, a microcontroller, or a combination of these.

[0163] The main memory 202 may be, for example, a semiconductor RAM.

[0164] The auxiliary memory 203 may be, for example, a flash memory, an HDD, an SSD, or a combination thereof. The auxiliary memory 203 stores a program for causing the computer to operate as the user terminal 20. The processor 201 loads the program stored in the auxiliary memory 203 onto the main memory 202 and executes each instruction included in the loaded program. The auxiliary memory 203 also stores various data referenced by the processor 201 to cause the computer to operate as the user terminal 20.

[0165] The communication interface 204 is an interface for connecting to a network.

[0166] The input / output interface 205 may be, for example, a USB interface, a short-range communication interface such as infrared or Bluetooth (registered trademark), or a combination of these.

[0167] The input device 206 may be, for example, a keyboard, a mouse, a touchpad, a microphone, or a combination thereof. The output device 207 may be, for example, a display, a printer, a speaker, or a combination thereof.

[0168] In this example, the processor 201 and the communication interface 204 are examples of hardware elements that realize the control units 22A, 22B, and 22C. The main memory 202 and the auxiliary memory 203 are examples of hardware elements that realize the storage units 21A, 21B, and 21C.

[0169] Instead of storing the above-described programs in auxiliary memories 103 and 203, the programs may be recorded on an external recording medium and supplied to the corresponding computer by being read from the external recording medium. The external recording medium may be a computer-readable "non-transitory tangible medium," such as a tape, a disk, a card, a semiconductor memory, or a programmable logic circuit. The above-described programs may also be supplied to the computer via any transmission medium (such as a communications network or broadcast waves). Another aspect of the present invention may be realized in the form of a data signal embedded in a carrier wave, in which the programs are embodied by electronic transmission.

[0170] The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention.

[0171] <<Summary of this Disclosure>> The following description will focus on the operation and effect of the payment system according to one embodiment of the present disclosure. All of the configurations described below can also be used as configurations of this embodiment.

[0172] A payment system according to one aspect of the present disclosure is a payment system for allowing a second person to use a payment tool owned by a first person to make a payment, and includes an acquisition unit that acquires judgment information used to determine whether or not to allow use of the payment tool, a judgment unit that determines whether or not payment can be made using the payment tool depending on whether or not the judgment information satisfies specified conditions, and a payment unit that, when a request for payment using the payment tool is received, executes the payment depending on the judgment result by the judgment unit.

[0173] According to the above configuration, for example, in the case of services such as nursing care or housekeeping, when a service user entrusts their prepaid card or the like to the service provider to make a purchase, or in other cases where the payment tool is used by someone other than the owner of the payment tool, payment processing can be more appropriately realized.

[0174] In a payment system according to one aspect of the present disclosure, it is preferable that the acquisition unit acquires, as the judgment information, at least one of the following information: the day, the day of the week, or the time when the judgment unit is about to make the judgment.

[0175] According to the above configuration, whether or not payment is possible using the payment tool is determined using at least one of the information such as the day, day of the week, or time when the payment is about to be made, thereby enabling more appropriate payment processing.

[0176] In the payment system according to one aspect of the present disclosure, it is preferable that the acquisition unit acquires, as the determination information, information regarding reading of a predetermined identification code by a terminal device owned by the second person.

[0177] According to the above configuration, for example, whether or not payment can be made using the payment tool is determined using information related to the reading of a predetermined identification code, thereby realizing more appropriate payment processing.

[0178] In the payment system according to one aspect of the present disclosure, it is preferable that the determination information be information regarding a declaration of use of the payment tool input from a terminal device owned by the second person.

[0179] According to the above configuration, for example, whether or not payment can be made using the payment tool is determined using the declared information on the use of the payment tool by a person who has received a shopping request from the owner of the payment tool, thereby enabling more appropriate payment processing.

[0180] In a payment system according to one aspect of the present disclosure, it is preferable that the acquisition unit acquires, as the determination information, information regarding the start of service for the first person entered by the first person or the second person.

[0181] According to the above configuration, for example, whether or not payment can be made using the payment tool is determined using information indicating the start of service provision by a person who provides a service to the owner of the payment tool, thereby enabling more appropriate payment processing.

[0182] In a payment system according to one aspect of the present disclosure, it is preferable that the acquisition unit acquires, as the determination information, information regarding permission to use the payment tool entered by the first person or a family member of the first person.

[0183] According to the above configuration, for example, whether or not payment can be made using the payment tool is determined using the payment tool's license information from the owner of the payment tool, thereby realizing more appropriate payment processing.

[0184] In a payment system according to one aspect of the present disclosure, it is preferable that the determination unit determines whether payment can be made using the payment tool based on the time that has elapsed since the payment tool became available for use.

[0185] According to the above configuration, for example, whether or not payment can be made using the payment tool is determined using the time that has passed since the payment tool became available, thereby realizing more appropriate payment processing.

[0186] In a payment system according to one aspect of the present disclosure, it is preferable that the determination unit determines whether or not payment can be made using the payment tool based on the number of payments made since the payment tool became available for use.

[0187] According to the above configuration, for example, whether or not payment can be made using the payment tool is determined using the total number of payments made since the payment tool became available, thereby realizing more appropriate payment processing.

[0188] In a payment system according to one aspect of the present disclosure, it is preferable that the determination unit determines whether or not payment can be made using the payment tool based on information regarding the amount of payment made since the payment tool became available for use.

[0189] According to the above configuration, for example, whether or not payment can be made using the payment tool is determined using the total amount of payments made since the payment tool became available for use, thereby achieving more appropriate payment processing.

[0190] In a payment system according to one aspect of the present disclosure, it is preferable that the determination unit determines whether payment can be made using the payment tool based on information about the store where the payment is being requested using the payment tool.

[0191] According to the above configuration, for example, whether or not payment can be made using the payment tool is determined using the identification information of the store where the payment is requested using the payment tool, thereby realizing more appropriate payment processing.

[0192] In a payment system according to one aspect of the present disclosure, it is preferable that the determination unit determines whether payment can be made using the payment tool based on information regarding the suspension of use of the payment tool entered by the first person or a family member of the first person.

[0193] According to the above configuration, for example, whether or not payment can be made using a payment tool is determined using information on whether the owner of the payment tool has stopped using the payment tool, thereby realizing more appropriate payment processing.

[0194] It is preferable that a payment system according to one aspect of the present disclosure further includes a setting unit that sets stores at which the payment tool can be used or cannot be used in accordance with input from the first person, a family member of the first person, or the second person at the time when the determination unit determines that payment using the payment tool is possible.

[0195] According to the above configuration, for example, it is possible to add or delete stores where the payment tool can be used or stores where the payment tool cannot be used, thereby realizing more appropriate payment processing.

[0196] It is preferable that the payment system according to one aspect of the present disclosure further includes a balance display unit that displays the available balance when a request to view the available balance of the payment tool is received from a terminal device owned by the second person or a terminal device owned by the business entity to which the second person belongs.

[0197] According to the above configuration, for example, a business that provides a service at the request of the owner of the payment tool can also check the balance of the payment tool, thereby realizing more appropriate payment processing.

[0198] A method according to one aspect of the present disclosure includes an acquisition step of acquiring judgment information used to determine whether to allow a second person to use a payment tool owned by a first person to make a payment, using a payment system for allowing a second person to use the payment tool; a judgment step of determining whether or not payment can be made using the payment tool depending on whether or not predetermined conditions are met for the judgment information; and a payment step of executing payment depending on the judgment result by the judgment unit when a request for payment using the payment tool is received.

[0199] According to the above configuration, the same effects as those of the above-mentioned payment system can be achieved.

[0200] A program according to one aspect of the present disclosure is a program for causing a computer to function as the above-described payment system, and causes the computer to function as each of the above-described units.

[0201] According to the above configuration, the same effects as those of the above-mentioned payment system can be achieved. [Industrial Applicability]

[0202] One aspect of the present disclosure is useful for an information processing system that executes payment processing using a payment tool. [Explanation of symbols]

[0203] 1. Payment system 10 Servers 20A, 20B, 20C User terminal 11, 21A, 21B, 21C Storage section 12, 22A, 22B, 22C control section 101, 201 processors 102, 202 Main memory 103, 203 Auxiliary memory 104, 204 communication interface 110, 210 buses 121 Acquisition Department 122 Judgment section 123 Payment Department 124 Settings 125 Balance display section 205 Input / Output Interface 206 Input Device 207 Output Device

Claims

1. A payment system for allowing a second person to use a payment tool owned by a first person to make a payment, comprising: an acquisition unit that acquires determination information used to determine whether or not to permit use of the payment tool; a determination unit that determines whether or not payment can be made using the payment tool depending on whether or not the determination information satisfies a predetermined condition; A payment system comprising: a payment unit that, when receiving a payment request from the payment tool, executes payment in accordance with the determination result by the determination unit.

2. The payment system according to claim 1 , wherein the acquisition unit acquires, as the determination information, at least one of information regarding the day, day of the week, or time when the determination unit is about to make the determination.

3. The payment system according to claim 1 , wherein the acquisition unit acquires, as the determination information, information regarding reading of a predetermined identification code by a terminal device owned by the second person.

4. The payment system according to claim 1 , wherein the acquisition unit acquires, as the determination information, information relating to a declaration of use of the payment tool input from a terminal device owned by the second person.

5. The payment system according to claim 1 , wherein the acquisition unit acquires, as the determination information, information regarding the start of a service for the first person, which is input by the first person or the second person.

6. The payment system according to claim 1 , wherein the acquisition unit acquires, as the determination information, information regarding permission to use the payment tool entered by the first person or a family member of the first person.

7. The payment system according to claim 1 , wherein the determination unit determines whether or not payment can be made using the payment tool based on the amount of time that has elapsed since the payment tool became available.

8. The payment system according to claim 1 , wherein the determination unit determines whether or not payment can be made using the payment tool based on the number of payments made since the payment tool became available.

9. The payment system according to claim 1 , wherein the determination unit determines whether or not payment can be made using the payment tool based on information regarding the amount of payment made after the payment tool became available for use.

10. The payment system according to claim 1 , wherein the determination unit determines whether or not payment can be made using the payment tool based on information about a store where a payment request using the payment tool is being made.

11. The payment system according to claim 1 , wherein the determination unit determines whether payment can be made using the payment tool based on information regarding the suspension of use of the payment tool entered by the first person or a family member of the first person.

12. The payment system of claim 1, further comprising a setting unit that sets stores at which the payment tool can be used or cannot be used in accordance with input from the first person, a family member of the first person, or the second person at the time when the determination unit determines that payment using the payment tool is possible.

13. The payment system of claim 1 further comprises a balance display unit that displays the balance when a request to view the balance of the payment tool is received from a terminal device owned by the second person or a terminal device owned by a business entity to which the second person belongs.

14. A payment system for allowing a second person to use a payment tool owned by a first person to make a payment, an acquisition step of acquiring determination information used to determine whether or not to permit use of the payment tool; a determination step of determining whether or not payment can be made using the payment tool depending on whether or not the determination information satisfies a predetermined condition; a settlement step of executing the settlement in accordance with the determination result by the determination unit when a request for settlement is received by the settlement tool.

15. A program for causing a computer to function as the settlement system according to claim 1, the program causing the computer to function as each of said units.

Images