JP2017228151A - 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 capable of efficiently utilizing a privilege, and promoting selling using the privilege.SOLUTION: A privilege management system performs privilege management using a management server 20 comprising: a user information storage part 22 storing a privilege balance for every user; and a control part 21 for managing points of each user. The control part 21 provides an advance point to a user based on an advance request of the user, records an advance state in the user information storage part 22, then executes payment processing using the advance point. In a subsequent transaction, when it is determined that the advance point is recorded in the user information storage part 22, based on authentication of the user, repayment processing for subtracting the advance point, is executed, using points which are provided according to payment of the subsequent transaction.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 provided to 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 technique for making it possible to receive compensation for labor that has already been provided at any time has been studied (for example, see Patent Document 2). In the technique described in this document, a transfer table creation unit that stores a prepaid actual amount in association with an individual, a labor data input unit that inputs labor data indicating an individual's daily labor performance, A salary calculation unit that calculates a daily salary based on the work performance indicated by the data is used. Then, input the requested amount, obtain the total of the requested amount for a predetermined period, and obtain the total of the daily salary for a predetermined period calculated based on the labor performance indicated by the labor data indicating the individual labor performance To do. Then, a prepayable balance for the individual is determined based on the total of the requested amount and the daily salary, and whether the prepayment of the requested amount is determined based on the requested amount and the prepayable balance.

JP 2006-53812 A JP 2006-4263 A

  In the technique described in Patent Document 2, it is possible to borrow the value for labor already provided. However, privileges such as points are provided by transactions with users. Therefore, the privilege provided by the transaction varies depending on the transaction status of the user. In addition, if a transaction with a large amount of payment is performed after a transaction with a small amount of payment is performed first, it may be difficult to use a privilege granted in a later transaction.

  The present invention has been made in order to solve the above-described problems, and is capable of effectively utilizing the benefits, and a privilege management system, a privilege management method, and a privilege management program for promoting sales using the benefits. Is to provide.

  -The privilege management system which solves the said subject is provided with the control part which manages the user information storage part which memorize | stored the privilege balance for every user, and a user's privilege. The control unit provides a pre-borrowing benefit to the user based on a user's pre-borrowing request at the time of a prior transaction, records a pre-borrowing situation in the user information storage unit, and uses the pre-borrowing privilege. When payment processing is executed and it is determined that a pre-borrowing benefit is recorded in the user information storage unit based on user authentication in the subsequent transaction, the payment is provided in accordance with the payment of the subsequent transaction. A repayment process for subtracting the advance borrowing privilege is executed using the privilege. Thereby, a privilege can be borrowed beforehand at the time of a preceding transaction, and the privilege borrowed previously can be repaid in a subsequent transaction. Therefore, the user can effectively use the privilege and can promote sales using the privilege.

  The above privilege management system preferably further includes a transaction information storage unit that records transaction history information for each user, and based on the transaction history information, it is preferable to determine whether or not the advance borrowing privilege can be provided. Thereby, the propriety of borrowing can be determined according to the transaction status.

  In the privilege management system, it is preferable that the control unit obtains information related to the bank transaction of the user and determines whether or not to provide a pre-borrow privilege based on the information related to the bank transaction. Thereby, it is possible to determine whether or not advance borrowing is possible in accordance with information related to bank transactions.

In the privilege management system, the control unit performs segmentation to determine a user rank for each user, determines a pre-borrowing condition based on the user rank, and pre-borrows based on the pre-borrowing condition It is preferable to provide a privilege. Thereby, according to a user situation, a borrowing condition can be determined.
-In the said privilege management system, it is preferable to determine the advance borrowing upper limit as said advance borrowing conditions. Thereby, the advance borrowing upper limit can be determined according to the user situation.

  According to the present invention, it is possible to effectively use a privilege and to promote sales using the privilege.

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 sales information storage part. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this 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 store (seller) that provides points (privileges) provides a service that allows borrowing of points in advance.

