Settlement management system, settlement management program, and settlement management method

Abstract

To provide a new technique enabling smooth and secure settlement.SOLUTION: Provided is a settlement management system for managing a settlement of a customer using a facility. The settlement management system comprises a settlement management device and a user information management system. The settlement management device has a registration part and a settlement part. The registration part registers, in the user information management system, a user ID for identifying facility customers on an application and a facility customer ID for the facility to manage the facility customers in association with each other. The settlement part acquires settlement information regarding facility use from an external first system based on the user ID obtained from a user. The external first system stores the facility customer ID and the settlement information in association with each other.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a payment management system, a payment management program, and a payment management method. [Background technology]

[0002] In recent years, cashless payments have been gaining popularity in various service industries with the aim of improving the efficiency of cash register operations, reducing the workload of cash management, etc. An example of a system that enables such cashless payments is disclosed in, for example, Patent Document 1.

[0003] Patent Document 1 discloses, for example, that a system for accommodation facilities connects to a QR code (registered trademark) payment service and performs payment processing using communications based on the IEEE802 standard or the Mobile Communication System standard, and uses FaaS (Function as a Service), a serverless program execution environment configured on a cloud server, to perform HTTP communications using a RESTful API and send a payment request to a server of a QR code payment service provider. The QR code generated by the QR code payment service provider that received the payment request is dynamically displayed on a smartphone app running on a smartphone that is capable of communicating with the QR code, and the accommodation fee can be paid by scanning it with a QR code reader launched by the QR code payment service app running on the guest's smartphone. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2023-108572 Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the above-mentioned Patent Document 1, every time a payment is made, a payment request must be sent to the server of the QR code payment service, a QR code for the payment must be issued, and the issued QR code must be scanned, which is time-consuming. Also, there is a need for a system that can make payments securely.

[0006] In view of the above problems, an object of the present invention is to provide a novel system that enables smooth and secure payments. [Means for solving the problem]

[0007] In order to solve the above problems, the present invention provides a payment management system that manages payments for customers who use a facility, the payment management system comprising a payment management device and a user information management system, the payment management device having a registration unit and a payment unit, the registration unit linking a user ID for identifying a facility customer on an app with a facility customer ID for the facility to manage the facility customer and registering them in the user information management system, the payment unit acquiring payment information regarding facility usage from an external first system based on the user ID acquired from the user, and the external first system linking and storing the facility customer ID and the payment information.

[0008] With this configuration, payment information can be obtained from the external first system using the user ID obtained from the user, eliminating the need to issue a code for each payment or input the information required for payment, allowing for smooth payment.

[0009] In a preferred embodiment of the present invention, the registration unit links the facility customer ID acquired from the external first system with payment information for making payment for the facility customer and registers them in the external second system, and the payment unit sends a payment request including the payment information acquired from the external first system to the external second system.

[0010] With this configuration, the facility customer ID and payment information of the facility customer obtained from the external first system are registered in the external second system, and payment information obtained from the external first system is sent to the external second system, allowing payment for the facility customer. This allows customers using the facility to make payments without having to enter payment information for each payment, allowing for smooth payment.

[0011] In a preferred embodiment of the present invention, when the registration unit issues the user ID, it acquires the facility customer ID from the external first system, links the facility customer ID and the user ID, and registers them in the user information management system.

[0012] With this configuration, when a user ID is issued, the facility customer ID issued by the external first system is acquired, and the user ID and facility customer ID can be linked and managed. As a result, the user who has been issued a user ID does not need to acquire a facility customer ID for subsequent payments, allowing for smoother payments.

[0013] In a preferred embodiment of the present invention, the registration unit acquires the user ID and a key ID of a key for using a facility from the user, acquires the facility customer ID from the user information management system based on the user ID, links the key ID and the facility customer ID and registers them in the external first system, and the external first system stores the payment information linked to the key ID.

