JP7569425B1 - Payment processing device, payment processing method, and program - Google Patents

Abstract

[Problem] A payment processing device executes a deposit process to a supplier account on the same day that the price is debited from a buyer account by direct debit. [Solution] A payment processing device includes a memory unit and a control unit. The control unit executes the following: sending a direct debit request including at least information on the debit date to a direct debit system; receiving result information of the direct debit executed based on the direct debit request and storing it in the memory unit, the result information including at least information on the debit date; generating transfer data including at least information on the debit date, source account, destination account and amount, and generating a transfer message based on the transfer data. The source account is an account for which an overdraft limit has been set. The control unit reads out the debit date data from the billing information in the memory unit, and generates a direct debit request based on the information on the creditor account and debtor account obtained based on the read data, and the debit date and billing amount information in the read data. [Selected Figure] Figure 6

Description

The present invention relates to a payment processing device, a payment processing method, and a program. More specifically, the present invention relates to a payment processing device, a payment processing method, and a program that executes a deposit process to a deposit account on the same day that funds are debited from a debit account by account transfer.

In the field of business-to-business (BtoB) transactions, financial institutions are involved in the operation of transferring funds from buyers (debtors) to suppliers (creditors). Account transfer (also called "direct debit") is known as a payment method for business-to-business transactions (Patent Document 1). Direct debit is a transfer of funds that takes place under specified conditions between a buyer, supplier, collection agent, and financial institution, in which a direct debit is made from the buyer's account (debit account) and the withdrawn funds are deposited in the supplier's account (deposit account) via the collection agent.

Patent No. 5334394

In the conventional scheme where a collection agency was used to collect payments from buyers, it took several business days for the funds to be deposited in the supplier's account after the payment was debited from the buyer's account. In the conventional scheme, funds moved from the buyer's account → collecting bank account → collection agency account → supplier's account, but because there were periods when the funds were held up in the collecting bank account and collection agency account, it took several business days for the funds to reach the supplier.

Suppliers often need to have cash on hand. Because it takes several days for direct debit payments to be received, direct debit has not been widely used as a funds transfer scheme.

The present invention has been made to solve these problems, and aims to provide a payment processing device, a payment processing method, and a program that executes a deposit process to a supplier account on the same day that the price is debited from a buyer account by direct debit.

In order to solve the above problems, the present invention provides a payment processing device including a communication unit for communicating with an external network, a storage unit, and a control unit,
The storage unit stores billing information and funds transfer information;
The control unit is
Transmitting an account transfer request including at least information on a deduction date to an account transfer system via the communication unit;
receiving result information of the account transfer executed based on the account transfer request and storing the result information in the storage unit, the result information including at least information on the withdrawal date;
The method generates transfer data including at least information on the deduction date, the source account, the destination account, and the amount, and generates a transfer message based on the transfer data, the source account being an account for which an overdraft limit has been set.

According to the present invention, the payment processing device can execute the process of depositing money into the supplier's account on the same day that the supplier's account transfer request is processed. This allows the supplier to collect payment promptly.

A more detailed understanding of the embodiments disclosed herein can be had from the following description, taken in conjunction with the accompanying drawings, in which:
1 is a configuration diagram of an entire system including a payment processing device 10. 1 is a system configuration diagram of a payment processing device 10. FIG. 3 is a diagram showing an example of a data structure of a user master 106. FIG. 13 is a diagram showing an example of a data structure of contract/payment information 107. FIG. FIG. 2 is a diagram showing an example of the data structure of billing and funds transfer data 108. FIG. 13 is a diagram illustrating a process for depositing the amount debited from a buyer's account into a supplier's account on the same day. FIG. 7 is a diagram for explaining the process flow of FIG. 6 together with the flow of funds.

(Overall composition)
1 is a configuration diagram of an entire system including a payment processing device 10 according to an embodiment of the present invention, an account transfer system 11, a first bank system 12, and a second bank system 13. The payment processing device 10, the account transfer system 11, the first bank system 12, and the second bank system 13 are connected to each other via an arbitrary network 14 so as to be able to communicate with each other.

In this specification, the payment processing device 10 is described as a single system or device, but the various processes performed by the payment processing device 10 may be configured to be distributed and executed by multiple systems or devices.

The payment processing device 10 and the account transfer system 11 are described as systems independent of the financial institution's system, but the functions of both may be implemented within the financial institution's system (e.g., the second bank system 13).

