Labor management server, credit card management server, labor management method, credit card management method and program

Abstract

To provide a labor management server, labor management method, program, etc. capable of improving convenience for users by facilitating registration of salary receiving accounts.SOLUTION: A labor management server capable of communicating with terminal devices operated by company employees and an information processing device for providing services, the labor management server includes: a generation unit that generates application activation information including employee identification information for identifying an employee, server identification information for identifying the labor management server, and a link for activating an application for using the services; a transmission unit that transmits the application activation information to the information processing device; a receiving unit that receives an account linkage result between the labor management server and the information processing device from the information processing device; and an account management unit that manages account information of the employee in the services included in the account linkage result as a transfer account of the employee.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to a labor management server, a credit card management server, a labor management method, a credit card management method, and a program. [Background technology]

[0002] Conventionally, electronic payment services using user terminal devices owned by users have been known. For example, Patent Document 1 proposes an electronic payment system in which code information such as a barcode or QR code (registered trademark) is displayed on a user terminal device and the code information is read by a store terminal device installed in a store, thereby executing electronic payment. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2022-157339 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the electronic payment system described in Patent Document 1 was unable to link account information (for example, fund transfer account information) managed by the electronic payment system with external services. As a result, in order to register account information managed by the electronic payment system with an external service, the user himself had to register the account information with the external service he wanted to link, which could be inconvenient for the user.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objects is to provide a labor management server, a credit card management server, a labor management method, a credit card management method, and a program that allow account information to be easily registered and improve convenience for users. [Means for solving the problem]

[0006] One aspect of the present invention is a labor management server capable of communicating with a terminal device operated by an employee of a company and an information processing device that provides a service, the labor management server comprising: a generation unit that generates app launch information including employee identification information for identifying the employee, server identification information for identifying the labor management server, and a link for launching an app for using the service; a transmission unit that transmits the app launch information to the terminal device; a reception unit that receives from the information processing device an account linking result between the labor management server and the information processing device; and an account management unit that manages the employee's account information for the service included in the account linking result as a transfer account for the employee's salary. is. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to provide a labor management server, a credit card management server, a labor management method, a credit card management method, and a program that allow account information to be easily registered, thereby improving convenience for users. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] FIG. 2 is a configuration diagram of a payment server 100. [Figure 5] FIG. 10 is a diagram showing an example of the contents of user information 182. [Figure 6] FIG. 10 is a diagram showing an example of the contents of affiliated store / store information 186. [Figure 7] FIG. 3 is a configuration diagram of a labor management server 300. [Figure 8] FIG. 10 is a diagram showing an example of the contents of employee information 372. [Figure 9] FIG. 10 is a sequence diagram showing an example of a process executed by the employee terminal device 600, the labor management server 300, the payment server 100, and the user terminal device 200 to set the salary transfer method to electronic money. [Figure 10] FIG. 10 is a diagram showing an example of a salary deposit account setting window W1 in the labor management system. [Figure 11] FIG. 10 is a diagram showing an example of a QR code display window W2 in the labor management system. [Figure 12] FIG. 10 is a diagram illustrating an example of a salary receipt setting screen. [Figure 13] FIG. 10 is a sequence diagram showing an example of a process executed by the labor management server 300, the payment server 100, and the user terminal device 200 to set the salary transfer method to electronic money. [Figure 14] FIG. 4 is a diagram illustrating the configuration of a bank server 400. [Figure 15] FIG. 10 is a diagram showing an example of the contents of bank account information 472. [Figure 16] 10 is a sequence diagram showing an example of a process executed by the employee terminal device 600, the labor management server 300, the bank server 400, and the user terminal device 200 to set a salary transfer method to a bank account. [Figure 17] 10 is a sequence diagram showing an example of a process executed by the labor management server 300, the bank server 400, and the user terminal device 200 to set a salary transfer method to a bank account. [Figure 18] FIG. 5 is a diagram illustrating the configuration of a credit card management server 500. [Figure 19] FIG. 10 is a diagram showing an example of the contents of card information 572. [Figure 20] 10 is a sequence diagram showing an example of a process for setting up a credit card withdrawal account, which is executed by the employee terminal device 600, the credit card management server 500, the bank server 400, and the user terminal device 200. FIG. [Figure 21]10 is a sequence diagram showing an example of a process for setting a debit account for a credit card, which is executed by the credit card management server 500, the bank server 400, and the user terminal device 200. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0009] Below, with reference to the drawings, embodiments of a labor management server, a credit card management server, a labor management method, a credit card management method, and a program will be described. Various devices, such as the "server" mentioned below, that provide services to users and perform internal analysis may be realized by a group of distributed devices, and each device may be operated by a different business. Furthermore, the owner of the device's hardware (the cloud server provider) and the business that actually operates it may also be different. An electronic payment service is a service that supports payments for the purchase of goods and services at a store. A store is, for example, a physical store (real-world store) that exists in real space, but may also include a virtual store for e-commerce. Virtual stores may also include those provided by entities other than the operator of the electronic payment service. In such cases, when making a payment for a purchase at a virtual store, the user is controlled to transition to the interface screen of the electronic payment service. In an electronic payment service, a store is treated as belonging to, for example, an affiliated store (brand), and when a purchase is made at a store, processing such as payment is primarily conducted between the user and the affiliated store. Alternatively, processing such as payment may be conducted between the user and the store.

[0010] First Embodiment [Electronic payment service] Figure 1 shows an example of a configuration for realizing an electronic payment service. The electronic payment service is realized mainly by a payment server 100. The payment server 100 communicates with, for example, one or more user terminal devices 200, one or more first store terminal devices 50, one or more second store terminal devices 70, a labor management server 300, a bank server 400, a credit card management server 500, and an employee terminal device 600 via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, etc.

[0011] The user terminal device 200 is, for example, a portable terminal device such as a smartphone or a tablet terminal. The user terminal device 200 is a computer device having at least an optical reading function, a communication function, a display function, an input acceptance function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a central processing unit (CPU), etc. In the user terminal device 200, a processor such as a CPU executes a payment application (hereinafter referred to as a payment app) 20, which operates in cooperation with the payment server 100 to provide electronic payment services to users. In addition, a processor such as a CPU executes a bank application (hereinafter referred to as a bank app) 30 in the user terminal device 200, which operates in cooperation with the bank server 400 to provide bank services to users. The payment app 20 and the bank app 30 are installed in the user terminal device 200 from, for example, an application store, and control the camera, communication device, touch panel, etc.

[0012] The first store terminal device 50 is installed, for example, in a store. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 includes a so-called POS (Point of Sale) device, and the product price acquisition function and the optical reading function may be realized by the POS device. The store code image 60 is placed in the store and is a code image such as a QR code (registered trademark) printed on a paper or plastic medium. The store code image 60 may be displayed on a display placed in the store (which may be the display of a terminal device such as a smartphone).

[0013] The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, tablet terminal, personal computer, etc. An interface for affiliated stores 72 runs on the second store terminal device 70. The interface for affiliated stores 72 may be an app for affiliated stores or a browser. The interface for affiliated stores 72 accepts coupon settings and the like from the operator of the affiliated store and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone, has the function of displaying a code image corresponding to a store code image and reading the code image displayed by the user terminal device 200 by executing the app for affiliated stores.

[0014] The payment server 100 realizes electronic payment based on payment information received from the user terminal device 200 or the first store terminal device 50. The first store terminal device 50 may include a POS device and an affiliated store server, in which case payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, this distinction will not be made and it is assumed that payment information is sent from the first store terminal device 50.

[0015] The labor management server 300 is a computer that manages information related to employee labor in a company, and communicates with the payment server 100, the bank server 400, and the employee terminal device 600 via the network NW. As will be described in detail later, the labor management server 300 provides services such as managing employee information and linking with attendance management systems and payroll management systems.

[0016] The bank server 400 is a computer that manages information related to bank accounts, and communicates with the user terminal device 200 and the labor management server 300 via the network NW. As will be described in detail later, the bank server 400 provides bank-related services (deposits, transfers, etc.).

[0017] The credit card management server 500 is a computer managed by a credit card company, and communicates with the user terminal device 200, the bank server 400, and the employee terminal device 600 via the network NW. As will be described in detail later, the credit card management server 500 provides credit card-related services (such as credit card payments).

[0018] The employee terminal device 600 is a computer operated by an employee of the company, and communicates with the labor management server 300 and the credit card management server 500 via the network NW. As will be described in detail later, the employee terminal device 600 is used to use services provided by the labor management server 300 and the credit card management server 500.

[0019] 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns for electronic payment: Pattern 1 and Pattern 2.

