JP2017228150A - Privilege management system, privilege management method and privilege management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a privilege management system, a privilege management method and a privilege management program for promoting use of a privilege which a user possesses.SOLUTION: A management server 20 comprises: a user information storage part 22 for storing user information for segmenting a user for every user; and a control part 21 which is connected to a point management server 40 which stores a privilege possession amount for every user, and manages a privilege of every user. The control part 21 performs segmentation of the user based on the user information stored in the user information storage part 22, then loans an amount of a privilege which a borrower user desires, to the borrower user, while determining a maturity date, according to the rank, in the privilege which a lender user possesses, then at the maturity date, repays the amount of the privilege which is loaned to the borrower user, to the lender user by collecting the privilege from the borrower user.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a privilege management system, a privilege management method, and a privilege management program for managing a privilege held by a user.

  Today, various efforts are being made to promote sales while continuing transactions with customers. For example, benefits (points, mileage, etc.) that can be used in the same manner as cash at the store are provided to customers who have purchased products or used services (see, for example, Patent Document 1). . In the technique described in this document, the valid period of points is calculated based on a transaction history with a customer.

  In addition, a point management apparatus for using points by lending and borrowing points by users has been studied (for example, see Patent Document 2). In the technique described in this document, point management information having a user identifier and a point, group management information having a group identifier and a user identifier, and borrowing information having a borrowed user identifier, a lending user identifier and point designation information. Use. Then, it is determined whether or not the group identifier associated with the borrowed user identifier and the loaned user identifier of the loan information are the same. In the same case, at least a part of the points associated with the lending user identifier included in the lending information is set as the user point indicated by the borrowing user identifier, and the borrowing user identifier, the lending user identifier, and the lending target Accumulate loan management information with points.

JP 2006-53812 A Japanese Patent Application Laid-Open No. 2015-232806

  In the technique described in Patent Literature 2, points (privileges) can be lent and borrowed between users. However, since it is assumed that the lending user and the borrowing user belong to the same group, it is difficult to utilize the benefits under various users in an open environment.

  This invention is made in order to solve the said problem, and provides the privilege management system, privilege management method, and privilege management program for performing financing using the privilege which the user has. is there.

  -The privilege management system which solves the said subject is the privilege which memorize | stored the possession amount of the privilege for every user, and the user information storage part which memorize | stored the user information for segmenting a user for every user A control unit is connected to the possession amount management unit and manages the user's benefits. Then, the control unit performs segmentation of the user based on the user information stored in the user information storage unit, determines a rank, and the privilege held by the lender user in the rank. Accordingly, the borrower user wants to borrow the amount of privilege desired by the borrower user by setting a repayment date, and collects the borrowed privilege amount from the borrower user on the repayment date, and uses the lender. Repay. Thereby, according to a user's rank, a privilege of a lender can be loaned to a borrower.

  In the privilege management system, it is preferable to determine a lender user who provides a loan to the borrower user according to the rank of the lender user. Thereby, even when there are many lenders, a lender can be determined in consideration of a lender's rank.

  -In the said privilege management system, it is preferable to determine the lender user who finances the said borrower user according to the effective period of the privilege of the said lender user. When the validity period is defined in the privilege, the longer the validity period, the higher the degree of freedom of use of the privilege. Thereby, a lender can be determined in consideration of the degree of freedom of the privilege.

  -In the said privilege management system, it is preferable to determine the interest rate at the time of repayment of the loaned privilege according to the rank of the said borrower user. Depending on the borrower, there may be risks such as default. Thereby, the interest rate can be determined in consideration of the risk.

-In the said privilege management system, it is preferable to acquire the utilization condition of a privilege for every user from the said privilege possession amount management part, and to determine a user's rank according to the said utilization condition. Thereby, a privilege balance can be estimated based on the utilization status of a privilege, and a rank can be determined.
-In the above privilege management system, when a loan is made from a lender user to a borrower user, a time-limited privilege exchange ticket is provided to the lender user and a privilege loaned from the borrower user is collected It is preferable to repay a privilege to the lender user based on the time-limited privilege exchange ticket. Thereby, even when there is a usage restriction on the privilege, the repayment of the loan can be managed using the privilege exchange ticket.

  According to the present invention, it is possible to promote the use of a privilege held by a user.

