Management systems, management methods, and programs

Abstract

Users can easily manage the value they possess. [Solution] The management system includes a storage unit that stores a first value held by a user in association with a value identifier, a value issuing unit that issues a second value with a set usage range in response to a request from a user terminal used by the user and associates the issued second value with a value identifier, and a registration unit that uses the value identifier to register the issued second value on the user terminal so that it can be used within the set usage range.

Description

Technical Field

[0001] The present invention relates to a management system, a management method, and a program.

Background Art

[0002] There is a system that allows a user to make payments at multiple stores using values such as electronic money from a mobile terminal owned by the user. For example, Patent Document 1 describes a regional wallet service having a payment function using a regional value available in a specific region.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in addition to conventional values such as electronic money and digital gift certificates, services are diversifying, such as providing values specialized for use in a specific region, or values that differ depending on the user's usage pattern, the type of store where the value is used, etc., making it cumbersome for users to manage their values.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to provide a management system, a management method, and a program that enable a user to easily manage the values they possess.

Means for Solving the Problems

[0006] To solve the above-mentioned problems, one aspect of the present invention includes: a storage unit that stores a first value held by a user in association with a value identifier; a value issuing unit that issues a second value with a set usage range in response to a request from a user terminal used by the user, and associates the issued second value with the value identifier; and a registration unit that registers the issued second value with the user terminal so that it can be used within the set usage range, so that settlement processing can be performed using the value identifier of the first value. The storage unit further stores attribute information that identifies whether or not the user is a resident of a specific region, and the value issuing unit issues the second value, which has a shorter usage period than the first value, if the user is not a resident of the specific region. It is a management system.

[0007] Furthermore, one aspect of the present invention is a management method performed by a computer used in a management system, comprising: storing a first value held by a user in association with a value identifier; issuing a second value with a set usage range in response to a request from a user terminal used by the user; associating the issued second value with the value identifier; and registering the issued second value on the user terminal so that it can be used within the set usage range so that settlement processing can be performed using the value identifier of the first value. A management method that includes the following: associating the value identifier with the value identifier includes storing attribute information that identifies whether or not the user is a resident of a specific region; associating the issued second value with the value identifier includes issuing the second value with a shorter usage period than the first value if the user is not a resident of the specific region. This is a management method.

[0008] Furthermore, in one aspect of the present invention, a computer used in a management system stores a first value owned by a user, associating it with a value identifier. death, In response to a request from the user terminal used by the aforementioned user, a second value with a defined usage range is issued, and the issued second value is associated with the value identifier. hair, The issued second value is registered in the user terminal so that payment processing can be performed using the value identifier of the first value, and so that it can be used within the set usage range. The program causes the user to perform the following actions: associating the value identifier with the value identifier includes storing attribute information that identifies whether or not the user is a resident of a specific region; associating the issued second value with the value identifier includes issuing the second value, which has a shorter usage period than the first value, if the user is not a resident of the specific region. It is a program. [Effects of the Invention]

[0009] As explained above, users can easily manage the value they possess. [Brief explanation of the drawing]

[0010] [Figure 1] This is a schematic block diagram showing an example configuration of the management system according to this embodiment. [Figure 2] This is a schematic block diagram showing an example of the configuration of the management server according to this embodiment. [Figure 3] This is a schematic diagram showing the data structure and data example of the value management table according to this embodiment. [Figure 4] This is a schematic diagram showing the data structure and data example of the user information table according to this embodiment. [Figure 5] This is a schematic diagram showing the data structure and data example of the merchant information table according to this embodiment. [Figure 6] This is a schematic block diagram showing an example of the configuration of a user terminal according to this embodiment. [Figure 7] This is a schematic block diagram showing an example of the configuration of a service provider terminal according to this embodiment. [Figure 8] This is a schematic block diagram showing an example of the configuration of the issuer terminal according to this embodiment. [Figure 9] This is a sequence diagram showing the flow of the local currency application process performed by the management system according to this embodiment. [Figure 10] This is a sequence diagram showing the flow of the charge processing performed by the management system according to this embodiment. [Figure 11] This is a sequence diagram showing the flow of the purchase point awarding process performed by the management system according to this embodiment. [Figure 12] This is a sequence diagram showing the flow of the gift certificate application process performed by the management system according to this embodiment. [Figure 13] This is a sequence diagram showing the flow of the short-term gift certificate application process performed by the management system according to this embodiment. [Figure 14] This diagram illustrates the process of linking short-term gift certificates according to this embodiment. [Figure 15] This is a sequence diagram showing the flow of value settlement processing performed by the management system according to this embodiment. [Figure 16]This is an image diagram showing an example of a payment screen displayed on a user terminal according to this embodiment.

Embodiment for Implementing the Invention

[0011] Hereinafter, a management system, a management method, and a program according to an embodiment of the present invention will be described with reference to the drawings.

[0012] <Configuration of Management System 1> FIG. 1 is a schematic block diagram showing a configuration example of a management system 1 according to this embodiment. The management system 1 is an information processing system that centrally manages values such as electronic money (digital currency), digital gift certificates, points, etc. A value is something that can be used to receive goods or services and decreases according to usage. For example, a value can be the amount of electronic money, points, the numerical value of a digital gift certificate, etc. Also, a value can be discount coupons, vouchers, coupon tickets, exchange tickets, etc., such as "Electronic coupon worth 500 yen", "5 pieces of electronic exchange tickets for 1 watermelon, a specialty of ○○ area", "Auxiliary ticket worth 5,000 yen for taxis within ○○ area (apply to the ward office with the receipt to get a subsidy later)", "3-day lift ticket for ○○ area ski resort for 1 day". In this embodiment, as an example of electronic money, regional currency issued by a local government (also referred to as "local government" or "local public entity") and available for use in the area covered by the local government will be described. Also, as an example of a digital gift certificate, a regional gift certificate (electronic premium gift certificate) issued by a local government to its residents, etc. for the purpose of regional revitalization will be described. Residents belonging to a local government are residents belonging to the area covered by the local government. For example, they are residents living in the area covered by the local government.

