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

Description

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

Patent Document 1 discloses a storage device that stores a list defining the attributes of each person related to a predetermined area, and when a regional promotion ticket issuance request is received from a predetermined device, information about the issuance candidate indicated by the issuance request is provided. Identify the attribute in the list, determine the premium amount of the regional promotion ticket to be issued to the person who wishes to issue it according to the type of the specified attribute, and purchase the determined premium amount as the purchase amount desired by the person who wishes to issue it A regional promotion ticket management system is disclosed that includes a computing device that executes a predetermined issuing process for a regional promotion ticket with a denomination added to the value of the regional promotion ticket.

JP 2018-018216 A

The present disclosure provides methods and apparatus that are effective in both increasing local revenue and stimulating local consumption.

An electronic ticket management method according to one aspect of the present disclosure is an electronic ticket management method executed by an electronic ticket management device, in which a ticket issuing unit receives donations from residents outside the region to a local government in a predetermined region. In this case, issuing an electronic gift ticket to which the user condition and the area restriction condition are attached, the store registration unit registering the store as a member store in accordance with the registration request from the store, The change department changes the user conditions of the gift electronic ticket according to the transfer request of the gift gift electronic ticket, and the payment processing department, the person who intends to pay the expenses at the member store with the gift gift electronic ticket Judging whether payment is possible based on whether the user conditions for the gift electronic ticket are satisfied and whether the target of payment satisfies the regional constraint conditions, and if it is determined that payment is possible, the local government to the affiliated store and processing payment for the cost of

An electronic ticket management device according to another aspect of the present disclosure provides a gift electronic gift giving user conditions and regional constraint conditions when donations are made by residents outside the region to local governments in a predetermined region. A ticket issuing unit that issues tickets, a store registration unit that registers the store as a member store according to a registration request from the store, and a user condition change that changes the user conditions of the gift electronic ticket according to the gift electronic ticket transfer request. Department, and whether the person who intends to pay the fee at the member store with the gift electronic ticket satisfies the user conditions, and whether the payment target satisfies the regional constraint conditions. and a payment processing unit that performs payment processing from the local government to the member store when it is determined that payment is possible.

Advantageous Effects of Invention According to the present disclosure, it is possible to provide a method and apparatus that are effective in achieving both increased local revenue and stimulating local consumption.

1 is a block diagram illustrating a functional configuration of an electronic ticket management system; FIG. It is a table which illustrates the content of a gift database. 4 is a table illustrating the contents of a donation database; 4 is a table illustrating the contents of a ticket database; It is a table which illustrates the content of a store database. 1 is a block diagram illustrating the hardware configuration of an electronic ticket management system; FIG. It is a flow chart which illustrates a return gift arrangement procedure. 10 is a flowchart illustrating a procedure for issuing a gift electronic ticket; FIG. 11 is a flow chart illustrating a normal electronic ticket issuing procedure; FIG. It is a flowchart which illustrates the registration procedure of a store. FIG. 10 is a flowchart illustrating a procedure for settlement using a gift electronic ticket; FIG. 10 is a flow chart illustrating a procedure for settlement using a normal electronic ticket;

Hereinafter, embodiments will be described in detail with reference to the drawings. In the explanation, the same reference numerals are given to the same elements or elements having the same function, and duplicate explanations are omitted.

[Electronic ticket management system]
The electronic ticket management system 1 shown in FIG. 1 is a system that executes electronic ticket issuance and electronic payment processing using the electronic ticket. An electronic ticket is electronic data that defines the right to use a predetermined amount of money to purchase goods or services. An electronic ticket is provided with at least a unique ID, user conditions, payment conditions, and payment information.

User conditions shall determine the person who has the right to make a payment using the electronic ticket (hereinafter referred to as "user"). The payment terms define, for example, a maximum payment amount. Payment information is information for electronically executing payment by a payment source. A specific example of the payment information is information (for example, bank account number or credit card number) for receiving payment (electronic payment) by the payment source.

The electronic ticket management system 1 manages at least two types of electronic tickets: gift electronic tickets and normal electronic tickets. A gift electronic ticket is an electronic ticket that is issued as a gift in return for the donation made by residents outside the region (for example, so-called "hometown tax") to a local government in a predetermined region. A normal electronic ticket is an electronic ticket that is issued according to a request from a ticket issuer, regardless of hometown tax donation. For example, the electronic ticket management system 1 has a hometown tax payment acceptance device 200 and an electronic ticket management device 100 .

The hometown tax payment acceptance device 200 performs the above-mentioned donation acceptance and payment processing, and arranges gifts in return for the donation. The hometown tax payment acceptance device 200 includes, as a functional configuration (hereinafter referred to as "functional blocks"), a gift database 214, a donation reception unit 211, a donation information database 212, a donation settlement unit 213, and a gift arrangement. 215.

The gift database 214 stores the content of the gifts for each local public entity to which donations are made. The gift database 214 is built in advance according to the agreement between each local government and the operating company of the hometown tax payment acceptance device 200 .

For example, as shown in FIG. 2, the gift database 214 stores the donation destination ID, the type of gift, and detailed information on the gift in association with each other. The donation destination ID is an identification code of the local government. A specific example of the donation recipient ID is a local government code determined by the Ministry of Internal Affairs and Communications. The return gift type is a predetermined type of return gift item. The return gift type includes the above-described return gift electronic ticket.

The return gift detailed information includes at least return conditions (conditions for determining the amount of return gifts according to the donation amount). Specific examples of return conditions for gift electronic tickets include an electronic ticket of 2,000 yen for a donation of 10,000 yen, an electronic ticket of 5,000 yen for a donation of 20,000 yen, and the like. If the type of gift in return is an electronic ticket, the detailed gift in return information includes payment information and regional constraints on the electronic ticket.

The payment information is information for executing electronic payment with a local government as the payment source. A specific example of the payment information is a bank account number of a local government. The area constraint restricts the subject of electronic ticket payment to those associated with the jurisdiction of the local government. A subject related to a jurisdiction means a subject for which at least a portion of the monies paid to the subject is income for residents (including businesses, etc.) of the jurisdiction. Concrete examples of the region constraint include the provision place constraint, the store constraint, the name constraint, and the company constraint, which will be described below.

The place-of-service constraint limits the e-ticket's payment of costs to those offered within its jurisdiction. The jurisdictional area in the provision place constraint may be represented by a range of latitude and longitude, for example, or may be represented by a donation destination ID.

The store constraint limits the stores at which electronic ticket payments can be made to stores associated with the jurisdiction. A store constraint may be represented by, for example, a list of one or more store names or identities.

The name constraint restricts the payment of fees by electronic tickets to those named in relation to the jurisdiction. A name constraint may be represented, for example, by a list of one or more names. A specific example of a name associated with a jurisdictional area is a name commonly given to goods produced in the jurisdictional area or services provided in the jurisdictional area (eg, regional collective trademark). Also, the name associated with the jurisdiction may be the unique name given to the company's products or services by a company based in the jurisdiction.

Even if the goods are provided outside the jurisdiction, if the goods are produced in the jurisdiction, at least a portion of the monies paid for the goods may become the income of the residents of the jurisdiction. Even if the services are provided outside the jurisdiction, if the provider of the services is a business traveler from within the jurisdiction to outside the jurisdiction, at least a portion of the money paid for such services shall Can be income for residents.

The company constraint limits the payment of costs to those provided by companies associated with the jurisdiction. A company constraint may be represented, for example, by a list of one or more company names or identities.

Even if the goods are provided outside the jurisdiction, at least a portion of the monies paid for the goods will go to the income of the residents of the jurisdiction if the goods are produced by companies associated with the jurisdiction. can be. Even if the service is provided outside the jurisdiction, if the service is provided remotely by a company within the jurisdiction, at least a portion of the monies paid for the service will be a resident of the jurisdiction. income.