[0014] With this configuration, a user ID and a key ID can be obtained from a user, and a facility customer ID obtained based on the user ID and the key ID can be managed on the external system 1. By obtaining the user ID from a user, the external system 1 can manage the payment information of facility customers, making it easy to manage the user's payment information.

[0015] In a preferred embodiment of the present invention, the payment management system further includes a facility usage management unit, wherein the registration unit accepts input related to check-in, acquires the user ID and the key ID of the key for using the facility from the user, and links the facility customer ID and the key ID based on the user ID and registers them in the external first system; and upon completion of the payment processing for the facility customer, the facility usage management unit releases the link between the facility customer ID and the key ID based on the facility customer ID of the facility customer.

[0016] With this configuration, once a facility customer has completed payment, the link between the user ID and key ID can be updated, allowing another facility customer to process a payment using the same key as a separate user. This prevents another user's payment information from being erroneously reflected. [Effects of the Invention]

[0017] The present invention has the effect of providing a novel technology that enables smooth and secure payments. [Brief explanation of the drawings]

[0018] [Figure 1] 1 is a block diagram illustrating a configuration of a system according to an embodiment. [Figure 2] FIG. 1 is a hardware configuration diagram of a system according to an embodiment. [Figure 3] FIG. 1 is a functional block diagram illustrating a configuration of a system according to an embodiment. [Figure 4] 1 is a processing flowchart of a system according to an embodiment. [Figure 5] 1 is a processing flowchart of a system according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0019] The present invention will now be described more fully with reference to the accompanying drawings, in which preferred embodiments are shown, but which may be embodied in many different forms and are not limited to the embodiments set forth herein.

[0020] For example, while the configuration, operation, etc. of a payment management system are described in this embodiment, methods, devices, computer programs, etc. with similar configurations can also achieve similar effects. The program may also be stored on a recording medium. Using this recording medium, the program can be installed on a computer, for example, to configure a payment management device and payment management system. Here, the recording medium storing the program may be a non-transitory recording medium, such as a CD-ROM.

[0021] The present invention relates to a system for managing payments for customers who use facilities. In this invention, payment is completed by accepting a payment request for facility usage fees (total amount of facility basic fee, meal fee, service usage fee, product rental fee, product purchase fee, etc.) incurred within the facility. Note that the facility in this invention is a bathing facility, but the type of facility is not limited to this.

[0022] <1. System configuration> FIG. 1 is a block diagram showing the configuration of a system according to one embodiment. As shown in FIG. 1, a payment management system 0 includes a payment management device 1, an information management system 3, a payment processing system 4, a facility customer database 5, a payment database 6, and a user terminal device 7, and is configured to be able to communicate via a communication network NW. In this embodiment, the payment management device 1 includes a user information management system 2 that is able to communicate via wired or wireless communication, and manages user information in the user information management system 2. The information management system 3 and the payment processing system 4 are external systems, with the information management system 3 being an external first system and the payment processing system 4 being an external second system. In this embodiment, the communication network NW is an IP (Internet Protocol) network, but there are no limitations on the type of communication protocol, and there are also no limitations on the type or scale of the network.

[0023] In this embodiment, the payment management device 1, information management system 3, and payment processing system 4 can be implemented using general-purpose server computers, personal computers, smartphones, tablet terminals, wearable devices, etc. The user terminal device 7 can be implemented using smartphones, tablet terminals, personal computers, wearable devices, etc. In this embodiment, the payment management device 1 is configured using one computer, but it can also be configured using multiple computers.

[0024] The user information management system 2 stores user information regarding users who use the app of the present invention, and user linking information indicating the relationship between users who use the facility (facility customers) and users who use the app of the present invention. The user information includes a user ID that uniquely identifies a user on the application, a user name, contact information, etc. Note that a terminal ID that uniquely identifies the user terminal device 7 may be used as the user ID. As the user association information, a user ID that uniquely identifies a user in the app is stored in association with a facility customer ID that uniquely identifies a facility customer who has registered as a member at a facility.

