Mediation server, mediation method, and program

Abstract

To facilitate the use of BPSP which is credit card payment using a payment intermediary, as a method of paying bills.SOLUTION: A mediation server includes: a payment intermediary service unit which generates settlement candidate data, which is a candidate to be settled in a payment intermediary server, based on bill basic data received from a supplier server and indicating the contents of a bill for a buyer who is a payer, and transmits the generated settlement candidate data to the payment intermediary server; and a buyer service unit which generates bill data which is a bill for the buyer based on the bill basic data, and transmits the generated bill data to a buyer terminal. When the buyer selects BPSP which is credit card payment using a payment intermediary, as a payment method for the bill data, the payment intermediary service unit transmits, to the payment intermediary server, bill key information which is identification information of the bill data for which BPSP has been selected.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to an intermediation server, an intermediation method, and a program. [Background technology]

[0002] Efforts are underway to use corporate cards in B2B (business-to-business) payments. In particular, there is growing demand for corporate cards that link expense settlement systems with credit card usage statement data. For example, Patent Document 1 discloses technology for inter-business payment agency that connects a paying company with an inter-business payment agency system to reduce the risk of information leakage when exchanging information such as requesting payment agency, requesting credit card authorization, and obtaining the results of authorization. [Prior art documents] [Patent documents]

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

[0004] When credit card payment through a payment agent (BPSP, Business Payments Solution Provider) is selected, the payment agent will carry out credit card payment to the payer (buyer) and also make payment to the payee (supplier).

[0005] When credit card payment is made through a payment agency, the payment agency verifies the buyer's credit. Therefore, the supplier does not need to investigate the buyer's credit. In addition, once credit card payment is made through a payment agency, payment to the supplier is completed, so the supplier does not bear the risk of bad debt and does not need to send a reminder. For this reason, suppliers often want buyers to actively use credit card payment through a payment agency.

[0006] The present invention has been made in consideration of the above circumstances, and its purpose is to provide an intermediary server, an intermediary method, and a program that make it easier to use BPSP, which is credit card payment through a settlement agency, as a payment method for billing. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems, the intermediary server of the present invention comprises a payment agency correspondence unit that generates payment candidate data that is a candidate for payment to be executed at the payment agency server based on billing basic data notified from the supplier server, which indicates the content of the bill to the buyer, who is the payer, and transmits the generated payment candidate data to the payment agency server, and a buyer correspondence unit that generates invoice data that is an invoice for the buyer based on the billing basic data and transmits the generated invoice data to a buyer terminal, and when BPSP, which is a credit card payment through a payment agency, is selected by the buyer as the payment method for the invoice data, the payment agency correspondence unit transmits billing key information, which is identification information of the invoice data for which BPSP was selected, to the payment agency server.

[0008] In order to solve the above-mentioned problems, the intermediation method of the present invention is an intermediation method executed by a computer that is an intermediation server, in which a payment agency correspondence unit generates payment candidate data that is a candidate for payment to be executed at the payment agency server based on billing basic data notified from a supplier server, the billing basic data indicating the contents of the bill to the buyer who is the payer, and transmits the generated payment candidate data to the payment agency server, a buyer correspondence unit generates invoice data that is an invoice for the buyer based on the billing basic data, and transmits the generated invoice data to a buyer terminal, and when BPSP, which is a credit card payment via payment agency, is selected by the buyer as the payment method for the invoice data, the payment agency correspondence unit transmits billing key information, which is identification information of the invoice data for which BPSP was selected, to the payment agency server.

[0009] In order to solve the above-mentioned problems, the program of the present invention causes a computer which is an intermediary server to generate payment candidate data which is a candidate for settlement to be executed at a payment agency server based on billing basic data notified from a supplier server, which indicates the contents of the bill to the buyer who is the payer, to transmit the generated payment candidate data to the payment agency server, generate invoice data which is an invoice for the buyer based on the billing basic data, to transmit the generated invoice data to a buyer terminal, and when BPSP, which is a credit card payment via payment agency, is selected by the buyer as the payment method for the invoice data, transmit billing key information which is identification information of the invoice data for which BPSP was selected to the payment agency server. Effect of the Invention

[0010] According to the present invention, it is possible to facilitate the use of BPSP, which is a credit card payment through a settlement agent, as a payment method for billing. [Brief description of the drawings]

[0011] [Figure 1]1 is a block diagram showing a configuration example of a payment system 1 according to an embodiment. [Diagram 2] 1 is a block diagram showing an example of the configuration of an intermediation server 10 according to an embodiment. [Diagram 3] FIG. 2 is a diagram showing an example of information stored in supplier information 120 according to the embodiment. [Figure 4] FIG. 2 is a diagram showing an example of information stored in buyer information 121 according to the embodiment. [Diagram 5] 10 is a diagram showing an example of information stored in billing basic data 122 according to the embodiment. FIG. [Figure 6] FIG. 11 is a diagram showing an example of information stored in invoice data 123 according to the embodiment. [Figure 7] FIG. 11 is a diagram showing an example of information stored in payment candidate data 124 according to the embodiment. [Figure 8] FIG. 2 is a diagram showing an example of a screen displayed on a buyer terminal 30 according to the embodiment. [Figure 9] FIG. 2 is a diagram showing an example of a screen displayed on a buyer terminal 30 according to the embodiment. [Figure 10] FIG. 2 is a diagram showing an example of a screen displayed on a buyer terminal 30 according to the embodiment. [Figure 11] FIG. 2 is a diagram showing an example of a screen displayed on a buyer terminal 30 according to the embodiment. [Figure 12] 1 is a sequence diagram showing the flow of processing performed by payment system 1 of an embodiment. [Figure 13] 1 is a sequence diagram showing the flow of processing performed by payment system 1 of an embodiment. [Figure 14] FIG. 13 is a diagram showing an example of a screen displayed on a buyer terminal 30 in a modified example of the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] An embodiment of the present invention will be described below with reference to the drawings. In the following description, a business entity corresponding to a payee may be referred to as a "supplier." A business entity corresponding to a payer may be referred to as a "buyer." A business entity that executes credit card payments through a payment agent may be referred to as a "payment agent."

