JP2017084151A - Electronic ticket management device and electronic ticket management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an electronic ticket management device and an electronic ticket management method that are useful for use promotion of an electronic ticket.SOLUTION: An electronic ticket management device 2 comprises: an issued ticket management table TBL 213 in which electronic ticket information including a use upper limit amount, a use right holder and a payer is accumulated; a handover management unit 26 which obtains a handover request from the payer and changes the use right holder of the electronic ticket information accumulated in the issued ticket management table TBL 213 to a person designated in the handover request; a transaction management unit 27 which permits a transaction using the electronic ticket only in cases where the use right holder uses the electronic ticket within the use upper limit amount; and a payment processing unit 28 which performs payment processing such that a differential amount between the use upper limit amount of the electronic ticket used in the transaction and an actual used amount in the transaction is refunded to the payer of the electronic ticket.SELECTED DRAWING: Figure 2

Description

  The present disclosure relates to an electronic ticket management apparatus and an electronic ticket management method.

  In recent years, electronic payment services using information communication technology have been widely used. For example, in the system described in Patent Document 1, a taxi ticket is converted into an electronic ticket and settlement is performed using the electronic ticket. Payment processing can be simplified by using an electronic ticket.

JP-A-2005-135330

  Although the settlement processing using the electronic ticket has the advantages described above, it is difficult to say that the use of the electronic ticket is widely permeated at present.

  Therefore, an object of the present disclosure is to provide an electronic ticket management apparatus and an electronic ticket management method that are useful for promoting the use of electronic tickets.

  The present inventors pay attention to the desire to smoothly transfer electronic tickets between users, and suitably provide electronic tickets from one user (first user) to another user (second user). If it can be transferred, the use of electronic tickets will be promoted. Therefore, the present inventors have come up with an apparatus for transferring an electronic ticket having a usage upper limit amount to a second user in response to a request from the first user as an electronic ticket management apparatus. According to the electronic ticket management apparatus, the first user can easily transfer the electronic ticket set with the usage upper limit amount to the second user via the electronic ticket management apparatus.

  Here, at the stage of transferring the electronic ticket, it is often difficult to specify the amount actually used by the second user. Therefore, the first user needs to set a higher usage upper limit with a margin. As a result, the first user who is a settlement person hesitates to transfer the electronic ticket, and the use of the electronic ticket may not be promoted sufficiently.

  In this regard, the present inventors have conducted intensive research and have found the fact that the above-described problem can be solved by an electronic ticket management device having the following configuration.

  That is, the electronic ticket management device according to an aspect of the present disclosure acquires a storage unit that stores electronic ticket information including an upper limit of usage amount, a right holder, and a settlement person, and a transfer request from a settlement person The transfer management unit changes the right holder of the electronic ticket information stored in the storage unit to the person specified in the transfer request, and only when the right holder uses the electronic ticket within the upper limit of use. A transaction management unit that permits transactions using the electronic ticket, and when the transaction management unit permits transactions using the electronic ticket, the upper limit of the electronic ticket used for the transaction, A settlement processing unit that performs a settlement process so that a difference from the actual usage amount is returned to the settlement person of the electronic ticket.

  In this electronic ticket management apparatus, the right of use is changed based on a transfer request from a settlement person. When the right holder uses the electronic ticket within the usage upper limit, the use of the electronic ticket is permitted, and the difference between the usage upper limit and the usage amount is returned to the settlement person. For this reason, the lower the usage amount of the right holder and the higher the upper limit of use of the electronic ticket, the larger amount is returned to the settlement person. Therefore, even when the usage upper limit is set high at the stage of setting the usage upper limit or when the purchase price of the right holder is low, there is no disadvantage to the settlement person of the electronic ticket. As a result, transfer of the electronic ticket can be promoted, and as a result, use of the electronic ticket can be promoted.

  Further, in the electronic ticket management device, the electronic ticket information further includes information for specifying a use of the electronic ticket, and the transaction management unit uses the electronic ticket when the right of use uses the electronic ticket within the upper limit of use. May be further limited to the case where is within the scope of the use, and the transaction using the electronic ticket may be permitted. Thereby, the use application of an electronic ticket will be limited and the management burden of an electronic ticket can be reduced.

  In addition, the information processing apparatus may further include a use management unit that acquires use purpose designation from a settlement person and sets information specifying the use of the electronic ticket information stored in the storage unit to contents designated in the use purpose designation. . Thereby, it is possible to prevent the electronic ticket from being used for a purpose not intended by the settlement person. As a result, convenience for the settlement person is improved, and the use of electronic tickets can be further promoted.

  In the electronic ticket management apparatus, the electronic ticket information further includes a validity period of the electronic ticket, and the transaction management unit uses the electronic date and time within the validity period when the right holder uses the electronic ticket. Further, the transaction using the electronic ticket may be permitted only when it is within. Thereby, the period during which the electronic ticket is used is limited, and the management burden of the electronic ticket can be reduced. Further, for example, when the valid period can be set by the settlement person, it is possible to prevent the electronic ticket from being used during a period not intended by the settlement person. That is, it is possible to urge the use of the electronic ticket during a period intended by the settlement person. As a result, convenience for the settlement person is improved, and the use of electronic tickets can be further promoted.

  In the electronic ticket management apparatus, the settlement processing unit may perform a pre-settlement for the usage upper limit amount before the settlement process, and may perform a correction process according to the actual usage amount in the settlement process. By making a pre-settlement for the upper limit amount of use, the purchasing power of the electronic ticket and the settlement completion amount can be linked, and settlement can be performed more in line with the actual situation.

  In the electronic ticket management apparatus, the settlement processing unit may perform post-settlement for the amount of usage in the settlement process. As a result, the payment only needs to be made once after the use amount of the electronic ticket is determined, and the payment can be simplified.

  An electronic ticket management method according to an aspect of the present invention is an electronic ticket management method performed by an electronic ticket management apparatus, and stores electronic ticket information including an upper limit of use amount, a right holder, and a settlement person of an electronic ticket. And when a transfer request from a settlement person is acquired, the right holder of the electronic ticket information is changed to a person designated in the transfer request, and the right holder uses the electronic ticket within the upper limit of use. If the transaction using the electronic ticket is permitted in the step of permitting and permitting the transaction using the electronic ticket, the upper limit amount of the electronic ticket used for the transaction, and the And performing a settlement process so that a difference from the actual usage amount in the transaction is returned to the settlement person of the electronic ticket.

  According to the present disclosure, it is possible to provide an electronic ticket management apparatus and an electronic ticket management method that are useful for promoting the use of electronic tickets.