[0020] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, user terminal device 200, with payment application 20 running, decodes store code image 60 using its optical reading function (S1). Store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is the domain of the electronic payment service to which store identification information has been added, and is associated with an affiliated store ID, store ID, etc. in payment server 100 (described below). Payment application 20 sends first payment information including the store URL and account ID to payment server 100 (S2). Payment server 100 searches for store information (described below) using the affiliated store ID and store ID corresponding to the store URL, acquires information on the affiliated store name and store name (S3), and sends this information to payment application 20 (S4). The user enters the payment amount into user terminal device 200 on the screen displaying the affiliated store name and store name (S5). Then, the user terminal device 200 generates second payment information including at least the payment amount and sends it to the payment server 100 (S6). The payment server 100 makes the electronic payment based on the received second payment information (S7). The payment server 100 then sends a payment completion notice (information for displaying a payment completion screen) to the payment app 20 (S8), and the payment app 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include information on the payment amount in addition to the store URL. In this case, the step of the user inputting the payment amount is omitted, and the payment amount information is included in the first payment information and sent to the payment server 100. Information on the affiliated store name and store name may be included and displayed on the payment completion screen.

[0021] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, the payment app 20 sends a request to issue a one-time code to the payment server 100 when the payment app 20 is launched, when a payment operation is performed in the payment app 20, at the automatic update timing (e.g., every minute), and at other timings (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment app 20 (S13). The payment app 20 displays a code image, such as a QR code (registered trademark) or barcode, generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 200 over the first in-store terminal device 50, and the first in-store terminal device 50 decodes the code image using its optical reading function and acquires the one-time code, etc. (S15). The first in-store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode, manually entering it, etc. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs electronic payment (S17). Then, the payment server 100 sends a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0022] Note that electronic payment may be performed using only one of the above patterns. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuing a one-time code may be omitted in store scanning, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0023] [Payment server] 4 is a configuration diagram of the payment server 100. The payment server 100 includes, for example, a communication unit 110, a payment content providing unit 120, a payment processing unit 130, an information management unit 140, a receiving unit 150, an acquiring unit 160, a transmitting unit 170, and a storage unit 180. The components other than the communication unit 110 and the storage unit 180 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a GPU (Graphics Processing Unit), or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD (Hard Disk Drive) or flash memory (a storage device with a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0024] The storage unit 180 is a hard disk drive (HDD), a flash memory, a random access memory (RAM), etc. The storage unit 180 may be a network attached storage (NAS) device that can be accessed by the payment server 100 via a network. The storage unit 180 stores information such as user information 182, payment content information 184, and affiliated store / shop information 186.

[0025] The communication unit 110 is a communication interface for connecting to the network NW, and is, for example, a network interface card.

[0026] The payment content providing unit 120 has, for example, a function of a web server, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 200. The payment content providing unit 120 reads out necessary content from the payment content information 184 as appropriate and provides it to the user terminal device 200. The user terminal device 200 accepts various inputs from the user while content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

[0027] The payment processing unit 130 performs payment processing based on the payment information transmitted by the user terminal device 200 or the first store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 182.

[0028] FIG. 5 is a diagram showing an example of the contents of user information 182. User information 182 is an example of user registration information. User information 182 includes, for example, a user URL, account ID, telephone number, and password, as well as an email address, user ID, name, address, gender, date of birth, registration date, remaining balance, credit card payment settings, credit card limit, credit card payment amount, available credit card payment amount, payment method settings, bank account, credit card number, charge history information, payment history information, employee ID, server ID, and virtual account information. The user URL is used for remittance processing between users. When registering for the electronic payment service, registration of a phone number and password is required. The account ID is issued to the user by the payment server 100, and the user ID can be set by the user (or does not have to be set). The email address, name, address, and date of birth are also information that can be set by the user (or do not have to be set). The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). Hereinafter, the user's instance (electronic payment account) to which this information is associated will be referred to as an account.

[0029] The charge balance indicates the balance of electronic money set by the user by transferring funds to the account in advance. Transfer methods include transfers from a designated bank's ATM (Automatic Teller Machine) or from a registered bank account. The credit payment setting indicates whether the settings for electronic credit payment have been completed and is set to either "completed" or "not completed." The credit payment limit is the monthly credit payment limit. The credit payment amount is the amount of credit payment already used in the current month. The available credit payment amount is the amount of credit payment available in the current month, calculated by subtracting the credit payment amount from the credit payment limit. While the figure shows only one credit payment limit, in reality, there may also be daily limits, and the lower of these may be set as the credit payment limit. Further details on credit payments will be described later. The payment method setting indicates whether the user will currently make electronic payments using the charge balance or by credit payment. The bank account and credit card number are information on the bank account or credit card number (account number, card number) that can be used to deposit funds into the electronic payment service. The charge history information is a history of the user transferring funds to the electronic payment service in advance to increase the charge balance. The payment history information is information that shows the details of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.). The employee ID is identification information used to identify the employee. The server ID is identification information used to identify the labor management server 300. The virtual account information is information related to bank accounts (bank name, branch number, account number, etc.) linked to each employee and owned by the company that operates the electronic payment service.

[0030] 6 is a diagram showing an example of the contents of affiliated store / store information 186. The affiliated store / store information 186 includes, for example, a first table 186A in which an affiliated store ID and a store ID are associated with a store URL, a second table 186B in which an affiliated store ID is associated with an affiliated store name and sales amount, and a third table 186C in which a store ID is associated with a store name. In addition to this information, the affiliated store / store information 186 may also include information such as the category of the affiliated store or store, the store's location, and payment patterns.

[0031] The information management unit 140 manages the user information 182 and the affiliated store / store information 186 based on information acquired from the user terminal device 200 and the second store terminal device 70. For example, the information management unit 140 adds, edits, deletes, etc. new records for the user information 182 and the affiliated store / store information 186.

[0032] The receiving unit 150 receives various information (e.g., account linking applications) from other devices by controlling the communication unit 110. The acquiring unit 160 acquires employee virtual account information. The transmitting unit 170 transmits various information (e.g., account linking results) to other devices by controlling the communication unit 110. Details of the processing by the receiving unit 150, acquiring unit 160, and transmitting unit 170 will be described later.

[0033] [Electronic Payment] When payment information is acquired from the user terminal device 200 or the first store terminal device 50, the payment processing unit 130 refers to the user information 182 to acquire the "payment method setting" of the user. For users whose "payment method setting" is set to "charge balance," the payment processing unit 130 performs electronic payment as follows: For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales proceeds. The item value of the affiliated store's sales proceeds is not itself used as electronic money, for example, but rather the amount corresponding to the item value of the sales proceeds is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

[0034] The payment processing unit 130 performs electronic payments for users whose "Payment Method Setting" is set to "Credit Card Payment" as follows. Credit card payment is a payment method in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service. The operator of the electronic payment service acts as the creditor, and allows electronic payments within the credit card payment limit, independent of the remaining balance. To receive the credit card payment service, a user may be required to obtain a credit card provided by the operator of the electronic payment service. The monthly amount used for credit card payment is settled on the following month's payment date, for example, by debit from a bank account. In this case, the payment processing unit 130 makes a provisional settlement by adding the settlement amount to the credit card payment amount and subtracting the same amount from the available credit card balance. On the closing date, the payment processing unit 130 performs the process described above to debit the current month's payment on the following month's payment date, or requests the credit card company operator to perform this process. If the settlement amount exceeds the available credit card balance at the time of provisional settlement, an error notification is returned to the payment app 20.

[0035] [Labor management server] FIG. 7 is a configuration diagram of the labor management server 300. The labor management server 300 includes, for example, a communication unit 310, a login processing unit 320, a generation unit 330, an account management unit 340, a receiving unit 350, a transmission unit 360, and a storage unit 370. The components other than the communication unit 310 and the storage unit 370 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be implemented by a combination of software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as an HDD or flash memory, or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive.

[0036] The storage unit 370 is a hard disk drive (HDD), flash memory, RAM (Random Access Memory), etc. The storage unit 370 may be a NAS device that the labor management server 300 can access via a network. The storage unit 370 stores employee information 372.

[0037] The communication unit 310 is a communication interface for connecting to the network NW, and is, for example, a network interface card.

[0038] The login processing unit 320 accepts logins from employees. The generation unit 330 generates application startup information for starting the payment application 20 on the user terminal device 200. The account management unit 340 manages the employee's salary deposit account. The reception unit 350 controls the communication unit 310 to receive various information (e.g., account linking results) from other devices. The transmission unit 360 controls the communication unit 310 to transmit various information (e.g., application startup information) to other devices. Details of the processing by the login processing unit 320, the generation unit 330, the account management unit 340, the reception unit 350, and the transmission unit 360 will be described later.

