Service provision system and automated ticket gate

Abstract

To provide a service providing system and an automatic ticket examining machine capable of being incorporated into the service providing system, in which various services can be provided by utilizing a settlement medium (a credit card or the like) even when settlement is not accompanied.SOLUTION: A service providing system 100 includes: a token management system 11 for managing tokenization of a settlement medium ID (PAN of a credit card CC); a reading unit RD which reads the PAN and notifies the token management system 11 of the same separately from the settlement processing and receives the notification of the corresponding token; and the terminal equipment ME which is notified of the token from the reading unit RD and provides the service based on the notified token.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a service providing system and an automatic ticket gate that utilize a payment medium such as a credit card. [Background technology]

[0002] A common fare payment and collection system is known that is configured to enable the purchase of tickets and / or passes for public transport (see Patent Document 1).

[0003] However, while the above-mentioned Patent Document 1 discloses a common fare payment and collection system configured to enable a user to purchase tickets or passes for multiple public transportation systems using a single account or device, it is assumed that payment-related processes such as purchase, payment, and collection will be carried out, and does not disclose aspects that do not involve payment. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Special Publication No. 2020-526807 Summary of the Invention

[0005] The present invention has been made in consideration of the above-mentioned points, and aims to provide a service provision system that makes it possible to provide various services by using a payment medium such as a credit card, even in cases where payment is not involved, and an automatic ticket gate that can be incorporated into the service provision system.

[0006] The service provision system for achieving the above-mentioned objective comprises a token management unit that manages the tokenization of a payment medium ID, a reading unit that reads the payment medium ID and notifies the token management unit separately from the payment processing and also receives notification of the corresponding token, and a terminal device that is notified of the token from the reading unit and provides a service based on the notified token.

[0007] In the above-described service providing system, notification of a token corresponding to a payment medium ID is handled separately from the payment process, making it possible to provide various services based on the token.

[0008] In a specific aspect of the present invention, a service providing server that manages information on the service provision contents is provided, and the terminal device provides a service according to the token notified by the reading unit from among the contracted service provision contents stored in the service providing server. In this case, it is possible to provide a service according to the contents stored in the service providing server by using the token.

[0009] In another aspect of the present invention, the information managed in the service providing server includes information on a right to use a facility for a certain period of time. In this case, the token can be used when exercising the right to use the facility for a certain period of time without involving a payment process.

[0010] In yet another aspect of the present invention, a payment management server including a token management unit and a payment system that manages payments using a payment medium is provided, and the payment management server performs tokenization of the payment medium ID in response to a notification from the reading unit separately from processing in the payment system. In this case, the payment management server manages payments using a payment medium and also performs tokenization of the payment medium ID that is not involved in the payment.

[0011] In yet another aspect of the present invention, the payment management server accepts a token notification from the terminal device and performs crediting and settlement based on the accepted token. In this case, when a process involving settlement is performed in the payment management server, crediting and settlement based on the token via the terminal device can be performed.

[0012] In yet another aspect of the present invention, the settlement by the settlement management server includes settlement by credit card as a settlement medium. In this case, settlement by credit card is possible, and various services can be provided without settlement processing using tokenization of credit card number (PAN: Primary Account Number).

[0013] In yet another aspect of the present invention, the reader starts notifying the token manager when the payment medium is held over a predetermined medium reading range. In this case, the provision of the corresponding service can be started when the user physically holds the payment medium over the reader.

[0014] To achieve the above objective, an automated ticket gate includes a reading unit that reads the payment medium ID and notifies a token management unit that manages tokenization separately from the payment processing, and receives notification of the corresponding token, and a terminal device that is notified of the token from the reading unit and provides services based on the notified token.

[0015] In the above-mentioned automated ticket gate, the reader notifies the token manager, which manages tokenization, of the read payment medium ID, and further receives notification of a token corresponding to the payment medium ID from the token manager. The terminal device provides services based on the token from the reader. In the above, tokenization of the payment medium ID (token generation) is performed separately and separately from the payment processing.

[0016] In a specific aspect of the present invention, the permission of passage is determined based on the ticket or pass information corresponding to the token notified to the terminal device. In this case, passage through the automatic ticket gate using the payment medium ID is possible. [Brief description of the drawings]

