JP7766508B2 - Information processing system, information processing method, and information processing program - Google Patents

Description

The present invention relates to an information processing system, an information processing method, and an information processing program.

Technologies have been proposed to transfer value information such as electronic money via various networks, such as the Internet, and collect a specified billing amount.

The program described in Patent Document 1 provides billing information to the user and, based on the user's operation, executes a settlement process to pay the billed amount indicated in the billing information by transferring electronic money or the like. As a result, the program transfers value information from a specified account and collects the specified billed amount.

Patent No. 6880165

However, the program described in Patent Document 1 requires user operation when executing the payment process, which poses the problem of not being able to smoothly store value information.

Therefore, the present invention aims to provide an information processing system, information processing method, and information processing program that enable smooth storage of value information.

An information processing system according to one aspect of the present invention includes a first billing data acquisition unit that acquires, from a first information processing system, first billing data for collecting a specified billing amount from a user's account managed by a funds transfer service provider. The first billing data is billing data generated in a first data format compatible with a first information processing system of the collection service provider that collects the specified billing amount. A format conversion unit that converts the first billing data into second billing data in a second data format that is compatible with a second information processing system of the funds transfer service provider and is a data format different from the first data format. A deduction request transmission unit that transmits a deduction request to the second information processing system to execute a deduction process that deducts the specified billing amount from the account based on the second billing data. A deduction result data acquisition unit that acquires, from the second information processing system, deduction result data indicating the results of the deduction process. A transfer instruction data transmission unit that transmits, to the first information processing system, transfer instruction data for executing a transfer process that transfers the specified billing amount from the funds transfer service provider to the collection service provider based on the deduction result data.

In one aspect of the present invention, an information processing method involves a computer acquiring, from a first information processing system, first billing data for collecting a specified billing amount from a user's account managed by a funds transfer service provider, the first billing data being generated in a first data format compatible with the first information processing system of the collection service provider that collects the specified billing amount; converting the first billing data into second billing data in a second data format compatible with the second information processing system of the funds transfer service provider but different from the first data format; sending a deduction request to the second information processing system to execute a deduction process to deduct the specified billing amount from the account based on the second billing data; acquiring deduction result data from the second information processing system indicating the results of the deduction process; and sending transfer instruction data to the first information processing system to execute a transfer process to transfer the specified billing amount from the funds transfer service provider to the collection service provider based on the deduction result data.

An information processing program according to one aspect of the present invention runs on a computer and includes the following: a first billing data acquisition unit that acquires, from a first information processing system, first billing data for collecting a specified billing amount from a user's account managed by a funds transfer service provider, the first billing data being billing data generated in a first data format compatible with a first information processing system of the collection service provider that collects the specified billing amount; a format conversion unit that converts the first billing data into second billing data in a second data format compatible with a second information processing system of the funds transfer service provider but different from the first data format; a deduction request transmission unit that transmits to the second information processing system a deduction request to execute a deduction process that deducts the specified billing amount from the account based on the second billing data; a deduction result data acquisition unit that acquires from the second information processing system deduction result data indicating the results of the deduction process; and a transfer instruction data transmission unit that transmits to the first information processing system transfer instruction data for executing a transfer process to transfer the specified billing amount from the funds transfer service provider to the collection service provider based on the deduction result data.

In this invention, the term "unit" does not simply mean a physical means, but also includes cases where the functions of that "unit" are realized by software. Furthermore, the functions of a single "unit" or device may be realized by two or more physical means or devices, and the functions of two or more "units" or devices may be realized by a single physical means or device.

The present invention makes it possible to provide an information processing system, information processing method, and information processing program that enable smooth storage of value information.

1 is a diagram showing the configuration of a storage processing system 100 according to an embodiment of the present invention. 10 is a diagram showing an example of first billing data stored in the storage unit 111. FIG. FIG. 10 is a diagram showing an example of second billing data stored in the storage unit 111. 10 is a diagram showing an example of data for determining whether or not a request is accepted stored in a storage unit 111. FIG. FIG. 10 is a diagram showing an example of reduction result data stored in the storage unit 111. 10 is a diagram showing an example of movement instruction data stored in a storage unit 111. FIG. 10 is a flowchart showing an example of processing in the storage processing system 100. 10 is a flowchart showing an example of a third billing data generation process in the collection processing system 100. 10 is a flowchart showing an example of a third billing data generation process when error information is acquired in the storage processing system 100. FIG. 9 illustrates an example of the hardware configuration of a computer 900.

A preferred embodiment of the present invention will be described with reference to the accompanying drawings. Figure 1 shows the configuration of a storage processing system 100, which is one embodiment of the present invention.

The storage processing system 100 is a system that is communicatively connected to the first information processing system 200 and the second information processing system 300 via a network such as the Internet.