As shown in FIG. 1, in this embodiment, a store terminal 10 and a management server 20 connected via a network are used. Furthermore, the management server 20 is connected to the bank server 30.
The store terminal 10 is a computer terminal that is installed at a store front and performs settlement of goods and the like. The shop terminal 10 includes an input unit including a control unit, a storage unit, a key operation unit, and an output unit including a display.

  The management server 20 is a computer system that manages settlement at a store. The management server 20 includes a control unit 21, a user information storage unit 22, and a sales 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 processes described later (user management stage, transaction management stage, point management stage, loan management stage, accounting management stage, etc.) Etc.). And the control part 21 functions as the user management part 211, the transaction management part 212, the point management part 213, the loan management part 214, and the accounting management part 215 by executing the privilege management program.

  The user management unit 211 executes processing for managing users (point members) in this store. The user management unit 211 performs user segmentation based on the user information and assigns a user rank. In the present embodiment, the user rank is determined based on the default rate of the user. Further, the user management unit 211 performs user authentication of point members based on the membership card.

The transaction management unit 212 executes a settlement process for transactions (sales of merchandise) in the store.
The point management unit 213 executes processing for managing user points. The point management unit 213 holds information for calculating the number of points provided to the user according to the payment amount.

The loan management unit 214 executes a process for managing the advance borrowing of points for the user. The loan management unit 214 holds a condition determination table for calculating the advance borrowing condition (the number of points as the advance borrowing upper limit) according to the user rank. In this condition determination table, a higher advance borrowing limit is set as the user rank is higher. Then, the loan management unit 214 permits the advance borrowing of points within the advance borrowing upper limit.
The accounting management unit 215 executes processing for managing accounting of a store (seller). Therefore, the accounting management unit 215 includes an accounting management memory. Information relating to the financial statements including the balance sheet is recorded in the accounting management memory. In the present embodiment, the accounting management unit 215 executes the allocation process in the balance sheet for the points provided to the user.

  As shown in FIG. 2A, the user information storage unit 22 stores a user management record 220 for managing point members who use the point service. The user management record 220 is recorded when a point member is registered. In the user management record 220, data relating to a user code, a bank customer code, a user attribute, a user rank, a point balance, and a state of advance borrowing are recorded.

Data relating to an identifier for identifying each point member 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 user attribute data area, data relating to attribute information (name, sex, date of birth, address, etc.) of each point member is recorded.
In the user rank data area, data related to ranks calculated by segmenting each point member is recorded.

In the point balance data area, data relating to the user's point balance (number of points) is recorded.
In the advance borrowing status data area, data relating to the number of points borrowed by the user is recorded.

  As shown in FIG. 2B, the sales information storage unit 23 records a sales management record 230 for managing transactions in the store. The sales management record 230 is recorded when a transaction is performed at a store. In the sales management record 230, transaction code, transaction date, user code, and data regarding transaction contents are recorded.

Data relating to an identifier for specifying each transaction is recorded in the transaction code data area.
In the transaction date data area, data relating to the time (date and time) when the transaction was performed is recorded.

In the user code data area, data relating to an identifier for specifying the point member who has made this transaction is recorded.
In the transaction content data area, data relating to the transaction content (purchased products, quantity, transaction amount, number of used points, number of provided points, etc.) 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.

Next, processing performed using the above system will be described with reference to the drawings.
(Segmentation processing)
First, the segmentation process will be described with reference to FIG. This process is periodically executed for each point member.

  Here, the control part 21 of the management server 20 performs the acquisition process of user information (step S1-1). Specifically, the user management unit 211 of the control unit 21 acquires the bank customer code recorded in the user management record 220 to be segmented. Then, the bank server 30 is accessed, the bank customer information is acquired from the customer information storage unit 32 using the bank customer code, and the information associated with the account identifier of this information is acquired from 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 management unit 211 acquires transaction history information associated with the user code of the point member from the sales information storage unit 23.

  Next, the control unit 21 of the management server 20 executes rank registration processing (step S1-2). Specifically, the user management unit 211 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 transaction history information acquired from the sales information storage unit 23. To do. And the user management part 211 of the control part 21 determines a user rank with the calculated default rate. Here, a higher user rank is assigned as the default rate is lower. Then, the user management unit 211 records the determined user rank in the user management record 220.