[0013] In the following explanation, credit card payment through a payment agent will be referred to as "BPSP" or simply as "card payment." When BPSP is selected as the payment method for the invoice, the payment agent processes the credit card payment for the buyer and also makes the payment to the supplier. After the BPSP is implemented, the buyer only needs to make payment to the payment service provider by the due date (for example, the following month) based on the credit card terms of use, so the actual due date for the invoice can be extended. Also, if there is a special offer that gives points according to the amount of credit card usage, the buyer can enjoy the special offer by using the credit card. In addition, when BPSP is executed, the payment agent will grant credit to the buyer, so the supplier does not need to investigate the buyer's credit. In addition, once BPSP is executed, payment to the supplier is completed, so the supplier does not bear the risk of bad debt and does not need to send a reminder. Generally, with normal invoices, payment is often made according to an arrangement such as closing at the end of the month and paying at the end of the following month. For this reason, it was necessary to wait up to about one month from the issuance of the invoice until the payment was completed. In contrast, when BPSP is executed, the invoice amount is deposited into the supplier's deposit account several days later, depending on the contract. Therefore, cash flow can be expected to improve compared to when invoices are paid on the due date.

[0014] In the following description, "invoice" refers to an electronic invoice (e.g., a PDF file).

[0015] (Configuration of payment system 1) 1 is a block diagram showing a configuration example of a payment system 1 according to an embodiment. The payment system 1 includes, for example, an intermediary server 10, a supplier server 20, a buyer terminal 30, a payment agent server 40, and a financial institution server 50.

[0016] The settlement system 1 is a system that generates an invoice for a buyer based on a request from a supplier, sends it to the buyer, and provides a service (called a settlement support service) that causes a settlement agent to execute BPSP when the buyer selects BPSP as a payment method for the invoice. For example, the settlement support service is provided via a site (a settlement support site) that corresponds to the settlement support service.

[0017] The supplier server 20 is a server device managed by the supplier. The supplier server 20 is communicably connected to the intermediation server 10. The supplier server 20 requests the intermediation server 10 to generate an invoice for the buyer. A supplier has account information on a site (payment support site) that supports the payment support service. For example, when an accounting staff member of the supplier operates the supplier server 20 to access the supplier's My Account on the payment support site and selects to request the generation of an invoice, an input form for requesting the generation of an invoice from the payment support site is displayed on the supplier server 20. The accounting staff member of the supplier visually checks the input form, enters the necessary information, and performs an operation to request the generation of an invoice. Then, information required for generating an invoice (information equivalent to billing basic data 122 described later) is transmitted from the supplier server 20 to the intermediary server 10. In this way, the supplier server 20 can request the intermediary server 10 to generate an invoice. For example, in the supplier's My Page on the payment support site, information related to invoices requested by the supplier is stored so that it can be referenced along with its attribute information. The attribute information is, for example, information indicating the billing content (details) of the invoice and progress such as the invoice sending status and the payment status of invoices that have already been sent. The supplier's accounting staff can grasp the invoice sending status and the payment status of invoices that have already been sent by accessing the supplier's My Page on the payment support site via the supplier server 20 or the like.

[0018] The buyer terminal 30 is a terminal device such as a personal computer or tablet terminal managed by the buyer. The buyer terminal 30 receives a notification that an invoice has been issued from the supplier to the buyer via the intermediary server 10. This notification is sent by the intermediary server 10 to a pre-registered destination, for example, the buyer's accounting department, using a communication tool such as e-mail or SNS. The buyer has account information on a site (payment support site) that supports the payment support service. For example, when an accountant of the buyer operates the buyer terminal 30 to access the buyer's My Account on the payment support site, a list of invoices issued to the buyer is displayed on the buyer terminal 30. The accountant of the buyer can visually check the list of invoices and confirm the contents of the invoices.

[0019] The payment agency server 40 is a server device managed by a payment agency. The payment agency may be a card issuing company or a company that has a contract with a card issuing company. The payment agency concludes a payment agency contract with each of the supplier and the buyer, and provides a payment agency service for payments between the supplier and the buyer. When the buyer selects BPSP as the payment method for the invoice from the supplier, the payment agency executes credit card settlement with the buyer and also makes a payment to the supplier.

[0020] The financial institution server 50 is a server device managed by a financial institution such as a bank. The financial institution server 50 is, for example, a server device of a financial institution in which a deposit account designated by a supplier for payment of an invoice is held. When the payment agent executes the BPSP, the financial institution server 50 deposits the money into the supplier's deposit account in response to a deposit request from the payment agent server 40. The financial institution server 50 may be a server device of a financial institution that holds a withdrawal account designated as the withdrawal destination of the settlement agency fee when the buyer uses the BPSP. After the settlement agency executes the BPSP, in response to a withdrawal request from the settlement agency server 40, when the withdrawal due date of the settlement agency fee arrives, the financial institution server 50 withdraws the settlement agency fee from the withdrawal account of the buyer and deposits it into the designated account of the settlement agency.

[0021] The intermediary server 10 mediates payments between the supplier and the buyer. For example, the intermediary server 10 stores an invoice generated for the buyer in a payment support site and makes it possible to view the invoice from the buyer terminal 30. In this case, the intermediary server 10 may provide an operation button for performing "card payment" on the invoice (see symbol D14 in FIG. 8). Whether or not to provide an operation button for "card payment" on the invoice may be set according to the supplier's wishes. For example, if the supplier indicates that they do not permit the buyer to make a payment using BPSP, the intermediary server 10 generates an invoice that does not have an operation button for "card payment." In this case, the buyer pays the invoice by a method other than BPSP, such as bank transfer. If the supplier indicates its intention to permit the buyer to make a payment using BPSP, the intermediary server 10 generates an invoice with a selectable operation button for "card payment." In this case, the buyer may pay the invoice using BPSP or by a method other than BPSP. When the supplier indicates that it is his intention to permit the buyer to make payments only using BPSP, the intermediary server 10 generates an invoice with only an operation button for making a "card payment". In this case, the buyer must make payments on the invoice using BPSP. For example, a supplier may indicate his intention to permit only payments using BPSP to a buyer who has just started trading with the supplier, for reasons such as the lack of trading history.