Explanatory drawing of the privilege management system of this embodiment. It is explanatory drawing of the data recorded on the information storage part of this embodiment, Comprising: (a) is a user information storage part, (b) is explanatory drawing of a loan information storage part. It is explanatory drawing of the process sequence of this embodiment, Comprising: (a) is user registration processing, (b) is lender registration processing, (c) is explanatory drawing of borrower registration processing. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of other embodiment.

  Hereinafter, an embodiment in which a privilege management system, a privilege management method, and a privilege management program are embodied will be described with reference to FIGS. In the present embodiment, it is assumed that a service provider (platformer) provides a service that lends points (privileges) held by a lender who is a point member and mediates a loan to another borrower who is a point member. To do.

As shown in FIG. 1, in this embodiment, a user terminal 10, a management server 20, a bank server 30, and a point management server 40 connected via a network are used.
The user terminal 10 is a computer terminal used by users (lenders and borrowers) who use this service. The user terminal 10 includes a control unit, a storage unit, an input unit including a keyboard and a pointing device, and an output unit including a display.

  The management server 20 is a computer system of a service provider that mediates loan of points from a lender to a borrower. The management server 20 includes a control unit 21, a user information storage unit 22, and a loan information storage unit 23.

  The control unit 21 includes a control unit such as a CPU (not shown), and a memory such as a RAM and a ROM, and will be described later (each process such as a user registration stage, a segmentation stage, a use acceptance stage, a matching stage, and a loan management stage). To do. And the control part 21 functions as the user registration part 211, the segmentation part 212, the use reception part 213, the matching part 214, and the loan management part 215 by executing a privilege management program.

The user registration unit 211 executes a registration process for users who are lenders and borrowers.
The segmenting unit 212 performs a process of determining a rank by segmenting users (lenders and borrowers). This segmenting unit 212 holds data relating to a credit model for calculating a default risk (default rate) based on bank customer information held by a bank and purchase information held by a point service provider. . The segmenting unit 212 holds a rank determination table for determining a lender rank and a borrower rank according to the calculated default rate.

The use reception unit 213 executes processing for receiving an application for lending points and an application for borrowing from the user.
The matching unit 214 performs matching between the loan application and the borrowing application, and executes a process of determining a point loan destination.
The loan management unit 215 executes a process of managing the collection of the loaned points while financing the borrower's points to the borrower.

  As shown in FIG. 2A, a user management record 220 for managing users (lenders and borrowers) is recorded in the user information storage unit 22. Furthermore, a lender management record 221 and a borrower management record 222 are recorded in the user management record 220 in association with each other.

  The user management record 220 is recorded when the user registration of this service is performed. In the user management record 220, data related to a user code, a bank customer code, a point member code, a family situation, and user attributes are recorded.

Data relating to an identifier for specifying each user is recorded in the user code data area.
In the bank customer code data area, data relating to an identifier for identifying the user is recorded in the bank server 30. By using this bank customer code, the bank server 30 can acquire the user's bank account and bank transaction information.

  In the point member code area, data relating to an identifier for identifying the user (point member) in the point management server 40 is recorded. By using this point member code, the point management server 40 can acquire purchase information when points are acquired.

In the family status data area, data for specifying the family status (for example, the presence / absence of marriage, the presence / absence of children, etc.) of the user is recorded.
In the user attribute data area, data for specifying an attribute (for example, sex, work place, etc.) of the user is recorded.

  The lender management record 221 is recorded when an application for lending points owned by the user is accepted. In this lender management record 221, data relating to lender rank, lending capacity, lending period, and lending rate are recorded.

  In the lender rank data area, data relating to an identifier for specifying a segment to which a user belongs (rank as a lender) is recorded. The lender rank is a value obtained by evaluating the superiority as a lender. In this embodiment, the calculation is performed using a credit model using deposit / withdrawal information, deposit asset information, and the like.

Data relating to the number of points that can be lent by the lender is recorded in the rentable amount data area.
In the lending available period data area, data relating to lending periods (starting and ending) are recorded in the lender.
In the lending interest rate data area, data relating to the interest rate when renting points is recorded.

  The borrower management record 222 is recorded when an application for borrowing points owned by the user is accepted. In the borrower management record 222, data on the borrower rank and the maximum borrowable amount is recorded.

