System, method, and program for registering image data

Abstract

It supports the smooth registration of image data associated with input information. [Solution] A payment processing server 10 according to one embodiment of the present invention provides payment processing services to users using first and second user terminals 20 and 30 that are connected to each other via a communication network NW. The server 10 provides access information for accessing an image data acquisition screen for acquiring image data related to input information acquired from the first user terminal 20. Based on the operation on the image data acquisition screen output by the second user terminal 30 via access through the access information, the server registers the image data acquired from the second user terminal 30 in association with the input information. Therefore, users can easily register image data associated with input information entered via the first user terminal 20 by accessing the image data acquisition screen via the second user terminal 30.

Description

Technical Field

[0001] The present invention relates to a technique for registering image data, and more particularly, to a technique for registering by associating input information with image data.

Background Art

[0002] Conventionally, in various types of procedures such as applications or registrations, registration of image data associated with input information has been performed. For example, the input information is information input along with an application or the like, and the image data includes image data obtained by photographing evidentiary documents or the like required at the time of the application or the like. For example, Patent Document 1 below discloses a payment processing service for a user who has received a statement for account transfer by a financial institution to make a payment using a credit card instead of account transfer. In such a service, image data of the statement or the like may be required as evidentiary documents along with the input of payment information based on the statement to be paid. In this case, the image data is registered in association with the input payment information.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the conventional services as described above, when inputting information associated with an application or registration through a device such as a personal computer, it may be a burden for the user to prepare image data of necessary evidentiary documents or the like. For example, when there is no image data of evidentiary documents or the like, it is necessary to obtain the image data by reading through a scanner or photographing through a camera, and transfer the image data to a device such as a personal computer.

[0005] One of the objectives of the embodiments of the present invention is to support the smooth registration of image data associated with input information. [Means for solving the problem]

[0006] A system according to one embodiment of the present invention is a system comprising one or more computer processors, wherein the one or more computer processors perform the steps of: acquiring input information from a first terminal; providing access information for accessing a first screen for acquiring image data related to the input information; acquiring image data from a second terminal based on an operation on the first screen output at a second terminal via access through the access information; and registering the image data and the input information in association based on the access information.

[0007] A method according to one embodiment of the present invention is a method performed by one or more computers, comprising: acquiring input information from a first terminal; providing access information for accessing a first screen for acquiring image data related to the input information; acquiring image data from a second terminal based on an operation on the first screen output at a second terminal via access through the access information; and registering the image data and the input information in association based on the access information.

[0008] A program according to one embodiment of the present invention causes one or more computers to perform the steps of: acquiring input information from a first terminal; providing access information for accessing a first screen for acquiring image data related to the input information; acquiring image data from a second terminal based on an operation on the first screen output by the second terminal via access through the access information; and registering the image data and the input information in association based on the access information. [Effects of the Invention]

[0009] Various embodiments of the present invention support the smooth registration of image data associated with input information. [Brief explanation of the drawing]

[0010] [Figure 1] A schematic diagram showing the configuration of a network including a payment processing server 10 according to one embodiment of the present invention. [Figure 2] A diagram illustrating the information managed by user information table 1511. [Figure 3] A diagram illustrating the information managed by payment information management table 1512. [Figure 4] A flowchart illustrating the processes that the payment processing server 10 executes when a user registers payment information. [Figure 5] A diagram illustrating the payment target selection screen 50. [Figure 6] A diagram illustrating the first payment information input screen 60. [Figure 7] A diagram illustrating the second payment information input screen 70. [Figure 8] A diagram illustrating the first image file registration screen 80. [Figure 9] A diagram illustrating the second image file registration screen 90. [Figure 10] This figure illustrates the first image file registration screen 80 when an image file has been registered. [Figure 11] This diagram illustrates the first top screen 300 of the first mobile image file registration screen. [Figure 12] This diagram illustrates the first confirmation screen 310 of the first mobile image file registration screen. [Figure 13] This diagram illustrates the second top screen 320 of the first mobile image file registration screen. [Figure 14] This diagram illustrates the second confirmation screen 330 of the first mobile image file registration screen. [Figure 15]A diagram illustrating the completion screen 340 of the image file registration screen for the first mobile device. [Figure 16] A diagram illustrating the top screen 400 of the image file registration screen for the second mobile device. [Figure 17] A diagram illustrating the confirmation screen 410 of the image file registration screen for the second mobile device. [Figure 18] A diagram illustrating the completion screen 420 of the image file registration screen for the second mobile device. [Figure 19] A diagram illustrating the image confirmation screen 500. [Figure 20] A flowchart illustrating the processing executed by the payment processing server 10 when performing clearing processing in a batch.

Embodiments for Carrying Out the Invention

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In each drawing, the same or similar components may be assigned the same reference numerals. Other objects of the embodiments of the present invention will become apparent by referring to the entire specification.

[0012] FIG. 1 is a configuration diagram schematically showing the configuration of a network including a payment processing server 10 according to an embodiment of the present invention. As shown in the figure, the payment processing server 10 is communicably connected to a first user terminal 20 and a second user terminal 30 used by the same user via a communication network NW such as the Internet. The payment processing server 10 provides a payment processing service to the users who use the first user terminal 20 and the second user terminal 30. In addition, the payment processing server 10 is communicably connected to a staff terminal 48 used by the person in charge of the payment processing service. The payment processing server 10 is an example of a device that implements all or part of the system of the present invention.