[0039] FIG. 8 is a diagram showing an example of the contents of employee information 372. The employee information 372 associates information such as an employee ID, password, salary transfer method, virtual account information, bank account information, salary history, and account ID. As described above, the employee ID is identification information for identifying the employee. The password is authentication information used to authenticate the employee when the labor management server 300 performs login processing. The salary transfer method is the method by which the employee's salary is transferred, and is set as electronic money or a bank account. The virtual account information is the same as the virtual account information shown in FIG. 5 and is information related to the bank account (bank name, branch number, account number, etc.) associated with each employee and owned by the company that operates the electronic payment service. The bank account information is information related to the employee's bank account (bank name, branch number, account number, etc.). The salary history is information indicating the history of salary paid to the employee. The account ID is the same as the account ID shown in FIG. 5 and is information for identifying the employee's account in the electronic payment service.

[0040] [Process to set salary transfer method to electronic money] 9 is a sequence diagram showing an example of a process for setting the salary transfer method to electronic money, which is executed by the employee terminal device 600, the labor management server 300, the payment server 100, and the user terminal device 200. First, the employee terminal device 600 transmits login information to the labor management server 300 (step S21). Specifically, the employee terminal device 600 displays a login screen for logging in to the labor management system provided by the labor management server 300, and transmits the login information, including the employee ID and password entered by the employee on the login screen, to the labor management server 300.

[0041] Next, the login processing unit 320 of the labor management server 300 performs login processing based on the login information received from the employee terminal device 600 (step S22). Specifically, the login processing unit 320 determines whether the employee ID and password included in the login information match the employee ID and password included in the employee information 372. If the login processing unit 320 determines that this information does not match, it sends a notification to the employee terminal device 600 indicating that the login is not permitted.

[0042] On the other hand, if the login processing unit 320 determines that the information matches, it sends a notification to the employee terminal device 600 indicating that the login is permitted (step S23). This allows the employee to log in, and the home screen of the labor management system is displayed on the display unit of the employee terminal device 600.

[0043] Next, the employee terminal device 600 sends an account setting application to the labor management server 300 to set up a salary deposit account for the employee whose login has been accepted (step S24). The account setting application is an application to set up a salary deposit account for the employee whose login has been accepted. This point will be explained in detail using a screen of the labor management system.

[0044] 10 is a diagram showing an example of a salary deposit account setting window W1 in the labor management system. As shown in Fig. 10, the salary deposit account setting window W1 includes buttons B1 to B4.

[0045] Button B1 is a radio button for specifying a bank account as the employee's salary deposit account. Button B2 is a radio button for specifying electronic money as the employee's salary deposit account. Button B3 is a cancel button for canceling the salary deposit account settings. When button B3 is clicked by an employee, the salary deposit account settings window W1 will be closed.

[0046] On the other hand, if an employee clicks button B4 while either button B1 or B2 is selected, the employee terminal device 600 sends an account setting request to the labor management server 300. The account setting request includes the employee ID and the salary transfer method. If button B1 is clicked, the salary transfer method will be bank account, and if button B2 is clicked, the salary transfer method will be electronic money.

[0047] Returning to the explanation of Figure 9, an example will be described in which electronic money is selected as the salary transfer method. When the receiving unit 350 of the labor management server 300 receives an account setting application from the employee terminal device 600 (step S24), the generating unit 330 generates a QR code (registered trademark) in response to the account setting application (step S25).

[0048] The QR code is an example of application activation information for activating the payment application 20. The QR code is code information that encodes an employee ID, a server ID, and a link (such as a deep link) for activating the payment application 20 to use an electronic payment service. The server ID is identification information for identifying the labor management server 300 and is stored in the storage unit 370.

[0049] The generation unit 330 creates a QR code by a method determined in advance between the payment server 100 and the labor management server 300, but the method of generating the QR code is not limited to this. For example, the generation unit 330 may send a QR code generation request to the payment server 100 and receive the generated QR code from the payment server 100. In this case, the process of receiving the QR code from the payment server 100 is considered to be the process of generating a QR code.

[0050] The transmission unit 360 transmits the QR code to the employee terminal device 600 (step S26). Upon receiving the QR code from the labor management server 300, the employee terminal device 600 displays the QR code on the display unit (step S27). This point will be specifically explained using a screen of the labor management system.

[0051] 11 is a diagram showing an example of a QR code display window W2 in a labor management system. As shown in FIG. 11, the QR code display window W2 includes a message M and a QR code C. The message M includes an explanation about receiving wages in electronic money. After checking the contents of the message M, the employee uses the user terminal device 200 to photograph the QR code C.

[0052] Returning to the explanation of Figure 9, user terminal device 200 photographs QR code C (step S28) and decodes QR code C (step S29). This allows user terminal device 200 to obtain the employee ID, the server ID, and a link to launch payment application 20 for using the electronic payment service.

[0053] Next, the user terminal device 200 launches the payment application 20 based on the link (deep link, etc.) obtained by decoding the QR code C (step S30). At this time, the payment application 20 displays a salary receipt setting screen on the display unit of the user terminal device 200.

[0054] Figure 12 is a diagram showing an example of the salary receipt setting screen. As shown in Figure 12, the salary receipt setting screen displays a message about receiving salary in electronic money. The salary receipt setting screen also includes buttons B5 and B6.

[0055] Button B5 is a button for canceling the salary receipt settings. When an employee selects (tap) button B5, the salary receipt settings screen is closed. Button B6 is a button for proceeding with the salary receipt settings procedure. When an employee selects (tap) button B6, the user terminal device 200 (payment application 20) sends an account linking request to the payment server 100 (step S31). The account linking request includes the employee ID, the server ID, and an account ID for identifying the employee's account in the electronic payment service.

[0056] The receiving unit 150 of the payment server 100 receives the account linking request from the user terminal device 200. The acquiring unit 160 acquires the employee's virtual account information in the electronic payment service based on the account ID included in the account linking request (step S32). Specifically, the acquiring unit 160 references the user information 182 to acquire the virtual account information linked to the account ID included in the account linking request. If there is no virtual account information linked to the account ID, the acquiring unit 160 links new virtual account information to the account ID.

[0057] Next, the information management unit 140 performs account linking processing (step S33). Specifically, the information management unit 140 associates the account ID, employee ID, server ID, and virtual account information and writes them into the user information 182. This allows the payment server 100 to associate users who use the electronic payment service with employees who use the labor management system of the labor management server 300.

[0058] Next, the transmission unit 170 transmits the account linking result to the labor management server 300 (step S34). Specifically, the account linking result includes the employee ID and account ID included in the account linking request, and the virtual account information acquired in step S32. The transmission unit 170 also transmits the account linking result to the labor management server 300 corresponding to the server ID included in the account linking request. This allows the account linking result to be sent to the appropriate destination even if there are multiple labor management servers 300.

[0059] The receiving unit 350 of the labor management server 300 receives the account linking result from the payment server 100. The account management unit 340 updates the employee information 372 based on the account linking result (step S35). Specifically, the account management unit 340 writes the employee information 372, which associates the employee ID, virtual account information, and account ID included in the account linking result, to the storage unit 370.

[0060] Next, the transmission unit 360 transmits a confirmation screen for confirming the account linking result to the employee terminal device 600 (step S36). The employee terminal device 600 displays the confirmation screen received from the labor management server 300 on the display unit (step S37). The confirmation screen (not shown) may include a message indicating that linking with the electronic payment service has been completed, the account ID of the electronic payment service, and a button for instructing the employee to register electronic money as a salary transfer method.

[0061] When the employee clicks a button on the confirmation screen to indicate that electronic money is to be registered as the salary transfer method, the employee terminal device 600 sends a virtual account registration request to the labor management server 300 (step S38). This confirms the content written in the employee information 372.

[0062] The confirmation screen may include a cancel button for canceling the electronic money registration. If the employee clicks the cancel button, the employee terminal device 600 may send a cancellation request to the labor management server 300 and the payment server 100. In this case, the labor management server 300 may return the contents of the employee information 372 to the state before the update in step S35, and the payment server 100 may return the contents of the user information 182 to the state before the account linking process in step S33. This allows the account linking to be canceled even if the employee mistakenly submits an account setting request.

[0063] As described above, the labor management server 300 of this embodiment can communicate with the employee terminal device 600 operated by a company employee and the payment server 100 that provides electronic payment services. The labor management server 300 includes a generation unit 330, a transmission unit 360, a reception unit 350, and an account management unit 340. The generation unit 330 generates a QR code that includes an employee ID for identifying the employee, a server ID for identifying the labor management server 300, and a link for launching an app for using the electronic payment service. The transmission unit 360 transmits the QR code to the employee terminal device 600. The reception unit 350 receives from the payment server 100 a result of account linking between the labor management server 300 and the payment server 100. The account management unit 340 manages the employee's virtual account information for the electronic payment service, included in the account linking result, as a transfer account for the employee's salary. This allows account information such as virtual account information to be easily registered, improving user convenience.