The collection processing system 100, for example, performs processing to convert data formats between the collection agent and the funds transfer agent, and to determine whether collection is possible, so that the collection agent can collect the specified billing amount from the user using value information. In this way, the collection processing system 100 improves the convenience of payments for collection agents and users, and enables smooth collection of value information. Details of the collection processing system 100 will be provided later.

The first information processing system 200 is, for example, an information processing system of a collection agency. The collection agency uses the first information processing system 200 to collect a specified invoice amount from a user on behalf of a biller who makes a specified invoice to the user, and provides the collected amount to the biller. Specifically, for example, in relation to payment for a subscription-based service subscribed to by the user, the collection agency collects a specified invoice amount (e.g., a monthly fee) from a user's account, etc., on behalf of a service provider, and transfers the collected invoice amount to the service provider's account.

The second information processing system 300 is, for example, an information processing system for a funds transfer service provider. The funds transfer service provider uses the second information processing system 300 to obtain money from the user via a predetermined method such as a bank, and adds the corresponding amount of value information (e.g., electronic money or points) to the user's account. In other words, the funds transfer service provider manages the electronic money and points held by the user, and performs payment processing, etc., using the electronic money or points as necessary.

Note that while Figure 1 shows one second information processing system 300, there may be multiple second information processing systems 300, and each of the multiple second information processing systems 300 may correspond to a respective one of multiple money transfer service providers.

Next, an overview of the processing of the collection processing system 100 will be explained. The collection processing system 100 acquires first billing data from the first information processing system 200 of the collection agent. Based on the first billing data, the collection processing system 100 collects the specified billing amount from the user's account managed by the funds transfer agent. Hereinafter, the process of collecting the specified billing amount from the user's account will be referred to as the "collection process."

Specifically, the collection processing system 100 converts the first billing data in a first data format into second billing data in a second data format compatible with the second information processing system 300. The collection processing system 100 transmits a reduction request to the second information processing system 300 to execute a reduction process that reduces the billing amount indicated by the second billing data. In other words, by converting billing data in a data format used by the collection agent into billing data in a data format used by the funds transfer agent, the collection processing system 100 can achieve smooth collection of value information by the second information processing system.

The collection processing system 100 then obtains deduction result data indicating the results of the deduction process from the second information processing system 300. The collection processing system 100 determines, for example, based on the deduction result data, whether the deduction process is possible from the user's account at the funds transfer service provider. Based on the determination result, the collection processing system 100 transmits transfer instruction data to the first information processing system 200 to execute a transfer process to transfer the invoice amount from the funds transfer service provider to the collection service provider. In other words, the collection processing system 100 can reliably transfer the invoice amount from the funds transfer service provider to the collection service provider when the funds transfer service provider is able to collect value information corresponding to the invoice amount.

Next, the detailed configuration of the collection processing system 100 will be described. The collection processing system 100 comprises a memory unit 111, a first billing data acquisition unit 121, a format conversion unit 122, a data generation unit for feasibility determination 131, a data transmission unit for feasibility determination 132, a collection feasibility determination unit 133, a first determination unit 134, a reduction request transmission unit 135, a reduction result data acquisition unit 136, a transfer instruction data generation unit 141, a second determination unit 142, a transfer instruction data transmission unit 143, an error acquisition unit 151, a third billing data generation unit 152, and a third billing data transmission unit 153. The computer that constitutes the collection processing system 100 comprises a processor and a memory area. Each unit shown in FIG. 1 can be realized, for example, by using the memory area or by the processor executing a program stored in the memory area.

The memory unit 111 stores data acquired and generated by the collection processing system 100. As described below, the memory unit 111 stores, for example, first billing data, second billing data, data for determining whether or not a claim is accepted, deduction result data, transfer instruction data, and third billing data.

The first billing data acquisition unit 121 acquires the first billing data from the first information processing system 200 and stores it in the memory unit 111.

Here, the first billing data is billing data for collecting a specified billing amount from a user's account managed by the funds transfer service provider. The first billing data is billing data generated in a first data format corresponding to the first information processing system 200 of the collection service provider that collects the specified billing amount.

Here, the first data format corresponding to the first information processing system 200 is a data format that can be processed by the first information processing system 200, for example, a data format that allows collection processing or processing related to collection processing in the first information processing system 200. The first data format may be, for example, a CSV (Comma Separated Value) format, or a JBA-specified format established by the Japanese Bankers Association (JBA) for the exchange of online data between companies and banks using the JBA standard communication protocol.

Figure 2 shows an example of first billing data stored in memory unit 111. The first billing data stored in memory unit 111 includes, for example, a collection ID, billing destination information, account information, billing amount information, and billing source information.

The storage ID is information that identifies the billing data obtained from the first information processing system 200.

Billing information is information associated with the deposit ID and is information about the funds transfer service provider that manages the account of the user for whom the deposit process is performed. The billing information may be information indicating the name of a service provided by the funds transfer service provider, such as "XX Pay," or it may be information indicating the name of the funds transfer service provider. The billing information may also be information that identifies the name of a service provided by the funds transfer service provider or the name of the funds transfer service provider (for example, a code consisting of a four-digit number string).

