JP7371280B2 - Entry/exit management device and entry/exit management system - Google Patents

Description

Embodiments of the present invention relate to an entry/exit management device and an entry/exit management system.

BACKGROUND ART Conventionally, there is a system (stored fare system) in which an IC card issued by a railway company is charged with electronic money in advance, and the railway fare is settled by holding the IC card over an automatic ticket gate. In connection with this, it is known that an IC card and a credit card are linked in advance and electronic money is automatically charged to the IC card by credit card payment. However, this system cannot be used unless an IC card is issued by a railway company, which is very time-consuming and inconvenient for, for example, travelers from foreign countries.

Japanese Patent Application Publication No. 2002-109584 Japanese Patent Application Publication No. 2005-215877 Japanese Patent Application Publication No. 2012-215999

The problem to be solved by the present invention is to provide an entry/exit management device and an entry/exit management system that can improve convenience when entering or exiting a space where entry/exit is managed.

The entry/exit management device of the embodiment includes a charge management section, a settlement section, and a refund management section. The charging management unit associates the amount of electronic money charged through the payment by the payment provider with the identification information assigned to the user for using the payment by the payment provider. When the identification information is acquired by an entry/exit processing device that permits or prohibits the entry/exit of the user, the payment unit is configured to provide information to the entry/exit processing device derived based on the information acquired by the entry/exit processing device. The usage fee for services provided in the space to which the user is permitted to enter and exit is deducted from the amount of electronic money. The refund management unit requests the payment provider to refund the amount of electronic money to the user when a predetermined refund timing is reached. The charge management unit determines whether the electronic money amount has been fully refunded based on the identification information acquired when the user enters or exits, and determines whether the electronic money amount has been fully refunded or not. If so, a request is made to a payment server managed by the payment provider to charge electronic money.

FIG. 1 is a schematic diagram of an entry/exit management system 1 according to an embodiment. A functional configuration diagram of an entry/exit management device 300 and an automatic ticket gate 400 according to an embodiment. 3 is a diagram showing an example of the contents of balance information 332. FIG. FIG. 3 is a diagram showing an example of the contents of user information 333. FIG. 3 is a sequence diagram showing an example of a process including an admission inquiry process (A) and an appearance inquiry process (P). FIG. 3 is a sequence diagram showing an example of a process including an admission inquiry process (D) and an appearance inquiry process (Q). 5 is a flowchart showing an example of processing by the entrance/exit management device 300. A flowchart showing an example of admission inquiry processing. 12 is a flowchart showing another example of admission inquiry processing. The flowchart which shows an example of admission inquiry processing (D). 12 is a flowchart showing an example of a process subsequent to the admission inquiry process (D). The flowchart which shows an example of participation inquiry processing. A flowchart showing an example of participation inquiry processing (Q). The flowchart which shows an example of participation inquiry processing. The flowchart which shows an example of participation inquiry processing.

Hereinafter, an entry/exit management device and an entry/exit management system according to embodiments will be described with reference to the drawings. Below, an example will be described in which the entrance/exit management device of the embodiment manages the entrance/exit of a user using a railway. Note that the entry/exit management device is not limited to this, and may, for example, be one that manages entry/exit to facilities such as amusement parks and zoos, and may also be used to manage entry/exit to other facilities where fees are charged according to time. It may also be something that manages participation.

FIG. 1 is a schematic diagram of an entry/exit management system 1 according to an embodiment. The entrance/exit management system 1 includes, for example, one or more payment servers 100, one or more intermediary servers 200, one or more entrance/exit management devices 300, one or more automatic ticket gates (entrance/exit processing devices) 400, and one or more station service equipment 500. These configurations are connected to each other by a network NW and communicate with each other via this network NW. The network NW includes, for example, some or all of a WAN (Wide Area Network), a LAN (Local Area Network), the Internet, a leased line, a wireless base station, a provider, and the like.

Payment server 100 is a server managed by a payment provider. Payment service providers include, for example, credit card companies, financial institutions such as banks, and businesses that provide proxy payment services that perform payments on behalf of other subscribers. This payment provider is different from a service provider (in this case, a railway company) that provides services to users in the space where entry and exit are managed by the automatic ticket gate 400. An example will be described below in which the payment provider is a credit card company and the identification information assigned to each contractor with the credit card company is a credit card number. Further, although an example in which a credit card number is stored in an electronic tag mounted on a credit card will be described below, the present invention is not limited to this. For example, a two-dimensional code in which a credit card number is encoded may be used, and this two-dimensional code may be displayed on paper, other media, a display screen of a terminal device, or the like.

The mediation server 200 is a server managed by a mediation business. The intermediary business is a business that mediates credit confirmation for the payment server 100. Credit confirmation is to confirm whether or not credit is provided to a contractor who has a contract with a payment provider in advance. If the payment provider is providing credit to the contractor (in other words, if credit has been confirmed), the payment provider can make payments on behalf of the contractor. On the other hand, if credit is not provided to the contractor (in other words, credit confirmation cannot be obtained), the payment provider cannot make payments on behalf of the contractor. When the intermediary server 200 is requested by the entry/exit management device 300 to charge electronic money through payment by a payment provider, the intermediary server 200 performs credit confirmation by communicating with the payment server 100 . Note that the intermediary business operator is a business different from the service provider. Currently, service providers often pay intermediary fees for each credit check, regardless of the payment amount.

The entrance/exit management device 300, automatic ticket gate 400, and station equipment 500 are managed by a service provider. Automatic ticket gate 400 and station service equipment 500 are installed at each station. The automatic ticket gate 400 is an example of an entry/exit processing device that allows or prohibits users from entering and exiting. The entrance/exit management device 300 is installed for each service provider, for example. The entrance/exit management device 300 communicates with another server (not shown) managed by a service provider and acquires various information such as a price list. The station equipment 500 is, for example, a device operated by a station employee or the like, and transmits information input by the station employee or the like to the entry/exit management device 300.

The automatic ticket gate 400 communicates with, for example, a credit card held over a reading window, and reads a credit card number from an electronic tag mounted on the credit card. Note that the automatic ticket gate 400 may include a reader that reads a two-dimensional code, reads the two-dimensional code displayed on the display screen of the terminal device, and obtains the credit card number encoded in the two-dimensional code. The medium holding the credit card number acquired by the automatic ticket gate 400 is hereinafter referred to as a card ticket. The automatic ticket gate 400 may include a display section, receive information indicating a processing result by the entry/exit management device 300, and display entry information based on the received information on the display section. The output information includes, for example, the amount paid, whether entry or participation is permitted or prohibited, and the reason for the prohibition.