[0064] In the above description, the employee logs in to the labor management system using the employee terminal device 600, but this is not limited to this. For example, the employee may log in to the labor management system using the user terminal device 200. The processing in this case will be described in detail below.

[0065] 13 is a sequence diagram showing an example of a process for setting the salary transfer method to electronic money, which is executed by the labor management server 300, the payment server 100, and the user terminal device 200. First, the user terminal device 200 transmits login information to the labor management server 300 (step S41). Specifically, the user terminal device 200 displays a login screen for logging in to the labor management system provided by the labor management server 300, and transmits the login information, including the employee ID and password entered by the employee on the login screen, to the labor management server 300.

[0066] Next, the login processing unit 320 of the labor management server 300 performs login processing based on the login information received from the user terminal device 200 (step S42). Specifically, the login processing unit 320 determines whether the employee ID and password included in the login information match the employee ID and password included in the employee information 372. If the login processing unit 320 determines that this information does not match, it sends a notification to the user terminal device 200 indicating that the login is not permitted.

[0067] On the other hand, if the login processing unit 320 determines that the information matches, it sends a notification to the user terminal device 200 indicating that the login is permitted (step S43). This allows the employee to log in, and the home screen of the labor management system is displayed on the display unit of the user terminal device 200.

[0068] Next, the user terminal device 200 sends an account setting application to the labor management server 300 to set up a salary deposit account for the employee whose login has been accepted (step S44). As described above, when the salary deposit account setting window W1 shown in FIG. 10 is displayed on the display unit of the user terminal device 200 and the employee clicks button B4 with either button B1 or B2 selected, the user terminal device 200 sends the account setting application to the labor management server 300. The account setting application includes the employee ID and the salary transfer method. If button B1 is clicked, the salary transfer method is bank account, and if button B2 is clicked, the salary transfer method is electronic money.

[0069] An example in which electronic money is selected as the salary transfer method will be described below. When the receiving unit 350 of the labor management server 300 receives the account setting application from the user terminal device 200, the generating unit 330 generates an account setting screen (step S45).

[0070] The account setting screen is an example of application startup information for starting the payment application 20. Specifically, the account setting screen is a screen having a startup button for starting the payment application 20. The startup button is associated with an employee ID, a server ID, and a link (such as a deep link) for starting the payment application 20. The transmission unit 360 transmits the account setting screen to the user terminal device 200 (step S46).

[0071] When the user terminal device 200 receives the account setting screen from the labor management server 300, it displays the account setting screen on the display unit (step S47). When the employee selects (tap) the launch button displayed on the account setting screen, the user terminal device 200 acquires the employee ID, server ID, and link (deep link, etc.) associated with the launch button for launching the payment app 20. The user terminal device 200 also launches the payment app 20 based on the acquired link (deep link, etc.) (step S48). At this time, the payment app 20 displays the salary receipt setting screen shown in FIG. 12 on the display unit of the user terminal device 200.

[0072] 12, when the employee selects (tap) button B6, the user terminal device 200 (payment application 20) sends an account linking request to the payment server 100 (step S49). The account linking request includes the employee ID, the server ID, and an account ID for identifying the employee's account in the electronic payment service.

[0073] The receiving unit 150 of the payment server 100 receives an account linking request from the user terminal device 200. The acquiring unit 160 acquires the employee's virtual account information in the electronic payment service based on the account ID included in the account linking request (step S50). Specifically, the acquiring unit 160 references the user information 182 to acquire the virtual account information linked to the account ID included in the account linking request. If there is no virtual account information linked to the account ID, the acquiring unit 160 links new virtual account information to the account ID.

[0074] Next, the information management unit 140 performs account linking processing (step S51). Specifically, the information management unit 140 associates the account ID, employee ID, server ID, and virtual account information and writes them into the user information 182. This allows the payment server 100 to associate users who use the electronic payment service with employees who use the labor management system of the labor management server 300.

[0075] Next, the transmission unit 170 transmits the account linking result to the labor management server 300 (step S52). Specifically, the account linking result includes the employee ID and account ID included in the account linking request, and the virtual account information acquired in step S52. The transmission unit 170 also transmits the account linking result to the labor management server 300 corresponding to the server ID included in the account linking request. This allows the account linking result to be sent to the appropriate destination even if there are multiple labor management servers 300.

[0076] The receiving unit 350 of the labor management server 300 receives the account linking result from the payment server 100. The account management unit 340 updates the employee information 372 based on the account linking result (step S53). Specifically, the account management unit 340 writes the employee information 372, which associates the employee ID, virtual account information, and account ID included in the account linking result, into the storage unit 370.

[0077] Next, the transmission unit 360 transmits a confirmation screen for confirming the account linking result to the user terminal device 200 (step S54). The user terminal device 200 displays the confirmation screen received from the labor management server 300 on the display unit (step S55). The confirmation screen (not shown) may include a message indicating that linking with the electronic payment service has been completed, the account ID of the electronic payment service, and a button for instructing the user to register electronic money as a salary transfer method.

[0078] When the employee clicks a button on the confirmation screen to indicate that electronic money is to be registered as the salary transfer method, the user terminal device 200 sends a virtual account registration request to the labor management server 300 (step S56). This confirms the content written in the employee information 372.

[0079] The confirmation screen may include a cancel button for canceling the electronic money registration. If the employee clicks the cancel button, the user terminal device 200 may send a cancellation request to the labor management server 300 and the payment server 100. The labor management server 300 may return the contents of the employee information 372 to the state before the update in step S53, and the payment server 100 may return the contents of the user information 182 to the state before the account linking process in step S51. This allows the account linking to be canceled even if the employee mistakenly sends an account setting request.

[0080] [Payment processing to virtual account] When transferring an employee's salary as electronic money, the salary is transferred by specifying a virtual account linked to the employee. A virtual account is a bank account linked to each employee and owned by a company that operates an electronic payment service. Specifically, a salary management system (not shown) of the company to which the employee belongs sends the employee ID to the labor management server 300 and receives virtual account information linked to the employee ID from the labor management server 300. The salary management system also sends a salary transfer request to the bank server 400 to transfer the employee's salary to the bank account indicated by the virtual account information. The bank server 400 performs the transfer process of the employee's salary based on the salary transfer request received from the salary management system.

[0081] Next, the payment server 100 receives a transfer completion notice indicating that the salary has been transferred to the virtual account. The transfer completion notice includes the virtual account information and the amount of the transferred salary. The payment processing unit 130 of the payment server 100 reads out the account ID linked to the virtual account information included in the transfer completion notice from the user information 182, and charges electronic money in an amount equivalent to the employee's salary to the read account ID.

[0082] In this way, companies can charge employees' accounts with electronic money equivalent to their salaries by transferring their salaries to virtual accounts (bank accounts) linked to employees without even being aware of the electronic payment service.

[0083] As described above, the labor management server 300 of this embodiment can communicate with the user terminal device 200 operated by a company employee and the payment server 100 that provides electronic payment services. The labor management server 300 includes a generation unit 330, a transmission unit 360, a reception unit 350, and an account management unit 340. The generation unit 330 generates a QR code that includes an employee ID for identifying the employee, a server ID for identifying the labor management server 300, and a link for launching an app for using the electronic payment service. The transmission unit 360 transmits the QR code to the user terminal device 200. The reception unit 350 receives from the payment server 100 a result of account linking between the labor management server 300 and the payment server 100. The account management unit 340 manages the employee's virtual account information for the electronic payment service, included in the account linking result, as a transfer account for the employee's salary. This allows account information such as virtual account information to be easily registered, improving convenience for users.

[0084] In this embodiment, the salary is transferred to a virtual account linked to the employee, but this is not limited to this. For example, a company may have a corporate account for an electronic payment service, and electronic money equivalent to the salary may be transferred from the company's corporate account to an account ID linked to the employee. In this case, electronic money equivalent to the salary can be charged to the employee's account without sharing virtual account information between the payment server 100 and the labor management server 300.

[0085] In the above explanation, electronic money is selected as the salary transfer method. However, in this embodiment, it is also possible to select a bank account as the salary transfer method. This point will be explained in detail below.

[0086] [Bank Server] FIG. 14 is a configuration diagram of the bank server 400. The bank server 400 includes, for example, a communication unit 410, a transfer processing unit 420, an information management unit 430, a receiving unit 440, an acquiring unit 450, a transmitting unit 460, and a storage unit 470. The components other than the communication unit 410 and the storage unit 470 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be implemented by a combination of software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as an HDD or flash memory, or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive.