It is a figure which shows typically schematic structure of the electronic ticket management system which concerns on this embodiment. It is a block diagram which shows the functional structure of an electronic ticket management apparatus. FIG. 3A is a table showing a table included in the electronic ticket management apparatus, FIG. 3A shows a customer management table, and FIG. 3B shows an electronic ticket management table. 4A is a table showing a table possessed by the electronic ticket management apparatus. FIG. 4A shows an issued ticket management table, FIG. 4B shows a purchase management table, and FIG. 4C shows a final settlement table. Yes. It is a sequence diagram which shows the execution procedure of an electronic ticket management method. It is a figure which shows typically the image of the electronic ticket management using an application. It is a sequence diagram which shows the execution procedure of the electronic ticket management method which concerns on a modification.

  Hereinafter, embodiments will be described in detail with reference to the drawings. In the description, the same elements or elements having the same functions are denoted by the same reference numerals, and redundant description is omitted.

[Electronic ticket management system]
As shown in FIG. 1, the electronic ticket management system 1 includes an electronic ticket management device 2, a communication network 3, mobile terminals 4 and 5, a card company terminal 6, and a user company terminal 7. . The communication network 3 is, for example, the Internet, and the electronic ticket management device 2, the mobile terminals 4 and 5, the card company terminal 6, and the user company terminal 7 are each connected to the communication network 3.

  The mobile terminals 4 and 5 are, for example, mobile phones such as smartphones or feature phones, and communication terminals such as tablet terminals. The mobile terminals 4 and 5 have downloaded software (applications) for using electronic tickets. By executing the application, communication is performed between the mobile terminals 4 and 5 and the electronic ticket management apparatus 2, and the user of the mobile terminals 4 and 5 can use the electronic ticket. Although the use of the electronic ticket is not necessarily realized by the above-described application, the following description will be made assuming that the electronic ticket is used by using the above-described application.

  The mobile terminals 4 and 5 execute an application to issue an electronic ticket issue request, view the issued electronic ticket, change the usage of the electronic ticket, transfer / transfer the electronic ticket, and transactions using the electronic ticket (product) Or purchase of services). In the present embodiment, the mobile terminal 4 is a terminal used by a first user (settler and transferor) who purchases an electronic ticket and transfers it to another person. The mobile terminal 5 is a terminal used by a second user (transferee) who receives an electronic ticket from the first user and uses the electronic ticket. Since the first user and the second user are both persons who can purchase products etc. using an electronic ticket, they may be described together as “consumers”.

  For convenience, the mobile terminals 4 and 5 are described with different reference numerals, but there is no difference in functions for using the electronic tickets in the mobile terminals 4 and 5. In FIG. 1, each of the mobile terminals 4 and 5 is illustrated one by one, but there may be a plurality of mobile terminals 4 and 5, and the number is not limited.

  The card company terminal 6 is a terminal of a credit card company that issues a credit card and manages transactions by the credit card. The card company terminal 6 communicates with the electronic ticket management device 2 to make a card settlement related to the purchase of an electronic ticket for purchasing goods or services. The user company terminal 7 is a terminal of a customer (user company) that receives a price in a transaction using an electronic ticket. Since the business partner is a person who sells products or the like, it may be described as “seller”. For example, when a user who takes a taxi uses an electronic ticket, the user company terminal 7 is a terminal of a taxi company. The user company terminal 7 communicates with the electronic ticket management device 2 to perform a settlement process in a transaction using the electronic ticket. The card company terminal 6 and the user company terminal 7 are provided for each company, and may be provided for each company, or a plurality of them may be provided.

