System, method, and program for registering image data

Abstract

This assists in 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 a payment processing service to users using first and second user terminals 20, 30 that are communicatively connected 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, and registers the image data acquired from the second user terminal 30 in association with the input information based on an operation on the image data acquisition screen output on the second user terminal 30 through access via the access information. This allows a user to easily register image data associated with the 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 input information and image data in association with each other. [Background technology]

[0002] Conventionally, image data associated with input information has been registered in various types of application or request procedures. For example, the input information is information input in conjunction with an application, and the image data includes image data of supporting documents required for the application. For example, Patent Document 1 below discloses a payment processing service that enables a user who receives a bank transfer invoice from a financial institution to pay by credit card instead of bank transfer. In such a service, image data of the invoice or other supporting documents may be requested as supporting documents when payment information based on the invoice to be paid is input. In this case, the image data is registered in association with the input payment information. [Prior art documents] [Patent documents]

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

[0004] However, in the conventional services described above, when information for an application or request is input via a device such as a personal computer, preparing image data of the necessary evidence, etc., can be a burden for the user. For example, if image data of the evidence, etc., does not exist, it is necessary to obtain the image data by reading it with a scanner or photographing it with a camera, and then transfer the image data to a device such as a personal computer.

[0005] An object of the embodiment of the present invention is to support 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, which perform the following steps: acquiring input information from a first terminal; providing access information for accessing a first screen to acquire image data related to the input information; acquiring the image data from the second terminal based on an operation on the first screen output on the second terminal by access via the access information; and registering the image data in association with the input information based on the access information.

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

[0008] A program according to one embodiment of the present invention causes one or more computers to execute 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 the image data from the second terminal based on an operation on the first screen output on the second terminal by access via the access information, and registering the image data in association with the input information based on the access information. [Effects of the Invention]

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

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

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

[0012] FIG. 1 is a diagram illustrating a schematic configuration of a network including a payment processing server 10 according to one embodiment of the present invention. As shown in the figure, the payment processing server 10 is communicatively 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 users who use the first user terminal 20 and the second user terminal 30. The payment processing server 10 is also communicatively connected to a staff member terminal 48 used by a staff member providing 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, we will explain the hardware configuration of the payment processing server 10. The payment processing server 10 is configured as a general computer, and as shown in Figure 1, it includes a computer processor 11, a main memory 12, an input / output I / F 13, a communication I / F 14, and a storage (storage device) 15, with each of these components electrically connected via a bus or the like (not shown).

[0014] The computer processor 11 is configured with a CPU, GPU, FPGA, etc., or a circuit including any of them, and loads various programs stored in the storage 15, etc., into the main memory 12 and executes various instructions included in the programs. The main memory 12 is configured with, for example, a DRAM, etc.

[0015] The input / output I / F 13 includes various input / output devices for exchanging information with an operator, etc. The input / output I / F 13 includes, for example, information input devices such as a keyboard and a pointing device (e.g., a mouse, a touch panel, etc.), a voice input device such as a microphone, and an image input device such as a camera. The input / output I / F 13 also includes an image output device such as a display, and an audio output device such as a speaker.

[0016] The communication I / F 14 is implemented as hardware such as a network adapter, various communication software, or a combination of these, and is configured to enable wired or wireless communication via a communication network NW or the like.

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

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

[0019] The payment processing server 10 configured in this manner can be configured to function as a web server and an application server, in which case it executes various processes in response to requests from the first terminal-side program 42 or the second terminal-side program 44 installed in the first user terminal 20 or the second user terminal 30, respectively, and transmits screen data (e.g., HTML data) and control data according to the results of the processes to the first user terminal 20 or the second user terminal 30. The first user terminal 20 and the second user terminal 30 output web pages or other screens based on the received data.

[0020] Next, we will explain the hardware configuration of the first user terminal 20. The first user terminal 20 is configured as a general computer, and as shown in Fig. 1, it includes a computer processor 21, a main memory 22, an input / output I / F 23, a communication I / F 24, and a storage (storage device) 25, and these components are electrically connected via a bus or the like (not shown).

[0021] The computer processor 21 is configured with a CPU, GPU, FPGA, etc., or a circuit including any of them, and loads various programs stored in the storage 25, etc., into the main memory 22 and executes various instructions included in the programs. The main memory 22 is configured with, for example, a DRAM, etc.