The payment processing device 10 is a device used for payment-related processing of business-to-business transactions, and stores information such as billing detail data for transactions between suppliers and buyers, and business-to-business transaction contract data for the suppliers and buyers. This specification describes same-day deposit processing of a collection agency service executed by the payment processing device 10. In detail, the payment processing device 10 generates account transfer request data by the deduction date based on the billing detail data for transactions between suppliers and buyers and the business-to-business transaction contract data for the suppliers and buyers, and transmits it to the account transfer system 11. The account transfer request data includes information such as the deduction account and the deduction amount. When the payment processing device 10 receives the account transfer result data from the account transfer system 11, it generates a transfer message and transmits it to the second bank system 13.

The first bank system 12 and the second bank system 13 are bank systems such as accounting systems controlled by financial institutions. The first bank system 12 is the buyer's bank system, manages the buyer's account, and performs deposit and withdrawal processing for the buyer's account. The second bank system 13 is the supplier's and collection agent's bank system, manages the supplier's and collection agent's accounts, and performs deposit and withdrawal processing for the supplier's and collection agent's accounts. If the buyer's bank and the supplier's and collection agent's bank are the same financial institution, the first bank system 12 and the second bank system 13 are the same system.

When the account transfer system 11 receives the account transfer request data, it generates an account transfer message by the debit date and sends it to the first bank system 12. The account transfer message includes information on the debit date, the debit account, and the debit amount. The first bank system 12 executes the account transfer process (account debit process) based on the account transfer message, generates an account transfer result, and sends it to the account transfer system 11. The account transfer system 11 sends the contents of the first account transfer result received from the first bank system 12 to the payment processing device 10.

The funds debited by the first bank system 12 are deposited in the collection agent's account via a specified account (e.g., a collection bank account such as a separate account) in the first bank system 12. The debited funds are then deposited from the collection agent's account in the first bank system 12 to the collection agent's account in the second bank system 13. The second bank system 13 transfers the funds to the supplier's account before they arrive in the collection agent's account.

(System configuration of payment processing device 10)
FIG. 2 is a system configuration diagram of the payment processing device 10 according to the embodiment of the present invention. As shown in FIG. 2, the payment processing device 10 includes a control unit 101, a main memory unit 102, an auxiliary memory unit 103, an IF unit 104, and an output unit 105, which are connected to each other by a bus 120 or the like, like a general computer. The auxiliary memory unit 103 stores programs that implement each function of the payment processing device 10 and data handled by the programs. The various programs stored in the auxiliary memory unit 103 are executed by the payment processing device 10. The auxiliary memory unit 103 includes a user master 106, contract/payment information 107, and billing and funds transfer data 108 in the form of a file/database or the like. The payment processing device 10 can read, edit, or update the information stored in the user master 106, contract/payment information 107, and billing and funds transfer data 108.

The control unit 101, also called the central processing unit (CPU), controls each component of the payment processing device 10 and performs data calculations, and also reads out and executes various programs stored in the auxiliary storage unit 103 into the main storage unit 102. The main storage unit 102, also called the main memory, stores various received data, computer-executable instructions, and data after calculation processing based on those instructions. The auxiliary storage unit 103 is a storage device such as a hard disk drive (HDD), and is used for long-term storage of data and programs.

The embodiment in FIG. 2 describes an embodiment in which the control unit 101, main memory unit 102, and auxiliary memory unit 103 are provided inside the same computer, but in another embodiment, the payment processing device 10 can be configured to realize parallel distributed processing by multiple computers by using multiple control units 101, main memory units 102, and auxiliary memory units 103. In another embodiment, it is also possible to install multiple servers for the payment processing device 10, and have the multiple servers share a single auxiliary memory unit 103.

The IF unit 104 acts as an interface (IF) when sending and receiving data with other systems and devices, and also provides an interface that accepts various commands and input data (various masters, tables, etc.) from the system operator. The output unit 105 provides a display screen that displays the processed data and a printing means for printing the data.

The user master 106 stores information on users such as suppliers and buyers who use the payment processing device 10. FIG. 3 is a diagram showing an example of the data structure of the user master 106 according to an embodiment of the present invention. The user master 106 may include a user ID 301, a user name 302, and a payment account 303, but is not limited to these data items and may also include other data items.

The user ID 301 is an identifier that identifies a user who uses the payment processing device 10, such as a supplier or buyer in a business-to-business transaction, or a collection agent. The user name 302 indicates the name of the user (such as the company name). The payment account 303 indicates the user's account information used when processing deposits and withdrawals.