[0013] The management system 1 includes a management server 10, a user terminal 20, a service provider terminal 30, and an issuer terminal 40. The management server 10 communicates with the user terminal 20, the service provider terminal 30, and the issuer terminal 40 via a network NW using wired or wireless connections, enabling them to send and receive various types of data to and from each other.

[0014] The network (NW) may be any or a combination of the following: the Internet, a Public Land Mobile Network (PLMN), a Local Area Network (LAN), or a Virtual Personal Network (VPN).

[0015] The number of user terminals 20 and service provider terminals 30 can generally be multiple. In the example in Figure 1, the number of service provider terminals 30 is N. Multiple user terminals 20 and multiple service provider terminals 30 are distinguished using sub-numbers such as "-1". In this embodiment, when there are commonalities among multiple user terminals 20 and multiple service provider terminals 30, or when it is not necessary to distinguish between multiple user terminals 20 and multiple service provider terminals 30, they are simply referred to as user terminals 20 and service provider terminals 30.

[0016] <Management Server 10> The management server 10 is an information processing device that centrally controls the management system 1. The management server 10 is composed of, for example, one or more PCs (personal computers), server devices (for example, cloud servers), databases (for example, cloud storage), etc.

[0017] Figure 2 is a schematic block diagram showing an example of the configuration of the management server 10 according to this embodiment. The management server 10 comprises a control unit 110, a storage unit 120, an input unit 130, a communication unit 140, and a display unit 150. The control unit 110 has the function of controlling the overall operation of the management server 10. The control unit 110 is implemented, for example, by causing the CPU (Central Processing Unit) provided as hardware in the management server 10 to execute a program. The control unit 110 comprises a value issuance unit 111, a value management unit 112, a settlement processing unit 113, a registration unit 114, and a display control unit 115.

[0018] The value issuing unit 111 issues value for each user and stores information about the issued value in the value management table 121. The Value Management Unit 112 manages the value of each user. The settlement processing unit 113 executes a settlement process to settle the transaction by value based on the transaction information received from the service provider terminal 30 or the user terminal 20. The registration unit 114 registers the value to the user application, which will be described later. The display control unit 115 controls the display on the user terminal 20 or the service provider terminal 30.

[0019] The input unit 130 has the function of receiving input from the user. The functions of the input unit 430 are realized, for example, by a mouse, keyboard, buttons, touch panel, microphone, etc., provided by the management server 10.

[0020] The communication unit 140 has the function of sending and receiving various types of information. The communication unit 140 communicates with external devices via wired or wireless connection.

[0021] The display unit 150 has the function of displaying various information. The display unit 450 is composed of display devices such as a display device or touchscreen (touch panel) that are provided as hardware by the management server 10.

[0022] The storage unit 120 has the function of storing various types of information. The storage unit 120 is composed of storage media provided as hardware by the management server 10, such as HDD (Hard Disk Drive), SSD (Solid State Drive), flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), RAM (Random Access read / write Memory), ROM (Read Only Memory), or any combination of these storage media. The storage unit 120 may also be cloud storage. For example, the storage unit 120 stores the value management table 121, the user information table 122, and the merchant information table 123.

[0023] (Value Management Table) Figure 3 is a schematic diagram showing the data structure and data example of the value management table 121 according to this embodiment. The Value Management Table 121 is a database that manages multiple values ​​held by each user, each with a different set of usage scopes. The Value Management Table 121 has the following data items: User ID, Card ID, Balance, Value Type, Category, and Usage Scope. The User ID is identification information that identifies each user. The Card ID is a value identifier (e.g., card number) that identifies each value. The Balance is the balance of the value. The Value Type is the value's value type (e.g., electronic money or gift certificate). The Category is the value's category. For each Value Type (major category), there are one or more Categories (minor categories).

[0024] The scope of use refers to the range within which the value can be used. In other words, each value is only available within its defined scope of use. The scope of use includes, for example, the types of merchants where it can be used, the regions where it can be used, the period during which it can be used (validity period), and the goods or services that can be used. In the illustrated example, items marked with "-" indicate that there are no restrictions on the scope of use. For example, in the illustrated example, the values ​​(limited-time points, limited-time money) for card IDs "1-9999" and "2-9999" are set to be usable in the region "Region A" and have an expiration period of "2025 / 1 / 1 to 2025 / 3 / 31". Limited-time points are points with an expiration date. Limited-time money is electronic money with an expiration date. In the illustrated example, the value (special gift certificate) for card ID "1-9998" is limited to "individual stores" as the usable merchant type and "Region A" as the usable region. The value (short-term gift certificate) for card ID "2-9998" is limited to "Region A" as the usable region and "January 1, 2025 to January 31, 2025" as the usable period. Special gift certificates are gift certificates that can only be used at "individual stores" as the merchant type. Short-term gift certificates have a shorter validity period than general gift certificates and special gift certificates.

