Point management system, point management method, and program

Abstract

This technology provides a way to differentiate and manage points awarded to customers when they purchase goods or services through a point-issuing business, and points distributed through other businesses. [Solution] The point management system includes means for issuing external sales codes, which are code information distributed to users by a point issuing business via other businesses, and external sales points, which are points associated with said external sales codes; means for granting the external sales points associated with the distributed external sales codes to the user by linking the user ID of the user who received the external sales code with the external sales code ID of the distributed external sales code; and means for distinguishing and storing the points granted to the user between regular points, which are points granted to the user by the point issuing business without going through the other businesses, and the external sales points.

Description

Technical Field

[0004] , , , , , , , ,

[0005]

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

Background Art

[0002] When a customer purchases a product at a store or the like, points (numerical values that can be exchanged with other value media such as money or currency) may be given to the customer. The customer who has been given points can use the given points as part of the purchase price of a product or the like. Generally, a business operator that provides products or services often gives points to customers according to the purchase amount or the like.

[0003] Patent Document 1 discloses a system for the purpose of selling or distributing points themselves, rather than points associated with the sale of such products or services. The points distributed by this system (referred to as gift points) can be exchanged with points individually issued by many business operators (referred to as existing points). For example, business operator A purchases gift points through the system and distributes the gift points to new customers or long-term customers. A customer who has received gift points from business operator A can exchange the distributed gift points for desired existing points and use them when purchasing products or the like.

[0004] Patent Document 1 does not describe a method for business operator B, which issues existing points, to distribute the existing points to business operator C, which desires to attract customers by distributing the existing points, and to distinguish and manage the existing points directly given to customers by business operator B itself and the points given to the customer among the existing points distributed via business operator C.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

[0006] One of the objectives is to provide technology that allows for the separate management of points awarded to customers when they purchase goods or services through a service provider that issues points, and points distributed through other businesses. [Means for solving the problem]

[0007] According to one aspect of the present invention, the point management system includes: an issuing means for issuing external sales codes, which are code information distributed by a point issuing business to a user through another business, and external sales points, which are points associated with the external sales code, for points exchangeable for a medium of value; an awarding means for awarding the external sales points associated with the external sales code to the user by linking the user ID of the user who acquired the external sales code with the external sales code ID of the external sales code; a storage means for storing regular points, which are points awarded to the user by a point issuing business to the user by linking them with the user ID without linking them with the external sales code, as regular points usable by the user, linked with the user ID; a storage means for storing the external sales points awarded by the awarding means as external sales points usable by the user, linked with the user ID; and a storage value obtained by summing the regular points and the external sales points, linked with the user ID, as at least a portion of the points usable by the user.

[0008] According to one aspect of the present invention, in a point management method, a computer issues, for points exchangeable for a medium of value, an external sales code which is code information distributed to the user by the point issuing business operator through another business operator, and external sales points which are the points associated with the external sales code. The computer grants the external sales points associated with the external sales code to the user by linking the user ID of the user who acquired the external sales code with the external sales code ID of the external sales code. The computer stores the regular points which are the points granted to the user by the point issuing business operator by linking them to the user ID without linking them to the external sales code, as the regular points that the user can use, linked to the user ID. The computer stores the granted external sales points which are the external sales points that the user can use, linked to the user ID. The computer stores the sum of the regular points and the external sales points as at least a portion of the points that the user can use, linked to the user ID.

[0009] According to one aspect of the present invention, the program causes the computer to function as: means for issuing external sales codes, which are code information distributed to users by a point issuing business through other businesses for points exchangeable for a medium of value; and external sales points, which are points associated with the external sales codes; means for granting the external sales points associated with the external sales codes to the user by linking the user ID of the user who acquired the external sales codes with the external sales code ID of the external sales codes; means for storing regular points, which are points granted to the user by a point issuing business by linking them to the user ID without linking them to the external sales codes, as regular points usable by the user, linked to the user ID; means for storing the granted external sales points as external sales points usable by the user, linked to the user ID; and means for storing the sum of the regular points and the external sales points as at least a portion of the points usable by the user, linked to the user ID. [Effects of the Invention]

[0010] According to the present invention, it is possible to distinguish and manage points awarded to customers when they purchase goods, etc. through a service provided by a point issuing business, and points distributed through other businesses. [Brief explanation of the drawing]

[0011] [Figure 1] This figure shows an example of a point management system according to the embodiment. [Figure 2] This figure shows an example of an external sales code table according to the embodiment. [Figure 3] This figure shows an example of a point allocation management table according to the embodiment. [Figure 4] This figure shows an example of a consumption point management table according to the embodiment. [Figure 5] This figure shows an example of a point setting table according to the embodiment. [Figure 6A] The first figure shows an example of the external sales point awarding flow according to the embodiment. [Figure 6B] This is a second figure showing an example of the external sales point awarding flow according to the embodiment. [Figure 7] This figure shows an example of a sales code registration screen according to the embodiment. [Figure 8] This figure shows an example of a point confirmation screen according to the embodiment. [Figure 9] This figure shows an example of a normal point awarding flow according to the embodiment. [Figure 10] This figure shows an example of the point consumption flow according to the embodiment. [Figure 11] This figure shows a detailed example of the point consumption flow according to the embodiment. [Figure 12] This figure shows an example of a reward provision flow corresponding to external sales points according to the embodiment. [Figure 13] The first figure shows an example of a reward provision flow based on the number of external sales points held or acquired according to the embodiment. [Figure 14]It is a diagram showing an example of a campaign content presentation screen according to an embodiment. [Figure 15] It is a diagram showing an example of an increase rate of the number of acquired points according to the external sales points according to an embodiment. [Figure 16] It is a second diagram showing an example of a privilege provision flow according to the number of held or acquired external sales points according to an embodiment. [Figure 17] It is a diagram showing an example of an increase rate of the winning probability according to the external sales points according to an embodiment. [Figure 18] It is a third diagram showing an example of a privilege provision flow according to the number of held or acquired external sales points according to an embodiment. [Figure 19] It is a diagram showing an example of a privilege according to the external sales points according to an embodiment. [Figure 20] It is a first diagram showing an example of a privilege provision flow according to the number of uses of external sales points according to an embodiment. [Figure 21] It is a second diagram showing an example of a privilege provision flow according to the number of uses of external sales points according to an embodiment. [Figure 22] It is a third diagram showing an example of a privilege provision flow according to the number of uses of external sales points according to an embodiment. [Figure 23] It is a first diagram showing an example of a privilege provision flow according to the number of uses of external sales points at the granting store according to an embodiment. [Figure 24] It is a diagram showing an example of a campaign content presentation screen according to an embodiment. [Figure 25] It is a diagram showing an example of a table in which stores that join the external sales destination are registered according to an embodiment. [Figure 26] It is a diagram showing an example of an increase rate of the number of acquired points according to the number of uses of external sales points at the requesting store according to an embodiment. [Figure 27] It is a second diagram showing an example of a privilege provision flow according to the number of uses of external sales points at the granting store according to an embodiment. [Figure 28] It is a diagram showing an example of an increase rate of the winning probability according to the number of uses of external sales points at the granting store according to an embodiment. [Figure 29] The third figure shows an example of a reward provision flow based on the number of external sales points used at the issuing store according to the embodiment. [Figure 30] This figure shows an example of a reward based on the number of points used at the issuing store according to the embodiment. [Figure 31] The first figure shows an example of a benefit provision flow in response to participation in an external sales partner-related event according to the embodiment. [Figure 32] The second figure shows an example of a benefit provision flow for participation in an external sales partner-related event according to the embodiment. [Figure 33] This figure shows an example of an external sales point conversion table according to the embodiment. [Figure 34] This figure shows an example of the hardware configuration of the point management system according to the embodiment. [Modes for carrying out the invention]

[0012] <Embodiment> (System Configuration) Figure 1 shows an example of a point management system according to an embodiment. As shown in the figure, the point management system 1 includes a user terminal 10, various service servers 20, a point management server 30, an external sales server 40, and a store terminal 50. The user terminal 10, various service servers 20, point management server 30, external sales server 40, and store terminal 50 are connected to each other via a network NW so that they can communicate with each other.

[0013] User terminal 10 is a terminal device such as a smartphone or PC (personal computer) used by a user who is a customer of various online services such as e-commerce services (online shopping malls), payment services, communication services, financial services, facility reservation services (accommodation reservations, rental car reservations, transportation ticket reservations, beauty salon reservations, golf course reservations, etc.), lottery services (services in which users can receive some kind of benefit if they win a lottery), and reward services (services in which users can receive benefits according to their membership rank, usage status of various services such as purchase amount, and the number of points the user has).

[0014] The various service servers 20 are servers used by business operator A, which provides various services, to provide the above-mentioned e-commerce services, payment services, etc. The various service servers 20 may consist of multiple servers per service. Business operator A is also a business operator that issues points, etc., using the point management server 30 described below. The services provided by the various service servers 20 are affiliated with the point program service provided by business operator A. In other words, when a user purchases an item using the services provided by the various service servers 20, the user is awarded points. In addition, users can use points when purchasing items using the services provided by the various service servers 20. Services refer to e-commerce services, payment services, communication services, financial services, facility reservation services, etc., and items refer to tangible and intangible transactional objects such as goods and reservation service plans provided by each of these services.

[0015] Furthermore, in this embodiment, the user ID of a user (customer) using the user terminal 10 is valid through multiple services and point program services provided by various service servers 20. For example, if business operator A provides multiple services such as the aforementioned e-commerce service, payment service, communication service, financial service, and facility reservation service, as well as a point program service that manages points usable across multiple services, and users of this integrated internet service are assigned a user ID, then this user ID is common identification information that can be used across multiple services included in the integrated internet service. The user ID in this embodiment may be the user ID assigned by the integrated internet service in this example.

[0016] The point management server 30 manages the points for the point program service provided by business operator A. Point management includes issuing points, granting points, and consuming points. Issuing points means creating new points of a certain value. Granting points means allowing users to acquire those points. Consuming points means invalidating the points used when a user who has acquired points uses those points (uses points to pay for the purchase of items). There are two types of points: regular points and externally sold points. Regular points are points that are awarded when a user purchases items through services provided by various service servers 20. In other words, these are points that business operator A directly grants to users without going through other businesses, and are not linked to the externally sold codes that will be explained later.

[0017] Regular points may further consist of general regular points and limited-time points. General regular points are points valid for a predetermined first period from the last date of regular point issuance to the user. Limited-time points are points valid for a predetermined second period from the date they are issued to the user (first period > second period). Externally sold points are points issued by the point management server 30 that business operator A sells to another business operator B. Business operator B notices the high customer attraction power of points issued by business operator A and purchases points from business operator A for the purpose of awarding points to users who will become customers of the business that business operator B provides, in order to attract its own customers. Externally sold points are awarded to users through the external sales server 40. More precisely, an external sales code, which is code information exchangeable for external sales points (for example, a one-dimensional code consisting of a string of alphanumeric characters or a two-dimensional code such as a QR code (registered trademark)), is distributed to the user via the external sales server 40 (or directly transmitted to the user terminal 10). By registering this external sales code information with the point management server 30, external sales points linked to the registered external sales code are awarded to the user who received the external sales code. External sales points are points that business operator A awards to users via another business operator B, and are points linked to an external sales code.

[0018] The total of regular points and external sales points constitutes a user's points balance. For example, if a user has 1000 regular points and 500 external sales points, their total points balance will be 1500. A user's points balance is not limited to regular points and external sales points; other points may also be included. (If this user has an additional 500 points in other forms, their total points balance will be 2000.) From the user's perspective, regular points and external sales points can be used interchangeably. There is no distinction as to whether an item can only be purchased with regular points or only with external sales points; either type of point can be used. In the example above, the user can use 1500 points regardless of the breakdown of regular points and external sales points in their points balance. (However, items that can only be purchased with regular points or items that can only be purchased with external sales points may be offered.) Furthermore, when using points, users may choose to prioritize the use of external sales points or regular points from their points balance.

[0019] For example, when a user purchases an item through a service provided by the various service servers 20, the point management server 30 issues regular points corresponding to the purchase amount and awards those points to the user. Furthermore, when a user uses regular points to purchase an item through a service provided by the various service servers 20, the point management server 30 consumes those points. Additionally, when an external sales code distributed through the external sales server 40 is registered with the point management server 30, the point management server 30 awards external sales points corresponding to the external sales code to the user. These processes will be explained later with reference to Figures 6A to 11.

[0020] The point management server 30 comprises a control unit 31 and a storage unit 34. The control unit 31 performs various processes related to points. For example, the control unit 31 provides information on points earned to each user, provides an interface for registering external sales codes, provides an interface for users to set whether to prioritize using external sales points or regular points, accepts point grant applications, accepts point expiration reports, accepts requests for external sales codes, and issues external sales codes and manages points in response to accepted requests. The control unit 31 comprises an external sales point management unit 32 and a regular point management unit 33.

[0021] The External Sales Point Management Unit 32 manages external sales codes and external sales points. Specifically, the External Sales Point Management Unit 32 registers external sales codes, external sales points, etc., in the External Sales Code Table 301, as illustrated in Figure 2, and manages external sales points. The External Sales Code Table 301 has fields such as External Sales Code ID, External Sales Code, Number of External Sales Points, External Sales Destination ID, External Sales Code Issuance Date and Time, User ID, and External Sales Point Issuance Date and Time. The External Sales Code ID registers the identification information of the external sales code. The External Sales Code registers the code information (one-dimensional code, two-dimensional code, etc.) distributed to external sales destinations and users. The Number of External Sales Points registers the number of external sales points linked to the external sales code. The External Sales Destination ID registers the identification information of business operator B that purchases the external sales code. The External Sales Code Issuance Date and Time registers the date and time when the external sales code was issued in response to a request from the external sales destination (business operator B). The User ID field registers the identification information of the user who received the external sales code from the external sales partner. The External Sales Point Issuance Date and Time field registers the date and time when the external sales points associated with the external sales code were issued. External sales points are issued when the user who received the external sales code registers that external sales code with the point management server 30 (the number of external sales points themselves is registered when the external sales code is issued). For example, when the external sales code is registered, the User ID and the External Sales Point Issuance Date and Time fields are registered.