For the settlement accounts of the collection agent that are stored in the second bank system 13, an overdraft limit is set by the financial institution. Overdraft is a service that allows the shortfall in the deposit balance to be automatically borrowed. Accounts with an overdraft limit are allowed to have a deficit, i.e., a negative balance (for example, a balance of -1 million yen).

Returning to FIG. 2, the contract/payment information 107 stores contract information and payment information relating to transactions between suppliers and buyers in business-to-business transactions. FIG. 4 is a diagram showing an example of the data structure of the contract/payment information 107 according to an embodiment of the present invention. The contract/payment information 107 may include a supplier ID 401, a buyer ID 402, and payment terms 403, but is not limited to these data items and may also include other data items.

The supplier ID 401 is an identifier that indicates a supplier in a business-to-business transaction. The buyer ID 402 is an identifier that indicates a buyer in a business-to-business transaction. The identifier set as the supplier ID 401 and the buyer ID 402 may be the user ID 301. The payment terms 403 may be payment terms that have been agreed upon in advance between the supplier and the buyer, such as the payment date.

Returning to FIG. 2, billing and funds transfer data 108 stores billing information and funds transfer information related to transactions between suppliers and buyers. FIG. 5 is a diagram showing an example of the data structure of billing and funds transfer data 108 according to an embodiment of the present invention. Billing and funds transfer data 108 can include supplier ID 401, buyer ID 402, billing number 501, billing details 502, billing amount 503, payment date 504, account transfer request information 505, account transfer result information 506, and transfer data 507, but is not limited to these data items and can also include other data items.

The supplier ID 401 is an identifier indicating the supplier related to the billing information. The buyer ID 402 is an identifier indicating the buyer related to the billing information. With respect to the billing information, the supplier is the creditor and the buyer is the debtor. The billing number 501 is an identifier that identifies the billing information. The billing content 502 indicates the content of the bill (e.g., the cost of goods, the cost of services). The billing amount 503 indicates the amount billed by the supplier to the buyer. The payment date 504 indicates the payment date for the bill, that is, the deduction date when the billing amount is debited from the buyer account. The account transfer request information 505 includes information on the account transfer request created based on the billing information, and includes information such as the buyer account (also called the "debtor account") which is the debit account, the deduction amount, etc. The account transfer result information 506 includes result information of the account transfer process executed based on the account transfer request. The result information includes information such as whether the deduction was successful or not due to insufficient balance, as well as information such as the deduction account. The transfer data 507 includes information on the deposit process from the collection agent account to the supplier account, which is executed after the account transfer process is successfully completed.

(The process of debiting the buyer's account and depositing the amount into the supplier's account on the same day)
6 is a diagram explaining the process of depositing the amount debited from the buyer's account to the supplier's account on the same day. As a premise of this process, it is assumed that the payment processor 10 stores billing information data on the transaction between the supplier and the buyer in the billing and funds transfer data 108, and that the payment account of the collection agent stored in the second bank system 13 has an overdraft limit set and is allowed to have a negative balance.

In S601, the payment processing device 10 reads data from the billing and funds transfer data 108 in which the deduction date indicated by the payment date 504 falls within a predetermined period, queries the user master 106 based on the supplier ID 401 and buyer ID 402 of the read data, and obtains the supplier's settlement account and the buyer's settlement account. The predetermined period includes at least the date on which the processing date on which the processing flow of FIG. 6 is performed and the deduction date indicated by the payment date 504 match, and may additionally include dates in the range up to the next business day for the deduction date indicated by the payment date 504 if the day after the processing date on which the processing flow of FIG. 6 is performed is not a business day. For example, if the processing date is Friday, July 28, 2023, data indicating Friday, July 28, 2023 for the payment date 504 and additionally data indicating Monday, July 31, 2023 for the payment date 504 may be read.

The payment processing device 10 generates an account transfer request based on the acquired supplier payment account and buyer payment account, and the information on the billing amount 503 and payment date 504 from the read data, and stores this in the account transfer request information 505. The account transfer request includes at least the deduction date, buyer payment account (debtor account), and billing amount. If the deduction date indicated by the payment date 504 is not a business day of the financial institution, the actual deduction date will be the next business day.

At S602, the payment processing device 10 sends the generated account transfer request to the account transfer system 11.

At S603, when the account transfer system 11 receives an account transfer request from the payment processing device 10, it reads out the information of the received account transfer request and generates an account transfer message. The account transfer message is associated with the account transfer request and may include information on the requester in addition to the deduction date, buyer settlement account, and billing amount. The transaction bank account of the account transfer message, i.e., the bank account to which the funds are to be transferred, is the settlement account of the collection agent of the first bank system 12.