The region constraint may be a combination of two or more of the provision location constraint, the store constraint, the name constraint, and the company constraint.

Returning to FIG. 1 , the donation reception unit 211 receives the application for donation from the donor terminal 310 . The donor terminal 310 is a terminal used by the donor. The donor terminal 310 may be a stationary personal computer, a notebook computer, a tablet computer, or a portable terminal such as a smart phone. For simplification, only one donor terminal 310 is shown in FIG.

The donation reception unit 211 displays on the donor terminal 310 a list of local governments that can be donation destinations and gifts in return for the donation, based on the gift database 214 . For example, the donation receiving unit 211 displays the above list on a general-purpose web browser installed in the donor terminal 310, an application dedicated to hometown tax payment, or the like.

The donor applies for donation to the donor terminal 310 based on the list display. For example, the donor selects the local government to which the donation is to be made, and inputs the donation amount, payment information for the donation, and the recipient of the gift in return using the web browser or application. The settlement information is information for electronically executing the payment of the donation from the donor to the donation destination (executing the electronic settlement of the donation). Specific examples of payment information include bank account numbers and credit card numbers. Specific examples of the return gift destination include the mailing address of the item (for example, the donor's address) or the transmission destination of the electronic ticket (for example, the donor's e-mail address).

The donation reception unit 211 acquires the donation application details and the donor's identification information from the donor terminal 310 in response to the application operation on the donor terminal 310 . Hereinafter, the information that the donation receiving unit 211 acquires from the donor terminal 310 will be collectively referred to as "donation information".

The donation information database 212 stores donation information acquired by the donation reception unit 211 from the donor terminal 310 . For example, as shown in FIG. 3, the donation information database 212 includes a donor ID, the donation destination ID, the donation amount, the payment information, the return gift destination, the payment status, and the return gift arrangement status. are associated with each other and stored. Donor ID is a donor's identification code. A specific example of the donation destination ID is an account entered by the donor at the time of login. The settlement status indicates whether electronic settlement of the donation has been completed. "Not yet" in the figure indicates that the electronic settlement of the donation has not been completed, and "Completed" indicates that the electronic settlement of the donation has been completed. The return gift arrangement status indicates whether or not arrangements for the return gift corresponding to the payment of the donation have been completed. "Unfinished" in the figure indicates that the return gift has not yet been arranged, and "Done" indicates that the return gift has been arranged.

Returning to FIG. 1 , the donation settlement unit 213 executes electronic settlement processing for donations according to the settlement information of the donation information stored in the donation information database 212 . For example, the donation settlement unit 213 requests the settlement agency server 600 to execute electronic settlement of the donation according to the settlement information stored in the donation information database 212 . The settlement agency server 600 is a server of a bank or a credit card company, and performs electronic settlement of the donation. The execution of the electronic payment processing by the donation receiving unit 211 in this manner includes the donation receiving unit 211 making the payment service provider server 600 perform the electronic payment on behalf of the donation receiving unit 211 .

The donation settlement unit 213 changes the settlement status of the donation information database 212 from "uncompleted" to "completed" in response to the completion of the electronic settlement agency by the settlement agency server 600 . For the sake of simplification, FIG. 1 shows only one settlement agency server 600 , but in reality a large number of settlement agency servers 600 can be connected to the hometown tax payment acceptance device 200 .

The return gift arrangement unit 215 executes processing for arranging return gifts according to the donation amount in response to the completion of the electronic payment processing by the donation settlement unit 213 (completion of the electronic payment by the settlement agency server 600). For example, if the gift is an article, the gift arrangement unit 215 requests the company providing the gift to send the gift to the delivery destination (above-mentioned gift delivery destination).

If the gift is the gift electronic ticket, the gift arrangement unit 215 requests the electronic ticket management device 100 to issue the gift electronic ticket. For example, the return gift arrangement unit 215 refers to the donation information database 212 and the return gift database 214, and sends the donation amount, the donor ID, the return gift destination, and the return gift detailed information to the electronic ticket management device 100. Then, the electronic ticket management device 100 is requested to issue the return gift electronic ticket for the amount corresponding to the donation amount.

After the return gift arrangement processing is completed, the return gift arrangement unit 215 changes the return gift arrangement status of the donation information database 212 from "unfinished" to "finished". The electronic ticket management device 100 issues an electronic ticket in accordance with the ticket issue request, and executes electronic settlement processing for payment using the electronic ticket. The electronic ticket management device 100 provides the electronic ticket with constraints specified when issuing the ticket issuance request. In addition, the electronic ticket management device 100 returns the difference between the maximum payment amount of the electronic ticket and the actual payment amount to the payment source.

The electronic ticket management device 100 issues a gift electronic ticket to which a user condition and an area constraint condition are added when a local public body in a predetermined area receives a donation from a resident outside the area; Registering the store as a member store in accordance with the registration request from the store, changing the user conditions of the gift electronic ticket in accordance with the gift gift electronic ticket transfer request, and paying the fee at the member store with the gift gift electronic ticket Judging whether or not the person who intends to pay satisfies the user conditions and whether the subject of payment satisfies the regional restrictions It is configured to perform payment processing of expenses to

The electronic ticket management device 100 is used by a person who intends to issue a normal electronic ticket to which a user condition is attached in accordance with an electronic ticket issuing request from a ticket issuer, and to pay expenses at a member store with the normal electronic ticket. determining whether or not payment is possible based on whether or not the customer conditions are satisfied, and if it is determined that payment is possible, processing the payment from the ticket issuer to the member store. good. For example, the electronic ticket management device 100 has a ticket issuing unit 111, a ticket database 112, a user condition changing unit 113, a store registration unit 114, a store database 115, and a payment processing unit 116 as functional blocks.

A ticket issuing unit 111 issues an electronic gift gift ticket to which a user condition and an area constraint condition are attached when a local public body in a predetermined area receives a donation from a resident outside the area. For example, the ticket issuing unit 111 issues the return gift electronic ticket in accordance with the return gift electronic ticket issuance request from the return gift arrangement unit 215 .

As described above, the return gift arrangement unit 215 requests the issuance of a return gift electronic ticket when a donation is received from a resident outside the region to a local government in a predetermined area. Therefore, issuing the return gift electronic ticket in accordance with the return gift electronic ticket issuance request from the return gift arrangement unit 215 is effective when the local government in the predetermined area receives donations from residents outside the area. This is an example of issuing a ticket.

For example, the ticket issuing unit 111 generates user conditions, payment conditions, and payment information based on the donation amount, the donor ID, the return gift destination, and the return gift detailed information transmitted from the return gift arrangement unit 215. , and issue a gift electronic ticket to which regional restrictions are applied. The user conditions define the identification code (hereinafter referred to as "user ID") of the user who has the right to make a payment using the gift electronic ticket. The payment terms determine the maximum payment amount according to the donation amount. Payment information is information for electronically executing payment by a local government. As described above, the locality constraint limits the payment of electronic ticket costs to those associated with the jurisdiction of the local government.

For example, the ticket issuing unit 111 generates a ticket ID unique to the gift electronic ticket, and associates the donor ID as the user ID with the ticket ID. Further, the ticket issuing unit 111 associates the maximum payment amount based on the donation amount and the return condition of the detailed return item information with the ticket ID, and associates the payment information of the detailed return item information with the ticket ID. Furthermore, the ticket issuing unit 111 associates the above-mentioned area constraint condition of the detailed gift item information with the ticket ID. As described above, a gift electronic ticket is issued in which the ticket ID, the user ID, the maximum payment amount, the settlement information, and the regional constraint are associated with each other.