(Payment support processing)
Next, payment support processing will be described with reference to FIG. This process is executed when the user pays for the purchased product at the store.

  First, the control unit 21 of the management server 20 executes a payment calculation process (step S2-1). Specifically, the transaction management unit 212 of the control unit 21 reads a product code for a user's purchase desired product. Then, the transaction management unit 212 specifies a sales price based on the product code and calculates a payment amount in a POS system (not shown).

  Next, the control part 21 of the management server 20 performs the determination process about whether it is a point member (step S2-2). Specifically, the store clerk requests the user to present a membership card. When receiving the membership card, the store terminal 10 reads the membership card. The user management unit 211 of the control unit 21 acquires the user code read from the member card. When the user management record 220 in which the acquired user code is recorded can be extracted from the user information storage unit 22, it is determined as a point member. On the other hand, if the member card is not presented or the user management record 220 in which the user code read from the member card cannot be extracted, it is determined that the user is not a point member.

  When it determines with not being a point member (in the case of "NO" in step S2-2), the control part 21 of the management server 20 performs a payment process (step S2-3). Specifically, the transaction management unit 212 of the control unit 21 waits for payment of the payment amount at the store terminal 10. When the payment amount is received at the store terminal 10, the transaction management unit 212 of the control unit 21 generates a sales management record 230, records it in the sales information storage unit 23, and ends the payment process. In this case, since it is not a point member, the user code is left blank.

  On the other hand, when it determines with a point member (in the case of "YES" in step S2-2), the control part 21 of the management server 20 performs the determination process about whether there is advance borrowing (step S2-4). Specifically, the loan management unit 214 of the control unit 21 determines whether or not the amount of advance borrowing is recorded in the state of advance borrowing of the extracted user management record 220. When the advance borrowing amount is not recorded in the user management record 220 (when the advance borrowing amount is “0”), it is determined that there is no advance borrowing.

  When it is determined that there is no advance borrowing (in the case of “NO” in step S2-4), the control unit 21 of the management server 20 executes a determination process as to whether or not advance borrowing is desired (step S2-5). Specifically, the store clerk confirms whether or not the user wants to borrow in advance. Then, the store clerk inputs the presence / absence of advance borrowing to the store terminal 10. In this case, the loan management unit 214 of the control unit 21 obtains the input of whether or not the desired borrowing is input.

  When it is determined that the advance borrowing is not desired (in the case of “NO” in step S2-5), the control unit 21 of the management server 20 executes a determination process as to whether or not the points are used (step S2-6). The store clerk confirms the handling of points to the user. Then, the store clerk inputs “use point” or “store point” to the store terminal 10. In this case, the point management unit 213 of the control unit 21 acquires the desired information regarding the input “point use” or “point accumulation”.

  When it is determined that points are used (in the case of “YES” in step S2-6), the control unit 21 of the management server 20 executes a determination process as to whether or not the points can be allocated (step S2-7). Specifically, the point management unit 213 of the control unit 21 acquires the point balance recorded in the extracted user management record 220. Then, the point management unit 213 compares the point balance with the payment amount. If there is a point balance greater than the payment amount, it is determined that the points can be used. On the other hand, when the point balance is less than the payment amount, it is determined that the points cannot be applied.

  When it is determined that points cannot be allocated (in the case of “NO” in step S2-7), the control unit 21 of the management server 20 executes a difference calculation process (step S2-8). Specifically, the point management unit 213 of the control unit 21 calculates the difference by subtracting the point balance from the payment amount.

  Next, the control part 21 of the management server 20 performs a payment process (step S2-9). Specifically, the transaction management unit 212 of the control unit 21 waits for payment of the difference at the store terminal 10. When the difference is deposited at the store terminal 10, the transaction management unit 212 of the control unit 21 generates a sales management record 230 and records it in the sales information storage unit 23.

  Next, the control part 21 of the management server 20 performs a point update process (step S2-10). Specifically, the point management unit 213 of the control unit 21 calculates the number of points to be provided to the user based on the deposited difference. Then, the point management unit 213 once resets the point balance of the user management record 220 and records the number of points calculated based on the difference as a new point balance.

  On the other hand, when it is determined that the points are not used (in the case of “NO” in step S2-6), the control unit 21 of the management server 20 determines whether or not the points can be allocated (step S2-7). The calculation process (step S2-8) is skipped and the payment process is executed (step S2-9). Specifically, the transaction management unit 212 of the control unit 21 waits for payment of the payment amount at the store terminal 10. When the payment amount is received at the store terminal 10, the transaction management unit 212 of the control unit 21 generates a sales management record 230 and records it in the sales information storage unit 23.

  And the control part 21 of the management server 20 performs a point update process (step S2-10). Specifically, the point management unit 213 of the control unit 21 calculates the number of points to be provided to the user based on the payment amount received. Then, the point management unit 213 adds the calculated number of points to the point balance of the user management record 220.

  In addition, when it is determined that the points can be applied (in the case of “YES” in step S2-7), the control unit 21 of the management server 20 skips the difference calculation process (step S2-8) and performs the payment process. Execute (Step S2-9). Here, the transaction management unit 212 of the control unit 21 generates a sales management record 230 as “payment amount = 0” and records it in the sales information storage unit 23.

  Next, the control part 21 of the management server 20 performs a point update process (step S2-10). Specifically, the point management unit 213 of the control unit 21 subtracts the number of points corresponding to the payment amount from the point balance of the user management record 220.

  Next, the control unit 21 of the management server 20 executes an allocation process (step S2-11). Specifically, the transaction management unit 212 of the control unit 21 calculates the allowance based on the point balance updated in the user information storage unit 22 and records it on the balance sheet of the accounting management memory.

  Further, when it is determined that advance borrowing is desired (in the case of “YES” in step S2-5), the control unit 21 of the management server 20 executes a determination process as to whether or not advance borrowing is possible (step S2-12). Specifically, the store clerk confirms the number of points desired to borrow in advance (the number of desired points) from the user. Then, the clerk inputs the desired number of points to the store terminal 10 by the user. In this case, the loan management unit 214 of the control unit 21 calculates the advance borrowing upper limit based on the user rank recorded in the user management record 220. Next, the loan management unit 214 compares the number of desired points with the previous borrowing upper limit. When the desired number of points is equal to or less than the upper limit of advance borrowing, it is determined that advance borrowing is possible.

  If it is determined that advance borrowing is possible ("YES" in step S2-12), the control unit 21 of the management server 20 executes advance borrow registration processing (step S2-13). Specifically, the loan management unit 214 of the control unit 21 records the desired number of points as the number of advance borrowing in the advance borrowing status of the user management record 220. Then, the loan management unit 214 adds the number of previous borrowed points to the point balance.