[0025] Multiple values ​​have pre-established parent-child relationships for each card type, and each value is assigned a card ID to identify these relationships. For example, the value with the widest range of use is designated as the parent card, and values ​​with a narrower range of use than the parent card are designated as child cards. In terms of parent-child relationships, for example, in the case of digital gift certificates, a common gift certificate usable at all participating stores is called the parent card, and a special gift certificate usable at only some of the participating stores (e.g., individual stores) is called the child card. For example, the card ID of a child card (hereinafter sometimes referred to as the "child card ID") includes the card ID of the parent card (hereinafter sometimes referred to as the "parent card ID"). In the illustrated example, the card IDs "1-9998" and "2-9998" of the common gift certificate child cards (special gift certificates, short-term gift certificates) have numbers such as "1-" and "2-" added before the card ID "9998" of the parent card (common gift certificate). Furthermore, in terms of parent-child relationships, for example, in the case of local currency (electronic money), the electronic money (regular electronic money) that can be repeatedly charged and used within that region (e.g., "Region A") is designated as the parent card, while limited-time points, limited-time money, etc., are designated as child cards. Similar to digital gift certificates, the card ID of the child card of local currency includes the card ID of the parent card.

[0026] The parent card ID corresponds to a single value identifier that manages the parent card and its child cards (multiple values) in common. When a user uses a value, the parent card ID is used. In the following explanation, "value corresponding to the parent card ID" includes the parent card and its child cards.

[0027] (User information table) Figure 4 is a schematic diagram showing the data structure and data example of the user information table 122 according to this embodiment. User Information Table 122 is a database that stores user information about each user who uses Value. User Information Table 122 has data items for User ID, User Attributes, Personal Information, and Payment Information. User Attributes are the user's attributes (for example, whether they are a resident of the area governed by the local government (issuer) or a short-term user (for example, a tourist, etc.)). Personal Information is the user's personal information (for example, address, telephone number, date of birth, gender, etc.). Payment Information is Value's payment information (for example, credit card or bank account information).

[0028] (Franchise Information Table) Figure 5 is a schematic diagram showing the data structure and data example of the merchant information table 123 according to this embodiment. The merchant information table 123 is a database that stores merchant information for each merchant. A merchant is a store or other establishment where Value can be used. The merchant information table 123 has the following data items: merchant ID, merchant type, and account information. The merchant ID is identification information that identifies each merchant. The merchant type is the type of merchant (e.g., large store, small store, local store, etc.). The account information is information about the account used for settling transactions settled with Value.

[0029] <User terminal> The user terminal 20 is an information terminal operated by the user who will be using the value. For example, the user receives the value issued by the issuer and uses the value in accordance with the rules set by the issuer. The user terminal 20 can be, for example, a smartphone or a tablet device. The user terminal 20 has an application program for using the value (hereinafter sometimes referred to as the "user app") pre-installed. The user can set in the user app which of the multiple values ​​associated with the card ID will be used preferentially (for example, in the case of local currency, preferential use of limited-time points or limited-time money). In this embodiment, the user terminal 20 is used as an example of a user-owned medium, but the user-owned medium may be a prepaid card or the like that stores a card ID (parent card ID). The prepaid card may have a barcode (such as a two-dimensional barcode like a QR code (registered trademark) or a one-dimensional barcode) representing the card ID printed on it.

[0030] Figure 6 is a schematic block diagram showing an example of the configuration of the user terminal 20 according to this embodiment. The user terminal 20 comprises a control unit 210, a storage unit 220, an input unit 230, a communication unit 240, a display unit 250, and a reading unit 260. The control unit 210 comprises a user registration unit 211, a value processing unit 212, and a display control unit 213. The user registration unit 211 registers the use of value by the user (user registration) to the management server 10. The value processing unit 212 performs various value-related processes, such as charging electronic money and making payments using value. The display control unit 213 controls the display on the display unit 250.

[0031] The storage unit 220 has the function of storing various types of information. The storage unit 220 is composed of storage media provided as hardware by the user terminal 20, such as an HDD (Hard Disk Drive), SSD (Solid State Drive), flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), RAM (Random Access read / write Memory), ROM (Read Only Memory), or any combination of these storage media. For example, the storage unit 220 stores the user ID and the card ID (parent card ID) of the value held by the user.

[0032] The input unit 230 has the function of receiving input from the user. The functions of the input unit 230 are realized, for example, by a mouse, keyboard, buttons, touch panel, microphone, etc., provided on the user terminal 20.

[0033] The communication unit 240 has the function of sending and receiving various types of information. The communication unit 240 communicates with external devices via wired or wireless connection.

[0034] The display unit 250 has the function of displaying various information. The display unit 250 is composed of a display device such as a display device or touchscreen (touch panel) that is provided as hardware in the user terminal 20.

[0035] The reading unit 260 has the function of reading barcodes (such as two-dimensional codes like QR codes (registered trademarks) and one-dimensional barcodes). The reading unit 260 is composed of a camera, a barcode scanner, and other hardware components provided by the user terminal 20.

[0036] <Service provider terminal 30> The service provider terminal 30 is an information terminal installed at the merchant. The service provider terminal 30 can be, for example, a smartphone, tablet, PC (Personal Computer), or POS (Point of Sale) terminal. The service provider terminal 30 comes pre-installed with an application program (sometimes referred to as the "merchant app") for settling transactions using value.