The ticket issuing unit 111, in order to issue the return gift electronic ticket, executes electronic payment in advance from the local public body that is the source of payment to the management company of the electronic ticket management device 100 for the upper limit of payment. 600 may be requested. The payment agency server 600 performs this electronic payment on behalf of the electronic ticket management apparatus 100, thereby pooling electronic money up to the upper limit of payment. In this case, the electronic ticket management device 100 associates the ticket ID with payment information for performing electronic payment with the above-mentioned management company, which has pooled the maximum payment amount of electronic money, as the payment source. The payment information for electronic payment with the local government as the payment source is hereinafter referred to as "post-payment payment information", and the payment information for electronic payment with the above management company as the payment source is referred to as "advance payment payment information for

The ticket issuing unit 111 transmits the issued gift electronic ticket to the user terminal 330 . For example, the ticket issuing unit 111 converts the issued electronic ticket into a readable electronic code such as a one-dimensional code or a two-dimensional code (for example, QR code (registered trademark)) and transmits it to the user terminal 330 . Note that transmitting the electronic code to the user terminal 330 includes transmitting to the user terminal 330 a link of a website displaying the electronic code.

A user terminal 330 is a terminal used by a user. The user terminal 330 may be a stationary personal computer, a notebook computer, a tablet computer, or a mobile terminal such as a smart phone.

For convenience of explanation, the user terminal 330 is distinguished from the donor terminal 310, but the user terminal 330 and the donor terminal 310 may be the same terminal. For example, in the above example, the user terminal 330 is the same as the donor terminal 310 because the donor ID is the user ID of the gift electronic ticket. In this case, the ticket issuing unit 111 transmits the return gift electronic ticket to the donor terminal 310 according to the donor's e-mail address indicated by the return gift destination.

The ticket issuing unit 111 may issue a normal electronic ticket to which a user condition is added according to an electronic ticket issuing request from a ticket issuer. For example, the ticket issuing unit 111 acquires an electronic ticket issuing request from the ticket issuer terminal 320 .

The ticket issuer terminal 320 is a terminal used by the ticket issuer. The ticket issuer terminal 320 may be a stationary personal computer, a notebook computer, a tablet computer, or a portable terminal such as a smart phone. For the sake of simplification, only one ticket issuer terminal 320 is shown in FIG.

The ticket issuing unit 111 displays on the ticket issuer terminal 320 an input screen for information necessary for issuing a normal electronic ticket. For example, the ticket issuing unit 111 sends user conditions, payment conditions, payment information, and individual constraints to a general-purpose web browser installed in the ticket issuer terminal 320 or an application dedicated to the issuer/user of electronic tickets. Display the input screen. The user conditions define the identification code (hereinafter referred to as "user ID") of the user who has the right to make a payment with a normal electronic ticket. The terms of payment determine the upper limit of payment. Payment information is information for electronically executing payment by a ticket issuer. Specific examples of payment information include the issuer's bank account number or credit card number. The individual constraint is a constraint arbitrarily set by the issuer. Specific examples of individual constraints include conditions that limit the type of payment object (for example, the type of goods or services), conditions that determine the deadline for payment, and the like.

For example, the ticket issuer inputs the user ID, maximum payment amount, payment information, and individual constraint conditions according to the input screen. The ticket issuing unit 111 issues a normal electronic ticket to which user conditions, payment conditions, payment information, and individual constraint conditions are attached based on the input on the input screen by the ticket issuer. For example, the ticket issuing unit 111 generates a ticket ID unique to a normal electronic ticket, and associates the ticket ID with the user ID, maximum payment amount, payment information, and individual constraint conditions input on the input screen. As described above, a normal electronic ticket is issued in which the ticket ID, user ID, maximum payment amount, and settlement information are associated with each other.

In order to issue a normal electronic ticket, the ticket issuing unit 111 instructs the settlement agency server 600 in advance to execute electronic settlement for paying the upper limit of payment from the ticket issuer of the payment source to the management company of the electronic ticket management device 100. may be requested. The payment agency server 600 performs this electronic payment on behalf of the electronic ticket management apparatus 100, thereby pooling electronic money up to the upper limit of payment. In this case, the electronic ticket management device 100 associates the ticket ID with payment information for performing electronic payment with the above-mentioned management company, which has pooled the maximum payment amount of electronic money, as the payment source. The payment information for electronic payment with the ticket issuer as the payment source is hereinafter referred to as "post-payment payment information", and the payment information for electronic payment with the management company as the payment source is referred to as "pre-payment payment information”.

The ticket issuing unit 111 transmits the issued normal electronic ticket to the user terminal 330 . For example, the ticket issuing unit 111 converts the issued normal electronic ticket into a readable electronic code such as a one-dimensional code or a two-dimensional code (for example, QR code (registered trademark)) and transmits it to the user terminal 330 .

For convenience of explanation, the user terminal 330 is distinguished from the ticket issuer terminal 320, but the user terminal 330 and the ticket issuer terminal 320 may be the same terminal. For example, when issuing a normal electronic ticket issuance request, the user terminal 330 is the same as the ticket issuer terminal 320 when the issuer identifies himself/herself as a user. For the sake of simplification, only one user terminal 330 is shown in FIG.

The ticket database 112 stores electronic tickets issued by the ticket issuer 111 . For example, as shown in FIG. 4, the ticket database 112 stores ticket IDs, user IDs, maximum payment amounts, payment information, and constraints (regional constraints or individual constraints) in association with ticket types and statuses. do. The ticket type indicates whether the ticket is a gift electronic ticket or a normal electronic ticket.

Status indicates the current state of the electronic ticket. "Issued" in the status in FIG. 4 indicates that the electronic ticket has been issued. “Sent” indicates that the electronic ticket has been sent to the user terminal 330 . “Received” indicates that the electronic ticket has been received by the user terminal 330 . "Used" indicates that the electronic ticket has been used for payment.

The ticket issuing unit 111 sets the status of the electronic ticket to "issued" when the electronic ticket is recorded in the ticket database 112, and changes the status from "issued" to "transmitted" when the electronic ticket has been transmitted to the user terminal 330. , when the receipt of the electronic ticket by the user terminal 330 is confirmed, "sent" is changed to "received".

Returning to FIG. 1, the user condition change unit 113 changes the user condition of the return gift electronic ticket in accordance with the return gift electronic ticket transfer request. The user condition changing unit 113 may change the user condition of the normal electronic ticket according to the normal electronic ticket transfer request. For example, the user condition changing unit 113 changes the user ID of the electronic ticket (return gift electronic ticket or normal electronic ticket) to the user ID of the transfer source in accordance with the transfer request from the user terminal 330 used by the transfer source user to the user ID of the transfer destination.

The user condition changing unit 113 changes the user ID of the electronic ticket from the transfer source user ID to the transfer destination user ID in accordance with the transfer request from the user terminal 330 used by the transfer destination user. good too. The user condition changing unit 113 changes the electronic ticket according to both the transfer request from the user terminal 330 used by the transfer source user and the transfer request from the user terminal 330 used by the transfer destination user. may be changed from the user ID of the transfer source to the user ID of the transfer destination. Note that the user condition change unit 113 does not necessarily change the user condition after issuing the gift electronic ticket, and may change the user condition when issuing the gift electronic ticket. For example, in accordance with the transfer request from the donor terminal 310, the user condition changing unit 113 changes the user ID that the ticket issuing unit 111 associates with the ticket ID of the gift electronic ticket to the ID of a person different from the donor. good too.