Similarly to step S2-7, the control unit 21 of the management server 20 executes a determination process as to whether or not the points can be allocated (step S2-14).
When it is determined that points cannot be applied (in the case of “NO” in step S2-14), the control unit 21 of the management server 20 performs a difference calculation process (step S2-15). Specifically, the point management unit 213 of the control unit 21 calculates the difference by subtracting the point balance from the payment amount.

  Next, the control part 21 of the management server 20 performs a payment process (step S2-16). Specifically, the transaction management unit 212 of the control unit 21 waits for payment of the difference at the store terminal 10. When the difference is deposited at the store terminal 10, the transaction management unit 212 of the control unit 21 generates a sales management record 230 and records it in the sales information storage unit 23.

  Next, the control part 21 of the management server 20 performs a point update process (step S2-17). The point management unit 213 of the control unit 21 calculates the number of points provided to the user based on the received difference. Then, the point management unit 213 resets the point balance of the user management record 220 and adds the calculated number of points.

  On the other hand, when it is determined that advance borrowing is not possible (in the case of “NO” in step S2-12), the control unit 21 of the management server 20 skips the determination process (step S2-14) as to whether or not the points can be allocated. In the same manner as in step S2-8, difference calculation processing is executed (step S2-15).

  Next, the control part 21 of the management server 20 performs a payment process (step S2-16). Specifically, the transaction management unit 212 of the control unit 21 waits for payment of the difference at the store terminal 10. When the difference is received at the store terminal 10, the transaction management unit 212 generates a sales management record 230 and records it in the sales information storage unit 23.

  Further, when it is determined that the points can be applied (in the case of “YES” in step S2-14), the control unit 21 of the management server 20 skips the difference calculation process (step S2-15) and performs the payment process (step S2-15). Step S2-16) is executed. Here, the transaction management unit 212 of the control unit 21 generates a sales management record 230 as “payment amount = 0” and records it in the sales information storage unit 23.

  Next, the control part 21 of the management server 20 performs a point update process (step S2-17). Specifically, the point management unit 213 of the control unit 21 subtracts the number of points corresponding to the payment amount from the point balance of the user management record 220.

  Next, the control unit 21 of the management server 20 executes an allocation process (step S2-18). Specifically, the accounting management unit 215 of the control unit 21 calculates an allowance based on the point balance updated in the user information storage unit 22 as in step S2-11, and stores the provision in the accounting management memory. Record on balance sheet.

  Further, when it is determined that there is advance borrowing (in the case of “YES” in step S2-4), the control unit 21 of the management server 20 executes a payment process (step S2-19). Specifically, the transaction management unit 212 of the control unit 21 waits for payment of the payment amount at the store terminal 10. When the payment amount is received at the store terminal 10, the transaction management unit 212 of the control unit 21 generates a sales management record 230 and records it in the sales information storage unit 23. Further, the point management unit 213 calculates the number of points provided to the user based on the deposit amount.

  Next, the control part 21 of the management server 20 performs a borrowing adjustment process (step S2-20). Specifically, the loan management unit 214 of the control unit 21 updates the advance borrowing status by subtracting the advance borrowing point number recorded as the advance borrowing status from the number of points calculated based on the deposit amount. In this case, if the calculated number of points is equal to or greater than the number of previous borrowed points, the number of previous borrowed points is reset. When the calculated number of points is less than the number of pre-borrowed points, it is updated with a value obtained by subtracting the number of calculated points from the number of previous borrow points.