In the borrower rank data area, data relating to an identifier for identifying a segment (rank as a borrower) to which the user belongs is recorded. The borrower rank is a value obtained by evaluating the superiority as a borrower. In this embodiment, the calculation is performed using a credit model using deposit / withdrawal information, deposit asset information, and the like.
Data relating to the maximum number of points that can be borrowed by the borrower is recorded in the maximum borrowable amount data area. The maximum borrowable amount is determined using a table in which the maximum borrowable amount is associated with the borrower rank.

  As shown in FIG. 2B, the loan information storage unit 23 records a loan management record 230 for the loan of the lender's point to the borrower. The loan management record 230 is recorded when a point is loaned. In the loan management record 230, data relating to a lender code, a borrower code, a loan amount, a loan interest rate, a loan date, a repayment date, and a status are recorded.

In the lender code data area, data relating to a user code for identifying a lender who lent the loaned points is recorded.
In the borrower code data area, data relating to the user code for identifying the borrower of the loaned point is recorded.

In the loan amount data area, data relating to the number of points loaned by the lender to the borrower is recorded.
In the loan interest rate data area, data relating to the interest rate when collecting the loaned points is recorded.

In the loan date data area, data relating to the time (date) of the loan is recorded.
In the repayment date data area, data relating to the time (date) of collecting the loaned points is recorded.
In the status data area, data relating to a flag for specifying the status of the loan (during loan, collected) is recorded.

  A bank server 30 shown in FIG. 1 is a computer system that manages customer information and transaction information in a financial institution. The bank server 30 includes a customer information storage unit 32 and a transaction information storage unit 33.

  The customer information storage unit 32 stores customer management records for customers of financial institutions. The customer management record is recorded when a customer opens an account with a financial institution. In the customer management record, data related to the bank customer code, name, account identifier, contact information, address, customer attribute, and procedure history are recorded.

In the bank customer code data area, data relating to an identifier for identifying each customer of a financial institution is recorded.
In the name data area, data related to the customer's name is recorded.
In the account identifier data area, data relating to an identifier (main branch code, type code, account number, etc.) for specifying an account held by the customer is recorded.

In the contact address and address data area, data related to the customer's contact information (telephone number and the like) and address are recorded.
In the customer attribute data area, data relating to the customer attributes (age, gender, job type, etc.) is recorded.

  In the procedure history data area, data relating to the procedure status with the customer is recorded. For example, the transaction status (procedure date, procedure type) such as address change, family card issuance, and mortgage use is recorded.

  In the transaction information storage unit 33, a transaction management record for managing a transaction using an account opened by a customer is recorded. The transaction management record is registered when an account is opened at a financial institution. In this transaction management record, data relating to an account identifier, an account balance, and a transaction history is recorded.

Data relating to an identifier for identifying each account is recorded in the account identifier data area.
Data relating to the balance of this account is recorded in the account balance data area.
In the transaction history data area, data relating to transaction date / time, amount, summary, and location is recorded for transactions such as deposits and withdrawals in this account.

  The point management server 40 is a computer system that functions as a privilege holding amount management unit and manages points of point members. The point management server 40 manages the point balance of the point member who uses the point service and manages the allowance based on the point balance. The point management server 40 includes a member information storage unit 42 and a usage information storage unit 43.

  The member information storage unit 42 stores a member management record for point members who use the point service. The member management record is recorded when the member registration for the point service is performed. In the customer management record, data relating to the point member code, name, contact information, registration date, and point balance are recorded.

In the point member code data area, data relating to an identifier for identifying a point member is recorded.
In the name data area, data on the name of the point member is recorded.
In the contact data area, data relating to the contact information (email address, etc.) of the point member is recorded.

In the registration date data area, data relating to the time (year / month / day) when the point member was registered is recorded.
In the point balance data area, data relating to the number of points held by the point member is recorded.

  In the usage information storage unit 43, a usage management record regarding the use of points in the point service is recorded. The usage management record is recorded when points are used (acquired or used). In the use management record, data relating to the point member code, the use date, the use store, the use amount, and the use contents are recorded.