[0022] Furthermore, the external sales point management unit 32 manages external sales points by registering the external sales points earned by the user in the points management table 302, which is illustrated in Figure 3. The points management table 302 has items such as user ID, normal points, service ID, event ID, number of external sales points, external sales destination ID, date and time of acquisition, and expiration date. The points management table 302 may also have fields for registering the item ID of the item purchased when the points were earned, the store ID of the store where the item was purchased, etc. The normal points and service ID will be explained later. When the external sales point management unit 32 grants external sales points to a user, it registers the user's user ID, the identification information of the event (sales promotion campaign, etc.) in which the external sales points were earned, the number of external sales points to be awarded to the user, the identification information of the external sales partner (business operator B) that requested the issuance of the external sales code associated with the external sales points, the date and time the external sales points were awarded to the user, and the expiration date of the external sales points in the awarded points management table 302 as user ID, event ID, number of external sales points, external sales partner ID, date and time of acquisition, and expiration date, respectively. The event ID is not required.

[0023] Furthermore, the external sales point management unit 32 manages consumed external sales points by registering the external sales points used by the user and external sales points that have expired and become invalid in the consumption point management table 303, as illustrated in Figure 4. By subtracting the total number of external sales points registered in the consumption point management table 303 from the total number of external sales points registered in the grant point management table 302, the number of external sales points currently held by the user can be determined. The consumption point management table 303 has items such as user ID, normal points, external sales points, usage date and time, store ID, and classification flag. In addition, the consumption point management table 303 may also have fields for registering the service ID of the service used when the points were used, the item ID of the item purchased when the points were used, and the store ID of the store where the item was purchased. The classification flag is set to "0" if the number of external sales points or normal points registered in the consumption point management table 303 are points used by the user, and to "1" if they are points that have expired and become invalid. The normal points will be explained later. When a user uses external sales points, the external sales point management unit 32 registers the user's user ID, the number of external sales points used by the user, the date and time the external sales points were used, the identification information of the store where the external sales points were used, and 0 in the user ID, number of external sales points, date and time of use, store ID, and category flag in the points consumption management table 303, respectively. In addition, the external sales point management unit 32 refers to the expiration date in the points granted management table 302, and when an external sales point expires, it registers the user ID, number of external sales points, expiration date, and 1 related to that external sales point in the user ID, number of external sales points, date and time of use, and category flag in the points consumption management table 303, respectively.

[0024] The regular points management unit 33 manages regular points. For example, the regular points management unit 33 registers the regular points earned by a user in the points granting management table 302, as illustrated in Figure 3, and manages regular points. When the regular points management unit 33 grants regular points to a user, it registers the user's user ID, the number of regular points to be granted to the user, the identification information of the service used to earn the regular points, the identification information of the event (sales promotion campaign, etc.) in which the regular points were earned, the date and time the regular points were awarded to the user, and the expiration date of the regular points in the points granting management table 302, respectively. The event ID is not mandatory.

[0025] Furthermore, the regular points management unit 33 manages regular points by registering regular points used by users and regular points that have expired and become invalid in the consumption points management table 303, as illustrated in Figure 4. When a user uses regular points, the regular points management unit 33 registers the user's user ID, the number of regular points used by the user, the date and time the regular points were used, the identification information of the store where the regular points were used, and 0 in the consumption points management table 303 as user ID, number of regular points, date and time of use, store ID, and category flag, respectively. In addition, the regular points management unit 33 refers to the expiration date in the granted points management table 302, and when expired regular points occur, it registers the user ID, number of regular points, expiration date, and 1 related to those regular points in the consumption points management table 303 as user ID, number of regular points, date and time of use, and category flag, respectively.