[0017] [Figure 1] 1 is a block diagram for explaining an overview of a service providing system according to a first embodiment. [Diagram 2] FIG. 2 is a conceptual diagram for explaining a part of the operation of the service providing system. [Diagram 3] 2 is a block diagram for explaining the overall operation of the service providing system. FIG. [Figure 4] FIG. 11 is a conceptual diagram for explaining a service providing system including an automated ticket gate according to a second embodiment. [Diagram 5] 1A to 1C are diagrams illustrating an example of data stored in a service providing server. [Figure 6] 10 is a block diagram for explaining an example of the operation of a ticket issuing device incorporated in the service providing server. FIG. [Figure 7] 10 is a block diagram for explaining an example of the operation of an automatic ticket gate incorporated in the service providing server. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] [First embodiment] An example of a service providing system according to the first embodiment will be described below with reference to Fig. 1 etc. As shown in Figs. 1 and 2, the service providing system 100 according to this embodiment includes a payment management server 10, a terminal device 20, and a service providing server 50. The payment management server 10 is composed of a token management system 11 as a token management unit, and a payment system 12. The terminal device 20 is composed of a reading unit RD and a terminal device ME.

[0019] Here, a case will be described in which a credit card CC that is EMV (Europay, MasterCard, VISA protocol) compatible and can be read by the reading unit RD without contact is used as an example of a payment medium.

[0020] The service providing system 100 provides various services when the terminal device 20 reads information on the credit card CC via the reading unit RD. For example, the terminal device 20 can be applied to various things such as ticket vending machines and ticket gates at stations, or devices that manage entry and exit at event venues and membership-based facilities. For example, if the service providing system 100 is applied to stations, the credit card CC as a physical object can be used as a ticket, a commuter pass, or the like. Alternatively, the credit card CC can be used as an event ticket, a membership card for membership-based facilities, or the like.

[0021] In particular, in this embodiment, a token for a credit card CC is used to exercise rights without making a payment for items for which the right to use has already been purchased, such as a commuter pass, thereby enhancing convenience.

[0022] Each of the above components constituting the service providing system 100 will be described below in order.

[0023] First, as shown in FIG. 1, for example, the payment management server 10 is configured as a PCIDSS (Payment Card Industry Data Security Standard) certified server or an equivalent server capable of generating tokens in order to ensure security regarding card information of a credit card CC used as a payment medium.

[0024] Among the payment management server 10, the token management system 11 manages the tokenization of the payment medium ID. More specifically, the token management system 11 performs tokenization, i.e., generates a token, for the credit card number (PAN: Primary Account Number) of the credit card CC, which is the payment medium ID in the above embodiment, between a specific external device (reader unit RD) and notifies the generated token.

[0025] Of the payment management server 10, the payment system 12 performs payment processing (processing of payment requests) based on tokens. That is, the payment system 12 accepts requests for credit and payment from outside, and also requests the token management system 11 in the payment management server 10 to convert the token into a PAN, for example, to perform processing related to credit and payment with the service providing server 50, and requests payment from a credit company or the like depending on the processing result. That is, the payment system 12 manages payments by credit card CC, which is a payment medium.

[0026] Of the terminal device 20, the reading unit RD is configured as an EMV authentication reading device to enable communication with the payment management server 10 as a PCI DSS certified server regarding the PAN and the corresponding token. That is, the reading unit RD reads the PAN as a payment medium ID from the credit card CC and notifies the token management system (token management unit) 11, and also receives notification of the token corresponding to the PAN from the token management system 11.

[0027] Among the terminal devices 20, the terminal equipment ME is notified of the token from the reading unit RD and provides a service based on the notified token. At this time, the terminal device 20 makes a request to the service providing server 50 for a service to be provided to the user by referring to stored information, etc.

[0028] The service providing server 50 is composed of various storage devices, electronic circuits, etc., and stores various data related to the service provision that has been digitized using a token as an ID, and performs necessary judgment processing. In the illustrated example, the service providing server 50 has a ticket database TB, in which information on the service content corresponding to the token corresponding to the read credit card CC is stored so that the credit card CC can be used as a commuter pass, a ticket, or various tickets such as an admission ticket for various events or a coupon ticket. In other words, the service providing server 50 refers to the information stored in the ticket database TB for the number of the token notified from the reading unit RD of the terminal device 20, and provides various services via the terminal device 20. In other words, the terminal device 20 and the service providing server 50 work together to provide the necessary services to the user. From another perspective, the terminal device ME of the terminal device 20 provides the service according to the token notified from the reading unit RD, among the contracted service provision contents stored in the service providing server 50.

