Payment agent server, method and program

Abstract

To provide a payment agent server that enables a biller to use a payment means under desired conditions when the biller receives payment of a service fee or the like from a billing destination. [Solution] Access is received based on link information included in the billing request. In response to the access, a payment screen is displayed to the billing recipient. Instructions for selecting a financial institution are received from the billing recipient using the payment screen. A payment method is identified by the financial institution that received the instruction to select, based on rules previously defined with the billing source related to the billing request. Payment is made using the identified payment method using the access token for that payment method.

Description

[Technical Field]

[0001] The present invention relates to a payment agent server, a method thereof, and a program thereof. [Background technology]

[0002] Companies that receive bank transfers of service fees and other payments from a large number of users accept transfers via multiple payment methods that have different arrival times and fees. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2023-067739 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, such companies have a demand for payment methods that have low fees and allow the funds to arrive quickly. However, there has been a problem in that the payment method used has not been able to reflect the wishes of the company receiving the transfer (the company from which the bill is sent).

[0005] The present invention has been made in consideration of the above circumstances, and aims to provide a payment agent server, a method and a program for the same that enable a biller to use a payment method with desired conditions when receiving payment for service fees, etc. from a billee. [Means for solving the problem]

[0006] The present invention is a payment agency server that executes the following steps: a first step of generating a billing request including link information regarding payment from the billing destination of the invoice to the billing source; a second step of receiving access from the billing destination related to the billing request based on the link information included in the billing request; a third step of displaying a payment screen to the billing destination in response to the access in the second step; a fourth step of receiving an instruction to select a financial institution from the billing destination using the payment screen displayed in the third step; a fifth step of identifying a payment method by the financial institution that received the instruction to select a payment method based on rules previously defined between the billing destination related to the billing request and the financial institution; and a sixth step of making payment using the payment method identified in the fifth step using the access token of the payment method or an authentication process specified by the financial institution.

[0007] Preferably, the sixth step performs processing to transfer the amount indicated in the billing request from the billing destination to the billing source using the access token of the payment method identified in the fifth step or an authentication process specified by the financial institution.

[0008] Preferably, the rule defines a priority order for using the plurality of payment methods for the payment.

[0009] Preferably, the method includes a seventh step of determining whether the access token of the payment means identified in the fifth step is in possession of the access token, and an eighth step of, if it is determined in the seventh step that the access token is not in possession of the access token, displaying an authentication screen by the financial institution to the billing destination and obtaining the access token through authentication by the billing destination using the authentication screen, and the sixth step makes payment using the payment means using the access token obtained in the eighth step or an authentication process specified by the financial institution.

[0010] Preferably, the seventh step determines that the access token or the authentication process designated by the financial institution is in possession of the access token, the sixth step performs payment using the payment means based on the access token or the authentication process designated by the financial institution, and if the payment fails, a ninth step is further performed in which payment is made using the payment means based on the access token of the payment means with the next highest priority among the plurality of payment means according to the rule or the authentication process designated by the financial institution.

[0011] Preferably, the payment failure is due to the access token or an authentication process specified by the financial institution expiring, or the specified payment method being unavailable.

[0012] The payment agency method of the present invention includes a first step of generating a billing request including link information regarding payment from the billing destination of the invoice to the billing source, a second step of receiving access from the billing destination related to the billing request based on the link information included in the billing request, a third step of displaying a payment screen to the billing destination in response to the access in the second step, a fourth step of receiving an instruction to select a financial institution from the billing destination using the payment screen displayed in the third step, a fifth step of identifying a payment method by the financial institution that received the instruction to select a payment method based on rules previously defined between the billing destination and the billing source related to the billing request, and a sixth step of making payment using the payment method identified in the fifth step.

[0013] The program of the present invention causes a computer to execute the following steps: a first step of generating a billing request including link information regarding payment from the billing destination of the invoice to the billing source; a second step of receiving access from the billing destination related to the billing request based on the link information included in the billing request; a third step of displaying a payment screen to the billing destination in response to the access in the second step; a fourth step of receiving an instruction to select a financial institution from the billing destination using the payment screen displayed in the third step; a fifth step of identifying a payment method by the financial institution that received the selection instruction based on rules previously defined between the billing destination related to the billing request and the billing source related to the billing request; and a sixth step of making payment using the payment method identified in the fifth step. [Effects of the Invention]