[Electronic ticket management device]
The electronic ticket management device 2 is a server that issues an electronic ticket and manages transactions using the electronic ticket. The electronic ticket management apparatus 2 includes a processor 201, a memory 202, a storage 203, a network adapter 204, and a bus 205 that connects them. The processor 201 inputs and outputs data via the network adapter 204 by executing a program in cooperation with at least one of the memory 202 and the storage 203. Thereby, various functions of the electronic ticket management apparatus 2 are realized. The configuration of the electronic ticket management device 2 shown here is an example. The electronic ticket management device 2 may be configured in hardware as long as the functions described below can be realized.

  FIG. 2 is a diagram showing each function of the electronic ticket management device 2 as a virtual component (hereinafter referred to as “function block”). These functional blocks are merely the functions of the electronic ticket management apparatus 2 divided into a plurality of blocks for convenience, and do not mean that the hardware is divided into such blocks.

  As shown in FIG. 2, the electronic ticket management device 2 includes a communication unit 21, a customer information update unit 22, an issue unit 23, a usage management unit 24, a ticket information output unit 25, and a transfer as functional blocks. Management unit 26, transaction management unit 27, settlement processing unit 28, customer management table TBL211, electronic ticket management table TBL212, issued ticket management table TBL213 (storage unit), purchase management table TBL214, and fixed settlement table TBL215.

  The communication unit 21 refers to the mobile terminals 4 and 5, the card company terminal 6, and the user company terminal 7 (hereinafter, the mobile terminals 4 and 5, the card company terminal 6 and the user company terminal 7 are referred to as “mobile terminals 4 and 5”). To send and receive information. That is, the communication unit 21 receives a predetermined request or the like from the mobile terminals 4 and 5 and outputs the request or the like to other functional blocks in the electronic ticket management device 2. The communication unit 21 receives an input such as a predetermined request from another functional block in the electronic ticket management device 2 and transmits the request to the portable terminals 4 and 5.

  The customer information update unit 22 receives a customer information update request from the mobile terminals 4 and 5 or the user company terminal 7 via the communication unit 21 and updates the customer management table TBL211. FIG. 3A is a table showing the customer management table TBL211. As shown in FIG. 3A, the customer management table TBL211 stores customer information in which each customer is associated with a user ID, name, user type, notification destination, and card number.

  A customer is a person who makes a transaction using an electronic ticket by communicating with the electronic ticket management device 2. That is, the customers are consumers who purchase goods or services using electronic tickets (that is, users who use the mobile terminals 4 and 5), and sellers who receive payment for goods or services using electronic tickets (that is, users). , A user company that uses the user company terminal 7). The user ID is an identifier that uniquely identifies the user. The name is the name of the user. The user type is the type of the user and is, for example, “1” or “2”. The user type “1” indicates that the user is a seller, and “2” indicates that the user is a consumer. The notification destination is a contact address of the user, and is a contact address used when communicating with the electronic ticket management apparatus. For example, an e-mail address or a telephone number is registered as the notification destination. The card number is the credit card number of the user. The card number is used in the settlement process. In the customer management table TBL211, the name and card number are not necessarily set.

  The customer information update unit 22 adds, deletes, and edits customer information as update processing of the customer management table TBL211. That is, when the customer information update unit 22 receives a customer information update request from the mobile terminals 4, 5 or the like in which customer information is not stored, the customer information update unit 22 adds the customer information related to the terminal to the customer management table TBL211. In this case, the customer information update request includes information indicating a name, a user type, a notification destination, and a card number. The customer information update unit 22 creates customer information by associating each piece of information included in the customer information update request with an arbitrarily determined user ID, and adds the customer information to the customer management table TBL211.

  When the customer information update unit 22 receives a customer information update request including a request for deleting customer information from the mobile terminals 4, 5, etc., the customer information update unit 22 deletes the customer information related to the mobile terminals 4, 5, etc. When the customer information update unit 22 receives a customer information update request including a request for editing customer information from the mobile terminals 4 and 5, the customer information update unit 22 edits the customer information related to the mobile terminals 4 and 5. Editing customer information refers to changing the name, notification destination, card number, and the like, for example. When the update process is completed, the customer information update unit 22 may transmit a completion notification to the mobile terminals 4, 5, etc. via the communication unit 21.

  The issuing unit 23 receives an electronic ticket issue request from the portable terminal 4 via the communication unit 21 and issues an electronic ticket. More specifically, the issuing unit 23 issues an electronic ticket when receiving an electronic ticket issuing request and further receiving a prepayment processing completion report (details will be described later) from the payment processing unit 28. The electronic ticket issuance request includes information (ticket ID) for specifying an electronic ticket desired to be issued, an electronic ticket usage upper limit, an electronic ticket validity period, and a user ID. The issuing unit 23 refers to the electronic ticket management table TBL212 and issues an electronic ticket based on information included in the electronic ticket issue request. Specifically, the issuing unit 23 stores (adds) an electronic ticket associated with predetermined information in the issued ticket management table TBL213.

  FIG. 3B is a table showing the electronic ticket management table TBL212. As shown in FIG. 3B, the electronic ticket management table TBL212 stores the ticket ID, usage, usage company ID, and settable amount of all electronic tickets in association with each other. The ticket ID is an identifier that uniquely identifies the type of electronic ticket. Note that the predetermined ticket ID (for example, “99999”) may be an identifier of an electronic ticket whose usage, user company ID, settable amount, etc. are “free”. “Free” for usage or the like means that the user can freely specify the usage or the like (details will be described later). Use is the use of the electronic ticket. The user company ID is an identifier that uniquely identifies a user company (seller) that can be a usage destination of the electronic ticket. A plurality of IDs may be set for the user company ID. The settable amount is a range of an amount that can be set as the use upper limit amount of the electronic ticket. In the electronic ticket management table TBL212, the settable amount does not necessarily have to be set.

  FIG. 4A is a table showing the issued ticket management table TBL213. As shown in FIG. 4A, the issued ticket management table TBL 213 includes an issued ticket ID, a ticket ID, a usage upper limit, a valid period, a settlement person ID, and a right holder of the electronic ticket issued by the issuing unit 23. Electronic ticket information in which the ID and the used flag are associated is stored (accumulated).

  The issued ticket ID is an identifier that uniquely identifies the issued electronic ticket. The ticket ID is an identifier that uniquely identifies the type of the electronic ticket. The usage upper limit is the usage upper limit set for the electronic ticket. The valid period is a valid period of the electronic ticket (a period during which the electronic ticket can be used). In FIG. 4A, the valid period is set up to the date, but may be set up to the time. The settlement person ID is an identifier that uniquely identifies a person who performs settlement related to the purchase of the electronic ticket. The right-of-use user ID is an identifier that uniquely identifies a person who can purchase a product or the like using the electronic ticket. The used flag is a flag indicating whether or not the electronic ticket has been used. “1” is set when the electronic ticket is used, and “0” is set when the electronic ticket is not used.

  As is clear from the electronic ticket management table TBL212 shown in FIG. 3B, the ticket ID may be used and used company ID (hereinafter referred to as “used” together with the used and used company ID). Are associated with each other. In other words, the electronic ticket information in the issued ticket management table TBL213 includes a ticket ID that is information for specifying the use of the electronic ticket.

  The issuing unit 23, based on the information in the electronic ticket management table TBL212 and the information included in the electronic ticket issuance request, issues a ticket ID, a usage upper limit, a valid period, a payer ID, and a usage of the electronic ticket to be issued. Specify the right holder ID. That is, when the ticket ID included in the electronic ticket issue request exists in the electronic ticket management table TBL212, the issuing unit 23 specifies the ticket ID as the ticket ID of the electronic ticket to be issued. In addition, when the use upper limit included in the electronic ticket issue request is within the settable amount range in the electronic ticket management table TBL212, the issuing unit 23 sets the use upper limit to the use upper limit of the electronic ticket to be issued. As specified.

  Further, the issuing unit 23 specifies the validity period included in the electronic ticket issuance request as the validity period of the issued electronic ticket. Further, the issuing unit 23 specifies the user ID included in the electronic ticket issuing request as the settlement person ID and the right-of-use user ID of the electronic ticket to be issued. At the time of issuing the electronic ticket, the issuing unit 23 specifies that the used flag of the electronic ticket to be issued is “0”. Then, the issuing unit 23 stores (adds) an electronic ticket in which the arbitrarily set issuance ticket ID and the identified information are associated with each other in the issuance ticket management table TBL213. When the issuing process is completed, the issuing unit 23 may transmit a completion notification to the mobile terminal 4 via the communication unit 21.

  The use management unit 24 specifies information for specifying the use of the electronic ticket stored in the issued ticket management table TBL 213 according to the use purpose designation from the first user who is a settlement person of the issued electronic ticket, that is, a ticket ID. Set (change). Specifically, the usage management unit 24 receives a usage purpose designation from the mobile terminal 4 of the first user who is a settlement person via the communication unit 21. The use purpose designation includes an issued ticket ID for specifying an electronic ticket whose ticket ID is to be changed, and a ticket ID after the change. The use purpose designation may include a use upper limit and / or a validity period after changing the ticket ID. Then, the usage management unit 24 refers to the issued ticket management table TBL213, and changes the ticket ID of the electronic ticket specified by the issued ticket ID included in the usage purpose specification to the ticket ID included in the usage purpose specification. . When the usage purpose designation includes a usage upper limit amount or the like, the usage upper limit amount or the like may be changed together with the ticket ID.

  The usage management unit 24 may change the ticket ID only when the ticket ID of the target electronic ticket is a predetermined ID. Specifically, the use management unit 24 may change the above-described ticket ID only for the electronic ticket with the ticket ID “99999” whose use is “free”. When the change of the ticket ID is completed, the usage management unit 24 may transmit a completion notification to the mobile terminal 4 via the communication unit 21.

  The ticket information output unit 25 outputs information related to an electronic ticket in which the user is at least one of a settlement person and a right-of-use user in response to a browsing request from the user. Specifically, the ticket information output unit 25 receives a browsing request from the mobile terminal 4 or the mobile terminal 5 via the communication unit 21. The browsing request includes an issuance ticket ID that specifies an electronic ticket that is desired to be browsed. The ticket information output unit 25 refers to the issued ticket management table TBL213 and identifies the electronic ticket information related to the issued ticket ID included in the browsing request. Further, the ticket information output unit 25 refers to the electronic ticket management table TBL212 and identifies the usage and user company ID associated with the ticket ID of the identified electronic ticket information. Then, the ticket information output unit 25 transmits information related to the specified electronic ticket to the mobile terminal 4 or the mobile terminal 5 that is the transmission source of the browsing request via the communication unit 21.

  The transfer management unit 26 acquires a transfer request from the first user who is a settlement person of the issued electronic ticket, and changes the use right holder of the electronic ticket to a person designated in the transfer request. Specifically, the transfer management unit 26 receives a transfer request from the mobile terminal 4 of the first user who is a settlement person via the communication unit 21. The transfer request includes an issuance ticket ID for specifying an electronic ticket for changing the right holder and a user ID for specifying the second user who is the changed right holder (that is, the assignee). Then, the transfer management unit 26 refers to the issued ticket management table TBL213, and uses the right holder ID of the electronic ticket specified by the issued ticket ID included in the transfer request as the user of the second user included in the transfer request. Change to ID. The transfer management unit 26 may transmit a notification to the effect that the change (rewrite) of the right holder has been completed to the mobile terminal 4 of the first user and the mobile terminal 5 of the second user via the communication unit 21. .

  The transaction management unit 27 manages transactions using electronic tickets by users. The transaction management unit 27 permits transactions using the electronic ticket only when the right holder uses the electronic ticket within the usage upper limit. When the right holder uses the electronic ticket within the upper limit of use, the transaction management unit 27 uses the electronic ticket within the range of the use of the electronic ticket (that is, usage and user ID), and the use date and time. Is permitted only when the electronic ticket is within the validity period of the electronic ticket, and transactions using the electronic ticket are permitted.

  Specifically, the transaction management unit 27 receives a settlement request from the user company terminal 7 via the communication unit 21. The settlement request is output by the utilization company terminal 7 in response to a settlement request from a second user who conducts a transaction using an electronic ticket with the seller associated with the utilization company terminal 7 as a business partner. The payment request includes the usage amount of the electronic ticket and the name of the product / service to be traded. The settlement request includes a user ID for identifying a seller related to the user company terminal 7, a usage amount and a product / service name included in the settlement request, a use date and time when a transaction using an electronic ticket was performed, It is included. Note that the use date and time when the transaction was performed is, for example, the date and time when the user company terminal 7 received a payment request from the second user.

  Upon receipt of the settlement request, the transaction management unit 27 authenticates the user company terminal 7 that has transmitted the settlement request. Specifically, the transaction management unit 27 refers to the customer management table TBL211, the user ID included in the settlement request exists in the customer management table TBL211, and the user is associated with the user ID in the customer management table TBL211. It is confirmed that the type is “1” (the user is a seller). When the authentication is completed, the transaction management unit 27 associates the information included in the payment request and stores it in the purchase management table TBL214.

  FIG. 4B is a table showing the purchase management table TBL214. As shown in FIG. 4B, the purchase management table TBL 214 stores purchase information in which a user company ID, a usage amount, a product / service name, a usage date, and a payment code are associated with each transaction using an electronic ticket. I remember it. The user company ID is an identifier that uniquely identifies a user company (seller) in a transaction using an electronic ticket. The usage amount is an amount paid by an electronic ticket in the transaction. The product / service name is the name of the product or service related to the transaction. The use date is the date when the transaction was performed. The payment code is an identifier that uniquely identifies the transaction.

  The transaction management unit 27 specifies a user ID, a usage amount, a product / service name, and a usage date and time included in the settlement request, and purchases in which the specified information is associated with an arbitrarily set payment code. Information (purchase information for which a payment code has been issued) is stored in the purchase management table TBL 214. After the storage, the transaction management unit 27 transmits a code issue notification indicating that the payment code has been issued to the user company terminal 7 via the communication unit 21. The code issuance notification includes the issued payment code.

  The user company terminal 7 that has received the code issue notification transfers the code issue notification to the mobile terminal 5 of the second user. The transfer of the code issuance notification from the user company terminal 7 to the mobile terminal 5 may be realized by displaying the payment code on the application and presenting it to the second user, or may include a QR code, a barcode, Further, it may be realized by displaying as a graphic such as a color code and presenting it to the second user, or may be realized by using short-range communication. Alternatively, the transfer of the code issue notification may be performed by verbally transmitting the payment code from the user of the user company terminal 7 to the second user. Then, the payment code is input from the mobile terminal 5 by the second user who has confirmed the payment code. The input of the payment code by the second user may be realized by manual input in the code input field of the application, or may be realized by reading a figure such as a QR code by a camera function provided in the mobile terminal 5. . The transaction management unit 27 acquires, via the communication unit 21, the payment code input in the mobile terminal 5 and a user ID that identifies the second user who has input the payment code.

  The transaction management unit 27 that has acquired a payment code or the like from the mobile terminal 5 performs transaction validity determination processing. In the validity determination process, the transaction management unit 27 performs each process of code confirmation, usage right holder confirmation, and amount confirmation. The transaction management unit 27 determines that the transaction using the electronic ticket is valid when a predetermined condition is satisfied in all the processes.

  In the code confirmation process, the transaction management unit 27 determines whether or not the payment code acquired from the mobile terminal 5 is a correct payment code for which a settlement request has occurred. Specifically, the transaction management unit 27 determines whether or not the acquired payment code is a payment code stored in the purchase management table TBL214. The transaction management unit 27 considers that a predetermined condition in the code confirmation process is satisfied only when it is determined that the payment code is a correct payment code for which a settlement request has occurred.

  In the usage right owner confirmation process, the transaction management unit 27 determines whether or not the second user can become a usage right holder. Specifically, the transaction management unit 27 determines whether or not an electronic ticket in which the acquired user ID of the second user is the usage right user ID is stored in the issued ticket management table TBL213. Only when it is determined that the second user can be a right holder, the transaction management unit 27 considers that a predetermined condition in the right holder confirmation process is satisfied. In this case, the transaction management unit 27 specifies an electronic ticket in which the user ID of the second user is a usage right ID.

  In the amount confirmation processing, the transaction management unit 27 determines whether the amount used in the transaction is within the upper limit of use of the electronic ticket, whether the purpose of use of the transaction is within the range of use of the electronic ticket, and the transaction It is determined whether or not the use date and time is within the validity period of the electronic ticket. Specifically, the transaction management unit 27 refers to the purchase management table TBL 214 and identifies the user company ID, the usage amount, the product / service name, and the usage date and time corresponding to the payment code acquired from the mobile terminal 5. The purpose of use is specified by the user company ID and the product / service name.

  Then, the transaction management unit 27 refers to the issued ticket management table TBL213, and the use upper limit amount is larger than the above use amount in the electronic ticket specified in the use right holder confirmation process, and the use matches the purpose of use. Then, it is determined whether or not there is an electronic ticket whose valid period includes the use date and time. Here, as described above, in the issued ticket management table TBL213, a ticket ID is stored as information for specifying the use of the electronic ticket. In the electronic ticket management table TBL212, the ticket ID is associated with the ticket ID and used for the electronic ticket. A certain usage and user ID are stored. Therefore, the transaction management unit 27 compares the use and user company ID, which is the use of the electronic ticket specified in the right holder confirmation process, with the product / service name and user company ID that are the purpose of use corresponding to the payment code. By doing so, it is determined whether there is an electronic ticket whose usage matches the purpose of use.

  Only when it is determined that there is the electronic ticket, the transaction management unit 27 considers that a predetermined condition in the amount confirmation process is satisfied. In this case, the transaction management unit 27 identifies one electronic ticket that satisfies the conditions for the confirmation process such as the amount. When there are a plurality of electronic tickets that satisfy the condition, the transaction management unit 27 may preferentially specify an electronic ticket having a small use upper limit, for example. Further, an input of information specifying an electronic ticket to be used may be received from the second user, and one electronic ticket may be specified according to the input.

  If the transaction management unit 27 considers that a predetermined condition is satisfied in all of the code confirmation process, the right holder confirmation process, and the amount confirmation process, the transaction management unit 27 uses the electronic ticket specified in the amount confirmation process. Determine that the transaction is valid and authorize the transaction. In this case, the transaction management unit 27 refers to the issued ticket management table TBL213 and changes the used flag of the electronic ticket specified in the amount confirmation process to “1”. After changing the used flag, the transaction management unit 27 outputs a corrected settlement request to the settlement processing unit 28. The corrected settlement request includes an issuance ticket ID that identifies an electronic ticket whose used flag has been changed, and a payment code related to the transaction.

  When the transaction management unit 27 permits the transaction using the electronic ticket, the settlement processing unit 28 determines that the difference between the upper limit of the electronic ticket used for the transaction and the actual usage amount in the transaction is the electronic Settlement processing is performed so that it is returned to the ticket settler. Specifically, the settlement processing unit 28 performs pre-settlement for the upper limit amount of use in the previous stage of the settlement process (more specifically, the stage before the electronic ticket is issued), and in the settlement process, Perform correction processing according to the transaction usage amount.

  In the advance settlement process, the settlement processing unit 28 first receives an electronic ticket issue request from the portable terminal 4 via the communication unit 21. The electronic ticket issuance request includes information indicating the upper limit amount of the electronic ticket scheduled to be issued and the user ID of the first user. The settlement processing unit 28 refers to the customer management table TBL211 to identify the card number of the first user, communicates with the card company terminal 6 via the communication unit 21, and issues the credit card using the user's credit card. Settlement (pre-settlement) only for the upper limit of the planned electronic ticket usage. When the pre-settlement process is completed, the settlement processing unit 28 outputs a completion report of the pre-settlement process to the issuing unit 23.

  In the correction process (payment process), the payment processing unit 28 first receives a corrected payment request from the transaction management unit 27, and acquires the issued ticket ID and payment code included in the corrected payment request. The settlement processing unit 28 refers to the issued ticket management table TBL213 to identify the upper limit amount of use of the electronic ticket indicated by the acquired issued ticket ID, and refers to the purchase management table TBL214 to indicate the acquired payment code. Identify the amount of money used in the transaction. Then, the payment processing unit 28 specifies an amount obtained by subtracting the usage amount from the specified usage upper limit amount as a return amount to the first user who is a settlement person. The settlement processing unit 28 refers to the customer management table TBL211 and identifies the card number of the first user, and then communicates with the card company terminal 6 via the communication unit 21 and uses the credit card of the user to Make a refund for the refund amount. Alternatively, the settlement processing unit 28 may perform a process of correcting the amount of advance settlement to the above usage amount. By such correction processing, finally, the settlement amount related to the transaction becomes equal to the usage amount in the transaction.

  When the correction process (payment process) is completed, the payment processing unit 28 notifies the right holder (second user) and the payment person (first user) of the electronic ticket indicated by the issued ticket ID included in the corrected payment request. A settlement completion notification is transmitted, and a settlement completion notification is transmitted to the user company (seller) of the transaction indicated by the payment code. Finally, the settlement processing unit 28 updates the final settlement table TBL215.

  FIG. 4C is a table showing the fixed settlement table TBL215. As shown in FIG. 4C, the final settlement table TBL15 stores final settlement information in which a settlement person ID, a payment code, and a settlement amount related to the settlement process performed by the settlement processing unit 28 are associated. . The settlement person ID is an identifier that uniquely identifies the settlement person of the electronic ticket related to the settlement. The payment code is an identifier that uniquely identifies the transaction. The settlement amount is the final settlement amount in the transaction. The settlement processing unit 28 associates the settlement person ID, the payment code, and the settlement amount (that is, the usage amount in the transaction), and stores them in the settlement settlement table TBL 215 as the settlement settlement information.