The automatic ticket gate 400 generates usage information when reading a credit card number from a card ticket. The usage information includes, for example, identification information indicating the station (or location) where the automatic ticket gate 400 is installed, time information, and the like. The automatic ticket gate 400 transmits information in which the read credit card number is associated with usage information to the entrance/exit management device 300. The entrance/exit management device 300 determines whether the user is entering or exiting based on the received credit card number and usage information, and transmits the determination result to the automatic ticket gate 400. Based on the received determination result, the automatic ticket gate 400 executes opening processing or closing processing for the restricting material that restricts the passage of users.

FIG. 2 is a functional configuration diagram of the entrance/exit management device 300 and the automatic ticket gate 400 according to the embodiment. The entry/exit management device 300 includes, for example, a first communication section 311, a second communication section 312, a third communication section 313, a storage section 330, and a processing section 350. The first communication unit 311 communicates with the mediation server 200. The second communication unit 312 communicates with the automatic ticket gate 400. The third communication unit 313 communicates with the station service equipment 500. The first communication unit 311, the second communication unit 312, and the third communication unit 313 include communication interfaces such as NICs. The storage unit 330 is, for example, a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory such as an SSD, an HDD (Hard Disk Drive), or the like. The storage unit 330 stores, for example, price list information 331, balance information 332, user information 333, negative list 334, and the like.

The fare table information 331 is information related to a fare table for deriving a fare based on input information such as the boarding station, the getting off station, the transfer station, and whether or not a limited express ticket is used. When fees vary depending on the attributes of the user or the due date, the fee list information 331 includes information regarding the respective fee schedules.

FIG. 3 is a diagram showing an example of the contents of the balance information 332. The balance information 332 is, for example, information in which a credit card number is associated with an expiration date, a subscriber's name, a payment provider, a ticket balance, a final payment date, a usage suspension notice, and the like. A credit card number is identification information assigned to each credit card subscriber by a credit card company. A credit card number is an example of identification information assigned to a user in order to use payment by a payment provider. The credit card number may be one number for one subscriber, or it may be one number for one subscriber, or multiple credit card numbers linked to one credit card number or one subscriber, such as family cards or disposable credit card numbers. It may also include a number. The subscriber name is the name of the credit card subscriber registered at the time of the contract. The expiration date is the deadline by which payment can be made using the corresponding credit card number. The payment provider is the name of the credit card company. The ticket balance is the amount of electronic money charged by the payment provider. The final settlement date is information indicating the latest date on which the usage fee was settled using the ticket balance. The usage suspension notification will be described later.

FIG. 4 is a diagram showing an example of the contents of the user information 333. The user information 333 is, for example, information in which a credit card number is associated with usage status, payment completion information, name on the card, attributes, telephone number, and the like. The usage status is information indicating the usage status of the service provided by the service provider. Usage status includes, for example, entering the ticket gate (entering state), exiting from the ticket gate (exiting state), and the station from which you entered or exited (station name, identification information, etc.) ), the time of entry or exit, etc. The payment completion information includes information indicating whether the payment of usage fees incurred by using the service provided by the service provider has been completed. Further, the payment completion information may include information indicating past payment status. Information indicating past payment status includes, for example, the number of times payment was completed without delay, the number of times payment was completed with delay, and the number of times payment was not completed. The name on the card is the user's name displayed on the card. The name on the card may be the same as the name of the credit card holder or may be different. The latter case includes, for example, a case where the number of characters that can be displayed on a card ticket is limited. Attributes include age, gender, etc.

The negative list 334 is a list of users who are prohibited from entering or exiting. The users whose entry/exit is prohibited are determined by the entry/exit management device 300, for example. The negative list 334 includes, for example, credit card numbers of users whose entry and exit are prohibited.

Returning to FIG. 2, the processing unit 350 includes, for example, a data management unit 351, a registration unit 352, a charge management unit 353, a settlement unit 354, a refund management unit 355, and an entry/exit determination unit 356. These configurations are realized, for example, by a processor such as a CPU (Central Processing Unit) executing a program (software) stored in the storage unit 330. In addition, some or all of the functions of these components may be realized by hardware (including circuitry) such as LSI, ASIC, or FPGA, or may be realized by collaboration between software and hardware. It may be realized.

The data management unit 351 encrypts information to be sent to the mediation server 200 and sends it using the first communication unit 311. Furthermore, the data management unit 351 uses the first communication unit 311 to decode the information received from the mediation server 200. For example, when a new credit card number is registered by the registration unit 352, the data management unit 351 encrypts the new credit card number and transmits it to the intermediary server 200. By decoding the information received from the intermediary server 200, the data management unit 351 obtains the expiration date of the credit card number, the name of the contractor, and the like. The data management section 351 may output the information received from the automatic ticket gate 400 using the second communication section 312 to each section of the processing section 350 or may store it in the storage section 330.

Further, the data management unit 351 uses the third communication unit 313 to receive information transmitted from the station equipment 500, and causes the storage unit 330 to store the received information. For example, the data management unit 351 stores information indicating the name on the ticket, attributes, telephone number, etc. received from the station equipment 500 in the storage unit 330 as part of the user information 333. Note that the data management unit 351 may use the third communication unit 313 to receive information transmitted from another server managed by a service provider, and store the received information in the storage unit 330.

When the registration unit 352 receives a new credit card number from the automatic ticket gate 400 using the second communication unit 312, the registration unit 352 registers the received new credit card number in the balance information 332 and the user information 333. Further, the registration unit 352 registers the expiration date, contract name, etc. received from the intermediary server 200 using the first communication unit 311 in the balance information 332 in association with the new credit card number. Further, the registration unit 352 registers the usage status based on the usage information in the user information 333 in association with the credit card number. In addition, the registration unit 352 associates user attributes (age, gender, etc.), telephone number, etc. received from the station equipment 500 using the third communication unit 313 with the new credit card number, and adds the balance information 333 to the new credit card number. Register.

The charge management unit 353 communicates with the intermediary server 200 using the first communication unit 311 and requests the payment server 100 to charge electronic money. For example, the charge management unit 353 determines whether or not a predetermined charge timing has been reached, and if it is determined that the charge timing has been reached, the charge management unit 353 generates request information requesting a charge of a set amount, and sends the request information to the intermediary server 200. Send to. The charging timing includes, for example, when usage information is received from the automatic ticket gate 400 (in other words, when an entry notification or exit notification is received from the automatic ticket gate 400), or when a predetermined date and time (charging date and time) is reached. This includes cases where the payment unit 354 executes a process to withdraw the usage fee from the charge balance, a case where the ticket balance becomes less than the minimum amount threshold L1 (first threshold), and so on. By doing this, it is possible to charge the set amount at the time when the credit card number is acquired by the automatic ticket gate 400, so the ticket balance increases from the time of admission to the time of participation and after participation, and the ticket balance increases at the time of participation. It is possible to avoid a situation where the balance is insufficient or a situation where the ticket balance is insufficient at the time of the next admission.