At S604, the account transfer system 11 sends the account transfer message to the first bank system 12 of the financial institution associated with the debit account included in the account transfer message, i.e., the buyer settlement account.

At S605, when the first bank system 12 receives the account transfer message, it checks the balance of the debit account (buyer settlement account) based on the information of the debit account included in the received account transfer message, and if the balance is sufficient, it executes the process of debiting the invoice amount from the debit account. In other words, the first bank system 12 executes the account debit process on the debit date included in the account transfer message. The debited funds are temporarily deposited into a receiving bank account such as a separate account of the first bank system 12, and then deposited into the collection agent account of the first bank system 12. The first bank system 12 transfers the money from the collection agent account of the first bank system 12 to the collection agent account of the second bank system 13.

At S606, the first bank system 12 generates a first account transfer result based on the information in the received account transfer message and the result of the account debit process, and transmits it to the account transfer system 11. The first account transfer result is associated with the account transfer message, and can therefore include the debit account (buyer settlement account), the debit amount, the account transfer process result, and information for identifying the account transfer message.

At S607, the account transfer system 11 generates a second account transfer result based on the received information on the first account transfer result and the account transfer request information identified from the account transfer message associated with the first account transfer result, and transmits the second account transfer result to the payment processing device 10.

In S608, when the payment processing device 10 receives the second account transfer result from the account transfer system 11, it stores information on the second account transfer result in the account transfer result information 506 of the data associated with the second account transfer result. The second account transfer result can include the deduction date, the deduction account (buyer payment account), the deduction amount, and the account transfer processing result. Note that the deposit account of the account transfer result is not the supplier payment account, but the collection agent account with an overdraft limit set, into which the money will actually be deposited by the account transfer processing. The processing from S609 onwards is executed only if the account transfer processing result indicates success.

At S609, the payment processing device 10 generates transfer data based on the information in the account transfer result information 506 read from the billing and funds transfer data 108, and stores the data in the transfer data 507. The transfer data has the transfer date as the account transfer debit date, the transfer destination as the supplier payment account, the transfer source as the collection agent's account (an account with an overdraft limit set), and the transfer amount as the debit amount, i.e., the billing amount minus the amount for which the account transfer process was unsuccessful.

At S610, the payment processing device 10 generates a transfer message conforming to the all-banks format based on the generated transfer data, and transmits it to the second bank system 13 having the source account. The all-banks format of the transfer message may be a format for transfer of funds. The source account is a collection agent account with an overdraft limit set.

At S611, the second bank system 13 executes a transfer process from the collection agent's account to the supplier's payment account based on the transfer message received from the payment processing device 10. Through the above process, on the day the account transfer process is executed, a notice of direct debit is received by the payment processing device 10, and the supplier's account is deposited. The collection agent's account will initially have a negative balance, but the funds transferred from the collection agent's account in the first bank system 12 to the collection agent's account in the second bank system 13 will then be deposited, and the negative balance will be eliminated after the deposit.

Figure 7 is a diagram explaining the processing flow of Figure 6 together with the flow of funds. In Figure 7, the day of processing is explained as day N.

As explained in S604 of FIG. 6, a direct debit message based on a direct debit request from the payment processing device 10 is sent from the account transfer system 11 to the first bank system 12 (Nth day). As explained in S605, in response to receiving the direct debit message, the first bank system 12 debits the invoice amount from the withdrawal account (buyer settlement account) (funds debit (Nth day)) and deposits the amount into the collection agent account of the first bank system 12 (funds deposit (Nth day or N+1th day)).

Meanwhile, after the account debit process, the first bank system 12 notifies the processing result as described in S606 to S607. That is, the first direct debit result is transmitted (Nth day) and the second direct debit result is transmitted (Nth day).

As explained in S609 to S611 of FIG. 6, the payment processing device 10 generates a transfer message and sends it to the second bank system 13 (Nth day), and then the second bank system 13 executes the transfer process from the agent account, which has an overdraft limit, to the supplier account in accordance with the transfer message (Nth day).

When a transfer process is executed, the balance of the agent account with the overdraft limit set will be in the red, but the second bank system 13 will clear the red balance by receiving a transfer from the first bank system 12 (N+2 days).

In the example of Figure 7, the second bank system 13 has two types of agent accounts: an account with an overdraft limit and an account that receives deposits from other financial institutions.

In the above process, it is assumed that funds debited from multiple buyer accounts are deposited into the same supplier account on the same day. In such a case, when generating the transfer data in S609, the payment processing device 10 can merge the deposit information for the same supplier account to generate a single transfer data.