[0029] The service providing server 50 is also capable of making inquiries to the payment system 12 of the payment managing server 10, and when performing processing involving payment, it is also possible to provide a service after making a payment based on a token notified from the terminal device ME of the terminal apparatus 20. From another perspective, the payment managing server 10 can also receive a token notification from the terminal device ME via the service providing server 50, and perform credit and payment based on the received token.

[0030] As shown in the figure, there may be multiple terminal devices 20, each of which is composed of terminal equipment ME, etc., and these may be installed at different points A, B, etc., and each terminal device 20 operates in accordance with the results of referencing the data of the service providing server 50 based on the token.

[0031] In the service providing system 100 configured as above, processing involving settlement via each terminal device 20 is also possible, but in this embodiment, a token corresponding to a credit card CC is generated by the token management system 11 separately from the settlement processing, and a service is provided based on the generated token. Specifically, as shown in FIG. 2, the reading unit RD notifies the token management system 11 of the PAN (payment medium ID) read from the credit card CC separately from the settlement processing in the settlement management server 10, that is, whether or not settlement is made in the settlement management server 10, and the token management system 11 generates (issues) a token corresponding to this and notifies (replies) the token to the reading unit RD. In the terminal device 20, the reading unit RD notifies the terminal device ME of the notified (received) token, and the terminal device ME refers to the items (contract contents, etc.) corresponding to the acquired token in the service providing server 50, and provides the corresponding service. In this case, if the content referred to by the service providing server 50 is an item for which payment has already been made, the corresponding service is provided without performing payment processing from the service providing server 50 to the payment system 12 (see FIG. 1). For example, when the terminal device 20 is an automatic ticket gate installed at each station, if it is related to the right to use the facility for a certain period of time, such as passing through a ticket gate with a purchased commuter pass, the expiration date and validity area of ​​the commuter pass stored in the service providing server 50 are referred to, and the terminal device 20 as an automatic ticket gate appropriately performs an operation to allow or deny the currency in accordance with this. Note that, for more detailed aspects of the above, a specific aspect will be described as a second embodiment with reference to FIG. 4 and the like.

[0032] With regard to the above, looking at the payment management server 10, it can be said that in the payment management server 10, the token management system 11 performs tokenization of the PAN (payment medium ID) in response to a notification from the reading unit RD separately from the processing in the payment system 12. From another perspective, the token management system 11 and the reading unit RD perform processing for tokenization separately and independently from the payment, and as a result, the reading unit RD has a function of only reading the PAN and returning a token to the terminal device ME.

[0033] An example of the overall operation of the service providing system 100 will be described below with reference to the block diagram shown in Fig. 3. Specifically, an example will be described in which a credit card CC is used at a terminal device 20 installed at one point (point A) and operations including a settlement process are performed.

[0034] In the illustrated case, it is assumed that, in the terminal device 20, the terminal equipment ME issues a token request to the reader RD, either constantly or periodically (step S1). In this state, when the credit card CC approaches within a predetermined range of the reader RD (when the credit card CC is held up and within a range where contactless communication is possible), the reader RD reads the PAN of the credit card CC (step S2) and notifies the token management system 11 of the result of the reading (step S3).

[0035] The token management system 11 that has received the PAN from the reader RD in step S3 converts the PAN into a token, i.e., generates a token (step S4), and notifies the reader RD of the token (step S5). In other words, the token is issued.

[0036] In response to the token request in step S1, the reader RD notifies the terminal device ME of the token notified in step S5 (step S6).

[0037] The terminal device ME, having received the notification from the reading unit RD, makes a request for service provision by sending the token, as well as location information and various parameters such as its own installation location, reception hours, and the type of service desired to be provided, to the service providing server 50 (step S7).

[0038] The service providing server 50 that has received the request performs processing related to the service to be provided, for example, by referring to the ticket database TB, and also, if necessary, proceeds with processing a request related to payment to the payment system 12 (steps S8 to S15). Specifically, first, the service providing server 50 requests the payment system 12 of the payment managing server 10 to credit the token from the terminal device ME (step S8). In response to this, the payment system 12 requests the token management system 11 in the payment managing server 10 to convert the token into a PAN (step S9), and the token management system 11 converts the token into a PAN in response to this (step S10). The converted PAN is notified to the payment system 12 (step S11), and based on this, the payment system 12 returns the credit result to the service providing server 50 (step S12a). In other words, if there is no abnormality in the above processing in the payment managing server 10, the token from the terminal device ME is given trust.