The donor may input a transfer request to the donor terminal 310 in the donation application operation. For example, the donor sends the identification information (hereinafter referred to as "other ID") of a person other than the donor (hereinafter referred to as "other person") and the electronic ticket to the other person as the recipient of the return gift. You may also enter a destination (e.g., someone else's email address). In this case, the user condition changing unit 113 acquires the contents of the return gift delivery destination as a transfer request from the return gift arrangement unit 215, and the ticket issuing unit 111 assigns the user ID associated with the ticket ID of the return gift electronic ticket to the donor. Change your ID to another company's ID.

The store registration unit 114 registers the store as a member store in accordance with a registration request from the store. For example, the store registration unit 114 acquires information on the store requesting registration from the store terminal 500 and registers the acquired information as member store information. A store terminal 500 is a terminal used in a store. The store terminal 500 may be a stationary personal computer, a notebook computer, a tablet computer, or a mobile terminal such as a smart phone. For the sake of simplification, only one store terminal 500 is shown in FIG.

The store database 115 stores information on member stores registered by the store registration unit 114 . For example, as shown in FIG. 5, the store database 115 stores store IDs, store types, store names, company IDs, locations, region IDs, and settlement information in association with each other. The store ID is unique identification information of the store. The company ID is unique identification information of the company that operates the store. The belonging area ID is unique identification information of the area to which the store belongs (area including the location of the store). The belonging area ID is, for example, an identification code of a local government (for example, the above-described local government code). The settlement information is information for executing electronic settlement with the store as the payee. A specific example of the payment information is the store's bank account number.

Returning to FIG. 1, the payment processing unit 116 determines whether a person who intends to pay the fee at a member store with the gift electronic ticket (hereinafter referred to as the "applicant") satisfies the user conditions, It determines whether or not payment is possible based on whether or not the payment object satisfies the area constraint conditions, and if it is determined that the payment is possible, the local government performs the payment processing of the expenses to the member store.

For example, the payment processing unit 116 collects the identification information of a person who intends to pay the fee at a member store with the gift electronic ticket (hereinafter referred to as "unauthenticated user ID") and the gift electronic ticket. An ID (hereinafter referred to as an “unauthenticated ticket ID”), a store ID of a member store, and information on a payment target are acquired. The information on the target of payment of the cost includes at least the amount of the cost. The information of the target of payment may include the name of the target of payment of the cost, or the identification information (company ID) of the company that provides the target of payment of the cost.

Here, the gift electronic ticket is used, for example, in the following manner.
(Method 1)
The store terminal 500 reads the information of the payment target. Further, the store terminal 500 reads the unauthenticated ticket ID (for example, the electronic code) displayed by the user terminal 330 and the unauthenticated user ID displayed by the user terminal 330 .
(Method 2)
The user terminal 330 reads the store ID of the member store and the information of the payment target. The user terminal 330 may acquire the information on the payment target based on the user's input instead of reading the information on the payment target.

In the case of method 1, the payment processing unit 116 acquires an unauthenticated ticket ID, a shop ID, an unauthenticated user ID, and information on a payment target from the shop terminal 500 . In the case of method 2, the payment processing unit 116 acquires from the user terminal 330 an unauthenticated ticket ID, a store ID, an unauthenticated user ID, and information on a payment target.

If the unauthenticated ticket ID and the unauthenticated user ID are associated in the ticket database 112, the payment processing unit 116 determines that the applicant satisfies the user conditions, and determines that the unauthenticated ticket ID and the unauthenticated user If the user ID for authentication is not associated with the ticket database 112, it is determined that the applicant does not satisfy the user conditions.

If the prospective user satisfies the user conditions, the payment processing unit 116 determines whether or not the target of payment satisfies the regional constraint based on at least the information on the member store or the information on the target of payment of the charge. For example, if the region constraint is the provision region constraint, the payment processing unit 116 determines whether the cost payment target satisfies the region constraint based on whether the location of the member store satisfies the provision region constraint. judge.

For example, if the supply location constraint is represented by a donation destination ID, the payment processing unit 116 will determine if the affiliated region ID associated with the store ID of the affiliated store in the store database 115 matches the donation destination ID. , it is determined that the target of payment of the expense satisfies the area constraint, and if the belonging area ID does not match the donation destination ID, it is determined that the target of payment of the expense does not satisfy the area constraint.

If the provision location constraint is represented by a range based on latitude, longitude, etc. (hereinafter referred to as a “donation destination range”), the payment processing unit 116 determines the address associated with the store ID of the member store in the store database 115. is located within the range of the donation destination, it is determined that the target of payment of expenses satisfies the regional constraint, and if the location is not within the range of the donation destination, the target of payment of expenses does not satisfy the regional constraint. I judge.

If the regional constraint is the store constraint, the payment processing unit 116 determines whether or not the payment target satisfies the region constraint based on whether the member store satisfies the store constraint. When the store constraint condition is represented by the name of the store (hereinafter referred to as “region-related store name”), the payment processing unit 116 determines that the store name associated with the store ID of the member store in the store database 115 is region-related. If the store name matches the store name, it is determined that the payment target satisfies the region constraint, and if the store name does not match the region-related store name, it is determined that the charge payment target does not satisfy the region constraint. .

When the region constraint is the name constraint, the payment processing unit 116 determines whether the cost payment target satisfies the region constraint based on whether the name attached to the cost payment target satisfies the name constraint. determine whether or not When the name constraint condition is represented by a name (hereinafter referred to as "area-related name"), the payment processing unit 116 determines that the name of the fee payment object matches the area-related name. If it is determined that the constraint is satisfied, and if the name of the target of payment does not match the region-related name, it is determined that the target of payment of the cost does not satisfy the region constraint.

If the region constraint is the company constraint, the payment processing unit 116 determines whether the target of payment satisfies the region constraint based on whether the company providing the target of payment satisfies the company constraint. determine whether or not When the company constraint is represented by company identification information (hereinafter referred to as “area-restricted company ID”), the payment processing unit 116 determines that the company ID associated with the store ID of the member store in the store database 115 is a region. If the company ID matches the restricted company ID, it is determined that the cost payment target satisfies the region constraint, and if the company ID does not match the region restricted company ID, it is determined that the cost payment target does not satisfy the region constraint. do.

If it is determined that payment is possible, the payment processing unit 116 executes payment processing from the local government to the member store. The payment processing unit 116 returns the difference between the maximum payment amount of the gift electronic ticket (the maximum payment amount associated with the ticket ID in the ticket database 112) and the cost to the local government that is the source of the payment. payment processing.

If the payment information of the gift electronic ticket (the payment information associated with the ticket ID in the ticket database 112) is the payment information for post-payment, the payment processing unit 116 collects the above-mentioned expenses from the local public body that is the source of payment. The settlement agent server 600 is requested to execute electronic settlement for payment to the member store of the payment destination. For example, the payment processing unit 116 executes the electronic payment based on the payment information associated with the ticket ID in the ticket database 112 and the payment information associated with the store ID of the member store in the store database 115. A request is made to the agency provider server 600 . In response to this, the settlement agency server 600 performs the electronic settlement as a proxy. According to this settlement, the difference remains with the local government, so the difference is returned to the local government.

If the payment information of the gift electronic ticket is payment information for pre-payment, the payment processing unit 116 pays the above-mentioned expenses out of the electronic money pooled for the gift electronic ticket to the member store as the payment destination. A request is made to the payment agency operator server 600 to execute electronic payment and electronic payment for returning the difference to the local government of the payment source. In response to this, the settlement agency server 600 executes the above two electronic settlements.

When a normal electronic ticket is used for payment at a member store, the payment processing unit 116 determines whether or not payment can be made based on at least whether the user satisfies the user conditions. Settlement processing may be performed with the ticket issuer as the payment source. In the use of the normal electronic ticket, the processing until it is determined whether or not the user condition is satisfied is the same as in the case of the gift electronic ticket, so the explanation is omitted.

If the user satisfies the user conditions, the payment processing unit 116 determines whether or not the payment object satisfies the individual constraint conditions based on at least the member store information or the payment object information. If the conditions are met, it is determined that the payment is possible.

If it is determined that the payment can be made, the payment processing unit 116 calculates the difference between the maximum payment amount of the normal electronic ticket (the maximum payment amount associated with the ticket ID in the ticket database 112) and the payment amount for the payment object at the payment source. Settlement processing is performed so as to return to a certain ticket issuer.

When the payment information of the normal electronic ticket (the payment information associated with the ticket ID in the ticket database 112) is the payment information for post-payment, the payment processing unit 116 receives the payment amount from the ticket issuer as the payment source. The settlement agency server 600 is requested to execute electronic settlement for payment to the previous member store.

For example, the payment processing unit 116 executes the electronic payment based on the payment information associated with the ticket ID in the ticket database 112 and the payment information associated with the store ID of the member store in the store database 115. A request is made to the agency provider server 600 . In response to this, the settlement agency server 600 performs the electronic settlement as a proxy. According to this settlement, the difference remains with the ticket issuer, so the difference is returned to the ticket issuer.

When the payment information of the normal electronic ticket is the payment information for advance payment, the payment processing unit 116 performs electronic payment for paying the payment amount of the electronic money pooled for the normal electronic ticket to the member store as the payment destination. Then, the payment agent server 600 is requested to execute electronic payment for returning the difference to the ticket issuer of the payment source. In response to this, the settlement agency server 600 executes the above two electronic settlements.

As described above, the execution of the electronic payment processing by the payment processing unit 116 includes the electronic payment processing performed by the payment processing unit 116 on behalf of the payment service provider server 600 . For the sake of simplification, the settlement agency server 600 on which the donation settlement unit 213 performs electronic settlement and the settlement agency server 600 on which the settlement processing unit 116 performs electronic settlement are shared. may be different. Although only one settlement agency server 600 is illustrated for simplification, in practice, a large number of settlement agency servers 600 can be connected to the electronic ticket management apparatus 100 .

The payment processing unit 116 changes the status of the electronic ticket (return gift electronic ticket or normal electronic ticket) in the ticket database 112 from the above-mentioned "received" in response to completion of electronic payment by the payment agency server 600. Change to "Used".

If the gift electronic ticket used for payment of expenses does not satisfy a predetermined use completion condition, the ticket issuing unit 111 may reissue the gift electronic ticket with the difference as a new maximum payment amount. In this case, the settlement processing unit 116 returns the difference to the local government as described above when the gift electronic ticket used for payment satisfies the usage completion condition. Hereinafter, the gift electronic ticket used for payment is referred to as "old ticket", and the gift electronic ticket reissued according to the use of the old ticket is referred to as "new ticket".

When reissuing a new ticket, the ticket issuing unit 111 generates, for example, a ticket ID unique to the new ticket (hereinafter referred to as "new ticket ID"), and associates the same user ID as the old ticket with the new ticket ID. In addition, the ticket issuing unit 111 associates the difference with the new ticket ID as a new maximum payment amount, and associates the same payment information and area constraint as those of the old ticket with the new ticket ID. As described above, a new ticket is reissued in which the new ticket ID, the user ID, the maximum payment amount, the payment information, and the regional constraint are associated with each other.

When a new ticket including payment information for prepayment is issued by the ticket issuing unit 111, the payment processing unit 116 does not perform electronic payment for returning the difference to the local government that made the payment. As a result, the electronic money up to the new maximum payment amount is continuously pooled by the management company of the electronic ticket management device 100 .

The ticket issuing unit 111 transmits the reissued new ticket to the user terminal 330 . For example, the ticket issuing unit 111 converts the reissued new ticket into a readable electronic code such as a one-dimensional code or a two-dimensional code (for example, QR code (registered trademark)) and transmits it to the user terminal 330 .

If the normal electronic ticket used for payment of expenses does not satisfy a predetermined usage completion condition, the ticket issuing unit 111 may reissue the normal electronic ticket using the difference as a new maximum payment amount. In this case, the payment processing unit 116 returns the difference to the ticket issuer as described above when the normal electronic ticket used for payment satisfies the use completion condition. Hereinafter, the normal electronic ticket used for payment is referred to as "old ticket", and the normal electronic ticket reissued according to the use of the old ticket is referred to as "new ticket".

When reissuing a new ticket, the ticket issuing unit 111 generates, for example, a ticket ID unique to the new ticket (hereinafter referred to as "new ticket ID"), and associates the same user ID as the old ticket with the new ticket ID. Further, the ticket issuing unit 111 associates the new ticket ID with the difference as a new maximum payment amount, and associates the same payment information and individual constraint conditions as those of the old ticket with the new ticket ID. As described above, a new ticket is reissued in which the new ticket ID, user ID, maximum payment amount, payment information, and individual constraint are associated with each other.

When a new ticket including payment information for advance payment is issued by the ticket issuing unit 111, the payment processing unit 116 does not perform electronic payment for returning the difference to the ticket issuer who made the payment. As a result, the electronic money up to the new maximum payment amount is continuously pooled by the management company of the electronic ticket management device 100 .

The ticket issuing unit 111 transmits the reissued new ticket to the user terminal 330 . For example, the ticket issuing unit 111 converts the reissued new ticket into a readable electronic code such as a one-dimensional code or a two-dimensional code (for example, QR code (registered trademark)) and transmits it to the user terminal 330 .

The ticket issuing unit 111 changes the status of the new ticket to "issued" when the new ticket is recorded in the ticket database 112, and changes the status from "issued" to "sent" when the transmission of the new ticket to the user terminal 330 is completed. , when the receipt of the new ticket by the user terminal 330 is confirmed, "sent" is changed to "received".

Any usage completion condition can be set. Examples are given below.
Example 1) The above difference is less than the predetermined use completion amount.
Example 2) The number of times the gift electronic ticket has been reissued has reached the predetermined upper limit.