In the point member code data area, data relating to an identifier for identifying a point member is recorded.
In the use date data area, data relating to the time (year / month / day) when the point is used (acquired or used) is recorded.
In the use store data area, data related to stores using points is recorded.
Data relating to the number of points used in this store is recorded in the usage amount data area.
In the use content data area, data related to purchase content when using points is recorded.

Next, processing performed using the above system will be described with reference to FIGS.
(User registration process)
First, user registration processing will be described with reference to FIG. When using this service, the user terminal 10 is used to access the management server 20.

  First, the control unit 21 of the management server 20 executes a user application acquisition process (step S1-1). Specifically, the user registration unit 211 of the control unit 21 outputs a user registration screen on the display of the user terminal 10. The user registration screen is provided with setting fields for inputting bank customer information registered in the bank server 30, point member information registered in the point management server 40, family status, and the like. And the user registration part 211 acquires the various information input in the user registration screen, and provides a user code. Then, the user registration unit 211 generates a user management record 220 including a user code, a bank customer code, a point member code, and a family situation, and records the user management record 220 in the user information storage unit 22.

  Next, the control unit 21 of the management server 20 executes user information acquisition processing (step S1-2). Specifically, the user registration unit 211 of the control unit 21 accesses the bank server 30 and acquires bank customer information from the customer information storage unit 32 and the transaction information storage unit 33. This bank customer information includes information regarding customer attributes, account balances, transaction histories, and the like. Furthermore, the user registration unit 211 accesses the point management server 40 and acquires the usage information of the point member's point service. This usage information includes information related to a usage management record (purchasing history) and the like recorded in the usage information storage unit 43.

  Next, the control unit 21 of the management server 20 executes a credit model application process (step S1-3). Specifically, the segmentation unit 212 of the control unit 21 calculates a default rate by applying a credit model to the bank customer information acquired from the bank server 30 and the purchase record information acquired from the point management server 40.

  Next, the control part 21 of the management server 20 performs a segmentation process (step S1-4). Specifically, the segmentation unit 212 of the control unit 21 determines the lender rank and the borrower rank based on the calculated default rate. Next, the segmenting unit 212 generates a lender management record 221 in which the lender rank is recorded, and records it in the user information storage unit 22. Further, the segmentation unit 212 generates a borrower management record 222 in which the borrower rank is recorded, and records it in the user information storage unit 22. Next, the segmenting unit 212 calculates the maximum borrowable amount based on the borrower rank, and records it in the borrower management record 222.

(Lender registration process)
Next, the lender registration process will be described with reference to FIG. A user (lender) who wants to lend his / her points accesses the management server 20 and performs lender registration.

  Here, the control unit 21 of the management server 20 executes a loan application acquisition process (step S2-1). Specifically, the user registration unit 211 of the control unit 21 outputs a lender registration screen on the display of the user terminal 10. This lender registration screen is provided with setting fields for the number of points that can be lent (the lent amount), the rentable period, and the loan interest rate for the loan. And the user registration part 211 acquires the information input in the lender registration screen.

  Next, the control unit 21 of the management server 20 executes lender information registration processing (step S2-2). Specifically, the use reception unit 213 of the control unit 21 records the acquired information in the lender management record 221 associated with the user management record 220.