[0025] The information management system 3 records and manages information relating to facility usage in the facility customer database 5, such as facility customer information, facility sales information, facility usage status information, and key usage information indicating which user is using the key to use the facility. Facility customer information is information about customers who use a facility, and includes a facility customer ID that uniquely identifies a customer who has registered as a member at the facility, the facility customer name, gender, contact information, date of birth, the facility use pass ID, and the number of facility use passes. Facility sales information is information related to facility sales, and as facility sales information, payment information, payment status (before checkout, waiting for payment, or paid), acceptance date, etc. are stored in association with a key ID. Here, payment information is information related to the usage fee incurred when using each service of the facility, and the product, product unit price, and quantity are registered. Note that the payment information may register the product unit price x quantity for each product in addition to or instead of the product unit price and quantity. Facility usage status information is information related to the usage status of a facility, and the facility usage status information is stored in association with a key ID, a key number, and a key status indicating the usage status of the key (before check-in (after check-out), or after check-in (before check-out)). Note that the key ID and the key number may be the same. The key usage information stores a combination of a facility customer ID and a key ID that uniquely identifies a key for using the facility. Note that the key in this embodiment refers to a physical key, such as a locker key for the facility.

[0026] The payment processing system 4 records and manages user payment information in the payment database 6 as information related to user payments, linking it to information identifying facility customers. Here, the payment information is information related to electronic payments for facility customer payments, and specifically, for example, credit card information, debit card information, prepaid card information, electronic money information, point information, etc. may be used as payment information. In this embodiment, the information identifying facility customers that is linked to the user payment information and stored is a facility customer ID, but it may also be a user ID.

[0027] <1.1. Hardware Configuration> 2 is a hardware configuration diagram. As shown in FIG. 2(a), the server 10 (payment management device 1) includes a processing unit 101, a storage unit 102, and a communication unit 103.

[0028] The processing unit 101 has a processor such as a CPU that can execute an instruction set, and controls the overall operation and processing of the payment management device 1 by executing the payment management program according to the present invention, an OS, and other applications. The storage unit 102 has a volatile memory such as a RAM capable of storing an instruction set, and a non-volatile recording medium such as an HDD or SSD capable of recording an OS, a payment management program, and the like. The communication unit 103 has a communication interface device for connecting to a network, and controls communication with the communication network NW to input and output information.

[0029] As shown in FIG. 2(b), the terminal device 9 (user terminal device 7) includes a processing unit 91, a storage unit 92, a communication unit 93, an input unit 94, and an output unit 95.

[0030] The processing unit 91 has a processor such as a CPU that can execute an instruction set, and controls the overall operating processing of the payment management device 1 by executing a payment management device usage program, an OS, and other applications for using the payment management device 1. The storage unit 92 has a volatile memory such as a RAM capable of storing an instruction set, and a non-volatile recording medium such as an HDD or SSD capable of recording an OS, a program for using the payment management device, and the like. The communication unit 93 has a communication interface device for connecting to a network, and controls communication with the communication network NW to input and output information. The input unit 94 has an input device capable of input processing, such as a keyboard or a touch panel. The output unit 95 has a display device capable of display processing, such as a display.

[0031] The following functions may be executed by installing the payment management program of this embodiment in the information management system 3 or the payment processing system 4 and causing the information management system 3 or the payment processing system 4 to function as the payment management device 1. The information management system 3 and the payment processing system 4 may also have the functional configurations of the payment management system.

[0032] <1.2. System Functional Configuration> 2 is a diagram showing the functional configuration of the payment management system 0 of this embodiment. The payment management system 0 of this embodiment includes a payment management device 1, which is equipped with a registration unit 11, a facility usage management unit 12, a payment unit 13, and a display processing unit 14. This is information processing by software (stored in the memory unit 102 / memory unit 902) specifically realized by hardware (processing units 101 / 901, etc.).