The charge management unit 353 may also determine whether the ticket balance has been reset, and generate request information if there is a history of the ticket balance being reset. Resetting the ticket balance means, for example, that the refund management unit 355 fully refunds the electronic money of the ticket balance on a predetermined date (for example, the last day of the month).

Note that the charge management unit 353 determines whether the ticket balance is insufficient in settling the usage fee (described later) derived by the payment unit 354, and if the ticket balance is insufficient in settling the usage fee, Request information requesting charging of an amount equal to or more than the insufficient amount may be generated. If the ticket balance is insufficient when settling the usage fee, for example, after deriving the usage fee, it is determined that the usage fee is not less than the ticket balance, and when the set amount is charged, the set amount and ticket balance are This includes cases where the total value of is less than the usage fee. In addition, the case where the ticket balance is insufficient when paying the usage fee includes the case where the ticket balance is less than the initial ride fee after entering without paying. By doing so, it is possible to avoid a situation where the usage fee cannot be settled due to insufficient ticket balance.

Additionally, the charging management unit 353 compares the usage fee derived by the settlement unit 354 (described later) with the set amount, etc., and if the usage fee is higher than the set amount, requests a request to charge the usage fee or more. Information may be generated. Further, the charge management unit 353 refers to the ticket balance in the balance information 332, determines whether the total value of the ticket balance and the set amount is greater than or equal to the usage fee, and determines whether the total value of the ticket balance and the set amount is equal to or higher than the usage fee. If this is not the case, request information requesting a charge of an amount equal to or greater than the usage amount may be generated. By doing so, it is possible to avoid a situation where the ticket balance becomes insufficient when paying the usage fee after being charged.

Further, after transmitting the request information, if the payment server 100 confirms that the set amount of electronic money is to be paid to the credit card number, the charge management unit 353 indicates that the credit confirmation has been made. A notification (hereinafter referred to as a credit confirmation notification) is received from the mediation server 200. The credit confirmation notification includes, for example, information indicating the credit card number and the amount of electronic money settled by the settlement server 100 (hereinafter referred to as charge amount). The charge management unit 353 adds the charge amount to the ticket balance based on the received credit confirmation notification. For example, the charge management unit 353 associates the charge amount with the credit card number included in the credit confirmation notification and stores it in the storage unit 330 as part of the balance information 332. Note that if electronic money has already been charged as a ticket balance, the charging management unit 353 reads the ticket balance associated with the credit card number included in the credit confirmation notification from the balance information 332, and adds the ticket balance to the read ticket balance. The "ticket balance" column of the balance information 332 is rewritten with the added value of the charge amount.

Further, after transmitting the request information, if the payment server 100 cannot confirm the credit of paying the set amount of electronic money to the credit card number, the charge management unit 353 indicates that the credit confirmation cannot be obtained. A notification (hereinafter referred to as a credit confirmation failure notification) is received from the intermediary server 200. In this case, the charge management unit 353 registers the credit card number for which credit confirmation could not be obtained in the negative list 334 . Note that the charge management unit 353 may transmit the same request information multiple times at a certain period of time, and register the credit card number in the negative list 334 if only a credit confirmation failure notification is received. . In other words, even if there is a case where credit confirmation cannot be obtained, if credit confirmation is obtained later, the credit card number may not be registered in the negative list 334.

When the automatic ticket gate 400 acquires a credit card number, the settlement unit 354 derives a usage fee based on the information acquired by the automatic ticket gate 400. The usage fee is the usage fee for a service provided in a space where entry and exit is permitted or prohibited by the automatic ticket gate 400. For example, the payment unit 354 refers to the fee list information 331 and the user information 333 and derives the usage fee based on the usage information received from the automatic ticket gate 400. Specifically, the payment unit 354 reads out the "entrance station" stored as the usage status of the user information 333, and reads the fare (or entrance station) to the "exit station" received from the automatic ticket gate 400 as the usage information. (the fee after deducting the fee paid at the time of payment) is derived with reference to the fee list information 331. Note that if the "station of entry" is not stored as the usage status in the user information 333, the payment unit 354 derives the initial fare from the "station of entry" received from the automatic ticket gate 400 as the usage information as the usage fee. It's okay. In addition, if "information indicating that payment at the time of admission has not been completed" is stored in the usage status column of the user information 333, the payment unit 354 determines whether payment at the time of admission has been completed at the time of participation. The payment amount at the time of participation, including the amount that is not available, may be derived and used as the usage fee.

Note that, before deriving the usage fee, the settlement unit 354 determines whether it is necessary to derive the usage fee based on the credit card number and usage information received from the automatic ticket gate 400 using the second communication unit 312. may be determined. For example, in the case of a system in which a fee is not collected at the time of entry but a fee is collected at the time of exit, the settlement unit 354 determines that it is necessary to derive the usage fee when it is the time of exit. Note that the payment unit 354 handles cases where the usage information includes information indicating participation processing, or when only the admission status is recorded in the usage status of the user information and the participation status is not recorded. It is determined that it is time to participate.

The settlement unit 354 executes a process of subtracting the derived usage fee from the ticket balance. For example, the settlement unit 354 refers to the balance information 332 and uses the second communication unit 312 to read the ticket balance associated with the credit card number received from the automatic ticket gate 400. If the usage fee is less than or equal to the ticket balance, the settlement unit 354 rewrites the "ticket balance" column of the balance information 332 with the value obtained by subtracting the usage fee from the ticket balance. Further, the settlement unit 354 writes information indicating the date of settlement (the date and time including time information may be used) in the “last settlement date” column of the balance information 332. On the other hand, if the usage fee is not less than the ticket balance, the payment unit 354 adds the set amount to the ticket balance by the charge management unit 353 (or, if the usage amount is more than the set amount, the ticket balance is equal to or more than the usage amount). ), the usage fee is deducted from the ticket balance.

When a predetermined refund timing is reached, the refund management unit 355 requests the payment server 100 to refund the electronic money of the ticket balance to the user. Thereby, the payment server 100 executes a process of transferring the electronic money of the ticket balance to the bank account of the subscriber identified by the credit card number, for example.

The refund timing includes, for example, at least one of refund timings 1 to 3 described below. Refund timing 1 is a predetermined date and time (refund date and time). Refund timing 2 is when the period in which the payment unit 354 does not perform payment processing using the ticket balance continues to exceed a predetermined period (for example, two weeks). Refund timing 3 is the last day of the expiration date associated with the credit card number or a predetermined date and time before the last day. For example, when determining whether refund timing 2 has been reached, the refund management unit 355 refers to the "last settlement date" of the balance information 332 and waits for a predetermined period from the last day on which the usage fee was deducted from the ticket balance. It is determined whether or not the period has elapsed. Note that by adopting refund timing 3, it is possible to avoid a situation where the expiration date is exceeded and the refund cannot be made in association with the credit card number. Furthermore, by employing refund timing 1, it is possible to periodically reset the ticket balance, for example.