(Borrower registration process)
Next, the borrower registration process will be described with reference to FIG. A user (borrower) who wants to borrow points accesses the management server 20 and performs borrower registration.

  Here, the control unit 21 of the management server 20 executes a borrowing application acquisition process (step S3-1). Specifically, the use receiving unit 213 of the control unit 21 outputs a borrower registration screen on the display of the user terminal 10. This borrower registration screen is provided with setting fields for the number of desired borrowing points (loan amount) and borrowing period. And the user registration part 211 acquires the information input in the borrower registration screen.

  Next, the control part 21 of the management server 20 performs a matching process (step S3-2). Specifically, the matching unit 214 of the control unit 21 specifies the loan interest rate based on the borrower rank. Next, the matching unit 214 specifies the lender management record 221 in which the loan interest rate specified based on the borrower rank, the loan interest rate corresponding to the borrowing period, and the lending available period are recorded. Next, the matching unit 214 specifies the number of points that can be lent (a lent amount) recorded in the specified lender management record 221. Here, when the matching unit 214 specifies a plurality of lender management records 221, the total number of points that can be lent is totaled. Then, the matching unit 214 determines that the loan is possible when the specified number of points that can be lent exceeds the number of desired borrowing points. In this case, the matching unit 214 specifies the lender management record 221 in order of increasing lender rank until the desired borrowing point number (loan amount) is reached.

  Next, the control part 21 of the management server 20 performs the determination process about whether financing is possible (step S3-3). Specifically, the matching unit 214 of the control unit 21 compares the specified number of lent points with the desired borrowing point number. Here, whether or not the loan is possible is determined based on a comparison between the number of points that can be lent and the number of desired borrowing points. If the desired number of borrowing points exceeds the maximum borrowable amount, it is determined that the loan is not possible.

  When the number of points that can be lent does not reach the desired number of borrowed points and it is determined that the loan is not possible (“NO” in step S3-3), the control unit 21 of the management server 20 executes a rejection process ( Step S3-4). Specifically, the matching unit 214 of the control unit 21 outputs a message indicating that financing cannot be performed to the user terminal 10 of the borrower.

  On the other hand, when the number of points that can be lent reaches the desired number of borrowed points and it is determined that the loan is possible ("YES" in step S3-3), the control unit 21 of the management server 20 executes the loan process. (Step S3-5). Specifically, the loan management unit 215 of the control unit 21 generates a loan management record 230 and records it in the loan information storage unit 23. In the loan management record 230, the user code (borrower code) of the borrower who desires the loan and the user code (lender code) of the lender management record 221 are recorded. Furthermore, the number of points lent by the lender in the loan is recorded as the loan amount. Further, the loan management unit 215 records the loan interest rate and the last day of the borrowing period as the repayment date.

  Next, the loan management unit 215 transmits a point transfer instruction to the point management server 40. The point transfer instruction includes data on the point member code of the transfer source (the lender), the point member code of the transfer destination (the borrower), and the point transfer amount (loan amount). The point management server 40 that has acquired the point transfer instruction subtracts the transfer amount from the point balance of the transfer source point member in the member information storage unit 42 and adds the transfer amount to the point balance of the transfer destination point member. Further, the point management server 40 generates a usage management record related to this point migration and records it in the usage information storage unit 43.

The lender uses the loaned points.
In this case, the point management server 40 executes point use processing (step S3-6). Specifically, the point management server 40 subtracts the usage amount from the point balance of the point member using the point service. Further, when the point member makes a new purchase, the point member obtains a point corresponding to the purchase. In this case, the acquired amount corresponding to the purchase is added to the point balance of the point member.

  Next, the point management server 40 executes a point allocation update process (step S3-7). Specifically, the point management server 40 updates the point allowance based on the changed point balance.

(Loan management processing)
Next, loan management processing will be described with reference to FIG. This process is executed periodically (for example, every day).

  First, the control unit 21 of the management server 20 executes a loan specifying process (step S4-1). Specifically, the loan management unit 215 of the control unit 21 specifies the loan management record 230 in which the loan flag is recorded in the loan information storage unit 23.