Account information is information associated with the deposit ID and is information related to the user's account. Account information may be any information that can identify the user's account at the funds transfer service provider, and may include, for example, a branch code indicating the branch name of the funds transfer service provider.

Billing amount information is information indicating the billing amount that is the subject of collection processing. Billing source information is information about the billing source in collection processing, such as information indicating the service used by the user (e.g., "XX Pay"), the business providing the service (e.g., the business providing "XX Pay"), or the collection agent.

The first billing data may be stored in the memory unit 111 in a format specified by the Japanese Bankers Association, or may be stored in the memory unit 111 in a format different from the Japanese Bankers Association format.

The format conversion unit 122 converts the first billing data in a first data format into second billing data in a second data format that is compatible with the second information processing system 300 but is different from the first data format. The format conversion unit 122 stores the second billing data in the storage unit 111. Here, the data format compatible with the second information processing system 300 is a data format that can be processed by the second information processing system 300, for example, a data format that allows collection processing or processing related to collection processing in the second information processing system 300.

If the first data format corresponding to the first information processing system 200 (i.e., the first data format that can be processed by the first information processing system 200) differs from the second data format corresponding to the second information processing system 300 (i.e., the second data format that can be processed by the second information processing system 300), the data format of the first billing data sent from the first information processing system 200 must be converted into a data format that can be processed by the second information processing system 300.

Specifically, the second information processing system 300 may be unable to process the first billing data in a first data format (e.g., the format specified by the Japanese Bankers Association). Therefore, the format conversion unit 122 converts the first billing data into second billing data in a second data format that can be processed by the funds transfer service provider's second information processing system 300, and transmits the second billing data to the second information processing system 300. This allows the second information processing system 300 to perform collection processing based on the second billing data.

Furthermore, when requesting collection processing from each of the second information processing systems 300 of multiple funds transfer businesses, the format conversion unit 122 can convert the first invoice data into a data format compatible with each second information processing system 300. This allows the collection processing system 100 to perform collection processing compatible with each of the multiple funds transfer businesses.

Figure 3 is a diagram showing an example of second billing data stored in memory unit 111. The second billing data stored in memory unit 111 includes, for example, a collection ID, account information, billing amount information, and billing source information. The second billing data contains the same information content as the first billing data shown in Figure 2, so its description will be omitted.

The feasibility determination data generation unit 131 generates feasibility determination data for determining whether the specified billing amount can be collected from the user's account based on at least either the first billing data or the second billing data, and stores the data in the memory unit 111.

The feasibility determination data generation unit 131 may also generate feasibility determination data for determining whether a user account corresponding to the collection process exists in the second information processing system 300 based on at least one of the first billing data or the second billing data. In this case, the feasibility determination data may include account information related to the user's account.

The feasibility determination data generation unit 131 may also generate feasibility determination data based on at least one of the first billing data and the second billing data to determine whether the user's account has a balance corresponding to a specified billing amount. In this case, the feasibility determination data may include billing amount information indicating the billing amount that is the subject of the collection process.

The data generation unit 131 for determining whether or not a claim is accepted may store the second claim data in the storage unit 111 as data for determining whether or not a claim is accepted. In other words, the collection processing system 100 can use the second claim data as data for determining whether or not a claim is accepted, thereby realizing smooth collection of value information.

The feasibility determination data generation unit 131 may also generate feasibility determination data from the information contained in the second billing data, excluding information (e.g., billing source information) that is unnecessary when checking whether the user has an account or whether there is a balance in that account. This allows the collection processing system 100 to process only the data necessary to determine whether the specified billing amount can be collected from the user's account, thereby improving the processing speed and security of the collection processing system 100, for example.

The feasibility determination data transmission unit 132 transmits the feasibility determination data to the second information processing system 300.

Here, the second information processing system 300 determines whether or not it is possible to collect the specified billing amount from the user's account based on the feasibility determination data, and transmits the determination result to the collection processing system 100. Specifically, the second information processing system 300 determines, for example, based on the account information and billing amount information included in the feasibility determination data, whether or not the user has an account and whether or not there is a balance in the user's account corresponding to the specified billing amount, and transmits the determination result to the collection processing system 100.

The determination of whether or not a specified billing amount can be collected from the user's account may be performed by the collection processing system 100. In this case, the collection processing system 100 may, for example, obtain information indicating the balance corresponding to the user's account (hereinafter referred to as "balance information") from the second information processing system 300, and determine whether or not collection is possible by comparing the balance indicated by the balance information with the specified billing amount.

Figure 4 shows an example of the data for determining whether or not a payment is accepted that is stored in the memory unit 111. The data for determining whether or not a payment is accepted that is stored in the memory unit 111 includes, for example, a payment ID, account information, and billing amount information.