When refunding electronic money to a user, the refund management unit 355 may register history information indicating this in the balance information 332 in association with the credit card number.

The entry/exit determination unit 356 determines whether or not entry or exit is permitted based on the credit card number acquired by the automatic ticket gate 400. First, the entrance/exit determination unit 356 refers to the user information 333 and determines whether it is an entrance process or an exit process based on the credit card number and usage information received from the automatic ticket gate 400. . For example, if "participation status" is registered in the usage status column of the user information 333, the entry/exit determination unit 356 determines that it is an entry process. On the other hand, if "entering state" is registered in the usage status column of the user information 333, the entering/exiting determination unit 356 determines that it is an exiting process. Note that if the usage information includes information indicating that it is an entrance process or an exit process, the entrance/exit determination unit 356 may make the determination based on the usage information.

Further, the entrance/exit determination unit 356 determines whether or not payment of usage fees is necessary in the entrance process or the exit process. For example, if it is predetermined that payment is made at the time of exit and payment of the usage fee is not required at the time of admission, the entry/exit determination unit 356 determines that payment of the usage fee is not required at the time of admission. Note that whether or not payment is required may be determined for each station, or may be determined for each railway company that manages the station.

If no payment is required, the entry/exit determination unit 356 permits entry or exit. If payment is required, it is determined whether payment is possible, and if it is determined that payment is possible, entry/exit determination unit 356 permits entry or exit. However, if the credit card number is registered in the negative list 334, the entry/exit determination unit 356 prohibits entry or participation.

To be more specific, when it is determined that the usage fee needs to be settled, the entry/exit determination section 356 refers to the balance information 332 based on the credit card number acquired by the automatic ticket gate 400, and makes the settlement section. 354, it is determined whether the usage fee derived is less than or equal to the ticket balance. If the usage fee is less than or equal to the ticket balance, the entrance/exit determination unit 356 permits the user to enter or exit, and sends a permission notification to the automatic ticket gate 400 using the second communication unit 312.

Note that even if the usage fee is not less than the ticket balance, the entrance/exit determination unit 356 may permit the user to enter or exit if predetermined conditions (hereinafter referred to as admission/exit permission conditions) are met. . The entry/exit permission conditions are, for example, (a) the user is a good user, (b) the usage fee derived by the payment unit 354 is less than or equal to the high payment threshold H1 (second threshold), and (c) This includes at least one of the following: the ticket balance is equal to or greater than the minimum amount threshold L1 (third threshold position).

The entry/exit determination unit 356 determines that the user is a good user when the past payment status of the usage fee based on the ticket balance satisfies a certain standard. If the past payment status of the usage fee based on the ticket balance satisfies certain criteria, for example, if the number of times the user's payment has not been completed is less than or equal to the first threshold, the payment has been completed without delay. This includes cases where the number of times is equal to or greater than the second threshold. Furthermore, if the credit card number received from the automatic ticket gate 400 is registered in the negative list 334, the entrance/exit determination unit 356 determines that the user is not a good user.

Furthermore, if the usage fee is not less than the ticket balance and if at least one of the entry/exit permission conditions (a) to (c) is met, the admission/exit judgment unit 356 determines whether the user can enter or participate. may be allowed. For example, if (c) is not satisfied, the entrance/exit determining unit 356 may determine whether or not (a) is satisfied, and if (a) is satisfied, the user may be allowed to enter or exit. . In addition, if the usage fee is not less than the ticket balance, the entry/exit judgment unit 356 prohibits the user from entering or participating unless all of the entrance/exit permission conditions (a) to (c) are satisfied. It's okay.

By doing this, even if the usage fee cannot be settled with the ticket balance, if the usage fee is not expensive or if there is even a small amount of ticket balance remaining, entry or participation can be permitted for the time being.

Next, an example of processing by the entry/exit management system 1 will be described with reference to FIGS. 5 and 6.

FIG. 5 is a sequence diagram showing an example of a process including an admission inquiry process (A) and an appearance inquiry process (P). The admission inquiry process (A) is executed by the entrance/exit management device 300 when no payment is required at the time of admission and when a new credit card number is acquired by the automatic ticket gate 400 at the time of admission. It is processing. The participation inquiry process (P) is a process executed by the entry/exit processing device 300 when payment is required at the time of participation and the ticket balance is not insufficient.

First, the admission inquiry process (A) will be explained. When the user's credit card is swiped at the automatic ticket gate 400 installed at the entrance gate, the automatic ticket gate 400 starts entry processing (step S1). In the entrance process, the automatic ticket gate 400 generates usage information and transmits information in which the usage information is associated with the credit card number to the entrance/exit management device 300 (step S2). Then, the entrance/exit management device 300 refers to its own storage unit 330 and determines whether the credit card number received from the automatic ticket gate 400 is registered. If the credit card number is not registered, the entrance/exit management device 300 starts the entrance inquiry process (A) (step S3). In the admission inquiry process (A), the admission/exit management device 300 generates request information that includes a credit card number and requests charging of a set amount of money, and transmits it to the intermediary server 200 (step S4). In addition, the entrance/exit management device 300 transmits a permission notice permitting entry to the automatic ticket gate 400 (step S5).

When receiving the request information, the mediation server 200 executes charging processing based on the request information (step S6). In the charging process, the intermediary server 200 requests the payment server 100 to confirm credit for paying a set amount of electronic money to the credit card number (step S7). The payment server 100 starts credit inquiry processing based on the request from the intermediary server 200 (step S8). In the credit inquiry process, the payment server 100 determines whether it is possible to pay a set amount of electronic money to the specified credit card number. The payment server 100 notifies the intermediary server 200 of the result of the credit inquiry process (step S9). The intermediary server 200 transfers the result of the credit inquiry process received from the payment server 100 to the entry/exit management device 300 (step S10). For example, if credit confirmation is obtained in the credit inquiry process in step S8, the intermediary server 200 transmits a credit confirmation notification to the entry/exit management device 300. On the other hand, if credit confirmation cannot be obtained in the credit inquiry process in step S8, the intermediary server 200 transmits a credit confirmation failure notification to the entry/exit management device 300.

By doing so, the user can register the credit card number in the entrance/exit management device 300 by simply holding the credit card over the automatic ticket gate 400, and the set amount is automatically charged. Therefore, there is no need for advance registration by the user, and convenience for the user and service provider improves.