[0039] On the other hand, after the credit request in step S8, until the credit result in step S12a is obtained, the service providing server 50 performs processing related to the service to be provided, such as ticket determination, based on the token from the terminal device ME, location information, or various parameters (step S12b). At this time, the service providing server 50 calculates the fee to be incurred as a payment-related item.

[0040] Once the credit result is obtained in step S12a and the process for the provided service is completed in step S12b, the corresponding service is executed (step S13).

[0041] Furthermore, the service providing server 50 notifies the payment system 12 of a payment request together with the token in order to make payment for the usage fee corresponding to the provided service (step S14), and the payment system 12 transmits the payment request to a credit company, etc., i.e., an acquirer AC or a payment gateway operator PG (step S15).

[0042] Regarding the above, looking at it from another perspective, when processing involving payment, the payment management server 10 accepts a token notification from the terminal device ME via the service providing server 50, and performs credit and payment based on the accepted token.

[0043] On the other hand, in the case of service provision without payment, the service providing server 50 that receives the service request using the token as a key from the terminal device ME in step S7 performs the service provision in step S13 without performing the payment-related processing in step S8 and after. In this case, the processing in step S14 and after is of course unnecessary. Therefore, the service is provided using the token without incurring any special payment fee.

[0044] In addition, in the above, as an example, the service providing server 50 performs processing related to service provision in response to a service request from a terminal device 20 installed at one point (point A), but the service providing server 50 can also handle service requests from terminal devices 20 installed at other points (for example, point B) in a similar manner as described above.

[0045] As described above, the service providing system 100 in this embodiment includes the token management system 11 as a token management unit that manages the tokenization of the payment medium ID (PAN of a credit card CC), the reading unit RD that reads the PAN and notifies the token management system 11 separately from the payment processing and receives notification of the corresponding token, and the terminal device ME that receives the token from the reading unit RD and provides a service based on the notified token. In this case, the service providing system 100 handles the notification of the token corresponding to the PAN (payment medium ID) separately from the payment processing, making it possible to provide various services based on the token.

[0046] Second Embodiment Hereinafter, an example of the service providing system 100 according to the second embodiment will be described with reference to FIG. 4 and the like. In this embodiment, as a more specific example of the service providing system 100 described in the first embodiment, a configuration example in which the service providing system 100 is introduced into a station will be described. That is, in this embodiment, a ticket vending machine or an automatic ticket gate installed in a station functions as the terminal device 20 or the terminal device ME. In addition, a ticket issuing system or a ticket gate system functions as the service providing server 50 or a part thereof, and for example, data related to a sold commuter pass or ticket is managed based on a token of a credit card CC, so that the credit card CC can be used as a commuter pass or the like. Note that the overall configuration of the service providing system 100 is the same as that of the first embodiment, and detailed illustrations and explanations of the overall configuration will be omitted.

[0047] 4, in this embodiment, a reader unit RD, i.e., an EMV authentication reader, is attached to a ticket issuing device (ticket vending machine) TD and an automatic ticket gate AG installed at a station and configured to communicate with a token management system 11, so that the ticket issuing device TD and the automatic ticket gate AG function as terminal devices 20. Also, a ticket issuing system TS and a ticket gate system GS, which are connected to the ticket issuing device TD and the automatic ticket gate AG directly or indirectly by wire or wirelessly and manage data, function as a service providing server 50 by being connected to, for example, a payment management server 10 and capable of various processes.

[0048] The ticket issuing device TD illustrated in the figure has various operation units OU for purchasing commuter passes and tickets, as well as a reception unit RP1 with depth for accepting contactless credit cards CC. As shown in the figure, by placing the credit card CC on the placement unit PP of the reception unit RP1, it can be read by the reading unit RD.

[0049] In addition, the automated ticket gate AG is capable of reading a credit card CC by holding it near the reception unit RP2 provided on the entrance / exit side. That is, when the credit card CC as a payment medium is held over the reader RD, the reader RD starts notifying the token management system 11 as a token management unit.