The collection possibility determination unit 133 determines whether or not it is possible to collect the specified billing amount from the user's account based on the determination result obtained from the second information processing system 300. The collection possibility determination unit 133 may obtain information such as "possible," "not possible," "account available," or "balance available" from the second information processing system 300, and may also obtain balance information for the user's account.

The collection feasibility determination unit 133 may determine whether a specified billing amount can be collected from the user's account, for example, based on balance information and billing amount information included in at least one of the first billing data or the second billing data.

If the collection possibility determination unit 133 determines that collection is possible, the reduction request transmission unit 135 (described later) transmits a reduction request to the second information processing system 300. Also, if the collection possibility determination unit 133 determines that collection is not possible, the third billing data transmission unit 153 (described later) transmits the third billing data generated by the third billing data generation unit 152 (described later) to the first information processing system 200.

The first determination unit 134 determines whether the billing amount indicated by the first billing data matches the billing amount indicated in the reduction request sent by the reduction request sending unit 135, which will be described later. At this time, the first determination unit 134 may also determine whether the user's account indicated by the first billing data matches the user's account indicated in the reduction request sent by the reduction request sending unit 135, which will be described later. This allows the billing amount indicated by the first billing data and the value information corresponding to the user's account to be deposited smoothly and accurately.

The reduction request sending unit 135 sends a reduction request to the second information processing system 300. Here, the reduction process is a process of reducing a specified billing amount from the user's account (i.e., a process of subtracting value information from the account). Furthermore, the reduction request is information for causing the second information processing system 300 to execute a reduction process that reduces the billing amount indicated by the second billing data.

The second information processing system 300 then executes a deduction process corresponding to the deduction request and deducts the billing amount indicated in the second billing data from the user's account. The second information processing system 300 then transmits deduction result data indicating the results of the deduction process to the receipt processing system 100.

The reduction request sending unit 135 may also send the second billing data to the second information processing system 300 as a reduction request. In this case, the second information processing system 300 executes the reduction process based on the second billing data. This allows the collection processing system 100 to use the second billing data as is as data for determining whether or not the value information can be collected, ensuring smooth collection of the value information.

The reduction request sending unit 135 may also convert the second billing data into a specified format and send the converted data to the second information processing system 300 as a reduction request. This allows the second information processing system 300 to perform the reduction process based on data in a format that can be processed by the second information processing system 300.

In addition, the reduction request sending unit 135 may send a reduction request to the second information processing system 300 if the collection feasibility determination unit 133 determines that collection is possible.

In addition, the reduction request sending unit 135 may send a reduction request to the second information processing system 300 when the first determination unit 134 determines that the billing amount indicated by the first billing data matches the billing amount indicated in the reduction request.

The reduction request sending unit 135 may also send a reduction request to the second information processing system 300 when the collection feasibility determination unit 133 determines that collection is possible and the first determination unit 134 determines that the claim amount indicated by the first claim data matches the claim amount indicated in the reduction request. This allows the collection processing system 100 to avoid situations where it is unable to collect the specified claim amount as much as possible, and to smoothly and accurately collect value information corresponding to the claim indicated by the first claim data.

The deduction result data acquisition unit 136 acquires deduction result data indicating the results of the deduction process from the second information processing system 300 and stores the deduction result data in the memory unit 111.

Figure 5 is a diagram showing an example of deduction result data stored in the memory unit 111. The deduction result data stored in the memory unit 111 includes, for example, a deduction result ID, account information, deduction information, billing source information, and collection ID. The deduction result ID is information that identifies the deduction result data stored in the memory unit 111. The deduction information is information that indicates the amount deducted by the deduction process in the second information processing system 300. The account information, billing source information, and collection ID are the same as those in the first billing data shown in Figure 2, so their description will be omitted.

Based on the deduction result data, the transfer instruction data generation unit 141 generates transfer instruction data for executing a transfer process to transfer the invoice amount indicated in the second invoice data from the funds transfer service provider to the collection service provider, and stores this data in the memory unit 111. Specifically, the transfer process is a process for transferring the invoice amount from the account of the funds transfer service provider to the account of the collection service provider. This allows the collection service provider to transfer the invoice amount received from the funds transfer service provider to the biller who will make the specified invoice to the user, thereby realizing the collection process.

The transfer process may involve, for example, transferring funds (including, for example, cash or virtual currency) corresponding to the invoice amount, or transferring value information corresponding to the invoice amount. The funds transfer service provider may also transfer the invoice amount to the invoicer who will make the specified invoice to the user, and then receive the invoice amount from the funds transfer service provider.

Figure 6 shows an example of transfer instruction data stored in the memory unit 111. The transfer instruction data stored in the memory unit 111 includes, for example, a transfer instruction ID, transfer source information, billing amount information, transfer destination information, and a reduction result ID.