[0013] First, the hardware configuration of the payment processing server 10 will be described. The payment processing server 10 is configured as a general-purpose computer and, as shown in Figure 1, includes a computer processor 11, main memory 12, input / output interface 13, communication interface 14, and storage (memory device) 15. These components are electrically connected via buses and the like (not shown).

[0014] The computer processor 11 is composed of a CPU, GPU, FPGA, or a circuit including these, and reads various programs stored in storage 15, etc., into the main memory 12 and executes various instructions contained in the program. The main memory 12 is composed of, for example, DRAM.

[0015] The input / output interface 13 includes various input / output devices for exchanging information with the operator, etc. The input / output interface 13 includes, for example, information input devices such as keyboards and pointing devices (e.g., mice, touch panels, etc.), audio input devices such as microphones, and image input devices such as cameras. Furthermore, the input / output interface 13 includes image output devices such as displays and audio output devices such as speakers.

[0016] Communication I / F14 is implemented as hardware such as a network adapter, various communication software, or a combination thereof, and is configured to enable wired or wireless communication via a communication network NW.

[0017] The storage 15 is composed of, for example, a magnetic disk or flash memory. The storage 15 stores various programs, including an operating system, and various data. For example, the storage 15 has various tables 151 for managing various information. Also, for example, the storage 15 stores a server-side program 40 according to one embodiment of the present invention. The program 40 is a program for causing the payment processing server 10 to function as all or part of a system for providing payment processing services. At least a part of the server-side program 40 may be configured to be executed on the first user terminal 20 or second user terminal 30 side via the first terminal-side program 42 or second terminal-side program 44 described later.

[0018] In this embodiment, the payment processing server 10 may be configured using a plurality of computers, each having the hardware configuration described above. For example, the payment processing server 10 may be configured by one or more server devices.

[0019] The payment processing server 10 configured in this way can be configured to function as both a web server and an application server. In this case, it will perform various processes in response to requests from the first terminal-side program 42 or the second terminal-side program 44 installed on the first user terminal 20 or the second user terminal 30, respectively, and will transmit screen data (e.g., HTML data) and control data, etc., corresponding to the results of the processing, to the first user terminal 20 or the second user terminal 30. The first user terminal 20 and the second user terminal 30 will then output a web page or other screen based on the received data.

[0020] Next, the hardware configuration of the first user terminal 20 will be described. The first user terminal 20 is configured as a general-purpose computer and, as shown in Figure 1, includes a computer processor 21, main memory 22, input / output interface 23, communication interface 24, and storage (memory device) 25, with each of these components electrically connected via a bus or the like (not shown).

[0021] The computer processor 21 is composed of a CPU, GPU, FPGA, or a circuit including these, and reads various programs stored in storage 25, etc., into the main memory 22 and executes various instructions contained in the programs. The main memory 22 is composed of, for example, DRAM.

[0022] The input / output interface 23 includes various input / output devices for exchanging information with the operator, etc. The input / output interface 23 includes, for example, information input devices such as keyboards and pointing devices (e.g., mice, touch panels, etc.), audio input devices such as microphones, and image input devices such as cameras. Furthermore, the input / output interface 23 includes image output devices such as displays and audio output devices such as speakers.

[0023] Communication I / F24 is implemented as hardware such as network adapters, various communication software, and combinations thereof, and is configured to enable wired or wireless communication via a communication network NW, etc.

[0024] The storage 25 is composed of, for example, a magnetic disk or flash memory. The storage 25 stores various programs, including the operating system, and various data. The programs stored in the storage 25 can be downloaded and installed from an application market or the like. The storage 25 also stores the first terminal-side program 42 described above. The program 42 is configured as a web browser or other application (for example, a first application for payment processing services), and as described above, it may be configured to execute at least a part of the server-side program 40.

[0025] In this embodiment, the first user terminal 20 may be configured as a smartphone, tablet device, wearable device, or personal computer, etc.

[0026] A user operating the first user terminal 20 configured in this way can use the payment processing service provided by the payment processing server 10 by communicating with the payment processing server 10 via the first terminal-side program 42 installed on the storage 25, etc.

[0027] Next, the hardware configuration of the second user terminal 30 will be described. The second user terminal 30, like the first user terminal 20, is configured as a general-purpose computer and, as shown in Figure 1, includes a computer processor 31, main memory 32, input / output interface 33, communication interface 34, and storage (memory device) 35. These components are electrically connected via buses and the like (not shown).

[0028] The storage 35 stores the second terminal-side program 44 described above. The program 44 is configured as a web browser or other application (for example, a second application for payment processing services) and may be configured to execute at least a portion of the server-side program 40 as described above.

[0029] In this embodiment, the second user terminal 30 may be configured as a smartphone, tablet device, wearable device, or personal computer, etc.

[0030] A user operating the second user terminal 30 configured in this way can use the payment processing service provided by the payment processing server 10 by communicating with the payment processing server 10 via the second terminal-side program 44 installed on the storage 35, etc. In this embodiment, the second user terminal 30 is used when using the image data registration function in the payment processing service.

[0031] Next, the functions of the payment processing server 10 configured in this way will be described. As shown in Figure 1, the computer processor 11 of the payment processing server 10 is configured to function as a management function control unit 112 and a service provision control unit 114 by executing instructions contained in a program (for example, at least a part of the server-side program 40) loaded into the main memory 12.

