Information processing system, information processing method, and information processing program

Abstract

To achieve smooth storage of value information.SOLUTION: An information processing system includes a first billing data acquisition part for acquiring first billing data for storing a prescribed billing amount from a user's account managed by a fund transfer agent and being generated in a first data format corresponding to a first information processing system of a storage agent from the first information processing system, a format conversion part for converting the first billing data into second billing data in a second data format corresponding to a second information processing system of the fund transfer agent, a reduction request transmission part for transmitting a reduction request to execute reduction processing for reducing the billing amount from the account to the second information processing system, a reduction result data acquisition part for acquiring reduction result data showing a result of the reduction processing from the second information processing system, and a transfer instruction data transmission part for transmitting transfer instruction data for executing transfer processing for transferring the billing amount from the fund transfer agent to the storage agent to the first information processing system on the basis of the reduction result data.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] 2. Description of the Related Art Conventionally, there have been proposed techniques for transferring value information such as electronic money via various networks such as the Internet and receiving a predetermined bill amount.

[0003] The program described in Patent Document 1 provides billing information to a user, and based on the user's operation, executes a settlement process to pay the billed amount indicated by the billing information by transferring electronic money, etc. In this way, the program transfers value information from a specified account and realizes the receipt of the specified billed amount. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 6880165 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the program described in Patent Document 1 requires user operation when executing the payment process, which poses a problem in that it is not possible to smoothly store value information.

[0006] Therefore, an object of the present invention is to provide an information processing system, an information processing method, and an information processing program that realize smooth storage of value information. [Means for solving the problem]

[0007] An information processing system according to one embodiment of the present invention comprises: 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 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 to the second information processing system a deduction request to execute a deduction process to deduct 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.

[0008] An information processing method according to one aspect of the present invention comprises 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 billing data generated in a first data format corresponding to a 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 that is a data format corresponding to a 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 that deducts the specified billing amount from the account based on the second billing data; acquiring deduction result data from the second information processing system that indicates the results of the deduction process; and sending, 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.

[0009] An information processing program according to one aspect of the present invention causes a computer to implement 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 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 sending unit that sends 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 sending unit that sends 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.

[0010] In this invention, a "unit" does not simply mean a physical means, but also includes cases where the functions of the "unit" are realized by software. Furthermore, the functions of one "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 one physical means or device. [Effects of the Invention]

[0011] According to the present invention, it is possible to provide an information processing system, an information processing method, and an information processing program that realize smooth storage of value information. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a diagram showing the configuration of a storage processing system 100 according to one embodiment of the present invention. [Figure 2] 10 is a diagram showing an example of first billing data stored in a storage unit 111. FIG. [Figure 3]10 is a diagram showing an example of second billing data stored in the storage unit 111. FIG. [Figure 4] 10 is a diagram showing an example of data for determining whether or not a request is accepted, which is stored in the storage unit 111. FIG. [Figure 5] 10 is a diagram showing an example of reduction result data stored in the storage unit 111. FIG. [Figure 6] 10 is a diagram showing an example of movement instruction data stored in a storage unit 111. FIG. [Figure 7] 10 is a flowchart showing an example of processing in the storage processing system 100. [Figure 8A] 10 is a flowchart showing an example of a third billing data generation process in the collection processing system 100. [Figure 8B] 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. [Figure 9] FIG. 9 is a diagram illustrating an example of the hardware configuration of a computer 900. DETAILED DESCRIPTION OF THE INVENTION

[0013] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the present invention will now be described with reference to the accompanying drawings, in which: Figure 1 is a diagram showing the configuration of a storage processing system 100 according to one embodiment of the present invention;

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

[0015] The collection processing system 100, for example, performs a process of converting data formats between the collection agent and the funds transfer agent, and a process of determining whether collection is possible, so that the collection agent can collect a specified billing amount from the user using value information. In this way, the collection processing system 100 improves the convenience of payments for the collection agent and the user, and can achieve smooth collection of value information. Details of the collection processing system 100 will be described later.

[0016] The first information processing system 200 is, for example, an information processing system of a collection agency. Using the first information processing system 200, the collection agency collects a specified billing amount from a user on behalf of a biller who makes a specified bill to the user, and provides the collected amount to the biller. Specifically, for example, in relation to payment for a subscription-type service subscribed to by the user, the collection agency collects a specified billing amount (e.g., a monthly fee) from a user's account or the like on behalf of a service provider, and transfers the collected billing amount to the account of the service provider.

