Information processing device and program

Abstract

To make a refund to a user without requiring the user to perform an operation for refund even when an information processing apparatus is stopped before completion of the refund when the information processing apparatus executes processing after completion of settlement for execution of processing between the user and a settlement center and then the refund is required to be made.SOLUTION: An image forming apparatus 10 has a job execution control unit 12 that starts execution of a job after completion of settlement in association with the execution of the job, and a settlement processing unit 13 that requests a settlement center 3 to perform settlement with a user, and when a settlement amount exceeds an execution amount generated from the execution of the job, executes refund processing of requesting the settlement center 3 to make a refund to the user. In a case where the refund to the user is required, when the image forming apparatus 10 is stopped before the completion of the refund to the user is confirmed, the settlement processing unit 13 checks a state of completion of the refund to the user in reboot of the image forming apparatus 10, and when confirming that the refund to the user is not completed, executes the refund processing.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an information processing device and a program. [Background technology]

[0002] In recent years, when using an image forming apparatus, a user can make payments online or by electronic money. The image forming apparatus starts executing a job requested by the user after confirming the completion of the payment. In addition, a technique has been proposed for calculating a refund amount and making a refund when the amount of the payment made in advance exceeds the amount incurred by the execution of the job (for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2010-170442 A [Patent Document 2] JP 2018-046492 A [Patent Document 3] JP 2018-046494 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the past, there was no recovery process in place for when the device stopped before the refund was completed, so in order to complete the refund, the user had to perform some kind of operation after the device recovered from the shutdown.

[0005] To provide a method for making it possible to make a refund without making a user carry out any operation for refund when an information processing device executes a process and a refund becomes necessary after the completion of settlement for the execution of the process between a user and a settlement center, even if the information processing device stops before the refund is completed. [Means for solving the problem]

[0006] The information processing device according to the present invention includes a processor, which executes a process after confirming completion of a settlement related to the execution of the process between a user and a settlement center, and, if a settlement amount collected in the settlement before the information processing device starts the process exceeds a fee incurred by the execution of the process, executes a refund process to request the settlement center to refund the user, and, in response to the refund process, from A notice that the refund to the user has been completed but notification When the refund is received, the fact that the refund has been completed is stored internally and The information processing device has stopped Later On reboot If it is confirmed that the notification of the completion of the refund, which is notified from the settlement center in response to the refund process, is not stored internally, The refund process again The payment center performs the refund process at the time of restart. from The completion of the refund to the user is confirmed by receiving a notification of the completion of the refund to the user.

[0007] The processor is also characterized in that, when a refund to the user becomes necessary, it notifies the user that a refund is due.

[0008] After the information processing device is restarted, the processor The amount of the refund to the user cannot be determined because the amount calculated from the execution log of the process does not match the amount calculated from the settlement management log associated with the execution of the process. case, At reboot The refund process is not carried out and the administrator is notified of the indetermination.

[0010] The program according to the present invention includes a function for executing a process between a user and a settlement center after confirming completion of the process, a function for performing a refund process to request the settlement center to refund the user when a settlement amount collected in the settlement before the computer starts the process exceeds a price incurred by the execution of the process, and a function for requesting the settlement center to refund the user in response to the refund process. from A notice that the refund to the user has been completed but notification When a refund is received, the function to internally record that the refund has been completed. The above computer has stopped Later On reboot If it is confirmed that the notification of the completion of the refund, which is notified from the settlement center in response to the refund process, is not stored internally, The refund process againThe function to be performed is to execute the refund process at the time of restarting the payment center. from To realize a function of confirming the completion of refund to a user by receiving a notification of the completion of refund to the user. Effect of the Invention

[0011] According to the invention described in claim 1, if an information processing device executes a process and a refund becomes necessary after payment for the execution of the process between the user and the payment center is completed, the refund can be made without the user having to perform any operation for the refund even if the information processing device stops before the refund is completed.

[0012] According to the invention recited in claim 2, it is possible to inform the user that a refund is available.

[0013] According to the invention described in claim 3, refund processing that cannot be handled automatically can be handled by the administrator.

[0015] Claim 4 According to the invention described above, if a refund becomes necessary after a computer has executed a process after completion of settlement for the execution of the process between the user and the settlement center, the refund can be made without the user having to perform any operation for the refund even if the computer stops before the refund is completed. [Brief description of the drawings]

[0016] [Figure 1] 1 is a block diagram showing the overall configuration of a printing system according to an embodiment of the present invention and an image forming apparatus according to the embodiment of the present invention; [Diagram 2] 1 is a diagram illustrating a hardware configuration of an image forming apparatus according to an embodiment of the present invention. [Diagram 3] 5 is a diagram showing an example of a data configuration of a job log stored in a job log storage unit in the present embodiment. FIG. [Figure 4] 10 is a diagram showing an example of a data configuration of a payment management job log stored in a payment management job log storage unit in the present embodiment. FIG. [Diagram 5] 10 is a diagram showing an example of a data configuration of a payment log stored in a payment log storage unit in the present embodiment. FIG. [Figure 6] 5 is a flowchart showing a job execution process according to the present embodiment. [Figure 7] 10A to 10C are diagrams showing examples of screens displayed on an operation panel and screen transitions when a job is being executed in the present embodiment. [Figure 8A] FIG. 4 is a sequence diagram showing a job execution process according to the present embodiment. [Figure 8B] FIG. 8B is a sequence diagram continuing from FIG. 8A. [Figure 9] 6 is a flowchart showing a restart process of the image forming apparatus according to the present embodiment. [Figure 10] FIG. 13 is a diagram showing an example of a refund failure screen displayed to a user when a refund has failed in the present embodiment. [Figure 11] 11A to 11C are diagrams showing examples of screens for a machine administrator that are displayed on an operation panel in the present embodiment, and screen transitions. [Figure 12] FIG. 4 is a sequence diagram showing a restart process of the image forming apparatus according to the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.

[0018] Fig. 1 is a block diagram showing the overall configuration of a printing system according to the present embodiment and an image forming device 10 according to the present embodiment. Fig. 1 shows a configuration in which the image forming device 10, a mobile terminal 2 carried by a user who uses the image forming device 10, and a payment center 3 are connected via a network 4.

[0019] FIG. 2 is a hardware configuration diagram of an image forming apparatus 10 as an example of an information processing apparatus according to the present invention. The image forming apparatus 10 is a multifunction machine equipped with various functions such as a printing function, a copying function, and a scanning function, and is an apparatus equipped with a computer, that is, an information processing apparatus. In FIG. 2, a ROM 22 stores various programs related to the control of the apparatus and the transmission and reception of electronic data, and a CPU (processor) 21 controls the operation of various mechanisms installed in the apparatus, such as a scanner 26 and a printer 27, according to the programs stored in the ROM 22. A RAM 23 is used as a work memory when a program is executed and as a communication buffer when transmitting and receiving electronic data. A HDD (Hard Disk Drive) 24 stores electronic documents read using the scanner 26. An operation panel 25 accepts instructions from a user and displays information. The scanner 26 reads a document set by a user and stores the document in the HDD 24 or the like as electronic data. The printer 27 prints an image on an output paper according to an instruction from a control program executed by the CPU 21. A network interface (IF) 28 connects to the network 4 and is used for transmitting and receiving electronic data to and from external devices, and for accessing the device via a browser. An address data bus 29 connects to various mechanisms controlled by the CPU 21 and communicates data.

[0020] 1, the image forming device 10 in this embodiment has a user interface (UI) processing unit 11, a job execution control unit 12, a payment processing unit 13, a control unit 14, a job log storage unit 15, a job log storage unit for payment management 16, and a payment log storage unit 17. Note that the image forming device 10 originally has components for executing various functions such as a print function and a copy function, but components that are not used in the description of this embodiment are omitted from the figure.

[0021] The user interface processing unit 11 makes the operation panel 25 function. That is, the user interface processing unit 11 functions as an operation receiving unit that receives user operations on the operation panel 25, and as a display control unit that displays various screens on the operation panel 25. The job execution control unit 12 controls the execution of a job requested by a user. In this embodiment, a fee is incurred with the execution of a job, and the settlement processing unit 13 performs settlement-related processing such as collecting the fee from the user in cooperation with the settlement center 3. In addition, when a refund is required, the settlement processing unit 13 performs the refund processing. In this embodiment, the "refund processing" performed by the image forming device 10 refers to processing for requesting the settlement center 3 to refund the user. The control unit 14 cooperates with the other components 11 to 13 to control the image forming device 10 to execute a job, perform settlement processing that occurs with the execution of a job, and further perform refund processing as necessary.

[0022] FIG. 3 is a diagram showing an example of the data configuration of a job log stored in the job log storage unit 15 in this embodiment. In the job log storage unit 15, a job log generated by the job execution control unit 12 in association with the execution of a job is accumulated. A user, an execution date and time, the number of sheets discharged, and an execution status are included in a job ID as identification information for identifying each job. The user is set with identification information of a user who has requested the execution of a job, such as a user ID or a user name. The execution date and time is set with the date and time when the execution of the job is started. The number of sheets discharged is set with the accumulated number of sheets output by the execution of the job. The execution status is set with the current status of the job. The execution status is set with the status before the job is started (before start), during execution, a state in which the job is forcibly terminated during execution (i.e., aborted), normal termination, a case where the job is not normally terminated (abnormal termination), and the like.

[0023] FIG. 4 is a diagram showing an example of the data configuration of the job log for payment management stored in the job log storage unit for payment management 16 in this embodiment. In the job log storage unit for payment management 16, information on the job log received by the payment processing unit 13 from the job execution control unit 12 is saved as the job log for payment management. Basically, the same items as those in the job log may be set in the job log for payment management. The item fields for job ID and execution status are set in synchronization with the information from the job execution control unit 12. However, the transaction number to be linked to the payment log may be set to the information received from the payment center 3. Also, as described later, the job execution control unit 12 sends a notification to the payment processing unit 13 every time a sheet of paper is discharged, and the date and time when the notification is received is recorded in the job log for payment management as the date and time of discharge. In other words, the job log for payment management is generated every time a notification is received from the job execution control unit 12, and recorded in the job log for payment management 16.

[0024] FIG. 5 is a diagram showing an example of the data configuration of the payment log stored in the payment log storage unit 17 in this embodiment. In the payment log storage unit 17, information sent from the payment center 3 in association with the payment and refund is received by the payment processing unit 13 and stored. The payment log is generated for each transaction linked to the execution of a job, and includes a transaction number as information for identifying the transaction, in association with the date and time, the payment amount, the payment result, and the refund procedure. The date and time is set to the date and time when the transaction number is received, that is, the date and time when the transaction is started. The payment amount is set to the amount generated by the transaction, that is, the payment amount related to the execution of the job between the user and the payment center 3. The payment result is set to whether or not the payment has been completed with the user. The refund procedure is set to "-", which indicates that it is unclear whether or not a refund is required, whether or not a refund is required, and whether or not the refund procedure has been completed with the user if a refund is required.

[0025] Each of the components 11 to 14 in the image forming apparatus 10 is realized by the cooperative operation of a computer mounted on the image forming apparatus 10 and a program running on a CPU 21 mounted on the computer. Furthermore, the job log storage unit 15 and the payment management job log storage unit 16 are realized in the RAM 23. The HDD 24 may be used for backup. Furthermore, the payment log storage unit 17 is realized in the HDD 24. Alternatively, the RAM 23 may be used. Alternatively, an external storage means may be used via a network.

[0026] Furthermore, the programs used in the present embodiment can be provided not only by communication means, but also by being stored in a computer-readable recording medium such as a CD-ROM or a USB memory. The programs provided from the communication means or recording medium are installed in a computer, and various processes are realized by the CPU 21 of the computer sequentially executing the programs.

[0027] The mobile terminal 2 is an information device equipped with a computer, and is assumed to be, for example, a smartphone or a tablet terminal. As described later, in this embodiment, a payment code represented by a QR code (registered trademark) or the like displayed on the operation panel 25 is read, so the mobile terminal 2 is provided with a function of reading the payment code, such as a camera. The mobile terminal 2 also has at least an application having a function of analyzing the read payment code and a payment function for making a payment with the payment center 3.

[0028] A fee is incurred when a user executes a job using the image forming device 10, and the payment center 3 is a facility for handling the procedures for the payment at that time and for refunds when a refund to the user becomes necessary. The payment center 3 is provided with a payment server 31 for processing payments and refunds. The payment server 31 performs payments related to the user's use of the image forming device 10 by communicating with the mobile terminal 2 and the image forming device 10. Furthermore, when a refund becomes necessary as a result of the image forming device 10 executing a job in response to a user's request, the payment server 31 performs a refund to the user.

[0029] Next, the operation of this embodiment will be described.

[0030] The image forming apparatus 10 in this embodiment executes a job requested by a user. Here, a print job for outputting a printed matter as a deliverable will be described as an example of the job. When executing the job, the image forming apparatus 10 collects a fee from the user according to the quantity of deliverables, etc. Therefore, the image forming apparatus 10 starts executing the job requested by the user only after confirming that the settlement has been completed. Below, an overview of the process performed by the image forming apparatus 10 when executing a job will be described with reference to the flowchart shown in FIG. 6 and FIG. 7 showing a screen displayed on the operation panel 25.

[0031] A user logs in and selects the print button 30 from a menu screen (FIG. 7(a)) displayed on the operation panel 25 to display a print setting screen (FIG. 7(b)). When the user sets a desired print attribute on the print setting screen and selects the start button 32 to instruct execution of a job, the image forming device 10 accepts the execution instruction (step 110). Then, the image forming device 10 performs a payment process associated with the execution of the job (step 120). In the payment process, a payment screen (FIG. 7(c)) displaying a payment code generated by the payment server 31 is displayed on the operation panel 25. When the user reads the payment code displayed on the operation panel 25 using the mobile terminal 2 and completes the payment in a predetermined procedure (Y in step 130), the image forming device 10 starts execution of the job (step 140). During execution of the job, the image forming device 10 displays a job execution screen (FIG. 7(d)) ​​on the operation panel 25. If the payment is not made for some reason (N in step 130), the image forming apparatus 10 ends the process without executing the job.

[0032] The image forming apparatus 10 executes the job until the job is finished or the user selects the stop button 33 on the screen to cancel the job (N in step 150). When the job is finished or canceled (Y in step 150), the image forming apparatus 10 calculates the fee (hereinafter referred to as the "execution amount") incurred by actually executing the job (step 160). Next, the image forming apparatus 10 compares the payment amount with the execution amount, and if the payment amount exceeds the execution amount (Y in step 170), it performs a refund process (step 180) and refunds the difference between the payment amount and the execution amount as the refund amount. When the refund is completed, the image forming apparatus 10 displays a refund screen (FIG. 7(e)) on the operation panel 25 to inform the user of the refund amount. Note that if the payment amount and the execution amount match (N in step 170), the image forming apparatus 10 ends the process without performing the refund process and displays a menu screen (FIG. 7(a)) on the operation panel 25.

[0033] The refund screen shown in Figure 7(e) displays information such as the status indicating the reason why a refund was required, and whether the refund was completed successfully or, if not, the refund status indicating the reason why.

[0034] Next, the above-mentioned process will be described in detail with reference to the sequence diagrams shown in FIGS. 8A and 8B.

[0035] A user logs in to the image forming apparatus 10 and instructs the execution of a job from a job execution screen displayed by operating the operation panel 25 (step 111). When the user interface processing unit 11 in the image forming apparatus 10 accepts the instruction, the job execution control unit 12 instructs the payment processing unit 13 to make a payment for the execution of the job (step 112). The job execution control unit 12 issues job identification information (hereinafter, "job ID") for the instructed job, generates a job log including identification information (hereinafter, "user ID") of the user who instructed the execution of the job, and registers it in the job log storage unit 15. The instruction from the job execution control unit 12 includes information identifying the user who instructed the job (e.g., user ID) and the job ID, and information required to calculate the fee incurred by the execution of the job, such as printing attribute information such as paper size, number of output sheets, and black and white / color printing, and the payment processing unit 13 calculates the fee incurred by the execution of the job by referring to the printing attribute information (step 121). The fee calculated here is equal to the payment amount. The payment processing unit 13 then requests payment by transmitting payment request information including the payment amount and identification information of the user making the payment (hereinafter also referred to as the "payer") (step 122). In addition, the payment processing unit 13 generates a job log for payment management including a job ID in response to the payment instruction from the job execution control unit 12, and registers the job log in the payment management job log storage unit 16.

[0036] In response to a request from the payment processing unit 13, the payment server 31 in the payment center 3 creates a payment code including at least access information to the payment server 31, the payer, and the payment amount (step 123). The payment server 31 then generates and internally stores information related to the payment, specifically, payment information including the payer, the transaction number with the payer, and the payment amount. Thereafter, the payment server 31 returns the payment code to the payment processing unit 13 (step 124). The transaction number and the payment amount are added to the payment code. Note that, although the payment center 3 issues the transaction number in this embodiment, the transaction number may also be issued when the image forming device 10, for example the payment processing unit 13, requests payment.

[0037] When the payment processing unit 13 receives a reply from the payment server 31, it generates a payment log including the transaction number, the start date and time of the transaction, and the payment amount, and registers it in the payment log storage unit 17. Since the payment with the user has not yet been completed, flag information indicating that the payment has not yet been completed ("Not yet") is set as the initial value for the payment result in the payment log. Since it is unclear whether the refund procedure is necessary or not, information indicating this ("-") is set as the initial value. The payment processing unit 13 also sets and registers the transaction number in the job log for payment management that corresponds to the job ID received from the job execution control unit 12. Since the job has not yet been executed at this point, the discharge date and time of the job log for payment management is set to NULL, and the execution status is set to before start.

[0038] In this way, the job log and the job log for payment management are linked by the job ID, and the job log for payment management and the payment log are linked by the transaction number. Next, the payment processing unit 13 sends the payment code to the job execution control unit 12 (step 125), and waits for a payment completion notice to be sent from the payment server 31 (step 126).

[0039] When the payment code is received from the payment processing unit 13, the job execution control unit 12 instructs the user interface processing unit 11 to display the payment code on the operation panel 25 (step 127).

[0040] The payment code is a code that can be read by a camera, such as a QR code, as shown in Fig. 7(c). The user then operates the mobile terminal 2 to read the payment code, accesses the payment server 31, and makes a payment with the payment center 3 (step 131). The transaction for the payment between the user and the payment center 3 may be carried out by a conventional method.

[0041] When the payment with the user is completed, the payment server 31 adds a notice that the payment has been completed to the payment information and stores it internally. Then, the payment server 31 transmits a payment completion notice to the payment processing unit 13 (step 132). The payment processing unit 13 also changes the payment result in the payment log from "not yet" to information indicating that the payment has been completed ("completed").

[0042] When the payment process is completed as described above, the payment processing unit 13 instructs the job execution control unit 12 to start executing the job (step 141). At the timing of this instruction, the payment processing unit 13 may change the execution state of the payment management job log from before it was started to during execution, without receiving a notification of the start of job execution from the job execution control unit 12.

[0043] The job execution control unit 12 starts the execution of the job in response to an instruction from the payment processing unit 13 (step 142). At this time, the date and time when the job execution started is set to the execution date and time of the corresponding job log. Also, the execution status of the job log is changed from before it was started to during execution.

[0044] As described above, in this embodiment, a print job is executed, and when the job execution control unit 12 generates a printed matter on one sheet of paper, it increments the number of sheets discharged in the job log by 1 and notifies the payment processing unit 13 that one sheet of paper has been discharged (hereinafter referred to as "one sheet discharge notification") (step 143).

[0045] Each time the payment processing unit 13 receives a notification that one sheet of paper has been discharged, it registers the date and time when the notification was received (hereinafter, "discharge date and time") in the job log for payment management. In the job log, one record is registered for one job, but in the job log for payment management, one record is added each time one sheet of paper is discharged. In other words, for one job that produces multiple printed sheets, multiple logs are recorded in the job log for payment management. Note that in this embodiment, the method of recording the number of discharged sheets is different between the job log and the job log for payment management, but the number of discharged sheets may be managed in the same way according to either one.

[0046] When the job is completed (step 151), the job execution control unit 12 notifies the payment processing unit 13 of the completion (step 152). At this time, the job execution control unit 12 changes the execution status of the job log from "in progress" to "completed normally," "completed abnormally," or "stopped," depending on the completion situation.

[0047] When the payment processing unit 13 receives a job completion notification from the job execution control unit 12, it changes the execution status of the job log for payment management to match the job log. Note that since multiple records are registered in the job log for payment management for a job that produces multiple printed sheets, the execution status of all records may be changed, or only the execution status of the last record may be changed.

[0048] When the payment processing unit 13 receives a job completion notification from the job execution control unit 12, it calculates the amount actually incurred by the execution of the job, i.e., the execution amount (step 161). Next, the payment processing unit 13 compares the payment amount stored in the payment log with the calculated execution amount. If the payment amount exceeds the execution amount, the payment processing unit 13 performs a predetermined refund process. Specifically, it requests the payment center 3 to carry out a refund procedure by specifying the difference between the payment amount and the execution amount, i.e., the refund amount (step 181). At this time, if the refund procedure is necessary, the payment processing unit 13 sets information to the refund procedure item field in the payment log that the refund procedure is necessary but has not yet been completed ("not yet"). On the other hand, if the refund procedure is not necessary, the payment processing unit 13 sets information to the effect that the refund procedure is not necessary ("not necessary").

[0049] In response to the refund procedure request, the settlement center 3 refunds the refund amount to the user (step 182). Note that the refund method may be any conventional method. When the refund is completed, the settlement server 31 adds a message to the settlement information indicating that the refund has been completed and stores the message internally. The settlement server 31 then notifies the settlement processing unit 13 that the refund has been completed (step 183).

[0050] When the payment processor 13 receives a notification from the payment server 31 that the refund procedure has been completed, it sets information that the procedure has been completed ("Completed") in the item field for the refund procedure in the refund payment log, and notifies the job execution controller 12 that a refund has been made (step 184). When the job execution controller 12 receives this notification, it instructs the user interface processor 11 to display a refund screen shown in Fig. 7(e) on the operation panel 25, thereby notifying the user that a refund has been made (step 185).

[0051] According to this embodiment, by carrying out the above-mentioned processing, even if a refund is required, the user does not need to perform a special operation to receive the refund. In other words, the user can automatically receive the refund.

[0052] Incidentally, when a refund is necessary, as described above, the settlement center 3 carries out the refund in response to a request from the settlement processing unit 13. However, if the system of image forming device 10 goes down and stops for some reason between the time when the settlement center 3 carries out the refund procedure in response to the refund procedure request and the time when the settlement processing unit 13 is notified of the completion of the refund, that is, before the settlement center 3 confirms the completion of the refund to the user, image forming device 10 will not know whether the refund to the user has been normally carried out.

[0053] Therefore, in the present embodiment, even if the image forming apparatus 10 stops before the refund is completed, the refund can be made without the user having to perform any operation for the refund. Below, an overview of the process performed after the image forming apparatus 10 stops and is restarted will be described with reference to the flowchart shown in FIG.

[0054] When the image forming device 10 is restarted, it acquires the job log, the job log for payment management, and the payment log from each of the storage units 15 to 17 (step 210). Next, the image forming device 10 compares the registered contents of the job log and the job log for payment management (step 220). In this embodiment, since the number of sheets discharged with the execution of the job is compared, the number of logs linked to the job ID of the job for payment management is acquired as the number of discharged sheets from the job log for payment management, and is compared with the number of discharged sheets in the job log. Here, if the number of discharged sheets matches (Y in step 230), and if the refund procedure in the payment log is "required (completed)" (Y in step 240), the image forming device 10 does not need to perform any processing related to the refund since the refund to the user has been completed. If not (N in step 240), the image forming device 10 calculates the amount to be executed based on the number of discharged sheets (step 250), and then performs the refund processing (step 260).

[0055] As described above, in the present embodiment, the necessity of the refund process is determined after the image forming apparatus 10 is restarted, and if it is determined that the refund process is necessary, the refund process is automatically performed.

[0056] On the other hand, depending on the reason and timing of the image forming apparatus 10 stopping, the number of ejected sheets obtained from the job log and the job log for payment management may not match. In this case (N in step 230), the execution amount cannot be calculated accurately. In other words, since the amount to be refunded to the user cannot be determined, the necessity of refunding the user is uncertain. Therefore, the image forming apparatus 10 notifies the machine administrator that the automatic refund has failed because the necessity of refunding the user is uncertain (step 270). Alternatively, the refund failure screen shown in FIG. 10 may be displayed on the operation panel 25 to have the user contact the machine administrator.

[0057] The steps to be taken by the system administrator upon receiving the notification will be described with reference to an example of a screen displayed on the operation panel 25 shown in FIG.

[0058] First, when notified that the automatic refund has failed, the machine administrator logs in to the image forming apparatus 10. Next, from the menu screen (FIG. 11(a)) which is the same as FIG. 7(a) displayed on the operation panel 25, the machine administrator selects the payment list button 35 to display the machine administrator login screen (FIG. 11(b)). When the machine administrator logs in by inputting authentication information of the machine administrator ID and password on the machine administrator login screen and selecting the login button 36, the payment list screen (FIG. 11(c)) is displayed on the operation panel 25.

[0059] The payment list screen displays information registered in the payment log. Figure 11(c) shows a list of extracted transaction numbers, dates and times, and refund procedures. The payment logs to be displayed may be limited to transactions within a specified period or a specified number of recent transactions, or to transactions for which the refund procedure has not yet been completed.

[0060] Here, the machine administrator selects the icon 37 displayed corresponding to the transaction to be processed, thereby displaying the refund execution screen for that transaction (Fig. 11(d)) and proceeding with the refund procedure for that transaction. As described above, if the execution amount is unknown because the number of ejected sheets in the job log and the payment management job log do not match, the correct execution amount is found, set the refund amount on the refund execution screen, and the refund to the user is made by selecting the refund button 38. When the refund is completed, the refund screen (Fig. 11(e)) is displayed.

[0061] Next, the details of the above-mentioned process performed when the image forming apparatus 10 is restarted will be described with reference to a sequence diagram shown in FIG.

[0062] When the image forming apparatus 10 is restarted, the payment processing unit 13 acquires the job log, the payment management job log, and the payment log from each of the storage units 15 to 17 (steps 211, 212, 213). Note that the order of acquiring the logs from each of the storage units 15 to 17 is not limited to the above.

[0063] Next, the settlement processing unit 13 compares the number of ejected sheets obtained from the job log and the settlement management job log (step 221).

[0064] If the number of ejected sheets does not match, the settlement processing unit 13 cannot correctly calculate the amount to be executed since the correct number of ejected sheets is not obtained, and is therefore unable to request a refund procedure from the settlement center 3. In this case, the settlement processing unit 13 instructs the job execution control unit 12 to notify the machine administrator (step 271), and the job execution control unit 12 notifies the administrator in response to this notification (step 272). The machine administrator who has received the notification sets the amount to be executed from the refund screen shown in FIG. 11(d) as described above (step 273). The job execution control unit 12 notifies the settlement processing unit 13 of the amount to be executed set by the machine administrator (step 274). In response to this notification, the settlement processing unit 13 requests a refund procedure by specifying the difference between the settlement amount and the amount to be executed (i.e., the refund amount) (step 261).

[0065] On the other hand, if the number of output sheets matches, it can be considered whether the job has been completed normally or not. You can check whether the job has been completed by referring to the execution status in the job log.

[0066] If the job has not ended normally, it is highly likely that the execution amount has not reached the settlement amount. Therefore, the settlement processing unit 13 calculates the execution amount (step 251), and requests the refund procedure by specifying the difference between the settlement amount and the execution amount (i.e., the refund amount) (step 261). Since the job has not ended, it is unclear whether the refund procedure has been completed in the settlement log, so the settlement processing unit 13 leaves the initial value ("-") set in the refund procedure item field in the settlement log, but by requesting the refund procedure, it sets information indicating that the refund procedure has not been completed ("not yet").

[0067] It is possible that the payment amount and the execution amount are equal even though the job has not been completed normally, but the refund procedure in the payment log should not be “required (completed)”, so the payment processing unit 13 will always request the refund procedure.

[0068] On the other hand, if the job has been completed normally, and the refund procedure in the payment log is "required (completed)", the refund to the user has been completed and there is no need to process the refund. If the refund procedure in the payment log is "-", the payment processing unit 13 calculates the amount to be executed (step 251) and requests the refund procedure (step 261). If the refund procedure in the payment log is "required (not yet)", the payment processing unit 13 has requested the refund procedure but has not yet received a notice of completion of the refund procedure from the payment center 3. Therefore, the payment processing unit 13 again calculates the amount to be executed (step 251) and requests the refund procedure (step 261).

[0069] As described above, even if the job has been completed normally, if the completion of the refund cannot be confirmed, the amount to be executed is calculated and a request for the refund procedure is made again.

[0070] In response to the refund procedure request, the settlement center 3 refunds the refund amount to the user (step 262). Next, the settlement server 31 notifies the settlement processing unit 13 that the refund has been completed (step 263). When requesting the refund procedure, the settlement processing unit 13 sets the refund procedure in the settlement log to "needed (not yet)", and when it receives a refund procedure completion notification from the settlement server 31, it changes the setting of the refund procedure in the settlement log from "needed (not yet)" to "needed (completed)".

[0071] Now, suppose that the image forming device 10 stops after the payment processing unit 13 makes a refund procedure request but before receiving a refund procedure completion notice. The payment server 31 completes the refund when it first receives the refund procedure request. Although the payment server 31 sends a refund procedure completion notice when the refund is completed, the payment processing unit 13 does not receive the refund procedure completion notice due to the stop of the image forming device 10. For this reason, the refund procedure in the payment log remains "needed (not yet)". Therefore, since the refund procedure in the payment log is "needed (not yet)" as described above, the payment processing unit 13 will request the refund procedure. However, if the payment server 31 has completed the refund, it does not need to refund the user again even if it receives a refund procedure request again. It is possible to determine whether the refund to the user has been completed in the payment server 31 because the fact that the refund has been completed is stored internally.

[0072] As described above, when the refund procedure is performed as necessary, the settlement server 31 notifies the settlement processing unit 13 that the refund has been completed (i.e., a refund procedure completion notice) (step 263). As described above, if the refund to the user has already been completed, the settlement server 31 notifies the settlement processing unit 13 that the refund has been completed even if the refund to the user has not been made at this point.

[0073] When the payment processor 13 receives a notification from the payment server 31 that the refund procedure has been completed, it sets information that the procedure has been completed ("Completed") in the item field for the refund procedure in the refund payment log, and notifies the job execution controller 12 that a refund has been made (step 264). When the job execution controller 12 receives this notification, it instructs the user interface processor 11 to display a refund screen shown in Fig. 7(e) on the operation panel 25, thereby notifying the user that a refund has been made (step 265).

[0074] As described above, according to this embodiment, even if a refund to the user becomes necessary and image forming apparatus 10 stops before the refund to the user is completed, the refund can be made without the user having to perform any operation for the refund.

[0075] In this embodiment, a section for refund procedures is provided in the payment log so that the completion status of the refund to the user can be confirmed. However, if a failure occurs in the payment log or in a storage unit such as HDD 24 that stores the payment log in image forming device 10, the completion status of the refund cannot be confirmed. In this case, payment processing unit 13 may check the completion status of the refund to the user by inquiring about the completion status of the refund to the user to payment center 3 after restarting image forming device 10.

[0076] In addition, in the present embodiment, the printing process using the printing function of the image forming apparatus 10 has been described as an example of a process that requires payment, but this is not limiting.

[0077] In the above embodiments, the term "processor" refers to a processor in a broad sense, including general-purpose processors (e.g., CPU: Central Processing Unit, etc.) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic device, etc.).