The transfer instruction ID is information that identifies the transfer instruction data stored in memory unit 111. The transfer source information is information about the party from which the invoice amount will be transferred (i.e., the party that will be the payer) in the transfer process executed based on the transfer instruction data, such as a funds transfer service provider. The transfer destination information is information about the party that will receive the invoice amount (i.e., the party that will be the payee) in the transfer process executed based on the transfer instruction data, such as information indicating the service used by the user (e.g., "XX Pay") or the business that provides that service (e.g., the business that provides "XX Pay").

The transfer instruction data may be stored in the memory unit 111 in a data format specified by the Japanese Bankers Association.

The second determination unit 142 determines whether at least one of the billing amount indicated by the first billing data or the billing amount indicated by the reduction request matches the billing amount indicated by the transfer instruction data.

The transfer instruction data transmission unit 143 may transmit the transfer instruction data to the first information processing system 200, for example, when the second determination unit 142 determines that the transfer instruction data matches at least one of the billing amount indicated by the first billing data or the billing amount indicated by the reduction request. This allows the value information to be stored smoothly and accurately, even if the value information reduction process and the billing amount transfer process are executed separately.

When the first information processing system 200 receives movement instruction data from the movement instruction data transmission unit 143, it executes movement processing based on the movement instruction data, for example.

If it is determined that the billing amount indicated by the first billing data matches the billing amount indicated by the transfer instruction data, the transfer instruction data transmission unit 143 transmits the transfer instruction data to the first information processing system 200, allowing the collection processing system 100 to smoothly and accurately collect the value information corresponding to the billing amount indicated by the first billing data obtained from the first information processing system 200. If it is determined that the billing amount indicated by the reduction request matches the billing amount indicated by the transfer instruction data, the transfer instruction data transmission unit 143 transmits the transfer instruction data to the first information processing system 200, allowing the collection processing system 100 to smoothly and accurately collect the value information corresponding to the billing amount indicated by the reduction request transmitted to the second information processing system 300.

The error acquisition unit 151 acquires error information from the second information processing system 300. The error information is, for example, information indicating that the deduction process was not performed correctly in the second information processing system 300. The error information includes, for example, account information and billing amount information corresponding to the deduction process that was not performed correctly.

A situation in which the deduction process is not performed correctly in the second information processing system 300 may occur, for example, when the corresponding account no longer exists after the payment eligibility determination unit 133 determines whether payment is possible, or when the balance becomes less than the amount due.

The third billing data generation unit 152 generates third billing data to collect the specified billing amount from the user's account if the deduction process is not performed normally in the second information processing system.

Specifically, the third billing data generation unit 152 may generate the third billing data, for example, when the collection feasibility determination unit 133 determines that the specified billing amount cannot be collected from the user's account, or when the error acquisition unit 151 acquires error information. In this case, the third billing data generation unit 152 may generate the third billing data for collecting the specified billing amount from the user's account, for example, based on information that associates the user's account with the account.

Here, if the collection feasibility determination unit 133 determines that the specified billing amount cannot be collected from the user's account, the third billing data generation unit 152 can generate third billing data, for example, based on at least either the first billing data or the second billing data.

Specifically, the third billing data generation unit 152 may generate third billing data for collecting the billing amount corresponding to the billing amount information contained in at least one of the first billing data or the second billing data. This allows the collection processing system 100 to smoothly collect the corresponding billing amount even in the event that a situation arises in which the specified billing amount cannot be collected.

Furthermore, if the error acquisition unit 151 acquires error information, the collection eligibility determination unit 133 can generate third invoice data, for example, based on the error information.

Specifically, if the error information includes billing amount information corresponding to the deduction process in which an error occurred, the third billing data generation unit 152 may generate third billing data for collecting the billing amount corresponding to that billing amount information. This allows the collection processing system 100 to smoothly collect the corresponding billing amount even if an error occurs that prevents the deduction process based on the deduction request from being performed correctly.

Furthermore, if the error information includes account information corresponding to the deduction process in which an error occurred, the third billing data generation unit 152 may, for example, generate third billing data for collecting the billing amount corresponding to that account information based on the second billing data corresponding to the error information. This allows the collection processing system 100 to achieve smooth collection when an error occurs that prevents the deduction process based on the deduction request from being performed normally, even if the error information does not include billing amount information.

In addition, the information associating the user's account with the bank account may be set in advance in the collection processing system 100. Specifically, the collection processing system 100 may store information in advance that associates the user's account information with information related to the user's account (e.g., bank account number). The third billing data generation unit 152 of the collection processing system 100 may then identify the user's account corresponding to the user's account information based on at least one of the first billing data or the second billing data, or error information.

The third billing data generation unit 152 may generate the third billing data in a first data format (e.g., the format specified by the Japan Bankers Association), or may generate the third billing data in a second data format or another data format. This allows the collection processing system 100 to generate the third billing data in a data format that can be processed by the first information processing system 200, thereby enabling smooth collection.

The third billing data transmission unit 153 transmits the third billing data to the first information processing system 200. Upon receiving the third billing data, the first information processing system 200 performs a collection process to collect the specified billing amount from the user's account based on the third billing data.