[0022] Furthermore, when generating an invoice, in preparation for the case where BPSP is selected as the payment method for the invoice, the intermediary server 10 generates specific information to be used by the payment agent server 40 to execute BPSP and transmits the information in advance to the payment agent server 40. The specific information to be used to execute BPSP here is information equivalent to the payment candidate data 124 described later, and includes, for example, a supplier ID as identification information for identifying the supplier, a buyer ID as identification information for identifying the buyer, a billing ID as identification information for identifying the invoice, the billing amount, the payment due date, and the like (see FIG. 7). By receiving specific information used to execute BPSP from intermediary server 10, payment agency server 40 can grasp in advance the billing details for which BPSP may be used, and can prepare for the possibility that BPSP will be executed in the future. When BPSP is selected as the payment method for the invoice generated for the buyer, the intermediary server 10 notifies the payment agent server 40 of billing key information that can identify the invoice for which BPSP has been selected as the payment method. The billing key information is sufficient as long as it is information that can identify the invoice by at least the payment agent server 40, and is, for example, a billing ID as identification information that identifies the invoice. The payment agent server 40 identifies the invoice for which BPSP has been selected as the payment method based on the billing key information notified by the intermediary server 10, and executes the BPSP according to the billing content. The payment agent server 40 can execute the BPSP smoothly because it has already been notified by the intermediary server 10 of the specific information used to execute the BPSP.

[0023] (Overview of the process flow performed by payment system 1) Here, an overview of the process flow performed by the payment system 1 will be explained with reference to Fig. 1. Here, it is assumed that the corporate card of the buyer who has been permitted by the supplier to make "card payment" has already been registered on the payment support site.

[0024] Step S101: The supplier server 20 transmits information required to generate an invoice to the intermediary server 10, and requests the intermediary server 10 to generate an invoice and send it to the buyer. Here, the supplier server 20 may transmit to the intermediary server 10, in the information required to generate an invoice, permission information indicating whether or not "card payment" is permitted as a payment method for the invoice to the buyer. Step S102: The intermediary server 10 transmits the payment candidate data 124 to the payment agent server 40. The intermediary server 10 generates the payment candidate data 124 based on the information (information required to generate an invoice) notified from the supplier server 20. The payment candidate data 124 is information including, for example, a supplier ID as identification information for identifying the supplier, a buyer ID as identification information for identifying the buyer, a billing ID as identification information for identifying the invoice, the billing amount, the payment due date, and the like (see FIG. 7). Step S103: The intermediary server 10 generates an invoice based on the information (information necessary to generate an invoice) notified by the supplier server 20. The invoice generated here may be provided with an operation button for performing "card payment" according to the supplier's intention. The intermediary server 10 stores the generated invoice in a predetermined location on the payment support site, for example, in the buyer's personal page on the payment support site. The intermediary server 10 notifies the buyer terminal 30 by email, SNS, or the like that the invoice can be viewed on the payment support site.

[0025] Step S104: Based on the notification from the intermediary server 10 (notification that the invoice is available for viewing), the buyer's accounting staff refers to the invoice stored in the payment support site, and the invoice is displayed on the buyer terminal 30. The buyer's accounting staff checks the billing details of the invoice displayed on the buyer terminal 30 and considers, for example, the payment method. Step S105: If the payment method for the invoice is set to BPSP, the buyer terminal 30 sends a notification to the intermediary server 10 that BPSP has been selected as the payment method for the invoice. For example, the buyer's accounting staff performs an operation such as clicking and depressing an operation button for "card payment" provided on the invoice displayed on the buyer terminal 30. In response to this operation, the buyer terminal 30 sends a notification to the intermediary server 10 that BPSP has been selected as the payment method for the invoice.

[0026] Step S106: When the intermediary server 10 receives a notification from the buyer terminal 30 (a notification that BPSP has been selected as the payment method for the invoice), it sends the billing key information for the invoice corresponding to the notification to the payment agency server 40.

[0027] Step S107: The payment agent server 40 identifies the invoice for which BPSP is to be executed based on the billing key information received from the intermediary server 10, and communicates with the buyer terminal 30 as necessary. For example, the payment agent server 40 notifies the buyer of a confirmation screen for confirming the details of the payment made by BPSP, and receives a response from the buyer indicating that the buyer has understood the details of the payment.

[0028] Step S108: The payment agent server 40 executes the BPSP. The payment agent server 40 performs credit card payment for the buyer. The payment agent server 40 also requests the financial institution server 50 to deposit the invoice amount into the supplier's deposit account. In response to the deposit request from the payment agent server 40, the financial institution server 50 deposits the amount into the supplier's deposit account.

[0029] Step S109: The payment agent server 40 executes the BPSP, and when payment for the invoice is complete, it sends a notification that payment for the invoice has been completed to the supplier server 20. If a response is received from the supplier server 20 that payment has indeed been made, the payment agent server 40 clears the invoices in the supplier's My Account that have been paid.

[0030] Step S110: The payment agency server 40 updates the payment status of the invoice in the buyer's My Account. For example, for an invoice for which payment using BPSP has been completed, the payment agency server 40 updates the details of the payment to the payment agency, such as the amount paid to the payment agency, the payment due date, and a status flag indicating whether or not the invoice has been paid, as the payment status. For example, the payment agency server 40 sends a notification to the buyer terminal 30 that the payment status of the invoice in the buyer's My Account has been updated. The buyer terminal 30 can access the payment support site in response to an operation by an accounting staff member and check the payment status of the invoice by referring to the buyer's My Account.