The ticket issuing unit 111 may issue the gift electronic ticket with a predetermined expiration date. In this case, the payment processing unit 116 may return the maximum payment amount of the gift electronic ticket to the local government at the timing when the expiration date of the unused gift gift electronic ticket has passed. For example, if the payment information of the gift electronic ticket is payment information for subsequent payment, the payment processing unit 116 changes the status of the electronic ticket in the ticket database 112 from "received" to "expired". As a result, the electronic ticket becomes unusable, and the maximum payment amount is returned to the local government. If the payment information of the gift electronic ticket is payment information for advance payment, the payment processing unit 116 returns electronic money equivalent to the maximum payment amount pooled for the gift electronic ticket to the local government that made the payment. The settlement agent server 600 is requested to execute the settlement. In response, the settlement agency server 600 executes the electronic settlement, and the maximum payment amount is returned to the local government.

The ticket issuing unit 111 may issue a normal electronic ticket with a predetermined expiration date. In this case, the payment processing unit 116 may return the maximum payment amount of the normal electronic ticket to the ticket issuer at the timing when the expiration date of the unused normal electronic ticket has passed. For example, if the payment information of a normal electronic ticket is payment information for subsequent payment, the payment processing unit 116 changes the status of the electronic ticket in the ticket database 112 from "received" to "expired". As a result, the electronic ticket becomes unusable, and the maximum payment amount is returned to the ticket issuer. When the payment information of the normal electronic ticket is the payment information for pre-payment, the payment processing unit 116 performs electronic payment for returning the electronic money equivalent to the maximum payment amount pooled for the return gift electronic ticket to the local government that made the payment. is requested to the settlement agency server 600 to execute . In response, the settlement agency server 600 executes the electronic settlement, and the maximum payment amount is returned to the local government.