[0050] In this embodiment, as an example, a case will be described in which a commuter pass or the like is first purchased at the ticket issuing device TD using an EMV-compatible credit card CC, and then this credit card CC is used as a physical commuter pass to pass through an automatic ticket gate AG. That is, as a series of operations, for example, a user who has a credit card CC first purchases a commuter pass (a right equivalent to a commuter pass) or the like with the credit card CC at the reception unit RP1 of the ticket issuing device TD, and then holds this credit card CC over the reception unit RP2 of the automatic ticket gate AG, which opens the gate GT of the automatic ticket gate AG and allows the user to pass through.

[0051] 5(A) to 5(C) are diagrams illustrating data (information) stored in the ticket database TB of the service providing server 50. That is, as shown in FIG. 5(A), a data table DT is created every time a token is generated. In each data table DT, for example, data DD1 relating to the generated token ID (token number), its issue date and time, and expiration date, data DD2 relating to the contract contents (purchased right contents), and data DD3 relating to the facility usage history are stored. For example, as shown in FIG. 5(A), data DD2 includes the type of purchase contents, such as whether it is a commuter pass, and information on the period and section of the commuter pass, and data DD3 includes information on when and which station (ticket gate) was passed through. In addition to the above, for example, as shown in FIG. 5(B), in the case where a charge (deposit) has been made in advance in addition to a commuter pass, data DD2 includes information on the charge amount in addition to information on the section of the commuter pass, and further includes data CD1 of the charge balance. In addition to information on the station where the user got on and off, information on whether the use was within the commuter pass section is written in the data DD3, and if the use was outside the commuter pass section, a process of deducting the charge amount is performed, and a description to that effect is written. At this time, the data CD1 is also rewritten according to the amount deducted. That is, the service providing server 50 can also appropriately calculate the travel fare between multiple points as necessary. In addition, as shown in FIG. 5(C), for example, a type of ticket can be stored in the data DD2. In this case, information on the use of the ticket is written in the data DD3, and the data CD2 of the remaining number of times included in the data DD2 is also rewritten accordingly. Note that these data to be managed are merely examples, and various other forms are assumed, such as a free pass with a limited number of days. By managing these based on a token, it becomes possible to use a physical credit card CC in the same way as a ticket or a commuter pass by holding it over a ticket gate.

[0052] Hereinafter, with reference to the block diagram shown in FIG. 6, the overall operation of the service providing system 100 in the case where the ticket issuing device TD functions as the terminal device 20 will be described. FIG. 6 corresponds to FIG. 3. That is, in FIG. 6, the ticket issuing device TD corresponds to the terminal device 20 in FIG. 3. More specifically, the ticket issuing device TD that functions as the terminal device 20 is configured by attaching a reading unit RD to the ticket issuing device main body TDa as the terminal equipment ME. Also, the service providing server 50 is configured by the ticket issuing system TS that performs various processes related to ticket issuing (ticket selling) and the ticket database TB that stores data related to sold commuter passes, etc. The data stored in the ticket database TB is exemplified in FIG. 5(A) and the like. In the ticket issuing system TS that communicates with the ticket issuing device main body TDa, these data are generated, updated, etc. Here, as an example, one mode in the case where a commuter pass is purchased in the ticket issuing device TD will be described.

[0053] First, in the case shown in Fig. 6, similarly to steps S1 to S6 in the case of Fig. 3, a token for the PAN of the credit card CC is generated and notified between the ticket issuing device TD as the terminal device 20 installed at each point (local) and the token management system 11, independently of the presence or absence of a settlement (steps S201 to S206), and data for a commuter pass purchase request, for example, is transmitted from the ticket issuing device TD to the ticket issuing system TS of the service providing server 50 as a request for service provision (step S207). That is, information on the section and period of the commuter pass as the service to be received is transmitted from the ticket issuing device TD to the ticket issuing system TS together with a token corresponding to the PAN of the credit card CC.

[0054] The ticket issuing system TS of the service providing server 50 that receives the request performs credit-related processing (steps S208-S212) similar to steps S8-S12a in the case of Fig. 3. In parallel with this, the ticket issuing system TS performs processing related to the service to be provided, such as calculating the commuter pass fare, and generates data (commuter pass data) to be stored in the ticket database TB (step S213), and when the credit result is obtained in step S212, it registers the generated data in the ticket database TB (step S214), and further notifies the ticket issuing device TD as the terminal device 20 of a report of the result of the service execution (step S215).