Next, the control part 21 of the management server 20 performs a point update process (step S2-17). Specifically, the loan management unit 214 of the control unit 21 records the number of points remaining when the previous borrowed point number is subtracted from the calculated point number in the point balance of the user management record 220. If the calculated number of points is less than the number of pre-borrowed points and there are no remaining points, the point balance is not updated.
And the control part 21 of the management server 20 performs the allocation process similarly to step S2-11 (step S2-18).

As described above, according to the present embodiment, the following effects can be obtained.
(1) In the present embodiment, the control unit 21 of the management server 20 executes user information acquisition processing (step S1-1) and rank registration processing (step S1-2). Thus, segmentation is performed in consideration of the user's situation, and the advance borrowing upper limit can be determined by this segment.

  (2) In this embodiment, the control part 21 of the management server 20 performs the determination process about whether there exists a borrowing (step S2-4). And the control part 21 of the management server 20 performs the determination process about whether it is advance borrowing hope (step S2-5). Thereby, the advance borrowing situation in the user can be specified. And according to a user's hope, a point can be provided before dealings and a user can borrow in advance. For example, if a transaction with a large amount of payment is performed after a transaction with a small amount of payment is first performed, there is a possibility that the number of points given in the subsequent transaction may remain. Therefore, it is possible to borrow the number of points given in the subsequent transaction so that it can be used in the preceding transaction, thereby effectively using the points.

  (3) In this embodiment, when it determines with advance borrowing hope (in the case of "YES" in step S2-5), the control part 21 of the management server 20 performs the determination process about whether advance borrowing is possible (step S2). -12). Thereby, the risk that the points provided by the borrowing cannot be collected can be reduced.

  (4) In this embodiment, when it determines with advance borrowing being possible (in the case of "YES" in step S2-12), the control part 21 of the management server 20 performs a advance borrow registration process (step S2-13). Thereby, a user's advance borrowing situation can be managed.

  (5) In this embodiment, when it is determined that there is advance borrowing (in the case of “YES” in step S2-4), the control unit 21 of the management server 20 performs payment processing (step S2-19), advance borrow settlement processing ( Step S2-20) is executed. Thereby, the advance borrowing point can be repaid by the subsequent transaction.