FIG. 6 is a block diagram illustrating the hardware configuration of the electronic ticket management system 1. As shown in FIG. The electronic ticket management system 1 includes the electronic ticket management device 100 and the hometown tax payment acceptance device 200 as described above. The electronic ticket management device 100 and the hometown tax payment acceptance device 200 are connected via a communication network NW. In addition, the electronic ticket management device 100 and the hometown tax payment reception device 200 are connected to the donor terminal 310, the ticket issuer terminal 320, the user terminal 330, the store terminal 500, and the settlement agency server 600 via the communication network NW. ing. The communication network NW is a wide area network including, for example, the so-called Internet. The network lines forming the communication network NW may be wired or wireless.

The hometown tax payment acceptance device 200 has a circuit 290 . Circuitry 290 includes one or more processors 291 , memory 292 , storage 293 and communication port 294 . The storage 293 is, for example, a storage medium such as at least one hard disk or non-volatile memory. The storage 293 stores a program for causing the hometown tax payment acceptance device 200 to execute donation acceptance and payment processing, and arrangement of gifts in return for the donation. For example, the storage 293 stores a program for configuring each functional block of the hometown tax payment reception apparatus 200 .

The memory 292 temporarily stores the program loaded from the storage 293 and the calculation result by the processor 291 . The processor 291 cooperates with the memory 292 to execute the above programs, thereby configuring each of the above functional modules. The communication port 294 performs network communication with the electronic ticket management device 100, the donor terminal 310, the ticket issuer terminal 320, the user terminal 330, the store terminal 500, and the settlement agency server 600 in accordance with instructions from the processor 291. I do.

The electronic ticket management device 100 has a circuit 190 . Circuitry 190 includes one or more processors 191 , memory 192 , storage 193 and communication port 194 . The storage 193 is, for example, a storage medium such as at least one hard disk or non-volatile memory. The storage 193 issues a gift electronic ticket to which user conditions and area constraints are attached when donations are made by residents outside the area to a local public body in a predetermined area, and Registering the store as a member store in accordance with the registration request, changing the user conditions of the gift electronic ticket in accordance with the gift gift electronic ticket transfer request, and paying the fee at the member store with the gift gift electronic ticket Payment is determined based on whether the person who does so satisfies the user conditions and whether the subject of the payment satisfies the regional constraint conditions, and if it is determined that payment is possible, the local government pays the fee to the member store payment processing, and a program for causing the electronic ticket management device 100 to execute the payment processing. For example, the storage 193 stores programs for configuring the functional blocks of the electronic ticket management device 100 described above.

The memory 192 temporarily stores the program loaded from the storage 193 and the calculation result by the processor 191 . The processor 191 cooperates with the memory 192 to execute the above programs, thereby configuring each of the above functional modules. The communication port 194 performs network communication with the hometown tax payment acceptance device 200, the donor terminal 310, the ticket issuer terminal 320, the user terminal 330, the shop terminal 500, and the settlement agency server 600 according to the instructions from the processor 191. I do.

[Electronic ticket management method]
Next, as an example of an electronic ticket management method, an electronic ticket management procedure executed by the electronic ticket management system 1 will be illustrated. In this procedure, the ticket issuing unit 111 issues an electronic gift gift ticket to which a user condition and an area constraint condition are added when a local public body in a predetermined area receives a donation from a resident outside the area. the store registration unit 114 registers the store as a member store in response to a registration request from the store; By changing the conditions, the payment processing unit 116 determines whether a person who intends to pay the fee at the affiliated store with the gift electronic ticket satisfies the user condition, and whether or not the person who intends to pay the fee satisfies the area constraint condition. Determining whether payment is possible based on whether or not, and performing payment processing from the local government to the member store when it is determined that payment is possible.

This procedure consists of the ticket issuing unit 111 issuing a normal electronic ticket to which user conditions have been added in accordance with an electronic ticket issuing request from a ticket issuer, and Determining whether payment is possible based on whether or not the conditions are satisfied, and performing payment processing from the ticket issuer to the member store when it is determined that payment is possible.

In the following, a return gift arrangement procedure executed by the hometown tax payment acceptance device 200, a return gift electronic ticket issuing procedure and a normal electronic ticket issuing procedure executed by the electronic ticket management device 100, and a store shop executed by the electronic ticket management device 100 The electronic ticket management procedure will be illustrated in detail by dividing into a registration procedure, a payment procedure using a gift electronic ticket and a payment procedure using a normal electronic ticket, which are executed by the electronic ticket management apparatus 100. FIG.

(Return gift arrangement procedure)
As shown in FIG. 7, the hometown tax payment acceptance device 200 first executes steps S01, S02, S03, and S04. In step S<b>01 , the donation accepting unit 211 waits for an application for donation from the donor terminal 310 . During this time, in response to access from the donor terminal 310, the donation reception unit 211 displays on the donor terminal 310 a list of local public bodies that can be donation recipients and gifts in return for the donation. In step S<b>02 , the donation reception unit 211 acquires the donation information (contents of donation application and donor identification information) from the donor terminal 310 and records it in the donation information database 212 . In step S<b>03 , the donation settlement unit 213 performs electronic settlement processing of the donation according to the settlement information of the donation information stored in the donation information database 212 . In step S04, the return gift arrangement unit 215 refers to the return gift database 214 to confirm whether the gift to be donated is a gift electronic ticket.

When it is determined in step S04 that the donation recipient's return gift is the return gift electronic ticket, the hometown tax payment acceptance device 200 executes steps S05 and S06. In step S05, the return gift arrangement unit 215 generates information for issuing a return gift electronic ticket. For example, the gift arranging unit 215 refers to the donation information database 212 and the gift database 214 to generate information including the donation amount, the donor ID, the recipient of the gift, and the detailed gift information. In step S06, the gift arrangement unit 215 transmits the ticket issuing information to the electronic ticket management device 100, and requests the electronic ticket management device 100 to issue gift gift electronic tickets corresponding to the donation amount.

When it is determined in step S04 that the donation recipient's return gift is not a return gift electronic ticket, the hometown tax payment acceptance device 200 executes step S07. In step S07, the return gift arrangement unit 215 requests the return gift providing company to send the return gift to the destination (above-mentioned return gift destination). Hometown tax payment acceptance device 200 repeats the above procedure.

(Procedure for issuing return gift electronic ticket)
As shown in FIG. 8, the electronic ticket management device 100 executes steps S11, S12, S13, S14, S15, S16, S17 and S18. In step S<b>11 , the ticket issuing unit 111 waits for a return gift electronic ticket issuing request from the return gift arrangement unit 215 . In step S12, the ticket issuing unit 111 generates a ticket ID unique to the gift electronic ticket. In step S13, the ticket issuing unit 111 sets user conditions. For example, the ticket issuing unit 111 uses the donor ID as the user ID. In step S14, the ticket issuing unit 111 sets payment conditions. For example, the ticket issuing unit 111 sets the maximum payment amount based on the donation amount and the return condition of the detailed information on the gift item.

In step S15, the ticket issuing unit 111 sets payment information. For example, the ticket issuing unit 111 extracts the payment information included in the detailed information on the gift in return. In step S16, the ticket issuing unit 111 sets the regional constraint. For example, the ticket issuing unit 111 extracts the regional constraint included in the detailed information on the gift in return.

In step S17, the ticket issuing unit 111 adds the user ID set in step S13 to the ticket ID generated in step S12, the maximum payment amount set in step S14, and the payment information set in step S15. , and the regional constraint conditions set in step S16 are associated with each other to issue a gift electronic ticket and record it in the ticket database 112.例文帳に追加At this time, the ticket issuing unit 111 sets the status of the return gift electronic ticket to "issued".