[0014] According to the present invention, it is possible to provide a payment agency server, a method and a program that enable a biller to use a payment method with desired conditions when receiving payment for service fees, etc. from a billee. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 shows the overall configuration of a payment system 1 according to an embodiment of the present invention. [Figure 2] FIG. 2 is a flowchart illustrating the flow of processing in the payment system 1 shown in FIG. [Figure 3] FIG. 3 is a flowchart continuing from FIG. 2, illustrating the processing flow of the payment system 1 shown in FIG. [Figure 4] FIG. 4 is a flowchart for explaining the process when it is determined in step ST18 shown in FIG. 3 that an access token is stored (step ST19). [Figure 5] FIG. 5 is a flowchart for explaining the process when the payment authentication fails in step ST33 shown in FIG. [Figure 6] FIG. 6 is a functional block diagram of the billing device 3 shown in FIG. [Figure 7] FIG. 7 is a functional block diagram of the payment agent server 11 shown in FIG. DETAILED DESCRIPTION OF THE INVENTION

[0016] The payment system 1 according to the embodiment of the present invention will be described below. The payment agency that operates the payment agency server 11 concludes with financial institutions such as banks a usage agreement regarding the connection of the API (Application Programming Interface) provided by the financial institution server provided by the financial institution, as well as a usage agreement for each individual payment service provided by the financial institution. A payment agency is, for example, an electronic payment agency, and is a company that aims to popularize direct payments between bank accounts (Account to Account = A2A payments), which are expanding overseas, in Japan.

[0017] Direct payments between bank accounts are a simple system that does not involve an intermediary in the payment process, resulting in low payment fees and faster deposits into the bank accounts of the businesses (billers, merchants) that collect the payments.

[0018] Users who pay (billing recipients, consumers) prefer cashless payment methods through various point programs, but the source of points is mainly payment fees paid by the biller. These payment fees are included in the sales price as an invisible cost, which runs counter to wage increases and appropriate price pass-on. Payment service providers, acting as an electronic payment agent, promote the spread of direct payments between bank accounts by reforming the withdrawal process from bank accounts based on the entrustment of consumers who are depositors, thereby creating benefits for consumers, affiliated stores, and banks. In order to popularize direct payments between bank accounts, the process of withdrawing funds from bank accounts needs to be revamped, and one way to achieve this is to connect to deposit-taking institutions via update APIs.

[0019] The API connection with a financial institution transmits withdrawal instructions from the billee (user) to the bank's system (financial institution server 6) via the transfer request API provided by the financial institution, enabling bank transfers to be instructed and executed in real time. By selecting "Pay by Bank" as the payment method and choosing a deposit account at the financial institution, users can easily pay by transfer from that account. However, depending on the financial institution, approval of the transfer may require access to the financial institution's internet banking each time. Note that the connection with a financial institution in this invention is not limited to APIs.

[0020] Furthermore, when making a transfer request, users can check their deposit balance on the interface provided by the payment service provider without launching a bank app, etc., and can then begin the payment process only after confirming that they have sufficient funds. This balance check is performed using the balance reference API provided by the financial institution server 6.

[0021] Figure 1 shows the overall configuration of a payment system 1 according to an embodiment of the present invention. As shown in Figure 1, the payment system 1 includes, for example, a billing device 3, a billing destination terminal device 5, and a payment agent server 11, which communicate via a network 9.

[0022] The billing source device 3 is a device used by a biller (such as an affiliated store) that has made a prior contract with a payment agency and requests the payment agency to handle payment of a billing request issued to the billing destination. The billing destination terminal device 5 is the billing source's user (billing destination), and is a device used by the billing destination to make payment (transfer) based on the billing request from the billing source. The payment agency server 11 is a device used by a business that handles the procedure for the billing destination to pay the billing source based on the billing request issued by the billing source.