[0087] The storage unit 470 is a HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 470 may be a NAS device that can be accessed by the bank server 400 via a network. The storage unit 470 stores bank account information 472.

[0088] The communication unit 410 is a communication interface for connecting to the network NW, and is, for example, a network interface card.

[0089] The transfer processing unit 420 performs transfer processing to transfer salaries to employee bank accounts. The information management unit 430 manages bank account information 472. The receiving unit 440 receives various information (e.g., account linking applications) from other devices by controlling the communication unit 410. The acquiring unit 450 acquires employee bank account information. The transmitting unit 460 transmits various information (e.g., account linking results) to other devices by controlling the communication unit 410. Details of the processing by the transfer processing unit 420, information management unit 430, receiving unit 440, acquiring unit 450, and transmitting unit 460 will be described later.

[0090] FIG. 15 is a diagram showing an example of the contents of bank account information 472. The bank account information 472 associates information such as an account ID, bank account information, name, address, date of birth, deposit balance, transaction history, employee ID, and server ID. The account ID is identification information for identifying an employee's account in bank services. The bank account information is information about the bank account, such as the branch number, account number, and deposit type. The name, address, and date of birth are information about the name, address, and date of birth of the bank account holder. The deposit balance is information indicating the balance of money deposited in the bank account. The transaction history is information indicating the history of transactions (deposits, withdrawals, transfers, etc.) made to the bank account. The employee ID is information similar to the employee ID included in the user information 182 (FIG. 5) and is identification information for identifying the employee. The server ID is information similar to the server ID included in the user information 182 (FIG. 5) and is identification information for identifying the labor management server 300.

[0091] [Process to set salary transfer method to bank account] 16 is a sequence diagram showing an example of the process of setting the salary transfer method to a bank account, which is executed by the employee terminal device 600, the labor management server 300, the bank server 400, and the user terminal device 200. Note that the process of steps S61 to S63 is the same as the process of steps S21 to S23 in Fig. 9, and therefore a description thereof will be omitted. By performing the process of steps S61 to S63, the employee's login to the labor management system is accepted, and the home screen of the labor management system is displayed on the display unit of the employee terminal device 600.

[0092] Next, the employee terminal device 600 sends an account setting application to the labor management server 300 to set up a salary transfer account for the employee whose login has been accepted (step S64). Specifically, the above-mentioned setting window W1 (FIG. 10) is displayed on the display unit of the employee terminal device 600, and the employee selects a bank account as the salary transfer method. In this case, the employee terminal device 600 sends an account setting application to the labor management server 300 indicating that a bank account has been selected as the salary transfer method.

[0093] Next, when the receiving unit 350 of the labor management server 300 receives the account setting application from the employee terminal device 600, the generating unit 330 generates a QR code (registered trademark) in response to the account setting application (step S65).

[0094] The QR code is an example of application startup information for starting the bank application 30. The QR code is code information that encodes an employee ID, a server ID, and a link (such as a deep link) for starting the bank application 30 to use bank services. The server ID is identification information for identifying the labor management server 300 and is stored in the storage unit 370.

[0095] The generation unit 330 creates a QR code using a method determined in advance between the bank server 400 and the labor management server 300, but the method for generating the QR code is not limited to this. For example, the generation unit 330 may send a QR code generation request to the bank server 400 and receive the generated QR code from the bank server 400. In this case, the process of receiving the QR code from the bank server 400 is considered to be the process of generating a QR code.

[0096] The transmission unit 360 transmits the QR code to the employee terminal device 600 (step S66). Upon receiving the QR code from the labor management server 300, the employee terminal device 600 displays the QR code on the display unit (step S67).

[0097] Next, the user terminal device 200 photographs the QR code C (step S68) and decodes the QR code C (step S69). As a result, the user terminal device 200 can obtain the employee ID, the server ID, and a link to launch the bank application 30 to use the bank's services.

[0098] Next, the user terminal device 200 launches the banking application 30 based on the link (such as a deep link) obtained by decoding the QR code C (step S70). At this time, the banking application 30 displays a salary receipt setting screen on the display unit of the user terminal device 200.

[0099] When an employee instructs the bank to proceed with the salary receipt setup procedure from the salary receipt setup screen, the user terminal device 200 (bank application 30) sends an account linkage request to the bank server 400 (step S71). The account linkage request includes an employee ID, a server ID, and an account ID for identifying the employee's account in the bank's services.

[0100] The receiving unit 440 of the bank server 400 receives the account linking request from the user terminal device 200. The acquiring unit 450 acquires the bank account information of the employee for the bank service based on the account ID included in the account linking request (step S72). Specifically, the acquiring unit 450 refers to the bank account information 472 to acquire the bank account information linked to the account ID included in the account linking request.

[0101] Next, the information management unit 430 performs account linking processing (step S73). Specifically, the information management unit 430 associates the account ID, employee ID, server ID, and bank account information and writes them into the bank account information 472. This allows the bank server 400 to associate users who use bank services with employees who use the labor management system of the labor management server 300.

[0102] Next, the transmission unit 460 transmits the account linking result to the labor management server 300 (step S74). Specifically, the account linking result includes the employee ID and account ID included in the account linking request, and the bank account information acquired in step S72. The transmission unit 460 also transmits the account linking result to the labor management server 300 corresponding to the server ID included in the account linking request. This allows the account linking result to be sent to the appropriate destination even if there are multiple labor management servers 300.

[0103] The receiving unit 350 of the labor management server 300 receives the account linking result from the bank server 400. The account management unit 340 updates the employee information 372 based on the account linking result (step S75). Specifically, the account management unit 340 writes the employee information 372, which associates the employee ID, bank account information, and account ID included in the account linking result, into the storage unit 370.

[0104] Next, the transmission unit 360 transmits a confirmation screen for confirming the account linking result to the employee terminal device 600 (step S76). The employee terminal device 600 displays the confirmation screen received from the labor management server 300 on the display unit (step S77). The confirmation screen (not shown) may include a message indicating that linking with the bank's service has been completed, bank account information (account number, etc.), and a button for instructing the employee to register the bank account as a salary transfer method.

[0105] When the employee clicks a button on the confirmation screen to indicate that they want to register a bank account as the salary transfer method, the employee terminal device 600 sends a bank account registration request to the labor management server 300 (step S78). This confirms the content written in the employee information 372.

[0106] The confirmation screen may include a cancel button for canceling the bank account registration. If the employee clicks the cancel button, the employee terminal device 600 may send a cancellation request to the labor management server 300 and the bank server 400. In this case, the labor management server 300 may restore the contents of the employee information 372 to the state before the update in step S75, and the bank server 400 may restore the contents of the bank account information 472 to the state before the account linking process in step S73. This allows the account linking to be canceled even if the employee mistakenly submits an account setting request.

[0107] As described above, the labor management server 300 of this embodiment can communicate with the employee terminal device 600 operated by a company employee and the bank server 400 that provides banking services. The labor management server 300 includes a generation unit 330, a transmission unit 360, a reception unit 350, and an account management unit 340. The generation unit 330 generates a QR code that includes an employee ID for identifying the employee, a server ID for identifying the labor management server 300, and a link for launching the bank app 30 to use the banking services. The transmission unit 360 transmits the QR code to the employee terminal device 600. The reception unit 350 receives from the bank server 400 a result of account linking between the labor management server 300 and the bank server 400. The account management unit 340 manages the employee's bank account information for the banking services, included in the account linking result, as a transfer account for the employee's salary. This allows account information, such as bank account information, to be easily registered, improving user convenience.

[0108] In the above description, the employee logs in to the labor management system using the employee terminal device 600, but this is not limited to this. For example, the employee may log in to the labor management system using the user terminal device 200. The processing in this case will be described in detail below.

[0109] Figure 17 is a sequence diagram showing an example of the process of setting the salary transfer method to a bank account, which is executed by the labor management server 300, the bank server 400, and the user terminal device 200. Note that the process of steps S81 to S83 is the same as the process of steps S41 to S43 in Figure 13, and therefore a description thereof will be omitted. By performing the process of steps S81 to S83, the employee's login to the labor management system is accepted, and the home screen of the labor management system is displayed on the display unit of the user terminal device 200.

[0110] Next, the user terminal device 200 sends an account setting application to the labor management server 300 to set up a salary transfer account for the employee whose login has been accepted (step S84). Specifically, the aforementioned setting window W1 (FIG. 10) is displayed on the display unit of the user terminal device 200, and the employee selects a bank account as the salary transfer method. In this case, the user terminal device 200 sends an account setting application to the labor management server 300 indicating that a bank account has been selected as the salary transfer method.

[0111] Next, when the receiving unit 350 of the labor management server 300 receives the account setting application from the user terminal device 200, the generating unit 330 generates an account setting screen (step S85).