[0026] Furthermore, the control unit 31 registers the number of points held by each user (number of valid points) in the point setting table 304, as illustrated in Figure 5, based on the registered contents of the awarded points management table 302 and the consumed points management table 303. The point setting table 304 has items such as user ID, number of regular points held, number of external sales points held, number of points held, priority category, membership rank, and number of services used. The control unit 31 updates the contents of the point setting table 304 by performing the following processes at predetermined intervals. The control unit 31 aggregates the number of regular points registered in the awarded points management table 302 for each user ID and calculates the total (referred to as the first total). The control unit 31 aggregates the number of regular points registered in the consumed points management table 303 for each user ID and calculates the total (referred to as the second total). The control unit 31 calculates the current number of regular points held by each user by subtracting the second total from the first total for each user ID and registers it in the number of regular points held in the point setting table 304. Similarly, the control unit 31 aggregates the number of external sales points registered in the points grant management table 302 for each user ID and calculates the total (referred to as the third total). The control unit 31 aggregates the external sales points registered in the points consumption management table 303 for each user ID and calculates the total (referred to as the fourth total). The control unit 31 calculates the current number of external sales points held by each user by subtracting the fourth total from the third total for each user ID and registers this in the number of external sales points held in the point setting table 304. The control unit 31 also registers the sum of the number of regular points held and the number of external sales points held as the total number of points held in the point setting table 304. In addition, the priority section of the point setting table 304 registers setting information for each user indicating whether the user prioritizes using regular points or external sales points, as will be explained later with reference to Figure 8. Furthermore, the control unit 31 queries a user management server (not shown) which manages the user's personal information and attribute information, to obtain each user's membership rank (the user's grade assigned according to their usage of various services), and sets it in the membership rank of the point setting table 304.Furthermore, the control unit 31 queries the various service servers 20 for information on the usage status of each service by the user and obtains information indicating which services each user is using. The control unit 31 then aggregates the number of services used for each user and sets it in the number of services used in the point setting table 304. For example, if a user is using the EC service, payment service, and communication service, then 3 will be registered as the number of services used for this user.

[0027] The memory unit 34 stores the external sales code table 301, the grant point management table 302, the consumption point management table 303, the point setting table 304, and so on. Note that these tables are just examples. For example, the grant point management table 302 and the consumption point management table 303 may be integrated into a single table to manage the granting and consumption of points. Alternatively, the data structure may not be limited to a table format, but may be any data structure that allows mutual reference of any information.

[0028] The external sales server 40 is operated by business operator B, which wants to use external sales points to attract customers. The external sales server 40 requests an external sales code from the point management server 30 and receives the external sales code. The external sales server 40 also sends an external sales code to the user terminal 10 when a user takes an action that earns external sales points (for example, when the user purchases an item from a service provided by business operator B).

[0029] The store terminal 50 is a tablet terminal or PC installed in a physical store or other location belonging to various services provided by business operator A. The store terminal 50 is equipped with means for reading external sales codes (such as a camera and an application for reading external sales codes). The physical store or other location where the store terminal 50 is installed may be a member of the point program service provided by business operator A. In other words, when a user purchases an item at this physical store or other location, the user may be awarded points. The physical store or other location where the store terminal 50 is installed may also be a store affiliated with an external sales partner (a store that handles the services of an external sales partner). The store or other location affiliated with an external sales partner may be a member of the point program service provided by business operator A, or business operator B may cooperate with the point program service provided by business operator A only during the period in which business operator B distributes external sales codes. The physical store or other location where the store terminal 50 is installed does not have to be a permanent store; it may be a sales promotion event venue or a booth set up for an event.

[0030] (Flow of awarding points for external sales) Here's an explanation of the process for awarding points for external sales. When awarding external sales points to users, external sales codes are first distributed to users via business operator B. When a user who has obtained an external sales code registers that code with their user ID on the point management server 30, the external sales points associated with the external sales code are awarded to the user. Distributing external sales codes via business operator B means that business operator B is the entity distributing the external sales codes. The external sales code may be sent to the user terminal 10 from, for example, the external sales destination server 40, or from a store terminal 50 installed at an event hosted by business operator B or at business operator B's stores, or it may be printed on paper and distributed to users. Furthermore, it is not necessary for servers or terminals managed by business operator B to be used when distributing external sales codes; they may be sent to the user terminal 10 from the point management server 30 or terminals managed by business operator A, etc., with the request and approval of business operator B. Furthermore, regarding the registration of acquired external sales codes with the user ID in the point management server 30, the user may log in to the external sales code registration site using their user ID and enter the external sales code to register it in the point management server 30. Alternatively, the user may provide the external sales code and user ID to business operator A by sending data or submitting the information written on paper, and business operator A may register the user ID and external sales code in the point management server 30. Or, the user may submit the external sales code and user ID to business operator B by sending data or submitting paper, and business operator B may provide the submitted information to business operator A, and business operator A may register the user ID and external sales code in the point management server 30.

[0031] Figure 6A is the first diagram showing an example of the external sales point awarding flow according to the embodiment. The external sales server 40 requests external sales codes from the point management server 30 (step S1). This request includes the number of external sales codes, the external sales points to be associated with each external sales code, etc. At this time, business operator B may purchase the external sales codes by paying business operator A an amount corresponding to the total amount of external sales points requested by the external sales server 40. The control unit 31 of the point management server 30 receives this request. The control unit 31 instructs the external sales point management unit 32 to issue external sales codes. The external sales point management unit 32 issues external sales codes (step S2). The external sales point management unit 32 generates (issues) the number of external sales codes requested by the external sales server 40 according to predetermined rules, assigns an external sales code ID to each of them according to predetermined rules, and registers the external sales code ID, external sales code, requested external sales points, and the date and time the external sales code was generated in the corresponding fields of the external sales code table 301. Next, the control unit 31 transmits the sales codes issued by the sales point management unit 32 to the sales destination server 40 (step S3). The sales destination server 40 receives the transmitted sales codes and stores them in the storage unit (step S4).

[0032] Once external sales codes are available, business B will conduct customer acquisition events and sales promotion campaigns using these codes. When users purchase items offered by business B (Step S5) or attend events during these events or campaigns, business B will distribute external sales codes to those users. External sales points may be treated more favorably than regular points, even if they have the same number of points, by offering benefits to users that are not available with regular points. Offering preferential treatment to external sales points motivates users to acquire them. For business B, distributing external sales codes (which lead to the acquisition of external sales points) can be expected to improve customer acquisition effectiveness. Therefore, when business A sells external sales codes, advertising that external sales points are treated more favorably than regular points, it motivates business B to purchase the external sales codes. Furthermore, business A may also sell external sales codes by advertising that using external sales points is more advantageous than using regular points. Such preferential treatment increases users' motivation to acquire and use external sales codes, and increases business B's willingness to purchase external sales codes. By promoting the acquisition and use of external sales points through such preferential measures, the various services provided by business operator A can also be revitalized. Furthermore, events and campaigns conducted by business operator B may be held on online shops or in physical stores.

[0033] When a user purchases an item at an external sales destination (such as an event held by business operator B or a store operated by business operator B) (step S5), the external sales destination server 40 distributes an external sales code to the user. For example, when purchasing an item, the user sends their email address from the user terminal 10 to the external sales destination server 40. The external sales destination server 40 sends the external sales code and an event ID (optional) to the email address (to the user terminal 10) (step S6). Alternatively, if the user is purchasing an item by logging into an online service on the internet provided by the external sales destination (provided by the external sales destination server 40), the external sales code may be displayed on the user's personal page of the service they are logged into. In addition to the external sales code, the email sent to the user terminal 10 or the personal page of the online service may also include the URL of the external sales code registration page provided by the point management server 30. The user operates the user terminal 10 to access the URL of the external sales code registration page and logs into the page using a user ID that can be used for services provided by business operator A (step S7). If a user does not have a user ID, they may create a new user ID. Alternatively, if a user has both a user ID usable for services provided by an external sales partner (business B) and a user ID usable for services provided by business A, and is logged into business B's online service and selects the URL displayed on the external sales code registration page, the system may query an unillustrated management server where the two user IDs are pre-associated and managed, retrieve the user ID usable for services provided by business A, and automatically log the user into the external sales code registration page.

[0034] When a user logs into the external sales code registration page, an interface 71, as illustrated in Figure 7, is displayed. The user operates the user terminal 10 to enter the external sales code into the input field 72 and presses the registration button 73 to register the external sales code. The interface 71 may also have an input field for an event ID, allowing the user to enter an event ID. Alternatively, an event ID may be sent when the user logs into the page. Once the external sales code is registered, the control unit 31 receives the external sales code and the user ID of the logged-in user and grants external sales points to the user (step S8). Specifically, the external sales point management unit 32 registers the received user ID and the date and time of receipt with the user ID and the date and time of issuance of external sales points in the data where the distributed external sales code is registered in the external sales code table 301. Furthermore, the external sales point management unit 32 registers the same data (acquisition date is the external sales point issuance date) as the data registered in the external sales code table 301 for the user ID, number of external sales points, external sales destination ID, and acquisition date and time in the awarded points management table 302, and registers the event ID sent from the user terminal 10 in the event ID field. As a result, external sales points are awarded to the user. Once external sales points are awarded, the user can check the awarded points.

[0035] For example, when a user operates the user terminal 10 to access the URL of the user-specific point confirmation page provided by the point management server 30 and logs in, the point confirmation screen 81, as illustrated in Figure 8, is displayed. Based on the logged-in user ID, the control unit 31 reads the number of regular points held, the number of external sales points held, and the total number of points held associated with that user ID from the point setting table 304 and displays them on the point confirmation screen 81. Since external sales points and regular points are displayed separately, the user can understand the status of external sales points and regular points on the point confirmation screen 81. In addition, since the total of the external sales points and regular points held is displayed, the user can understand the total number of points held on the point confirmation screen 81. On the point confirmation screen 81, it is possible to set whether to prioritize the use of external sales points, prioritize the use of regular points, or confirm each time whether to use external sales points or regular points. This setting is stored in the priority section of the point setting table 304 stored in the storage unit 34. For example, if "Prioritize the use of external sales points" is set, the control unit 31 registers 0 in the priority category of the point setting table 304; if "Prioritize the use of regular points" is set, it registers 1; if "Confirm each time" is set, it registers 2; and if neither is set, it registers 3. When "Prioritize the use of external sales points" is set, external sales points will be used first when a user uses points to purchase items, etc. If a reward can be obtained by using external sales points, setting it in this way may allow the user to obtain more rewards. If "Confirm each time" is set, the user may be able to obtain the maximum rewards that can be obtained by using external sales points by making a choice each time points are used, such as using external sales points when a reward can be obtained by using external sales points, and using regular points otherwise.

[0036] (Variation 1) In the flow shown in Figure 6A, the external sales server 40 sends the purchased external sales code to the user terminal 10 when the user takes an action that earns external sales points. Alternatively, when the user takes an action that earns external sales points, the user's email address is collected, and later, when business operator B purchases the external sales codes to be distributed, it may provide the point management server 30 with information on the email addresses of the users to whom the external sales codes will be distributed and the number of external sales points to be awarded. The point management server 30 then sends the external sales code associated with the external sales points to be awarded to each email address.

[0037] (Modification 2) In the flow chart of Figure 6A and Modification 1, instead of distributing sales codes, the point management server 30 may send an email to the user's email address containing a URL to a web page where an online lottery can be conducted. The point management server 30 may then issue sales codes and sales points based on the results of the lottery conducted by the user on this web page, and award the sales points to the user. For example, in the online lottery, the winner can receive 10 points, 100 points, or 1000 points. If 10 points are won, the sales point management unit 32 may issue a sales code associated with 10 points, immediately associate the winning user's user ID with the sales code, and register it in the sales code table 301 and the awarded points management table 302. Alternatively, the point management server 30 may issue a sales code associated with 10 points, send the issued sales code to the user terminal 10, and then award the user 10 sales points through the processing in steps S7 and S8 of Figure 6A.

[0038] (Variation 3) In the flow shown in Figure 6A, the external sales server 40 pre-stores external sales codes and distributes the stored external sales codes to users. However, when a user takes an action that earns points, the external sales server 40 may request an external sales code from the point management server 30 online each time, specifying the external sales points to be associated with the code. In response to this request, the point management server 30 issues an external sales code and sends it to the external sales server 40, which then sends the external sales code to the user terminal 10 (or the point management server 30 may directly send the external sales code to the user terminal 10). This eliminates the need for business operator B to prepare external sales codes in advance, and allows them to obtain and distribute external sales codes linked to the number of external sales points to be awarded to users only when and in the required quantity.

[0039] Figure 6B is a second diagram showing an example of the external sales point awarding flow according to the embodiment. The flow in Figure 6A illustrates an example of the process of acquiring external sales points using a user terminal 10 and an external sales server 40. The flow in Figure 6B explains the awarding of external sales points when a user participates in an event primarily organized by an external sales company. When a user purchases an item or attends a designated offline event (for example, a sales promotion event primarily organized by an external sales partner), the user logs into the points program service using a store terminal 50 set up at the event venue (step S101). For example, the points program service has a page for awarding external sales points for the event, and a mechanism is implemented that allows external sales codes to be distributed on the spot to users who participated in the event with simple operations. For example, by pressing the "External Sales Code Issuance Button" on the store terminal 50, the user requests an external sales code from the points management server 30 (step S102). Upon receiving this request, the external sales point management unit 32 issues an external sales code and sends the issued external sales code to the store terminal 50 (step S103). The external sales point management unit 32 also registers the external sales code ID, the issued external sales code, the external sales partner ID, the predetermined number of external sales points, and the date and time of external sales code issuance in the external sales code table 301.

[0040] Next, the user operates the store terminal 50 to log in to the external sales code registration page and registers the external sales code (step S104). The external sales point management unit 32 registers the logged-in user's user ID, the event ID of the event (assuming it is set in advance), the number of external sales points, the external sales destination ID, and the date and time of acquisition in the points management table 302. The external sales point management unit 32 also registers the logged-in user's user ID and the current time in the external sales code table 301, along with the user ID and the date and time of issuance of the external sales points in the data associated with the external sales code registered in step S104. As a result, the predetermined external sales points are awarded to the user who participated in the event on the spot (step S105).

[0041] Alternatively, the "External Sales Code Issuance Button" can be used to issue an external sales code, and the issued external sales code can be sent to the user terminal 10 or printed on paper. After that, external sales points can be awarded to the user through the processes in steps S7 and S8 of Figure 5. If printed on paper, the external sales code can be registered by reading the external sales code at the store terminal 50.

[0042] (Normal point accrual flow) Next, we will explain the process for awarding points as usual. Figure 9 shows an example of a normal point awarding flow according to the embodiment. The user operates the user terminal 10 to purchase an item using an online service provided by the various service servers 20 or a physical store where a store terminal 50 is installed (step S11). The various service servers 20 calculate the number of points to be awarded to the user using at least one of the following: the item ID and purchase amount of the item purchased by the user, the service ID, the store ID of the store where the item was purchased (a physical store where a store terminal 50 is installed or an online virtual store), and, if points are awarded for a campaign or event, the event ID of that campaign or event. (In the case of a purchase at a physical store, the store terminal 50 sends the item ID and purchase amount of the item purchased by the user, the service ID of the service the store belongs to, the store ID of the store where the item was purchased, and, if points are awarded for a campaign or event, the event ID of that campaign or event, etc. to the various service servers 20.) The various service servers 20 identify the user ID of the user to whom points should be awarded and the number of points to be awarded, and submit a request for normal points to the point management server 30 (step S12). In this case, the application details may include not only the user ID and points, but also the item ID, purchase amount, service ID, store ID, and event ID.

[0043] The point management server 30 accepts the application for these regular points (step S13). The control unit 31 of the point management server 30 constantly monitors for incoming point applications and accepts them at predetermined control cycles. As a result, point applications arrive moment by moment from stores and other locations nationwide, and the acceptance process is carried out according to this control cycle. When the control unit 31 accepts the application for regular points, the regular point management unit 33 registers the information sent from the various service servers 20 in the user ID, number of regular points, service ID, and event ID in the awarded point management table 302, and registers, for example, the current date and time in the acquisition date and time. By registering the user ID and number of regular points in association with the awarded point management table 302, regular points are awarded to the user (step S14). Once regular points are awarded, the user can check the awarded regular points. For example, when a user operates the user terminal 10 to access the URL of the points confirmation page provided by the points management server 30 and logs in, the points confirmation screen 81 shown in Figure 8 is displayed, and the user can check their regular points on this screen.

[0044] (Point consumption flow) Next, I will explain the process for using points. Figure 10 shows an example of the point consumption flow according to this embodiment. The user operates the user terminal 10 to purchase items using points through online services provided by the various service servers 20 or at physical stores where store terminals 50 are installed (step S21). The various service servers 20 identify the item ID and purchase amount of the items purchased by the user, the service ID, the store ID of the store where the items were purchased, and the number of points used when purchasing the items (in the case of purchases at physical stores, this information is transmitted from the store terminal 50 to the various service servers 20), and report the use of points to the point management server 30 (step S22). At this time, the report may include the user ID, the number of points used, as well as the item ID, purchase amount, service ID, store ID, and event ID. Also, if the user has set "Confirm each time" on the point confirmation screen 81 as illustrated in Figure 8, the control unit 31 will display an option on the display of the user terminal 10 or store terminal 50 each time an item is purchased, asking whether to use external sales points or regular points. The user operates the user terminal 10, etc., to select whether to use external sales points or regular points and purchase the item. In this case, the report includes information indicating whether external sales points or regular points are used. The point management server 30 receives the report of points used (step S23). The control unit 31 of the point management server 30 constantly monitors for the transmission of point usage reports and accepts them at predetermined control cycles. As a result, point usage reports arrive moment by moment from stores nationwide, various transactions, and multiple service servers identified by service ID, and the acceptance processing is performed at these control cycles.

[0045] When the control unit 31 receives a report of points to be used, it confirms whether to use regular points or points to be used (step S24). For example, the control unit 31 confirms whether to use regular points or points to be used by one of the following methods (A1) to (A3). (A1) When using points (at the time of payment), the user will be shown the different types of points, and the points will be used in the order selected by the user. (A2) Users are asked to set their preferred points in advance, and when they use points, the process is carried out based on those settings. (A3) If the store where the purchase was made is an external sales location, the external sales points will be used first and will be used first. For example, if "Prioritize the use of external sales points" is selected on the point confirmation screen 81 illustrated in Figure 8, the control unit 31 decides to use external sales points (method (A2) above). If "Confirm each time" is selected, the control unit 31 decides whether to use external sales points or regular points based on the information included in the point usage report indicating whether to use external sales points or regular points (method (A1) above). In addition, the storage unit 34 stores a table for each store ID in which information such as which services the store is affiliated with and whether it is affiliated with the external sales partner (business operator B) who is the purchaser of external sales points is registered. The control unit 31 refers to this table based on the store ID included in the point usage report, and if the store ID is a store that handles the services of the external sales partner, it decides to use external sales points regardless of the setting on the point confirmation screen 81 (method (A3) above).

[0046] If the control unit 31 decides to use external sales points, it instructs the external sales point management unit 32 to process the consumption of the points to be used, and if it decides to use regular points, it instructs the regular point management unit 33 to process the consumption of regular points. In accordance with this instruction, the external sales point management unit 32 or the regular point management unit 33 consumes the reported points (step S25). For example, if a user with user ID=U001 uses 1000 external sales points at a store with store ID=P01, the external sales point management unit 32 registers "U001", "1000", and "P01" in the user ID, number of external sales points, and store ID in the consumed points management table 303, respectively, and registers, for example, the current date and time in the usage date and time. For example, if a user with user ID=U001 uses 1000 regular points at a store with store ID=P01, the regular points management unit 33 registers "U001", "1000", and "P01" in the user ID, regular points, and store ID fields of the points consumption management table 303, respectively, and registers the current date and time in the usage date and time field. By registering the user ID and the number of regular points or points purchased outside the store in association with each other in the points consumption management table 303, the user's points are consumed. The point status after consumption can be checked on the points confirmation screen 81, as illustrated in Figure 8.

[0047] The processes in steps S24 and S25 of Figure 10 will be explained in more detail with reference to Figure 11. Figure 11 shows a detailed example of the point consumption flow according to the embodiment. The control unit 31 obtains the user's priority setting for point usage (step S201). Specifically, when the control unit 31 receives a point usage instruction, for example, due to a transaction at the store with store ID=P01, it uses the user's user ID to read the priority category from the point setting table 304 in the storage unit 34. A priority category of 0 means that external sales points will be used preferentially, and a priority category of 1 means that regular points will be used preferentially. A priority category of 2 means that confirmation will be made each time, and a priority category of 3 indicates that no setting has been made. The control unit 31 uses either external sales points or regular points preferentially according to the value of the read priority category. If the priority category is 0 (prioritize external sales points) (step S202; external sales points), the control unit 31 uses external sales points preferentially (step S203). For example, assume that the value exchange rate for external sales points and regular points is 1 yen per point (this assumption is the same hereafter in Figure 11). Furthermore, if the amount used is 1000 points and the user has 2000 points, consisting of 1100 external sales points and 900 regular points, the control unit 31 will consume 1000 points from the external sales points. The external sales point management unit 32 registers the consumption of 1000 points of external sales points in the consumed points management table 303. The control unit 31 refers to the user's user ID data in the point setting table 304 and subtracts 1000 from both the number of external sales points held and the total number of points held in this data. Also, if the number of external sales points held by the user is less than the amount used, the deficit will be consumed from regular points. For example, in the above example, if the user has 900 external sales points and 1100 regular points, the control unit 31 will consume 900 points from the external sales points and 100 points from the regular points.

[0048] If the priority category is 1 (prioritize regular points) (step S202; regular points), the control unit 31 prioritizes consuming regular points (step S204). For example, if the usage amount is 1000 points and the user has 2000 points, consisting of 900 points from external sales and 1100 points from regular points, the control unit 31 consumes 1000 points from regular points. The regular point management unit 33 registers the consumption of 1000 points of regular points in the consumed points management table 303. The control unit 31 refers to the user ID data of the logged-in user in the point setting table 304 and subtracts 1000 from both the number of regular points held and the total number of points held in this data. Also, if the regular points held by the user are less than the usage amount, the deficit is consumed from external sales points. For example, in the above example, if the user has 1100 points from external sales and 900 points from regular points, the control unit 31 will consume 900 points from regular points and 100 points from external sales points.

[0049] If the priority category is 2 (confirm each time) (step S202; other, step S205; select each time), the control unit 31 presents the user with a choice of whether to prioritize the consumption of external sales points or regular points (step S206). For example, the control unit 31 sends an unillustrated point usage selection screen to the user terminal 10. The point usage selection screen includes a choice of whether to prioritize external sales points or regular points. The user selects one of the options displayed on the point usage selection screen. Once the user has selected an option, information indicating whether to prioritize the consumption of external sales points or regular points is sent from the user terminal 10 to the point management server 30. The control unit 31 obtains the point type selected by the user (external sales points or regular points) (step S207). The control unit 31 consumes either external sales points or regular points according to the obtained point type. If the selected point type is regular points (step S208; regular points), the control unit 31 executes the process in step S204. If the selected point type is an external sales point (step S208; external sales point), the control unit 31 executes the process in step S203.

[0050] If the priority category is 4 (not set) (step S202; Other, step S205; Other), the control unit 31 determines whether the store using the points is a store of an external sales partner (step S209). For example, the control unit 31 refers to the list of store IDs of external sales partners stored in the memory unit 34 and determines whether the store with store ID=P01 is a store of an external sales partner. If it is an external sales partner store (step S209; Yes), the control unit 31 executes the process in step S203. If it is not an external sales partner store (step S209; No), the control unit 31 executes the process from step S206 onwards. Alternatively, the system may be configured to execute step S204 or step S203 if it is not an external sales partner store. By managing external sales points linked to user IDs separately from regular points, the use of external sales points can be promoted in transactions at stores that award external sales points, and the business of business operator B involved in the operation of the store can be further promoted by business operator A, which issues the points.

[0051] The above-described process applies when an item transaction occurs at an online store. However, when an item transaction occurs at a physical store, the point information related to that transaction can also be reflected in the point granting management table 302, etc., of the point management server 30. For example, if a physical store is linked to various service servers 20 via POS, when an item transaction occurs at the physical store, data such as the transaction date and time, the item ID related to the transaction, the store ID of the physical store, and the transaction amount are sent to the various service servers 20. If points are earned or consumed in an item transaction, in addition to this data, the user ID and the number of points earned or consumed associated with that user ID are sent to the various service servers 20. The user ID, the number of points earned or consumed associated with that user ID, the store ID, etc. are then sent from the various service servers 20 to the point management server 30, and the control unit 31 registers them in the point granting management table 302, the point consumption management table 303, etc. If POS integration is not in place, after an item transaction, the transaction date and time, item ID related to the transaction, store ID of the physical store, transaction amount, user ID, and the number of points earned or consumed associated with that user ID are transmitted from a terminal device installed in the physical store to the various service servers 20, for example, by data transfer. In the same way as with POS integration, this information is registered in the points management table 302 of the points management server 30. Alternatively, the user may upload information from a user terminal 10 directly, for example, receipt information, and the transaction date and time, item ID, store ID, transaction amount, user ID, and the number of points earned or consumed contained in the receipt information are transmitted to the various service servers 20. In this case as well, the data transmitted by the user is sent from the various service servers 20 to the points management server 30 and registered in the points management table 302.

[0052] (A process for providing benefits based on external sales points) Next, we will explain the process for providing benefits based on external sales points. As mentioned above, in this embodiment, regular points and external sales points are managed separately. Therefore, it becomes possible to provide benefits to users according to their acquisition and usage of external sales points. By providing benefits to users who have acquired external sales points, it is possible to increase users' motivation to acquire external sales points and improve the effectiveness of attracting customers to the services provided by business operator B.

[0053] Figure 12 shows an example of a reward provision flow corresponding to external sales points according to the embodiment. The user operates the user terminal 10 to log in to the point program service provided by the point management server 30 (step S31). The point program service provides information on services and items that can earn points, the external sales code registration page 61 in Figure 6, the point confirmation screen 81 in Figure 7, and information on benefits offered to the user. The control unit 31 of the point management server 30 checks the status of external sales points by referring to the awarded points management table 302 and the consumed points management table 303 based on the user ID of the logged-in user (step S32). For example, the control unit 31 refers to the user ID, number of external sales points, and acquisition date and time in the awarded points management table 302 to calculate the total number of external sales points earned by the user within a predetermined period. Also, for example, the control unit 31 refers to the user ID, number of external sales points, and usage date and time in the consumed points management table 303 to calculate the total number of external sales points used by the user within a predetermined period. Furthermore, for example, the control unit 31 refers to the user ID, number of sales points, date and time of use, and store ID in the points consumption management table 303, and to a table in the storage unit 34 that registers stores affiliated with the sales partner, to calculate the total sales points used by the user at stores affiliated with the sales partner within a predetermined period. Next, the control unit 31 calculates benefits according to the status of sales point acquisition and usage (step S33). For example, the control unit 31 calculates benefits using the following methods (a) to (e).

[0054] (a) Calculate rewards based on the number of external sales points held or earned. Depending on the total number of external sales points held or acquired within a predetermined period, the control unit 31 decides to provide the following benefits: (a-1) The number of points earned in the campaign will be increased to N times the normal amount as a benefit; (a-2) The probability of winning in the lottery service will be increased compared to general users as a benefit; (a-3) Benefits will be given according to the number of external sales points held or acquired. The control unit 31 decides to provide one or more of the above benefits (a-1) to (a-3) to the user. An example of the processing for each of (a-1) to (a-3) will be explained below.

[0055] Regarding (a-1) Referring to Figure 13, an example of the process in (a-1) will be explained. The user operates the user terminal 10 to access the online medium (Web page) of the service that provides the benefits offered by the various service servers 20 (step S301). An example of a service that provides benefits is an e-commerce service. The various service servers 20 obtain the user ID of the user who accessed from the user terminal 10 (step S302). If the user is not logged in to the Web page, the various service servers 20 present the login screen for the e-commerce service, etc., and prompt the user to log in. If the user is already logged in, the various service servers 20 present the campaign details (step S303). For example, if the campaign details are that if the date on which an item is purchased in the e-commerce service falls within a specified period, the normal points for the purchase amount will be increased (for example, by +N times), the various service servers 20 present a screen 201, etc., showing the breakdown of points earned, as illustrated in Figure 14.

[0056] Meanwhile, the user performs an action on the e-commerce site that could potentially earn points, such as adding an item to their shopping cart (step S304). When such an action is performed, the various service servers 20 send the user ID to the point management server 30 and inquire about the external sales points (external sales points that serve as the basis for calculating points awarded in the campaign) associated with the user ID (step S305). In the point management server 30, the control unit 31 refers to the awarded points management table 302 and calculates the total number of external sales points earned during a predetermined period (for example, the campaign period, or six months prior to the time of participation in the campaign) associated with the transmitted user ID. Specifically, the control unit 31 refers to the awarded points management table 302, extracts data where the value of the user ID field is the user ID obtained from the various service servers 20 and the value of the acquisition date and time field falls within the predetermined period, and calculates the total number of external sales points for the extracted data. The control unit 31 also refers to the consumed points management table 303 and calculates the total number of external sales points consumed during the predetermined period associated with the user ID. Specifically, the control unit 31 refers to the consumption point management table 303 and extracts data where the value of the user ID field is a user ID obtained from the various service servers 20 and the value of the usage date and time field falls within a predetermined period, and calculates the total number of external sales points for the extracted data. Then, the control unit 31 subtracts the total number of external sales points consumed from the total number of external sales points earned, and uses this value as the basis for calculating the points to be awarded in the campaign. Alternatively, the control unit 31 may use the total number of external sales points earned during the predetermined period as the basis for calculating the points to be awarded in the campaign, without subtracting the total number of external sales points consumed during the predetermined period. Once the external sales points are calculated, the control unit 31 sends the calculated number of external sales points to the various service servers 20 (step S306).

[0057] The various service servers 20 calculate the number of regular points that can be awarded to the user based on the sales points obtained from the point management server 30, and present this to the user as points that can be earned in the campaign (step S307). The various service servers 20 have a correspondence table 202 between sales points and the rate of increase in earned points, as illustrated in Figure 15. This table may be prepared for each campaign. The various service servers 20 refer to the correspondence table 202 to obtain the rate of increase in earned points (+N times, +(N+1) times, +(N+2) times, etc.) corresponding to the sales points obtained from the point management server 30. Note that the rate of increase in earned points may be calculated not in table format, but by a function f that outputs the rate of increase in earned points when sales points are input. For example, suppose the rate of increase in earned points is +N times. Also, suppose that the regular points awarded for the amount of items purchased by the user are, for example, 1% of the purchase amount. The various service servers 20 calculate the normal points to be awarded to the user by multiplying the total value of the items the user has placed in their shopping cart by (1 × N)%, which is the point redemption rate of 1% awarded to the user, and displaying the calculated number of points on the shopping cart screen, for example. Furthermore, if the user changes the items in their shopping cart, the various service servers 20 calculate and display the points to be awarded to the user each time, based on the total value of the items in the shopping cart.

[0058] Next, the user operates the user terminal 10 to confirm an action that will earn points (step S308). For example, the user performs a purchase action for an item placed in the shopping cart. The various service servers 20 identify the number of points and user ID presented in step S307 and submit a request to the point management server 30 (step S309). The point management server 30 awards the user regular points in the same manner as the processes in steps S13 and S14 of Figure 9 (step S310).

[0059] While e-commerce services are used as an example here, the service conducting the campaign may be any other service. Furthermore, the online media in which the campaign is conducted may include online media provided by the various services, as well as online media linked to the services conducting the campaign. The conditions for awarding points based on external sales points may also be, in addition to or instead of the campaign period, for example, that points are awarded only if the location or store where the item is traded meets specific conditions. Conditions other than item purchase may also be used, such as usage of other services (purchase amount, frequency of use, etc.), usage of other services' online media (e.g., various transactions and experiences involving page views, impressions, clicks, installs, video viewing, etc.), or arbitrary user actions specified by the external sales partner, service provider, or related entities (e.g., conversions). Additionally, the campaign is not limited to online media; it may also be conducted in offline physical stores, etc.

[0060] Regarding (a-2) Referring to Figure 16, an example of the process in (a-2) is explained. The user operates the user terminal 10 to access the online medium (Web page) of a service linked to the lottery service by the various service servers 20 (step S321). The service linked to the lottery service may be any of the following: e-commerce service, payment service, communication service, usage reservation service, etc. The various service servers 20 obtain the user ID of the user who accessed from the user terminal 10 (step S322). If the user is not logged in to the Web page, the various service servers 20 present the login screen for the e-commerce service, etc., and prompt the user to log in. If the user is already logged in, the various service servers 20 present the lottery details (step S323). The lottery details may include information such as conditions such as the application period, eligibility requirements, and information on benefits such as points that can be obtained if the user wins. For example, when the user accesses the service linked to the lottery service, the lottery details may be displayed on the display unit of the user terminal 10 using a widget function, etc. Alternatively, the lottery service's functionality may be linked to the online media of each service via API integration, file integration, database integration, webhook integration, etc., and the system may be configured so that when the user terminal 10 logs in to the online media of each service, the lottery details are sent to the user terminal 10. Furthermore, the lottery details presented may be prepared for each service that the user first accesses.

[0061] Next, the user applies for the lottery by operating the user terminal 10 (step S324). The various service servers 20 accept the application for the lottery (step S325). The various service servers 20 determine whether the time of acceptance is within the application period. If it is not within the application period, the user terminal 10 is notified accordingly. The following explanation will continue assuming that it is within the application period. If it is within the application period, the various service servers 20 register the user ID that accepted the application as the applicant user in the storage unit. Alternatively, if it is within the application period, the various service servers 20 may issue a lottery number using a predetermined logic and send the issued lottery number to the user terminal 10. In this case, in the subsequent lottery, it will be determined whether the issued lottery number is a winning number or a losing number.

[0062] When it is time to execute the lottery (for example, a predetermined time such as one week after the end of the application period), the various service servers 20 decide to execute the lottery (step S326). Once the decision to execute the lottery is made, the various service servers 20 send the user ID to the point management server 30 and inquire about the external sales points associated with the user ID (step S327). In the point management server 30, the control unit 31 refers to the granted points management table 302 and calculates the total number of external sales points acquired during a predetermined period associated with the transmitted user ID (for example, the period during which the lottery can be applied for, or six months prior to the time the lottery was applied for). The control unit 31 then refers to the consumed points management table 303 and calculates the total number of external sales points consumed during the predetermined period associated with the user ID. The control unit 31 then subtracts the total number of consumed external sales points from the total number of acquired external sales points. Alternatively, the control unit 31 may calculate the total number of acquired external sales points during the predetermined period without subtracting the total number of consumed external sales points during the predetermined period. When the external sales points are calculated, the control unit 31 sends the calculated number of external sales points to the various service servers 20 (step S328). When the various service servers 20 receive the external sales points, they execute a lottery (step S329). The lottery is executed according to a predetermined logic. For example, whether or not to win the lottery may be determined based on a predetermined winning probability. The various service servers 20 have a correspondence table 203 between external sales points and the rate of increase in the winning probability, as illustrated in Figure 17. This table 203 may be prepared for each lottery. The various service servers 20 refer to the correspondence table 203 to obtain the rate of increase in the winning probability (+10%, +20%, etc.) corresponding to the external sales points received from the point management server 30. Note that the rate of increase in the winning probability may be calculated not in table format, but by a function f that outputs an increase rate when external sales points are input. For example, suppose the original predetermined winning probability is 10%, and the rate of increase in the winning probability according to external sales points is +10%. Then, the various service servers 20 execute the lottery with a winning probability of 20%. Users who possess external sales points will have a higher winning probability than users who do not possess external sales points.The various service servers 20 send the lottery results to the user terminal 10 (step S330).

[0063] Furthermore, the eligibility requirements for the lottery may be based on conditions other than the time period, such as awarding points only if the location or store where the item is traded meets specific conditions. Other conditions may also be based on usage of other services (purchase amount, frequency of use, etc.), usage of online media of other services (e.g., various transactions and experiences involving page views, impressions, clicks, installs, video viewing, etc.), or arbitrary user actions specified by external vendors, service providers, or related entities (e.g., conversions). Additionally, the lottery may be conducted offline, such as at physical stores, rather than being limited to online media.

[0064] Regarding (a-3) Referring to Figure 18, an example of the process in (a-3) is explained. The user operates the user terminal 10 to access the online medium (Web page) of a service linked to the reward service by the various service servers 20 (step S341). The service linked to the reward service may be any of the following: e-commerce service, payment service, communication service, reservation service, etc. The rewards provided by the reward service are usually points, lottery tickets, discount tickets, coupons, etc. The various service servers 20 obtain the user ID of the user who accessed from the user terminal 10 (step S342). If the user is not logged in to the Web page, the various service servers 20 present a login screen for the e-commerce service, etc., and prompt the user to log in. If the user is already logged in, the various service servers 20 activate the reward service (step S343). For example, when a user accesses a service linked to the reward service, information prompting participation in an online event to obtain rewards may be displayed on the display of the user terminal 10 using a widget function, etc. Alternatively, the rewards service may be configured to be linked to the online media of each service via API integration, file integration, database integration, webhook integration, etc., so that when the user terminal 10 logs in to the online media of each service, information prompting participation in online events, etc., to obtain rewards is sent to the user terminal 10.

[0065] Next, the user operates the user terminal 10 to perform an action to acquire the reward (step S344). This action can be anything. For example, it may be a simple action such as selecting an image that says "Acquire a reward" displayed on an online medium. The various service servers 20 accept the reward acquisition action (step S345). The various service servers 20 determine whether the time of acceptance falls within the period during which the reward can be acquired. If it is not within the period during which the reward can be acquired, the user terminal 10 is notified accordingly. The following explanation will continue assuming that it is within the period during which the reward can be acquired. If it is within the period during which the reward can be acquired, the various service servers 20 register the user ID related to the accepted reward acquisition action in the storage unit.

[0066] Next, the various service servers 20 send the user ID to the point management server 30 and inquire about the external sales points associated with the user ID (step S346). In the point management server 30, the control unit 31 refers to the granted points management table 302 and calculates the total number of external sales points earned during a predetermined period associated with the transmitted user ID (for example, the period during which benefits can be earned, or six months prior to the acceptance of the action to earn a benefit). It then refers to the consumed points management table 303 and calculates the total number of external sales points consumed during the predetermined period associated with the user ID, and subtracts the total number of consumed external sales points from the total number of earned external sales points. Alternatively, the control unit 31 may calculate the total number of external sales points earned during the predetermined period without subtracting the total number of consumed external sales points. Once the external sales points are calculated, the control unit 31 sends the calculated number of external sales points to the various service servers 20 (step S347). When the various service servers 20 acquire external sales points, they determine the reward (step S348). For example, the various service servers 20 have a correspondence table 204 that associates external sales points with rewards, as illustrated in Figure 19. The various service servers 20 refer to the correspondence table 204 and decide to give the user a reward corresponding to the external sales points acquired from the point management server 30. Alternatively, the various service servers 20 may determine the reward by lottery. In that case, the probability of winning the lottery may be determined according to the external sales points, as illustrated in (a-2). The various service servers 20 register the determined reward in association with the user ID (step S349). The registration of the reward may be done with the various service servers 20, or it may be registered with the point management server 30 or a user management server (not shown). The various service servers 20 present (transmit) the details of the reward to the user terminal 10 (step S350). Note that the presentation of the reward can be omitted.

[0067] Furthermore, the actions required to earn rewards may be determined based on, for example, the user's usage of other services (purchase amount, frequency of use, etc.) or the user's usage of online media of other services (e.g., various transactions and experiences involving page views, impressions, clicks, installs, video viewing, etc.), or they may be arbitrary user actions (e.g., conversions) designated by external sales partners, service providers, or related entities.

[0068] (b) Calculate rewards based on the number of points used for external sales. Based on the total number of external sales points consumed (used) within a predetermined period, the control unit 31 decides to provide the following benefits: (b-1) Increase the number of points earned in the campaign to N times the normal amount as a benefit, (b-2) Increase the probability of winning in the lottery service compared to normal (by N times), (b-3) Provide benefits according to the number of external sales points used. An example of the processing for each of (b-1) to (b-3) will be explained below.

[0069] Regarding (b-1) Referring to Figure 20, an example of the process in (b-1) will be explained. The user operates the user terminal 10 to access the online medium (Web page) of the service that provides the benefits offered by the various service servers 20 (step S401). An example of a service that provides benefits is an e-commerce service. The various service servers 20 obtain the user ID of the user who accessed from the user terminal 10 (step S402). If the user is not logged in to the Web page, the various service servers 20 present the login screen for the e-commerce service, etc., and prompt the user to log in. If the user is already logged in, the various service servers 20 present the campaign details (step S403). For example, if the campaign details are that if the date on which an item is purchased in the e-commerce service falls within a specified period, the normal points for the purchase amount will be increased (for example, by +N times), the various service servers 20 present a screen 201, etc., showing the breakdown of points earned, as illustrated in Figure 14.

[0070] Meanwhile, the user performs an action on the e-commerce site that could potentially earn points, such as adding an item to their shopping cart (step S404). When such an action is performed, the various service servers 20 send the user ID to the point management server 30 and inquire about the number of external sales points used associated with the user ID (external sales points that will be used as the basis for calculating the points awarded in the campaign) (step S405). In the point management server 30, the control unit 31 refers to the consumption point management table 303 and extracts data where the value of the user ID field is the user ID obtained from the various service servers 20 and the value of the usage date and time field falls within a predetermined period (for example, the campaign period, or six months prior to the time of participation in the campaign). The control unit 31 calculates the total number of external sales points for the extracted data and uses this value as the basis for calculating the points awarded in the campaign. Once the number of external sales points used is calculated, the control unit 31 sends the calculated number of external sales points to the various service servers 20 (step S406).

[0071] The various service servers 20 calculate the number of regular points that can be awarded to the user based on the sales points obtained from the point management server 30, and present this to the user as points that can be earned in the campaign (step S407). The various service servers 20 have a correspondence table 202 between sales points and earned points, as illustrated in Figure 15. This table may be prepared for each campaign. The various service servers 20 refer to the correspondence table 202 and, when the number of sales points used obtained from the point management server 30 is applied to the sales point field in the correspondence table 202, obtain the earned point increase rate (+N times, +(N+1) times, +(N+2) times, etc.) corresponding to the range of sales points applied. The earned point increase rate may be calculated not in table format, but by a function f that outputs the earned point increase rate when sales points are input. For example, suppose the earned point increase rate is +N times. Also, suppose that the regular points awarded for the amount of items purchased by the user are, for example, 1% of the purchase amount. The various service servers 20 calculate the normal points to be awarded to the user by multiplying the total value of the items the user has placed in their shopping cart by (1 × N)%, which is the point redemption rate of 1% awarded to the user, and displaying the calculated number of points on the shopping cart screen, for example. When the user changes items in their shopping cart, the various service servers 20 calculate and display the points to be awarded to the user each time, based on the total value of the items in the shopping cart.

[0072] Next, the user operates the user terminal 10 to confirm an action that will earn points (step S408). For example, the user performs a purchase action for an item placed in the shopping cart. The various service servers 20 identify the number of points and user ID presented in step S407 and submit a request to the point management server 30 (step S409). The point management server 30 awards the user regular points in the same manner as the processes in steps S13 and S14 of Figure 9 (step S410).

[0073] While e-commerce services are used as an example here, the service conducting the campaign may be any other service. Furthermore, the online media in which the campaign is conducted may include online media provided by the various services, as well as online media linked to the services conducting the campaign. The conditions for awarding points based on the number of external sales points used may also be, in addition to or instead of the campaign period, for example, that points are awarded only if the location or store where the item transaction takes place meets specific conditions. Conditions other than item purchase may also be used, such as usage of other services (purchase amount, frequency of use, etc.), usage of other services' online media (e.g., various transactions and experiences involving page views, impressions, clicks, installs, video viewing, etc.), or arbitrary user actions specified by external sales partners, service providers, or related entities (e.g., conversions). Additionally, the campaign is not limited to online media; it may also be conducted in offline physical stores, etc.

[0074] Regarding (b-2) Referring to Figure 21, an example of the process in (b-2) is explained. The user operates the user terminal 10 to access the online medium (Web page) of a service linked to the lottery service by the various service servers 20 (step S421). The service linked to the lottery service may be any of the following: e-commerce service, payment service, communication service, usage reservation service, etc. The various service servers 20 obtain the user ID of the user who accessed from the user terminal 10 (step S422). If the user is not logged in to the Web page, the various service servers 20 present the login screen for the e-commerce service, etc., and prompt the user to log in. If the user is already logged in, the various service servers 20 present the lottery details (step S423). The lottery details may include information such as conditions such as the application period, eligibility requirements, and information on benefits such as points that can be obtained if the user wins. For example, when the user accesses the service linked to the lottery service, the lottery details may be displayed on the display unit of the user terminal 10 using a widget function, etc. Alternatively, the lottery service's functionality may be linked to the online media of each service via API integration, file integration, database integration, webhook integration, etc., and the system may be configured so that when the user terminal 10 logs in to the online media of each service, the lottery details are sent to the user terminal 10. Furthermore, the lottery details presented may be prepared for each service that the user first accesses.

[0075] Next, the user applies for the lottery by operating the user terminal 10 (step S424). The various service servers 20 accept the application for the lottery (step S425). The various service servers 20 determine whether the time of acceptance is within the application period. If it is not within the application period, the user terminal 10 is notified accordingly. The following explanation will continue assuming that it is within the application period. If it is within the application period, the various service servers 20 register the user ID that accepted the application as the applicant user in the storage unit. Alternatively, if it is within the application period, the various service servers 20 may issue a lottery number using a predetermined logic and send the issued lottery number to the user terminal 10. In this case, in the subsequent lottery, it will be determined whether the issued lottery number is a winning number or a losing number.

[0076] When it is time to execute the lottery (for example, a predetermined time such as one week after the end of the application period), the various service servers 20 decide to execute the lottery (step S426). Once the decision to execute the lottery is made, the various service servers 20 send the user ID to the point management server 30 and inquire about the number of external sales points used associated with the user ID (step S427). In the point management server 30, the control unit 31 refers to the consumed point management table 303 and calculates the total number of external sales points associated with the user ID consumed during a predetermined period (for example, the application period for the lottery, or six months prior to the time of application). Once the external sales points are calculated, the control unit 31 sends the calculated number of external sales points used to the various service servers 20 (step S428). Once the various service servers 20 have obtained the external sales points, they execute the lottery (step S429). The lottery is executed according to predetermined logic. For example, whether or not to win the lottery may be determined based on a predetermined winning probability. Each service server 20 has a correspondence table 203 between sales points and the rate of increase in winning probability, as illustrated in Figure 17. This table 203 may be prepared for each lottery. Each service server 20 refers to the correspondence table 203 and applies the number of sales points used obtained from the point management server 30 to the sales point field in the correspondence table 203 to obtain the rate of increase in winning probability (+10%, +20%, etc.) corresponding to the range of sales points applied. The rate of increase in winning probability may be calculated not in table format, but by a function f that outputs the rate of increase in winning probability when the number of sales points used is input. For example, suppose the original predetermined winning probability is 10%, and the rate of increase in winning probability according to the number of sales points used is +10%. Then, each service server 20 executes the lottery with a winning probability of 20%. Users who have sales points will have a higher winning probability than users who do not have sales points. The various service servers 20 send the lottery results to the user terminal 10 (step S430).

[0077] Furthermore, the eligibility requirements for the lottery may be based on conditions other than the time period, such as awarding points only if the location or store where the item is traded meets specific conditions. Other conditions may also be based on usage of other services (purchase amount, frequency of use, etc.), usage of online media of other services (e.g., various transactions and experiences involving page views, impressions, clicks, installs, video viewing, etc.), or arbitrary user actions specified by external vendors, service providers, or related entities (e.g., conversions). Additionally, the lottery may be conducted offline, such as at physical stores, rather than being limited to online media.

[0078] Regarding (b-3) Referring to Figure 22, an example of the process in (b-3) is explained. The user operates the user terminal 10 to access the online medium (Web page) of a service linked to the reward service by the various service servers 20 (step S441). The service linked to the reward service may be any of the following: e-commerce service, payment service, communication service, reservation service, etc. The rewards provided by the reward service are usually points, lottery tickets, discount tickets, coupons, etc. The various service servers 20 obtain the user ID of the user who accessed from the user terminal 10 (step S442). If the user is not logged in to the Web page, the various service servers 20 present a login screen for the e-commerce service, etc., and prompt the user to log in. If the user is already logged in, the various service servers 20 activate the reward service (step S443). For example, when a user accesses a service linked to the reward service, information prompting participation in an online event to obtain rewards may be displayed on the display of the user terminal 10 using a widget function, etc. Alternatively, the rewards service may be configured to be linked to the online media of each service via API integration, file integration, database integration, webhook integration, etc., so that when the user terminal 10 logs in to the online media of each service, information prompting participation in online events, etc., to obtain rewards is sent to the user terminal 10.

[0079] Next, the user operates the user terminal 10 to perform an action to acquire the reward (step S444). This action can be anything. For example, it may be a simple action such as selecting an image that says "Acquire a reward" displayed on an online medium. The various service servers 20 accept the reward acquisition action (step S445). The various service servers 20 determine whether the time of acceptance falls within the period during which the reward can be acquired. If it is not within the period during which the reward can be acquired, the user terminal 10 is notified accordingly. The following explanation will continue assuming that it is within the period during which the reward can be acquired. If it is within the period during which the reward can be acquired, the various service servers 20 register the user ID related to the accepted reward acquisition action in the storage unit.

[0080] Next, the various service servers 20 send the user ID to the point management server 30 and inquire about the number of external sales points used associated with the user ID (step S446). In the point management server 30, the control unit 31 refers to the consumption point management table 303 and calculates the total number of external sales points used during a predetermined period associated with the transmitted user ID (for example, the period during which the reward can be obtained, or six months prior to the time when the action to obtain the reward was accepted). Once the number of external sales points used is calculated, the control unit 31 sends the calculated number of external sales points used to the various service servers 20 (step S447). Once the various service servers 20 obtain the number of external sales points used, they determine the reward (step S448). For example, the various service servers 20 have a correspondence table 204 that associates the relationship between external sales points and rewards, as illustrated in Figure 20. The various service servers 20 refer to the correspondence table 204 and, when they apply the number of external sales points used obtained from the point management server 30 to the external sales point field in the correspondence table 204, they decide to give the user a reward corresponding to the range of external sales points applied. Alternatively, the various service servers 20 may determine the reward by lottery. In that case, the probability of winning the lottery may be determined according to the number of external sales points used, as illustrated in (b-2). The various service servers 20 register the determined reward in association with the user ID (step S449). The registration of the reward may be done with the various service servers 20, or it may be registered with the point management server 30 or a user management server (not shown). The various service servers 20 present (transmit) the details of the reward to the user terminal 10 (step S450). Note that the presentation of the reward can be omitted.

[0081] The actions required to earn rewards may be determined, for example, based on usage of other services (purchase amount, frequency of use, etc.) or usage of online media of other services (e.g., various transactions and experiences involving page views, impressions, clicks, installs, video viewing, etc.), or they may be arbitrary user actions (e.g., conversions) designated by external sales partners, service providers, or related entities.

[0082] (c) If the points used for external sales are from the store or other external retailer that issued the points, then the benefits will be provided. If the store where the user used the external sales points (store ID in the points consumption management table 303) is registered as an external sales partner store in the table of stores affiliated with external sales partners stored in the storage unit 34, and the external sales partner related to that store is included in the sources of the external sales points held by the user, then the control unit 31 decides to provide the user with a benefit based on one of the processes (c-1) to (c-3) described below, according to the total amount of external sales points used at that store during a predetermined period. The source of the external sales points is the business operator that issued the external sales code that was the basis for the external sales points when the user acquired the external sales points. For example, a user α obtains an external sales code issued by business operator B1 and acquires 1000 points as external sales points associated with that external sales code. The same user α obtains an external sales code issued by another business operator B2 and acquires 2000 points as external sales points associated with that external sales code. When user α uses external sales points at a store of business operator B1 or business operator B2, the system provides benefits commensurate with the number of points used. For example, even if user α uses more than 1000 external sales points at a store of business operator B1, with business operator B1 as the requesting party, the system may provide benefits commensurate with the points used, up to a maximum of 1000 external sales points earned through business operator B1.

[0083] Regarding (c-1) Referring to Figure 23, an example of the process in (c-1) is explained. The user operates the user terminal 10 to access the online medium (Web page) of the service that provides the benefits offered by the various service servers 20 (step S501). An example of a service that provides benefits is an e-commerce service. The various service servers 20 obtain the user ID of the user who accessed from the user terminal 10 (step S502). If the user is not logged in to the Web page, the various service servers 20 present the login screen for the e-commerce service, etc., and prompt the user to log in. If the user is already logged in, the various service servers 20 present the campaign details (step S503). For example, if the campaign details are that if the date on which an item is purchased in the e-commerce service falls within a specified period, the normal points for the purchase amount will be increased (for example, by +N times), the various service servers 20 present a screen 205, etc., showing the breakdown of points earned, as illustrated in Figure 24.

[0084] Meanwhile, the user performs an action on the e-commerce site that could potentially earn points, such as adding an item to their shopping cart (step S504). When such an action is performed, the various service servers 20 send the user ID and the store ID of the store where the user added the item to their shopping cart to the point management server 30 and inquire about the number of external sales points used at the point-granting store associated with the user ID (external sales points that serve as the basis for calculating the points to be awarded in the campaign) (step S505). In the point management server 30, the control unit 31 refers to the table 206, which contains the stores affiliated with the external sales partners as illustrated in Figure 25, and obtains the external sales partner ID to which the store ID obtained from the various service servers 20 belongs. Next, the control unit 31 refers to the awarded points management table 302 and extracts data in which the value of the user ID field is the user ID obtained from the various service servers 20, the value of the external sales partner ID field is the external sales partner ID obtained from table 206, and the value of the acquisition date and time field is within a predetermined period (for example, the campaign period, or six months prior to the time of participation in the campaign). If no data meeting these conditions can be extracted, 0 points are sent to the various service servers 20 (step S506).

[0085] If data that satisfies the conditions can be extracted, the control unit 31 refers to the consumption point management table 303 and extracts data in which the value of the user ID field is a user ID obtained from the various service servers 20, the value of the store ID field is a store ID obtained from the various service servers 20, and the value of the usage date and time field is within a predetermined period (for example, the campaign period, or six months prior to the time of participation in the campaign). The control unit 31 calculates the total number of external sales points for the extracted data and uses this value as the basis for calculating the points to be awarded in the campaign. At this time, in addition to the total number of external sales points used at the store with the store ID, the control unit 31 may also calculate the total number of external sales points used by the user during the predetermined period, in the same manner as in step S406 of (b-1). Alternatively, instead of calculating the total number of external sales points used at the store with the store ID, the control unit 31 may calculate the total number of external sales points used by the user at all stores affiliated with the external sales destination ID obtained from table 206 during the predetermined period. When the control unit 31 calculates the number of external sales points used at the issuing store, it sends the calculated number of external sales points to the various service servers 20 (step S506). If the total number of external sales points used during a predetermined period is calculated, the control unit 31 may send the total number of external sales points used by the user during the predetermined period in addition to the external sales points used at the issuing store.

[0086] The various service servers 20 calculate the number of regular points that can be awarded to the user based on the external sales points obtained from the point management server 30, and present this to the user as points that can be earned in the campaign (step S507). The various service servers 20 have a correspondence table 207 between the number of external sales points used at the point-issuing store and the point increase rate, as illustrated in Figure 26. This table may be prepared for each campaign. The various service servers 20 refer to the correspondence table 207 to obtain the point increase rate (+M times, +(M+1) times, +(M+2) times, etc.) corresponding to the number of external sales points used at the point-issuing store obtained from the point management server 30. The point increase rate may be calculated not in table format, but by a function f that outputs the point increase rate when external sales points are input. For example, suppose the point increase rate is +M times. Also, suppose that the regular points awarded for the amount of items purchased by the user are, for example, 1% of the purchase amount. The various service servers 20 calculate the normal points to be awarded to the user by multiplying the total value of the items the user has placed in their shopping cart by (1 × M)%, which is the point redemption rate of 1% that is given to the user, and displaying the calculated number of points on the shopping cart screen, for example.

[0087] Furthermore, if the total number of external sales points used during a specified period is transmitted in addition to the external sales points issued by the issuing store, the various service servers 20 refer to the correspondence table 202 illustrated in Figure 15 for the total number of external sales points used during the specified period. When the total number of external sales points used during the specified period obtained from the point management server 30 is applied to the external sales point field in the correspondence table 202, the server obtains the acquisition point increase rate (+N times, +(N+1) times, +(N+2) times, etc.) corresponding to the range of external sales points applied. For example, suppose the acquisition point increase rate corresponding to the number of external sales points used at the issuing store is +M times, the acquisition point increase rate corresponding to the total number of external sales points used during the specified period is +N times, and the normal points awarded for item purchases are 1% of the purchase amount. The various service servers 20 calculate the normal points to be awarded to the user by multiplying the total value of the items the user has placed in their shopping cart by (1 × M + N times)%, which is the point redemption rate of 1% awarded to the user, and displaying the calculated number of points on the shopping cart screen, for example. When the user changes items in their shopping cart, the various service servers 20 calculate and display the points to be awarded to the user each time, based on the total value of the items in the shopping cart.

[0088] Next, the user operates the user terminal 10 to confirm an action that will earn points (step S508). The various service servers 20 identify the number of points and user ID presented in step S507 and submit a request to the point management server 30 (step S509). The point management server 30 awards the user the normal points in the same manner as the processes in steps S13 and S14 of Figure 9 (step S510).

[0089] While e-commerce services are used as an example here, the service conducting the campaign may be any other service. Furthermore, the online media in which the campaign is conducted may include online media provided by the various services, as well as online media linked to the services conducting the campaign. The conditions for awarding points based on the number of external sales points used may also be, in addition to or instead of the campaign period, for example, that points are awarded only if the location or store where the item transaction takes place meets specific conditions. Conditions other than item purchase may also be used, such as usage of other services (purchase amount, frequency of use, etc.), usage of other services' online media (e.g., various transactions and experiences involving page views, impressions, clicks, installs, video viewing, etc.), or arbitrary user actions specified by external sales partners, service providers, or related entities (e.g., conversions). Additionally, the campaign is not limited to online media; it may also be conducted in offline physical stores, etc.

[0090] (c-2) Referring to Figure 27, an example of the process in (c-2) is explained. The user operates the user terminal 10 to access the online media (Web page) of a store that has a service linked to the lottery service via the various service servers 20 (step S521). The service linked to the lottery service may be any of the following: e-commerce service, payment service, communication service, reservation service, etc. The various service servers 20 obtain the user ID of the user who accessed from the user terminal 10 (step S522). If the user is not logged in to the Web page, the various service servers 20 present a login screen for the e-commerce service, etc., and prompt the user to log in. If the user is already logged in and has accessed a store, the various service servers 20 present the lottery details (step S523). The lottery details may include information such as conditions such as the application period, eligibility requirements, and information on benefits such as points that can be obtained if the user wins. For example, when the user accesses a service linked to the lottery service, the lottery details may be displayed on the display unit of the user terminal 10 using a widget function, etc. Alternatively, the lottery service's functionality may be linked to the online media of each service via API integration, file integration, database integration, webhook integration, etc., and the system may be configured so that when the user terminal 10 logs in to the online media of each service, the lottery details are sent to the user terminal 10. Furthermore, the lottery details presented may be prepared for each service that the user first accesses.

[0091] Next, the user applies for the lottery by operating the user terminal 10 (step S524). The various service servers 20 accept the application for the lottery (step S525). The various service servers 20 determine whether the time of acceptance is within the application period. If it is not within the application period, the user terminal 10 is notified accordingly. The following explanation will continue assuming that it is within the application period. If it is within the application period, the various service servers 20 register the user ID that accepted the application as the applicant user in the storage unit. Alternatively, if it is within the application period, the various service servers 20 may issue a lottery number using a predetermined logic and send the issued lottery number to the user terminal 10. In this case, in the subsequent lottery, it will be determined whether the issued lottery number is a winning number or a losing number.

[0092] When it is time to execute the lottery (for example, at a predetermined time such as one week after the end of the application period), the various service servers 20 decide to execute the lottery (step S526). Once the decision to execute the lottery is made, the various service servers 20 send the user ID and the store ID of the online media that the user was accessing when the lottery details were presented to the point management server 30, and inquire about the number of external sales points used at the issuing store associated with the user ID (step S527). In the point management server 30, the control unit 31 refers to the table 206 in which stores affiliated with external sales partners, as illustrated in Figure 25, are registered, and obtains the external sales partner ID to which the store ID obtained from the various service servers 20 belongs. Next, the control unit 31 refers to the points management table 302 and extracts data in which the value of the user ID field is a user ID obtained from the various service servers 20, the value of the external sales destination ID field is an external sales destination ID obtained from table 206, and the value of the acquisition date and time field falls within a predetermined period (for example, the period during which the lottery can be applied for, or six months prior to the time the lottery was applied for). If no data that satisfies these conditions can be extracted, 0 points are sent to the various service servers 20 (step S528).

[0093] If data that satisfies the conditions can be extracted, the control unit 31 refers to the consumption point management table 303 and extracts data in which the value of the user ID field is a user ID obtained from the various service servers 20, the value of the store ID field is a store ID obtained from the various service servers 20, and the value of the usage date and time field is included in a predetermined period, and calculates the total number of external sales points for the extracted data. At this time, in addition to the total number of external sales points used at the store with the store ID, the control unit 31 may also calculate the total number of external sales points used by the user during the predetermined period, in the same manner as in step S428 of (b-2). Alternatively, instead of calculating the total number of external sales points used at the store with the store ID, the control unit 31 may calculate the total number of external sales points used by the user at all stores affiliated with the external sales destination ID obtained from table 206 during the predetermined period. Once the number of external sales points used at the issuing store is calculated, the control unit 31 sends the calculated number of external sales points to the various service servers 20 (step S528). When the total number of external sales points used during a predetermined period is calculated, the control unit 31 may transmit the total number of external sales points used by the user during the predetermined period, in addition to the external sales points from the store that awarded the points.

[0094] When the various service servers 20 acquire external sales points, they execute a lottery (step S529). The lottery is executed according to a predetermined logic. For example, whether or not to win the lottery may be determined based on a predetermined winning probability. The various service servers 20 have a correspondence table 208 between the number of external sales points used at the point-issuing store and the rate of increase in the winning probability, as illustrated in Figure 28. This table 208 may be prepared for each lottery. The various service servers 20 refer to the correspondence table 208 to obtain the rate of increase in the winning probability corresponding to the number of external sales points used at the point-issuing store acquired from the point management server 30. The rate of increase in the winning probability may be calculated not in table format, but by a function f that outputs the rate of increase in the winning probability when external sales points are input. For example, suppose the original predetermined winning probability is 10%, and the rate of increase in the winning probability according to the number of external sales points used at the point-issuing store is +10%. Then, the various service servers 20 execute the lottery with a winning probability of 20%.

[0095] Furthermore, if the total number of external sales points used during a specified period is transmitted in addition to the external sales points issued at the issuing store, the various service servers 20 refer to the correspondence table 203 illustrated in Figure 17 for the total number of external sales points used during the specified period, and apply the total number of external sales points used during the specified period obtained from the point management server 30 to the external sales point field in the correspondence table 203 to obtain the rate of increase in the winning probability (+10%, +20%, etc.) corresponding to the range of external sales points applied. For example, suppose the original predetermined winning probability is 10%, the rate of increase in the winning probability according to the number of external sales points used at the issuing store is +10%, and the rate of increase in the winning probability according to the total number of external sales points used during the specified period is +10%. Then, the various service servers 20 execute the lottery with a winning probability of 30%. The various service servers 20 transmit the lottery results to the user terminal 10 (step S530).

[0096] Furthermore, the eligibility requirements for the lottery may be based on conditions other than the time period, such as awarding points only if the location or store where the item is traded meets specific conditions. Other conditions may also be based on usage of other services (purchase amount, frequency of use, etc.), usage of online media of other services (e.g., various transactions and experiences involving page views, impressions, clicks, installs, video viewing, etc.), or arbitrary user actions specified by external vendors, service providers, or related entities (e.g., conversions). Additionally, the lottery may be conducted offline, such as at physical stores, rather than being limited to online media.

[0097] Regarding (c-3) Referring to Figure 29, an example of the process in (c-3) is explained. The user operates the user terminal 10 to access an online medium (Web page) of a store that has a service linked to the reward service via the various service servers 20 (step S541). The service linked to the reward service may be any of the following: e-commerce service, payment service, communication service, reservation service, etc. The rewards provided by the reward service are usually points, lottery tickets, discount tickets, coupons, etc. The various service servers 20 obtain the user ID of the user who accessed from the user terminal 10 (step S542). If the user is not logged in to the Web page, the various service servers 20 present a login screen for the e-commerce service, etc., and prompt the user to log in. If the user is already logged in and has accessed a store, the various service servers 20 activate the reward service (step S543). For example, when a user accesses a service linked to the reward service, information prompting participation in an online event to obtain rewards may be displayed on the display of the user terminal 10 using a widget function, etc. Alternatively, the rewards service may be configured to be linked to the online media of each service via API integration, file integration, database integration, webhook integration, etc., so that when the user terminal 10 logs in to the online media of each service, information prompting participation in online events, etc., to obtain rewards is sent to the user terminal 10.

[0098] Next, the user operates the user terminal 10 to perform an action to acquire the reward (step S544). This action can be anything. For example, it may be a simple action such as selecting an image that says "Acquire a reward" displayed on an online medium. The various service servers 20 accept the reward acquisition action (step S545). The various service servers 20 determine whether the time of acceptance falls within the period during which the reward can be acquired. If it is not within the period during which the reward can be acquired, the user terminal 10 is notified accordingly. The following explanation will continue assuming that it is within the period during which the reward can be acquired. If it is within the period during which the reward can be acquired, the various service servers 20 register the user ID related to the accepted reward acquisition action in the storage unit.

[0099] Next, the various service servers 20 send the store ID of the online store the user was accessing when the user ID and lottery details were presented to the point management server 30, and inquire about the number of external sales points used at the issuing store associated with the user ID (step S546). In the point management server 30, the control unit 31 refers to the table 206, which is registered with stores affiliated with external sales partners as illustrated in Figure 25, and obtains the external sales partner ID to which the store ID obtained from the various service servers 20 belongs. Next, the control unit 31 refers to the awarded point management table 302 and extracts data in which the value of the user ID field is the user ID obtained from the various service servers 20, the value of the external sales partner ID field is the external sales partner ID obtained from table 206, and the value of the acquisition date and time field is within a predetermined period (for example, the period during which the benefit can be acquired, or six months prior to the time the action to acquire the benefit was performed). If no data that satisfies these conditions can be extracted, 0 points are sent to the various service servers 20 (step S547).

[0100] If data that meets the conditions can be extracted, the control unit 31 refers to the consumption point management table 303 and extracts data in which the value of the user ID field is a user ID obtained from the various service servers 20, the value of the store ID field is a store ID obtained from the various service servers 20, and the value of the usage date and time field is included in a predetermined period, and calculates the total number of external sales points for the extracted data. At this time, in addition to the total number of external sales points used at the store with the store ID, the control unit 31 may also calculate the total number of external sales points used by the user during the predetermined period, in the same manner as in step S447 of (b-3). Alternatively, instead of calculating the total number of external sales points used at the store with the store ID, the control unit 31 may calculate the total number of external sales points used by the user at all stores affiliated with the external sales destination ID obtained from table 206 during the predetermined period. Once the number of external sales points used at the issuing store is calculated, the control unit 31 sends the calculated number of external sales points to the various service servers 20 (step S547). When the total number of external sales points used during a predetermined period is calculated, the control unit 31 may transmit the total number of external sales points used by the user during the predetermined period, in addition to the external sales points from the store that awarded the points.

[0101] The various service servers 20 determine the reward when they obtain the number of external sales points used at the issuing store (step S548). For example, the various service servers 20 have a correspondence table 209 that associates the number of external sales points used at the issuing store with the reward, as illustrated in Figure 30. The various service servers 20 refer to the correspondence table 209 and decide to give the user a reward corresponding to the number of external sales points used at the issuing store, which was obtained from the point management server 30. Alternatively, the various service servers 20 may determine the reward by lottery. In that case, the probability of winning the lottery may be determined according to the number of external sales points used at the issuing store, as illustrated in (c-2).

[0102] Furthermore, if the total number of external sales points used during a specified period is transmitted in addition to the external sales points awarded at the issuing store, the various service servers 20 refer to the correspondence table 204 exemplified in Figure 19 for the total number of external sales points used during the specified period. When the total number of external sales points used during the specified period obtained from the point management server 30 is applied to the external sales point field in the correspondence table 204, the service servers 20 obtain the benefits (benefit 1, benefit 2, ...) corresponding to the range of external sales points applied. The various service servers 20 decide to give the benefits obtained by referring to correspondence tables 204 and 209 to the user.

[0103] The various service servers 20 register the determined benefits in association with the user ID (step S549). The various service servers 20 present (transmit) the details of the benefits to the user terminal 10 (step S550). Note that the presentation of benefits can be omitted.

[0104] The actions required to earn rewards may be determined, for example, based on usage of other services (purchase amount, frequency of use, etc.) or usage of online media of other services (e.g., various transactions and experiences involving page views, impressions, clicks, installs, video viewing, etc.), or they may be arbitrary user actions (e.g., conversions) designated by external sales partners, service providers, or related entities.

[0105] (d) Benefits for participating in events related to external sales partners Rewards may be given according to the sales points earned through the flow illustrated in Figure 6B. For example, the control unit 31 decides to provide a reward to the user based on one of the processes (d-1) to (d-2) described below.

[0106] Regarding (d-1) Referring to Figure 31, an example of the process in (d-1) is explained. The user operates the user terminal 10 to access the online medium (Web page) of the service that is linked to the lottery service by the various service servers 20 (step S621). The various service servers 20 obtain the user ID of the user who accessed from the user terminal 10 (step S622). If the user is not logged in to the Web page, the various service servers 20 present a login screen for the EC service, etc., and prompt the user to log in. If the user is already logged in, the various service servers 20 present the lottery details (step S623).

[0107] Next, the user applies for the lottery by operating the user terminal 10 (step S624). The various service servers 20 accept the application for the lottery (step S625). The various service servers 20 determine whether the time of acceptance is within the application period. If it is not within the application period, the user terminal 10 is notified accordingly. The following explanation will continue assuming that it is within the application period. If it is within the application period, the various service servers 20 register the user ID that accepted the application as the applicant user in the storage unit. Alternatively, if it is within the application period, the various service servers 20 may issue a lottery number using a predetermined logic and send the issued lottery number to the user terminal 10. In this case, in the subsequent lottery, it will be determined whether the issued lottery number is a winning number or a losing number.

[0108] When it is time to execute the lottery (for example, a predetermined time such as one week after the end of the application period), the various service servers 20 decide to execute the lottery (step S626). Once the execution of the lottery is decided, the various service servers 20 send the user ID to the point management server 30 and inquire about the number of external sales points associated with the user ID and some event ID (step S627). In the point management server 30, the control unit 31 refers to the awarded points management table 302 and calculates the total number of external sales points that are associated with some event ID (the event ID field in the awarded points management table 302 is not blank) among the external sales points acquired during a predetermined period associated with the transmitted user ID (for example, the application period for the lottery, or six months prior to the time of application for the lottery). The control unit 31 then refers to the consumed points management table 303 and calculates the total number of external sales points that were consumed during the predetermined period associated with the user ID, and subtracts the total number of consumed external sales points from the total number of acquired external sales points. Alternatively, the control unit 31 may calculate the total number of external sales points associated with the user ID and any event ID acquired during the predetermined period without subtracting the total number of external sales points consumed during the predetermined period. Once the external sales points are calculated, the control unit 31 sends the calculated number of external sales points to the various service servers 20 (step S628).

[0109] When the various service servers 20 acquire external sales points, they execute a lottery (step S629). The lottery is executed according to a predetermined logic. For example, whether or not to win the lottery may be determined based on a predetermined winning probability. The various service servers 20 have a correspondence table 203 between external sales points and the rate of increase in winning probability, as illustrated in Figure 17. The various service servers 20 refer to the correspondence table 203 and, when they apply the number of external sales points acquired from the point management server 30 to the external sales point field in the correspondence table 203, they acquire the rate of increase in winning probability (+10%, +20%, etc.) corresponding to the range of external sales points applied. The rate of increase in winning probability may be calculated not in table format, but by a function f that outputs the rate of increase in winning probability when the number of external sales points used is input. For example, suppose the original predetermined winning probability is 10%, and the rate of increase in winning probability according to the number of external sales points used is +10%. Then, the various service servers 20 execute the lottery with a winning probability of 20%. The various service servers 20 send the lottery results to the user terminal 10 (step S630).

[0110] Furthermore, the eligibility requirements for the lottery may be based on conditions other than the time period, such as awarding points only if the location or store where the item is traded meets specific conditions. Other conditions may also be based on usage of other services (purchase amount, frequency of use, etc.), usage of online media of other services (e.g., various transactions and experiences involving page views, impressions, clicks, installs, video viewing, etc.), or arbitrary user actions specified by external vendors, service providers, or related entities (e.g., conversions). Additionally, the lottery may be conducted offline, such as at physical stores, rather than being limited to online media.

[0111] Regarding (d-3) Referring to Figure 32, an example of the process in (d-3) is explained. The user operates the user terminal 10 to access the online media (Web page) of the service linked to the reward service by the various service servers 20 (step S641). The various service servers 20 obtain the user ID of the user who accessed from the user terminal 10 (step S642). If the user is not logged in to the Web page, the various service servers 20 present a login screen for the EC service, etc., and prompt the user to log in. If the user is already logged in, the various service servers 20 activate the reward service (step S643).

[0112] Next, the user operates the user terminal 10 to perform an action to acquire a reward (step S644). The various service servers 20 accept the reward acquisition action (step S645). The various service servers 20 determine whether the time of acceptance falls within the period during which the reward can be acquired. If it is not within the period during which the reward can be acquired, the user terminal 10 is notified accordingly. The following explanation will continue assuming that it is within the period during which the reward can be acquired. If it is within the period during which the reward can be acquired, the various service servers 20 register the user ID related to the accepted reward acquisition action in the storage unit.

[0113] Next, the various service servers 20 send the user ID to the point management server 30 and inquire about the number of external sales points associated with the user ID and some event ID (step S646). In the point management server 30, the control unit 31 refers to the awarded points management table 302 and calculates the total number of external sales points that are associated with some event ID (the event ID field in the awarded points management table 302 is not blank) among the external sales points acquired during a predetermined period associated with the transmitted user ID (for example, the period during which lottery applications can be made, or six months prior to the time of application for the lottery). The control unit 31 then refers to the consumed points management table 303 and calculates the total number of external sales points that were consumed during the predetermined period associated with the user ID, and subtracts the total number of consumed external sales points from the total number of acquired external sales points. Alternatively, the control unit 31 may calculate the total number of external sales points acquired during the predetermined period associated with the user ID and some event ID without subtracting the total number of consumed external sales points during the predetermined period. Once the external sales points are calculated, the control unit 31 sends the calculated number of external sales points to the various service servers 20 (step S647).

[0114] The various service servers 20 determine the reward when they obtain the number of external sales points (step S648). For example, the various service servers 20 have a correspondence table 204 that associates the relationship between external sales points and rewards, as illustrated in Figure 20. The various service servers 20 refer to the correspondence table 204 and, when they apply the number of external sales points obtained from the point management server 30 to the external sales point field in the correspondence table 204, they determine to give the user a reward corresponding to the range of external sales points applied. Alternatively, the various service servers 20 may determine the reward by lottery. In that case, the probability of winning the lottery may be determined according to the number of external sales points, as illustrated in (d-1). The various service servers 20 register the determined reward in association with the user ID (step S649). The registration of the reward may be done with the various service servers 20, or it may be registered with the point management server 30 or a user management server (not shown). The various service servers 20 present (transmit) the details of the reward to the user terminal 10 (step S650). Please note that you may omit presenting the special offer.

[0115] The actions required to earn rewards may be determined, for example, based on usage of other services (purchase amount, frequency of use, etc.) or usage of online media of other services (e.g., various transactions and experiences involving page views, impressions, clicks, installs, video viewing, etc.), or they may be arbitrary user actions (e.g., conversions) designated by external sales partners, service providers, or related entities.

[0116] In (a-1) to (a-3) above, benefits are awarded based on the number of external sales points earned or held during a predetermined period. Benefits may also be awarded based on external sales points and other indicators. Other indicators include, for example, the user's service usage status (e.g., the number of services used in the point setting table 304 in Figure 5) and membership rank (e.g., the membership rank in the point setting table 304 in Figure 5). Figure 33 shows an example of a combination of external sales points and other indicators. Figure 33 is a diagram showing an example of a conversion table 210 for converting a combination of external sales points and other indicators into a single external sales point value. The conversion table 210 is stored in the storage unit 34 and can be used, for example, as follows. For example, if a user has earned or held 100 external sales points within a predetermined period and has used 4 services within the predetermined period, the control unit 31 refers to the conversion table 210 in step S307 and converts it to 1000 external sales points. Then, it provides the same benefits as a user who has earned or held 1000 external sales points within a predetermined period. Similarly, if a user has earned or holds 100 external sales points within a predetermined period and their membership rank is A, the control unit 31 refers to the conversion table 210 and converts them to 1000 external sales points. The control unit then provides the same benefits as a user who has earned or holds 1000 external sales points within a predetermined period. The same applies to step S329 of (a-2) and step S348 of (a-3).

[0117] Furthermore, in (b-1) to (b-3), benefits are awarded based on the number of external sales points used during a predetermined period, but benefits may also be awarded based on external sales points and other indicators. For example, if a user has used 200 external sales points during a predetermined period, used 3 services during the predetermined period, or has a membership rank of B, the control unit 31 will refer to the conversion table 210 in step S407 of (b-1), step S429 of (b-2), and step S448 of (b-3) to convert the user's external sales points to 1000. The control unit 31 will then provide the same benefits as a user who has used 1000 external sales points during the predetermined period.

[0118] Furthermore, in (c-1) to (c-3), the benefits are awarded based on the number of external sales points used at the issuing store during a predetermined period. However, benefits may also be awarded based on external sales points and other indicators. For example, if a user has used 300 external sales points at the issuing store during a predetermined period, and has used 2 services or has a membership rank of C, the control unit 31 refers to the conversion table 210 in step S507 of (c-1), step S529 of (c-2), and step S548 of (c-3) to convert the user to 1000 external sales points. The control unit then provides the same benefits as a user who has used 1000 external sales points at the issuing store during a predetermined period.

[0119] Furthermore, in (d-1) and (d-2), benefits are awarded based on sales points earned at events of external sales partners, but benefits may also be awarded based on sales points and other indicators. For example, if a user has earned 100 sales points at an external sales partner event, used 4 services within a predetermined period, or has a membership rank of A, the control unit 31 refers to the conversion table 210 in step S629 of (d-1) and step S648 of (d-2) to convert the sales points to 1000. The control unit then provides the same benefits as a user who has earned 1000 sales points at an external sales partner event.

[0120] Here, the number of services used and membership rank were given as examples of other indicators, but other indicator values ​​such as the total amount spent on each service during a predetermined period or the total number of item transactions may also be used. Furthermore, although the explanation described converting external sales points and other indicators into external sales points, tables such as a table associating external sales points, other indicators, and the rate of increase in acquired points, and a table associating external sales points, other indicators, and the rate of increase in winning probability, may be stored in the storage unit 34, and these tables may be used to provide users with benefits corresponding to external sales points and other indicators.

[0121] In addition, in (a) above, the benefits (a-1) to (a-3) are provided based on the sales points earned over a specified period. However, the content of the benefits may be further varied depending on the sales destination. For example, if two companies, B1 and B2, purchase sales codes from business A, and B1's purchase amount is larger than B2's, and user C1 earns sales points through B1's events, etc., while user C2 earns sales points through B2's events, etc., then the benefits that user C1 receives and the benefits that user C2 receives may be differentiated. The control unit 31 may refer to the points management table 302 under the conditions that the point acquisition date and time falls within a predetermined period T, the user ID is the ID of user C1, and the external sales destination ID is the ID of business operator B1. If the total value of the external sales points is greater than or equal to a predetermined value X, the control unit 31 may provide user C1 with a benefit such as the number of points that can be obtained from the campaign being N1 times the normal amount (N1>N2). Similarly, the control unit 31 may refer to the points management table 302 under the conditions that the point acquisition date and time falls within a predetermined period T, the user ID is the ID of user C2, and the external sales destination ID is the ID of business operator B2. If the total value of the external sales points is greater than or equal to a predetermined value X, the control unit 31 may provide user C2 with a benefit such as the number of points that can be obtained from the campaign being N2 times the normal amount (N1>N2).

[0122] (effect) As explained above, according to this embodiment, regular points awarded to users and external sales points can be managed separately. In other words, by managing external sales points separately from other points, each of the external sales points and regular points in a state where they can be used by each user, the portion of the points linked to the user that is external sales points can be separated and managed separately from regular points, even in terms of the manner in which benefits are provided. The manner in which external sales points are awarded and used can be precisely managed, taking into account the convenience of the point awarding source of the external sales destination other than the point issuer (business operator B). As a result, benefits (rewards) that focus on external sales points can be provided to users, and the motivation of users to acquire external sales points can be increased. By increasing the motivation to acquire external sales points, the customer acquisition effect of external sales points can be improved, which benefits the external sales destinations that purchase external sales points (external sales codes). As a result, the sale and use of external sales points can be promoted. External sales points can be used in the same way as regular points on various online services offered by business A, the issuer of external sales points (they may be equivalent to or better than regular points, as mentioned above). Therefore, business A can expect to stimulate user spending and increase new customers on its various services. Business B can use the appeal of points (including external sales points) to attract customers to its own transactions by utilizing external sales points. In other words, business A, as the issuer of external sales points, can support or subsidize the transaction activities of business B's users who utilize external sales points through external sales points. Furthermore, users to whom business B is awarded external sales points may be customers of business B, thus further supporting and subsidizing business B's transaction activities. In addition to managing external sales points and regular points separately, the total points (including any other points if applicable) that are combined should be managed in a way that is available for use by each user.This allows users to use all the points they have earned without having to be aware of the difference between points earned through external sales and regular points.

[0123] Figure 11 shows an example of the hardware configuration of a point management system according to an embodiment. The computer 900 includes a CPU 901, main memory 902, auxiliary memory 903, input / output interface 904, and communication interface 905. The user terminal 10, various service servers 20, point management server 30, external sales server 40, and store terminal 50 are implemented in the computer 900. The above-mentioned processes are stored in the auxiliary memory 903 in the form of programs. The CPU 901 reads the program from the auxiliary memory 903, expands it into the main memory 902, and executes the above processes according to the program. The CPU 901 also allocates a memory area in the main memory 902 according to the program. The CPU 901 also allocates a memory area in the auxiliary memory 903 to store the data being processed according to the program.

[0124] In at least one embodiment, the auxiliary storage device 903 is an example of a non-temporary tangible medium. Other examples of non-temporary tangible media include magnetic disks, magneto-optical disks, CD-ROMs, DVD-ROMs, semiconductor memory, etc., connected via the input / output interface 904. Furthermore, if this program is distributed to the computer 900 via a communication line, the computer 900 that receives the program may expand it into the main memory 902 and execute the above processing. The program may also be for the purpose of realizing some of the functions described above. Moreover, the program may be a so-called differential file (differential program) that realizes the above-mentioned functions in combination with other programs already stored in the auxiliary storage device 903.

[0125] Furthermore, it is possible to replace the components in the above-described embodiments with well-known components as appropriate, without departing from the spirit of the present invention. Also, the technical scope of this invention is not limited to the above-described embodiments, and various modifications can be made without departing from the spirit of the present invention.

[0126] Some or all of the above embodiments may be described as follows, but are not limited to the following:

[0127] (Note 1) A point management system comprising: an issuing means for issuing external sales codes, which are code information distributed to users by a point issuing business through other businesses, and external sales points, which are points associated with the said external sales code, for points exchangeable for a medium of value; an awarding means for awarding the external sales points associated with the said external sales code to the user by linking the user ID of the user who acquired the said external sales code with the external sales code ID of the said external sales code; a storage means for storing regular points, which are points awarded to the user by a point issuing business without linking them to the said user ID, as regular points that the user can use, linked to the said user ID; storing the external sales points awarded by the awarding means as external sales points that the user can use, linked to the said user ID; and storing the sum of the regular points and the external sales points as at least a portion of the points that the user can use, linked to the said user ID.

[0128] (Note 2) The point management system according to Appendix 1 further comprises: a transmission means for transmitting the external sales code issued by the issuing means from the server of the other business operator to the user terminal of the user, or transmitting it to the user terminal of the user; and a reception means for receiving the external sales code and the user ID of the user transmitted to the user terminal, wherein the assignment means links the user ID received by the reception means with the external sales code ID of the external sales code received by the reception means.

[0129] (Note 3) A point management system according to Appendix 1 or Appendix 2, further comprising: a transmission means for transmitting the external sales code issued by the issuing means to the user upon winning a lottery; and a reception means for receiving the external sales code transmitted to the user and the user ID of the user, wherein the assignment means links the user ID received by the reception means with the external sales code ID of the external sales code received by the reception means.

[0130] (Note 4) The point management system described in Appendix 3, wherein in the lottery, the number of points of the external sales points is determined, the transmission means transmits the external sales code associated with the determined number of points to the user, and the granting means grants the user the determined number of points of the external sales points.

[0131] (Note 5) A point management system according to any one of Appendix 1 to Appendix 4, further comprising a means for selecting to prioritize the use of external sales points when the user uses the points, wherein the means for using the points subtracts the number of external sales points used by the user from the number of external sales points granted to the user.

[0132] (Note 6) A point management system according to any one of Appendix 1 to Appendix 5, further comprising: when the user uses the points, the system accepts a selection of whether to use the regular points or the external sales points, and selects to prioritize the use of the accepted points, wherein the system subtracts the number of points used by the user from the number of accepted points granted to the user.

[0133] (Note 7) A point management system according to any one of Appendix 1 to Appendix 6, further comprising: a means for selecting to prioritize the use of external sales points when the store where the user uses the points is a store of the other business operator, wherein the means for selecting to prioritize the use of external sales points when the store where the user uses the points is a store of the other business operator, the number of external sales points used by the user is deducted from the number of external sales points granted to the user.

[0134] (Note 8) A point management system according to any one of Appendix 1 to Appendix 7, further comprising: a means for providing a predetermined benefit to the user according to the number of external sales points granted to the user or the number of external sales points held by the user.

[0135] (Note 9) With respect to the points awarded to the user in the campaign, the reward provision means awards the user points in proportion to the number of points of the external sales points as a reward, as described in Appendix 8 of the point management system.

[0136] (Note 10) The means for providing the aforementioned benefits is a point management system as described in Appendix 8, which increases the probability of winning the lottery in accordance with the number of points of the aforementioned external sales points.

[0137] (Note 11) The reward provision means is a point management system as described in Appendix 8, which provides the reward to the user by registering the reward corresponding to the number of points of the external sales points in association with the user ID.

[0138] (Note 12) A point management system according to any one of Appendix 1 to Appendix 11, further comprising a means for providing predetermined benefits to the user in accordance with the number of points used by the user for the external sales.

[0139] (Note 13) With respect to the points awarded to the user in the campaign, the reward provision means awards the user the points corresponding to the number of points used in the external sales campaign, as a reward, according to the point management system described in Appendix 12.

[0140] (Note 14) The means for providing the aforementioned benefits is a point management system as described in Appendix 12, which increases the probability of winning the lottery in accordance with the number of points used for external sales.

[0141] (Note 15) The reward provision means is a point management system as described in Appendix 12, which provides the reward to the user by registering the reward corresponding to the number of points used for external sales in association with the user ID.

[0142] (Note 16) A means for providing a predetermined benefit to the user in accordance with the number of points of the external sales points used by the user at the store of the other business operator, further comprising a point management system described in any one of the appendices 1 to 15.

[0143] (Note 17) A point management method comprising: a computer issuing external sales codes, which are code information distributed to users by a point issuing business through other businesses, and external sales points, which are points associated with the external sales codes, for points exchangeable for a medium of value; granting the external sales points associated with the external sales codes to the user by linking the user ID of the user who obtained the external sales code with the external sales code ID of the external sales code; storing the regular points, which are points granted to the user by the point issuing business without linking them to the external sales codes, as regular points usable by the user, linked to the user ID; storing the granted external sales points as external sales points usable by the user, linked to the user ID; and storing the sum of the regular points and the external sales points as at least a portion of the points usable by the user, linked to the user ID.

[0144] (Note 18) A program for causing a computer to function as: a means for issuing external sales codes, which are code information distributed to users by a point issuing business through other businesses, and external sales points, which are points associated with the external sales codes, for points exchangeable for a medium of value; a means for granting external sales points associated with the external sales codes to a user by linking the user ID of the user who acquired the external sales codes with the external sales code ID of the external sales codes; a means for storing regular points, which are points granted to a user by a point issuing business without linking them to the user ID, as regular points usable by the user, linked to the user ID; a means for storing the granted external sales points as external sales points usable by the user, linked to the user ID; and a means for storing the sum of the regular points and the external sales points as at least a portion of the points usable by the user, linked to the user ID. [Explanation of Symbols]

[0145] 1. Point Management System 10. User terminal 20. Various service servers 30... Point Management Server 31. Control Unit 32. External Sales Point Management Department 33..Regular Points Management Department 34...Storage section 40... External sales server 50...Store terminal 900... Computer 901···CPU 902...Main memory 903...Auxiliary storage device 904... Input / Output Interface 905...Communication Interface

Claims

1. Regarding points exchangeable for a medium of value, an issuing means for issuing an external sales code, which is code information distributed by the point issuing business to the user through another business, and external sales points, which are the points linked to the said external sales code. A granting means that grants the external sales points associated with the external sales code to the user by linking the user ID of the user who obtained the external sales code with the external sales code ID of the external sales code, A storage means that stores the regular points, which are points granted to the user by the point issuing business operator by linking them to the user ID without linking them to the external sales code, as regular points that the user can use, linked to the user ID; stores the external sales points granted by the granting means as external sales points that the user can use, linked to the user ID; and stores the sum of the regular points and the external sales points as at least a portion of the points that the user can use, linked to the user ID. A point management system equipped with the following features.

2. A transmission means that transmits the external sales code issued by the issuing means from the server of the other business operator to the user's user terminal, or transmits it to the user's user terminal. A receiving means for receiving the external sales code and the user ID of the user transmitted to the user terminal, Furthermore, The assignment means associates the user ID received by the receiving means with the external sales code ID of the external sales code received by the receiving means. The point management system according to claim 1.

3. A transmission means that transmits the external sales code issued by the issuing means to the user upon winning the lottery, A receiving means for receiving the external sales code and the user ID of the user transmitted to the user, Furthermore, The assignment means associates the user ID received by the receiving means with the external sales code ID of the external sales code received by the receiving means. A point management system according to claim 1 or claim 2.

4. In the aforementioned lottery, the number of points for the aforementioned external sales was determined by the winner. The transmission means transmits to the user the external sales code associated with the number of points won. The granting means grants the user the number of points that have been awarded as external sales points. The point management system according to claim 3.

5. When the user uses the points, a means of use that allows the user to choose to prioritize the use of the external sales points, Furthermore, The aforementioned means of use subtracts the number of points used by the user from the number of points granted to the user. A point management system according to claim 1 or claim 2.

6. When the user uses the points, the user is asked to choose whether to use the regular points or the points sold by external retailers, and the system selects to prioritize the use of the points chosen by the user. Furthermore, The aforementioned means of use subtracts the number of points used by the user from the number of points awarded to the user by the person who received the points. A point management system according to claim 1 or claim 2.

7. If the store where the user uses the points is a store of another business operator, a means of use to choose to prioritize the use of the external sales points, Furthermore, The aforementioned means of use, if the store where the user used the points is a store of another business operator, subtracts the number of external sales points used by the user from the number of external sales points awarded to the user. A point management system according to claim 1 or claim 2.

8. A reward-providing means that provides a predetermined reward to the user in accordance with the number of external sales points granted to the user or the number of external sales points held by the user. A point management system according to claim 1 or claim 2, further comprising:

9. Regarding the points awarded to the user in the campaign, The aforementioned reward provision means grants the user, as a reward, points corresponding to the number of points of the external sales points. The point management system according to claim 8.

10. The aforementioned means of providing the benefit increases the probability of winning the lottery in proportion to the number of points earned from the external sales, as the benefit. The point management system according to claim 8.

11. The reward provision means provides the reward to the user by registering the reward corresponding to the number of points of the external sales points in association with the user ID. The point management system according to claim 8.

12. A reward provision means that provides a predetermined reward to the user in accordance with the number of points used by the user from the external sales point system, A point management system according to claim 1 or claim 2, further comprising:

13. Regarding the points awarded to the user in the campaign, The aforementioned reward provision means grants the user points corresponding to the number of points used for the external sales, as the reward. The point management system according to claim 12.

14. The aforementioned means of providing the benefit increases the probability of winning the lottery in proportion to the number of points used for the external sales. The point management system according to claim 12.

15. The reward provision means provides the reward to the user by registering the reward corresponding to the number of points used in the external sales points and linking it to the user ID. The point management system according to claim 12.

16. A reward provision means that provides a predetermined reward to the user in accordance with the number of points the user has used at the store of the other business operator, The point management system according to claim 1 or claim 2, further comprising:

17. Computers Regarding points exchangeable for a medium of value, the issuing business of the points issues an external sales code, which is code information distributed to the user through another business, and the points linked to the external sales code, which is an external sales point. By linking the user ID of the user who obtained the external sales code with the external sales code ID of the external sales code, the external sales points associated with the external sales code are granted to the user. The business operator that issues the points stores the regular points that it has granted to the user by linking them to the user ID without linking them to the external sales code, and stores the granted external sales points as external sales points that the user can use, and stores the total value of the regular points and the external sales points as at least a portion of the points that the user can use, and stores it in association with the user ID. Point management methods.

18. Computers, Regarding points exchangeable for a medium of value, a means for issuing an external sales code, which is code information distributed by the point issuing business to the user through another business, and external sales points, which are the points linked to the external sales code. A means for granting the external sales points associated with the external sales code to the user by linking the user ID of the user who obtained the external sales code with the external sales code ID of the external sales code. A means for storing the regular points, which are points granted to the user by the point issuing business operator by linking them to the user ID without linking them to the external sales code, as regular points that the user can use, linked to the user ID; storing the granted external sales points as external sales points that the user can use, linked to the user ID; and storing the sum of the regular points and the external sales points as at least a portion of the points that the user can use, linked to the user ID. A program designed to function as such.

Images