[0078] In addition, the operations of the processor in the above embodiments may be performed not only by one processor, but also by multiple processors located at physically separate locations working together. The order of the operations of the processor is not limited to the order described in the above embodiments, and may be changed as appropriate. [Explanation of symbols]

[0079] 2 mobile terminal, 3 payment center, 4 network, 10 image forming device, 11 user interface (UI) processing unit, 12 job execution control unit, 13 payment processing unit, 14 control unit, 15 job log storage unit, 16 payment management job log storage unit, 17 payment log storage unit, 21 CPU, 22 ROM, 23 RAM, 24 HDD, 25 operation panel, 26 scanner, 27 printer, 29 address data bus, 31 payment server.

Claims

1. A processor is provided. The processor, After confirming the completion of the settlement regarding the execution of the process between the user and the settlement center, the process is executed; if the amount of the payment collected in the settlement before the start of the processing in the information processing device exceeds the amount of the fee incurred by the execution of the processing, a refund process is carried out to request the settlement center to refund the user; When the payment center notifies the user that the refund has been completed in response to the refund process, the payment center internally stores the completion of the refund; when it is confirmed that the notification of the completion of the refund, which is notified from the settlement center in response to the refund process, is not stored internally when the information processing device is restarted after being stopped, the refund process is carried out again; confirming the completion of the refund to the user by receiving a notification of the completion of the refund to the user from the settlement center in response to the refund process at the time of restart; 23. An information processing apparatus comprising:

2. 2 . The information processing apparatus according to claim 1 , wherein, when a refund becomes necessary for the user, the processor notifies the user that a refund will be made.

3. The information processing device according to claim 1, characterized in that if, after the information processing device is restarted, the amount to be refunded to the user cannot be determined because the amount calculated from the execution log of the process does not match the amount calculated from the payment management log associated with the execution of the process, the processor does not carry out the refund process at the time of restart and notifies an administrator that the amount is uncertain.

4. On the computer, A function of executing a process after confirming completion of a settlement between the user and the settlement center; a function of performing a refund process to request the settlement center to refund the user when the settlement amount collected in the settlement before the computer starts the process exceeds the amount incurred by the execution of the process; a function of storing, when a notification is received from the settlement center that the refund to the user has been completed in response to the refund process, the information indicating that the refund has been completed; a function of performing the refund process again when it is confirmed that the notification of the completion of the refund, which is notified from the settlement center in response to the refund process, is not stored internally when the computer is restarted after being stopped; a function of confirming completion of the refund to the user by receiving a notification of the completion of the refund to the user from the settlement center in response to the refund process at the time of restart; A program to achieve this.

Images