[0033] In this embodiment, the payment management system 0 is used via a user terminal device 7 that executes a payment management device utilization program, but the payment management device 1 may also be configured by installing a payment management program on the user terminal device 7.

[0034] <2. Processing Flowchart> Next, the payment management method of the present invention will be described with reference to Fig. 4. Fig. 4 is a flowchart showing the process in which a customer using a facility registers as a member of the app and displays screens related to the appropriate procedures, thereby completing payment when using the facility. The process related to the payment management method in this embodiment can be broadly divided into pre-processing (A), check-in and linking processing (B), payment information registration processing (C), and check-out processing (D).

[0035] <2.1. Pre-treatment (A)> In the pre-processing (A), a facility customer who has registered as a member to use the facility registers as a member of the app of the present invention, and the payment management device 1 executes a process of registering user association information that associates the user of the facility customer with the user of the app (see FIG. 5). Note that the following description will be given assuming that the user has registered payment information in the payment processing system in advance.

[0036] <2.1.1. Registering facility customer information in the facility customer database 5> First, in step SA01 (hereinafter, "step SXXX" will be referred to as "SXXX"), the user terminal device 7 accepts input from the facility customer regarding membership registration for the app, and in SA02, transmits to the registration unit 11 a request for issuance of a user ID, which is information that identifies the facility customer and uniquely identifies the user of the app. In this embodiment, the registration unit 11 accepts facility customer information, such as the facility customer's name, address, contact information, and facility name, along with the request for issuance of the user ID. Then, in SA03, the registration unit 11 issues the user ID.

[0037] <2.1.2. Linking facility customer ID and user ID> Next, in SA04 to SA07, the registration unit 11 associates the facility customer ID, which is information for identifying the facility customer, with the user ID and registers them in the user information management system 2. Here, the registration process is a process in which the registration unit 11 sends a registration request and causes the user information management system 2 to register the information.

[0038] In SA04, the registration unit 11 transmits a facility customer ID issuance request to the information management system 3. In this embodiment, the registration unit 11 transmits the facility customer information received in SA02 along with the facility customer ID issuance request to the information management system 3. Then, in SA05, the information management system 3 registers the facility customer information in the facility customer database 5, and the registration unit 11 acquires the facility customer ID issued by the information management system 3.

[0039] In SA06, the registration unit 11 transmits the facility customer ID and the user ID to the user information management system 2. In this embodiment, the registration unit 11 transmits the user ID issued in SA03 and the facility customer ID acquired in SA05 to the user information management system 2. Then, in SA07, the registration unit 11 registers the user ID and user association information linked to the facility customer ID in the user information management system 2.

[0040] <2.1.3. Registering facility customer ID in payment database 6> In SA08 to SA011, the registration unit 11 registers the facility customer ID issued by the information management system 3 and the user's payment information in the payment database 6. Here, the registration process is a process in which the registration unit 11 sends a registration request to the payment processing system 4 to register the information.

[0041] In SA08, the registration unit 11 transmits the facility customer ID acquired from the information management system 3 to the user terminal device 7. In this embodiment, the registration unit 11 transmits to the user terminal device 7, together with the facility customer ID acquired in SA05, an acquisition request to acquire payment information from the facility customer, and a registration request to link the facility customer ID and the payment information and register them in the payment database 6.

[0042] In SA09, the user terminal device 7 displays a screen for identifying payment information from the facility customer based on the acquisition request received in SA08, and accepts the payment information. In this embodiment, information for identifying payment information includes a membership number, an expiration date, etc. Then, in SA10, the user terminal device 7 transmits information for identifying the facility customer ID and payment information to the payment processing system 4 based on the registration request received in SA08. Then, in SA11, the payment processing system 4 links the facility customer's payment information and facility customer ID and registers them in the payment database 6 based on the information for identifying the payment information.

