Information processing method, information processing device, and information processing program

Abstract

To provide an information processing method executed by a computer which reduces an input burden on bill information and prevents an input error when a buyer pays a bill by cashless settlement means, an information processing device, and an information processing program.SOLUTION: An information processing method implemented by a settlement agent system includes a step of acquiring bill data from a system possessing the bill data; a step of receiving a request of a settlement screen including identification information for identifying the bill data in order to pay the bill from a buyer terminal by cashless settlement means; a step of identifying the bill data on the basis of identification information and displaying bill information extracted from the identified bill data on the settlement screen in advance, and displaying the settlement screen on the buyer terminal in replay to the request; and a step of receiving a request for executing payment by the cashless settlement means from the buyer terminal which has displayed the settlement screen.SELECTED DRAWING: Figure 3

Description

[Technical field]

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

[0002] Traditionally, in B2B (business-to-business) payments, if a seller (supplier) wanted to accept card payments from a buyer, the supplier had to become an affiliated store of the acquirer's card. In recent years, however, a system has emerged in which an inter-company payment agent, who stands between the acquirer and the supplier, is placed as a pseudo-affiliated store, and the inter-company payment agent receives card payments and transfers the funds to the supplier, making it easier to make inter-company payments by credit card. Note that in the case of services provided by Visa, the inter-company payment agent is sometimes called a Business Payment Service Provider (BPSP), and in the case of services provided by Mastercard, it is sometimes called a Business Payment Aggregator Program (BPAP).

[0003] However, when a buyer uses a B2B payment service provider to make payments to a supplier by credit card, the buyer is required to enter the invoice information (invoice number, invoice amount, transfer date, transfer account information, etc.) listed on the invoice issued by the supplier into the payment screen provided by the B2B payment service provider, and the B2B payment service provider performs credit card authorization, sales processing, and payment to the supplier based on the invoice information entered by the buyer, without knowing whether the invoice information entered by the buyer is correct. This places a burden on the buyer to enter the invoice information, and there is also the possibility of input errors.