Then, the following processing is repeated for each loan for the specified loan management record 230.
Here, the control part 21 of the management server 20 performs the determination process about whether the repayment date has arrived (step S4-2). Specifically, the loan management unit 215 of the control unit 21 compares the repayment date recorded in the loan management record 230 with the current date. If the current date has reached the repayment date, it is determined that the repayment date has arrived.

  When it is determined that the repayment date has not arrived (in the case of “NO” in step S4-2), the control unit 21 of the management server 20 ends the processing for the loan management record 230.

  On the other hand, when it is determined that the repayment date has arrived (“YES” in step S4-2), the control unit 21 of the management server 20 executes a point balance acquisition process (step S4-3). Specifically, the loan management unit 215 of the control unit 21 specifies the user management record 220 in which the user code of the loan management record 230 is recorded, and acquires the point member code from the user management record 220. Next, the loan management unit 215 accesses the point management server 40 and acquires the point balance of this point member code (borrower).

  Next, the control part 21 of the management server 20 performs the determination process about whether point repayment is possible (step S4-4). Specifically, the loan management unit 215 of the control unit 21 calculates the number of withdrawal points based on the repayment amount (number of points) including interest calculated from the number of loan points and the interest rate, and the service use fee. And the loan management part 215 determines with point repayment being possible, when the borrower's point balance exceeds the number of withdrawal points.

  If it is determined that the points can be repaid (“YES” in step S4-4), the control unit 21 of the management server 20 executes a point repayment process (step S4-5). Specifically, the loan management unit 215 of the control unit 21 transmits a point transfer instruction to the point management server 40. Then, the loan management unit 215 records the repayment flag in the status data area of the loan management record 230. The point transfer instruction includes data regarding the point member code of the transfer source (borrower), the point member code of the transfer destination (lender), and the point transfer amount (number of loan points and interest). Furthermore, the data includes the point member code of the transfer source (borrower), the point member code of the transfer destination (service provider), and the point transfer amount (service usage fee). The point management server 40 that has acquired the point transfer instruction subtracts the transfer amount from the point balance of the transfer source point member in the member information storage unit 42 and adds the transfer amount to the point balance of the transfer destination point member. Then, the point management server 40 generates a usage management record related to this point migration and records it in the usage information storage unit 43.

  On the other hand, when the point balance is insufficient in the repayment amount and it is determined that the point repayment is impossible (“NO” in step S4-4), the control unit 21 of the management server 20 executes the point repayment process for the point balance. (Step S4-6). Specifically, the loan management unit 215 of the control unit 21 transmits a point transfer instruction to the point management server 40. The point transfer instruction includes data on the point member code of the transfer source (borrower), the point member code of the transfer destination (lender), and the point transfer amount (point balance of the borrower). The point management server 40 that has acquired the point transfer instruction subtracts the transfer amount from the point balance of the transfer source point member in the member information storage unit 42 and adds the transfer amount to the point balance of the transfer destination point member. Further, the point management server 40 generates a usage management record related to this point migration and records it in the usage information storage unit 43.

  Next, the control part 21 of the management server 20 performs a point conversion process (step S4-7). Specifically, the loan management unit 215 of the control unit 21 subtracts the borrower's point balance from the number of withdrawal points to calculate the remaining amount of withdrawal. Next, the loan management unit 215 acquires from the point management server 40 a conversion rate when paying points with cash. Then, the loan management unit 215 calculates a withdrawal amount (remaining repayment amount, service fee) according to the withdrawal residual amount using the acquired conversion rate.

  Next, the control part 21 of the management server 20 performs a cash repayment process (step S4-8). Specifically, the loan management unit 215 of the control unit 21 transmits a transfer instruction to the bank server 30. The transfer instruction includes the bank customer code of the transfer source (borrower), the bank customer code of the transfer destination (lender, service provider), and data related to the withdrawal amount. The bank server 30 that has acquired the transfer instruction deducts the withdrawal amount from the account balance of the source bank customer code, and deposits the repayment amount into the account balance of the destination bank customer code.

  Furthermore, the point management server 40 generates a transaction management record relating to the transfer and records it in the transaction information storage unit 33. When the transfer is completed, the loan management unit 215 records a repayment flag in the status data area of the loan management record 230.

As described above, according to the present embodiment, the following effects can be obtained.
(1) In this embodiment, the control unit 21 of the management server 20 executes a credit model application process (step S1-3) and a segmentation process (step S1-4). Thereby, a user can be evaluated and an appropriate loan can be performed.

  (2) In this embodiment, the control part 21 of the management server 20 performs a matching process (step S3-2). As a result, the lender holding the privilege and the borrower can be linked. Further, based on the ranks of lenders and borrowers, it is possible to lend in consideration of each situation.

  (3) In this embodiment, when it determines with financing possible (in the case of "YES" in step S3-3), the control part 21 of the management server 20 performs a financing process (step S3-5). Thereby, the privilege which the lender possesses can be financed to the borrower who wishes to use the privilege.

  (4) In this embodiment, when it is determined that the repayment date has arrived (in the case of “YES” in step S4-2), the control unit 21 of the management server 20 executes a point balance acquisition process (step S4). -3). And the control part 21 of the management server 20 performs the determination process about whether point repayment is possible (step S4-4). If it is determined that the points can be repaid (“YES” in step S4-4), the control unit 21 of the management server 20 executes a point repayment process (step S4-5). Thereby, the loaned points can be repaid with the points acquired thereafter.

  (5) In this embodiment, when it determines with point repayment being impossible (in the case of "NO" in step S4-2), the control part 21 of the management server 20 performs a point repayment process about a point balance (step S4- 6). Next, the control part 21 of the management server 20 performs a point conversion process (step S4-7) and a cash repayment process (step S4-8). Thereby, when the point balance is insufficient, it can be repaid with cash.