[0031] Step S111: The payment agency server 40 updates the payment status of the invoice in the supplier's My Account. For example, for an invoice for which payment has been completed using BPSP, the payment agency server 40 updates the payment status to indicate that payment to the supplier has been completed. For example, the payment agency server 40 sends a notification to the supplier server 20 that the payment status of the invoice in the supplier's My Account has been updated. The supplier server 20 can access the payment support site in response to an operation by an accounting staff member and check the payment status of the invoice by referring to the supplier's My Account.

[0032] (Configuration of the intermediary server 10) Here, the configuration of the intermediation server 10 will be described with reference to Fig. 2 to Fig. 7. Fig. 2 is a block diagram showing an example of the configuration of the intermediation server 10 according to the embodiment. Figs. 3 to 7 are diagrams showing examples of information stored in the intermediation server 10.

[0033] 2, the intermediary server 10 includes, for example, a communication unit 11, a storage unit 12, and a control unit 13. The communication unit 11 communicates with the supplier server 20, the buyer terminal 30, and the payment agent server 40. The storage unit 12 stores supplier information 120, buyer information 121, billing basic data 122, invoice data 123, and payment candidate data 124.

[0034] FIG. 3 shows an example of information stored as supplier information 120. Supplier information 120 is master information related to a supplier. As shown in FIG. 3, supplier information 120 includes information corresponding to each item such as supplier ID, company information, account information, login information, and use of BPSP. Supplier ID is information that can identify a supplier. Company information is information related to a supplier as a business operator, such as information indicating a company name and a corporate number. Account information is information related to an account used by a supplier for deposits, etc., such as information indicating a financial institution code, a branch code, an account number, etc. Login information is information for a supplier to log in to a payment support site, such as information indicating a supplier's account (login user name) and password, etc. In the use of BPSP, information is stored indicating whether the supplier allows the buyer to make a payment using BPSP. In this way, when information indicating whether the supplier allows a payment using BPSP is stored as the master information of the supplier, whether or not the payment using BPSP is allowed as a payment method for the supplier is set uniformly regardless of the invoice. The information stored in the "Use of BPSP" item may be information indicating that individual settings (rather than uniform) are to be made. In this case, for example, whether or not payment using BPSP is permitted is set for each invoice or buyer. When individual settings are made, for example, information notified from the supplier server 20 (information necessary to generate an invoice) includes information indicating whether or not payment using BPSP is permitted.

[0035] 4 shows an example of information stored as the buyer information 121. The buyer information 121 is master information related to a buyer. As shown in FIG. 4, the buyer information 121 includes information corresponding to each item such as a buyer ID, company information, account information, login information, and registered card information. The buyer ID is information that can identify a buyer. Each of the company information, account information, and login information is equivalent to the corresponding information in the supplier information 120. The registered card information stores information about the corporate credit card held by the buyer, such as the card number, the registered flag, etc. The registered flag here is information indicating whether or not the credit card used for BPSP has been registered in the payment agent server 40.

[0036] FIG. 5 shows an example of information stored as billing basic data 122. The billing basic data 122 is information necessary for generating an invoice. The billing basic data 122 is generated, for example, for each supplier. For example, when the supplier server 20 requests the generation of an invoice, it transmits information necessary for generating an invoice to the intermediary server 10. The intermediary server 10 stores the information received from the supplier server 20 (information necessary for generating an invoice) in the storage unit 12 as billing basic data 122. As shown in FIG. 5, the billing basic data 122 includes information corresponding to each item such as a billing basic ID, a buyer ID, a billing amount, a payment due date, billing contents, and use of BPSP. The billing basic ID is information that can identify the billing basic data (information necessary for generating an invoice). The buyer ID is information that can identify the buyer. The billing amount is the billing amount to be described on the invoice. The payment due date is the payment due date to be described on the invoice. Note that, for example, if there is a prior agreement regarding the payment due date, such as closing at the end of the month and paying at the end of the following month, the payment due date may contain information such as "October" indicating the current month. In this case, the invoice may state "October" and store information indicating the end of the following month (November 30th) as the payment due date. The billing details are information indicating details such as a breakdown of the invoice. The use of BPSP is information indicating whether or not payment using BPSP is permitted as a payment method for an invoice.

[0037] Based on the billing basic data 122, the intermediary server 10 generates billing data 123 as information on the bill from the supplier to the buyer. The intermediary server 10 generates the billing data 123 including information on the supplier as the payee, the billing amount, the payment due date, the billing content, and whether or not it is possible to select payment using BPSP as the payment method for the bill. The intermediary server 10 stores the generated billing data 123 in the storage unit 12. For example, an invoice corresponding to invoice data 123 indicates the supplier as the payee, the buyer as the payee, the invoice amount, the payment due date, and the invoice details, and if the invoice allows the option to pay using BPSP, an operation button for making a "card payment" is provided.

[0038] In addition, the intermediary server 10 generates payment candidate data 124 as information to be notified to the payment agent server 40 in advance, in preparation for the case where BPSP is selected as the payment method for the invoice, based on the billing basic data 122. The intermediary server 10 generates the payment candidate data 124 including, for example, information on the supplier as the payee, the buyer as the payer, the billing amount, and the payment due date. The intermediary server 10 stores the generated payment candidate data 124 in the storage unit 12.

[0039] FIG. 6 shows an example of information stored as invoice data 123. Invoice data 123 is information about an invoice to be viewed by a buyer. As shown in FIG. 6, 123 stores information corresponding to each item such as an invoice ID, a supplier ID, an invoice amount, a payment due date, invoice details, and use of BPSP. Since invoice data 123 is information generated based on invoice basic data 122, it matches invoice basic data 122 for items other than the supplier ID item. Since invoice data 123 is information about an invoice to be viewed by a buyer, it includes information that can identify the supplier to which payment is made, i.e., the supplier ID.