[Electronic ticket management procedure]
Next, as an example of an electronic ticket management method, an electronic ticket management procedure by the electronic ticket management apparatus 2 will be described with reference to FIG. In FIG. 5, an electronic ticket is issued in response to a request from the first user (steps S101 to S107), and the right to use the electronic ticket is changed to a second user in response to a request from the first user (step S109). To 115), an example is shown in which settlement processing is performed in accordance with the use of the electronic ticket by the second user (steps S117 to S139). Of the steps to be described, steps S117 and S125 are not processes in the electronic ticket management apparatus 2, but are processes necessary for explaining the electronic ticket management, and will be described together.

  First, the electronic ticket issuing request transmitted from the mobile terminal 4 of the first user is received by the issuing unit 23 and the settlement processing unit 28 via the communication unit 21 (step S101). The electronic ticket issuance request includes the ticket ID of the electronic ticket that is desired to be issued, the maximum usage amount of the electronic ticket, the validity period of the electronic ticket, and the user ID.

  Subsequently, a pre-settlement process is performed by the settlement processing unit 28 (step S103). That is, the settlement processing unit 28 refers to the customer management table TBL211 and identifies the first user's card number, and then communicates with the card company terminal 6 via the communication unit 21 and uses the user's credit card. Settlement (pre-settlement) is made only for the maximum usage amount of the electronic ticket scheduled to be issued. When the pre-settlement process is completed, the settlement processing unit 28 outputs a completion report of the pre-settlement process to the issuing unit 23.

  Subsequently, an electronic ticket is issued by the issuing unit 23 that has received the electronic ticket issue request from the portable terminal 4 and the completion report of the pre-settlement process from the payment processing unit 28, and the electronic ticket is issued in the issued ticket management table TBL213. It is stored (accumulated) (step S105: accumulating step). In other words, the issuing unit 23, based on the information in the electronic ticket management table TBL212 and the information included in the electronic ticket issuance request, issues the ticket ID of the electronic ticket to be issued, the maximum usage amount, the valid period, the settlement person ID, Then, the use right holder ID is specified, and an electronic ticket in which the specified information is associated with the arbitrarily set issuance ticket ID is stored in the issuance ticket management table TBL213. After issuing the electronic ticket, the issuing unit 23 transmits an issue completion notification to the mobile terminal 4 (step S107).

  FIG. 6A shows an electronic ticket management image using an application in the electronic ticket issuing process shown in steps S101 to S107 described above. FIG. 6A shows an example in which a business partner (user company) in a transaction using an electronic ticket is a taxi company (the same applies to FIGS. 6B and 6C described later). In the example shown in FIG. 6, the first user's mobile terminal 4, the second user's mobile terminal 5, and the taxi company user company terminal 7 include a dedicated application for using an electronic ticket with the taxi company as a business partner. Has been downloaded.

  FIG. 6A shows an electronic ticket management image using an application when a first user who is a settlement person purchases an electronic ticket. The first user launches a taxi company dedicated application from the mobile terminal 4, inputs information specifying an electronic ticket to be purchased, a use upper limit amount, and the like, and performs an input instructing purchase (“FIG. 6A“ Refer to the app display image of “Before purchase”). Based on the input, the electronic ticket issue request described above is transmitted to the electronic ticket management apparatus 2. When the pre-settlement and issuance processing of the electronic ticket is completed, the first user can confirm the information related to the issued electronic ticket with the dedicated application (the application display “after purchase” in FIG. 6A). See image).

  Returning to FIG. 5, the right-of-user change process is described. After the electronic ticket is issued, a transfer request for the electronic ticket is transmitted from the mobile terminal 4 of the first user who is the settlement user who has made the pre-payment, and the transfer request is transferred via the communication unit 21 to the transfer management unit 26. (Step S109). The transfer request includes an issuance ticket ID for specifying an electronic ticket for changing the right holder and a user ID for specifying the second user who is the changed right holder (that is, the assignee).

  Subsequently, the transfer manager 26 changes the right to use the electronic ticket in response to the transfer request (step S111, changing step). That is, the transfer management unit 26 refers to the issued ticket management table TBL213, and uses the right holder ID of the electronic ticket specified by the issued ticket ID included in the transfer request as the user of the second user included in the transfer request. Change to ID. After the change of the right-of-use person, the transfer management unit 26 sends a notification to the effect that the change of the right-of-use person (rewrite) is completed to the mobile terminal 4 of the first user and the mobile terminal 5 of the second user (step) S113, S115).

  After the notification to the effect that the change of the right of use shown in steps S113 and S115 is completed (or when it is performed), the application is used between the first user and the second user. Electronic tickets may be sent and received. FIG. 6B shows an electronic ticket management image using an application when the electronic ticket is transferred from the mobile terminal 4 of the first user to the mobile terminal 5 of the second user.

  When the first user and the second user are close to each other, information indicating the transferred electronic ticket (rewritten the right holder) is transferred from the first user's portable terminal 4 to the second user's portable terminal 5. On the other hand, it may be directly transmitted by short-range communication (see the application display image of “when the second user is next” in FIG. 6B). In this case, information indicating the electronic ticket transmitted and received by the short-range communication is transmitted from both the portable terminal 4 and the portable terminal 5 to the electronic ticket management device 2.

  In addition, when the first user and the second user are far away, information indicating the transferred electronic ticket (rewritten the right-of-use holder) is sent from the portable terminal 4 via the communication network 3, for example. Further, the information may be transmitted to the device 2, and the information may be transmitted from the electronic ticket management device 2 to the portable terminal 5 (see the application display image of “when the second user is far away” in FIG. 6B).

  Returning to FIG. 5, the settlement process will be described. After the transfer of the electronic ticket, when the second user who is the transferee performs a transaction using the electronic ticket, a payment request is transmitted from the mobile terminal 5 of the second user to the user company terminal 7 which is the customer. (Step S117). The settlement request includes the usage amount of the electronic ticket and the name of the product / service to be traded. The payment request transmission may be realized by short-range communication, or may be realized by causing the user company terminal 7 to read a figure such as a QR code / bar code. Alternatively, the settlement request may be made verbally to the user of the user company terminal 7 from the second user. Then, a settlement request is transmitted from the user company terminal 7 that has received the settlement request to the electronic ticket management apparatus 2, and the settlement request is received by the transaction management section 27 via the communication section 21 (step S119). . The settlement request includes a user ID for identifying a seller related to the user company terminal 7, a usage amount and a product / service name included in the settlement request, a use date and time when a transaction using an electronic ticket was performed, It is included.

  Subsequently, the transaction management unit 27 authenticates the user company terminal 7 in response to the payment request (step S121). That is, the transaction management unit 27 refers to the customer management table TBL 211, the user ID included in the settlement request exists in the customer management table TBL 211, and the user type associated with the user ID in the customer management table TBL 211 is “ 1 ”(the user is a seller). When the authentication is completed, the transaction management unit 27 stores the purchase information in which the information included in the payment request is associated with the arbitrarily set payment code in the purchase management table TBL214. After the storage, the transaction management unit 27 transmits a code issuance notification indicating that the payment code has been issued to the user company terminal 7 (step S123), and further, the code issuance notification is transmitted from the user company terminal 7 to the portable terminal 5. Transferred (step S125). The transfer of the code issuance notification to the mobile terminal 5 by the user company terminal 7 may be realized by displaying the payment code on the application and presenting it to the second user, or QR code, bar code, and color It may be realized by displaying it as a graphic such as a code and presenting it to the second user, or may be realized using short-range communication. Alternatively, the transfer of the code issue notification may be performed by verbally transmitting the payment code from the user of the user company terminal 7 to the second user.

  Then, the payment code is input from the mobile terminal 5 by the second user who has confirmed the payment code, and the payment management code and the user ID that identifies the second user who has input the payment code are sent via the communication unit 21 to the transaction management unit. 27 (step S127).

  Subsequently, the transaction management unit 27 that has acquired the payment code from the mobile terminal 5 determines the validity of the transaction, and the transaction using the electronic ticket is performed only when the conditions such as the maximum usage amount are satisfied. Permitted (step S129, permitting step). In other words, the transaction management unit 27 performs each process of code confirmation, right-of-use confirmation, and confirmation of the amount of money, and the transaction using the electronic ticket is effective when the predetermined conditions are satisfied in all the processes. The electronic ticket transaction is permitted.

  When the transaction using the electronic ticket is permitted, the transaction management unit 27 updates the electronic ticket to “used” (step S131). That is, the transaction management unit 27 refers to the issued ticket management table TBL213 and changes the used flag of the electronic ticket specified as the electronic ticket used for the transaction to “1”. After changing the used flag, the transaction management unit 27 outputs a corrected settlement request to the settlement processing unit 28. The corrected settlement request includes an issuance ticket ID that identifies an electronic ticket whose used flag has been changed, and a payment code related to the transaction.

  Subsequently, the settlement processing unit 28 performs a modified settlement process so that the difference between the upper limit amount of the electronic ticket used for the transaction and the actual usage amount in the transaction is returned to the settlement person of the electronic ticket. (Step S133, step of performing a settlement process). That is, the settlement processing unit 28 refers to the issued ticket management table TBL213 to identify the upper limit amount of use of the electronic ticket indicated by the acquired issued ticket ID, and refers to the purchase management table TBL214 to obtain the acquired payment code. The usage amount in the transaction indicated by is specified. Then, the payment processing unit 28 specifies an amount obtained by subtracting the usage amount from the specified usage upper limit amount as a return amount to the first user who is a settlement person. The settlement processing unit 28 refers to the customer management table TBL211 and identifies the card number of the first user, and then communicates with the card company terminal 6 via the communication unit 21 and uses the credit card of the user to Refund payment is made for the refund amount (or processing for correcting the advance payment amount to the usage amount).

  After the payment processing, the payment processing unit 28 uses the portable terminal 5 of the right holder (second user) of the electronic ticket indicated by the issued ticket ID included in the corrected payment request and the payment person (first user). A payment completion notice is transmitted to the portable terminal 4 (steps S135 and S136). In addition, the settlement processing unit 28 transmits a payment completion notice to the user company terminal 7 of the seller of the transaction indicated by the payment code (step S137). Finally, the settlement processing unit 28 updates the final settlement table TBL215 (Step S139). That is, the settlement processing unit 28 associates the settlement person ID, the payment code, and the settlement amount (that is, the usage amount in the transaction), and stores them in the settlement settlement table TBL 215 as the settlement settlement information.

  In addition, the payment method (payment timing) from the credit card company to the user company is not limited. For example, a fee according to the amount of advance payment may be paid from the credit company to the user company at the time of advance payment, and payment (refund etc.) may be made between the credit company and the user company at the time of correction settlement. . Note that “at the time of advance payment” may be a timing at which advance payment is performed, or may be, for example, a closing date of a user's credit card. Further, the payment from the credit card company to the user company may not be performed at the time of the advance settlement, and the payment amount may be paid from the credit card company to the user company at the time of the corrected settlement.

  FIG. 6C shows an electronic ticket management image using an application when the second user performs a transaction using the transferred electronic ticket. The second user inputs from the mobile terminal 5 an instruction for payment by inputting an amount corresponding to a taxi fare. In response to the input, a payment request is transmitted to the user company terminal 7 of the taxi company, and the user company terminal 7 inputs to instruct payment. In response to the input, a settlement request is transmitted to the electronic ticket management device 2. The payment request may be made verbally to the user of the user company terminal 7 from the second user. When the electronic ticket management apparatus 2 authenticates the taxi company that is the user company, a payment code is issued, and when the second user inputs the payment code from the application, the electronic ticket management apparatus 2 performs a settlement process.