[0055] Next, the ticket issuing system TS, as the service providing server 50, notifies the payment system 12 of a payment request together with the token in order to make payment for the usage fee corresponding to the provided service (step S216), and the payment system 12 transmits the payment request to a credit company, etc., i.e., an acquirer AC or a payment gateway operator PG (step S217).

[0056] Through the above-described series of processes for purchasing a commuter pass, the credit card CC can be used as a commuter pass, i.e., a ticket or pass.

[0057] Next, with reference to the block diagram shown in FIG. 7, the overall operation of the service providing system 100 in the case where the automatic ticket gate AG functions as the terminal device 20 will be described. Note that FIG. 7 is a diagram corresponding to FIG. 3 and FIG. 6. For example, in FIG. 7, the automatic ticket gate AG corresponds to the location of the terminal device 20 in FIG. 3. More specifically, the automatic ticket gate AG that functions as the terminal device 20 is configured by attaching a reading unit RD to the automatic ticket gate main body AGa as the terminal device ME. Also, the service providing server 50 is configured by a ticket gate system GS that performs various processes related to ticket gates and a ticket database TB that stores data related to sold commuter passes and the like. Note that the data stored in the ticket database TB is exemplified in FIG. 5(A) and the like. The ticket gate system GS that communicates with the automatic ticket gate main body AGa generates and updates these data. Here, as an example, a case where the purchase procedure is performed using the credit card CC described with reference to FIG. 6, and the credit card CC as the purchased commuter pass is used in the automatic ticket gate AG will be described with reference to FIG. 7.

[0058] First, in the case shown in Fig. 7, similarly to steps S1 to S6 in the case of Fig. 3 and steps S201 to S206 in the case of Fig. 6, a token for the PAN of the credit card CC is generated and notified between the automated ticket gate AG as the terminal device 20 installed at each point (local) and the token management system 11, independently of the presence or absence of a payment (steps S301 to S306), and data related to, for example, a request for admission (request for permission to pass) at the ticket gate is transmitted from the automated ticket gate AG to the ticket gate system GS of the service providing server 50 as a request for service provision (step S307). That is, information related to the exercise of the commuter pass right for permission to pass as a desired service is transmitted from the ticket issuing device TD to the ticket issuing system TS together with a token corresponding to the PAN of the credit card CC.

[0059] The ticket gate system GS of the service providing server 50 that has received the request, as a process for the service to be provided, first reads the data (commuter pass data) related to the corresponding token from the data stored in the ticket database TB (step S308), and judges whether or not it can be used, that is, judges the validity of the exercise of the commuter pass right (step S309). If the ticket gate system GS judges in step S309 that the commuter pass is valid, it notifies the automated ticket gate AG as the terminal device 20 of admission permission in order to execute the service (step S310).

[0060] As described above, the automated ticket gate AG serving as the terminal device 20 determines whether or not passage is permitted based on the ticket or pass information corresponding to the token notified to the automated ticket gate main body AGa serving as the terminal equipment ME.

[0061] Furthermore, in the above cases, unlike the cases of Figures 3 and 6, no processing related to payment (credit processing, payment processing) occurs. Therefore, no fees associated with payment are incurred, and admission is notified promptly. For this reason, the parts related to payment are not shown in Figure 7.

[0062] In addition, in the case of the above-mentioned embodiment, the user's operation at the automatic ticket gate AG is to be able to pass through using a credit card CC in the same procedure as that for passing through using a contactless IC such as Suica (registered trademark), a two-dimensional code such as a QR code (registered trademark), or face authentication. In other words, passing through using a credit card CC can be made common to other methods such as passing through using a contactless IC. In this case, for example, it becomes easy to introduce the service providing system 100 into gate passage in combination with an existing system, and an increase in introduction costs can be suppressed.

[0063] In this embodiment as well, a notification of a token corresponding to a PAN (payment medium ID) is handled separately from the payment process in the service providing system 100, thereby enabling provision of a service based on the token. In particular, in this embodiment, a credit card CC as a physical card (such as a plastic card) can be used as a train station commuter pass, etc.

[0064] In the above embodiment, the ticket issuing system TS and the ticket gate system GS have been described as existing separately, but they may also be configured as an integrated system, with data management associated with the operation of the ticket issuing device TD and the automatic ticket gate AG being carried out centrally.