[0040] FIG. 7 shows an example of information stored as payment candidate data 124. The payment candidate data 124 is information notified to the payment agent server 40 in advance in case BPSP is selected as the payment method for the invoice. As shown in FIG. 7, the payment candidate data 124 stores information corresponding to each item such as supplier ID, buyer ID, and billing information. The supplier ID is information that can identify the supplier. The buyer ID is information that can identify the buyer. The billing information is information related to billing required for performing payment agent, such as information indicating the invoice ID, billing amount, and payment due date. The invoice ID, billing amount, and payment due date are equivalent to the corresponding information in the invoice data 123.

[0041] Returning to FIG. 2, the memory unit 12 is configured with a storage medium, such as a hard disk drive (HDD), a flash memory, an electrically erasable programmable read only memory (EEPROM), a random access read / write memory (RAM), a read only memory (ROM), or any combination of these storage media. The storage unit 12 may be, for example, a non-volatile memory. The storage unit 12 stores a program for implementing the functions of the intermediation server 10 (including functions corresponding to each unit of the control unit 13). The functions corresponding to each unit of the control unit 13 are implemented by a processor such as a CPU (Central Processing Unit) of the intermediation server 10 executing the program stored in the storage unit. At least some of the functions of the intermediation server 10 may be implemented by an electric circuit. Also, at least some of the functions of the intermediation server 10 may be implemented by executing a program acquired via a network.

[0042] The control unit 13 includes, for example, a supplier correspondence unit 130, a buyer correspondence unit 131, and a payment agent correspondence unit 132.

[0043] The supplier correspondence unit 130 executes processing related to correspondence with suppliers. For example, when a notification is made from the supplier server 20 requesting the creation of an invoice, the supplier correspondence unit 130 acquires information necessary for generating an invoice via the communication unit 11. The supplier correspondence unit 130 stores the acquired information in the storage unit 12 as billing basic data 122. The supplier correspondence unit 130 requests the buyer correspondence unit 131 to generate invoice data 123 based on the billing basic data 122. The supplier correspondence unit 130 also requests the payment agent correspondence unit 132 to generate payment candidate data 124 based on the billing basic data 122.

[0044] The buyer correspondence unit 131 executes processing related to correspondence with the buyer. For example, when the payment agent correspondence unit 132 is requested by the supplier correspondence unit 130 to generate invoice data 123, the payment agent correspondence unit 132 generates the invoice data 123 using the invoice basic data 122. The buyer correspondence unit 131 stores the generated invoice data 123 in the storage unit 12. The buyer correspondence unit 131 stores the generated invoice data 123 in the buyer's personal page on the settlement support site so that the data can be viewed. The buyer correspondence unit 131 notifies the buyer terminal 30 via the communication unit 11 that the invoice can be viewed. In addition, when the buyer response unit 131 receives a notification from the buyer terminal 30 indicating an invoice for which BPSP has been selected as the payment method, it requests the payment agency response unit 132 to send the corresponding billing key information to the payment agency server 40.

[0045] The payment agency correspondence unit 132 executes processing related to correspondence with the payment agency. For example, when the payment agency correspondence unit 132 is requested by the supplier correspondence unit 130 to generate payment candidate data 124, the payment agency correspondence unit 132 generates the payment candidate data 124 using the billing basic data 122. The payment agency correspondence unit 132 generates the payment candidate data 124 using the supplier information 120 and the buyer information 121 stored in the storage unit 12. The payment agency correspondence unit 132 stores the generated payment candidate data 124 in the storage unit 12. The payment agency correspondence unit 132 transmits the payment candidate data 124 to the payment agency server 40 via the communication unit 11. Furthermore, when the payment agency correspondence unit 132 is requested by the buyer correspondence unit 131 to transmit billing key information to the payment agency server 40, the payment agency correspondence unit 132 identifies an invoice for which BPSP was selected as the payment method based on a notification from the buyer terminal 30. The payment agency correspondence unit 132 transmits the billing key information of the identified invoice to the payment agency server 40 via the communication unit 11.

[0046] Here, the screens displayed on the buyer terminal 30 will be described with reference to Fig. 8 to Fig. 11. Fig. 8 to Fig. 11 are diagrams showing examples of screens displayed on the buyer terminal 30 of the embodiment.

[0047] FIG. 8 is a diagram showing an example of a list screen D10 on which a list of invoices issued to a buyer is displayed. Reference symbol D11 is an operation field for extracting a desired document, for example, an invoice, from various forms. In this manner, the payment support site may store various forms issued to buyers, such as quotations, delivery notes, invoices, etc. Reference symbol D12 is an operation field for searching invoices using search keywords such as invoice attributes, for example, the supplier as the payer, the invoice issue date, the invoice amount, etc. A list of invoices that match the search conditions set here is displayed on the buyer terminal 30.

[0048] Reference symbol D13 denotes a check box for setting an invoice to be selected in the list of invoices. By checking this box, an invoice can be selected. Note that in the example shown in this figure, an example is shown in which check boxes are provided for selecting invoices individually, but a button that allows all invoices to be selected at once may also be provided. In addition, a collective selection checkbox may be provided as code D13. By selecting this collective selection checkbox, the buyer can select all invoices, thereby reducing the time and effort required to select them one by one.

[0049] Code D14 is a selection button for selecting "Credit Card Payment." When the selection button code D14 is clicked, a notification is sent from the buyer terminal 30 to the intermediary server 10 that BPSP has been selected as the payment method for one or more invoices selected in code D13.

[0050] Reference symbol D15 is a selection button for checking points. In this embodiment, a selection button for checking points may be provided in this way. When points are awarded according to the amount of credit card usage, the acquisition of points can be a motivation for using a credit card. In this embodiment, by providing an operation button such as reference symbol D15, a predicted number of points that can be acquired if a payment is made can be confirmed before the payment is made. The buyer can know the number of points that can be acquired if the payment is made with a credit card before the payment is actually made, and this can provide information for deciding whether or not to make the payment with a credit card.