[0017] The second information processing system 300 is, for example, an information processing system of a funds transfer service provider. The funds transfer service provider uses the second information processing system 300 to obtain money from the user by a predetermined method via a bank or the like, and grants 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 or points held by the user, and performs payment processing, etc., using the electronic money or points as necessary.

[0018] Although 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.

[0019] 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 a specified billing amount from the user's account managed by the funds transfer agent. Hereinafter, the process of collecting a specified billing amount from the user's account will be referred to as the "collection process."

[0020] 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 deduction request to the second information processing system 300 to execute a deduction process to reduce the billing amount indicated by the second billing data. In other words, the collection processing system 100 can realize smooth collection of value information by the second information processing system by converting the billing data in a data format used by the collection agent into billing data in a data format used by the funds transfer agent.

[0021] The receipt processing system 100 then obtains deduction result data indicating the result of the deduction process from the second information processing system 300. The receipt processing system 100 determines, for example, based on the deduction result data, whether or not deduction processing is possible from the user's account at the funds transfer service provider. Based on the determination result, the receipt processing system 100 transmits transfer instruction data to the first information processing system 200 for executing transfer processing to transfer the invoice amount from the funds transfer service provider to the collection service provider. In other words, the receipt 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.

[0022] Next, the detailed configuration of the collection processing system 100 will be described. The collection processing system 100 includes a memory unit 111, a first billing data acquisition unit 121, a format conversion unit 122, a data generation unit for determination of feasibility 131, a data transmission unit for determination of feasibility 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 includes 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.

[0023] The storage unit 111 stores data acquired and generated by the storage processing system 100. As will be described later, the storage unit 111 stores, for example, first billing data, second billing data, data for determining whether or not a billing is possible, reduction result data, transfer instruction data, and third billing data.

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

[0025] 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.

[0026] Here, the first data format compatible with 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.

[0027] 2 is a diagram showing an example of first billing data stored in storage unit 111. The first billing data stored in storage unit 111 includes, for example, a collection ID, billing destination information, account information, billing amount information, and billing source information.

[0028] The storage ID is information for identifying the billing data acquired from the first information processing system 200.

[0029] The billing information is information associated with the deposit ID and is information related to 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 may be information indicating the name of the funds transfer service provider. The billing information may also be information identifying 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 string of four digits).

[0030] The account information is information associated with the deposit ID and is information related to the user's account. The 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.

[0031] The billing amount information is information indicating the billing amount that is the subject of the collection process. The billing source information is information about the billing source in the collection process, 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.

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

[0033] The format conversion unit 122 converts the first billing data in the first data format into second billing data in a second data format that is a data format compatible with the second information processing system 300 but 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.

[0034] 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) is different 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 needs to be converted into a data format that can be processed by the second information processing system 300.

[0035] 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 second information processing system 300 of the funds transfer service provider, 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.

[0036] Furthermore, when requesting collection processing from each of the second information processing systems 300 of multiple funds transfer service providers, 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 service providers.

[0037] 3 is a diagram showing an example of second billing data stored in storage unit 111. The second billing data stored in storage 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 FIG. 2, and therefore a description thereof will be omitted.

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

[0039] Furthermore, the data for determination of feasibility generation unit 131 may generate data for determination of feasibility based on at least one of the first billing data or the second billing data to determine whether or not a user account corresponding to the collection process exists in the second information processing system 300. In this case, the data for determination of feasibility may include account information related to the user account.

[0040] Furthermore, the data generation unit 131 for determining whether or not a balance corresponding to a predetermined billing amount is available in the user's account may generate data for determining whether or not the balance corresponds to a predetermined billing amount based on at least one of the first billing data and the second billing data. In this case, the data for determining whether or not a balance corresponding to a predetermined billing amount is available may include billing amount information indicating the billing amount to be processed.

[0041] The data generation unit for determination of feasibility 131 may store the second billing data as data for determination of feasibility in the storage unit 111. In other words, the collection processing system 100 can use the second billing data as data for determination of feasibility as it is, thereby realizing smooth collection of value information.