[Operational effects of this embodiment]
Next, the effect of the electronic ticket management apparatus 2 described above will be described.

  In the electronic ticket management apparatus 2, the right holder of the electronic ticket is changed based on a transfer request from the first user who is a settlement person. When the second user who is the right of use uses the electronic ticket within the upper limit of use, the use of the electronic ticket is permitted, and the difference between the upper limit of use and the amount of use is returned to the first user. For this reason, as the second user's usage amount is lower and the electronic ticket usage upper limit is higher, a larger amount is returned to the first user. Therefore, even when the first user sets the usage upper limit high in the usage upper limit setting stage or when the purchase price of the second user is low, there is no penalty for the first user. As a result, transfer of the electronic ticket can be promoted, and as a result, use of the electronic ticket can be promoted.

  Further, in the electronic ticket management device 2, the electronic ticket information includes information specifying the use of the electronic ticket, and the transaction management unit 27 uses the electronic ticket within the upper limit of use by the second user who is the right of use. In some cases, the transaction using the electronic ticket is permitted only when the purpose of use is within the scope of the application. Thereby, the use application of an electronic ticket will be limited and the management burden of an electronic ticket can be reduced.

  In addition, information specifying the use of the electronic ticket stored in the issued ticket management table TBL 213, that is, a ticket ID is set (changed) in accordance with the purpose of use designation from the first user who is the settler of the issued electronic ticket. ) Is further provided. Thereby, it is possible to prevent the electronic ticket from being used for a purpose not intended by the first user who is a settlement person. As a result, convenience for the settlement person is improved, and the use of electronic tickets can be further promoted.

  In the electronic ticket management device 2, the electronic ticket information further includes the validity period of the electronic ticket, and the transaction management unit 27 is used when the second user who is the right of use uses the electronic ticket within the upper limit of use. The transaction using the electronic ticket is permitted only when the use date is within the valid period. Thereby, the period during which the electronic ticket is used is limited, and the management burden of the electronic ticket can be reduced. In addition, since the valid period can be set by the settlement person, it is possible to urge the use of the electronic ticket during the period intended by the settlement person. As a result, convenience for the settlement person is improved, and the use of electronic tickets can be further promoted.

  In the electronic ticket management apparatus 2, the settlement processing unit 28 may make a pre-settlement for the usage upper limit amount before the settlement process, and may perform a correction process according to the actual usage amount in the settlement process. Good. By making a pre-settlement for the upper limit amount of use, the purchasing power of the electronic ticket and the settlement completion amount can be linked, and settlement can be performed more in line with the actual situation. In other words, when an electronic ticket with a usage upper limit amount is issued, the use of the electronic ticket makes it possible to purchase products and the like up to the usage upper limit amount. For this reason, it is possible to match the purchasing power (maximum purchase amount) of the electronic ticket with the amount for which settlement is performed by making a pre-payment for the upper limit of use.

  As mentioned above, although embodiment was described, this indication is not limited to the said embodiment. For example, the payment processing unit 28 has been described as performing pre-settlement for the usage upper limit amount in the previous stage of the payment processing, and performing correction processing according to the actual usage amount in the payment processing, but is not limited thereto. That is, the settlement processing unit 28 may perform post-settlement for the amount of money used in the settlement process without performing the pre-settlement. As a result, the payment only needs to be made once after the use amount of the electronic ticket is determined, and the payment can be simplified. Even when the settlement process is performed only once (post-settlement), the right corresponding to the difference between the usage upper limit and the usage amount is substantially the first by performing the payment for the usage amount. It remains in the user (reduced). That is, of the right to use the electronic ticket, the difference between the usage upper limit and the usage amount is returned to the first user.

  FIG. 7 is a sequence diagram showing an execution procedure of the electronic ticket management method according to the modified example in which post-payment is performed for the amount of money used. Each process shown in FIG. 7 is basically the same as each process in the case of performing the pre-settlement shown in FIG. 5, and steps S101, S105 to S131, and S135 to 139 in FIG. , S205 to S231 and S235 to 239, respectively. On the other hand, the pre-settlement process (step S103) is performed in response to the electronic ticket issue request in the process of FIG. 5, whereas the pre-settlement process is not performed in the process of FIG. Further, instead of the modified settlement process (step S133) performed in FIG. 5, a settlement process (step S234) for performing a subsequent settlement is performed in FIG. As described above, in the process according to the modification shown in FIG. 7, a settlement (post-settlement) is performed only once in the settlement process.

  2 ... Electronic ticket management device, 23 ... Issuing unit, 24 ... Usage management unit, 26 ... Transfer management unit, 27 ... Transaction management unit, 28 ... Settlement processing unit, TBL213 ... Issued ticket management table.