[0112] The account setting screen is an example of application startup information for starting the banking application 30. Specifically, the account setting screen is a screen having a startup button for starting the banking application 30. The startup button is associated with an employee ID, a server ID, and a link (such as a deep link) for starting the banking application 30. The transmission unit 360 transmits the account setting screen to the user terminal device 200 (step S86).

[0113] When the user terminal device 200 receives the account setting screen from the labor management server 300, it displays the account setting screen on the display unit (step S87). When the employee selects (tap) the launch button displayed on the account setting screen, the user terminal device 200 acquires the employee ID, server ID, and link (deep link, etc.) associated with the launch button for launching the banking app 30. The user terminal device 200 also launches the banking app 30 based on the acquired link (deep link, etc.) (step S88). At this time, the banking app 30 displays a salary receipt setting screen on the display unit of the user terminal device 200.

[0114] When the employee instructs on the salary receipt setting screen to proceed with the salary receipt setting procedure, the user terminal device 200 (bank application 30) sends an account linking request to the bank server 400 (step S89). The account linking request includes the employee ID, the server ID, and an account ID for identifying the employee's account in the bank's services.

[0115] The receiving unit 440 of the bank server 400 receives the account linking request from the user terminal device 200. The acquiring unit 450 acquires the bank account information of the employee for the bank service based on the account ID included in the account linking request (step S90). Specifically, the acquiring unit 450 refers to the bank account information 472 to acquire the bank account information linked to the account ID included in the account linking request.

[0116] Next, the information management unit 430 performs account linking processing (step S91). Specifically, the information management unit 430 associates the account ID, employee ID, server ID, and bank account information and writes them into the bank account information 472. This allows the bank server 400 to associate users who use bank services with employees who use the labor management system of the labor management server 300.

[0117] Next, the transmission unit 460 transmits the account linking result to the labor management server 300 (step S92). Specifically, the account linking result includes the employee ID and account ID included in the account linking request, and the bank account information acquired in step S90. The transmission unit 460 also transmits the account linking result to the labor management server 300 corresponding to the server ID included in the account linking request. This allows the account linking result to be sent to the appropriate destination even if there are multiple labor management servers 300.

[0118] The receiving unit 350 of the labor management server 300 receives the account linking result from the bank server 400. The account management unit 340 updates the employee information 372 based on the account linking result (step S93). Specifically, the account management unit 340 writes the employee information 372, which associates the employee ID, bank account information, and account ID included in the account linking result, into the storage unit 370.

[0119] Next, the transmission unit 360 transmits a confirmation screen for confirming the account linking result to the user terminal device 200 (step S94). The user terminal device 200 displays the confirmation screen received from the labor management server 300 on the display unit (step S95). The confirmation screen (not shown) may include a message indicating that linking with the bank's service has been completed, bank account information (account number, etc.), and a button for instructing the user to register the bank account as a salary transfer method.

[0120] When an employee clicks a button on the confirmation screen to indicate that they want to register a bank account as the salary transfer method, the user terminal device 200 sends a bank account registration request to the labor management server 300 (step S96). This confirms the content written in the employee information 372.

[0121] The confirmation screen may include a cancel button for canceling the bank account registration. If the employee clicks the cancel button, the user terminal device 200 may send a cancellation request to the labor management server 300 and the bank server 400. In this case, the labor management server 300 may restore the contents of the employee information 372 to the state before the update in step S93, and the bank server 400 may restore the contents of the bank account information 472 to the state before the account linking process in step S91. This allows the account linking to be canceled even if the employee mistakenly submits an account setting request.

[0122] [Payment processing to bank account] When transferring an employee's salary to a bank account, the employee's bank account is designated and the payment is made. Specifically, the salary management system (not shown) of the employee's company sends the employee ID to the labor management server 300 and receives bank account information linked to the employee ID from the labor management server 300. The salary management system also sends a salary transfer request to the bank server 400 to transfer the employee's salary to the bank account indicated by the bank account information. The bank server 400 performs the transfer process for the employee's salary based on the salary transfer request received from the salary management system. This makes it possible to transfer the employee's salary to the bank account.

[0123] As described above, the labor management server 300 of this embodiment can communicate with the user terminal device 200 operated by a company employee and the bank server 400 that provides banking services. The labor management server 300 includes a generation unit 330, a transmission unit 360, a reception unit 350, and an account management unit 340. The generation unit 330 generates an account setting screen that includes an employee ID for identifying the employee, a server ID for identifying the labor management server 300, and a link for launching the bank app 30 to use the banking services. The transmission unit 360 transmits the account setting screen to the employee terminal device 600. The reception unit 350 receives an account linking result between the labor management server 300 and the bank server 400 from the bank server 400. The account management unit 340 manages the employee's bank account information for the banking services, included in the account linking result, as a transfer account for the employee's salary. This allows account information such as bank account information to be easily registered, improving user convenience.

[0124] Second Embodiment In the first embodiment, the employee's salary deposit account is registered in the labor management server 300. In contrast, in the second embodiment, the credit card withdrawal account is registered in the credit card management server 500. This point will be explained in detail below.

[0125] In conventional systems, it was not possible to link accounts between the credit card management server 500 and the bank server 400. Therefore, in order to register account information (e.g., fund transfer account information) managed by the bank server 400 in the credit card management server 500, the user himself / herself had to register the account information in the credit card management server 500, which could be inconvenient for the user. The second embodiment has been made in consideration of such circumstances, and one of its objects is to provide a credit card management server, a credit card management method, and a program that can easily register account information and improve convenience for users.

[0126] [Credit card management server] FIG. 18 is a configuration diagram of a credit card management server 500. The credit card management server 500 includes, for example, a communication unit 510, a login processing unit 520, a generation unit 530, an account management unit 540, a receiving unit 550, a transmission unit 560, and a storage unit 570. The components other than the communication unit 510 and the storage unit 570 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be implemented by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device with a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0127] The storage unit 570 is a HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 570 may be a NAS device that can be accessed by the credit card management server 500 via a network. The storage unit 570 stores card information 572.

[0128] The communication unit 510 is a communication interface for connecting to the network NW, and is, for example, a network interface card.

[0129] The login processing unit 520 accepts login from a user. The generation unit 530 generates application startup information for starting the bank application 30. The account management unit 540 manages a credit card withdrawal account. The reception unit 550 receives various information (e.g., account linking results) from other devices by controlling the communication unit 510. The transmission unit 560 transmits various information (e.g., application startup information) to other devices by controlling the communication unit 510. Details of the processing by the login processing unit 520, the generation unit 530, the account management unit 540, the reception unit 550, and the transmission unit 560 will be described later.

[0130] FIG. 19 is a diagram showing an example of the contents of card information 572. Card information 572 associates information such as a user ID, password, credit card information, bank account information, card billing history, and account ID. The user ID is identification information for identifying the credit card user. The password is authentication information used to authenticate the user when the credit card management server 500 performs login processing. The credit card information is information related to the user's credit card (card number, expiration date, name, etc.). The bank account information is information related to the user's bank account (bank name, branch number, account number, etc.). The card billing history is information indicating the monthly credit card billing history. The account ID is identification information for identifying an employee's account for bank services.

[0131] [Process to set up a credit card withdrawal account] FIG. 20 is a sequence diagram showing an example of the process for setting up a credit card withdrawal account, which is executed by the employee terminal device 600, the credit card management server 500, the bank server 400, and the user terminal device 200. In this embodiment, the employee terminal device 600 is used as an example, but a terminal device (desktop PC, laptop PC, etc.) owned by the user may also be used. First, the employee terminal device 600 sends login information to the credit card management server 500 (step S101). Specifically, the employee terminal device 600 displays a login screen for logging in to the credit card management system provided by the credit card management server 500, and sends the login information, including the user ID and password entered by the user on the login screen, to the credit card management server 500.

[0132] Next, the login processing unit 520 of the credit card management server 500 performs login processing based on the login information received from the employee terminal device 600 (step S102). Specifically, the login processing unit 520 determines whether the user ID and password included in the login information match the user ID and password included in the card information 572. If the login processing unit 520 determines that this information does not match, it sends a notification to the employee terminal device 600 indicating that the login is not permitted.

[0133] On the other hand, if the login processing unit 520 determines that the information matches, it sends a notification to the employee terminal device 600 indicating that the login is permitted (step S103). This allows the login from the user to be accepted, and the home screen of the credit card management system is displayed on the display unit of the employee terminal device 600.

[0134] Next, the employee terminal device 600 transmits an account setting application to the credit card management server 500 to set up a debit account for the credit card of the user whose login has been accepted (step S104).

[0135] Next, when the receiving unit 550 of the credit card management server 500 receives the account setting application from the employee terminal device 600, the generating unit 530 generates a QR code (registered trademark) in response to the account setting application (step S105).