[0042] Furthermore, the feasibility determination data generating unit 131 may generate, as feasibility determination data, information included in the second billing data, excluding information (for example, billing source information) that is unnecessary when checking whether the user has an account or whether the account has a balance. This allows the receipt processing system 100 to process only the data necessary to determine whether the specified billing amount can be received from the user's account, thereby achieving, for example, improved processing speed and improved security in the receipt processing system 100.

[0043] The possibility determination data transmitting unit 132 transmits the possibility determination data to the second information processing system 300.

[0044] 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 receipt processing system 100. Specifically, the second information processing system 300 determines 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 based on, for example, the account information and billing amount information included in the feasibility determination data, and transmits the determination result to the receipt processing system 100.

[0045] The determination of whether or not a predetermined billing amount can be collected from the user's account may be performed by the receipt processing system 100. In this case, the receipt 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 compare the balance indicated by the balance information with the predetermined billing amount to determine whether or not collection is possible.

[0046] 4 is a diagram showing an example of the data for determining whether or not a payment is accepted that is stored in the storage unit 111. The data for determining whether or not a payment is accepted that is stored in the storage unit 111 includes, for example, a payment ID, account information, and billing amount information.

[0047] The collection possibility determination unit 133 determines whether or not a predetermined billing amount can be collected 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", "balance available" and the like from the second information processing system 300, and may also obtain balance information for the user's account.

[0048] The payment possibility determination unit 133 may determine whether or not a specified billing amount can be paid from the user's account, for example, based on the balance information and the billing amount information included in at least one of the first billing data or the second billing data.

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

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

[0051] 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 predetermined billing amount from the user's account (i.e., a process of subtracting value information from the account). 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.

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

[0053] The reduction request sending unit 135 may send the second billing data as a reduction request to the second information processing system 300. 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 it is as data for determining whether or not to collect the value information, thereby realizing smooth collection of the value information.

[0054] Furthermore, the reduction request sending unit 135 may convert the second billing data into a predetermined format and send the converted data as a reduction request to the second information processing system 300. This allows the second information processing system 300 to execute the reduction process based on data in a format that can be processed by the second information processing system 300.

[0055] Furthermore, the reduction request sending unit 135 may send a reduction request to the second information processing system 300 when the deposit possibility determining unit 133 determines that deposit is possible.

[0056] In addition, the reduction request sending unit 135 may send the 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 by the reduction request.

[0057] Furthermore, the reduction request sending unit 135 may send a reduction request to the second information processing system 300 when the collection possibility determining unit 133 determines that collection is possible and the first determining unit 134 determines that the claim amount indicated by the first claim data matches the claim amount indicated by the reduction request. This allows the collection processing system 100 to avoid, as much as possible, a situation in which the specified claim amount cannot be collected, and to smoothly and accurately collect value information corresponding to the claim indicated by the first claim data.

[0058] The reduction result data acquisition unit 136 acquires reduction result data indicating the result of the reduction process from the second information processing system 300 and stores the reduction result data in the storage unit 111.

[0059] FIG. 5 is a diagram showing an example of deduction result data stored in memory unit 111. The deduction result data stored in 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 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 FIG. 2, and therefore their description will be omitted.

[0060] 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 by the second invoice data from the funds transfer service provider to the collection service provider, and stores the data in the storage 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 invoicer who will make the specified invoice to the user, thereby realizing the collection process.

[0061] In the transfer process, for example, funds (including, for example, cash or virtual currency) corresponding to the invoice amount may be transferred, or value information corresponding to the invoice amount may be transferred. Furthermore, the funds transfer service provider may receive the invoice amount from the funds transfer service provider after transferring the invoice amount to the invoicer who makes the specified invoice to the user.

[0062] 6 is a diagram showing an example of transfer instruction data stored in storage unit 111. The transfer instruction data stored in storage unit 111 includes, for example, a transfer instruction ID, transfer source information, billing amount information, transfer destination information, and a reduction result ID.

[0063] The transfer instruction ID is information that identifies the transfer instruction data stored in the memory unit 111. The transfer source information is information about the party from which the billing amount is 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 billing 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 information indicating the business that provides the service (e.g., the business that provides "XX Pay").

[0064] The transfer instruction data may be stored in the storage unit 111 in a data format specified by the Japanese Bankers Association.

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