[0022] The input / output I / F 23 includes various input / output devices for exchanging information with an operator, etc. The input / output I / F 23 includes, for example, information input devices such as a keyboard and a pointing device (e.g., a mouse, a touch panel, etc.), audio input devices such as a microphone, and image input devices such as a camera. The input / output I / F 23 also includes an image output device such as a display, and an audio output device such as a speaker.

[0023] The communication I / F 24 is implemented as hardware such as a network adapter, various communication software, or a combination thereof, and is configured to realize wired or wireless communication via a communication network NW or the like.

[0024] The storage 25 is configured, for example, by a magnetic disk or a flash memory. The storage 25 stores various programs including an operating system, various data, and the like. 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 can be configured as a web browser or other application (e.g., a first application for a payment processing service) and can be configured to execute at least a part of the server-side program 40 as described above.

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

[0026] A user operating the first user terminal 20 configured in this manner 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 in storage 25 or the like.

[0027] Next, we will explain the hardware configuration of the second user terminal 30. Like the first user terminal 20, the second user terminal 30 is configured as a general computer, and as shown in Fig. 1, it includes a computer processor 31, a main memory 32, an input / output I / F 33, a communication I / F 34, and a storage (storage device) 35, and these components are electrically connected via a bus or the like (not shown).

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

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

[0030] A user operating the second user terminal 30 configured in this manner 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 in the storage 35 or the like. In this embodiment, the second user terminal 30 is used when using the image data registration function in the payment processing service.