Next, the participation inquiry process (P) will be explained. When the user's credit card is swiped at the automatic ticket gate 400 installed at the exit gate, the automatic ticket gate 400 starts exit processing (step S21). In the exit processing, the automatic ticket gate 400 generates usage information and transmits information in which the usage information is associated with the credit card number to the entry/exit management device 300 (step S22). Then, the entrance/exit management device 300 derives the usage fee, refers to the ticket balance in the balance information 332 associated with the credit card number received from the automatic ticket gate 400, and determines whether the usage fee is less than or equal to the ticket balance. judge. If the usage fee is less than or equal to the ticket balance, the entry/exit management device 300 starts the participation inquiry process (P) (step S23). In the entry/exit inquiry process (P), the entry/exit management device 300 derives the usage fee and executes a process of deducting the usage fee from the ticket balance associated with the credit card number received from the automatic ticket gate 400. Furthermore, the entrance/exit processing device 300 determines whether the user is present or not, and transmits the determination result to the automatic ticket gate 400 (step S24). Next, the entry/exit management device 300 executes an auto charge process (step S25).

FIG. 6 is a sequence diagram showing an example of a process including an admission inquiry process (D) and an appearance inquiry process (Q). The admission inquiry process (D) is a process executed by the admission/exit processing device 300 when a credit card number is registered and payment is required at the time of admission. The participation inquiry process (Q) is a process executed by the entry/exit processing device 300 when payment is required at the time of participation and the ticket balance is insufficient. In addition, in the participation inquiry process (Q), if entry and participation permission conditions are met, participation is permitted even before the usage fee is settled.

First, the admission inquiry process (D) will be explained. When the user's credit card is swiped at the automatic ticket gate 400 installed at the entrance gate, the automatic ticket gate 400 starts entry processing (step S31). In the entrance process, the automatic ticket gate 400 generates usage information and transmits information in which the usage information is associated with the credit card number to the entrance/exit management device 300 (step S32). Entry/exit management device 300 refers to its own storage unit 330 and determines whether the credit card number received from automatic ticket gate 400 is registered. If the credit card number is registered, the entrance/exit management device 300 starts entrance inquiry processing (D) (step S33). In the admission inquiry process (D), the entrance/exit management device 300 derives the usage fee and performs a process of deducting the usage fee from the ticket balance associated with the credit card number received from the automatic ticket gate 400. In addition, the entrance/exit processing device 300 determines whether the user has entered, and transmits the determination result to the automatic ticket gate 400 (step S34). Next, the entry/exit management device 300 executes an auto charge process (step S35).

Next, the participation inquiry process (Q) will be explained. When the user's credit card is swiped at the automatic ticket gate 400 installed at the exit gate, the automatic ticket gate 400 starts exit processing (step S41). In the exit process, the automatic ticket gate 400 generates usage information and transmits information that associates the usage information with the credit card number to the entry/exit management device 300 (step S42). Then, the entry/exit management device 300 derives the usage fee, refers to the ticket balance associated with the credit card number received from the automatic ticket gate 400, and determines whether the usage fee is less than or equal to the ticket balance. If the usage fee is not less than the ticket balance, the entry/exit management device 300 starts the entry/exit inquiry process (Q) (step S43). In the participation inquiry process (Q), the entry/exit management device 300 generates request information that includes a credit card number and requests charging of a set amount, and transmits it to the intermediary server 200 (step S44). Furthermore, the entrance/exit management device 300 determines whether the user is present or not, and transmits the determination result to the automatic ticket gate 400 (step S45).

When receiving the request information, the mediation server 200 executes charging processing based on the request information (step S46). In the charging process, the entry/exit management device 300 requests the payment server 100 to confirm credit for paying a set amount of electronic money to the credit card number (step S47). The payment server 100 starts credit inquiry processing based on the request from the entry/exit management device 300 (step S48). In the credit inquiry process, the payment server 100 determines whether it is possible to pay a set amount of electronic money to the specified credit card number. The payment server 100 notifies the intermediary server 200 of the result of the credit inquiry process (step S49). The intermediary server 200 transfers the result of the credit inquiry process received from the payment server 100 to the entry/exit management device 300 (step S50).

FIG. 7 is a flowchart showing an example of processing by the entry/exit management device 300. First, the entrance/exit determination unit 356 determines whether a credit card number has been received from the automatic ticket gate 400 using the second communication unit 312 (step S101). When receiving the credit card number, the entrance/exit determination unit 356 refers to the user information 333 and performs admission processing based on the credit card number and usage information received from the automatic ticket gate 400 using the second communication unit 312. It is determined whether or not (step S103). If it is determined that it is an entrance process, the entrance/exit determination unit 356 executes an admission inquiry process (step S105). Details of the admission inquiry process will be described later. If it is determined in step S103 that it is not an entry process, the entry/exit determination unit 356 refers to the user information 333 and determines whether or not it is an entry process based on the credit card number and usage information (step S107). . If it is determined that it is the participation process, the entry/exit determination unit 356 executes the participation inquiry process (step S109). Details of the participation inquiry process will be described later.

FIG. 8 is a flowchart illustrating an example of admission inquiry processing. First, the entrance/exit determination unit 356 determines whether or not payment of usage fees is necessary in the entrance process based on the credit card number and usage information received from the automatic ticket gate 400 using the second communication unit 312. (Step S201). If settlement of usage fees is not required in the admission process, the entrance/exit determination unit 356 refers to the balance information 332 and determines whether the credit card number received from the automatic ticket gate 400 is registered (step S203). . If the credit card number received from the automatic ticket gate 400 is not registered in the balance information 332, the entrance/exit management device 300 executes the entrance inquiry process (A). Then, the entrance/exit determination unit 356 determines that entry is permitted (step S205), and transmits the determination result to the automatic ticket gate 400 using the second communication unit 312 (step S207).

Next, the registration unit 352 registers the credit card number received from the automatic ticket gate 400 using the second communication unit 312 in the balance information 332 (step S209). Then, the registration unit 352 associates the usage information received from the automatic ticket gate 400 using the second communication unit 312 with the credit card number registered in step S209, and registers it in the balance information 332 (step S211). . In addition, in step S211, the registration unit 352 generates information indicating that the user is in the entry state, information indicating the station of entry, information indicating that payment processing has not been executed at the time of entry, etc., and transmits the generated information to the user. Add to the information 333 usage status.

Next, the charge management unit 353 uses the first communication unit 311 to transmit request information requesting a set amount of electronic money to be charged to the intermediary server 200 (step S213). Then, the charge management unit 353 uses the first communication unit 311 to determine whether or not a credit confirmation notification has been received from the intermediary server 200 (step S215). When receiving the credit confirmation notification, the charge management unit 353 adds the set amount to the ticket balance (step S217). On the other hand, if the credit check failure notification is received in step S215, the charge management unit 353 registers the credit card number received from the automatic ticket gate 400 in the negative list 334 (step S219).

On the other hand, in step S203, if the credit card number received from the automatic ticket gate 400 is registered in the balance information 332, the entrance/exit management device 300 executes the entrance inquiry process (B). The admission inquiry process (B) is a process executed by the admission/exit processing device 300 when a credit card number is registered and payment is not required at the time of admission.