For example, consider a case where supplier A collects 100,000 yen from buyer X and 150,000 yen from buyer Y by account transfer. The first bank system 12 sends the results of each transfer to the account transfer system 11, which sends the results to the payment processor 10. The payment processor 10 adds up the billing amounts for data with the same deposit account among the information in the account transfer result information 506 read from the billing and funds transfer data 108, creates transfer data with the transfer destination set to the supplier payment account and the transfer source set to the collection agent's account, and the transfer amount set to the combined amount, and sends this transfer data to the second bank system 13. This transfer data indicates that a combined amount of 250,000 yen is to be deposited into supplier A's account.

The above process allows the payment processing device 10 to know that the payment has been debited from the buyer's account on the day of the debit, and allows the collection agent to transfer the collected funds to the supplier's account before they actually arrive at the collection agent's account, making it possible to deposit the money into the supplier's account on the same day that the payment is debited from the buyer's account.

The principles of the present invention have been described above with reference to exemplary embodiments, but those skilled in the art will understand that various embodiments that change the configuration and details can be realized without departing from the gist of the present invention. In other words, the present invention can be embodied, for example, as a system, device, method, program, or storage medium.

REFERENCE SIGNS LIST 10 Payment processing device 11 Account transfer system 12 First bank system 13 Second bank system 14 Network 101 Control unit 102 Main memory unit 103 Auxiliary memory unit 104 IF unit 105 Output unit 106 User master 107 Contract/payment information 108 Billing and fund transfer data

Claims (4)

A payment processing device including a communication unit for communicating with an external network, a storage unit, and a control unit,
The storage unit stores a user master including user information and user account information, billing information, and fund transfer information;
The control unit is
reading data whose withdrawal date falls within a predetermined period from said billing information and fund transfer information, and making an inquiry to said user master based on the creditor information and debtor information included in said read data to obtain creditor accounts and debtor accounts;
generating an account transfer request including the acquired creditor account and debtor account information and the deduction date and billing amount information included in the read data , storing the generated account transfer request in the billing information and funds transfer information, and transmitting the account transfer request to the account transfer system via the communication unit;
receiving from the account transfer system result information of the account transfer executed based on the account transfer request, and storing the result information in the billing information and fund transfer information , the result information including information of the debit date , the debit amount, the debtor account as a debit account, and the business account with an overdraft facility as a final deposit account , associated with the account transfer executed based on the account transfer request ;
generating transfer data including information on the deduction date as the transfer date , the business account as the transfer source account, the creditor account as the transfer destination account, and the deduction amount as the transfer amount, which are read from the billing information and the fund transfer information, and generating a transfer message based on the transfer data, wherein the business account and the creditor account are accounts managed by the same financial institution ;
Transmitting the generated transfer message to a bank system associated with the transfer source account;
A payment processor that executes the above. The creditor account indicates an account of a supplier that is a creditor in a business-to-business transaction associated with the billing information and the fund transfer information ;
the debtor account indicates an account of a buyer who is a debtor in a business-to-business transaction associated with the billing information and funds transfer information ;
The payment processing device of claim 1 . 1. A method performed by a payment processor, comprising:
The payment processing device includes a communication unit for communicating with an external network, a storage unit, and a control unit, the storage unit stores a user master including user information and user account information, billing information, and fund transfer information, and the method includes:
The control unit reads data whose withdrawal date falls within a predetermined period from the billing information and fund transfer information, and queries the user master based on the creditor information and debtor information contained in the read data to obtain the creditor account and debtor account;
the control unit generates an account transfer request including the acquired information on the creditor account and the debtor account, and the information on the deduction date and the billing amount included in the read data, stores the generated account transfer request in the billing information and the funds transfer information, and transmits the request to the account transfer system via the communication unit;
The control unit receives from the account transfer system result information of the account transfer executed based on the account transfer request, and stores it in the billing information and the fund transfer information , the result information including information of the deduction date , the deduction amount, the debtor's account as a deduction account, and the business account with an overdraft facility as a final deposit account, which are associated with the account transfer executed based on the account transfer request ;
the control unit generates transfer data including information on the deduction date as the transfer date , the business account as the transfer source account, the creditor account as the transfer destination account, and the deduction amount as the transfer amount, which are read from the billing information and the fund transfer information, and generates a transfer message based on the transfer data, wherein the business account and the creditor account are accounts managed by the same financial institution ;
The control unit transmits the generated transfer message to a bank system associated with the transfer source account;
A method for providing the above. A program for causing a computer to execute the method according to claim 3 .

Images