[0037] Figure 7 is a schematic block diagram showing an example configuration of the service provider terminal 30 according to this embodiment. The service provider terminal 30 includes a control unit 310, a storage unit 320, an input unit 330, a communication unit 340, a display unit 350, and a reading unit 360. The control unit 310 comprises a merchant registration unit 311, a value processing unit 312, and a display control unit 313.

[0038] The merchant registration unit 311 registers merchant information with the management server 10. The value processing unit 312 executes processing related to settlement using the value. The display control unit 313 controls the display on the display unit 350.

[0039] The storage unit 320 has the function of storing various types of information. The storage unit 320 is composed of storage media provided as hardware by the service provider terminal 30, such as an HDD (Hard Disk Drive), SSD (Solid State Drive), flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), RAM (Random Access read / write Memory), ROM (Read Only Memory), or any combination of these storage media. The storage unit 320 stores, for example, the merchant ID.

[0040] The input unit 330 has the function of receiving input from the user. The function of the input unit 330 is realized, for example, by a mouse, keyboard, buttons, touch panel, microphone, etc., provided on the service provider terminal 30.

[0041] The communication unit 340 has the function of sending and receiving various types of information. The communication unit 340 communicates with external devices via wired or wireless connection.

[0042] The display unit 350 has the function of displaying various information. The display unit 350 is composed of a display device such as a display device or touchscreen (touch panel) that is provided as hardware in the service provider terminal 30.

[0043] The reading unit 360 has the function of reading barcodes (such as two-dimensional codes like QR codes (registered trademarks) and one-dimensional barcodes). The reading unit 360 is composed of a camera, a barcode scanner, and other hardware components provided by the service provider terminal 30.

[0044] <Issuer terminal 40> The issuer terminal 40 is an information terminal operated by the issuer (user business) that issues and distributes value to users. For example, if the value is local currency or local gift certificates (digital gift certificates), the issuer is a local government or similar entity. The issuer terminal 40 can be, for example, a smartphone, tablet, or PC (personal computer).

[0045] Figure 8 is a schematic block diagram showing an example of the configuration of the issuer terminal 40 according to this embodiment. The issuer terminal 40 comprises a control unit 410, a storage unit 420, an input unit 430, a communication unit 440, and a display unit 450. The control unit 410 has the function of controlling the overall operation of the issuer terminal 40. The control unit 410 is realized, for example, by causing the CPU (Central Processing Unit) provided as hardware in the issuer terminal 40 to execute a program. The control unit 410 includes a value registration unit 411 and a cooperation unit 412. The value registration unit 411 issues value (for example, local currency or digital gift certificates) and registers it with the management server 10. The linkage unit 412 performs processing in cooperation with the management server 10. For example, the linkage unit 412 sends and receives user information about users to and from the management server 10 via the communication unit 440. The linkage unit 412 also sends and receives merchant information about merchants to and from the management server 10 via the communication unit 440. Furthermore, the linkage unit 412 sends and receives transaction logs for each user and each merchant to and from the management server 10 via the communication unit 440.

[0046] The storage unit 420 has the function of storing various types of information. The storage unit 420 is composed of storage media provided as hardware by the issuer terminal 40, such as an HDD (Hard Disk Drive), SSD (Solid State Drive), flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), RAM (Random Access read / write Memory), ROM (Read Only Memory), or any combination of these storage media. The storage unit 420 stores, for example, user information about the user. For example, if the issuer is a local government, the storage unit 420 stores information about the residents.

[0047] The input unit 430 has the function of receiving input from the user. The function of the input unit 430 is realized, for example, by a mouse, keyboard, buttons, touch panel, microphone, etc., provided on the issuer terminal 40.

[0048] The communication unit 440 has the function of sending and receiving various types of information. The communication unit 440 communicates with external devices via wired or wireless connection.

[0049] The display unit 450 has the function of displaying various information. The display unit 450 is composed of display devices such as a display device or touchscreen (touch panel) that are provided as hardware in the issuer terminal 40.

[0050] Next, the operation of the management system 1 according to this embodiment will be described with reference to Figures 9 to 16.

[0051] <Local currency application processing> First, we will explain the local currency application process, which is the process by which users apply to use local currency (electronic money). Figure 9 is a sequence diagram showing the flow of the local currency application process performed by the management system 1 according to this embodiment.