[0023] The payment processing of the financial institution by the payment agent server 11 uses an access token acquired by the payment agent server 11 at the initial billing destination registration stage. Note that some payment methods do not have an access token, so the term "authentication process specified by the financial institution" is used. An example of an individually specified authentication process that replaces the access token is a combination of ID and PW. The payment agent server 11 and the financial institution server 6 are linked via API linkage or individual payment services. In this embodiment, the case where payment is made using an access token will be mainly described, but payment may also be made using an authentication process individually designated by the financial institution instead of an access token.

[0024] When the payment agent server 11 accesses the financial institution server 6 selected by the billing recipient, it presents terms of use for each applicable payment method and obtains the billing recipient's consent. Prior to presenting the terms and conditions, the payment agent server 11 also concludes a separate contract with the financial institution server 6. The billing recipient entrusts the payment agent server 11, which then accesses the financial institution server 6 on behalf of the billing recipient. At that time, whether the financial institution server 6 has been officially entrusted by the billing recipient is determined by authenticating the ID / PW, etc., on the authentication screen of the financial institution server 6. If this authentication is successful, the financial institution grants the payment agent server 11 an access token for the billing recipient. The access token is used to access the financial institution server 6 after the payment route (payment method) has been determined. As its name suggests, the access token is only used to access the account on the financial institution server 6 (similar to a duplicate key).

[0025] The processing flow of the payment system 1 will be explained below. Figure 2 is a flowchart illustrating the processing flow of the payment system 1 shown in Figure 1. Figure 3 is a flowchart continuing from Figure 2, illustrating the processing flow of the payment system 1 shown in Figure 1. Each step will be explained. Step ST11: A biller receiving services from a payment agency operates the billing source device 3 to send a first billing request regarding a bill made by the biller to the billee to the payment agency server 11. This processing is performed using an API provided by the payment agency server 11.

[0026] Step ST12: Based on the first billing request received in step ST11, the payment agent server 11 provides a second billing request including billing destination, billing source, billing amount, item, and link information for each bill to the billing source device 3. The payment agent server 11 may also provide the second billing request to the billing destination terminal device 5.

[0027] Step ST13: The billing source device 3 provides the second billing request to the billing destination terminal device 5 that is the billing destination.

[0028] Step ST14: The billing destination uses the billing destination terminal device 5 to check the contents of the second billing request provided in step ST13, and displays the payment screen provided by the payment agent server 11 based on the link information contained therein.

[0029] Step ST15: A financial institution selection screen is displayed on the payment screen of the billing destination terminal device 5. The billing destination operates the billing destination terminal device 5 and uses the selection screen to select a financial institution to be used for paying the bill.

[0030] Step ST16: The payment agency server 11 determines (identifies) the payment method with the highest priority based on the details of the billing request, such as the billing amount, and the rules pre-agreed (pre-determined) between the payment agency and the biller.

[0031] Step ST17: The payment agent server 11 determines whether it has previously stored (acquired) the access token or authentication process individually specified by the financial institution required for payment using the payment method identified in step ST16. If it determines that it has been previously stored, the payment agent server 11 proceeds to step ST19; otherwise, it proceeds to step ST20.

[0032] The following describes the processing to be performed when it is determined in step ST18 shown in Fig. 3 that an access token or an authentication process individually designated by a financial institution is stored (step ST19). Fig. 4 is a flowchart for explaining the processing to be performed when it is determined in step ST18 shown in Fig. 3 that an access token is stored (step ST19). Each step will be described.

[0033] Step ST31: The payment agent server 11 uses the access token of the payment means determined to have the highest priority in step ST16 to access the financial institution server 7 selected by the billing destination in step ST15.

[0034] Step ST32: The payment agent server 11 uses an API or the like to perform payment authentication support processing by the financial institution server 7 of the billing destination based on the access token of the payment method with the highest priority or the authentication process specified by the financial institution. If the access token or the authentication process specified by the financial institution is stored in the past transaction, the payment authentication support process does not require input and authentication of the billing party's ID and password.

[0035] Step ST33: If the payment authentication is successful, the financial institution server 7 proceeds to step ST34.