[0136] The QR code is an example of application startup information for starting the banking application 30. The QR code is code information that encodes a user ID, a server ID, and a link (such as a deep link) for starting the banking application 30 to use bank services. The server ID is identification information for identifying the credit card management server 500, and is stored in the storage unit 570.

[0137] The generation unit 530 creates a QR code using a method determined in advance between the bank server 400 and the credit card management server 500, but the method for generating the QR code is not limited to this. For example, the generation unit 530 may send a QR code generation request to the bank server 400 and receive the generated QR code from the bank server 400. In this case, the process of receiving the QR code from the bank server 400 is considered to be the process of generating a QR code.

[0138] The transmitting unit 560 transmits the QR code to the employee terminal device 600 (step S106). Upon receiving the QR code from the credit card management server 500, the employee terminal device 600 displays the QR code on the display unit (step S107).

[0139] Next, the user terminal device 200 photographs the QR code C (step S108) and decodes the QR code C (step S109). As a result, the user terminal device 200 can obtain the user ID, the server ID, and a link to launch the bank application 30 to use the bank's services.

[0140] Next, the user terminal device 200 launches the banking application 30 based on the link (such as a deep link) obtained by decoding the QR code C (step S110). At this time, the banking application 30 displays a setting screen for a debit account for the credit card on the display unit of the user terminal device 200.

[0141] When the user instructs the bank account setup procedure to proceed from the credit card withdrawal account setup screen, the user terminal device 200 (bank application 30) sends an account linkage request to the bank server 400 (step S111). The account linkage request includes a user ID, a server ID, and an account ID for identifying the user's account in the bank's services.

[0142] The receiving unit 440 of the bank server 400 receives the account linking request from the user terminal device 200. The acquiring unit 450 acquires the bank account information of the user for the bank's services based on the account ID included in the account linking request (step S112). Specifically, the acquiring unit 450 refers to the bank account information 472 to acquire the bank account information linked to the account ID included in the account linking request.

[0143] Next, the information management unit 430 performs account linking processing (step S113). Specifically, the information management unit 430 associates the account ID, user ID, server ID, and bank account information and writes them into the bank account information 472. In the first embodiment, the employee ID was written into the bank account information 472, but in the second embodiment, the user ID is written instead of the employee ID. This allows the bank server 400 to associate users who use bank services with users who use the credit card management system of the credit card management server 500.

[0144] Next, the transmission unit 460 transmits the account linking result to the credit card management server 500 (step S114). Specifically, the account linking result includes the user ID and account ID included in the account linking application, and the bank account information acquired in step S112. The transmission unit 460 also transmits the account linking result to the credit card management server 500 corresponding to the server ID included in the account linking application. This allows the account linking result to be sent to the appropriate destination even if there are multiple credit card management servers 500.

[0145] The receiving unit 550 of the credit card management server 500 receives the account linking result from the bank server 400. The account management unit 540 updates the card information 572 based on the account linking result (step S115). Specifically, the account management unit 540 writes the card information 572, in which the user ID, bank account information, and account ID included in the account linking result are associated, into the storage unit 570.

[0146] Next, the transmission unit 560 transmits a confirmation screen for confirming the account linking result to the employee terminal device 600 (step S116). The employee terminal device 600 displays the confirmation screen received from the credit card management server 500 on the display unit (step S117). The confirmation screen (not shown) may include a message indicating that linking with the bank's service has been completed, bank account information (account number, etc.), and a button for instructing the user to register the bank account as a debit account for the credit card.

[0147] When the user clicks a button on the confirmation screen to indicate that they want to register a bank account as a debit account for the credit card, the employee terminal device 600 sends a bank account registration request to the credit card management server 500 (step S118). This confirms the information written in the card information 572.

[0148] The confirmation screen may include a cancel button for canceling the bank account registration. If the user clicks the cancel button, the employee terminal device 600 may send a cancellation request to the credit card management server 500 and the bank server 400. In this case, the credit card management server 500 may restore the contents of the card information 572 to the state before the update in step S115, and the bank server 400 may restore the contents of the bank account information 472 to the state before the account linking process in step S113. This allows the account linking to be canceled even if the user mistakenly submits an account setting request.

[0149] As described above, the credit card management server 500 of this embodiment can communicate with the employee terminal device 600 operated by the credit card user and the bank server 400 that provides bank services. The credit card management server 500 includes a generation unit 530, a transmission unit 560, a reception unit 550, and an account management unit 540. The generation unit 530 generates a QR code that includes a user ID for identifying the user, a server ID for identifying the credit card management server 500, and a link for launching the bank app 30 to use the bank services. The transmission unit 560 transmits the QR code to the employee terminal device 600. The reception unit 550 receives from the bank server 400 a result of account linking between the credit card management server 500 and the bank server 400. The account management unit 540 manages the employee's bank account information for bank services, included in the account linking result, as a debit account for debiting the amount charged for the user's credit card usage. This allows account information such as bank account information to be easily registered, improving convenience for users.

[0150] In the above description, the user logs in to the credit card management system using the employee terminal device 600, but this is not limited to this. For example, the user may log in to the credit card management system using the user terminal device 200. The processing in this case will be described in detail below.

[0151] 21 is a sequence diagram showing an example of the process of setting up a credit card withdrawal account, which is executed by the credit card management server 500, the bank server 400, and the user terminal device 200. First, the user terminal device 200 transmits login information to the credit card management server 500 (step S121). Specifically, the user terminal device 200 displays a login screen for logging in to the credit card management system provided by the credit card management server 500, and transmits the login information, including the user ID and password entered by the user on the login screen, to the credit card management server 500.

[0152] Next, the login processing unit 520 of the credit card management server 500 performs login processing based on the login information received from the user terminal device 200 (step S122). Specifically, the login processing unit 520 determines whether the user ID and password included in the login information match the user ID and password included in the card information 572. If the login processing unit 520 determines that this information does not match, it sends a notification to the user terminal device 200 indicating that the login is not permitted.

[0153] On the other hand, if the login processing unit 520 determines that the information matches, it sends a notification to the user terminal device 200 indicating that the login is permitted (step S123). This allows the login from the user to be accepted, and the home screen of the credit card management system is displayed on the display unit of the user terminal device 200.

[0154] Next, the employee terminal device 600 transmits an account setting application to the credit card management server 500 to set up a debit account for the credit card of the user whose login has been accepted (step S124).

[0155] Next, when the receiving unit 550 of the credit card management server 500 receives the account setting application from the user terminal device 200, the generating unit 530 generates an account setting screen (step S125).

[0156] The account setting screen is an example of application startup information for starting the banking application 30. Specifically, the account setting screen is a screen having a startup button for starting the banking application 30. The startup button is associated with a user ID, a server ID, and a link (such as a deep link) for starting the banking application 30. The transmission unit 560 transmits the account setting screen to the user terminal device 200 (step S126).

[0157] When the user terminal device 200 receives the account setting screen from the credit card management server 500, it displays the account setting screen on the display unit (step S127). When the user selects (tap) the launch button displayed on the account setting screen, the user terminal device 200 acquires the user ID, server ID, and link (deep link, etc.) associated with the launch button for launching the banking application 30. The user terminal device 200 also launches the banking application 30 based on the acquired link (deep link, etc.) (step S128). At this time, the banking application 30 displays a setting screen for the credit card debit account on the display unit of the user terminal device 200.

[0158] When the user instructs the bank account setup procedure to proceed from the credit card withdrawal account setup screen, the user terminal device 200 (bank application 30) sends an account linkage request to the bank server 400 (step S129). The account linkage request includes the user ID, the server ID, and an account ID for identifying the user's account in the bank's services.

[0159] The receiving unit 440 of the bank server 400 receives the account linking request from the user terminal device 200. The acquiring unit 450 acquires the bank account information of the user for the bank's services based on the account ID included in the account linking request (step S130). Specifically, the acquiring unit 450 refers to the bank account information 472 to acquire the bank account information linked to the account ID included in the account linking request.

[0160] Next, the information management unit 430 performs account linking processing (step S131). Specifically, the information management unit 430 associates the account ID, user ID, server ID, and bank account information and writes them into the bank account information 472. In the first embodiment, the employee ID was written into the bank account information 472, but in the second embodiment, the user ID is written instead of the employee ID. This allows the bank server 400 to associate users who use bank services with users who use the credit card management system of the credit card management server 500.

[0161] Next, the transmission unit 460 transmits the account linking result to the credit card management server 500 (step S132). Specifically, the account linking result includes the user ID and account ID included in the account linking application, and the bank account information acquired in step S130. The transmission unit 460 also transmits the account linking result to the credit card management server 500 corresponding to the server ID included in the account linking application. This allows the account linking result to be sent to the appropriate destination even if there are multiple credit card management servers 500.