Figure 7 is a flowchart showing an example of processing in the storage processing system 100.

First, the collection processing system 100 acquires from the first information processing system 200 first billing data for collecting a specified billing amount from the user's account (e.g., XX Pay ID), which is generated in a first data format (e.g., a format specified by the Japan Bankers Association or CSV format) (S701). The collection processing system 100 converts the first billing data into second billing data in a second data format (e.g., a data format processable by the funds transfer service provider) that is compatible with the second information processing system 300 but different from the first data format (S702).

The collection processing system 100 generates feasibility determination data for determining whether the specified billing amount can be collected from the user's account based on at least either the first billing data or the second billing data (S703). The collection processing system 100 transmits the feasibility determination data to the second information processing system 300 (S704), obtains information regarding the result of the collection determination based on the feasibility determination data from the second information processing system 300 (S705), and determines whether collection is possible (collection feasibility determination) (S706).

If the collection eligibility determination determines that the amount can be collected (S706: Yes), the collection processing system 100 determines (first determination) whether the billing amount indicated in the first billing data matches the billing amount indicated in the reduction request (S707).

If the first determination determines that there is a match (S707: Yes), the collection processing system 100 sends a deduction request to the second information processing system 300 (S708). The collection processing system 100 obtains deduction result data indicating the results of the deduction processing corresponding to the deduction request from the second information processing system 300 (S709).

Note that the process related to the first determination (S707) may be performed before the process related to the storage feasibility determination (S703 to S706).

The collection processing system 100 generates transfer instruction data based on the deduction result data (S710). The collection processing system 100 determines (second determination) whether the invoice amount indicated by the transfer instruction data matches at least one of the invoice amount indicated by the first invoice data or the invoice amount indicated by the deduction request (S711).

If the second determination determines that there is a match (S711: Yes), the storage processing system 100 transmits movement instruction data to the first information processing system 200 (S712).

If the storage eligibility determination determines that the item cannot be stored (S706: No), or if the first or second determination determines that there is no match (S707: No, or S711: No), the storage processing system 100 performs the third billing data generation process (S713).

Next, an example of the third billing data generation process in the collection processing system 100 will be described with reference to Figure 8A. Figure 8A is a flowchart showing an example of the third billing data generation process in the collection processing system 100. Note that the flowchart shown in Figure 8A shows an example of the third billing data generation process that is performed when the collection feasibility determination determines that the item cannot be collected (S706: Not possible), or when the first or second determination determines that there is no match (S707: Not possible, or S711: Not possible).

First, the collection processing system 100 determines that the payment is not possible in the collection feasibility determination, or determines that there is no match in the first or second determination (S801a). Next, the collection processing system 100 generates third claim data (e.g., data in a format specified by the Japan Bankers Association) for collecting the specified claim amount from the user's account based on at least one of the first claim data or the second claim data (S802a). The collection processing system 100 transmits the third claim data to the first information processing system 200 (S803a).

Next, with reference to Figure 8B, another example of the third billing data generation process in the collection processing system 100 will be described. Figure 8B is a flowchart showing an example of the third billing data generation process when error information is acquired in the collection processing system 100.

First, the collection processing system 100 acquires error information from the second information processing system 300 indicating that the deduction process in the second information processing system 300 based on the deduction request was not performed normally (S801b). Based on the error information, the collection processing system 100 generates third billing data (e.g., data in the format specified by the Japan Bankers Association) for collecting the specified billing amount from the user's account (S802b). The collection processing system 100 transmits the third billing data to the first information processing system 200 (S803b).

Next, with reference to Figure 9, we will explain an example of the hardware configuration when the storage processing system 100 is realized by a computer 900. Figure 9 is a diagram showing an example of the hardware configuration of the computer 900.

As shown in FIG. 9, the computer 900 includes, for example, a processor 901, a memory 902, a storage device 903, an input I/F unit 904, a data I/F unit 905, a communication I/F unit 906, and a display device 907.

Computer 900 may be, for example, a server computer, a personal computer (e.g., desktop, laptop, tablet, etc.), a media computing platform (e.g., cable, satellite set-top box, digital video recorder, etc.), a handheld computing device (e.g., PDA, email client, etc.), or any other type of computer or communications platform.

The processor 901 is a control unit that controls various processes in the computer 900 by executing programs stored in the memory 902.

Memory 902 is a storage medium such as RAM (Random Access Memory). Memory 902 temporarily stores the program code of the program executed by processor 901 and data required when the program is executed.

The storage device 903 is a non-volatile storage medium such as a hard disk drive (HDD) or flash memory. The storage device 903 stores the operating system and various programs for implementing the above configurations.

The input I/F unit 904 is a device for receiving input from the user. The input I/F unit 904 may be, for example, a keyboard, a mouse, a touch panel, various sensors, a wearable device, etc. The input I/F unit 904 may be connected to the computer 900 via an interface such as a USB (Universal Serial Bus).