In the admission inquiry process (B), the entrance/exit determination unit 356 determines to permit admission (step S221), and transmits the determination result to the automatic ticket gate 400 using the second communication unit 312 (step S223). Then, the registration unit 352 registers the usage information received from the automatic ticket gate 400 using the second communication unit 312 in the balance information 332 in association with the received credit card number (step S225). In addition, in step S225, the registration unit 352 generates information indicating that the user is in an entry state, information indicating the station of entry, information indicating that payment processing has not been executed at the time of entry, etc., and transmits the generated information to the user. Add to the information 333 usage status.

Next, the charge management unit 353 determines whether the ticket balance is equal to or greater than the minimum amount threshold L1 (step S227). If the ticket balance is equal to or greater than the minimum amount threshold L1, the admission/exit management device 300 ends the admission inquiry process. On the other hand, in step S227, if the ticket balance is not equal to or greater than the minimum amount threshold L1, the charge management unit 353 moves to step S213.

FIG. 9 is a flowchart showing another example of the admission inquiry process. The flowchart shown in FIG. 9 is a process executed by the entry/exit management device 300 when payment is required at the time of entry. For example, if it is necessary to settle the usage fee at the time of admission, the entrance/exit determination unit 356 shifts to YES in step S201 of FIG. 8, and executes the process described below.

First, the entrance/exit determination unit 356 refers to the balance information 332 and determines whether the credit card number received from the automatic ticket gate 400 is registered (step S233). If the credit card number received from the automatic ticket gate 400 is not registered in the balance information 332, the entrance/exit management device 300 executes the entrance inquiry process (C). The admission inquiry process (C) is a process executed by the entrance/exit management device 300 when payment is required at the time of exit and a new credit card number is acquired by the automatic ticket gate 400 at the time of entrance. It is.

In the admission inquiry process (C), the entrance/exit determination unit 356 determines that admission is not permitted (step S235), and transmits the determination result to the automatic ticket gate 400 using the second communication unit 312 (step S237). . Hereinafter, steps S209, S213, S215, S217, and S219 are the same processes as described above, so the description thereof will be omitted.

By doing so, in the admission inquiry process (C), although admission is not permitted, the credit card number is registered and electronic money is charged as the ticket balance. Therefore, when re-entering after a certain period of time, since the credit card number is registered, the entrance inquiry process (D) described below is executed. Note that the admission inquiry process (C) is not limited to this, and at the time of admission, admission is permitted for the time being, the usage fee is derived, and the unpaid usage fee is associated with the credit card number and usage information, and the user information 333 is You may register in advance and settle the payment when electronic money is charged or when a credit card number is obtained at the time of participation.

On the other hand, in step S233, if the credit card number received from the automatic ticket gate 400 is registered in the balance information 332, the entrance/exit management device 300 executes the entrance inquiry process (D).

FIG. 10 is a flowchart illustrating an example of admission inquiry processing (D). In the admission inquiry process (D), the payment unit 354 derives a usage fee based on the usage information received from the automatic ticket gate 400 (step S241). For example, the settlement unit 354 determines the initial fare as the usage fee. Then, the settlement unit 354 determines whether the usage fee is less than or equal to the ticket balance (step S243). If the usage fee is less than or equal to the ticket balance, the payment unit 354 deducts the usage fee from the ticket balance (step S245), and the entrance/exit determination unit 356 determines that admission is permitted (step S247). Then, the entry/exit determination unit 356 transmits the determination result to the automatic ticket gate 400 using the second communication unit 312 (step S249). The registration unit 352 registers the usage information received from the automatic ticket gate 400 using the second communication unit 312 in the balance information 332 in association with the received credit card number (step S251). In addition, in step S251, the registration unit 352 generates information indicating the entry state, information indicating the station of entry, information indicating that payment processing was executed at the time of entry (including the payment amount, etc.), The generated information is added to the usage status of the user information 333.

On the other hand, if the usage fee is not equal to or less than the ticket balance in step S243, the entry/exit determination unit 356 determines whether the user is a good user (step S253). If it is determined that the user is a good user, the entrance/exit determination unit 356 determines that admission is permitted (step S255), and transmits the determination result to the automatic ticket gate 400 using the second communication unit 312 (step S255). Step S257). The registration unit 352 registers the usage information received from the automatic ticket gate 400 using the second communication unit 312 in the balance information 332 in association with the received credit card number (step S259). In addition, in step S259, the registration unit 352 generates information indicating that the user is in an entry state, information indicating the station of entry, information indicating that payment processing has not been executed at the time of entry, etc., and transmits the generated information to the user. Add to the information 333 usage status.

Next, the charge management unit 353 uses the first communication unit 311 to transmit request information requesting a set amount of electronic money to be charged to the intermediary server 200 (step S261). Note that when the usage amount is higher than the set amount, the charging management unit 353 generates request information requesting charging of electronic money equal to or higher than the usage amount, and sends it to the intermediary server 200 using the first communication unit 311. Good too. Then, the charge management unit 353 uses the first communication unit 311 to determine whether or not a credit confirmation notification has been received from the intermediary server 200 (step S263). When receiving the credit confirmation notification, the charge management unit 353 adds the set amount to the ticket balance (step S265). Then, the settlement unit 354 executes a process of subtracting the usage fee from the ticket balance (step S267). Note that, in step S267, the registration unit 352 generates information indicating that the payment at the time of admission has been completed, and rewrites a part of the usage status of the user information 333 using the generated information. Further, the settlement unit 354 may perform the withdrawal process from the ticket balance at the time of participation, without performing the withdrawal process in step S267. On the other hand, if the credit confirmation failure notification is received in step S263, the charge management unit 353 registers the credit card number received from the automatic ticket gate 400 in the negative list 334 (step S269).

By doing this, even if the ticket balance is insufficient when paying the usage fee, if you are a good user, you will be allowed to enter, and the usage fee will be automatically charged after electronic money is charged. can be removed. Therefore, it is possible to prevent the user from being stopped by the automatic ticket gate 400 at the time of entrance, and improve convenience for the user. Further, by setting a certain condition that the user must be a good user in order to be allowed to enter, it is possible to reduce the risk of not being able to collect usage fees.

FIG. 11 is a flowchart illustrating an example of a process subsequent to the admission inquiry process (D). In step S253, if it is determined that the user is not a good user, the entrance/exit determination unit 356 determines that entry is not permitted (step S271), and uses the second communication unit 312 to send a message to the automatic ticket gate 400 for the determination. The results are transmitted (step S273). Hereinafter, steps S213, S215, S217, and S219 are the same processes as described above, so the description thereof will be omitted.

FIG. 12 is a flowchart illustrating an example of participation inquiry processing. First, the entry/exit determination unit 356 refers to the balance information 332 and determines whether the credit card number received from the automatic ticket gate 400 is registered (step S301). If the credit card number received from the automatic ticket gate 400 is not registered in the balance information 332, the entrance/exit management device 300 determines that entry is not permitted (step S303), and uses the second communication unit 312 to close the automatic ticket gate. The determination result is transmitted to the machine 400 (step S305).