[0065] As described above, the service providing system 100 in this embodiment includes, for example, an automatic ticket gate AG, a reading unit RD that reads a payment medium ID (PAN of a credit card CC) and notifies the token management system 11 as a token management unit that manages tokenization separately from the payment process and receives notification of the corresponding token, and an automatic ticket gate main body AGa as a terminal device ME that receives the token from the reading unit RD and provides services based on the notified token. In this case, notification of the token corresponding to the PAN (payment medium ID) is performed separately from the payment process, making it possible to provide various services based on the token. In particular, in the case of this embodiment, it is possible to pass through the automatic ticket gate using a credit card CC as a commuter pass or the like as a physical object.

[0066] 〔others〕 The present invention is not limited to the above-described embodiment, and can be embodied in various forms without departing from the spirit and scope of the present invention.

[0067] First, in the second embodiment, the service providing system 100 is incorporated into a system for purchasing tickets (purchasing commuter passes or tickets) at a station. However, the service providing system 100 is not limited to this and can be used in various forms in providing various services. For example, by applying the service providing system 100 to managing entry and exit at an event venue or a membership facility, it is possible to use a credit card CC as a substitute for an admission ticket in combination with other media. In particular, the service providing system 100 can be used in combination even when a process involving payment is required, such as payment with electronic money such as Suica (registered trademark) or payment using QR code (registered trademark). Note that various forms of management at an event venue or a membership facility can be assumed, such as a subscription that can be freely used any number of times for a certain period of time, or a limited number of times that can be used and counted.

[0068] As substitutes for tickets, in addition to the contactless IC and two-dimensional code mentioned above, biometric authentication and the like are also possible, and a combination of these with the service providing system 100 is also possible. [Explanation of symbols]

[0069] 10...payment management server, 11...token management system (token management section), 12...payment system, 20...terminal device, 50...service providing server, 100...service providing system, A, B...location, AC...acquirer, AG...automatic ticket gate, AGa...automatic ticket gate main body, CC...credit card, CD1, CD2, DD1-DD3...data, DT...data table, GS...ticket gate system, GT...gate, ME...terminal device, OU...operation section, PG...payment gateway operator, PP...mounting section, RD...reading section, RP1, RP2...reception section, TB...ticket database, TD...ticket issuing device (ticket vending machine), TDa...ticket issuing device main body, TS...ticket issuing system

Claims

1. A token management unit that manages tokenization of payment medium IDs in a PCI DSS certified server; a reading unit that reads a credit card number as a payment medium ID and notifies the token management unit of the credit card number separately from the payment process and receives a notification of the corresponding token; a terminal device that provides a service based on the token notified from the reading unit separately from the payment processing based on the credit card number; Equipped with A service provision system in which, even when no payment is involved, the token management unit converts the credit card number from the reading unit into a token and notifies the reading unit, the reading unit notifies the terminal device of the token, and the terminal device provides a service based on the notified token.

2. A payment management server as the PCI DSS certified server including the token management unit and a payment system that manages payments using a payment medium, The service providing system according to claim 1 , wherein the payment management server performs tokenization of the payment medium ID in response to the notification from the reading unit separately from a payment process in the payment system.

3. A service providing server that manages information related to the content of the service provided, 3. The service providing system according to claim 2, wherein the terminal device provides a service according to the token notified by the reading unit, among the contents of the contracted service stored in the service providing server.

4. 4. The service providing system according to claim 3, wherein the information managed in said service providing server includes information regarding a right to use a facility for a certain period of time.

5. The service providing server is capable of making an inquiry to the payment system of the payment management server, The service providing system according to claim 3 , wherein the payment management server receives a token notification from the terminal device via the service providing server, and performs credit and payment based on the received token.

6. The service providing system according to any one of claims 1 to 5, wherein the reading unit begins notifying the token management unit when a payment medium is held over a specified medium reading range.

7. a reading unit that reads a credit card number as a payment medium ID, and notifies a token management unit that manages tokenization in a PCI DSS certified server separately from the payment process, and receives a notification of the corresponding token; a terminal device that is notified of the token from the reading unit and provides a service based on the notified token separately from a payment process based on a credit card number; Equipped with An automated ticket gate in which, even when no payment is involved, the token management unit converts the credit card number from the reading unit into a token and notifies the reading unit, the reading unit notifies the terminal device of the token, and the terminal device provides services based on the notified token.

8. 8. The automatic ticket gate according to claim 7, wherein permission for passage is determined based on information on a ticket or pass corresponding to the token notified to the terminal device.

Images