[0031] Next, we will explain the functions of the payment processing server 10 configured as above. 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 included in a program (e.g., 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 execute 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 of various screens related to the management functions to the first user terminal 20 or the second user terminal 30, executes various processes in response to operation input by the user via the screens output on 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 execute various processes for controlling the provision of the payment processing service. 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 that is the target of the payment processing (e.g., information written on 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 displayed on the first user terminal 20.

[0034] The service provision control unit 114 is also configured to perform payment processing (e.g., transfer processing to a financial institution's account, payment processing using a payment slip, etc.) for the payment information included in the input information. The payment processing includes processing for requesting payment from a financial institution, etc. (including requests for immediate payment and registration / reservation of future payment). The service provision control unit 114 is also configured to perform billing processing (card payment processing) for charging the billing amount to the user's payment card (e.g., 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. The billing processing includes, for example, approval request processing (authorization processing) for requesting approval for use of the payment card from the payment card company, and sales processing (clearing processing) for recording 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 in association with acquisition of input information from the first user terminal 20. The access information may be generated in advance or may be generated in response to acquisition of the input information. The access information is displayed, for example, on a screen output on the first user terminal 20 (for example, the above-mentioned input screen or another screen transitioned from the above screen). The access information includes, for example, the URL of a web page corresponding to the image data acquisition screen.

[0036] The service provision control unit 114 is also 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 an operation on the image data acquisition screen output on the second user terminal 30. For example, the second user terminal 30 photographs an invoice corresponding to payment information based on an operation by the user on the image data acquisition screen, and the service provision control unit 114 acquires 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 acquires the access information by optically reading a two-dimensional code including the access information displayed on the first user terminal 20, or by communication with the first user terminal 20, such as short-range wireless communication.

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

[0039] As described above, the payment processing server 10 in this embodiment provides access information for accessing an image data acquisition screen for acquiring image data associated with input information acquired from the first user terminal 20, acquires image data from the second user terminal 30 based on an operation on the image data acquisition screen output on the second user terminal 30 through access via the access information, and registers the image data in association with the input information, so that the user can easily register image data associated with the 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 of input information and image data based on access information can be realized in various ways. For example, the access information may be associated with the input information directly or indirectly in various ways. For example, the access information may include identification information capable of identifying the input information. In this case, when responding to an access request from the second user terminal 30 via the access information, the service provision control unit 114 acquires the identification information included in the access information and associates and registers the image data acquired from the second user terminal 30 with the input information identified by the identification information. Also, for example, an image data acquisition screen accessible via the access information may be associated with identification information capable of identifying the input information (e.g., the URL of a webpage 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 on the second user terminal 30, associated with the input information identified by the identification information associated with the image data acquisition screen. This configuration enables the association of input information and access information in various ways.

[0041] In this embodiment, the type of image data acquisition screen (e.g., screen configuration, screen transition, 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 the first type of image data acquisition screen when the type of input information is a first type, and to provide access information for accessing the 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 the input information. This configuration makes it possible to present an appropriate image data acquisition screen depending on the type of input information associated with image data.

[0042] The service provision control unit 114 may also be configured to determine whether or not payment processing is possible for the payment information included in the input information, and to control the payment processing based on the determination result of whether or not the payment processing is possible. For example, if it is determined that the payment processing is possible, the payment processing is executed, and if it is determined that the payment processing is impossible, the payment processing is not executed or canceled. For example, the service provision control unit 114 may be configured to determine whether or not payment processing is possible 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 member terminal 48 (configured as a general computer) operated by a staff member of the payment processing service, and if the staff member performs an operation indicating that the payment processing is possible, the payment processing is determined to be possible. For example, the service provision control unit 114 may also be configured to determine whether or not payment processing is possible based on the payment information and image data included in the input information. For example, the payment information included in the invoice is recognized based on the image data of the invoice corresponding to the payment information (for example, using OCR technology), and if the recognized payment information matches the payment information included in the input information, it is determined that payment processing is possible. This configuration makes it possible to determine whether payment processing is possible or not based on the registered image data.

[0043] Next, a specific example of one aspect of the payment processing server 10 of this embodiment having such functions will be described. The payment processing service in this example is configured as a service that allows users who receive an invoice to make payment by credit card instead of by bank transfer or payment by payment slip. Such a service is sometimes called a BPSP (Business Payment Solution Provider).

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

[0045] The credit card information includes the card number, expiration date, and cardholder name. A security code such as a CVC number may also be recorded as part of the credit card information. In this example, one user can register information about multiple credit cards.

[0046] FIG. 3 illustrates information managed by the payment information management table 1512 in this example. The payment information management table 1512 in this example manages information related to payment information registered by users. As shown in the figure, the table manages information such as a "payment object type" indicating the type of payment object, a "user ID" identifying the corresponding user, a "payment amount," a "transfer requester," "transfer account information," "payment slip information," "designated payment date," "credit card information" which is information about the credit card used to settle the amount invoiced to the user, a "sales processing date," "image file information" which is information about the image file (image data) of the documentary evidence submitted by the user, and an "image confirmation result" indicating the result of image confirmation based on the image file, in association with a "payment information ID" which identifies individual payment information. In this example, the payment object is a general invoice (direct transfer) and a social insurance premium payment slip, and the payment object type is set to a value corresponding to either of these. Furthermore, the transfer requester and the transfer account information are set when the payment object is a general invoice, but are not set when the payment object is a social insurance premium payment slip. In addition, the payment slip information is set when the payment object is a social insurance payment slip, but is not set when the payment object is a general invoice. The image file information includes information that can identify each image file, and specifically includes the path name and file name of the image file.

[0047] The information managed by each table in this example has been described above. Next, the processing executed by the payment processing server 10 and the screens output on the first user terminal 20, the second user terminal 30, the staff member terminal 48, etc. in this example will be described. Figure 4 is a flowchart illustrating the processing executed by the payment processing server 10 when a user registers payment information (requests payment). As shown in the figure, the payment processing server 10 first accepts the registration of payment information (step S100). In this example, the payment information is input by the user via a screen output on the first user terminal 20.

[0048] 5 illustrates a payment object selection screen 50 output on the first user terminal 20. The screen 50 is a screen for the user to select a payment object, and as shown in the figure, has a first button 52 that is selected when the payment object is a general bill, and a second button 54 that is selected when the payment object is a social insurance premium payment slip.

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

[0050] The transfer destination information entered through the transfer destination information input area 62 specifically includes the transfer destination financial institution, branch, account type, and account number, as shown in the figure. It is also possible to register multiple transfer destination information in advance, and select information from these multiple transfer destination information and enter it in the transfer destination information input area 62. The transfer request information entered through 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 on the information listed on an invoice received from a business partner, for example. In this example, the designated transfer date can be specified as a date that is three business days or later from the current day.

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

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

[0053] On the other hand, when the second button 54 on the payment object selection screen 50 illustrated in Fig. 5 is selected, a second payment information input screen 70 illustrated in Fig. 7 is output. The screen 70 is a screen for the user to input payment information corresponding to a social insurance premium payment slip, and as shown in the figure, 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 register button 78.

[0054] The payment slip information entered via the payment slip information input area 72 specifically includes the collection agency number, payment number, and confirmation number, as shown in the figure. The collection agency number is set as a fixed value ("00500" in the example of Figure 7) corresponding to the collection agency for social insurance premiums (Japan Pension Service). 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, for example, based on the information written on the payment slip received from the collection agency. In this example, the designated payment date can be specified as a date three business days from the current date, similar to the designated transfer date described 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 to be used from one or more credit cards that have been registered in advance in association with the user, and further displays the amount to be charged to the user. As described above, the amount to be charged is the payment amount (payment amount) plus a predetermined fee.

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

[0057] Returning to the flowchart of FIG. 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 a mobile image file registration screen (image data acquisition screen) for registering image files. The mobile image file registration screen is configured as a screen suitable for mobile terminals such as smartphones. The access information is displayed on the first user terminal 20.

[0058] 8 illustrates a first image file registration screen 80 output on the first user terminal 20 in response to selection of the registration button 68 on the first payment information input screen 60 illustrated in FIG. 6. The screen 80 is a screen for registering (uploading) image files of documents to be submitted (identification documents, and contract or invoice) when the payment object is a general invoice, and as illustrated, has a registration area 82 for registering image files, an access information display area 84 for displaying access information, and a confirm button 86. The registration area 82 has a file selection button 821 with the text "Select File" added.

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

[0060] Fig. 9 illustrates a second image file registration screen 90 output on the first user terminal 20 in response to selection of the registration button 78 on the second payment information input screen 70 illustrated in Fig. 7. The screen 90 is a screen for registering (uploading) an image file of a document to be submitted (a payment slip) when the payment object is a social insurance premium payment slip, and, like the first image file registration screen 80 described above, has a registration area 92, an access information display area 94, and a confirm button 96, as shown in the figure. The registration area 92 has a file selection button 921, like 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 above-described access information display area 84. Specifically, the access information is a parameterized URL of a second mobile image file registration screen that corresponds to the case where the payment object 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 of Figure 4, the payment processing server 10 then acquires the image file (step S120) and registers the image file in association with the payment information (step S130). In this example, the image file is registered via the mobile image file registration screen in addition to the first image file registration screen 80 and the second image file registration screen 90 described above.

[0063] For example, a user can register an image file by dragging and dropping the icon of the image file into the registration area 82 on the first image file registration screen 80. Furthermore, by selecting a file selection button 821 in 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 via that screen. When the image file is registered, the registered image file is stored in a predetermined area of ​​storage 15 of payment processing server 10, and the image file information (path name and file name of the image file) of the corresponding payment information is updated in payment information management table 1512.

[0064] 10 shows an example of the first image file registration screen 80 when an image file has been registered. As shown in the figure, the screen 80 in this state has an image file object 822 that displays information about the registered image file in a registration area 82. The object 822 displays a thumbnail image and the 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, the user can register an image file by accessing the mobile image file registration screen via the two-dimensional code 841 displayed in the access information display area 84 of the first image file registration screen 80. Specifically, the 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] 11 illustrates a 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 guide for photographing an identification document and has a continue button 302 with the text "Proceed to photographing." The photographing guide includes necessary information, the orientation of the document, etc. When the continue button 302 is selected, the camera of the second user terminal 30 is activated, and the user can photograph the target document via the camera.

[0067] When an image is captured using the camera, a first confirmation screen 310 of the first mobile image file registration screen, as shown in Fig. 12, is output. As shown in the figure, the screen 310 has an image display area 312 that displays the captured image, a re-capture button 314, and a confirm button 316 with the text "Use this photo" added. The user selects the re-capture button 314 if they do not want to adopt (register) the captured image, and selects the confirm button 316 if they want to adopt the image. When the re-capture button 314 is selected, the camera of the second user terminal 30 is activated again.

[0068] On the other hand, when the Confirm button 316 is selected, an image file corresponding to the photographed image of the identification 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 (specified 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 displaying 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 Confirm button 316 is selected, a second top screen 320 of the first mobile image file registration screen, as shown in FIG. 13, is output. As shown in the figure, the screen 320 displays a guide for photographing the contract or invoice, and has a continue button 322 with the text "Proceed to photographing." When the continue button 322 is selected, the camera of the second user terminal 30 is activated, allowing the user to photograph the document via the camera. Once the photograph is taken, a second confirmation screen 330 of the first mobile image file registration screen, as shown in FIG. 14, is output. Similar to the first confirmation screen 310 described above, the screen 330 has an image display area 332, a re-photograph button 334, and a confirm button 336, as shown in the figure.

[0070] When the Confirm button 336 is selected, an image file corresponding to the photographed 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 for the corresponding payment information is updated in the payment information management table 1512. Once the image file information has been updated, as described above, an image file object 822 displaying 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 Confirm button 336 is selected, a completion screen 340 of the first mobile image file registration screen, as shown in Fig. 15, is output. As shown in the figure, this screen 340 displays text notifying that the registration (upload) of the image files of the identification document and the contract or invoice has been completed, and has a Complete button 344. When the Complete 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 an icon of the image file into the registration area 92 on the second image file registration screen 90. Furthermore, by selecting a file selection button 921 in the registration area 92, a screen (not shown) for selecting an image file to register is displayed, and the user can register the selected image file via the screen. Once the 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 (path name and file name of the image file) of the corresponding payment information is updated in the payment information management table 1512. Once the image file information is updated, an image file object displaying information about the registered image file is arranged 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, the user can register an image file by accessing the mobile image file registration screen via the two-dimensional code 941 displayed in the access information display area 94 of the second image file registration screen 90. Specifically, the 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] 16 illustrates an example of a 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 photographing a social insurance payment slip, and has a continue button 402 with the text "Proceed to photographing." When the continue button 402 is selected, the camera of the second user terminal 30 is activated, and the user can photograph the target document via the camera.

[0075] When an image is captured using the camera, a confirmation screen 410 of the second mobile image file registration screen, as shown in Fig. 17, is output. As shown in the figure, the screen 410 has an image display area 412 that displays the captured image, a re-capture button 414, and a confirm button 416 with the text "Use this photo" added. The user selects the re-capture button 414 if they do not want to use the captured image, and selects the confirm button 416 if they want to use the image. When the re-capture button 414 is selected, the camera of the second user terminal 30 is activated again.

[0076] On the other hand, when the Confirm button 416 is selected, an image file corresponding to the photographed image of the social insurance premium payment slip 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 (specified 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 Confirm button 416 is selected, a completion screen 420 of the second mobile image file registration screen, as shown in Fig. 18, is output. 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 Complete button 424. When the Complete button 424 is selected, the completion screen 420 is closed.

[0078] Returning to the flowchart of Figure 4, once the image file has been registered, the payment processing server 10 then executes card payment processing (authorization processing and clearing processing) (step S140). Specifically, it requests authorization (approval of the credit card transaction) from the credit card company system (not shown) corresponding to the entered credit card, and requests sales processing of the corresponding billing amount. Sales processing is carried out with the payment processing service provider as the affiliated store. Once sales processing is carried out, the sales processing date is set in the payment information management table 1512, and payment by the corresponding credit card is confirmed. If the authorization processing fails, a predetermined error processing is carried out.

[0079] Next, the payment processing server 10 executes the payment request process (step S150). Specifically, if the payment object is a general invoice, a transfer request is made to the corresponding financial institution system (not shown). The transfer request process uses the transfer destination account information, transfer requester, transfer amount (payment amount), and transfer date (specified payment date) managed in the payment information management table 1512. The transfer source account is a specified account managed by the payment processing service provider. Furthermore, if the payment object is a social insurance premium payment slip, a request is made to the corresponding financial institution system (not shown) to make payment using the payment slip. The payment request process uses the payment slip information (receiving agency number, payment number, confirmation number) and payment date (specified payment date) managed in the payment information management table 1512. The payer account is a specified account managed by the payment processing service provider. On the specified payment date, the payment (account transfer or payment) process is carried out at the corresponding financial institution. The result of the payment process may be transmitted from the financial institution system to the payment processing server 10.

[0080] In this example, the image files of the registered evidential documents are visually confirmed by a payment processing service clerk. Figure 19 shows an example of an image confirmation screen 500 displayed on the payment processing service clerk's terminal 48. As shown, screen 500 includes 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 the payment information, an image information display area 504 that displays image information about the images registered in association with the payment information, an OK button 506, and an NG button 508. The clerk confirms that the appropriate evidential documents have been submitted based on the information displayed in areas 501, 502, and 504.

[0081] When the person in charge selects the OK button 506 or the NG button 508, the image confirmation result for the corresponding payment information is updated in the payment information management table 1512. When the image confirmation result is updated to "NG," the card settlement process and payment request process described above for the target payment information are canceled; specifically, a cancellation instruction is sent from the payment processing server 10 to the credit card company system (not shown) and the financial institution system (not shown). Note that after the image confirmation result is updated to "NG," a follow-up is performed by the person in charge of the payment processing service (such as requesting the user to resubmit supporting documents (image files)), and the card settlement process and payment request process may be canceled in accordance with separate instructions from the person in charge thereafter.

[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 payment amount plus a predetermined fee is charged to the payment processing service provider as an affiliated store using the user's credit card. Sales proceeds for a predetermined period are then transferred from each credit card company to the payment processing service provider as an affiliated store.

[0083] In the above example, the card payment process is performed in response to the registration of payment information, but the clearing process of the card payment process may be performed collectively for multiple payment information. In this case, for example, the sales processing date is set together with the execution of the authorization process described above, and for example, the date three business days after the execution date of the authorization process (i.e., the current day) is set as the sales processing date.

[0084] FIG. 20 is a flowchart illustrating the processing executed by the payment processing server 10 when performing a batch of clearing processing (sales processing of the amount billed to the user). This processing is executed at a predetermined time every business day. As shown in the figure, the payment processing server 10 first extracts payment information for which the sales processing date is the current day (step S200). Specifically, payment information for which the sales processing date is the current day and the image confirmation result is "OK" is extracted from the payment information management table 1512.

[0085] Next, the payment processing server 10 executes 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 process sales for the corresponding credit card. The sales processing is carried out with the payment processing service provider as the affiliated store. Once the sales processing is completed, the settlement by the corresponding credit card is confirmed.

[0086] In the above example, the access information is a parameterized URL of the mobile image file registration screen, and the value of the corresponding payment information ID is set as the URL parameter, but 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 payment information to be registered, and the URL may be managed in payment information management table 1512. In this case, it can be said that the mobile image file registration screen is associated with payment information.

[0087] In the above example, when the payment object is a general invoice, a screen for photographing the thickness of the identification document and a function for checking the thickness may be added to the first mobile image file registration screen.

[0088] In the above example, the image files of the registered evidential documents are visually inspected by a payment processing service representative, but such inspection may also be performed automatically. For example, a character recognition process may be performed on the registered image files, and the results of the image inspection may be determined based on a comparison of the recognized payment information with the payment information managed in the payment information management table 1512.

[0089] The payment processing server 10 according to the present embodiment described above provides access information for accessing an image data acquisition screen (e.g., a mobile image file registration screen) for acquiring image data associated with input information (e.g., payment information) acquired from a first user terminal 20, acquires image data from a second user terminal 30 based on an operation on the image data acquisition screen output on the second user terminal 30 through access via the access information, and registers the image data in association with the input information. This allows a user to 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 other embodiments of the present invention, some or all of the functions possessed by the payment processing server 10 in the above-described embodiments may be realized by cooperation between the payment processing server 10 and the first user terminal 20, the second user terminal 30, or the staff terminal 48, or may be realized by the first user terminal 20, the second user terminal 30, or the staff 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 for the other services. For example, image data of expense reimbursement evidence (e.g., receipts) is registered in association with input information (reimbursement request information) for an expense reimbursement service, image data of a driver's license is registered in association with input information (reservation information) for a rental car reservation service, and image data of a passport is registered in association with input information (reservation information) for an airline ticket reservation service. In this way, 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, other than those explicitly described, may be implemented by software, hardware, or any combination thereof. For example, the processes and procedures described herein may be implemented by implementing logic corresponding to the processes and procedures in media such as integrated circuits, volatile memory, non-volatile memory, and magnetic disks. The processes and procedures described herein may also be implemented as computer programs corresponding to the processes and procedures and executed by various computers.

[0093] Although processes and procedures described herein are described as being performed by a single device, software, component, or module, such processes or procedures may be performed by multiple devices, software, components, and / or modules. Also, the software and hardware elements described herein may be implemented by combining them into fewer components or breaking them down into more components.

[0094] In this specification, even if a component of the invention is described as either singular or plural, or is described without limitation as either singular or plural, the component may be either singular or plural unless the context requires otherwise. [Explanation of symbols]

[0095] 10 Payment Processing Server 11. Computer Processor 112 Management function control section 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 Program on the first terminal 44 Program on the second terminal 48 Personnel terminal 50 Payment item selection screen 60 First payment information entry 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. 1. A system comprising one or more computer processors, the one or more computer processors comprising: obtaining input information from a first terminal; providing access information to the first terminal for accessing a first screen for acquiring image data related to the input information; acquiring the image data from the second terminal based on an operation on the first screen output on the second terminal by access via the access information displayed on the first terminal; and registering the image data and the input information in association with each other based on the access information. system.

2. A system comprising one or more computer processors, wherein the one or more computer processors: obtaining input information from a first terminal; providing access information for accessing a first screen for obtaining image data related to the input information; acquiring the image data from the second terminal based on an operation on the second terminal with respect to the first screen output on the second terminal by access via the access information; and registering the image data and the input information in association with each other based on the access information. system.

3. the access information includes identification information capable of identifying the input information, the registering step registers the input information identified by the identification information included in the access information in association with the image data; 3. The system of claim 1 or 2.

4. the first screen is associated with identification information that can identify the input information; the registering step registers the input information identified by the identification information associated with the first screen and the image data in association with each other; 3. The system of claim 1 or 2.

5. the step of providing access information includes providing the access information for accessing the first screen of a first type when the type of the input information is a first type, and providing the access information for accessing the first screen of a second type when the type of the input information is a second type; the first screen of the first type and the first screen of the second type display different information from each other; 3. The system of claim 1 or 2.

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

7. The input information includes payment information to be processed; the first screen is a screen for acquiring the image data of an invoice corresponding to the payment information; 3. The system of claim 1 or 2.

8. The one or more computer processors further: a step of determining whether the payment process for the payment information is possible; and controlling the payment processing for the payment information based on the result of the determination of whether or not the payment processing is possible. The system of claim 7.

9. the step of determining whether the payment process is possible determines whether the payment process is possible based on an operation on a second screen that displays the image data. The system of claim 8.

10. the step of determining whether or not the payment process is possible determines whether or not the payment process is possible based on the payment information and the image data; The system of claim 8.

11. 1. A method implemented by one or more computers, comprising: obtaining input information from a first terminal; providing access information to the first terminal for accessing a first screen for acquiring image data related to the input information; acquiring the image data from the second terminal based on an operation on the first screen output on the second terminal by access via the access information displayed on the first terminal; and registering the image data and the input information in association with each other based on the access information. method.

12. A method executed by one or more computers, comprising: obtaining input information from a first terminal; providing access information for accessing a first screen for obtaining image data related to the input information; acquiring the image data from the second terminal based on an operation on the second terminal with respect to the first screen output on the second terminal by access via the access information; and registering the image data and the input information in association with each other based on the access information. method.

13. On one or more computers, obtaining input information from a first terminal; providing access information to the first terminal for accessing a first screen for acquiring image data related to the input information; acquiring the image data from the second terminal based on an operation on the first screen output on the second terminal by access via the access information displayed on the first terminal; and registering the image data and the input information in association with each other based on the access information. program.

14. One or more computers, obtaining input information from a first terminal; providing access information for accessing a first screen for obtaining image data related to the input information; acquiring the image data from the second terminal based on an operation on the second terminal with respect to the first screen output on the second terminal by access via the access information; and registering the image data and the input information in association with each other based on the access information. program.

Images