Moreover, you may change the said embodiment into the following aspects.
-In the said embodiment, the borrowing of a point is permitted in the store (seller) which provides a point (privilege). Advance benefits are not limited to points. For example, it is possible to use a mileage provided when boarding an aircraft as a privilege for advance borrowing.

  In the above embodiment, the control unit 21 of the management server 20 executes rank registration processing (step S1-2). Here, bank customer information acquired from the bank server 30, transaction history information acquired from the sales information storage unit 23, and the like are used. Here, the information for performing the segmentation for determining the rank of the user is not limited to these. For example, it is possible to use the place of work, presence / absence of marriage, presence / absence of children, and the like.

  In the above-described embodiment, when it is determined that advance borrowing is desired (in the case of “YES” in step S2-5), the control unit 21 of the management server 20 executes determination processing as to whether or not advance borrowing is possible (step S2-12). ). Here, whether or not advance borrowing is possible is determined based on the advance borrowing upper limit. The method for determining whether or not to borrow in advance is not limited to this. For example, whether or not advance borrowing is possible may be determined according to the type of transaction. In this case, information for determining whether or not advance borrowing is possible is recorded for each product to be traded in the POS system.

  In the above embodiment, the control unit 21 of the management server 20 executes the advance borrowing settlement process (Step S2-20). Here, the number of advance borrowed points is repaid based on the number of points acquired in the subsequent transaction. The prepaid settlement method is not limited to this. For example, cash repayment may be performed. In this case, a bank account, a credit card number, etc. used for repayment are recorded in the user information storage unit 22. If the advance borrowing settlement is not performed by a predetermined repayment deadline, the advance borrowing point number is converted into a cash amount and repaid by account settlement or credit card settlement. In addition, when converting into the amount of cash, you may make it change a conversion rate according to a user rank or transaction condition.

  Moreover, you may enable it to perform divisional repayment in the advance borrowing settlement process. In this case, the number of points to be repaid is registered in advance in the advance borrowing status data area of the user information storage unit 22 in one advance loan settlement process. Furthermore, a predetermined divided repayment may be repaid based on the user's wishes.

  In the above embodiment, the control unit 21 of the management server 20 executes the advance borrowing settlement process (Step S2-20). Here, the number of repayment points may be increased with respect to the number of borrowed points. For example, the number of repayment points is determined by adding interest and fees corresponding to the period to the number of advance borrowed points. In this case, in the condition determination table, information for calculating the interest and the fee is stored corresponding to the user rank. In this case, it is desirable to record more favorable conditions (low interest rate, low fee, etc.) as the user rank is higher.

  In the above embodiment, a service that allows a point to be borrowed in advance is provided at a store (seller) that provides the point service. Here, the seller and the point issuer may be separated. In this case, the point management system manages the user's points based on the transaction information from the seller system. Then, the point management system makes an allocation update request to the seller system. This allocation update request is a message for requesting an update of the reserve in the balance sheet based on the point balance.

  In the above embodiment, the control unit 21 of the management server 20 periodically performs segmentation processing. The execution timing of the segmentation process is not limited to this. For example, it may be performed at the timing desired by the user or at the time of settlement.

  In the above embodiment, it is assumed that a store (seller) that provides points (privileges) provides a service that allows borrowing of points in advance. A store is not limited to a real store as long as it is a transaction with a seller having a point (privilege) system. For example, in a non-face-to-face transaction such as a mail-order shop on the Internet or an unmanned machine such as a vending machine, it is possible to provide a service that allows the advance borrowing of points.

  DESCRIPTION OF SYMBOLS 10 ... Store terminal, 20 ... Management server, 21 ... Control part, 211 ... User management part, 212 ... Transaction management part, 213 ... Point management part, 214 ... Loan management part, 215 ... Accounting management part, 22 ... User Information storage unit, 23 ... Sales information storage unit, 30 ... Bank server, 32 ... Customer information storage unit, 33 ... Transaction information storage unit.