[0066] For example, when the second determination unit 142 determines that 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. This makes it possible to smoothly and accurately store the value information even when the reduction process of the value information and the transfer process of the billing amount are executed separately.

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

[0068] When 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, thereby allowing the receipt processing system 100 to smoothly and accurately collect the value information corresponding to the billing amount indicated by the first billing data acquired from the first information processing system 200. Furthermore, when 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, thereby allowing the receipt 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.

[0069] 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 normally 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 normally.

[0070] A situation in which the deduction process is not performed normally 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.

[0071] The third billing data generating unit 152 generates third billing data for collecting a predetermined billing amount from the user's account when the deduction process is not performed normally in the second information processing system.

[0072] Specifically, the third billing data generation unit 152 may generate the third billing data, for example, when the collection possibility determination unit 133 determines that the predetermined 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 predetermined billing amount from the user's account, for example, based on information that associates the user's account with the account.

[0073] Here, if the collection possibility 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 one of the first billing data or the second billing data.

[0074] Specifically, the third billing data generation unit 152 may generate third billing data for collecting the billing amount corresponding to the billing amount information based on the billing amount information included 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 if a situation occurs in which the specified billing amount cannot be collected.

[0075] Furthermore, when the error acquisition unit 151 acquires error information, the storage possibility determination unit 133 can generate third invoice data, for example, based on the error information.

[0076] 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 the 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 normally.

[0077] 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 generate third billing data for collecting the billing amount corresponding to the account information, for example, 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.

[0078] The information associating the user's account with the bank account may be set in advance in the receipt processing system 100. Specifically, the receipt processing system 100 may store in advance information associating 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 receipt 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.

[0079] The third billing data generation unit 152 may generate the third billing data in a first data format (for example, 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 achieving smooth collection.

[0080] 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 a predetermined billing amount from the user's account based on the third billing data.

[0081] FIG. 7 is a flowchart showing an example of processing in the storage processing system 100.

[0082] First, the receipt processing system 100 acquires first billing data for receiving a predetermined billing amount from a 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 a CSV format) from the first information processing system 200 (S701). The receipt processing system 100 converts the first billing data into second billing data in a second data format (e.g., a data format processable by a funds transfer service provider), which is a data format compatible with the second information processing system 300 but different from the first data format (S702).

[0083] The collection processing system 100 generates feasibility determination data for determining whether or not a predetermined 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 on the result of the collection feasibility determination based on the feasibility determination data from the second information processing system 300 (S705), and determines whether or not the payment can be collected (collection feasibility determination) (S706).

[0084] If the collection processing system 100 determines that the payment can be collected in the collection feasibility determination (S706: Yes), it makes a determination (first determination) as to whether the billing amount indicated by the first billing data matches the billing amount indicated by the reduction request (S707).

[0085] If the first determination determines that there is a match (S707: Yes), the receipt processing system 100 transmits a deduction request to the second information processing system 300 (S708). The receipt processing system 100 acquires deduction result data indicating the result of the deduction process corresponding to the deduction request from the second information processing system 300 (S709).

[0086] The process related to the first determination (S707) may be performed before the process related to the storage possibility determination (S703 to S706).

[0087] The receipt processing system 100 generates transfer instruction data based on the deduction result data (S710). The receipt processing system 100 determines whether or not the invoice amount indicated by the first invoice data or the invoice amount indicated by the deduction request matches the invoice amount indicated by the transfer instruction data (second determination) (S711).

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

[0089] If the storage processing system 100 determines that the item cannot be stored in the storage feasibility determination (S706: Not possible), or if the first or second determination determines that there is no match (S707: Not possible, or S711: Not possible), it performs the third billing data generation process (S713).

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

[0091] 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 determination or the second determination (S801a). Next, the collection processing system 100 generates third billing data (for example, data in a format specified by the Japan Bankers Association) for collecting a specified billing amount from the user's account based on at least one of the first billing data or the second billing data (S802a). The collection processing system 100 transmits the third billing data to the first information processing system 200 (S803a).

[0092] Next, with reference to Fig. 8B, a description will be given of another example of the third billing data generation process in the storage processing system 100. Fig. 8B is a flowchart showing an example of the third billing data generation process in the storage processing system 100 when error information is acquired.

[0093] 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 (for example, data in a 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).