[0052] First, the user registration unit 211 of the user terminal 20 receives application information necessary for applying for local currency (for example, the user's personal information, payment information, etc.) from the user (step S101). Next, the user registration unit 211 transmits the entered application information to the management server 10 via the communication unit 240 (step S102). The management server 10 receives the application information from the user terminal 20.

[0053] The value issuance unit 111 of the management server 10 issues a user ID and a card ID based on the received application information (step S103). The card ID issued here may consist only of the parent card ID, or it may also include child card IDs. Next, the value issuance unit 111 performs a linking process between the user ID, card ID, and the regional currency information (denomination, etc.) used by the user, and stores this information by writing it to the value management table 121 and the user information table 122 (step S104). Next, the value issuing unit 111 transmits ID information, including the user ID and card ID, to the user terminal 20 via the communication unit 140 (step S105). The ID information may be a two-dimensional barcode representing the user ID or card ID (parent card ID). The user terminal 20 receives the ID information from the management server 10 and stores the received ID information by writing it to the storage unit 120. After that, the regional currency application process is terminated.

[0054] <Charging process> Next, I will explain the process of charging local currency. Figure 10 is a sequence diagram showing the flow of the charge process performed by the management system 1 according to this embodiment.

[0055] First, we will explain the first charging process S200, which is performed directly on the user terminal 20. The value processing unit 212 of the user terminal 20 receives input of charge information (for example, charge amount, etc.) from the user (step S201). Next, the value processing unit 212 adds ID information (user ID and parent card ID) to the input charge information via the communication unit 240 and sends it to the management server 10 (step S202). The management server 10 receives the charge information from the user terminal 20.

[0056] The value management unit 112 of the management server 10 executes the charge process based on the received charge information (step S203). For example, the value management unit 112 adds the charge amount to the balance corresponding to the ID information in the value management table 121. The value management unit 112 also executes the settlement process for the charge amount based on the payment information corresponding to the user ID. Subsequently, the value management unit 112 sends the charge result, which is the processing result of the charge process, to the user terminal 20 (step S204). For example, the charge result includes the balance after the charge. The user terminal 20 receives the charge result from the management server 10 and displays the received charge result. After that, the first charge process is terminated.

[0057] Next, we will explain the second charging process S210 performed at the service provider terminal 30. First, the value processing unit 212 of the user terminal 20 displays a two-dimensional barcode representing ID information (for example, parent card ID) on the display unit 250 (step S211). The reader unit 360 of the service provider terminal 30 reads the ID information from the two-dimensional barcode displayed on the user terminal 20 (step S212). Next, the value processing unit 312 of the service provider terminal 30 receives input of the charge amount from the user or store clerk, etc. (step S213). Next, the value processing unit 312 transmits the charge information to the management server 10 via the communication unit 340 (step S214). The charge information includes the read ID information and the entered church amount. The management server 10 receives the charge information from the service provider terminal 30.

[0058] The value management unit 112 of the management server 10 executes the charge process based on the received charge information (step S215). Subsequently, the value management unit 112 transmits the charge result, which is the processing result of the charge process, to the service provider terminal 30 via the communication unit 140 (step S216). The service provider terminal 30 receives the charge result from the management server 10. The display control unit 313 of the service provider terminal 30 displays the received charge result (step S217). After that, the second charge process is terminated.

[0059] <Purchase Point Granting Process> Next, we will explain the process of awarding purchase points for the purchase of goods or services. Figure 11 is a sequence diagram showing the flow of the purchase point granting process performed by the management system 1 according to this embodiment. First, the value processing unit 212 of the user terminal 20 displays a two-dimensional barcode representing ID information (for example, parent card ID) on the display unit 250 (step S301). The reader unit 360 of the service provider terminal 30 reads the ID information from the two-dimensional barcode displayed on the user terminal 20 (step S302). Next, the value processing unit 312 of the service provider terminal 30 receives input from store employees, etc., regarding the purchase amount and point information (for example, the number of points awarded, etc.) (step S303). Next, the value processing unit 312 transmits transaction information to the management server 10 via the communication unit 340 (step S304). The transaction information includes the read ID information, the entered purchase amount, and point information. The management server 10 receives the transaction information from the service provider terminal 30.

[0060] The value management unit 112 of the management server 10 performs point processing based on the received transaction information (step S305). For example, based on the received transaction information, the value management unit 112 updates (adds or subtracts) the purchase points corresponding to the card ID in the value management table 121. Subsequently, the value management unit 112 transmits the point processing result, which is the result of point processing, to the service provider terminal 30 via the communication unit 140 (step S306). The service provider terminal 30 receives the point processing result from the management server 10.

[0061] The value processing unit 312 of the service provider terminal 30 executes the settlement process for the transaction (step S307). Next, the value processing unit 312 transmits the payment information, which is the processing result of the payment processing, to the management server 10 via the communication unit 340 (step S308). The management server 10 receives the payment information from the service provider terminal 30.

[0062] The value management unit 112 of the management server 10 performs history processing to update the transaction history (step S309). Next, the value management unit 112 transmits point information to the user terminal 20 via the communication unit 140 (step S310). The point information includes the points awarded this time and the total points, etc. The user terminal 20 receives the point information from the management server 10. The display control unit 213 of the user terminal 20 displays the point results (for example, the points awarded this time and the total points) on the display unit 250 based on the received point information (step S311). After that, the purchase point awarding process is terminated.

[0063] <Gift certificate application processing> Next, we will explain the process of applying for a common gift certificate (parent card) as a user. Figure 12 is a sequence diagram showing the flow of the gift certificate application process performed by the management system 1 according to this embodiment.

[0064] First, the user registration unit 211 of the user terminal 20 receives input from the user regarding the application for the gift certificate in the user application (step S401). Next, the user registration unit 211 transmits the gift certificate application information, including ID information (e.g., user ID), to the management server 10 via the communication unit 240 (step S402). The management server 10 receives the gift certificate application information from the user terminal 20.

[0065] The value issuing unit 111 of the management server 10 refers to the user information in the user information table 122 based on the received ID information (step S403). Next, the value issuing unit 111 issues a digital gift certificate based on the referenced user information (step S404). For example, the value issuing unit 111 issues a parent card ID for the digital gift certificate. Next, the value issuance unit 111 performs a process to link the received ID information with the parent card ID of the issued digital gift certificate (step S405). For example, the value issuance unit 111 writes the parent card ID and amount of the issued digital gift certificate to the value management table 121, associating them with the user ID. Next, the registration unit 114 of the management server 10 transmits digital gift certificate ID information, including the parent card ID of the digital gift certificate, to the user terminal 20 via the communication unit 140 (step S406). The digital gift certificate ID information is data for registering the digital gift certificate in the user application so that it can be used using the parent card ID. The user terminal 20 receives the digital gift certificate ID information from the management server 10.

[0066] The user registration unit 211 of the user terminal 20 writes the parent card ID of the digital gift certificate included in the received digital gift certificate ID information to the storage unit 220 and registers the digital gift certificate in the user application (step S407). After that, the gift certificate application process is terminated.

[0067] <Processing of applications for short-term gift certificates> Next, we will explain the application process for short-term gift certificates (sub-cards) that users apply for. Short-term gift certificates are digital gift certificates that can only be issued to users whose user attribute is "short-term user" (for example, a tourist). Figure 13 is a sequence diagram showing the flow of the short-term gift certificate application process performed by the management system 1 according to this embodiment.

[0068] First, the user registration unit 211 of the user terminal 20 receives input from the user regarding the application for short-term gift certificates in the user application (step S411). Next, the user registration unit 211 transmits the short-term gift certificate application information, including ID information (for example, user ID and parent card ID), to the management server 10 via the communication unit 240 (step S412). The management server 10 receives the short-term gift certificate application information from the user terminal 20.

[0069] The value issuing unit 111 of the management server 10 refers to the user information in the user information table 122 based on the received ID information (step S413). For example, the value issuing unit 111 determines whether the user attribute corresponding to the received user ID is "short-term user". If the user attribute is not "short-term user" (for example, "resident"), the value issuing unit 111 may return an error to the user terminal 20. Next, if the user attribute is "short-term user", the value issuing unit 111 issues a card ID for a short-term gift certificate, associated with the parent card ID (step S414). The card ID for the short-term gift certificate issued at this time includes the received parent card ID. Next, the value issuance unit 111 performs a process to link the received ID information with the card ID of the issued short-term gift certificate (step S415).

[0070] Figure 14 illustrates the linking process for short-term gift certificates according to this embodiment. Reference numeral 121A in this figure shows an example of data in the value management table 121 before the linking process. In the value management table 121 before the linking process, only the common gift certificate (parent card) with parent card ID "8888" is registered as a digital gift certificate corresponding to user ID "1112". The value issuing unit 111 issues a card ID "1-8888" for a short-term gift certificate that includes parent card ID "8888". The value issuing unit 111 then writes the card ID "1-8888" and amount "5,000" of the issued short-term gift certificate to the value management table 121, associating them with user ID "1112". Reference numeral 121B in this figure shows an example of data in the value management table 121 after the linking process. As shown in the diagram, user ID "1112" is associated with both a common gift certificate (parent card) with parent card ID "8888" and a short-term gift certificate with card ID "1-8888". In this way, the value management table 121 manages multiple values ​​with different usage scopes (e.g., validity periods) by associating them with a single parent card ID.

[0071] Returning to Figure 13, the registration unit 114 of the management server 10 then transmits short-term gift certificate issuance information, including the parent card ID, to the user terminal 20 via the communication unit 140 (step S416). The short-term gift certificate issuance information is data for registering the short-term gift certificate in the user application so that it can be used within the usage range (validity period) using the parent card ID. The user terminal 20 receives the short-term gift certificate issuance information from the management server 10.

[0072] The user registration unit 211 of the user terminal 20 registers the short-term gift certificates in the user application based on the received short-term gift certificate issuance information (step S417). After that, the short-term gift certificate application process is terminated.

[0073] In the example described above, we explained the case of issuing short-term gift certificates to users with the user attribute "short-term user." However, for example, the value issuance unit 111 may issue long-term gift certificates to users with the user attribute "resident." Long-term gift certificates are digital gift certificates with a longer validity period than short-term gift certificates (for example, with an unlimited validity period). In other words, the value issuing unit 111 issues a value with a set usage range (e.g., usage period) in response to a request from the user terminal 20, and writes the issued value to the value management table 121, associating it with the parent card ID. Then, the registration unit 114 uses the parent card ID to register the issued value to the user terminal 20 so that it can be used within the set usage range.

[0074] For example, the value issuing unit 111 issues value (e.g., short-term or long-term gift certificates) with a set usage period based on the user's attribute information. For example, the value issuing unit 111 may issue a short-term gift certificate if the user attribute is "short-term user," and a long-term gift certificate if the user attribute is "resident." Alternatively, the value issuing unit 111 may issue a short-term gift certificate if the user's address is outside a predetermined area (e.g., "Area A"), and a long-term gift certificate if the user's address is within the predetermined area.

[0075] Furthermore, the value issuing unit 111 may issue value with a set usable region based on the user's attribute information. For example, the value issuing unit 111 may issue a regional gift certificate that can only be used in the region where the user's address is located. Furthermore, the value issuing unit 111 may issue value that can be used at designated participating stores. For example, it may issue a special gift certificate that can only be used at local shops.

[0076] <Value settlement processing> Next, we will explain value settlement processing, which allows users to settle transactions (for example, the purchase of goods or services) using value. There are three methods for value-based payments: (1) CPM (Consumer Presented Mode), (2) MPM (Merchant Presented Mode), and (3) Web-MPM. CPM is a method in which the user displays a barcode on the user terminal 20 and scans it with a barcode reader on the service provider terminal 30 (store scan method). MPM is a method in which the user scans a barcode displayed at the merchant using the user terminal 20 (user scan method). Web-MPM is a method in which the barcode is read using a web browser on the user terminal 20.

[0077] Figure 15 is a sequence diagram showing the flow of value settlement processing performed by the management system 1 according to this embodiment. First, the first settlement process S600, which performs settlement using CPM, will be described.

[0078] First, the value processing unit 212 of the user terminal 20 displays a payment screen on the display unit 250 that includes ID information (for example, a two-dimensional barcode representing the parent card ID (card ID of the common gift certificate)) (step S601).

[0079] (Payment screen) Figure 16 is an image diagram showing an example of a payment screen displayed on the user terminal 20 according to this embodiment. As shown in the diagram, the payment screen 1400 includes an area 1410 for displaying a two-dimensional code representing the parent card ID, an area 1420 for displaying the total balance of gift certificates "15,000 yen", an area 1430 for displaying the balance of common gift certificates "10,000 yen", and an area 1440 for displaying the balance of short-term gift certificates "5,000 yen". In this way, since multiple values ​​(common gift certificates and short-term gift certificates) are managed with a single parent card ID, users can utilize multiple values ​​without having to hold multiple card IDs. In other words, even if a user holds multiple values, they do not need to manage multiple card IDs.

[0080] Returning to Figure 15, the reader unit 360 of the service provider terminal 30 reads the ID information from the two-dimensional barcode displayed on the user terminal 20 (step S602). Next, the value processing unit 312 of the service provider terminal 30 accepts input for addition and subtraction (step S603). For example, the value processing unit 312 accepts input for selecting the gift certificate to be used (e.g., a short-term gift certificate). The value processing unit 312 also calculates the purchase points (e.g., limited-time points) to be awarded to the user in this transaction. Next, the value processing unit 312 of the service provider terminal 30 transmits transaction information to the management server 10 via the communication unit 340 (step S604). The transaction information includes ID information, merchant ID, type (short-term gift certificate), transaction amount, number of purchase points to be awarded, etc. The management server 10 receives the transaction information from the service provider terminal 30.

[0081] The settlement processing unit 113 of the management server 10 executes settlement processing based on the received transaction information (step S605). For example, the settlement processing unit 113 subtracts the transaction amount from the balance of the type "Short-term gift certificate" corresponding to the parent card ID in the value management table 121, and adds the purchase points awarded to the type "Limited-time points" corresponding to the parent card ID. The settlement processing unit 113 also transfers the transaction amount to the merchant's account. In other words, the settlement processing unit 113 executes settlement processing for the transaction using the value available for the transaction from among the multiple values ​​corresponding to the received parent card ID. Furthermore, if there are multiple values ​​available for the transaction, the settlement processing unit 113 accepts a selection of the value to be used for the transaction from the service provider terminal 30 and executes settlement processing for the transaction using the selected value.

[0082] Next, the display control unit 115 of the management server 10 transmits the payment result, which is the processing result of the payment process, to the service provider terminal 30 via the communication unit 140 (step S606). The service provider terminal 30 receives the payment result from the management server 10. The display control unit 313 of the service provider terminal 30 displays the received payment result on the display unit 350 (step S607).

[0083] Furthermore, the display control unit 115 of the management server 10 transmits the settlement result, which is the processing result of the settlement process, to the user terminal 20 via the communication unit 140 (step S608). The user terminal 20 receives the settlement result from the management server 10. The display control unit 213 of the user terminal 20 displays the received payment result on the display unit 250 (step S609). After that, the first payment process S600 is terminated.

[0084] Next, we will explain the second settlement process S620, which performs settlement using MPM or Web-MPM. First, the reader unit 260 of the user terminal 20 reads ID information (for example, the merchant ID) from a two-dimensional barcode installed at the storefront of a merchant (step S621). Next, the value processing unit 212 of the user terminal 20 accepts input of the payment amount (transaction amount) and the number of transactions (step S622). At this time, the value processing unit 212 may also accept input of the type to be used (for example, short-term gift certificates). Alternatively, the user application may be pre-configured to prioritize the use of types with a narrower scope of use (for example, those with an approaching expiration date). Alternatively, the user may be able to pre-configure the user application to specify the type of gift certificate to be used preferentially. Next, the value processing unit 212 of the user terminal 20 transmits transaction information to the management server 10 via the communication unit 240 (step S623). The transaction information includes ID information (user ID, parent card ID), merchant ID, type (short-term gift certificate), payment amount, etc. The management server 10 receives the transaction information from the user terminal 20.

[0085] The settlement processing unit 113 of the management server 10 executes settlement processing based on the received transaction information (step S624). Next, the display control unit 115 of the management server 10 transmits the payment result, which is the processing result of the payment process, to the service provider terminal 30 via the communication unit 140 (step S625). The service provider terminal 30 receives the payment result from the management server 10. The display control unit 313 of the service provider terminal 30 displays the received payment result on the display unit 350 (step S626).

[0086] Furthermore, the display control unit 115 of the management server 10 transmits the payment result, which is the processing result of the payment process, to the user terminal 20 via the communication unit 140 (step S627). The user terminal 20 receives the payment result from the management server 10. The display control unit 213 of the user terminal 20 displays the received payment result on the display unit 250 (step S628). After that, the second payment process S620 is terminated.

[0087] As described above, the management system 1 according to this embodiment includes a storage unit 120 that stores a first value (parent card) owned by a user in association with a value identifier (parent card ID), a value issuing unit that issues a second value (child card) with a set usage range in response to a request from a user terminal used by the user, and associates the issued second value with a value identifier, and a registration unit 114 that uses the value identifier to register the issued second value with the user terminal 20 so that it can be used within the set usage range.

[0088] With this configuration, the management system 1 according to this embodiment can manage multiple values ​​owned by a user, each with a different scope of use, using a single value identifier. As a result, a user can use multiple values ​​by managing only one value identifier. Therefore, value management becomes easier for the user.

[0089] Furthermore, the management system 1 according to this embodiment stores user attribute information and issues a second value with a usage period set based on the user's attribute information. This makes it possible to issue values ​​for short-term use, such as for tourism, and long-term use, such as for regional development, according to the user's attributes.

[0090] Furthermore, the management system 1 according to this embodiment also stores user attribute information and issues a second value with available regions set based on the user's attribute information. This allows, for example, the automatic issuance of a value for reconstruction in the region where the user lives.

[0091] Furthermore, the management system 1 according to this embodiment issues a second value with a set number of available participating stores. This makes it possible to issue a value that can be used only by local shops, for example, for the purpose of regional revitalization.

[0092] In the embodiment described above, we explained the case where multiple values ​​are associated with a parent card ID that manages multiple values ​​in common. However, the invention is not limited to this, and multiple values ​​may be associated with a user ID. Specifically, each of the card IDs for multiple values ​​may be associated with a user ID. For example, one user ID may be associated with the card ID of the first value, the card ID of the second value, and the card ID of the third value. In this case, when a user uses a value, the user ID may be used instead of the parent card ID. In other words, the user ID may be used as a value identifier that manages multiple values ​​in common.

[0093] Furthermore, although the above-described embodiment described a case where the management server 10 is a terminal device such as a single computer, at least one of the functions among the value issuance unit 111, value management unit 112, settlement processing unit 113, registration unit 114, display control unit 115, or storage unit 120 may be provided on a server device connected to the terminal device via a communication network. In this case, the server device may be a physical server or a cloud server provided by a cloud computing service.

[0094] Some or all of the functions of the management system 1, management server 10, user terminal 20, service provider terminal 30, or issuer terminal 40 in the above-described embodiment may be implemented by a computer. In that case, the functions may be implemented by recording a program for implementing these functions on a computer-readable recording medium, loading the program recorded on this recording medium into the computer system, and executing it. Here, "computer system" includes hardware such as the OS and peripheral devices. Furthermore, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into the computer system. In addition, "computer-readable recording medium" may also include those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or communication lines such as telephone lines, and those that hold programs for a certain period of time, such as volatile memory inside the computer system that acts as a server or client in that case. Furthermore, the above-mentioned program may be for implementing some of the functions described above, or it may be a program that can implement the above-mentioned functions in combination with a program already recorded in the computer system, or it may be implemented using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0095] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments and includes designs and the like that do not depart from the spirit of this invention. [Explanation of symbols]