Claims (7)

A storage unit for storing electronic ticket information including an upper limit of use amount of the electronic ticket, a right holder, and a settlement person;
A transfer management unit that acquires a transfer request from the settlement person and changes the right holder of the electronic ticket information stored in the storage unit to a person specified in the transfer request;
Only when the right holder uses the electronic ticket within the usage limit, a transaction management unit that permits transactions using the electronic ticket;
When the transaction management unit permits a transaction using the electronic ticket, the difference between the upper limit of the electronic ticket used for the transaction and the actual usage amount of the electronic ticket is the settlement of the electronic ticket. An electronic ticket management apparatus comprising: a payment processing unit that performs a payment process so as to be returned to a person. The electronic ticket information further includes information specifying the use of the electronic ticket,
The transaction management unit, when the right holder uses the electronic ticket within the usage upper limit, further restricts the usage purpose to be within the range of the usage, and uses the electronic ticket. The electronic ticket management device according to claim 1, wherein   A usage management unit that obtains a usage purpose designation from the settlement person and sets information specifying the usage of the electronic ticket information stored in the storage unit to the content designated in the usage purpose designation; The electronic ticket management device according to claim 2. The electronic ticket information further includes a validity period of the electronic ticket,
In the case where the right holder uses the electronic ticket within the usage upper limit, the transaction management unit further restricts the transaction using the electronic ticket only when the usage date is within the validity period. The electronic ticket management device according to claim 1, wherein the electronic ticket management device permits.   5. The payment processing unit according to any one of claims 1 to 4, wherein the payment processing unit performs a pre-settlement for the usage upper limit in a stage before the payment processing, and performs a correction process according to an actual usage amount in the payment processing. The electronic ticket management device according to one item.   The electronic ticket management device according to any one of claims 1 to 4, wherein the settlement processing unit performs post-settlement for the usage amount in the settlement processing. An electronic ticket management method performed by an electronic ticket management device,
Storing electronic ticket information including the maximum amount of use of the electronic ticket, the right holder, and the settlement person;
Obtaining a transfer request from the settlement person, and changing the right holder of the electronic ticket information to a person designated in the transfer request;
Only when the right holder uses the electronic ticket within the upper limit of use, allowing a transaction using the electronic ticket;
When a transaction using the electronic ticket is permitted in the permitting step, a difference between the upper limit of the electronic ticket used for the transaction and an actual usage amount of the electronic ticket is the amount of the electronic ticket. An electronic ticket management method comprising: performing a settlement process so as to be returned to a settlement person.

Images