[0051] Reference symbol D16 is a selection button for confirming various information. The various information here is information that can be used as a basis for determining whether or not to settle with a credit card. For example, a buyer who is concerned about cash flow may request a simulation to see how much the cash flow can be improved if all bills for this month are settled by credit card and the actual payment due date is extended by one month. In such a case, the desired simulation can be performed by operating the operation button of reference symbol D16. The confirmation to which the operation button of reference symbol D16 corresponds may be arbitrarily set according to the buyer. For example, if the buyer registers the expected amount of payment A for this month in advance, the expected amount of payment A, the total amount of payment B on the invoice, the total amount of payment C on the invoice selected by reference symbol D13, etc. may be displayed on the list screen D10, and (AB) as the funds when credit card payment is not used, and (A-B+C) as the funds when credit card payment is used, etc. may be displayed.

[0052] Reference symbol D17 is an operation button for viewing the PDF of the invoice. When the selection button of reference symbol D17 is clicked, the PDF of one or more invoices selected in reference symbol D13 is displayed on the buyer terminal 30. Reference numeral D18 is a PDF of the invoice. When the selection button of reference numeral D17 is clicked, a PDF of the invoice such as reference numeral D18 is displayed on the buyer terminal 30.

[0053] Fig. 9 is a diagram showing an example of a confirmation screen D20 that is displayed when code D14 in Fig. 8 is operated. Pressing "Credit payment" in code D14 in Fig. 8 triggers notification of billing key information from the intermediary server 10 to the payment agent server 40, and based on the billing key, the payment agent server 40 notifies the buyer terminal 30 of a confirmation screen for confirming the payment details, such as confirmation screen D20. Reference numeral D21 denotes a display field in which the name of the buyer is displayed. Reference numeral D22 is a display field in which the name of the supplier as the billing source (payee) is displayed. Reference numeral D23 denotes a display field in which the name of the invoice is displayed. Reference numeral D24 denotes a display field in which the invoice ID is displayed. Reference numeral D25 denotes a display field in which the billing date is displayed. Reference numeral D26 denotes a display field in which the payment amount is displayed. Reference numeral D27 denotes an operation button that the buyer operates when executing settlement.

[0054] Fig. 10 is a diagram showing an example of a confirmation screen D30 that is displayed when code D15 in Fig. 8 is operated. Pressing "Confirm points" in code D15 in Fig. 8 triggers the display of a confirmation screen for checking the points that can be acquired, such as confirmation screen D30. Reference numeral D31 denotes a display field in which the name of the buyer is displayed. Reference numeral D32 denotes a display field in which the payment amount is displayed. Reference numeral D33 denotes a display field in which the predicted points to be acquired are displayed. Reference numeral D34 denotes a display field in which the points before payment (current status) are displayed. Reference numeral D35 denotes a display field in which points (estimated value) after settlement are displayed. Reference symbol D36 denotes an operation button that the buyer operates when checking the point conversion formula.

[0055] Points conversion rates generally vary depending on the credit card. For example, if the credit card used in the BPSP is issued by a business that corresponds to the intermediary server 10, the intermediary server 10 can calculate points (predicted value) according to the payment amount without making an inquiry to the credit card issuer. Alternatively, if the credit card used for BPSP is handled by a payment agency corresponding to the payment agency server 40, the intermediary server 10 can inquire of the payment agency server 40 and calculate points (predicted value) according to the payment amount. Also, the point conversion formula may be set in advance on the payment support site. In this case, the set point conversion formula may be edited by the buyer. For example, when the buyer presses the operation button D36, the point conversion formula is displayed. Variables used in the displayed point conversion formula, such as the point redemption rate, are displayed in an editable manner. The buyer can set a desired value for the point redemption rate as a variable in the point conversion formula, and check the points (estimated value) that can be acquired when points are redeemed at the desired redemption rate.

[0056] 11 is a diagram showing an example of a screen D40 showing a payment history notified to the buyer terminal 30 from the payment agent server 40 after executing BPSP. The screen D40 showing the payment history shows the history of payments made via the payment agent server 40, and shows the contents of the payment according to each item such as the payment number, the payment date and time, the payment amount, the biller, and the invoice number. The buyer's accounting staff can confirm that the payment to the supplier has been made by visually checking the screen D40 showing the payment history.

[0057] (Processing flow of payment system 1) Here, the flow of processing performed by the payment system 1 will be described with reference to Fig. 12 and Fig. 13. Fig. 12 and Fig. 13 are sequence diagrams showing the flow of processing performed by the payment system 1 of the embodiment.

[0058] FIG. 12 shows the flow of processing up to the display of the invoice on the buyer terminal 30. Step S10: The supplier server 20 transmits basic billing data (information necessary to generate an invoice) and requests the intermediation server 10 to generate an invoice. Step S11: The intermediary server 10 judges whether or not the supplier that has notified the billing basic data is a supplier that is permitted to use the BPSP. Step S12: If the supplier that has notified the billing basic data in step S11 is a supplier that has permission to use BPSP, the intermediary server 10 generates payment candidate data 124 from the billing basic data 122 and transmits the generated payment candidate data 124 to the payment agency server 40.

[0059] Step S13: The payment agent server 40 receives the payment candidate data 124 from the intermediary server 10, and assumes that a payment corresponding to the received payment candidate data 124 will be executed, and sets the status of the payment corresponding to the payment candidate data 124 to a preparation state. By setting the status to such a preparation state, when the billing key information is notified and the payment is actually executed, it becomes easier to identify the payment details, and the payment can be executed smoothly.