[0036] Step ST34: The financial institution server 7 performs payment (such as transferring the invoice amount from the invoice destination to the invoice source) using the payment means for which payment authentication was successful in step ST32. This payment process does not require input of transfer destination information or the invoice amount, and is automatically performed by the payment agent server 11 using the amount corresponding to the invoice request and the transfer destination account based on the access token. Specifically, the payment agent server 11 uses the access token of the specified payment method to perform processing to transfer the amount of the bill indicated in the billing request from the billing destination to the billing source.

[0037] Step ST35: The financial institution server 7 sends a settlement completion notice to the settlement agent server 11.

[0038] Step ST36: The payment agent server 11 transmits a payment completion notification to the billing device 3 that is the billing source.

[0039] Step ST37: The billing device 3 sends a settlement completion notice to the billing destination terminal device 5.

[0040] The following describes the process to be performed when payment authentication fails in step ST33 shown in FIG. FIG. 5 is a flowchart for explaining the process when the payment authentication fails in step ST33 shown in FIG. Each step will be explained.

[0041] Step ST41: The payment agent server 11 determines whether the access token used in the payment authentication in step ST32 or the authentication process designated by the financial institution has expired. Whether or not a payment method has expired is determined based on the results of communication from the payment agent server to the financial institution server. The payment method may also be unavailable via the financial institution server 6. This may be due to reasons such as concentrated access, maintenance, or not meeting the access conditions. If the payment agent server 11 determines that the card is invalid, it proceeds to step ST42.

[0042] Step ST42: The settlement agent server 11 displays an authentication screen provided by the financial institution server 6 on the billing destination terminal device 5, and causes the financial institution to perform authentication processing.

[0043] Step ST43: If the authentication in step ST42 is successful, the payment agent server 11 proceeds to step ST44, otherwise proceeds to step ST45.

[0044] Step ST44: The payment agent server 11 performs the payment process using the selected payment means that was successfully authenticated in step ST42.

[0045] Step ST45: The payment agent server 11 identifies the payment method with the next highest priority after the payment method that failed authentication in step ST43 based on the rules described above, and performs authentication of the payment process using the identified payment method.

[0046] The configuration of the billing device 3 shown in FIG. 1 will now be described. FIG. 6 is a functional block diagram of the billing device 3 shown in FIG. As shown in FIG. 6, the billing device 3 includes, for example, an operation unit 53, a communication unit 55, a memory 59, and a processing unit 61.

[0047] The operation unit 53 is an operation means such as a touch panel, a keyboard, or a mouse. The communication unit 55 communicates with the payment agent server 11 and the billing destination terminal device 5. The input unit 57 is a terminal or the like for inputting data from the outside. The memory 59 stores the program executed by the processing unit 61 . The processing unit 61 executes the program PRG1 stored in the memory 59 to perform the processing of the billing device 3 defined in this embodiment.

[0048] The configuration of the payment agent server 11 shown in FIG. 1 will be described below. FIG. 7 is a functional block diagram of the payment agent server 11 shown in FIG. As shown in FIG. 7, the payment agent server 11 includes, for example, a communication unit 75, an input unit 77, a memory 79, and a processing unit 81.

[0049] The communication unit 75 communicates with the billing device 3 , the billing destination terminal device 5 , and the financial institution server 6 . The input unit 77 is a terminal or the like for inputting data from the outside. The memory 79 stores the program executed by the processing unit 61 . The processing unit 81 executes the program PRG2 stored in the memory 59 to perform the processing of the payment agent server 11 defined in this embodiment.

[0050] As described above, the payment agent server 11 allows payment to be made using a payment method based on the rules desired by the biller. This allows the biller to settle the transaction at the fee and timing of payment desired.

[0051] Furthermore, by having the payment agent server 11 cooperate with the financial institution server 6 via API, a common API screen can be used even if the financial institutions to which the bill is to be billed are different.

[0052] This embodiment aims to revolutionize the process of withdrawing funds from a bank account in order to "change the norm of bank account payments." Through API connections with online banks and other mechanisms, it is possible to popularize direct payments between bank accounts and expand innovation in the payment field. Payments are a business tool, and by utilizing innovative payment methods, it is possible to expand collaboration with business partners who offer a better user experience and financial institutions that aim to revitalize deposit accounts.