[0032] The management function control unit 112 is configured to perform various processes related to the control of the management functions of the payment processing service. For example, the management function control unit 112 transmits screen data and control data for various screens related to the management functions to the first user terminal 20 or the second user terminal 30, performs various processes in response to user input via the screens output at the first user terminal 20 or the second user terminal 30, and transmits screen data and control data according to the results of the processes to the first user terminal 20 or the second user terminal 30. The management functions controlled by the management function control unit 112 include, for example, login processing (user authentication) and management of user information.

[0033] The service provision control unit 114 is configured to perform various processes to control the provision of payment processing services. In this embodiment, the service provision control unit 114 is configured to acquire input information from the first user terminal 20. The input information typically includes payment information subject to payment processing (e.g., information contained in an invoice received by the user). For example, the service provision control unit 114 acquires input information entered by the user via an input screen output at the first user terminal 20.

[0034] Furthermore, the service provision control unit 114 is configured to perform payment processing (for example, transfer processing to a financial institution's account, and payment processing using a payment slip) targeting payment information included in the input information. Payment processing includes processing to request payment from financial institutions, etc. (including requests for immediate payment, and registration / reservation of future payments). The service provision control unit 114 is also configured to perform billing processing (card payment processing) to bill the user's payment card (for example, a credit card, etc.). The billing amount to the user is set, for example, as the payment amount in the payment processing plus a predetermined fee. Billing processing includes, for example, authorization request processing (authorization processing) to request approval of the use of the payment card from the payment card company, and sales processing (clearing processing) to record sales corresponding to the billing amount.

[0035] In this embodiment, the service provision control unit 114 is configured to provide access information for accessing an image data acquisition screen (first screen) for acquiring image data related to input information. For example, the service provision control unit 114 transmits the access information to the first user terminal 20 upon acquisition of input information from the first user terminal 20. The access information may be generated in advance or generated in response to the acquisition of input information. The access information is displayed, for example, on a screen output by the first user terminal 20 (for example, the input screen or another screen accessed from that screen). The access information includes, for example, the URL of a web page corresponding to the image data acquisition screen.

[0036] Furthermore, the service provision control unit 114 is configured to acquire image data from the second user terminal 30. For example, in response to an access request from the second user terminal 30 via the access information, the service provision control unit 114 transmits screen data and control data of the image data acquisition screen to the second user terminal 30, and acquires image data based on the operation of the image data acquisition screen output by the second user terminal 30. For example, the second user terminal 30 takes a picture of an invoice corresponding to payment information based on the user's operation of the image data acquisition screen, and the service provision control unit 114 acquires the image data of the invoice from the second user terminal 30.

[0037] In this embodiment, the second user terminal 30 can acquire the access information in various ways. For example, the second user terminal 30 can acquire the access information by optically reading a two-dimensional code containing the access information displayed on the first user terminal 20, or by communication such as short-range wireless communication between it and the first user terminal 20.

[0038] Furthermore, the service provision control unit 114 is configured to associate and register the image data acquired from the second user terminal 30 with the input information based on the access information. For example, the access information is configured as information that can identify the related input information, and the input information identified by the access information and the image data are registered in association. The image data is stored, for example, in a predetermined area of ​​the storage 15, and the electronic file corresponding to the image data (for example, the path name and file name, etc.) is managed in association with the input information.

[0039] Thus, in this embodiment, the payment processing server 10 provides access information for accessing an image data acquisition screen to acquire image data related to input information acquired from the first user terminal 20. Based on the operation on the image data acquisition screen output by the second user terminal 30 via access through said access information, the server acquires image data from the second user terminal 30 and registers the image data in association with the input information. Therefore, the user can easily register image data associated with input information entered via the first user terminal 20 by accessing the image data acquisition screen via the second user terminal 30. In other words, the payment processing server 10 supports the smooth registration of image data associated with input information.

[0040] In this embodiment, the association between input information and image data based on access information can be realized in various ways. For example, access information may be associated with input information directly or indirectly in various ways. For example, access information may include identification information that can identify input information. In this case, when the service provision control unit 114 responds to an access request from the second user terminal 30 via access information, it acquires the identification information contained in the access information and registers the image data acquired from the second user terminal 30 in association with the input information identified by the identification information. Alternatively, for example, an image data acquisition screen accessible via access information may be associated with identification information that can identify input information (for example, the URL of the web page corresponding to the screen may be associated with the identification information). In this case, the service provision control unit 114 registers the image data acquired from the second user terminal 30 based on an operation on the image data acquisition screen output by the second user terminal 30, in association with the input information identified by the identification information associated with the image data acquisition screen. Such a configuration makes it possible to associate input information and access information in various ways.

[0041] In this embodiment, the type of image data acquisition screen (e.g., screen configuration, screen transitions, and functions, etc.) may differ depending on the type of input information. That is, the service provision control unit 114 may be configured to provide access information for accessing a first type of image data acquisition screen when the type of input information is a first type, and to provide access information for accessing a second type of image data acquisition screen when the type of input information is a second type. The first and second types of image data acquisition screens display different information from each other. The type of input information may be, for example, the type of image data corresponding to that input information. This configuration makes it possible to present an appropriate image data acquisition screen according to the type of input information to which the image data is associated.

[0042] Furthermore, the service provision control unit 114 may be configured to determine whether or not a payment process can be performed for payment information included in the input information, and to control the payment process based on the result of the determination of whether or not the payment process can be performed. For example, if it is determined that the payment process can be performed, the payment process is executed, and if it is determined that the payment process cannot be performed, the payment process is not executed or is canceled. For example, the service provision control unit 114 is configured to determine whether or not a payment process can be performed based on an operation on an image data confirmation screen (second screen) that displays registered image data. The image data confirmation screen is output, for example, on a staff terminal 48 (configured as a general computer) operated by a staff member in charge of the payment processing service, and if the staff member performs an operation indicating that the payment process can be performed, it is determined that the payment process can be performed. Alternatively, for example, the service provision control unit 114 may be configured to determine whether or not a payment process can be performed based on the payment information and image data included in the input information. For example, based on the image data of the invoice corresponding to the payment information, the payment information contained in the invoice is recognized (for example, using OCR technology), and if the recognized payment information matches the payment information contained in the input information, it is determined that payment processing is possible. This configuration makes it possible to determine whether or not payment processing is possible based on registered image data.

[0043] Next, a specific example of a payment processing server 10 of this embodiment having such functions will be described. In this specific example, the payment processing service is configured to allow a user who has received an invoice to make a payment by credit card instead of by bank transfer or payment slip. Such a service is sometimes called a BPSP (Business Payment Solution Provider).

[0044] First, in this example, we will explain the information managed by each table included in the various tables 151. Figure 2 illustrates the information managed by the user information table 1511 in this example. In this example, the user information table 1511 manages information about users of the payment processing service, and as shown in the figure, it manages information such as "basic information" including name and contact information, and "credit card information" which is information about credit cards, associated with a "user ID" that identifies individual users. Users include individual users and corporate users.

[0045] Credit card information includes the card number, expiration date, and cardholder name. Security codes such as the CVC number may also be recorded as part of the credit card information. In this example, one user can register information for multiple credit cards.

[0046] Figure 3 illustrates the information managed by the payment information management table 1512 in this example. In this example, the payment information management table 1512 manages information related to payment information registered by the user, and as shown in the figure, it manages information such as the "payment target type" indicating the type of payment target, the "user ID" identifying the corresponding user, "payment amount", "remitter", "bank account information", "payment slip information", "payment date", "credit card information" which is information about the credit card used to settle the invoice amount to the user, "sales processing date", "image file information" which is information about the image file (image data) of the supporting document submitted by the user, and "image verification result" which indicates the result of image verification based on the image file. In this example, the payment targets are general invoices (bank transfer) and social insurance premium payment slips, and the payment target type is set to a value corresponding to one of these. In addition, the remitter and bank account information are set when the payment target is a general invoice, but not when the payment target is a social insurance premium payment slip. Furthermore, payment slip information is set when the payment subject is a social insurance premium payment slip, but not when the payment subject is a general invoice. Image file information includes information that can identify each image file, specifically the path name and file name of the image file.

[0047] The above explains the information managed by each table in this example. Next, we will explain the processes executed by the payment processing server 10 in this example, as well as the screens output on the first user terminal 20, the second user terminal 30, and the staff terminal 48, etc. Figure 4 is a flowchart illustrating the processes executed by the payment processing server 10 when a user registers payment information (requests payment). First, the payment processing server 10 accepts the registration of payment information as shown in the figure (step S100). In this example, the payment information is entered by the user via the screen output on the first user terminal 20.

[0048] Figure 5 illustrates a payment target selection screen 50 displayed on the first user terminal 20. This screen 50 is for the user to select a payment target and, as shown in the figure, has a first button 52 which is selected when the payment target is a general invoice and a second button 54 which is selected when the payment target is a social insurance premium payment slip.

[0049] When the first button 52 is selected, the first payment information input screen 60, as illustrated in Figure 6, is displayed. This screen 60 is for the user to input payment information corresponding to a general invoice, and as shown in the figure, it has a bank transfer information input area 62 for inputting bank transfer destination information, a bank transfer request information input area 64 for inputting bank transfer request information, a card information input area 66 for inputting card information related to the credit card to be used, and a registration button 68.

[0050] The recipient information entered via the recipient information input area 62 specifically includes the recipient's financial institution, branch, account type, and account number, as shown in the diagram. Multiple recipient information entries can be pre-registered, and the selected information from these entries will be entered into the recipient information input area 62. Furthermore, the transfer request information entered via the transfer request information input area 64 specifically includes the transfer amount, the name of the transferor, and the designated transfer date. The user enters these items based, for example, on information contained in an invoice received from a business partner. In this example, the designated transfer date can be set to a date three business days or more after the current date.

[0051] The card information input area 66 is configured to allow the user to select a card from one or more credit cards (managed in the user information table 1511) that are pre-registered and associated with the user, and also displays the billing amount to the user (the amount to be settled by credit card). The billing amount is the payment amount (transfer amount) plus a prescribed fee.

[0052] When the registration button 68 is selected, the information entered via areas 62, 64, and 66 is registered. Specifically, the payment processing server 10 generates a new record in the payment information management table 1512 and sets the payment information ID, payment target type, user ID, payment amount (transfer amount), remitter (name of remitter), recipient account information, payment date (transfer date), and credit card information.

[0053] On the other hand, when the second button 54 on the payment target selection screen 50 illustrated in Figure 5 is selected, the second payment information input screen 70 illustrated in Figure 7 is displayed. This screen 70 is for the user to input payment information corresponding to the social insurance premium payment slip, and as shown in the figure, it has a payment slip information input area 72 for inputting payment slip information, a payment request information input area 74 for inputting payment request information, a card information input area 76 for inputting card information related to the credit card to be used, and a registration button 78.

[0054] The payment slip information entered via the payment slip information input area 72 specifically includes the collecting agency number, payment number, and confirmation number, as shown in the figure. The collecting agency number is set as a fixed value corresponding to the collecting agency for social insurance premiums (Japan Pension Service) (in the example in Figure 7, it is "00500"). The payment request information entered via the payment request information input area 74 specifically includes the payment amount and the designated payment date. The user enters these items based on the information written on the payment slip received from the collecting agency, for example. In this example, the designated payment date can be set to a date three business days or more after the current date, similar to the designated transfer date mentioned above.

[0055] The card information input area 76, like the card information input area 66 described above, is configured to allow the user to select a card from one or more credit cards that have been pre-registered and associated with the user, and further displays the billing amount to the user. As described above, the billing amount is the payment amount (repayment amount) plus a prescribed fee.

[0056] When the registration button 78 is selected, the information entered via areas 72, 74, and 76 is registered. Specifically, the payment processing server 10 generates a new record in the payment information management table 1512 and sets the payment information ID, payment target type, user ID, payment amount (payment amount), payment slip information, payment date (payment date), and credit card information.

[0057] Returning to the flowchart in Figure 4, once the payment information registration is accepted, the payment processing server 10 then generates and presents access information (step S110). The access information is information for accessing the mobile image file registration screen (image data acquisition screen) for registering image files. The mobile image file registration screen is configured to be suitable for mobile devices such as smartphones. The access information is displayed on the first user terminal 20.

[0058] Figure 8 illustrates the first image file registration screen 80 that is output on the first user terminal 20 in response to the selection of the registration button 68 on the first payment information input screen 60 illustrated in Figure 6. This screen 80 is for registering (uploading) image files of documents to be submitted (identity verification documents and contracts or invoices) when the payment target is a general invoice, and as shown in the figure, it has a registration area 82 for registering image files, an access information display area 84 for displaying access information, and a confirmation button 86. The registration area 82 has a file selection button 821 with the text "Select File" added to it.

[0059] The access information display area 84 displays a two-dimensional code 841 in which the aforementioned access information is embedded. Specifically, this access information is a parameterized URL for the first mobile image file registration screen corresponding to the case where the payment target is a general invoice, and the value of the corresponding payment information ID (identification information) is set as the URL parameter.

[0060] Figure 9 illustrates the second image file registration screen 90 that is output on the first user terminal 20 in response to the selection of the registration button 78 on the second payment information input screen 70 illustrated in Figure 7. This screen 90 is for registering (uploading) an image file of the document to be submitted (payment slip) when the payment target is a social insurance premium payment slip. Similar to the first image file registration screen 80 described above, it has a registration area 92, an access information display area 94, and a confirmation button 96, as shown in the figure. The registration area 92 has a file selection button 921, similar to the registration area 82 described above.

[0061] The access information display area 94 displays a two-dimensional code 941 with embedded access information, similar to the access information display area 84 described above. Specifically, this access information is a parameterized URL for the second mobile image file registration screen corresponding to the case where the payment target is a social insurance premium payment slip, and the value of the corresponding payment information ID is set as the URL parameter.

[0062] Returning to the flowchart in Figure 4, the payment processing server 10 then retrieves the image file (step S120) and registers the image file in association with the payment information (step S130). In this example, the registration of the image file is performed via the first image file registration screen 80 and the second image file registration screen 90 described above, as well as via the mobile image file registration screen.

[0063] For example, a user can register an image file by dragging and dropping the image file icon onto the registration area 82 on the first image file registration screen 80. Alternatively, by selecting the file selection button 821 on the registration area 82, a screen (not shown) for selecting the image file to register is displayed, and the user can register the selected image file through this screen. Once an image file is registered, the registered image file is stored in a predetermined area of ​​the storage 15 of the payment processing server 10, and the corresponding payment information image file information (image file path name and file name) is updated in the payment information management table 1512.

[0064] Figure 10 illustrates the first image file registration screen 80 when an image file has been registered. In this state, as shown in the figure, an image file object 822 is placed in the registration area 82 to display information about the registered image file. This object 822 displays a thumbnail image and a file name, and has a cancel button 823. When the cancel button 823 is selected, the registration of the corresponding image file is canceled.

[0065] Furthermore, for example, a user can register an image file by accessing the mobile image file registration screen via a two-dimensional code 841 displayed in the access information display area 84 of the first image file registration screen 80. Specifically, a user can access the mobile image file registration screen by reading the two-dimensional code 841 via the camera of the second user terminal 30.

[0066] Figure 11 illustrates the first top screen 300 of the first mobile image file registration screen output on the second user terminal 30. As shown in the figure, the screen 300 displays a shooting guide for identity verification documents and has a continue button 302 with the text "Proceed to shooting". The shooting guide includes necessary information and the orientation of the document. When the continue button 302 is selected, the camera of the second user terminal 30 is activated, and the user can take a picture of the target document through the camera.

[0067] When a photograph is taken via the camera, the first confirmation screen 310 of the first mobile image file registration screen, as illustrated in Figure 12, is displayed. As shown in the figure, the screen 310 has an image display area 312 that displays the captured image, a retake button 314, and a confirmation button 316 with the text "Use this photo" added to it. The user selects the retake button 314 if they do not want to use (register) the captured image, and selects the confirmation button 316 if they want to use the image. When the retake button 314 is selected, the camera of the second user terminal 30 is activated again.

[0068] On the other hand, when the confirmation button 316 is selected, an image file corresponding to the image of the captured identity verification document is sent to the payment processing server 10, and the payment processing server 10 registers the received image file in association with the payment information. Specifically, the received image file is stored in a predetermined area of ​​the storage 15, and the image file information of the target payment information (identified using the payment information ID set as a URL parameter) is updated in the payment information management table 1512. When the image file information is updated, the above-mentioned image file object 822, which displays information about the registered image file, is placed in the registration area 82 of the first image file registration screen 80 output on the first user terminal 20.

[0069] Furthermore, when the confirmation button 316 is selected, the second top screen 320 of the first mobile image file registration screen, as illustrated in Figure 13, is displayed. As shown in the figure, this screen 320 displays a shooting guide for the contract or invoice and has a continue button 322 with the text "Proceed to shooting". When the continue button 322 is selected, the camera of the second user terminal 30 is activated, and the user can take a picture of the document through the camera. Once the shooting is completed, the second confirmation screen 330 of the first mobile image file registration screen, as illustrated in Figure 14, is displayed. This screen 330, like the first confirmation screen 310 described above, has an image display area 332, a reshoot button 334, and a confirmation button 336, as shown in the figure.

[0070] When the confirmation button 336 is selected, the image file corresponding to the captured image of the contract or invoice is sent to the payment processing server 10, and the payment processing server 10 registers the received image file in association with the payment information. Specifically, the received image file is stored in a predetermined area of ​​the storage 15, and the image file information of the target payment information is updated in the payment information management table 1512. When the image file information is updated, as described above, an image file object 822 that displays information about the registered image file is placed in the registration area 82 of the first image file registration screen 80 output on the first user terminal 20.

[0071] Furthermore, when the confirmation button 336 is selected, the completion screen 340 of the first mobile image file registration screen, as illustrated in Figure 15, is displayed. As shown in the figure, this screen 340 displays text notifying that the registration (upload) of the identity verification document and the image files of the contract or invoice has been completed, and has a completion button 344. When the completion button 344 is selected, the completion screen 340 is closed.

[0072] Furthermore, for example, a user can register an image file by dragging and dropping the image file icon onto the registration area 92 on the second image file registration screen 90. Alternatively, by selecting the file selection button 921 on the registration area 92, a screen (not shown) for selecting the image file to register is displayed, and the user can register the selected image file through this screen. Once an image file is registered, as described above, the registered image file is stored in a predetermined area of ​​the storage 15 of the payment processing server 10, and the image file information (image file path name and file name) of the target payment information is updated in the payment information management table 1512. When the image file information is updated, an image file object displaying information about the registered image file is placed in the registration area 92 of the second image file registration screen 90, similar to the first image file registration screen 80.

[0073] Furthermore, for example, a user can register an image file by accessing the mobile image file registration screen via a two-dimensional code 941 displayed in the access information display area 94 of the second image file registration screen 90. Specifically, a user can access the mobile image file registration screen by reading the two-dimensional code 941 via the camera of the second user terminal 30.

[0074] Figure 16 illustrates the top screen 400 of the second mobile image file registration screen output on the second user terminal 30. As shown in the figure, the screen 400 displays a guide for taking a picture of the social insurance payment slip and has a continue button 402 with the text "Proceed to shooting". When the continue button 402 is selected, the camera of the second user terminal 30 is activated, and the user can take a picture of the target document through the camera.

[0075] When a photograph is taken via the camera, a confirmation screen 410 for registering the second mobile image file, as illustrated in Figure 17, is displayed. As shown in the figure, the screen 410 has an image display area 412 that displays the captured image, a retake button 414, and a confirmation button 416 with the text "Use this photo." The user selects the retake button 414 if they do not want to use the captured image, and selects the confirmation button 416 if they want to use the image. When the retake button 414 is selected, the camera of the second user terminal 30 is activated again.

[0076] On the other hand, when the confirmation button 416 is selected, an image file corresponding to the image of the social insurance payment slip that was photographed is sent to the payment processing server 10, and the payment processing server 10 registers the received image file in association with the payment information. Specifically, the received image file is stored in a predetermined area of ​​the storage 15, and the image file information of the target payment information (identified using the payment information ID set as a URL parameter) is updated in the payment information management table 1512. When the image file information is updated, an image file object displaying information about the registered image file is placed in the registration area 92 of the second image file registration screen 90 output on the first user terminal 20.

[0077] Furthermore, when the confirmation button 416 is selected, the completion screen 420 of the second mobile image file registration screen, as illustrated in Figure 18, is displayed. As shown in the figure, this screen 420 displays text notifying that the registration (upload) of the image file of the social insurance premium payment slip has been completed, and has a completion button 424. When the completion button 424 is selected, the completion screen 420 is closed.

[0078] Returning to the flowchart in Figure 4, once the image file is registered, the payment processing server 10 then performs card payment processing (authorization and clearing) (step S140). Specifically, it requests authorization (approval of the transaction by credit card) from the credit card company system (not shown) corresponding to the configured credit card, and also requests sales processing for the corresponding billing amount. Sales processing is performed with the payment processing service provider as the merchant. Once sales processing is completed, the sales processing date is set in the payment information management table 1512, and the payment by the corresponding credit card is confirmed. If the authorization process fails, a predetermined error handling procedure is performed.

[0079] Next, the payment processing server 10 executes the payment request process (step S150). Specifically, if the payment is for a general invoice, it requests a transfer from the corresponding financial institution system (not shown). In the process of requesting the transfer, the recipient account information, the transferor, the transfer amount (payment amount), and the transfer date (payment date), which are managed in the payment information management table 1512, are used. The transfer source account is a designated account managed by the payment processing service provider. If the payment is for a social insurance premium payment slip, it requests payment by payment slip from the corresponding financial institution system (not shown). In the process of requesting payment, the payment slip information (collector number, payment number, confirmation number) and the payment date (payment date), which are managed in the payment information management table 1512, are used. The transfer source account is a designated account managed by the payment processing service provider. On the payment date, the corresponding financial institution processes the payment (account transfer or payment). The result of the payment processing may be transmitted from the financial institution system to the payment processing server 10.

[0080] In this example, the image files of the registered supporting documents are visually reviewed by the payment processing service staff. Figure 19 illustrates the image verification screen 500 displayed on the staff terminal 48 used by the payment processing service staff. As shown in the figure, the screen 500 has a user information display area 501 that displays information about the user who registered the payment information, a payment information display area 502 that displays payment information, an image information display area 504 that displays image information related to the image registered in association with the payment information, an OK button 506, and an NG button 508. The staff member confirms that the appropriate supporting documents have been submitted based on the information displayed in areas 501, 502, and 504.

[0081] When the person in charge selects either the OK button 506 or the NG button 508, the image verification result for the corresponding payment information is updated in the payment information management table 1512. When the image verification result is updated to "NG", the card payment processing and payment request processing for the target payment information are canceled. Specifically, the payment processing server 10 sends cancellation instructions to the credit card company system (not shown) and the financial institution system (not shown), respectively. Alternatively, after the image verification result is updated to "NG", the person in charge of the payment processing service may follow up (e.g., request the user to resubmit supporting documents (image files)), and the card payment processing and payment request processing may be canceled according to further instructions from the person in charge.

[0082] In this example, the payment amount registered by the user is paid by bank transfer or payment by the payment processing service provider, and the invoice amount, which includes a prescribed fee, is settled using the user's credit card, with the payment processing service provider acting as the merchant. The sales proceeds for the prescribed period are then transferred from each credit card company to the payment processing service provider as the merchant.

[0083] In the example described above, card payment processing is performed in response to the registration of payment information. However, the clearing process within the card payment processing may be performed collectively for multiple payment information entries. In this case, for example, the sales processing date is set along with the execution of the authorization process described above. For example, the sales processing date may be set to a date three business days after the date the authorization process is executed (i.e., today).

[0084] Figure 20 is a flowchart illustrating the processes executed by the payment processing server 10 when performing a clearing process (sales processing of invoice amounts to users) in a batch. These processes are executed at a predetermined time every business day. First, as shown in the figure, the payment processing server 10 extracts payment information for which the sales processing date is today (step S200). Specifically, in the payment information management table 1512, payment information for which the sales processing date is today and the image verification result is "OK" is extracted.

[0085] Next, the payment processing server 10 performs sales processing for the billing amount corresponding to the extracted payment information (step S210). Specifically, for each payment information, it requests the corresponding credit card company system to perform sales processing for the corresponding credit card. The sales processing is performed with the payment processing service provider as the merchant. Once the sales processing is completed, the payment by the corresponding credit card is finalized.

[0086] In the example described above, the access information is a parameterized URL for the mobile image file registration screen, and the value of the corresponding payment information ID is set as the URL parameter. However, the method of associating access information with payment information is not limited to this. For example, the URL of the mobile image file registration screen itself may be changed for each piece of payment information to be registered, and the URL may be managed in the payment information management table 1512. In this case, the mobile image file registration screen can be said to be associated with the payment information.

[0087] In the example described above, when the payment target is a general invoice, the first mobile image file registration screen may include a screen for taking a picture of the thickness of the identity verification document, and a function to confirm said thickness.

[0088] In the example described above, the image files of the registered evidence documents were to be visually reviewed by the payment processing service staff, but this review could also be automated. For example, character recognition processing could be performed on the registered image files, and the result of the image review could be determined based on a comparison of the recognized payment information with the payment information managed in the payment information management table 1512.

[0089] As described above, the payment processing server 10 according to this embodiment provides access information for accessing an image data acquisition screen (e.g., a mobile image file registration screen) for acquiring image data related to input information (e.g., payment information) acquired from the first user terminal 20. Based on the operation on the image data acquisition screen output by the second user terminal 30 via access through said access information, the server acquires image data from the second user terminal 30 and registers the image data in association with the input information. Therefore, the user can easily register image data associated with input information entered via the first user terminal 20 by accessing the image data acquisition screen via the second user terminal 30. In other words, the payment processing server 10 supports the smooth registration of image data associated with input information.

[0090] In another embodiment of the present invention, some or all of the functions of the payment processing server 10 in the above-described embodiment are realized by the cooperation of the payment processing server 10 and the first user terminal 20, the second user terminal 30, or the person in charge terminal 48, or can be realized by the first user terminal 20, the second user terminal 30, or the person in charge terminal 48.

[0091] In other embodiments of the present invention, services other than the payment processing service described above are provided, and image data is registered in association with input information in those other services. For example, image data of supporting documents for expense reimbursement (e.g., receipts) is registered in association with input information (reimbursement request information) in an expense reimbursement service, image data of a driver's license is registered in association with input information (reservation information) in a rental car reservation service, and image data of a passport is registered in association with input information (reservation information) in an airline ticket reservation service. Thus, embodiments of the present invention can be applied to the registration of image data associated with input information in various service systems.

[0092] The processes and procedures described herein can be implemented by software, hardware, or any combination thereof, in addition to those explicitly described herein. For example, the processes and procedures described herein can be implemented by implementing the logic corresponding to those processes and procedures on a medium such as an integrated circuit, volatile memory, non-volatile memory, or magnetic disk. Furthermore, the processes and procedures described herein can be implemented as computer programs corresponding to those processes and procedures and executed by various types of computers.

[0093] Even if a process or procedure described herein is described as being performed by a single device, software, component, or module, such process or procedure may be performed by multiple devices, multiple software programs, multiple components, and / or multiple modules. Furthermore, the software and hardware elements described herein can also be realized by integrating them into fewer components or by decomposing them into more components.

[0094] In this specification, where a component of the invention is described as either one or more, or without limitation to either one or more, such component may be either one or more, unless the context should be otherwise interpreted. [Explanation of symbols]

[0095] 10 Payment Processing Server 11 Computer Processors 112 Management Function Control Unit 114 Service Provision Control Unit 15 Storage 1511 User Information Table 1512 Payment Information Management Table 20. First User Terminal 30 Second User Terminal 40 Server-side programs 42 First Terminal Program 44 Second Terminal Program 48. Terminal of the person in charge 50 Payment Method Selection Screen 60. First Payment Information Input Screen 70. Second Payment Information Input Screen 80 First Image File Registration Screen 90 Second Image File Registration Screen 300 First mobile image file registration screen (first top screen) 310 First mobile image file registration screen (first confirmation screen) 320 First mobile image file registration screen (second top screen) 330 First mobile image file registration screen (second confirmation screen) 340 First mobile image file registration screen (completion screen) 400 Second mobile image file registration screen (top screen) 410 Second mobile image file registration screen (confirmation screen) 420 Second mobile image file registration screen (completion screen) 500 Image confirmation screen

Claims

1. A system comprising one or more computer processors, wherein the one or more computer processors are The steps include obtaining input information from the first terminal, The steps include providing access information for accessing a first screen for acquiring image data related to the input information, The steps include: acquiring the image data from the second terminal based on the operation on the first screen output at the second terminal via access via the access information; The steps of registering the image data and the input information in association with each other based on the access information are performed. system.

2. The access information includes identification information that can identify the input information, The registration step involves associating the input information identified by the identification information included in the access information with the image data and registering them together. The system according to claim 1.

3. The first screen is associated with identification information that can identify the input information, The registration step involves associating the input information identified by the identification information associated with the first screen with the image data and registering them together. The system according to claim 1.

4. The step of providing the access information includes, when the type of input information is a first type, providing the access information for accessing the first screen of the first type, and when the type of input information is a second type, providing the access information for accessing the first screen of the second type. The first type of the first screen and the second type of the first screen display different information from each other. The system according to claim 1.

5. The step of providing the access information includes providing the access information for accessing the first screen of the first type when the type of image data corresponding to the input information is of the first type, and providing the access information for accessing the first screen of the second type when the type of image data corresponding to the input information is of the second type. The first type of the first screen and the second type of the first screen display different information from each other. The system according to claim 1.

6. The aforementioned input information includes payment information subject to payment processing, The first screen is a screen for obtaining the image data of the invoice corresponding to the payment information. The system according to claim 1.

7. The one or more computer processors described above further include: A step of determining whether the payment processing applied to the payment information is permissible, The following steps are performed: Based on the result of determining whether the payment processing is possible or not, control the payment processing targeting the payment information. The system according to claim 6.

8. The step of determining whether the payment processing is possible is to determine whether the payment processing is possible based on an operation on the second screen displaying the image data. The system according to claim 7.

9. The step of determining whether or not to process the payment involves determining whether or not to process the payment based on the payment information and the image data. The system according to claim 7.

10. A method performed by one or more computers, The steps include obtaining input information from the first terminal, The steps include providing access information for accessing a first screen for acquiring image data related to the input information, The steps include: acquiring the image data from the second terminal based on the operation on the first screen output at the second terminal via access via the access information; The system includes the step of registering the image data and the input information in association with each other based on the access information. method.

11. On one or more computers, The steps include obtaining input information from the first terminal, The steps include providing access information for accessing a first screen for acquiring image data related to the input information, The steps include: acquiring the image data from the second terminal based on the operation on the first screen output at the second terminal via access via the access information; The system performs the steps of registering the image data and the input information in association with each other based on the access information. program.

Images