[0060] Step S14: The intermediation server 10 generates, from the basic billing data 122, billing data 123 from which a BPSP can be selected. Step S15: On the other hand, if the supplier that notified the billing basic data in step S11 is not a supplier that permits the use of BPSP, the intermediary server 10 generates invoice data 123 from the billing basic data 122 in which BPSP cannot be selected. Step S16: The intermediary server 10 sets up the payment support site so that the invoice data 123 stored therein can be viewed by the buyer. Step S17: The intermediary server 10 transmits a notification to the buyer terminal 30 that the invoice is available for viewing. Step S18: The buyer terminal 30 becomes able to display the invoice by accessing a site corresponding to the notification that the invoice can be viewed, for example, the buyer's personal page on a payment support site.

[0061] FIG. 13 shows the flow of processing up to the execution of a payment. Step S19: The buyer terminal 30 selects the use of BPSP as the payment method for the invoice. The buyer's accounting staff selects the invoice to be paid using BPSP by checking the check box D13 on the list screen D10 in Fig. 8, and presses the operation button D14. As a result, information indicating the invoice to be paid using BPSP is sent from the buyer terminal 30 to the intermediary server 10. Step S20: The intermediary server 10 transmits to the settlement agent server 40 billing key information for the bill to be paid using BPSP. Step S21: The payment agent server 40 generates a confirmation screen for confirming the details of the payment using the BPSP, and notifies the buyer terminal 30. If the credit card used in the BPSP is not registered, the payment agent server 40 may generate a registration screen for registering the credit card and prompt the buyer to register the credit card. Step S22: The buyer terminal 30 displays a confirmation screen. Step S23: The buyer's accounting staff visually checks the confirmation screen, checks whether there are any mistakes in the payment details, and if it is determined that the payment can be executed with the details, presses the operation button (D27 in FIG. 9) for executing the payment. As a result, the buyer terminal 30 transmits a response to the payment agent server 40 that the payment can be executed. Step S24: The payment agent server 40 determines whether the payment can be executed. For example, if the available credit of the credit card used for the BPSP is greater than the payment amount, the payment agent server 40 determines that the payment can be executed. On the other hand, if the available credit of the credit card used for the BPSP is less than the payment amount, the payment agent server 40 determines that the payment cannot be executed. Step S25: If the payment agent server 40 determines in step S24 that payment can be made, it executes the payment. The payment agent server 40 executes the credit card payment for the buyer, deposits the money into the supplier's deposit account, and makes a payment to the supplier. Step S26: When the payment is executed, the intermediary server 10 acquires the details of the executed payment. Step S27: The intermediary server 10 transmits the details of the executed settlement to each of the supplier server 20 and the buyer terminal 30. As shown in steps S26 to S27, the intermediary server 10 may periodically (e.g., once a month) collect details of the executed settlement from the settlement agent server 40, and transmit a transaction history to each of the supplier server 20 and the buyer terminal 30 according to the collected details. Also, the settlement agent server 40 may transmit a transaction history to each of the supplier server 20 and the buyer terminal 30. For example, the details of the settlement notified to the buyer are the settlement history shown in FIG. 11. Step S28: On the other hand, if it is determined in step S24 that the payment cannot be executed, the payment agent server 40 notifies the buyer terminal 30 that the payment cannot be executed, and ends the process.

[0062] As described above, the payment system 1 of the embodiment includes the payment agency correspondence unit 132 and the buyer correspondence unit 131. The payment agency correspondence unit 132 generates payment candidate data 124 that is a candidate for which payment is executed in the payment agency server 40 based on the billing basic data 122, and transmits the generated payment candidate data 124 to the payment agency server 40. The buyer correspondence unit 131 generates invoice data 123 that is an invoice for the buyer based on the billing basic data 122, and transmits the generated invoice data 123 to the buyer terminal 30. When the buyer selects BPSP, which is a credit card payment by payment agency, as a payment method for the invoice data 123, the payment agency correspondence unit 132 transmits billing key information, which is identification information of the invoice data 123 for which BPSP was selected, to the payment agency server 40. As a result, in the intermediary server 10 of the embodiment, before the BPSP is executed, the payment candidate data 124 is notified to the payment agent, and when the BPSP is actually executed, only the billing key information is notified, so that the payment can be executed smoothly. Therefore, it is possible to make it easier to use the BPSP, which is a credit card payment by a payment agent.

[0063] In addition, in the settlement system 1 of the embodiment, the buyer correspondence unit 131 generates invoice data 123 in which whether or not BPSP is selectable is set according to the availability information indicating whether or not the use of BPSP is permitted, which is notified from the supplier server 20. As a result, the intermediation server 10 of the embodiment can generate an invoice according to the supplier's intention.

[0064] Moreover, the payment system 1 of the embodiment further includes a storage unit 12. The storage unit 12 stores supplier information 120 and buyer information 121. The payment agent support unit 132 generates payment candidate data 124 using the supplier information 120 and the buyer information 121 stored in the storage unit 12. As a result, the payment system 1 of the embodiment can generate the payment candidate data 124 by acquiring the contents of the bill from the bill basic data 122, acquiring information on the payee from the supplier information 120 and on the payer from the buyer information 121.

[0065] In addition, in the settlement system 1 of the embodiment, the buyer handling unit 131 displays a list screen showing the invoice data 123 corresponding to each of a plurality of invoices issued to the buyer, for example, the list screen D10 of FIG. 8, on the buyer terminal 30. On the list screen, the buyer can collectively select credit card payment through a settlement agent as a payment method for the displayed group of invoices. This allows the buyer to select all invoices with a single operation in the settlement system 1 of the embodiment, thereby reducing the effort of selecting them one by one. In addition, in the payment system 1 of the embodiment, the buyer support unit 131 displays on the buyer terminal 30 the predicted value of points that can be acquired when BPSP, which is a credit card payment by payment agent, is executed as payment for the invoice data 123. This allows the payment system 1 to display the number of points that can be acquired when making a payment with a credit card before actually making the payment, and provides the buyer with information to decide whether or not to make a payment with a credit card. The buyer can grasp the number of points that can be acquired when making a payment with a credit card before actually making the payment, and can determine whether or not to use BPSP after grasping the predicted number of points to be acquired.