The data I/F unit 905 is a device for inputting data from outside the computer 900. The data I/F unit 905 is, for example, a drive device for reading data stored on various storage media. The data I/F unit 905 may be provided outside the computer 900. When the data I/F unit 905 is provided outside the computer 900, the data I/F unit 905 is connected to the computer 900 via an interface such as a USB.

The communication I/F unit 906 is a device for performing data communication with devices external to the computer 900 via a network such as the Internet, either wired or wirelessly. The communication I/F unit 906 may be provided external to the computer 900. If the communication I/F unit 906 is provided external to the computer 900, the communication I/F unit 906 is connected to the computer 900 via an interface such as a USB, for example.

The display device 907 is a device for displaying various types of information. The display device 907 may be, for example, a liquid crystal display, an organic electroluminescence (EL) display, or a display for a wearable device. The display device 907 may be provided external to the computer 900. If the display device 907 is provided external to the computer 900, the display device 907 is connected to the computer 900 via, for example, a display cable. Furthermore, if a touch panel is used as the input I/F unit 904, the display device 907 may be configured as an integral part of the input I/F unit 904.

The above describes one embodiment of the present invention. The collection processing system 100 converts first billing data in a first data format into second billing data in a second data format compatible with the second information processing system 300, sends a deduction request to the second information processing system 300 based on the second billing data, and sends transfer instruction data to the first information processing system 200 based on deduction result data indicating the results of the deduction process corresponding to the deduction request. This allows the collection processing system 100 to achieve smooth collection of value information.

Furthermore, if the collection processing system 100 determines that the claim amount indicated in the first claim data matches the claim amount indicated in the reduction request, it can send a reduction request to the second information processing system 300. This allows the collection processing system 100 to smoothly and accurately collect value information corresponding to the claim amount indicated in the first claim data.

Furthermore, when it is determined that the billing amount indicated by the transfer instruction data matches at least one of the billing amount indicated by the first billing data or the billing amount indicated by the reduction request, the collection processing system 100 can transmit the transfer instruction data to the first information processing system 200. This allows the collection processing system 100 to smoothly and accurately collect value information corresponding to the billing amount indicated by the first billing data or the reduction request.

The collection processing system 100 can also determine whether a specified billing amount can be collected from the user's account based on at least either the first billing data or the second billing data, and if it determines that collection is possible, send a reduction request to the second information processing system 300. At this time, the collection processing system 100 can determine whether collection is possible based on whether an account exists or whether there is a balance in the account corresponding to the billing amount. This allows the collection processing system 100 to avoid situations where the specified billing amount cannot be collected as much as possible, and achieve smooth collection of value information.

In addition, the collection processing system 100 determines whether or not it is possible to collect the specified billing amount from the user's account, and if it determines that collection is not possible, it generates third billing data for collecting the specified billing amount from the user's account and transmits the third billing data to the second information processing system 300. This allows the collection processing system 100 to achieve smooth collection even in the event that it is unable to collect the specified billing amount.

The collection processing system 100 can also obtain error information from the second information processing system 300 indicating that the deduction process based on the deduction request was not performed properly in the second information processing system 300, generate third billing data for collecting the specified billing amount from the user's account, and transmit the third billing data to the second information processing system 300. This allows the collection processing system 100 to achieve smooth collection even if an error occurs that prevents the deduction process based on the deduction request from being performed properly.

In addition, the collection processing system 100 can transmit transfer instruction data generated in a data format specified by the Japan Bankers Association to the first information processing system 200. This allows the first information processing system 200 to smoothly perform collection processing using the Japan Bankers Association standard communication protocol.

Note that the present embodiment is intended to facilitate understanding of the present invention and is not intended to limit the scope of the present invention. The present invention may be modified or improved without departing from its spirit, and equivalents thereof are also included within the scope of the present invention.

100 Collection Processing System, 111 Memory Unit, 121 First Billing Data Acquisition Unit, 122 Format Conversion Unit, 131 Appropriateness Determination Data Generation Unit, 132 Appropriateness Determination Data Transmission Unit, 133 Collection Appropriateness Determination Unit, 134 First Determination Unit, 135 Reduction Request Transmission Unit, 136 Reduction Result Data Acquisition Unit, 141 Transfer Instruction Data Generation Unit, 142 Second Determination Unit, 143 Transfer Instruction Data Transmission Unit, 151 Error Acquisition Unit, 152 Third Billing Data Generation Unit, 153 Third Billing Data Transmission Unit, 200 First Information Processing System, 300 Second Information Processing System, 900 Computer, 901 Processor, 902 Memory, 903 Storage Device, 904 Input Interface Unit, 905 Data Interface Unit, 906 Communication Interface Unit, 907 Display Device

Claims (11)