Claims (7)

A user information storage unit storing a privilege balance for each user;
A privilege management system comprising a control unit for managing user privileges,
The control unit is
At the time of advance transaction, based on the user's advance borrowing request, the user is provided with the advance borrowing benefit, the advance borrowing situation is recorded in the user information storage unit, and the payment process is executed using the advance borrowing benefit. ,
In subsequent transactions, based on user authentication, if it is determined that a pre-borrowed benefit is recorded in the user information storage unit, using the benefit provided in accordance with the payment of the subsequent transaction, A privilege management system characterized by executing a repayment process for subtracting a pre-borrowed privilege. A transaction information storage unit that records transaction history information for each user;
The privilege management system according to claim 1, wherein whether or not a pre-borrow privilege is provided is determined based on the transaction history information. The control unit obtains information on the bank transaction of the user,
The privilege management system according to claim 1 or 2, wherein whether or not a pre-borrow privilege is provided is determined based on information related to the bank transaction. The control unit performs segmentation to determine a user rank for each user,
Based on the user rank, the advance borrowing conditions are determined,
The privilege management system according to any one of claims 1 to 3, wherein whether or not provision of a pre-borrowing privilege is determined is determined based on the pre-borrowing conditions.   The privilege management system according to claim 4, wherein an upper limit for advance borrowing is determined as the advance borrowing condition. A user information storage unit storing a privilege balance for each user;
A privilege management system using a privilege management system provided with a control unit for managing a user privilege,
The control unit is
At the time of advance transaction, based on the user's advance borrowing request, the user is provided with the advance borrowing benefit, the advance borrowing situation is recorded in the user information storage unit, and the payment process is executed using the advance borrowing benefit. ,
In subsequent transactions, based on user authentication, if it is determined that a pre-borrowed benefit is recorded in the user information storage unit, using the benefit provided in accordance with the payment of the subsequent transaction, The privilege management method characterized by performing the repayment process which subtracts a front borrow privilege. A user information storage unit storing a privilege balance for each user;
It is a program for performing privilege management using a privilege management system provided with a control unit for managing user privileges,
The control unit
At the time of advance transaction, based on the user's advance borrowing request, the user is provided with the advance borrowing benefit, the advance borrowing situation is recorded in the user information storage unit, and the payment process is executed using the advance borrowing benefit. ,
In subsequent transactions, based on user authentication, if it is determined that a pre-borrowed benefit is recorded in the user information storage unit, using the benefit provided in accordance with the payment of the subsequent transaction, A privilege management program that functions as means for executing a repayment process for subtracting a pre-borrowed privilege.

Images