[0004] Patent document 1 proposes a program for use in a payment collection system for collecting payments from payers, which causes a processor to execute the steps of registering the payer's account information, issuing an invoice linked to the payer's account, and notifying a terminal used by the payer of information related to the invoice along with an electronic payment means (e.g., claim 1). [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent Publication No. 2022-184700 Summary of the Invention [Problem to be solved by the invention]

[0006] The present invention has been made in consideration of the above points, and an object of the present invention is to provide a technology that can reduce the burden of inputting invoice information and prevent input errors when a buyer pays an invoice using a cashless payment method. [Means for solving the problem]

[0007] An information processing method according to a first aspect of the present invention is an information processing method executed by a computer, comprising: acquiring invoice data from a system that holds the invoice data; receiving a request for a payment screen for paying an invoice with a cashless payment method from a buyer's terminal, the request including specific information for identifying invoice data; a step of displaying the settlement screen on the buyer's terminal in response to the request, the step of identifying invoice data based on the identification information, and displaying invoice information extracted from the identified invoice data on the settlement screen in advance; receiving a request to make a payment using a cashless payment method from the buyer's terminal that has displayed the payment screen; Includes.

[0008] According to this embodiment, invoice data is obtained in advance from a system that holds the invoice data, and when a buyer pays the invoice using a cashless payment method, invoice information extracted from the invoice data obtained in advance is displayed in advance on the payment screen, thereby reducing the burden on the buyer of inputting invoice information and preventing input errors.

[0009] An information processing method according to a second aspect of the present invention is the information processing method according to the first aspect, The method further includes a step of identifying invoice data based on the identification information, and then checking the payment history of the identified invoice data via a cashless payment method, and if payment has been made, outputting information notifying that payment has been made to the buyer's terminal.

[0010] According to this embodiment, if the invoice data to be paid by a cashless payment method has already been paid, the buyer is notified that the invoice data has already been paid, thereby preventing duplicate credit card payments.

[0011] An information processing method according to a third aspect of the present invention is the information processing method according to the first aspect, The method further includes a step of, after acquiring the invoice data from a system that holds the invoice data, and before receiving a request for the payment screen from the buyer's terminal, conducting a pre-screening of the supplier and / or buyer identified by the invoice information extracted from the acquired invoice data.

[0012] According to this embodiment, invoice data obtained in advance can be used to screen suppliers and / or buyers in advance (before transactions begin) (for example, by checking the existence of the corporation or whether they have any criminal cases), thereby preventing money laundering or transactions with anti-social organizations.

[0013] An information processing method according to a fourth aspect of the present invention is an information processing method according to any one of the first to third aspects, The invoice information includes at least one of an invoice number, an invoice amount, a transfer date, and transfer account information.

[0014] An information processing method according to a fifth aspect of the present invention is an information processing method according to any one of the first to third aspects, The step of displaying the settlement screen includes a step of displaying, on the settlement screen, an amount obtained by adding a prescribed handling fee to the invoice amount extracted from the specified invoice data as the credit card invoice amount.

[0015] An information processing method according to a sixth aspect of the present invention is an information processing method according to any one of the first to third aspects, receiving a request for a supplier's personal page from a supplier's terminal, the request including identification information for identifying the supplier and search conditions for identifying one or more invoice data; a step of displaying the My Page on the terminal of the supplier in response to the request, identifying the supplier based on the identification information, and displaying on the My Page a list of invoice data of the identified supplier that satisfies the search conditions; Further includes:

[0016] According to this embodiment, even if a large number of invoices have been issued by a supplier, the supplier can easily search for and check the invoice data that he or she wishes to check.

[0017] An information processing method according to a seventh aspect of the present invention is an information processing method according to the sixth aspect, receiving information for selecting one invoice data from the list of invoice data from the terminal of the supplier that has displayed the My Page; A step of confirming the transfer status of the selected invoice data and displaying it on the My Page; Further includes:

[0018] According to this embodiment, the supplier can easily check the transfer status of his / her own invoice data.

[0019] An information processing method according to an eighth aspect of the present invention is an information processing method according to the sixth aspect, receiving a request for reconciliation data for the invoice data that has already been transferred from the terminal of the supplier that has displayed the My Page; transmitting the reconciliation data to the supplier terminal in response to the request; Further includes:

[0020] According to this embodiment, the workload of clearing payments by suppliers can be reduced.

[0021] An information processing method according to a ninth aspect of the present invention is an information processing method according to any one of the first to third aspects, A step of receiving a request for a buyer's personal page from a buyer's terminal, the request including identification information for identifying the buyer and search conditions for identifying one or more invoice data; a step of displaying the My Page on the buyer's terminal in response to the request, the step of identifying a buyer based on the identification information, and displaying on the My Page a list of invoice data of the identified buyer that satisfies the search conditions; Further includes:

[0022] According to this embodiment, even if a large number of invoices have been issued to a buyer, the buyer can easily search for and check the invoice data that he or she wishes to check.

[0023] An information processing device according to a tenth aspect of the present invention comprises: an invoice data acquisition unit that acquires invoice data from a system that holds the invoice data; a payment screen request receiving unit that receives a request for a payment screen for making a payment of an invoice by a cashless payment means from a buyer's terminal, the request including specific information for identifying the invoice data; a payment screen display unit that displays the payment screen on the buyer's terminal in response to the request, identifies invoice data based on the identification information, and displays invoice information extracted from the identified invoice data on the payment screen in advance; a payment execution request receiving unit that receives a request to execute a payment using a cashless payment method from the buyer's terminal that has displayed the payment screen; Includes.

[0024] An information processing program according to an eleventh aspect of the present invention comprises: acquiring invoice data from a system that holds the invoice data; receiving a request for a payment screen for paying an invoice with a cashless payment method from a buyer's terminal, the request including specific information for identifying invoice data; a step of displaying the settlement screen on the buyer's terminal in response to the request, the step of identifying invoice data based on the identification information, and displaying invoice information extracted from the identified invoice data on the settlement screen in advance; receiving a request to make a payment using a cashless payment method from the buyer's terminal that has displayed the payment screen; to be executed by the computer. Effect of the Invention

[0025] According to the present invention, when a buyer pays an invoice using a cashless payment method, the burden of inputting invoice information can be reduced and input errors can be prevented. [Brief description of the drawings]

[0026] [Figure 1] FIG. 1 is a diagram showing an overall configuration of an information processing system according to an embodiment. [Diagram 2] FIG. 2 is a diagram showing a schematic configuration of a payment agent system. [Diagram 3] FIG. 3 is a diagram for explaining an example of the operation of the payment agent system. [Figure 4] FIG. 4 is a diagram for explaining an example of the operation of the payment agent system. [Diagram 5] FIG. 5 is a table showing an example of invoice information included in the invoice data. [Figure 6] FIG. 6 is a diagram showing an example of a registration screen displayed on a buyer's terminal. [Figure 7] FIG. 7 is a diagram showing an example of a payment screen displayed on the buyer's terminal. [Figure 8] FIG. 8 is a diagram showing an example of a payment screen displayed on the buyer's terminal. [Figure 9] FIG. 9 is a diagram showing an example of a notification screen displayed on the buyer's terminal. [Figure 10] FIG. 10 is a diagram showing an example of a My Page displayed on a supplier's terminal. [Figure 11] FIG. 11 is a diagram showing an example of a My Page displayed on a supplier's terminal. [Figure 12] FIG. 12 is a diagram showing an example of a My Page displayed on the supplier's terminal. [Figure 13] FIG. 13 is a diagram showing an example of a My Page displayed on a buyer's terminal. [Figure 14] FIG. 14 is a diagram showing an example of a My Page displayed on a buyer's terminal. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings. In the following description and the drawings used in the following description, the same reference numerals are used for parts that can be configured identically, and duplicated descriptions will be omitted.

[0028] In the following explanation, a credit card will be used as an example of a "cashless payment method", but this is not limited to this, and it may be, for example, another post-payment payment method such as BNPL (Buy Now Pay Later), an advance payment method such as a prepaid card, or an instant payment method such as a debit card.

[0029] In addition, in the following explanation, the "system that holds invoice data" will be described as an example of the system of an invoice issuing agent (also called an invoice issuing vendor) that stands between a seller company (also called a supplier) and a buyer company (also called a buyer), but this is not limited to this and may be, for example, the system of a Peppol certified business (also called a Peppol service provider) or a supplier's system.

[0030] (Device Configuration) FIG. 1 is a diagram showing the overall configuration of an information processing system 1 according to an embodiment. As shown in FIG. 1, the information processing system 1 has a payment agency system 2, an invoice issuing agency system 3 (a system that holds invoice data), a buyer terminal 4, a supplier terminal 5, an acquirer system 6, and an issuer system 7. Each system and terminal 2-7 are connected to each other so as to be able to communicate with each other via a network such as the Internet. The network may be either a wired line or a wireless line, and the type and form of the line are not important. At least a part of each system and terminal 2-7 is realized by a computer.

[0031] The following describes the general data flow in information processing system 1. First, when a supplier entrusts an invoice issuing agent with invoice issuance operations, invoice data is sent from the supplier's terminal 5 to invoice issuing agent system 3 and stored therein. Then, when a buyer receives an invoice from an invoice issuing vendor and views it, the invoice data is sent from invoice issuing agent system 3 to the buyer's terminal 4 and displayed therein. In this embodiment, the invoice data is transferred from invoice issuing agent system 3 to payment agent system 2 and stored therein.

[0032] When a buyer uses a payment service provider to make a payment to a supplier by credit card (cashless payment method), a payment screen is sent from the payment service provider system 2 to the buyer's terminal 4 and displayed. After the buyer confirms and inputs the invoice information on the payment screen, the buyer performs an operation to execute the payment, and a request to execute the payment is sent from the buyer's terminal 4 to the payment service provider system 2, and an authorization process is executed between the payment service provider system 2 and the acquirer system 6. The payment service provider system 2 then notifies the buyer's terminal 4 that the credit card payment has been completed, and the payment service provider system 2 passes the card payment result to the invoice issuing service provider system 3.

[0033] After that, sales processing is carried out between the payment agent system 2 and the acquirer system 6, and the payment agent transfers the invoice amount to the supplier. The acquirer also transfers the invoice card payment amount to the payment agent, and the invoice card payment amount is claimed / paid between the issuer and the buyer.

[0034] Next, a detailed description will be given of the payment agent system 2. FIG.

[0035] 2, the payment service provider system 2 has a communication unit 21, a control unit 22, and a storage unit 23. The units 21 to 23 are connected to each other via a bus or a network so as to be able to communicate with each other.

[0036] Of these, the communication unit 21 is a communication interface between the payment service provider system 2 and an external network. The communication unit 21 transmits and receives information between the payment service provider system 2 and other systems and terminals 3 to 6 via an external network such as the Internet.

[0037] The storage unit 23 is a non-volatile data storage such as a flash memory or a hard disk. The storage unit 23 stores various data handled by the control unit 22. For example, the storage unit 23 includes an invoice data database 23a, a buyer information database 23b, and a supplier information database 23c.

[0038] The invoice data database 23a stores a plurality of invoice data acquired from the invoice issuing agent system 3. FIG. 5 is a table showing an example of invoice information included in the invoice data. As shown in FIG. 5, the invoice information included in the invoice data may include basic invoice information, supplier (transfer destination) account information, and buyer transfer information. Of these, the basic invoice information may include an invoice ID (specific information) for uniquely identifying the invoice data, an invoice number, an invoice amount, a transfer due date, a supplier ID, and a buyer ID. The transfer destination account information may include a financial institution code, a branch code, a financial institution name, a branch name, an account type, an account number, and an account holder. The buyer transfer information may include a transfer holder's name.

[0039] In the invoice data database 23a, for each invoice data, the payment history of the invoice amount by the buyer using a credit card and / or the transfer history of the invoice amount to the supplier's (transfer destination) account may be stored in association with the invoice data.

[0040] In the buyer information database 23b, corporate information of multiple buyers is stored in association with a buyer ID for uniquely identifying the buyer. For example, the corporate information of a buyer may include a company name, a kana version of the company name, a business form (corporation / sole proprietor), a corporate number, an industry type, a postal code, a prefecture, and an address (such as a city, ward, town, or village level). The corporate information of a buyer may be stored in the buyer information database 23b by the payment agent system 2 acquiring the information in advance as linked data from the invoice issuing agent system 3, or the buyer may enter the information himself / herself on a registration screen when using the payment agent system 2 for the first time and register for use, thereby storing the information in the buyer information database 23b.

[0041] In the supplier information database 23c, the company information and account information of a plurality of suppliers are stored in association with a supplier ID for uniquely identifying the supplier. For example, the company information of the supplier may include the company name, the company name in kana, the business form (corporation / sole proprietor), the corporation number, the type of business, the postal code, the prefecture, and the address (such as below city, ward, town, village, etc.). The account information may include the financial institution code, the branch code, the financial institution name, the branch name, the account type, the account number, and the account holder. The company information and account information of the buyer may be stored in the supplier information database 23c by the payment agent system 2 acquiring the information in advance as linked data from the invoice issuing agent system 3, or may be stored in the supplier information database 23c by the supplier himself entering the information on a registration screen and registering for use when using the payment agent system 2 for the first time.

[0042] In addition, the memory unit 23 does not necessarily have to be physically located within the payment processing service provider system 2, and part or all of the memory unit 23 may be located within another device (e.g., cloud storage) that is communicatively connected to the payment processing service provider system 2 via an external network.

[0043] 2, the control unit 22 has an invoice data acquisition unit 22a, a pre-screening unit 22a2, a payment screen request receiving unit 22b, a payment screen display unit 22c, a payment execution request receiving unit 22d, a payment completion notifying unit 22e, a supplier's MyPage display unit 22f, a reconciliation data sending unit 22g, and a buyer's MyPage display unit 22h. Each of these units 22a to 22h may be realized by a processor in the payment agent system 2 executing a predetermined program, or may be implemented in hardware.

[0044] The invoice data acquisition unit 22a periodically accesses the invoice issuing agent system 3 to acquire invoice data. The invoice data acquired by the invoice data acquisition unit 22a is stored in the invoice data database 23a.

[0045] The preliminary screening unit 22a2 extracts invoice information (see FIG. 5) from the invoice data acquired by the invoice data acquisition unit 22a, and performs preliminary screening (for example, checking the existence of a corporation or the presence or absence of a criminal case) on the supplier and / or buyer identified by the extracted invoice information. For example, the preliminary screening unit 22a2 may use a Web-API provided by the National Tax Agency's Corporation Number System to check whether the identified supplier and / or buyer exists as a corporation. Also, for example, with reference to FIG. 1, the preliminary screening unit 22a2 may use an external corporation confirmation system 8 (for example, Nikkei Risk & Compliance provided by Nihon Keizai Shimbun, Inc.) to check whether the identified supplier and / or buyer is an antisocial force (anti-social force) or whether the identified supplier and / or buyer is a criminal case. The preliminary screening unit 22a2 performs preliminary screening of the supplier and / or buyer (before the start of trading) using invoice data obtained in advance, thereby preventing money laundering and trading with antisocial forces. The results of the pre-screening of suppliers and / or buyers by the pre-screening unit 22a2 are stored in the supplier information database 33c and / or the buyer information database 33b.

[0046] The payment screen request receiving unit 22b receives a payment screen request (hereinafter, also referred to as a payment screen request) from the buyer's terminal 4 for making payment of an invoice by credit card. For example, when a buyer displays and views invoice data on the buyer's terminal 4 and then operates (tap or click) a "Pay by card" button displayed on the screen, a payment screen request may be sent from the buyer's terminal 4 to the payment agent system 2, and the payment screen request may be received by the payment screen request receiving unit 22b. Alternatively, for example, when a buyer photographs a two-dimensional code printed on a paper invoice with the camera of the terminal 4, a payment screen request may be sent from the buyer's terminal 4 to the payment agent system 2, and the payment screen request may be received by the payment screen request receiving unit 22b. The payment screen request includes specific information for uniquely identifying the invoice data. In addition to the specific information, the payment screen request may further include a supplier ID for uniquely identifying the supplier, or may further include a buyer ID for uniquely identifying the buyer.

[0047] In response to the payment screen request received by the payment screen request receiving unit 22b, the payment screen display unit 22c transmits a payment screen (see Figs. 7 and 8) to the buyer terminal 4 for display. At this time, the payment screen display unit 22c refers to the invoice data database 23a based on the identification information included in the payment screen request to identify the corresponding invoice data. Then, the payment screen display unit 22c extracts invoice information (see Fig. 5) from the identified invoice data, and confirms the preliminary screening results by the preliminary screening unit 22a2 for the supplier and buyer identified by the extracted invoice information.

[0048] If the preliminary screening by the preliminary screening unit 22a2 has revealed in advance that there is a problem with either or both of the supplier and the buyer, the settlement screen display unit 22c transmits an error screen, instead of the settlement screen, to the buyer's terminal 4 and displays it, indicating that the procedure cannot be continued. On the other hand, if the preliminary screening by the preliminary screening unit 22a2 has revealed in advance that there is no problem with either the supplier or the buyer, the settlement screen display unit 22c extracts invoice information (see FIG. 5) from the identified invoice data and displays the extracted invoice information in advance on the settlement screen. For example, in the example shown in FIG. 7, the settlement screen display unit 22c refers to the supplier information database based on the supplier ID included in the extracted invoice information to identify the supplier's company name, and displays the identified company name in advance in the input field for the payee company name (invoice issuing business entity) on the settlement screen. In addition, the settlement screen display unit 22c displays in advance the invoice number, invoice amount, deadline (transfer due date), and transfer account information included in the extracted invoice information in the respective input fields on the settlement screen. This reduces the input burden on the buyer and prevents input errors when the buyer inputs invoice information into the input fields on the payment screen.

[0049] The payment screen display unit 22c may display the invoice amount extracted from the identified invoice data plus a specified fee (for example, 3% of the invoice amount) as the credit card invoice amount on the payment screen (see Figure 8).

[0050] The payment execution request receiving unit 22d receives a request to execute a payment by credit card (hereinafter also referred to as a payment execution request) from the buyer's terminal 4 that has displayed the payment screen. For example, when the buyer confirms and inputs the invoice information and credit card information on the buyer's terminal 4 and then operates (tap or click) the "Pay" button displayed on the confirmation screen, a payment execution request is sent from the buyer's terminal 4 to the payment agent system 2, and the payment execution request receiving unit 22d may receive the payment execution request.

[0051] When the payment execution request receiving unit 22d receives the payment execution request, authorization processing is executed between the payment agent system 2 and the acquirer system 6. Then, when the authorization processing is normally completed, information notifying that the credit card payment has been completed is sent and output from the payment agent system 2 to the buyer's terminal 4 (see FIG. 9), and the card payment result is passed from the payment agent system 2 to the invoice issuing agent system 3.

[0052] After the payment screen display unit 22c identifies bill data based on the identification information included in the payment screen request, the payment completion notification unit 22e checks the credit card payment history for the identified bill data by referring to the bill data database 23a. If the bill data has been paid, the payment completion notification unit 22e transmits information (for example, an alert) notifying the buyer that payment has been made to the buyer's terminal 4 and causes it to be output. In this way, if the bill data that the buyer is attempting to pay by credit card has already been paid, the buyer is notified that the bill data has been paid, thereby preventing duplicate credit card payments.

[0053] The supplier-oriented MyPage display unit 22f receives a request for the supplier-oriented MyPage (hereinafter, the first request) from the supplier's terminal 5. The first request may include identification information (supplier ID) for identifying the supplier and search conditions for identifying one or more invoice data. For example, when a supplier operates the supplier's terminal 5 to log in to the website of the payment service provider system 2, the supplier's terminal 5 displays the supplier-oriented MyPage (start page) with reference to FIG. 10. Then, when the supplier inputs search conditions (in the illustrated example, the transfer date and / or the buyer's company name, and whether or not to display only transferred items) in the search condition input field in the start page, the first request including the input search conditions and the supplier ID is transmitted from the supplier's terminal 5 to the payment service provider system 2, and the first request may be received by the supplier-oriented MyPage display unit 22f.