a first billing data acquisition unit that acquires, from a first information processing system, first billing data that is billing data for collecting a predetermined billing amount from a user's account managed by a funds transfer service provider, the billing data being generated in a first data format that corresponds to a first information processing system of a collecting service provider that collects the predetermined billing amount;
a format conversion unit that converts the first billing data into second billing data in a second data format that is compatible with a second information processing system of the funds transfer service provider and is a data format different from the first data format;
a reduction request sending unit that sends a reduction request to the second information processing system to execute a reduction process that reduces the predetermined billing amount from the account based on the second billing data;
a deduction result data acquisition unit that acquires deduction result data indicating a result of the deduction process from the second information processing system;
a transfer instruction data transmission unit that transmits, to the first information processing system, transfer instruction data for executing a transfer process to transfer the specified invoice amount from the funds transfer service provider to the collection service provider based on the deduction result data;
An information processing system comprising: a first determination unit that determines whether or not a billing amount indicated by the first billing data matches a billing amount indicated by the reduction request;
the price reduction request sending unit sends the price reduction request to the second information processing system when the first determination unit determines that the price reduction request matches;
The information processing system according to claim 1 . a second determination unit that determines whether or not at least one of the billing amount indicated by the first billing data or the billing amount indicated by the reduction request matches the billing amount indicated by the transfer instruction data;
the movement instruction data transmission unit transmits the movement instruction data to the first information processing system when the second determination unit determines that there is a match;
3. The information processing system according to claim 1. a data generation unit for determining whether or not the predetermined billing amount can be collected from the account based on at least one of the first billing data and the second billing data; and
a data transmission unit for determining whether or not the data is acceptable that transmits the data for determining whether or not the data is acceptable to the second information processing system;
a payment possibility determination unit that obtains a determination result based on the possibility determination data from the second information processing system and determines whether the predetermined billing amount can be paid from the account;
Furthermore,
the reduction request sending unit sends the reduction request to the second information processing system when the payment possibility determining unit determines that the predetermined billed amount can be paid;
The information processing system according to any one of claims 1 to 3. a third billing data generation unit that generates third billing data, which is billing data for collecting the specified billing amount from the user's account, when the collection possibility determination unit determines that the specified billing amount cannot be collected from the account; and
a third billing data transmitting unit that transmits the third billing data to the first information processing system;
The information processing system according to claim 4 , further comprising: The information processing system described in claim 4 or 5, wherein the feasibility determination data generation unit generates feasibility determination data for determining whether the account exists in the second information processing system based on at least one of the first request data or the second request data. The information processing system described in any one of claims 4 to 6, wherein the feasibility determination data generation unit generates feasibility determination data for determining whether the account has a balance corresponding to the specified billing amount based on at least one of the first billing data or the second billing data. an error acquisition unit that acquires error information indicating that the deduction process based on the deduction request has not been performed normally from the second information processing system;
a third billing data generating unit that generates third billing data, which is billing data for collecting the predetermined billing amount from the user's account, when the error information is acquired;
a third billing data transmitting unit that transmits the third billing data to the first information processing system;
The information processing system according to any one of claims 1 to 7, further comprising: The information processing system described in any one of claims 1 to 8, wherein the transfer instruction data transmission unit transmits the transfer instruction data generated in a data format specified by the Japan Bankers Association to the first information processing system. The computer
Obtaining, from a first information processing system, first billing data for collecting a predetermined billing amount from a user's account managed by a funds transfer service provider, the billing data being generated in a first data format corresponding to a first information processing system of a collection service provider that collects the predetermined billing amount;
converting the first billing data into second billing data in a second data format that is compatible with a second information processing system of the funds transfer service provider and is a data format different from the first data format;
transmits a deduction request to the second information processing system to execute a deduction process for deducting the predetermined billing amount from the account based on the second billing data;
Acquires deduction result data indicating a result of the deduction process from the second information processing system;
transmits to the first information processing system transfer instruction data for executing a transfer process to transfer the specified invoice amount from the funds transfer service provider to the collection service provider based on the deduction result data;
Information processing methods. On the computer,
a first billing data acquisition unit that acquires, from a first information processing system, first billing data that is billing data for collecting a predetermined billing amount from a user's account managed by a funds transfer service provider, the billing data being generated in a first data format that corresponds to a first information processing system of a collecting service provider that collects the predetermined billing amount;
a format conversion unit that converts the first billing data into second billing data in a second data format that is compatible with a second information processing system of the funds transfer service provider and is a data format different from the first data format;
a reduction request sending unit that sends a reduction request to the second information processing system to execute a reduction process that reduces the predetermined billing amount from the account based on the second billing data;
a deduction result data acquisition unit that acquires deduction result data indicating a result of the deduction process from the second information processing system;
a transfer instruction data transmission unit that transmits, to the first information processing system, transfer instruction data for executing a transfer process to transfer the specified invoice amount from the funds transfer service provider to the collection service provider based on the deduction result data;
An information processing program to achieve this.