In addition, you may change the said embodiment into the following aspects.
In the above embodiment, the lender benefits (points) are loaned to the borrower. The benefits for financing are not limited to points. For example, a mileage provided when boarding an aircraft can be used as a privilege to be financed.

As shown in FIG. 5, when the lender who has acquired the mileage does not plan to use the mileage within the effective period, the renter is lent to the lender.
Specifically, the renter mileage is registered in the management server 20 by the lender registration process (step S5-1). Then, through the borrower registration process (step S5-2), the lender's mileage is given to the borrower who is scheduled to board the aircraft within the valid period of the lender's mileage and does not have the mileage necessary for the boarding schedule. To finance.

In this case, the borrower uses the loaned mileage to board the aircraft.
Thereafter, the borrower further boardes the aircraft and accumulates mileage. When the repayment date arrives, the mileage is paid back to the lender by the loan management process (step S5-3).

  Thereby, the lender can effectively utilize the mileage that is not scheduled to be used. In addition, a borrower who has insufficient mileage on hand can use the loaned mileage to board the aircraft.

  In addition, when borrowing a mileage to a borrower by the borrower registration process, a voucher with a time limit may be provided. This voucher with a time limit can be exchanged for mileage within a predetermined period after the repayment date for collecting the mileage from the borrower in the loan management process. By using this voucher with a time limit, the rented mileage can be collected after the repayment date.

  In the above embodiment, another point member is assumed as a borrower (finance destination). Loans are not limited to individuals. For example, it can be used for business investment such as crowdfunding. In this case, according to the lender's rank, preferential investment possible, investment destination selection, investment period, number of investments, number of investment points, etc. may be given preferential treatment. Furthermore, in the case of crowd funding, points may be repaid to the lender using products and services based on the investee business.

In the above embodiment, the control unit 21 of the management server 20 executes a matching process (step S3-2). In this case, depending on the validity period of the privilege (point), the loan destination, the lent amount, and the loan interest rate may be limited. For example, when the effective period is long, it is incorporated into an advantageous loan than when the effective period is short. Thereby, a privilege with a long effective period and a high degree of freedom can be effectively utilized.
Further, the lender may be determined based on the scheduled use date of the borrower and the validity period of the privilege. In this case, the control unit 21 of the management server 20 acquires the scheduled use date of the borrower's privilege in the borrowing application. Further, the control unit 21 acquires the valid period of the lent candidate point from the point management server 40. And the control part 21 matches a privilege use estimated date and a point effective period, and determines a lender in order with a short point effective period within a point effective period within a privilege effective date.

  In the above embodiment, the control unit 21 of the management server 20 executes segmentation processing (step S1-4). In this case, the lender rank and the borrower rank are determined using the default rate calculated by applying the credit model. The method for determining the lender rank and the borrower rank is not limited to using these pieces of information. For example, based on bank customer information and purchase information, for a lender, segmentation may be performed in which a user's assets and holding points are predicted and the rank is determined according to the prediction. For example, when a high point balance is expected based on purchase information, a high rank is assigned.

  In the above embodiment, the control unit 21 of the management server 20 executes a loan application acquisition process (step S2-1). Specifically, on the lender registration screen, the number of points that can be lent (amounts that can be lent), the rentable period, and the loan interest rate in the case of financing are set. Instead of this, the lending upper limit amount and the lending interest rate may be determined according to the lender rank. In this case, the higher the lender rank, the higher the maximum lending amount and the lending interest rate. For this purpose, the user registration unit 211 holds a lending condition table for determining the lending upper limit amount and the lending interest rate according to the lender rank. Then, the user registration unit 211 acquires a lent available amount from the user terminal 10 within the lent upper limit amount. Moreover, you may make it determine a loan interest according to the effective period of a privilege (point).

  -In above-mentioned embodiment, when it determines with the repayment date having arrived (in the case of "YES" in step S4-2), the control part 21 of the management server 20 performs a repayment process with a point or cash. Repayment methods are not limited to these. For example, when it is determined that point repayment is impossible (in the case of “NO” in step S4-4), the entire repayment amount may be repaid with cash.

  Moreover, you may make it repay by division. In this case, in the loan management record 230 of the loan information storage unit 23, the divided repayment amount is recorded for each divided repayment date. Moreover, you may enable it to carry out an early repayment.

  -In the said embodiment, the control part 21 of the management server 20 performs a cash repayment process (step S4-8). In this case, transfer in the bank server 30 is used. Cash repayment is not limited to transfer. For example, it is possible to use credit card payment. In this case, card information necessary for credit card payment is recorded in the user management record 220 of the user information storage unit 22.

  In the above embodiment, the loan management unit 215 of the control unit 21 calculates the withdrawal amount (point number) based on the number of loan points, the interest rate, and the service usage fee. The method of acquiring the service usage fee in the service provider is not limited to collection from the borrower's point balance. For example, you may make it collect | recover from the point provider which provides the point service.

  DESCRIPTION OF SYMBOLS 10 ... User terminal, 20 ... Management server, 21 ... Control part, 211 ... User registration part, 212 ... Segmentation part, 213 ... Usage reception part, 214 ... Matching part, 215 ... Loan management part, 22 ... User information Storage unit, 23 ... loan information storage unit, 30 ... bank server, 32 ... customer information storage unit, 33 ... transaction information storage unit, 40 ... point management server, 42 ... member information storage unit, 43 ... usage information storage unit.