[0094] Next, an example of a hardware configuration in the case where the storage processing system 100 is realized by a computer 900 will be described with reference to Fig. 9. Fig. 9 is a diagram showing an example of the hardware configuration of the computer 900.

[0095] As shown in FIG. 9, a 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.

[0096] 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 computing or communications platform.

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

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

[0099] The storage device 903 is a non-volatile storage medium such as a hard disk drive (HDD), flash memory, etc. The storage device 903 stores an operating system and various programs for realizing the above-mentioned configurations.

[0100] The input I / F unit 904 is a device for receiving input from a user. The input I / F unit 904 is, 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).

[0101] 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 in 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.

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

[0103] The display device 907 is a device for displaying various types of information. The display device 907 is, for example, a liquid crystal display, an organic EL (Electro-Luminescence) display, a display of a wearable device, or the like. The display device 907 may be provided outside the computer 900. When the display device 907 is provided outside the computer 900, the display device 907 is connected to the computer 900 via, for example, a display cable. Furthermore, when a touch panel is adopted 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.

[0104] The above describes one embodiment of the present invention. The storage processing system 100 can convert 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, transmit a deduction request to the second information processing system 300 based on the second billing data, and transmit transfer instruction data to the first information processing system 200 based on deduction result data indicating the result of the deduction process corresponding to the deduction request. This allows the storage processing system 100 to achieve smooth storage of value information.

[0105] Furthermore, when it is determined that the billing amount indicated by the first billing data matches the billing amount indicated by the billing reduction request, the receipt processing system 100 can transmit the billing reduction request to the second information processing system 300. This allows the receipt processing system 100 to smoothly and accurately receive the value information corresponding to the billing amount indicated by the first billing data.

[0106] Furthermore, when it is determined that 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 receipt processing system 100 can transmit the transfer instruction data to the first information processing system 200. This allows the receipt processing system 100 to smoothly and accurately realize the receipt of value information corresponding to the billing amount indicated by the first billing data or the reduction request.

[0107] Furthermore, the receipt processing system 100 can determine whether or not a predetermined 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 is determined that the collection is possible, can send a reduction request to the second information processing system 300. At this time, the receipt processing system 100 can determine whether or not collection is possible based on whether or not the account exists or whether or not there is a balance in the account corresponding to the billing amount. This allows the receipt processing system 100 to avoid situations where the predetermined billing amount cannot be collected as much as possible, and can achieve smooth collection of value information.

[0108] Furthermore, the receipt processing system 100 can determine whether or not a predetermined billing amount can be collected from the user's account, and if it determines that the collection is not possible, generate third billing data for collecting the predetermined billing amount from the user's account and transmit the third billing data to the second information processing system 300. This allows the receipt processing system 100 to achieve smooth collection even in the event that the predetermined billing amount cannot be collected.

[0109] Furthermore, the collection processing system 100 can obtain error information from the second information processing system 300 indicating that the deduction process based on the deduction request was not performed normally 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 normally.

[0110] Furthermore, 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.

[0111] It should be noted that the present embodiment is provided to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit thereof, and equivalents thereof are also included in the present invention. [Explanation of symbols]

[0112] 100 collection processing system, 111 memory unit, 121 first billing data acquisition unit, 122 format conversion unit, 131 data generation unit for determining feasibility, 132 data transmission unit for determining feasibility, 133 collection feasibility determination unit, 134 first determination unit, 135 reduction request transmission unit, 136 reduction result data acquisition unit, 141 movement instruction data generation unit, 142 second determination unit, 143 movement 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 I / F unit, 905 data I / F unit, 906 communication I / F unit, 907 display device

Claims

1. 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 amount of billing 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:

2. 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 .

3. 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.

4. 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.

5. 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:

6. The information processing system described in claim 4 or 5, wherein the data generation unit for determining whether or not the account exists in the second information processing system generates data for determining whether or not the account exists in the second information processing system based on at least one of the first request data or the second request data.

7. An information processing system as described in any one of claims 4 to 6, wherein the data generation unit for determining feasibility generates data for determining feasibility based on at least one of the first billing data or the second billing data to determine whether or not there is a balance in the account corresponding to the specified billing amount.

8. 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:

9. The information processing system according to 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.

10. 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.

11. 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 amount of billing 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.

Images