[0053] The present invention is not limited to the above-described embodiments. That is, those skilled in the art may make various modifications, combinations, subcombinations, and substitutions of the components of the above-described embodiments within the technical scope of the present invention or its equivalents. [Industrial Applicability]

[0054] The present invention is applicable to a payment agency system. [Explanation of symbols]

[0055] 1. Payment system 3…Billing device 5...Billing terminal device 6...Financial institution server 11...Payment agency server

Claims

1. A payment agent server used to settle a bill by a billing source to a billing recipient in response to a request from the billing source, a first step of receiving a first billing request from the billing source regarding a bill to be made by the billing source to the billee; a second step of generating a second billing request based on the first billing request received in the first step, the second billing request including link information relating to payment from the billing destination to the billing source; a third step of receiving access from the requestee based on link information included in the second request; a fourth step of displaying a payment screen to the billing destination in response to the access in the third step; a fifth step of receiving an instruction to select a financial institution from the billing recipient using the payment screen displayed in the fourth step; a sixth step of identifying the payment means to be used for the payment from among a plurality of payment means of the financial institution that received the selection instruction, based on a priority indicated by a rule previously defined by the requester related to the first request; a seventh step of making a payment by the payment means identified in the sixth step using the access token of the payment means; A payment processing server that executes the above.

2. The seventh step performs processing to transfer the amount of the claim indicated in the first claim request from the claim recipient to the claim source using the access token of the payment means identified in the sixth step or an authentication process individually designated by the financial institution. The payment agent server according to claim 1.

3. an eighth step of determining whether the access token of the payment means identified in the sixth step or an authentication process designated by the financial institution is held; a ninth step of displaying an authentication screen by the financial institution to the billing destination when it is determined in the eighth step that the financial destination does not have the access token, and acquiring the access token or an authentication process designated by the financial institution through authentication by the billing destination using the authentication screen; and The seventh step is to perform payment by the payment means using the access token acquired in the ninth step or an authentication process designated by the financial institution. The payment agent server according to claim 2.

4. a tenth step of determining that the access token is held in the eighth step, making a payment using the payment means based on the access token or an authentication process designated by the financial institution in the seventh step, and if the payment fails, making a payment using the payment means based on the access token of a payment means having the next highest priority according to the rule among the plurality of payment means or an authentication process individually designated by the financial institution; Do more The payment agent server according to claim 3.

5. The failure of the payment is due to the expiration of the access token or the authentication process designated by the financial institution, or the unavailability of the specified payment method. The payment agent server according to claim 4.

6. A payment agent method used to act on behalf of a billing source to settle a bill to a billing recipient in response to a request from the billing source, a first step of receiving a first billing request from the billing source regarding a bill to be made by the billing source to the billee; a second step of generating a second billing request based on the first billing request received in the first step, the second billing request including link information relating to payment from the billing destination to the billing source; a third step of receiving access from the requestee based on link information included in the second request; a fourth step of displaying a payment screen to the billing destination in response to the access in the third step; a fifth step of receiving an instruction to select a financial institution from the billing recipient using the payment screen displayed in the fourth step; a sixth step of identifying the payment means to be used for the payment from among a plurality of payment means of the financial institution that received the selection instruction, based on a priority indicated by a rule previously defined by the requester related to the first request; a seventh step of making a payment by the payment means identified in the sixth step using the access token of the payment means; A payment processing method in which the above is performed by a computer.

7. A program used to settle a bill by a billing source to a billing recipient in response to a request from the billing source, a first step of receiving a first billing request from the billing source regarding a bill to be made by the billing source to the billee; a second step of generating a second billing request based on the first billing request received in the first step, the second billing request including link information relating to payment from the billing destination to the billing source; a third step of receiving access from the requestee based on link information included in the second request; a fourth step of displaying a payment screen to the billing destination in response to the access in the third step; a fifth step of receiving an instruction to select a financial institution from the billing recipient using the payment screen displayed in the fourth step; a sixth step of identifying the payment means to be used for the payment from among a plurality of payment means of the financial institution that received the selection instruction, based on a priority indicated by a rule previously defined by the requester related to the first request; a seventh step of making a payment by the payment means identified in the sixth step using the access token of the payment means; A program that causes a computer to execute the following.

Images