[0054] When the supplier-oriented my-page display unit 22f receives a first request from the supplier's terminal 5, it responds to the first request by transmitting a supplier-oriented my-page (search result summary page) to the supplier's terminal 5 to display it. At this time, the supplier-oriented my-page display unit 22f refers to the invoice data database 23a based on the supplier ID included in the first request to identify the supplier's invoice data, and displays a list of the identified supplier's invoice data that satisfies the search conditions included in the first request on the search result summary page (see FIG. 11). This allows the supplier to easily search for and check the invoice data that he or she wishes to check, even when a large number of invoices have been issued by the supplier.

[0055] Furthermore, the supplier-oriented mypage display unit 22f receives information for selecting one piece of invoice data from the list of invoice data displayed on the search result summary page from the supplier's terminal 5 that has displayed the search result summary page. For example, when a supplier operates the supplier's terminal 5 to select (tap or click) one piece of invoice data, information for selecting the one piece of invoice data may be transmitted from the supplier's terminal 5 to the payment agent system 2, and the supplier-oriented mypage display unit 22f may receive the information for selecting the one piece of invoice data.

[0056] When the supplier-oriented my-page display unit 22f receives information for selecting one piece of invoice data from the supplier's terminal 5, it checks the transfer status of the selected invoice data by referring to the invoice data database 23a. Then, the supplier-oriented my-page display unit 22f transmits the confirmed transfer status to the supplier's terminal 5 and displays it on the supplier-oriented my-page (search result details page) (see FIG. 12). This allows the supplier to easily check the transfer status of his / her own invoice data. If the selected invoice data has already been transferred, the supplier-oriented my-page display unit 22f may refer to FIG. 12 and display a download button for reconciliation data, which will be described later, on the search result details page.