On the other hand, if the credit card number received from the automatic ticket gate 400 is registered in the balance information 332, the settlement unit 354 refers to the user information 333 and uses the credit card number received from the automatic ticket gate 400 based on the usage information. A fee is derived (step S307). Then, the settlement unit 354 determines whether the derived usage fee is less than or equal to the ticket balance (step S309). If the usage fee is less than or equal to the ticket balance, the entry/exit management device 300 executes an entry/exit inquiry process (P).

In the participation inquiry process (P), the settlement unit 354 executes a process of subtracting the usage fee from the ticket balance (step S311). Then, the entrance/exit determination unit 356 determines that entry is permitted (step S313), and transmits the determination result to the automatic ticket gate 400 using the second communication unit 312 (step S315). The registration unit 352 registers the usage information received from the automatic ticket gate 400 using the second communication unit 312 in the balance information 332 in association with the received credit card number (step S317). In addition, in step S317, the registration unit 352 generates information indicating the participating state, information indicating the participating station, information indicating that payment at the time of participating has been completed, etc., and stores the generated information in the user information 333. Add to usage. On the other hand, in step S309, if the usage fee is not equal to or less than the ticket balance, the entry/exit management device 300 executes an entry/exit inquiry process (Q).

FIG. 13 is a flowchart showing an example of participation inquiry processing (Q). In the participation inquiry process (Q), the entry/exit determination unit 356 first determines whether the ticket balance is equal to or greater than the minimum amount threshold L1 (step S321). If the ticket balance is equal to or greater than the minimum amount threshold L1, the entry/exit determination unit 356 determines whether the usage fee is equal to or less than the high-value payment threshold H1 (step S323). If the usage fee is less than or equal to the high-value payment threshold H1, the entry/exit determination unit 356 determines whether the user is a good user (step S325). If the user is a good user, the entry/exit determination unit 356 determines to permit entry (step S327), and transmits the determination result to the automatic ticket gate 400 using the second communication unit 312 (step S329). . Then, the registration unit 352 registers the usage information received from the automatic ticket gate 400 using the second communication unit 312 in the balance information 332 in association with the received credit card number (step S331). Note that, in step S331, the registration unit 352 generates information indicating that the player is in the participating state, information indicating the participating station, and information indicating that payment at the time of participation has not been completed (including unpaid amount, etc.). , the generated information is added to the usage status of the user information 333.

Next, the charge management unit 353 uses the first communication unit 311 to transmit request information requesting a set amount of electronic money to be charged to the intermediary server 200 (step S333). Then, the charge management unit 353 uses the first communication unit 311 to determine whether or not a credit confirmation notification has been received from the intermediary server 200 (step S335). When receiving the credit confirmation notification, the charge management unit 353 adds the set amount to the ticket balance (step S337). Then, the settlement unit 354 executes a process of subtracting the usage fee from the ticket balance (step S339). Note that, in step S339, the registration unit 352 generates information indicating that payment at the time of participation has been completed, and rewrites a part of the usage status of the user information 333 using the generated information. On the other hand, if the credit check failure notification is received in step S335, the charge management unit 353 registers the credit card number received from the automatic ticket gate 400 in the negative list 334 (step S341).

By doing this, even if the ticket balance is insufficient when paying the usage fee, if the admission and participation permission conditions are met, participation will be allowed for the time being, and after electronic money has been charged, the ticket will be automatically refunded. Usage fees can be deducted. Therefore, it is possible to prevent the user from being stopped by the automatic ticket gate 400 at the time of exit, and improve convenience for the user. Furthermore, by setting a certain condition that entry and exit conditions must be met in order for the player to participate, the risk of not being able to collect usage fees can be reduced.

On the other hand, if a negative determination is made in at least one of steps S321, S323, and S325, the entry/exit determination unit 356 determines that participation is not permitted (step S343), and uses the second communication unit 312 to automatically The determination result is transmitted to the ticket inspection machine 400 (step S345). After that, the user requests payment at the station counter. The station staff operates the station equipment 500 to perform payment processing at the counter and exit processing. The station service equipment 500 manages entry/exit management of information indicating the results of payment processing and entry processing at the counter (including information indicating the entry station, entry status, etc.), information associated with credit card numbers, etc. The information is transmitted to the device 300. Then, the registration unit 352 registers the information received from the station equipment 500 using the third communication unit 313 in the balance information 332 in association with the received credit card number (step S347). For example, in step S347, the registration unit 352 generates information indicating the participating state, information indicating the participating station, information indicating that payment at the time of participation has not been completed (including unpaid amount, etc.), etc. Then, the generated information is added to the usage status of the user information 333.

FIG. 14 is a flowchart illustrating an example of participation inquiry processing. First, the charge management unit 353 determines whether the charge timing has been reached (step S401). If the charge timing has not been reached, the charge management unit 353 repeats the process of step S401.

On the other hand, in step S401, when the charging timing has been reached, the charging management unit 353 uses the first communication unit 311 to transmit request information requesting charging of a set amount of electronic money to the intermediary server 200 (step S403). ). Then, the charge management unit 353 uses the first communication unit 311 to determine whether or not a credit confirmation notification has been received from the intermediary server 200 (step S405). When receiving the credit confirmation notification, the charge management unit 353 adds the set amount to the ticket balance (step S407). On the other hand, in step S405, if the credit confirmation failure notification is received, the charge management unit 353 registers the credit card number received from the automatic ticket gate 400 in the negative list 334 (step S409).

FIG. 15 is a flowchart illustrating an example of participation inquiry processing. First, the refund management unit 355 determines whether the refund timing has arrived (step S501). If the refund timing has not been reached, the refund management unit 355 repeats the process of step S501. When the refund timing has been reached, the refund management unit 355 refers to the balance information 332 and determines whether the ticket balance is higher than 0 yen (step S503). If the ticket balance is not higher than 0 yen (that is, if the ticket balance is 0 yen or less), the refund management unit 355 ends the process. On the other hand, if the ticket balance is higher than 0 yen, the refund management unit 355 executes processing to refund the entire ticket balance to the user (step S505).

This eliminates the need for the user to go through the procedures at the counter when requesting a refund of the ticket balance, improving convenience for the user and for the service provider. By the way, the method of using an IC card loaded with electronic money (so-called closed-loop card) is becoming popular among users living in Japan, but travelers from abroad can purchase this IC card in Japan and transfer it to Japan. In many cases, the charged amount will be refunded at the counter before leaving the country. In this case, foreign travelers sometimes queue up at the counter, and there are cases where refunds cannot be made because they are unable to make it in time for departure. This kind of problem can also be improved by the refund management unit 355 automatically executing refund processing. Furthermore, by using open-loop cards such as credit cards or using two-dimensional codes encoded with credit card numbers, there is no need to purchase closed-loop cards, improving convenience for users. .