[0096] 1 Management System 10 Management Server 110 Control Unit 111 Value Publishing Department 112 Value Management Department 113 Payment Processing Unit 114 Registration Department 115 Display Control Unit 120 Storage section 130 Input section 140 Communications Department 150 Display section 20 User Terminals 210 Control Unit 211 User Registration Section 212 Value Processing Unit 213 Display Control Unit 220 Storage section 230 Input section 240 Communications Department 250 Display section 260 Reading Unit 30 Service Provider Terminals 310 Control Unit 311 Merchant Registration Department 312 Value Processing Unit 313 Display Control Unit 320 Storage section 330 Input section 340 Communications Department 350 Display section 360 Reading Unit 40 Issuer terminal 410 Control Unit 411 Value Registration Department 412 Liaison Department 420 Storage section 430 Input section 440 Communications Department 450 Display section

Claims

1. A storage unit that stores the first value held by the user, associating it with a value identifier, A value issuing unit that, in response to a request from the user terminal used by the user, issues a second value with a defined usage range, and associates the issued second value with the value identifier, A registration unit registers the issued second value to the user terminal so that payment processing can be performed using the value identifier of the first value, and makes it available for use within the set usage range. Equipped with, The aforementioned storage unit further stores attribute information that identifies whether or not the user is a resident of a specific region. The value issuing unit issues a second value with a shorter usage period than the first value if the user is not a resident of the specific region. Management system.