[0057] The reconciliation data transmission unit 22g receives a request for reconciliation data for the transferred invoice data from the supplier's terminal 5 that has displayed the supplier's personal page. For example, when the supplier operates (tap or click) the download button for reconciliation data displayed on the search result summary page using the supplier's terminal 5, a request for reconciliation data is transmitted from the supplier's terminal 5 to the payment agent system 2, and the request for reconciliation data is received by the reconciliation data transmission unit 22g. The reconciliation data is data that can be used when performing payment reconciliation processing on the supplier's accounting system.

[0058] When the reconciliation data transmission unit 22g receives a request for reconciliation data from the supplier's terminal 5, in response to the request, it transmits reconciliation data for the invoice data for which payment has already been made to the supplier's terminal 5. By using the downloaded reconciliation data, the supplier can reduce the workload of reconciling payments on the supplier's accounting system.

[0059] The buyer's My Page display unit 22h receives a request for a buyer's My Page (hereinafter, a second request) from the buyer's terminal 4. The second request may include identification information (buyer ID) for identifying the buyer and search conditions for identifying one or more invoice data. For example, when a buyer operates the buyer's terminal 4 to log in to the website of the payment agent system 2, the buyer's My Page (start page) is displayed on the buyer's terminal 4 with reference to FIG. 13. Then, when the buyer inputs search conditions (in the illustrated example, the transfer date and / or the buyer's company name, and whether or not to display only transferred items) in the search condition input field on the start page, a second request including the input search conditions and the buyer ID is sent from the buyer's terminal 4 to the payment agent system 2, and the second request may be received by the buyer's My Page display unit 22h.

[0060] When the buyer-oriented my-page display unit 22h receives the second request from the buyer terminal 4, it responds to the second request by transmitting a buyer-oriented my-page (search result summary page) to the buyer terminal 4 and displaying it. At this time, the buyer-oriented my-page display unit 22h identifies the buyer's invoice data by referring to the invoice data database 23a based on the buyer ID included in the second request, and displays a list of the identified buyer's invoice data that satisfies the search conditions included in the second request on the search result summary page (see FIG. 14). This allows the buyer to easily search for and check the invoice data he or she wishes to check, even if a large number of invoices have been issued to the buyer.

[0061] (Example of operation) Next, an example of the operation of the payment service provider system 2 will be described with reference to Figures 3 and 4. Figures 3 and 4 are diagrams for explaining an example of the operation of the payment service provider system 2.

[0062] As shown in FIG. 3, first, the invoice data acquisition unit 22a periodically accesses the invoice issuing agent system 3 to acquire multiple invoice data, and stores the data in the invoice data database 23a (step S10).

[0063] Next, the pre-screening unit 22a2 extracts invoice information (see Figure 5) from the billing data acquired by the invoice data acquisition unit 22a, conducts a pre-screening (for example, confirming the existence of a corporation or whether or not there are any criminal cases) on the supplier and / or buyer identified by the extracted invoice information, and stores the pre-screening results in the supplier information database 33c and / or the buyer information database 33b (step S101).

[0064] Next, when the buyer operates the buyer terminal 4 to make a payment to the supplier by credit card, a payment screen request is sent from the buyer terminal 4 to the payment agent system 2, and the payment screen request receiving unit 22b receives the payment screen request from the buyer terminal 4 (step S11). The payment screen request includes specific information for uniquely identifying the invoice data. The payment screen request may include the supplier ID and / or buyer ID in addition to the specific information.

[0065] When the payment screen request receiving unit 22b receives the payment screen request, the payment screen display unit 22c refers to the invoice data database 23a based on the identification information included in the payment screen request to identify the corresponding invoice data, extracts invoice information (see FIG. 5) from the identified invoice data, and checks the results of the pre-screening by the pre-screening unit 22a2 for the supplier and the buyer identified by the extracted invoice information. If the pre-screening by the pre-screening unit 22a2 determines in advance that there is a problem with one or both of the supplier and the buyer, the payment screen display unit 22c transmits and displays an error screen to the buyer's terminal 4 to the effect that the procedure cannot be continued. On the other hand, if the pre-screening by the pre-screening unit 22a2 determines in advance that there is no problem with either the supplier or the buyer, the payment screen display unit 22c refers to the buyer information database 23b and determines whether or not the buyer is a first-time buyer using the payment agent system 2 (step S12). If it is the first time the user uses the service (step S12: YES), the payment screen display unit 22c refers to Fig. 6 and transmits the company information registration screen to the buyer terminal 4 to display it (step S13). At this time, if the buyer's company information has been previously acquired as linked data from the invoice issuing agent system 3 and stored in the buyer information database 23b, the payment screen display unit 22c may refer to the buyer information database 23b based on the buyer ID included in the payment screen request, extract the corresponding buyer's company information, and display the extracted company information in advance in each input field on the company information registration screen.

[0066] After the buyer confirms and inputs the company information, administrator information, and account information on the buyer terminal 4, the buyer operates (tap or click) the “Register” button displayed on the confirmation screen, and the payment screen display unit 22c stores the information input by the buyer in the buyer information database 23b.

[0067] Next, the payment screen display unit 22c refers to the invoice data database 23a based on the specific information included in the payment screen request to identify the corresponding invoice data, and the payment completion notification unit 22e checks the credit card payment history for the identified invoice data by referring to the invoice data database 23a (step S14). If the invoice data has been paid (step S14: YES), the payment completion notification unit 22e transmits information (e.g., an alert) notifying the buyer that the payment has been made to the buyer's terminal 4 and causes it to be output (step S15). As a result, if the invoice data that the buyer is attempting to pay by credit card has already been paid, the buyer is notified that the data has been paid, thereby preventing duplicate credit card payments.

[0068] On the other hand, if the payment has not been made (step S14: NO), the payment screen display unit 22c transmits the payment screen to the buyer's terminal 4 and displays it (step S16). At this time, the payment screen display unit 22c extracts the invoice information (see FIG. 5) from the specified invoice data and displays the extracted invoice information in advance on the payment screen (see FIG. 7). As shown in FIG. 7, the payment screen display unit 22c may display the extracted invoice information in advance in each input field on the payment screen, or may display it around the input field so that it can be referenced. This reduces the input burden on the buyer when the buyer inputs the invoice information in the input field on the payment screen and prevents input errors.

[0069] In step S16, the payment screen display unit 22c may add a predetermined fee (e.g., 3% of the billing amount) to the billing amount extracted from the identified bill data and display the sum as the credit card billing amount on the payment screen (see FIG. 8). If the buyer's credit card information is already stored in the buyer information database 23b, the payment screen display unit 22c may refer to the buyer information database 23b based on the buyer ID included in the payment screen request, extract the corresponding buyer's credit card information, and display the extracted credit card information in advance in the input field on the payment screen.

[0070] Next, the buyer confirms and inputs the invoice information and credit card information on the buyer's terminal 4, and then operates (tap or click) the "Pay" button displayed on the confirmation screen. This causes a payment execution request to be sent from the buyer's terminal 4 to the payment agent system 2, and the payment execution request receiving unit 22d receives the payment execution request from the buyer's terminal 4 that displayed the payment screen (step S17).

[0071] Then, when the payment execution request receiving unit 22d receives the payment execution request, authorization processing is executed between the payment agency system 2 and the acquirer system 6 (step S18), and when the authorization processing is normally completed, information notifying that the credit card payment has been completed is sent and output from the payment agency system 2 to the buyer's terminal 4 (see FIG. 9), and the card payment result is passed from the payment agency system 2 to the invoice issuing agency system 3. After that, sales processing is executed between the payment agency system 2 and the acquirer system 6, and transfer processing of the invoice amount to the payee (supplier) account is executed between the payment agency system 2 and a financial institution system (not shown) (step S19).

[0072] Next, referring to Figure 4, the supplier operates the supplier's terminal 5 to log in to the website of the payment agent system 2, and as shown in Figure 10, enters search conditions (in the illustrated example, the transfer date and / or the buyer company name, and whether or not to display only transferred items) in the search condition input field in the supplier's my page (start page), and a first request including the entered search conditions and supplier ID is sent from the supplier's terminal 5 to the payment agent system 2, and the supplier's my page display unit 22f receives the first request from the supplier's terminal 5 (step S20).

[0073] Next, in response to the first request received from the supplier's terminal 5, the supplier's mypage display unit 22f transmits the supplier's mypage (search result summary page) to the supplier's terminal 5 and displays it (step S21). At this time, the supplier's mypage display unit 22f refers to the invoice data database 23a based on the supplier ID included in the first request to identify the supplier's invoice data, and displays a list of the identified supplier's invoice data that satisfies the search conditions included in the first request on the search result summary page (see FIG. 11). This allows the supplier to easily search for and check the invoice data that he or she wants to check, even if a large number of invoices have been issued by the supplier.

[0074] In step S21, when the supplier operates the supplier's terminal 5 to select (tap or click) one piece of invoice data from the list of invoice data displayed on the search result summary page, the supplier's My Page display unit 22f checks the transfer status of the selected invoice data by referring to the invoice data database 23a, and displays the confirmed transfer status on the supplier's My Page (search result details page) (see FIG. 12). This allows the supplier to easily check the transfer status of his or her own invoice data.

[0075] Next, when the supplier operates (tap or click) the download button for reconciliation data displayed on the search result summary page using the supplier's terminal 5, a request for reconciliation data is sent from the supplier's terminal 5 to the payment agent system 2, and the reconciliation data sending unit 22g receives the request for reconciliation data from the supplier's terminal 5 (step S22).

[0076] Then, in response to a request for reconciliation data from the supplier's terminal 5, the reconciliation data transmission unit 22g transmits the reconciliation data for the transferred invoice data to the supplier's terminal 5 (step S23). By using the downloaded reconciliation data, the supplier can reduce the workload of reconciling payments on the supplier's accounting system.

[0077] Next, the buyer operates the buyer terminal 4 to log in to the website of the payment agent system 2 and, as shown in FIG. 13, enters search conditions (in the illustrated example, the transfer date and / or supplier company name, and whether or not to display only transferred items) in the search condition input fields in the buyer's personal page (start page). A second request including the entered search conditions and buyer ID is then sent from the buyer terminal 4 to the payment agent system 2, and the buyer's personal page display unit 22h receives the second request from the buyer terminal 4 (step S24).

[0078] Next, in response to the second request received from the buyer's terminal 4, the buyer's my page display unit 22h transmits the buyer's my page (search result summary page) to the buyer's terminal 4 and displays it (step S25). At this time, the buyer's my page display unit 22h identifies the buyer's invoice data by referring to the invoice data database 23a based on the buyer ID included in the second request, and displays a list of the identified buyer's invoice data that satisfies the search conditions included in the second request on the search result summary page (see FIG. 14). This allows the buyer to easily search for and check the invoice data he or she wants to check, even if a large number of invoices have been issued to the buyer.

[0079] According to the embodiment described above, the payment agent system 2 obtains invoice data in advance from the invoice issuing agent system 3 (a system that holds invoice data), and when the buyer pays the invoice by credit card (a cashless payment method), the payment agent system 2 displays in advance on the payment screen invoice information extracted from the invoice data obtained in advance, thereby reducing the burden on the buyer of inputting invoice information and preventing input errors.

[0080] Furthermore, according to this embodiment, if the invoice data that is to be paid by credit card (cashless payment method) has already been paid, the payment agent system 2 notifies the buyer that the invoice data has already been paid, thereby preventing duplicate payments by credit card (cashless payment method).

[0081] Furthermore, according to this embodiment, when the payment agency system 2 receives a request including search conditions from a supplier's terminal, it displays a list of the supplier's invoice data that satisfies the search conditions on the supplier's personal page. Therefore, even if a supplier has issued a large number of invoices, the supplier can easily search for and view the invoice data they wish to view.

[0082] Furthermore, according to this embodiment, when the payment agency system 2 receives a request for reconciliation data from a supplier's terminal that has displayed their personal page, it responds to the request by sending reconciliation data for the invoice data that has already been transferred to the supplier's terminal, thereby reducing the workload of the supplier in reconciling payments.

[0083] The above description of the embodiment and the disclosure of the drawings are merely examples for explaining the invention described in the claims, and the invention described in the claims is not limited by the description of the embodiment or the disclosure of the drawings. The components of the above embodiment can be combined in any manner without departing from the spirit of the invention.

[0084] In addition, the payment processing agency system 2 in the above-mentioned embodiment may be composed of one or more computers, but the program for realizing the payment processing agency system 2 in one or more computers and the computer-readable recording medium on which the program is recorded non-transitory are also protected by this case. [Explanation of symbols]

[0085] 1. Information Processing Systems 2 Payment processing company system (information processing device) 21 Communications Department 22 Control section 22a Invoice Data Acquisition Section 22a2 Preliminary Examination Department 22b Payment screen request receiving section 22c Payment screen display section 22d Payment execution request receiving section 22e Paid Notice Section 22F Supplier My Page Display Area 22g Data transmission unit for reconciliation 22h My Page display section for buyers 23 Memory section 23a Invoice data database 23b Buyer information database 23c Supplier Information Database 3. Invoice issuing agency system 4. Buyer's terminal 5. Supplier's terminal 6 Acquirer System 7 Issuer System

Claims

1. 1. A computer-implemented information processing method, comprising: acquiring invoice data from a system that holds the invoice data; receiving a request for a payment screen for paying an invoice with a cashless payment method from a buyer's terminal, the request including specific information for identifying invoice data; a step of displaying the settlement screen on the terminal of the buyer in response to the request, the step of identifying invoice data based on the identification information, and displaying invoice information extracted from the identified invoice data on the settlement screen in advance; receiving a request to make a payment using a cashless payment method from the buyer's terminal that has displayed the payment screen; An information processing method comprising:

2. 2. The information processing method according to claim 1, further comprising the step of: after identifying invoice data based on said identification information, checking the payment history of the identified invoice data via a cashless payment method; and, if payment has been made, outputting information to said buyer's terminal notifying said buyer that payment has been made.

3. 2. The information processing method according to claim 1, further comprising a step of conducting a pre-screening of suppliers and / or buyers identified by invoice information extracted from the acquired invoice data after acquiring the invoice data from a system that holds the invoice data and before receiving a request for the payment screen from the buyer's terminal.

4. 4. The information processing method according to claim 1, wherein the invoice information includes at least one of an invoice number, an invoice amount, a transfer date, and transfer account information.

5. An information processing method according to any one of claims 1 to 3, wherein the step of displaying the payment screen includes a step of displaying on the payment screen an amount obtained by adding a predetermined fee to the invoice amount extracted from the identified invoice data as the cashless payment method invoice amount.

6. receiving a request for a supplier's personal page from a supplier's terminal, the request including identification information for identifying the supplier and search conditions for identifying one or more invoice data; a step of displaying the My Page on the terminal of the supplier in response to the request, identifying the supplier based on the identification information, and displaying on the My Page a list of invoice data of the identified supplier that satisfies the search conditions; The information processing method according to any one of claims 1 to 3, further comprising:

7. receiving information for selecting one invoice data from the list of invoice data from the terminal of the supplier that has displayed the My Page; A step of confirming the transfer status of the selected invoice data and displaying it on the My Page; The information processing method according to claim 6 , further comprising:

8. receiving a request for reconciliation data for the invoice data that has already been transferred from the terminal of the supplier that has displayed the My Page; transmitting the reconciliation data to the supplier terminal in response to the request; The information processing method according to claim 6 , further comprising:

9. A step of receiving a request for a buyer's personal page from a buyer's terminal, the request including identification information for identifying the buyer and search conditions for identifying one or more invoice data; a step of displaying the My Page on the buyer's terminal in response to the request, the step of identifying a buyer based on the identification information, and displaying on the My Page a list of invoice data of the identified buyer that satisfies the search conditions; The information processing method according to any one of claims 1 to 3, further comprising:

10. an invoice data acquisition unit that acquires invoice data from a system that holds the invoice data; a payment screen request receiving unit that receives a request for a payment screen for making a payment of an invoice by a cashless payment means from a buyer's terminal, the request including specific information for identifying the invoice data; a payment screen display unit that displays the payment screen on the buyer's terminal in response to the request, identifies invoice data based on the identification information, and displays invoice information extracted from the identified invoice data on the payment screen in advance; a payment execution request receiving unit that receives a request to execute a payment using a cashless payment method from the buyer's terminal that has displayed the payment screen; An information processing device comprising:

11. acquiring invoice data from a system that holds the invoice data; receiving a request for a payment screen for paying an invoice with a cashless payment method from a buyer's terminal, the request including specific information for identifying invoice data; a step of displaying the settlement screen on the terminal of the buyer in response to the request, the step of identifying invoice data based on the identification information, and displaying invoice information extracted from the identified invoice data on the settlement screen in advance; receiving a request to make a payment using a cashless payment method from the buyer's terminal that has displayed the payment screen; An information processing program that causes a computer to execute the above.

Images