In step S18, the ticket issuing unit 111 transmits the gift electronic ticket issued in step S17 to the user terminal 330, and changes the status of the gift electronic ticket in the ticket database 112 from "issued" to "sent". . Upon confirming receipt of the gift electronic ticket by the user terminal 330, the ticket issuing unit 111 changes the status from "sent" to "received". The electronic ticket management device 100 repeats the above procedure. Note that the execution order of steps S11 to S16 can be changed as appropriate. The electronic ticket management device 100 may execute steps S11 to S16 in parallel.

(How to issue a normal electronic ticket)
As shown in FIG. 9, the electronic ticket management device 100 executes steps S21, S22, S23, and S24. In step S<b>21 , the ticket issuing unit 111 waits for a normal electronic ticket issuing request from the ticket issuer terminal 320 . At step S22, the ticket issuing unit 111 generates a ticket ID unique to the normal electronic ticket.

In step S23, the ticket issuing unit 111 generates a normal electronic ticket by associating the ticket ID generated in step S22 with the user ID, maximum payment amount, settlement information, and individual constraint conditions obtained from the ticket issuer terminal 320. Issue a ticket and record it in the ticket database 112 . At this time, the ticket issuing unit 111 sets the status of the normal electronic ticket to "issued".

In step S24, the ticket issuing unit 111 transmits the normal electronic ticket issued in step S23 to the user terminal 330, and changes the status of the normal electronic ticket in the ticket database 112 from "issued" to "transmitted". Upon confirming receipt of the normal electronic ticket by the user terminal 330, the ticket issuer 111 changes the status from "sent" to "received". The electronic ticket management device 100 repeats the above procedure.

(Store registration procedure)
As shown in FIG. 10, the electronic ticket management device 100 executes steps S31 and S32. In step S<b>31 , the store registration unit 114 waits for a registration request from the store terminal 500 . In step S32, the store registration unit 114 acquires the information of the store requesting registration from the store terminal 500, and records the acquired information in the store database 115 as the member store information. The electronic ticket management device 100 repeats the above procedure.

(Payment procedure using return gift electronic ticket)
As shown in FIG. 11, the electronic ticket management device 100 first executes steps S41, S42, and S43. In step S41, the payment processing unit 116 waits for the use of the gift electronic ticket by method 1 or method 2 described above. In step S42, the payment processing unit 116 acquires an unauthenticated ticket ID, a store ID, an unauthenticated user ID, and information on a payment target. For example, when the gift electronic ticket is used in method 1 above, the payment processing unit 116 stores the unauthenticated ticket ID, the shop ID, the unauthenticated user ID, and the information of the payment target. Acquired from the store terminal 500 . When the gift electronic ticket is used in method 2 above, the payment processing unit 116 sends the unauthenticated ticket ID, the shop ID, the unauthenticated user ID, and the information of the payment target to the user. Acquire from the terminal 330 . In step S43, the payment processing unit 116 confirms whether the status of the unauthenticated ticket ID is "received" in the ticket database 112 or not. If it is determined in step S43 that the status of the unauthenticated ticket ID is not "accepted", the settlement processing unit 116 returns the process to step S41.

If it is determined in step S43 that the status of the unauthenticated ticket ID is "accepted", the electronic ticket management device 100 executes step S44. In step S44, the payment processing unit 116 confirms whether or not the unauthenticated ticket ID and the unauthenticated user ID are associated in the ticket database 112 or not.

If it is determined in step S44 that the unauthenticated ticket ID and the unauthenticated user ID are not associated in the ticket database 112, the payment processing unit 116 determines that the user does not satisfy the user conditions, The process is returned to step S41.

If it is determined in step S44 that the unauthenticated ticket ID and the unauthenticated user ID are associated in the ticket database 112, the electronic ticket management device 100 executes step S45. In step S45, the payment processing unit 116 confirms whether or not the target of payment satisfies the regional constraint based on at least the information of the member store or the information of the target of payment of the cost.

If it is determined in step S45 that the payment target does not satisfy the area constraint, the settlement processing unit 116 returns the process to step S41. If it is determined in step S45 that the target of payment satisfies the area constraint, the electronic ticket management device 100 executes step S46. In step S46, the settlement processing unit 116 determines that payment is possible, and returns the difference between the maximum payment amount of the gift electronic ticket and the amount of payment for the settlement object to the local public body that is the source of the payment. Process payments from organizations to member stores.

If the gift electronic ticket used for payment of expenses does not satisfy the predetermined usage completion condition, the ticket issuing unit 111 reissues the gift electronic ticket with the difference as a new maximum payment amount after step S46. may

The payment processing unit 116 changes the status of the gift electronic ticket in the ticket database 112 from "received" to "used" in response to completion of payment (for example, completion of electronic payment by the payment agency server 600). change. The electronic ticket management device 100 repeats the above procedure.

(Payment procedure using a normal electronic ticket)
As shown in FIG. 12, the electronic ticket management device 100 first executes steps S51, S52, and S53. In step S51, the payment processing unit 116 waits for the normal electronic ticket to be used by method 1 or method 2 described above. In step S52, the payment processing unit 116 acquires an unauthenticated ticket ID, a store ID, an unauthenticated user ID, and information on a payment target. For example, when the gift electronic ticket is used in method 1 above, the payment processing unit 116 stores the unauthenticated ticket ID, the shop ID, the unauthenticated user ID, and the information of the payment target. Acquired from the store terminal 500 . When the gift electronic ticket is used in method 2 above, the payment processing unit 116 sends the unauthenticated ticket ID, the shop ID, the unauthenticated user ID, and the information of the payment target to the user. Acquire from the terminal 330 . In step S53, the payment processing unit 116 confirms whether the status of the unauthenticated ticket ID is "received" in the ticket database 112 or not. If it is determined in step S53 that the status of the unauthenticated ticket ID is not "received", the settlement processing unit 116 returns the process to step S51.

If it is determined in step S53 that the status of the unauthenticated ticket ID is "accepted", the electronic ticket management device 100 executes step S54. In step S<b>54 , the payment processing unit 116 confirms whether or not the unauthenticated ticket ID and the unauthenticated user ID are associated in the ticket database 112 .

If it is determined in step S54 that the unauthenticated ticket ID and the unauthenticated user ID are not associated in the ticket database 112, the payment processing unit 116 determines that the user does not satisfy the user conditions, The process is returned to step S51.

If it is determined in step S54 that the unauthenticated ticket ID and the unauthenticated user ID are associated in the ticket database 112, the electronic ticket management device 100 executes step S55. In step S55, the settlement processing unit 116 confirms whether or not the payment object satisfies the individual constraint condition based on at least the member store information or the payment object information.

If it is determined in step S55 that the payment target does not satisfy the individual constraint, the settlement processing unit 116 returns the process to step S51. If it is determined in step S55 that the payment target satisfies the individual constraint, the electronic ticket management device 100 executes step S56. In step S56, the payment processing unit 116 determines that the payment can be made, and returns the difference between the maximum payment amount of the normal electronic ticket and the payment amount for the payment object to the ticket issuer as the payment source. Payment processing of expenses from to the member store.

The payment processing unit 116 changes the status of the normal electronic ticket in the ticket database 112 from "received" to "used" in response to completion of payment (for example, completion of electronic payment by the payment agency server 600). do. The electronic ticket management device 100 repeats the above procedure.

If the normal electronic ticket used for payment of expenses does not satisfy the predetermined use completion condition, the ticket issuing unit 111 may reissue the normal electronic ticket after step S56 with the difference as the new maximum payment amount. good.

[Effect of this embodiment]
As described above, the electronic ticket management method according to the present embodiment is an electronic ticket management method executed by the electronic ticket management device 100, in which the ticket issuing unit 111 issues a When there is a donation from a resident of the store, the store registration unit 114 issues the store as a member store according to the registration request from the store. The user condition change unit 113 changes the user condition of the gift electronic ticket in accordance with the request for transfer of the gift electronic ticket, Judging whether or not the person who intends to pay the fee satisfies the user conditions for the gift electronic ticket and whether or not the subject of the payment satisfies the regional constraint conditions, and determined that the payment is possible. Including the processing of payment of expenses from the local public body to the member store in the case.