2. The aforementioned memory unit further stores attribute information that identifies the area where the user lives. The value issuing unit issues the second value which is usable only in the area where the user lives. The management system according to claim 1.

3. The value issuing unit issues the second value for which the available merchants have been set. The management system according to claim 1.

4. A management method performed by a computer used in a management system, The first value held by the user is stored in association with a value identifier. In response to a request from the user terminal used by the user, a second value with a defined usage range is issued, and the issued second value is associated with the value identifier. The issued second value is registered in the user terminal so that payment processing can be performed using the value identifier of the first value, and so that it can be used within the set usage range. This is a management method that includes the following: Storing the aforementioned value identifier in association with it includes storing attribute information that identifies whether or not the user is a resident of a specific region. Associating the issued second value with the value identifier includes issuing the second value with a shorter validity period than the first value if the user is not a resident of the specific region. Management method.

5. The computer used in the management system The first value held by the user is stored in association with a value identifier. In response to a request from the user terminal used by the user, a second value with a defined usage range is issued, and the issued second value is associated with the value identifier. The issued second value is registered in the user terminal so that payment processing can be performed using the value identifier of the first value, and so that it can be used within the set usage range. It is a program that makes something happen. Storing the aforementioned value identifier in association with it includes storing attribute information that identifies whether or not the user is a resident of a specific region. Associating the issued second value with the value identifier includes issuing the second value with a shorter validity period than the first value if the user is not a resident of the specific region. program.

Images