[0043] <2.2. Check-in and linking process (B)> In the check-in and linking process (B), a user who has acquired a key for using the facility enters the facility, and a linking process between the user ID and the key ID is executed. In this embodiment, the user can enter the facility by having the barcode attached to the key read by a barcode reader provided at the entrance gate.

[0044] <2.2.1. Key Status Update> In SB01, the information management system 3 acquires a key ID via the entrance gate as an input related to check-in, and updates the key status of the facility usage information based on the key ID (updating from before check-in to after check-in).

[0045] <2.2.2. Linking Key ID and Facility Customer ID> In SB02 to SB06, the facility usage management unit 12 performs a process of linking information identifying a facility customer with a key ID. Here, the linking process is a process in which the facility usage management unit 12 sends a linking request to the information management system 3 to link and register the information.

[0046] In SB02, the facility usage management unit 12 acquires a key ID and information identifying the facility customer. In this embodiment, the facility usage management unit 12 acquires one or more key IDs input by the facility customer via the user terminal device 7 or the facility reception machine, and a user ID as information identifying the facility customer.

[0047] Next, in SB03-04, the facility use management unit 12 acquires a facility customer ID from the user information management system 2 based on the user ID. In this embodiment, the facility use management unit 12 transmits a facility customer ID acquisition request including the user ID acquired in SB02 to the user information management system 2 (SB03). Then, the facility use management unit 12 acquires the facility customer ID linked to the user ID from the user information management system 2 based on the user association information (SB04).

[0048] Then, in SB05-06, the facility use management unit 12 links the key ID and facility customer ID and registers them in the facility customer database 5. In this embodiment, the facility use management unit 12 sends an association request including one or more key IDs acquired in SB02 and the facility customer ID acquired in SB04 to the information management system 3 (SB05). Then, the information management system 3 registers the key use information linked to the one or more key IDs acquired in SB05 and the facility customer ID in the facility customer database 5 (SB06).

[0049] In this embodiment, the facility customer ID is registered in association with the key ID as information for identifying the facility customer, but instead of the facility customer ID, the user ID may be registered in association with the key ID. Also, when multiple key IDs are registered in association with the facility customer ID, the selection input of a representative key ID (representative key ID) may be accepted.

[0050] <2.3. Payment Information Registration Process (C)> In the payment information registration process (C), a process is executed to register payment information generated when a user uses facility services.

[0051] <2.3.1. Registering payment information> In SC01, the information management system 3 registers payment information linked to a key ID. In this embodiment, when paying for each service at a facility, the information management system 3 acquires a key ID by reading a barcode attached to a key linked to a facility customer ID, and registers payment information including the key ID and the usage fee for each service linked to the key ID. In this embodiment, if a key ID not linked to a facility customer ID is acquired, an instruction to link the key ID and the facility customer ID is displayed to the facility customer via the facility terminal. In addition, in SB06, if multiple key IDs are linked to facility customer IDs and a key ID is acquired from a barcode attached to a key other than the representative key, the payment information may be registered linked to the representative key ID linked via the key ID and the facility customer ID.

[0052] <2.4. Checkout Process (D)> In the checkout process (D), the facility customer operates the user terminal device 7 to carry out procedures related to checkout, thereby executing the payment process.

[0053] <2.4.1. Acquisition of payment information> In SD01 to SD06, payment information is acquired using information identifying the facility customer and a key ID linked to the information identifying the facility customer.

[0054] In SD01, the user terminal device 7 receives input related to check-out from the facility customer, and in SD02, the settlement unit 13 receives the user ID from the user terminal device 7.

[0055] In SD03-04, the settlement unit 13 acquires a facility customer ID from the user information management system 2. In this embodiment, the settlement unit 13 sends a facility customer ID acquisition request including the user ID acquired in SD02 to the user information management system 2 (SD03). Then, the settlement unit 13 acquires the facility customer ID linked to the user ID from the user information management system 2 based on the user association information (SD04). Then, the process proceeds to SD05.