According to this electronic ticket management method, when there is a donation from a resident outside the area (for example, "hometown tax") to a local public body in a predetermined area, Gift electronic tickets will be issued. Gift electronic tickets can be used for a wide range of products and services within the scope of regional restrictions. This characteristic may motivate donors to donate and contribute to increased revenue in a given area. In addition, this characteristic can contribute to stimulating consumption of a wide range of products and services related to a given area. In addition, it is possible to change the user conditions after the fact in accordance with the transfer request of the gift electronic ticket. Therefore, for example, it is possible for the donor to transfer the gift electronic ticket before use to another person (for example, the donor's relative who is a resident of a predetermined area) who is in a position to easily use the gift electronic ticket. . This can more reliably stimulate consumption related to the predetermined area. In addition, the contribution to consumer incentives may encourage registration of the store. This will increase the number of member stores, making it possible to use them for a wider range of products and services, which is expected to create a virtuous cycle that will contribute to further increases in revenue and stimulation of consumption. Therefore, it is effective in both increasing local revenues and stimulating local consumption.

In the electronic ticket management method, the ticket issuing unit 111 issues a normal electronic ticket to which user conditions have been added in accordance with an electronic ticket issuing request from a ticket issuer, and the payment processing unit 116 issues a normal electronic ticket to a member store. Judge whether or not the person who intends to pay the fee meets the user conditions of the normal electronic ticket, and if it is determined that the payment is possible, the payment process from the ticket issuer to the member store may further include performing. In this case, by making it possible to use a normal electronic ticket with no area restrictions, it is possible to improve the convenience of general consumption activities unrelated to gift gifts and further stimulate consumption in a predetermined area. In addition, by enabling the use of normal electronic tickets, the registration of the store can be further encouraged. Due to the effectiveness described above, if the number of local governments using this electronic ticket management method increases, normal electronic tickets can be commonly used in a wider area. Due to this convenience, the use of normal electronic tickets is further expanded, which may further encourage store registration. Therefore, it is more effective for increasing local revenues and stimulating local consumption.

The area constraints include the supply area restrictions, and the payment processing unit 116 determines whether or not the cost payment target satisfies the area restrictions based on whether the location of the member store satisfies the area restrictions. may In this case, it is possible to stimulate consumption within the predetermined area.

The area restrictions include the store restrictions, and the payment processing unit 116 may determine whether or not the payment target satisfies the area restrictions based on whether the member store satisfies the store restrictions. In this case, it is possible to stimulate consumption at stores related to the predetermined area.

The area constraints include a name constraint, and the payment processing unit 116 determines whether the cost payment target satisfies the region constraint based on whether the name attached to the cost payment target satisfies the name constraint. may be determined. In this case, it is possible to stimulate consumption of brands related to the predetermined area.

The region constraints include company constraints, and the payment processing unit 116 determines whether the target of payment satisfies the region constraint based on whether the company providing the target of payment satisfies the company constraint. You can judge. In this case, it is possible to stimulate consumption for companies related to the predetermined area.

The ticket issuing unit 111 issues a gift electronic ticket with a maximum payment amount corresponding to the donation amount, and the payment processing unit 116 returns the difference between the maximum payment amount and the cost to the local government. You may process payments. In this case, the maximum payment amount set for the gift electronic ticket can be used more reliably to increase local revenues and stimulate local consumption.

The ticket issuing unit 111 reissues the gift electronic ticket with the difference as a new maximum payment amount when the gift electronic ticket used for payment of expenses does not satisfy the predetermined use completion condition, and the settlement processing unit 116 , the difference may be returned to the local government when the gift electronic ticket used to pay the expenses satisfies the use completion conditions. In this case, by making it easier for the user to use an amount close to the initial maximum payment amount, it is possible to further increase the willingness to contribute, which is the starting point of the virtuous circle.

Although the embodiments have been described above, the present disclosure is not necessarily limited to the above-described embodiments, and various modifications are possible without departing from the gist thereof.

DESCRIPTION OF SYMBOLS 100... Electronic ticket management apparatus, 111... Ticket issue part, 113... User condition change part, 114... Store registration part, 116... Payment process part.

Claims (9)

An electronic ticket management method executed by an electronic ticket management device,
A ticket issuing unit issues a gift electronic ticket to which a user condition and an area constraint condition are attached when a local government in a predetermined area receives a donation from a resident outside the area;
A store registration unit registers the store as a member store in accordance with a registration request from the store;
a user condition changing unit changing the user condition of the electronic gift ticket in accordance with the transfer request for the electronic gift ticket;
The payment processing unit determines whether a person who intends to pay the fee at the member store with the gift electronic ticket satisfies the user conditions of the gift gift electronic ticket, and determines whether the payment target for the fee is the region restriction. Determining whether payment is possible based on whether or not conditions are satisfied, and performing payment processing of the expenses from the local government to the member store when it is determined that the payment is possible. The ticket issuing unit issues a normal electronic ticket to which a user condition is attached in accordance with an electronic ticket issuing request from a ticket issuer;
The payment processing unit determines whether or not a person who intends to pay the fee at the member store with the normal electronic ticket satisfies the user conditions of the normal electronic ticket, and determines whether the payment is possible. 2. The electronic ticket management method according to claim 1, further comprising: performing payment processing of said fee from said ticket issuer to said member store when it is determined that The area constraints include provision location constraints,
3. The electronic device according to claim 2, wherein said payment processing unit determines whether or not a target for payment of said cost satisfies said region constraint based on whether the location of said member store satisfies said supply location constraint. Ticket management method. The area constraints include store constraints,
4. The electronic ticket management according to claim 2 or 3, wherein said payment processing unit determines whether or not said fee payment target satisfies said area constraint based on whether said member store satisfies store constraint. Method. the region constraint includes a name constraint;
The payment processing unit determines whether or not the target of payment satisfies the region constraint based on whether a name given to the target of payment satisfies the name constraint. The electronic ticket management method according to 2 or 3. the region constraints include company constraints;
3. The settlement processing unit determines whether or not the target of payment of the cost satisfies the region constraint based on whether or not the company providing the target of payment of the cost satisfies the company constraint. 6. The electronic ticket management method according to any one of -5. The ticket issuing unit issues the return gift electronic ticket with a maximum payment amount according to the donation amount,
The electronic ticket management method according to any one of claims 1 to 6, wherein said payment processing unit performs payment processing of said cost so as to return a difference between said maximum payment amount and said cost to said local government. . The ticket issuing unit reissues the electronic gift ticket using the difference as a new maximum payment amount when the electronic gift ticket used for payment of the expense does not satisfy a predetermined usage completion condition,
8. The electronic ticket management method according to claim 7, wherein said payment processing unit returns said difference to said local government when said return gift electronic ticket used for payment of said expenses satisfies said usage completion condition. a ticket issuing unit that issues a gift electronic ticket with user conditions and area restrictions when donations are made by residents outside the area to a local public body in a predetermined area;
a store registration unit that registers the store as a member store in accordance with a registration request from the store;
a user condition changing unit that changes the user condition of the return gift electronic ticket in accordance with the return gift electronic ticket transfer request;
Whether the payment is possible or not based on whether the person who intends to pay the fee at the member store with the gift electronic ticket satisfies the user conditions and whether the person to whom the fee is to be paid satisfies the regional constraint condition and a payment processing unit that performs payment processing of the cost from the local government to the member store when it is determined that the payment is acceptable.

Images