[0162] The receiving unit 550 of the credit card management server 500 receives the account linking result from the bank server 400. The account management unit 540 updates the card information 572 based on the account linking result (step S133). Specifically, the account management unit 540 writes the card information 572, in which the user ID, bank account information, and account ID included in the account linking result are associated, into the storage unit 570.

[0163] Next, the transmitting unit 560 transmits a confirmation screen for confirming the account linking result to the user terminal device 200 (step S134). The user terminal device 200 displays the confirmation screen received from the credit card management server 500 on the display unit (step S135). The confirmation screen (not shown) may include a message indicating that linking with the bank's service has been completed, bank account information (account number, etc.), and a button for instructing the user to register the bank account as a debit account for the credit card.

[0164] When the user clicks a button on the confirmation screen to indicate that they want to register a bank account as a withdrawal account for the credit card, the user terminal device 200 sends a bank account registration request to the credit card management server 500 (step S136). This confirms the contents written in the card information 572.

[0165] The confirmation screen may include a cancel button for canceling the bank account registration. If the user clicks the cancel button, the user terminal device 200 may send a cancellation request to the credit card management server 500 and the bank server 400. In this case, the credit card management server 500 may restore the contents of the card information 572 to the state before the update in step S133, and the bank server 400 may restore the contents of the bank account information 472 to the state before the account linking process in step S131. This allows the account linking to be canceled even if the user mistakenly sends an account setting request.

[0166] As described above, the credit card management server 500 of this embodiment can communicate with the user terminal device 200 operated by a credit card user and the bank server 400 that provides bank services. The credit card management server 500 includes a generation unit 530, a transmission unit 560, a reception unit 550, and an account management unit 540. The generation unit 530 generates a QR code that includes a user ID for identifying the user, a server ID for identifying the credit card management server 500, and a link for launching the bank app 30 for using the bank services. The transmission unit 560 transmits the QR code to the user terminal device 200. The reception unit 550 receives from the bank server 400 a result of account linking between the credit card management server 500 and the bank server 400. The account management unit 540 manages the bank account information of the employee for the bank services, included in the account linking result, as a debit account for debiting the amount charged for the user's credit card usage. This allows account information such as bank account information to be easily registered, improving convenience for users.

[0167] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0168] 20. Payment App 30. Banking App 50 First store terminal device 100 Payment Server 110 Communications Department 120 Payment Contents Department 130 Payment processing unit 140 Information Management Department 150 Receiver 160 Acquisition Department 170 Transmitter 180 Storage section 200 User terminal device 300 Labor Management Server 310 Communications Department 320 Login processing section 330 Generation part 340 Account Management Department 350 Receiver 360 Transmitter 370 Storage section 400 Bank Server 410 Communications Department 420 Transfer Processing Unit 430 Information Management Department 440 Receiver 450 Acquisition Department 460 Transmitter 470 Storage section 500 Credit card management server 510 Communications Department 520 Login processing section 530 Generation part 540 Account Management Department 550 Receiver 560 Transmitter 570 Storage section 600 Employee terminal equipment

Claims

1. A labor management server capable of communicating with a terminal device operated by an employee of a company and an information processing device that provides a service, a generation unit that generates application launch information including employee identification information for identifying the employee, server identification information for identifying the labor management server, and a link for launching an application for using the service; a transmitting unit that transmits the application launch information to the terminal device; a receiving unit that receives an account linking result between the labor management server and the information processing device from the information processing device; an account management unit that manages the employee's account information for the service included in the account linking result as a transfer account for the employee's salary; A labor management server comprising:

2. further comprising a login processing unit that accepts logins from the employees; the receiving unit receives from the terminal device an account setting application for setting up a transfer account for the salary of the employee whose login has been accepted; the generation unit generates the application launch information in response to the account setting application. The labor management server according to claim 1.

3. The account linking result further includes the employee identification information; The account management unit writes employee information, which is included in the account linking result and in which the employee identification information and the account information are associated, into a storage unit provided in the labor management server. The labor management server according to claim 1.

4. the application launch information is code information in which the employee identification information, the server identification information, and the link are coded; When the code information is decoded by the terminal device, the app is launched, and an account linking request including the employee identification information, the server identification information, and account identification information for identifying the employee's account in the service is sent by the app to the information processing device. The labor management server according to claim 1.

5. the application launch information is an account setting screen having a button for launching the application, When the user selects the button, the app is launched, and an account linking request including the employee identification information, the server identification information, and account identification information for identifying the employee's account in the service is sent by the app to the information processing device. The labor management server according to claim 1.

6. the information processing device is a payment server that performs electronic payment in an electronic payment service, the account information is information indicating the employee's virtual account in the electronic payment service; The sending unit sends a salary transfer request including the employee's virtual account and the amount of the employee's salary to the information processing device. The labor management server according to claim 1.

7. the information processing device is a bank server that manages information about bank accounts, The account information is information indicating the employee's bank account, The sending unit sends a salary transfer request including the employee's bank account and the amount of the employee's salary to the information processing device. The labor management server according to claim 1.

8. A credit card management server capable of communicating with a terminal device operated by a credit card user and an information processing device that provides a service, a generation unit that generates application launch information including user identification information for identifying the user, server identification information for identifying the credit card management server, and a link for launching an application for using the service; a transmitting unit that transmits the application launch information to the terminal device; a receiving unit that receives, from the information processing device, a result of account linking between the credit card management server and the information processing device; an account management unit that manages the account information of the user for the service included in the account linking result as a debit account from which a billing amount corresponding to the use of the credit card by the user is debited; A credit card management server comprising:

9. further comprising a login processing unit that accepts login from the user; the receiving unit receives from the terminal device an account setting application for setting up the withdrawal account of the user whose login has been accepted; the generation unit generates the application launch information in response to the account setting application.

9. The credit card management server according to claim 8.

10. The account linking result further includes the user identification information, the account management unit writes card information, which is included in the account linking result and which associates the user identification information with the account information, into a storage unit provided in the credit card management server; 9. The credit card management server according to claim 8.

11. the application launch information is code information in which the user identification information, the server identification information, and the link are coded; When the code information is decoded by the terminal device, the app is started, and an account linking request including the user identification information, the server identification information, and account identification information for identifying the user's account in the service is transmitted by the app to the information processing device.

9. The credit card management server according to claim 8.

12. the application launch information is an account setting screen having a button for launching the application, When the user selects the button, the app is launched, and an account linking request including the user identification information, the server identification information, and account identification information for identifying the user's account in the service is transmitted by the app to the information processing device.

9. The credit card management server according to claim 8.

13. the information processing device is a bank server that manages information about bank accounts, The account information is information indicating the bank account of the user, the transmitting unit transmits to the information processing device a card billing request including billing information indicating the bank account of the user and the billing amount of the user; 9. The credit card management server according to claim 8.

14. A labor management server that can communicate with a terminal device operated by an employee of a company and an information processing device that provides a service, generating application launch information including employee identification information for identifying the employee, server identification information for identifying the labor management server, and a link for launching an application for using the service; transmitting the application launch information to the terminal device; receiving, from the information processing device, a result of account linkage between the labor management server and the information processing device; Manage the employee's account information for the service included in the account linking result as a transfer account for the employee's salary. Labor management methods.

15. A terminal device operated by a credit card user and a credit card management server capable of communicating with an information processing device that provides a service, generating application launch information including user identification information for identifying the user, server identification information for identifying the credit card management server, and a link for launching an application for using the service; transmitting the application launch information to the terminal device; receiving, from the information processing device, a result of account linking between the credit card management server and the information processing device; managing the account information of the user for the service included in the account linking result as a debit account for withdrawing the amount charged in accordance with the use of the credit card by the user; How to manage credit cards.

16. A labor management server that can communicate with a terminal device operated by a company employee and an information processing device that provides services. A process of generating application launch information including employee identification information for identifying the employee, server identification information for identifying the labor management server, and a link for launching an application for using the service; a process of transmitting the application launch information to the terminal device; A process of receiving an account linking result between the labor management server and the information processing device from the information processing device; a process of managing the employee's account information in the service included in the account linking result as a salary transfer account for the employee; A program that executes the following.

17. A credit card management server capable of communicating with a terminal device operated by a credit card user and an information processing device that provides a service, a process of generating application launch information including user identification information for identifying the user, server identification information for identifying the credit card management server, and a link for launching an application for using the service; a process of transmitting the application launch information to the terminal device; a process of receiving, from the information processing device, a result of account linking between the credit card management server and the information processing device; a process of managing the account information of the user for the service included in the account linking result as a debit account for debiting the amount charged according to the use of the credit card by the user; A program that executes the following.

Images