[0056] In addition, if the settlement unit 13 receives input regarding the use of the facility use coupon and the facility use coupon ID in addition to the user ID in SD02, it determines that the settlement has already been completed and proceeds to SD10.

[0057] In SD05-06, the payment unit 13 acquires payment information based on a facility customer ID, which is information that identifies a facility customer. In this embodiment, the payment unit 13 sends a payment information acquisition request including the facility customer ID acquired in SD04 to the information management system 3 (SD05). Then, the payment unit 13 acquires payment information from the information management system 3 based on one or more key IDs linked to the facility customer ID (SD06).

[0058] In this embodiment, if the input of multiple key IDs is not accepted at check-in, the input of a key ID for payment can be accepted at the same time at check-out, and payment can be made. Specifically, the facility usage management unit 12 accepts the input of multiple key IDs for payment in SD01 via the user terminal device 7, transmits the facility customer ID and the multiple key IDs to the information management system 3 in SD05, and acquires payment information linked to each key ID.

[0059] <2.4.2. Payment Processing> In SD07-SD09, the payment unit 13 executes payment processing based on the acquired payment information. In this embodiment, the payment unit 13 sends a payment request including the payment information acquired in SD06 and the facility customer ID acquired in SD04 to the payment processing system 4 (SD07). Then, the payment processing system performs payment for the facility customer identified by the facility customer ID based on the facility customer ID and the payment information. In this embodiment, the payment processing system 4 performs payment based on the payment information and payment information linked to the facility customer ID (SD08).

[0060] If a user ID is stored in the payment database 6 instead of the facility customer ID as information for identifying the facility customer, the payment unit 13 transmits the user ID to the payment processing system 4 in SD07.

[0061] <2.4.3. Unlinking Key ID and User ID, and Updating Information> In SD09 to SD012, the facility use management unit 12 performs a process of canceling the association between the key ID and the information identifying the facility customer, and a process of updating the key status and payment information. Here, the process of canceling the association is a process in which the facility use management unit 12 sends a request to cancel the association to cause the information management system 3 to delete the combination of information that has been associated with the key ID and the information management system 3. In addition, the process of updating is a process in which the facility use management unit 12 sends an update request to cause the information management system 3 to update the information.

[0062] In SD09, the facility use management unit 12 receives a notification that payment has been completed or that payment is possible, and in SD10, the facility use management unit 12 transmits a request to release the link between the key ID and facility customer ID, including the facility customer ID of the facility customer who performed the payment process, and a request to update the key status and payment information, to the information management system 3. In this embodiment, upon receiving a notification that payment has been completed or that payment is possible, the facility use management unit 12 considers the payment process for the facility customer to be complete, and upon completion of the payment process, transmits a request to release the link and a request to update the information management system 3, including the facility customer ID of the facility customer who performed the payment process in SD07-08.

[0063] <2.4.4. Status Update> Then, in SD11, the information management system 3 updates the payment information and the status of the key. In this embodiment, based on the update request sent in SD10, the facility use management unit 12 causes the information management system 3 to update the status of the payment information (payment status) stored in association with the facility customer ID included in the update request from before check-out to "waiting for payment" or "payment completed," and update the status of the key associated with the facility customer ID from before check-out to after check-out.

[0064] Then, in SD12, the facility usage management unit 12 causes the information management system 3 to delete the combination of the key ID and the facility customer ID based on the facility customer ID included in the link release request.

[0065] If the payment unit 13 has accepted the ID of the facility use coupon in SD02, the facility use management unit 12 sends an association release request including the facility customer ID and an update request to the information management system 3. Then, the information management system 3 updates the status and key status of the payment information based on the key ID associated with the facility customer ID, updates the facility use coupon count in the facility customer information associated with the facility customer ID, and deletes the combination of the facility customer ID and the key ID.