[0066] (Modification of the embodiment) Here, a modified example of the embodiment will be described. This modified example differs from the above-described embodiment in that invoice data 123 issued by each of a plurality of different suppliers to the same buyer is displayed.

[0067] Fig. 14 is a diagram showing an example of a screen displayed on the buyer terminal 30 in a modified example of the embodiment. Fig. 14 is a diagram showing an example of a list screen D50 on which a list of invoices issued to a buyer is displayed. Reference number D51 is a display field that displays a list of invoices from a specific supplier (in this example, □□□ Sports). This list is provided with check boxes for selecting invoices for which credit card payment is required. Reference numbers D510 and D511 indicate that invoices have not been selected for which credit card payment is required. Reference number D52 is a display field that displays a list of invoices received from other suppliers (X Corporation in this example). This list is provided with check boxes for selecting invoices for credit card payment. Reference number D520 indicates that an invoice has been selected for credit card payment. Reference number D521 indicates that an invoice has not been selected for credit card payment.

[0068] Reference symbol D53 is a display field that displays a list of invoices received from other suppliers (Y Corporation in this example). This list is provided with check boxes for selecting invoices for which credit card payment is to be made. Reference symbols D530 and D531 indicate that the invoices have been designated in advance by the supplier as invoices for which credit card payment is to be made. In this way, the intermediary server 10 may generate invoices that specify payment using BPSP in accordance with the supplier's wishes.

[0069] Reference numeral D54 denotes a display field for displaying the total billed amount, which is the sum of the billed amounts for each of the invoices shown in the lists D51 to D53. Reference numeral D55 is a display field that displays the total credit card payment amount. This display field displays the total of the billing amounts of the invoice group selected as invoices to be paid by credit card in the check boxes D51 to D53. Reference symbol D56 is a display field that displays the predicted number of points to be acquired. This display field displays the number of points that are predicted to be acquired if the credit payment of the total credit payment amount displayed in reference symbol D56 is made. In the list screen D50, an operation button equivalent to reference symbol D36 in FIG. 10 (an operation button for checking the point conversion formula) may be provided.

[0070] The payment system 1 and the intermediary server 10 in the above-mentioned embodiment may be realized in whole or in part by a computer. In that case, a program for realizing this function may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into a computer system and executed to realize the function. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into a computer system. The term "computer-readable recording medium" may also include a medium that dynamically holds a program for a short period of time, such as a communication line when a program is transmitted via a network such as the Internet or a communication line such as a telephone line, and a medium that holds a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client in such a case. The above-mentioned program may be a program for realizing a part of the above-mentioned function, or may be a program that can realize the above-mentioned function in combination with a program already recorded in the computer system, or may be a program that is realized using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0071] Although an embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and designs that do not deviate from the gist of the present invention are also included. [Explanation of symbols]

[0072] 1: payment system, 10: intermediary server, 120: supplier information, 121: buyer information, 122: billing basic data, 123: invoice data, 124: payment candidate data, 131: buyer correspondence section, 132: payment agent correspondence section, 20: supplier server, 30: buyer terminal, 40: payment agent server

Claims

1. A payment agent corresponding unit that generates payment candidate data that are candidates for execution of payment in the payment agent server based on the billing basic data notified from the supplier server, the billing basic data indicating the contents of the bill to the buyer who is the payer, and transmits the generated payment candidate data to the payment agent server; a buyer handling unit that generates invoice data, which is an invoice for the buyer, based on the invoice basic data and transmits the generated invoice data to a buyer terminal; Equipped with When the buyer selects BPSP, which is a credit card payment through a payment agency, as a payment method for the invoice data, the payment agency support unit transmits billing key information, which is identification information of the invoice data selected by the BPSP, to the payment agency server. Intermediary server.

2. the buyer correspondence unit generates the invoice data in which whether or not use of the BPSP is selectable is set according to availability information indicating whether or not use of the BPSP is permitted, which is notified from the supplier server; The intermediation server according to claim 1 .

3. A storage unit that stores supplier information related to the supplier corresponding to the supplier server and buyer information related to the buyer, The payment agent support unit generates the payment candidate data using the supplier information and the buyer information stored in the storage unit. The intermediation server according to claim 1 .

4. The buyer support unit displays on the buyer terminal a list screen showing a list of the invoice data corresponding to each of a plurality of invoices issued to the buyer, and on the list screen, the buyer can collectively select a BPSP, which is a credit card payment through a settlement agent, as a payment method for the displayed group of invoices. The intermediation server according to claim 1 .

5. The buyer handling unit displays on the buyer terminal a predicted value of points that can be acquired when BPSP, which is a credit card payment through a settlement agent, is executed as a payment for the invoice data. The intermediation server according to claim 1 .

6. An intermediation method executed by a computer that is an intermediation server, comprising: A payment agent corresponding unit generates payment candidate data which are candidates for execution of payment in the payment agent server based on the billing basic data notified from the supplier server, the billing basic data indicating the contents of the bill to the buyer who is the payer, and transmits the generated payment candidate data to the payment agent server; A buyer correspondence unit generates invoice data which is an invoice for the buyer based on the invoice basic data, and transmits the generated invoice data to a buyer terminal; When the buyer selects BPSP, which is a credit card payment through a payment agency, as a payment method for the invoice data, the payment agency support unit transmits billing key information, which is identification information of the invoice data selected by the BPSP, to the payment agency server. Mediation method.

7. On the intermediary server computer, generating payment candidate data which are candidates for execution of payment in the payment agent server based on the billing basic data notified from the supplier server, the billing basic data indicating the contents of the bill to the buyer who is the payer, and transmitting the generated payment candidate data to the payment agent server; generating invoice data which is an invoice for the buyer based on the invoice basic data, and transmitting the generated invoice data to a buyer terminal; When the buyer selects a BPSP, which is a credit card payment through a settlement agent, as a payment method for the invoice data, the BPSP transmits billing key information, which is identification information of the selected invoice data, to the settlement agent server. program.

Images