Claims (8)

For each user, a user information storage unit that stores user information for segmenting users,
For each user, a privilege management system that is connected to a privilege holding amount management unit that stores a privilege holding amount and includes a control unit that manages a user's privilege,
The control unit is
Based on the user information stored in the user information storage unit, segment the user, determine the rank,
About the privilege held by the lender user, according to the rank, the borrower user wants to borrow the amount of privilege desired by setting a repayment date to the borrower user,
The privilege management system characterized in that on the repayment date, the loaned privilege amount is collected from the borrower user and is repaid to the lender user.   The privilege management system according to claim 1, wherein a lender user who provides a loan to a borrower user is determined according to a rank of the lender user.   The privilege management system according to claim 1 or 2, wherein a lender user who makes a loan to the borrower user is determined according to an effective period of the privilege of the lender user.   The privilege management system according to any one of claims 1 to 3, wherein an interest rate at the time of repayment of the loaned privilege is determined according to a rank of the borrower user.   The usage status of the privilege is acquired for each user from the privilege holding amount management unit, and the rank of the user is determined according to the usage status. The privilege management system described. When a loan is made from a lender user to a borrower user, a reward voucher with a time limit is provided to the lender user,
When the privilege loaned from the borrower user is collected, the privilege is repaid to the lender user based on the time-limited privilege exchange ticket. The privilege management system according to item. For each user, a user information storage unit that stores user information for segmenting users,
A method for performing privilege management using a privilege management system provided with a control unit that manages a privilege of a user, connected to a privilege possession amount management unit that stores the amount of privilege held for each user. ,
The control unit is
Based on the user information stored in the user information storage unit, segment the user, determine the rank,
About the privilege held by the lender user, according to the rank, the borrower user wants to borrow the amount of privilege desired by setting a repayment date to the borrower user,
A privilege management method characterized in that, on the repayment date, the loaned privilege amount is collected from the borrower user and repaid to the lender user. For each user, a user information storage unit that stores user information for segmenting users,
It is a program for performing privilege management using a privilege management system provided with a control unit that manages a privilege of a user, connected to a privilege possession amount management unit that stores a privilege amount for each user. ,
The control unit
Based on the user information stored in the user information storage unit, segment the user, determine the rank,
About the privilege held by the lender user, according to the rank, the borrower user wants to borrow the amount of privilege desired by setting a repayment date to the borrower user,
A privilege management program characterized in that, on the repayment date, the loaned privilege amount is collected from the borrower user and functions as means for repayment to the lender user.

Images