[0066] As described above, by processing SA01 to SD12, customers using the facility can pay for the facility fee without visiting the reception desk. This eliminates the waiting time for payment that occurs at the reception desk. In addition, by sending the facility customer ID to the payment processing system each time payment is made, the problem of the user's payment information being leaked can be prevented, and secure payments can be achieved.

[0067] Furthermore, since payment does not have to be made at the reception desk, there is no need to wait in a waiting space for payment, which reduces the cost of creating a waiting space.Furthermore, there is no need to install a device for payment, which reduces the space required to install the device and the costs of manufacturing and installing the device.

[0068] In this embodiment, the payment process refers to the process in which the payment management device 1 transmits the facility customer ID and payment information to the payment processing system, and also transmits a request for payment processing. Alternatively, the payment management device 1 may store the payment information of the facility customer and perform payment based on the payment information. The payment method may be deferred payment or immediate payment. [Explanation of symbols]

[0069] 0: Payment management system 1: Payment management device 2: User information management system 3: Information management system (external system 1) 4: Facility customer database 5: Payment processing system (external second system) 6: Payment database 7: User terminal device 10: Server 101: Processing section 102: Storage section 103: Communications Department 9: Terminal device 91: Processing section 92: Storage section 93: Communications Department 94: Input section 95: Output section 11: Registration section 12: Facility Use Management Department 13: Payment Department 14: Display processing section

Claims

1. A payment management system for managing payments made by customers using a facility, The payment management system includes a payment management device and a user information management system, the settlement management device includes a registration unit and a settlement unit; the registration unit associates a user ID for identifying the facility customer on the app with a facility customer ID for managing the facility customer by the facility, and registers the user ID in the user information management system; the payment unit acquires payment information related to facility use from an external first system based on the user ID acquired from the user; The external first system stores the facility customer ID and the payment information in association with each other. Payment management system.

2. the registration unit links the facility customer ID acquired from the external first system with payment information for making a payment for the facility customer, and registers the linked information in the external second system; The settlement unit transmits a settlement request including the settlement information acquired from the external first system to the external second system. The payment management system according to claim 1 .

3. When the user ID is issued, the registration unit acquires the facility customer ID from the external first system, and associates the facility customer ID with the user ID and registers them in the user information management system. The payment management system according to claim 1 .

4. the registration unit acquires the user ID and a key ID of a key for using a facility from the user, acquires the facility customer ID from the user information management system based on the user ID, and performs a registration process in the external first system by linking the key ID and the facility customer ID; The external first system stores the payment information in association with the key ID. The payment management system according to claim 1 .

5. The payment management system further includes a facility usage management unit, the registration unit receives input related to check-in, acquires the user ID and a key ID of a key for using a facility from the user, and performs a registration process in the external first system by linking the facility customer ID and the key ID based on the user ID; When the payment process of the facility customer is completed, the facility usage management unit performs processing to release the association between the facility customer ID and the key ID based on the facility customer ID of the facility customer. The payment management system according to claim 1 .

6. A payment management program for managing payments made by customers using a facility, the payment management program causes a computer to function as a registration unit and a payment unit; the registration unit associates a user ID for identifying the facility customer on the app with a facility customer ID for managing the facility customer by the facility, and registers the user ID in a user information management system; The settlement unit acquires settlement information regarding facility use from an external first system based on the user ID acquired from the user. The external first system stores the facility customer ID and the payment information in association with each other. Payment management program.

7. A payment management method for managing payments made by customers using a facility, comprising: The computer A process of linking a user ID for identifying facility customers on the app with a facility customer ID for the facility to manage facility customers, and registering them in a user information management system; and acquiring payment information regarding facility use from an external first system based on the user ID acquired from the user; The external first system stores the facility customer ID and the payment information in association with each other. Payment management methods.

Images