According to at least one embodiment described above, charging management that associates the amount of electronic money charged through payment by a payment provider with the identification information assigned to the user in order to use payment by the payment provider 353 and an entrance/exit processing device (automatic ticket gate 400) that permits or prohibits entry/exit of the user, an entry/exit processing device derived based on the information acquired by the entrance/exit processing device. By including a payment unit 354 that deducts the usage fee for the service provided in the space where entry and exit is permitted by the entry processing device from the amount of electronic money, it is possible to Convenience can be improved.

Convenience will be explained in detail. For example, by charging a certain amount (several thousand yen or tens of thousands of yen) to the ticket balance, the number of payments required is less than the number of rides, and the service provider pays the intermediary company. Fees can be reduced. In addition, by calculating the usage fee from the charge balance, there is no need to make a credit inquiry every time you enter and exit. Enables quick entry and exit. Furthermore, by charging a certain amount in advance, it is possible to reduce the risk that the service provider will not be able to collect usage fees.

Although several embodiments of the invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included within the scope and gist of the invention as well as within the scope of the invention described in the claims and its equivalents.

In addition, regarding a system in which payment is made at the time of entry but not at the time of exit, a method in which payment is not made at the time of entry but at the time of exit can be applied.

Note that if the contractor notifies the payment service provider of suspension of usage due to loss of credit card, etc., the payment server 100 will notify the suspension of usage, either voluntarily or based on a request from the entry/exit management device 300. It may also be transmitted to the entry/exit management device 300 via the mediation server 200. The usage suspension notice includes the credit card number whose usage is to be suspended. When the processing unit 350 of the entry/exit management device 300 receives the usage suspension notification, it sets a flag on the usage suspension notification in the balance information 332, for example. Before generating the request information, the charge management unit 353 may determine whether or not the usage suspension notification is flagged, and if the usage suspension notification is flagged, it may not generate the request information. . In addition, the settlement unit 354 similarly determines whether or not the usage suspension notification is flagged, at the latest before executing the process of deducting the usage fee from the ticket balance, and determines whether the usage suspension notification is flagged. In this case, the process of deducting the usage fee from the ticket balance may not be executed. On the other hand, the refund management unit 355 may refund the ticket balance to the user even if the usage suspension notification is flagged.

Although the entry/exit management device 300 has been described as allowing entry or exit even if the amount spent is not less than the ticket balance, it may also prohibit entry or exit depending on the service provider. . In other words, the entry/exit determination unit 356 may prohibit entry or exit if the payment unit 354 does not complete the process of withdrawing the usage fee.

Note that the automatic ticket gate 400 may communicate with the entrance/exit management device 300 via the station service equipment 500 instead of communicating directly with the entrance/exit management device 300.

Further, whether or not to pay the bill may be determined for each user. For example, it may be determined that users registered in the negative list 334 are required to pay the initial ride fee at the time of admission.

1... Entrance/exit management system, 100... Payment server, 200... Intermediary server, 300... Entrance/exit management device, 311... First communication unit, 312... Second communication unit, 313... Third communication unit, 330... Storage unit, 331...Charge list information, 332...Balance information, 333...User information, 334...Negative list, 350...Processing section, 351...Data management section, 352...Registration section, 353...Charge management section, 354...Settlement section, 355 ...Refund management department, 356...Entrance/exit judgment department, 400...Automatic ticket gate (entrance/exit processing device), 500...Station service equipment

Claims (8)

a charging management unit that associates the amount of electronic money charged by the payment by the payment provider with identification information assigned to the user for using the payment by the payment provider;
If the identification information is acquired by an entry/exit processing device that permits or prohibits the entry/exit of the user, the entry/exit processing device determines entry/exit based on the information acquired by the entry/exit processing device. a settlement unit that deducts usage fees for services provided in the permitted space from the amount of electronic money;
a refund management unit that requests the payment provider to refund the electronic money amount to the user when a predetermined refund timing is reached;
Equipped with
The charge management department
Based on the identification information obtained when the user enters or exits, it is determined whether the electronic money amount has been fully refunded, and if there is a history that the electronic money amount has been fully refunded, the payment requesting a payment server managed by a business operator to charge electronic money;
Entry/exit control device. a charging management unit that associates the amount of electronic money charged by the payment by the payment provider with identification information assigned to the user for using the payment by the payment provider;
If the identification information is acquired by an entry/exit processing device that permits or prohibits the entry/exit of the user, the entry/exit processing device determines entry/exit based on the information acquired by the entry/exit processing device. a settlement unit that deducts usage fees for services provided in the permitted space from the amount of electronic money;
Based on the identification information acquired by the entry/exit processing device, it is determined whether the usage fee is less than or equal to the amount of electronic money, and if the usage fee is less than or equal to the amount of electronic money, the usage fee is an entrance/existence judging department that allows persons to enter or participate;
Equipped with
The entry and participation judgment department is
Even if the usage fee is not less than the amount of electronic money, if predetermined conditions are met, the user is permitted to enter or participate;
The predetermined conditions include:
the past settlement status of the usage fee based on the amount of electronic money satisfies certain criteria;
the usage fee is less than or equal to a second threshold;
including at least one of the following: the amount of electronic money is equal to or higher than a third threshold;
Entry/exit control device. The charge management department
Based on the identification information acquired when the user enters or exits, it is determined whether the amount of the electronic money of the user is less than a first threshold, and the amount of the electronic money of the user is determined. If the amount is less than the first threshold, requesting a payment server managed by the payment provider to charge electronic money;
The entrance/exit management device according to claim 1 or 2. The charge management department
Based on the identification information obtained when the user enters or exits, it is determined whether or not the amount of electronic money is insufficient for settling the usage fee, and the electronic money is used for settling the usage fee. If the amount is insufficient, request a payment server managed by the payment provider to charge electronic money;
An entry/exit management device according to any one of claims 1 to 3. The payment department is
If the usage fee is not less than the amount of electronic money, after electronic money is charged from a payment server managed by the payment provider, the usage fee is deducted from the amount of electronic money.
An entry/exit management device according to any one of claims 1 to 4. The charge management department
A restriction that prohibits the user from entering or exiting if the requested electronic money is not added to the amount of electronic money after requesting the payment server managed by the payment provider to charge electronic money. add to list,
An entrance/exit management device according to any one of claims 1 to 5. The charge management department
If the requested electronic money is not added to the amount of electronic money after requesting the payment server managed by the payment provider multiple times to charge electronic money, the user is restricted from entering and exiting. Add to restricted list,
An entry/exit management device according to any one of claims 1 to 6. An entrance/exit management device according to any one of claims 1 to 7,
an entrance/exit processing device that allows or prohibits users from entering and exiting;
An entrance/exit management system equipped with

Images