JP7364550B2 - Payment programs, payment devices and payment methods - Google Patents

Description

The present invention relates to a payment program, a payment device, and a payment method.

In recent years, various techniques regarding electronic payment using terminal devices used by users have been proposed. For example, a technology has been provided for paying a user's bill by electronic payment (for example, Patent Document 1).

JP2020-021458A

However, with the techniques described above, there is room to improve usability in bill settlement.

For example, in the above-mentioned conventional technology, characters extracted from a bill without a barcode are displayed, and instructions for payment regarding the contents of the displayed electronic payment are received from the user and the electronic payment is performed. Therefore, if the user has a large number of requests, he or she must instruct payment for each request, which may result in a time-consuming process for the user.

The present application has been made in view of the above, and aims to improve usability in bill settlement.

The payment program according to the present application includes a provision procedure for providing a user with a plurality of billing information indicating the content of each of a plurality of charges to the user, and at least one of the plurality of charges to be paid collectively by the user. When a group of claims including two or more claims is selected, the computer is made to execute a payment processing procedure for executing a lump sum payment process for collectively paying each of the claims.

According to one aspect of the embodiment, it is possible to improve usability in bill settlement.

FIG. 1 is a diagram illustrating an example of a payment process according to an embodiment. FIG. 2 is a diagram illustrating an example of content displayed by an electronic payment application. FIG. 3 is a diagram illustrating an example of batch payment processing. FIG. 4 is a diagram showing another example of content displayed by the electronic payment application. FIG. 5 is a diagram illustrating a configuration example of a terminal device according to an embodiment. FIG. 6 is a diagram illustrating a configuration example of the second application according to the embodiment. FIG. 7 is a diagram illustrating a configuration example of a payment server according to an embodiment. FIG. 8 is a diagram illustrating an example of an account database according to the embodiment. FIG. 9 is a diagram illustrating an example of a billing information database according to the embodiment. FIG. 10 is a flowchart illustrating an example of a payment processing procedure according to the embodiment. FIG. 11 is a hardware configuration diagram showing an example of a computer that implements the functions of the terminal device.

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments (hereinafter referred to as "embodiments") for implementing the payment program, payment device, and payment method according to the present application will be described in detail with reference to the drawings. Note that this embodiment does not limit the payment program, payment device, and payment method according to the present application. Further, in each of the embodiments below, the same parts are given the same reference numerals, and redundant explanations will be omitted.

[1. Embodiment]
The payment process realized by the payment program of this embodiment will be explained using FIG. 1. FIG. 1 is a diagram illustrating an example of a payment process according to an embodiment. Note that in FIG. 1, the payment processing by the payment program according to the embodiment is performed by the terminal device 100 shown in FIG. That is, the terminal device 100 executes the payment process according to the embodiment according to the control by the payment program according to the embodiment.

[1-1. Example of information processing system]
As shown in FIG. 1, the payment system 1 according to the embodiment includes a payment server 10, a terminal device 100, and a business server 200. The payment server 10, the terminal device 100, and the business server 200 are connected to be able to communicate with each other by wire or wirelessly via a network N (see FIG. 5, for example). The network N is, for example, a WAN (Wide Area Network) such as the Internet. Note that the payment system 1 shown in FIG. 1 may include a plurality of payment servers 10, a plurality of terminal devices 100, and a plurality of company servers 200.

The payment server 10 shown in FIG. 1 is an information processing device that provides electronic payment services related to electronic payments using the terminal device 100 and performs various payments, and is realized by, for example, a server device or a cloud system. For example, the payment server 10 manages the accounts of providers (business operators) of transaction objects and users to whom transaction objects are provided (hereinafter referred to as "users"), and handles payments from users. Various payments are realized by transferring electronic money between accounts according to requests. Note that electronic money may be, for example, points or currency used independently by various companies, or may be currency provided by a country such as Japanese yen or dollars that can be electronically transacted. good.

The terminal device 100 shown in FIG. 1 is an information processing device used by a user. The terminal device 100 is a mobile terminal, and is realized by, for example, a smartphone, a tablet terminal, a notebook PC (Personal Computer), a mobile phone, a PDA (Personal Digital Assistant), or the like. Further, the terminal device 100 displays information distributed by the payment server 10 using a web browser or an application. Note that the example shown in FIG. 1 shows a case where the terminal device 100 is a smartphone.

The company server 200 shown in FIG. 1 is an information processing device used by each company, and is realized by, for example, a server, a cloud system, or the like. For example, the business server 200 manages billing information regarding billing of fees according to the use of services by users, as information regarding services provided by each business operator.

[1-2. Payment using terminal device]
Here, prior to the payment process executed by the terminal device 100, an example of payment (electronic payment) using the terminal device 100 will be described. In the following explanation, the user U uses the two-dimensional code (QR code (registered trademark)) placed at the store and indicates store identification information to identify the store, to connect the user U to the terminal device 100. An example in which payment is made using the following will be described, but the embodiment is not limited to this. An example of a payment described below is applicable even when any user U uses any terminal device 100 to make a payment at any store. Further, the store identification information may be not only a QR code (registered trademark) but also a barcode, a predetermined mark, a number, etc.

For example, when the user U makes a payment for the use or purchase of various products and services to be paid at a store, the user U starts a payment application installed in the terminal device 100 in advance. Then, the user U photographs the store identification information installed at the store via the application. In such a case, the terminal device 100 displays a screen for inputting the price to be paid, and accepts the input of the payment amount from the user U or the store clerk. Then, the terminal device 100 receives the user information that identifies the user U, the store identification information (or the information indicated by the store identification information, that is, the information indicating the store (for example, the store ID)), and the payment amount. The payment information shown is transmitted to the payment server 10.

In such a case, the payment server 10 transfers the amount of electronic money indicated by the payment amount from the account of the user U indicated by the user information to the account of the store indicated by the store identification information. Then, the payment server 10 transmits a notification to the terminal device 100 that the payment has been completed. In such a case, the terminal device 100 notifies the user that the payment has been made using electronic money by displaying a screen or outputting a predetermined sound indicating that the payment has been completed.

Note that payment using the terminal device 100 is not limited to the above-described processing. For example, the payment using the terminal device 100 may be made using a store terminal installed in a store. For example, the terminal device 100 displays user identification information for identifying the user U on the screen. In such a case, the store terminal installed in the store reads the user identification information displayed on the terminal device 100, and reads the user identification information (or the information indicated by the user identification information, that is, the information indicating the user U). (for example, user ID)), the payment amount, and information identifying the store, is transmitted to the payment server 10. In such a case, the payment server 10 transfers the amount of electronic money indicated by the payment amount from the account of the user U indicated by the user identification information to the account of the store, and transfers it to the store terminal or terminal device 100 of the store. On the other hand, the fact that the payment has been completed may be notified by outputting a screen or a predetermined sound indicating that the payment has been completed.

In addition, payment using the terminal device 100 is not limited to the process of transferring electronic money from an account in which the user U has previously charged electronic money to an account at a store, but also includes, for example, a process of transferring electronic money from an account to which the user U has previously registered a credit card. It may be a payment made using In such a case, for example, the payment server 10 may remit electronic money for the payment amount to the store's account and request the payment amount from the company that operates the user U's credit card.

Further, the payment using the terminal device 100 is not only a process of transferring electronic money from the account of the user U to the account of the store, but also a process of transferring electronic money from the account of the user U to a provider who provides a predetermined transaction object. It may also be a payment method in which electronic money is transferred to a (business operator's) account. In such a case, the user U uses the photographing device equipped with the terminal device 100 to scan the barcode included in the payment slip (for example, a transfer slip used in a convenience store collection agency service) sent to the user U by the business operator. Read with (camera). Then, the terminal device 100 displays the payee and payment amount indicated by the read barcode on the screen, and when receiving an operation from the user U to approve the remittance to the payee, the terminal device 100 displays the user identification information and the payment amount. Payment information indicating the payment amount and information identifying the payee is transmitted to the payment server 10. In such a case, the payment server 10 transfers the amount of electronic money indicated by the payment amount from the user U's account to the payee's account.

[1-3. Overview of batch payment processing]
Here, a technique is known in which bills such as electronic bills and paper bills are paid by electronic payment. However, when electronic payments are made for multiple bills using such technology, it is a time-consuming process for users to operate each bill individually, which reduces usability. In some cases, it may not be said that it is good.

Therefore, the terminal device 100 executes the payment process according to the embodiment. The payment process executed by the terminal device 100 will be described below with reference to FIG. In addition, in the following description, an example in which the terminal device 100 is used by a user U will be shown. Furthermore, in the following description, the terminal device 100 may be equated with the user U. That is, below, the user U can also be read as the terminal device 100.

In addition, in the following explanation, the payment system 1 refers to operator servers 201, 202, and 203 (hereinafter referred to as "business utilities") managed by businesses that provide services (public utilities) that supply water, electricity, gas, etc. to users. server 200). In the example of FIG. 1, it is assumed that the business server 201 is a business server 200 managed by a business that provides a service that supplies water (also referred to as a "water business"). Furthermore, in the example of FIG. 1, it is assumed that the business server 202 is a business server 200 managed by a business that provides a service that supplies electricity (also referred to as an "electricity business"). In the example of FIG. 1, it is assumed that the business server 203 is a business server 200 managed by a business that provides a gas supply service (also referred to as a "gas business").

Note that the payment system 1 may include any number of terminal devices 100 and business servers 200. For example, although FIG. 1 illustrates the company servers 201, 202, and 203 of three companies, the number of companies is not limited to three, and there may be four or more companies.

First, in FIG. 1, the company server 201 managed by the water company transmits billing information regarding the billing of the fee according to the water usage of the user U to the payment server 10 (step S1-1). Further, the company server 202 managed by the electricity company transmits billing information regarding billing of charges according to the electricity usage of the user U to the payment server 10 (step S1-2). Further, the company server 203 managed by the gas company transmits billing information regarding the billing of the fee according to the gas usage of the user U to the payment server 10 (step S1-3). Note that steps S1-1 to S1-3 are for explaining each process, and do not define the order of the processes. That is, the order in which steps S1-1 to S1-3 are performed is not limited to the order of steps S1-1, S1-2, and S1-3, but may be performed in any order and at any timing. Hereinafter, when steps S1-1 to S1-3 are described without distinction, they will be collectively referred to as step S1. Note that in step S1 in FIG. 1, billing information may be transmitted not only for user U but also for each user. Further, the billing information is not limited to steps S1-1 to S1-3, and the billing information may be transmitted from the business server 200 to the payment server 10 multiple times.

In this manner, in step S1, each business server 200 transmits billing information regarding billing of fees according to each user's use of the service to the payment server 10. For example, the business server 200 determines the fee to be charged to each user according to the usage of water, electricity, gas, etc., and transmits billing information regarding billing of the determined fee to the payment server 10. To give a specific example, the business server 200 stores information indicating the user who has charged the fee (billing party), information indicating the business operator (billing source) that charges the fee to the user, and the billing amount (billing party). Billing information including the amount), transaction object to be billed, payment date, etc. is transmitted to the settlement server 10. For example, the business server 200 transmits an electronic bill regarding payment of utility charges, etc. to the payment server 10.

The payment server 10 distributes billing information to the terminal device 100 (step S2). For example, the billing information includes information indicating the billing amount, information indicating the billing source, information indicating the transaction object to be billed, and the like. For example, the payment server 10 transmits a plurality of pieces of billing information indicating the contents of each of the plurality of bills of the user U such as water, electricity, gas, etc. to the terminal device 100. In FIG. 1, the payment server 10 stores a plurality of billing information displayed in a list on an electronic payment application (an application provided by the payment server 10, hereinafter also referred to as "electronic payment application") installed in advance on the terminal device 100. is transmitted to the terminal device 100. For the sake of explanation, FIG. 1 shows a case where the payment server 10 delivers a plurality of pieces of billing information indicating the contents of each of a plurality of bills such as water, electricity, gas, etc. to the terminal device 100 in step S2. Each piece of billing information may be distributed from the payment server 10 to the terminal device 100 at different timings. For example, the payment server 10 may distribute the billing information to the terminal device 100 at the timing of receiving the billing information from each business server 200.

The terminal device 100 displays a plurality of pieces of billing information indicating the contents of each of the plurality of bills for the user U (step S3). Thereby, the terminal device 100 provides the user U with a plurality of pieces of billing information. For example, when the user U starts an electronic payment application and performs an operation to display bill payment information, the terminal device 100 displays a plurality of bills corresponding to each of a plurality of bills that the user U has not paid. List billing information.

The user U, who has confirmed the plurality of billing information displayed in a list, selects a billing group (hereinafter also referred to as "collective payment billing group") from among the plurality of billings to be paid together (step S4). For example, the user U selects two or more bills to form a lump sum bill group from among multiple bills for water, electricity, gas, etc. In FIG. 1, the user U selects three bills for water, electricity, and gas as a lump-sum bill group from among the multiple bills displayed in a list. Then, the user U performs an operation (also referred to as a "lump payment operation") for performing a process for collectively paying each of the group of lump sum payment requests (also referred to as a "lump payment process"). For example, as a lump sum payment operation, the user U performs an operation to designate (select) a button (also referred to as a "lump payment execution button") for executing a lump sum payment displayed on the terminal device 100 by an electronic payment application. . Thereby, the terminal device 100 receives an operation from the user U to execute a lump-sum payment process for making payments for each lump-sum payment request group at once.

Then, the terminal device 100 executes a lump sum payment process for the batch payment bill group (step S5). In FIG. 1, the terminal device 100 executes a lump sum payment process for three bills: water, electricity, and gas. The detailed processing flow of the batch payment process will be explained in FIGS. 2 to 4, but the terminal device 100 transmits billing information for each bill to be processed in the batch payment process to the payment server 10. In FIG. 1, the terminal device 100 notifies the payment server 10 of billing information for each of three bills: water, electricity, and gas.

The payment server 10 then performs payment processing according to the notified billing information (step S6). As a payment process, the payment server 10 performs remittance between accounts according to the notified billing information. For example, the payment server 10 remits electronic money equivalent to the billed amount from the user U's account to the billing source's account corresponding to the notified billing information. In FIG. 1, the terminal device 100 remits electronic money corresponding to the billed amount from the account of the user U to the accounts of the three billing sources for each of water, electricity, and gas.

As described above, the terminal device 100 according to the embodiment can improve usability in bill settlement for a user by performing lump sum payment processing for a group of bills.

[1-3-1. Example of bulk payment processing]
Here, an example of the lump sum payment process will be described using FIGS. 2 and 3 with reference to various contents displayed on the terminal device 100 by the electronic payment application. FIG. 2 is a diagram illustrating an example of content displayed by an electronic payment application. FIG. 3 is a diagram illustrating an example of batch payment processing.

As shown in FIG. 2, the terminal device 100 displays content C1 that lists a plurality of billing information BL1 to BL3 corresponding to each of a plurality of bills that the user U has not paid. For example, in the initial display displayed when the electronic payment application is started, the terminal device 100 allows the user to perform operations (such as specifying a button) to display payment (invoice payment) information regarding the bill (invoice). ), content C1 is displayed.

Content C1 includes three claims: billing information BL1 indicating a bill for AAA gas, billing information BL2 indicating a billing for AAA electricity (written in hiragana as "AAA electricity" in the figure), and billing information BL3 indicating a billing for AAA water. Contains information. Billing information BL1 is billing information for AAA gas, and indicates that the billed amount is "7,200 yen" and the number of days remaining until the payment deadline is "6 days." For example, billing information BL1 is billing information corresponding to an electronic bill for AAA gas.

Billing information BL2 is billing information for AAA electricity, and indicates that the billed amount is "6837 yen" and the number of days remaining until the payment deadline is "12 days." Further, billing information BL2 is billing information for AAA water supply, and indicates that the billed amount is "5,982 yen" and the number of days remaining until the payment deadline is "23 days." Note that the information indicating the payment deadline is not limited to the number of days remaining until the payment deadline, and for example, the date of the payment deadline may be displayed.

In this way, in the content C1, a plurality of bills are displayed in a list in order of their payment deadlines. Specifically, in content C1, AAA gas billing information BL1 with the closest payment deadline is arranged at the top, AAA electricity billing information BL2 with the next closest payment deadline is arranged directly below billing information BL1, Billing information BL3 for the AAA water service with the latest payment deadline is placed at the bottom. In this manner, the terminal device 100 displays a list of multiple bills in order of payment deadlines, thereby preventing the user from forgetting to pay and causing the bill payment deadline to pass. Note that the terminal device 100 is not limited to the above, and may display a list of multiple requests based on various types of information. For example, the terminal device 100 may display a list of multiple bills arranged in order based on the payment amount. Further, for example, if there are a plurality of bills whose payment deadlines are on the same day (also referred to as "same-day billings"), the terminal device 100 may display a list of the plurality of same-day billings in an order based on the payment amount. In this case, the terminal device 100 may display a list of multiple same-day deadline requests arranged in descending order of payment amount. Further, the terminal device 100 may display a list of multiple same-day deadline claims arranged in descending order of payment amount.

Here, in the area AR1 in the content C1, information for adding a bill corresponding to a paper bill to a subject of batch payment processing is arranged. For example, when the user U specifies the area AR1 (for example, by touching the position on the terminal device 100 where the area AR1 is displayed), the terminal device 100 executes a process for reading a paper bill. In this case, the terminal device 100 starts an application that reads a paper bill using, for example, a camera (imaging unit 130), reads the paper bill using the camera, and transfers the billing information corresponding to the read paper bill to the content C1. Add to. For example, the terminal device 100 may add the billing information BL4 read from a paper bill to the content C1 and display the billing information BL4 as a list together with the billing information BL1 to BL3. In this way, the terminal device 100 may be subject to batch payment processing for either electronic bills or paper bills.

In the content C1, a check box CB1 is arranged at a position corresponding to the billing information BL1. Furthermore, in the content C1, a check box CB2 is arranged at a position corresponding to the billing information BL2. In the content C1, a check box CB3 is arranged at a position corresponding to the billing information BL3. Specifically, each of the check boxes CB1 to CB3 is arranged on the left side of each of the billing information BL1 to BL3. By operating check boxes CB1 to CB3, the user U selects whether or not to subject bills corresponding to each of billing information BL1 to BL3 to batch payment processing.

For example, the user U selects the bill corresponding to the billing information BL1 to be subject to the batch payment process by specifying and checking the checkbox CB1. Furthermore, the user U specifies the check box CB1 again and removes the check, thereby excluding the bill corresponding to the billing information BL1 from being subject to the batch payment process. Note that the operation for the checkbox is the same as a normal operation, so a detailed explanation will be omitted.

In the example of FIG. 2, the user U checks all of the check boxes CB1 to CB3, and selects three bills corresponding to each of the billing information BL1 to BL3 to be subject to batch payment processing. In this case, the terminal device 100 selects three bills corresponding to each of the billing information BL1 to BL3 as a collective payment bill group. The above process corresponds to step S4 in FIG. That is, the terminal device 100 selects three bills, AAA gas, AAA electricity, and AAA water, as a lump sum bill group. Note that the user U is not limited to selecting all the requests, and may select only some of the requests that he/she wishes to process. User U may select two bills, AAA gas and AAA electricity, as a lump sum bill group without selecting AAA water bill.

In the content C1, a button BT1 labeled "Pay in bulk" is arranged below the list of billing information BL1 to BL3. When the user U specifies the button BT1, the terminal device 100 displays content C2 regarding final confirmation of execution of the lump sum payment process.

In the content C2, information for the user U to confirm the payment details of the lump sum payment process is displayed. Content C2 displays billing information BL1 to BL3 indicating payment details of each bill selected as a group of lump-sum payment bills. Note that the display contents of billing information BL1 to BL3 in content C1 and billing information BL1 to BL3 in content C2 may be different or may be the same. In content C2 of FIG. 2, instead of the remaining days displayed in content C1, information indicating when the bill is due (in FIG. 2, for October) is displayed. In Figure 2, three bills, AAA gas, AAA electricity, and AAA water, are selected as a lump sum bill group, so content C2 shows the payment details for the three bills, AAA gas, AAA electricity, and AAA water. Billing information BL1 to BL3 is arranged.

Furthermore, the content C2 includes information indicating the amount of money that the user can use for batch payment processing (also referred to as "user's balance"). In FIG. 2, content C2 includes information indicating that user U's balance is "30,000 yen." In FIG. 2, an example is shown in which the balance of user U is greater than or equal to the sum of the billing amounts for each group of lump-sum payment claims (also referred to as the "total lump-sum payment amount"). Specifically, the total lump sum payment amount for the three bills of AAA gas, AAA electricity, and AAA water is "20,019 (=7,200+6,837+5,982) yen", and user U's balance is "30,000 yen". That is, FIG. 2 shows a case where three lump-sum payment processes for AAA gas, AAA electricity, and AAA water are possible with user U's balance. Note that the process when the user's balance is less than the total lump-sum payment amount will be described later, but if the user's balance is less than the total lump-sum payment amount, the terminal device 100 will, for example, determine that the user's balance is insufficient. Users may be notified that the

Further, at the bottom of the content C2, a button BT2 (also referred to as a "lump payment execution button BT2") is arranged to instruct execution of lump sum payment processing for a group of lump sum payment requests included in the content C2. The user U causes the terminal device 100 to display the lump sum payment execution button BT2 at the bottom of the content C2 by operating the terminal device 100, such as scrolling down, and specifies the lump sum payment execution button BT2. instruct to execute batch payment processing. Thereby, the terminal device 100 executes the lump sum payment process for the batch payment bill group. The above process corresponds to step S5 in FIG. For example, the terminal device 100 notifies the payment server 10 of billing information corresponding to each bill in the group of lump-sum payments, thereby executing lump-sum payment processing for the group of lump-sum payments.

The terminal device 100 instructs the payment server 10 to perform bill payment processing (payment) in the order of AAA gas, AAA electricity, and AAA water. The terminal device 100 instructs the payment server 10 to execute the payment processing (payment) for each claim in that order by transmitting information indicating the order in which the payment processing (payment) for each claim is executed to the payment server 10. Instruct. In FIG. 2, the terminal device 100 notifies the payment server 10 of billing information (for example, billing information BL1 to BL3) corresponding to each of the three bills of AAA gas, AAA electricity, and AAA water. Execute batch payment processing for three bills: electricity and AAA water.

The payment server 10, which has received a notification from the terminal device 100 that a batch payment process will be performed for a group of lump-sum payment claims, performs remittance between accounts for each bill in the group of lump-sum payment claims.

FIG. 2 shows an example of the display transition when confirming with the user U whether or not the payment process can be executed for each bill in the group of lump-sum payment claims in the lump-sum payment process. First, in FIG. 2, the payment server 10 performs processing of remittance between accounts for the AAA gas bill among the lump sum bill group. Then, the payment server 10 notifies the terminal device 100 that the processing of remittance between accounts regarding the AAA gas bill has been completed. As a result, the terminal device 100 completes the payment process (payment) for the AAA gas bill, and displays content C3 indicating that the payment for the AAA gas bill is completed. Content C3 indicates that the AAA gas bill for October for “7,200 yen” was completed on November 24, 2020. After displaying content C3, terminal device 100 displays content C4.

The content C4 is a content in which a partial content PT1 for confirming with the user whether to subsequently perform the payment processing (payment) for the next billing is superimposed on the content C3. In the partial content PT1, a button BT3 (also referred to as a "continue button BT3"), which is written as "Yes" and instructs to continue the batch payment process, is arranged. When the user U specifies the continue button BT3, the terminal device 100 instructs the payment server 10 to perform remittance between accounts for the bill before payment processing among the group of lump-sum payment bills. Note that if the user U specifies the button labeled "No" placed below the continue button BT3, the terminal device 100 may end the batch payment process.

For example, the terminal device 100 instructs the payment server 10 to perform remittance between accounts for the next bill after the last bill for which payment processing (payment) was completed. In FIG. 2, the terminal device 100 instructs the payment server 10 to execute the payment process (payment) for the AAA electricity bill, which is the next bill after the AAA gas bill. As a result, the payment server 10 performs processing for remittance between accounts for the AAA electricity bill among the group of lump-sum payment bills. Then, the payment server 10 notifies the terminal device 100 that the processing of remittance between accounts regarding the AAA electricity bill has been completed. As a result, the terminal device 100 completes the payment process (payment) for the AAA electricity bill, and displays content C5 indicating that the payment for the AAA electricity bill has been completed. Content C5 indicates that AAA Electric's October bill for "6,837 yen" was completed on November 24, 2020. Then, the terminal device 100 performs processing for AAA water, which is the next bill after AAA electricity. Note that the transition of the display related to the AAA water bill is the same as the transition of the display of contents C4 to C5, so a description thereof will be omitted.

The batch payment process explained with the display transitions using FIG. 2 will be explained by illustrating the process flow in the payment system 1 using FIG. 3. Note that the explanation of the points explained in FIG. 2 will be omitted as appropriate. In FIG. 3, the payment server 10 performs payment processing for the AAA gas bill (step S51). The payment server 10, which has completed the payment of the AAA gas bill, notifies the terminal device 100 of the completion of the payment of the AAA gas bill (step S52).

The terminal device 100, which has received the completion of payment for the AAA gas bill, provides information indicating that the payment for the AAA gas bill has been completed to the user U, and receives an instruction from the user U to continue the lump sum payment process (step S53). Thereby, the terminal device 100 instructs the payment server 10 to continue the batch payment process (step S54).

The payment server 10, which has received the instruction to continue the lump sum payment process from the terminal device 100, performs payment processing for the AAA electricity bill (step S55). The payment server 10, which has completed the payment of the AAA electricity bill, notifies the terminal device 100 of the completion of the payment of the AAA electricity bill (step S56).

The terminal device 100, which has received the completion of payment of the AAA electricity bill, provides information indicating that the payment of the AAA electricity bill has been completed to the user U, and receives an instruction from the user U to continue the lump sum payment process (step S57). Thereby, the terminal device 100 instructs the payment server 10 to continue the batch payment process (step S58).

The payment server 10, which has received the instruction to continue the bulk payment process from the terminal device 100, performs payment processing for the AAA water bill (step S59). The payment server 10, which has completed the payment of the AAA water bill, notifies the terminal device 100 of the completion of the payment of the AAA water bill (step S60). As a result, all three bills for AAA gas, AAA electricity, and AAA water included in the lump sum bill group have been completed, so the terminal device 100 concludes the lump sum payment process and ends the process.

[1-3-2. Other examples of bulk payment processing]
Note that the above-mentioned batch payment process is just one example, and the batch payment process may take any processing form as long as it is possible for the user to pay multiple bills at once. In the above-mentioned example, utility charges such as electricity, gas, and water were exemplified as an example of the object of the lump-sum payment process, but the object of the lump-sum payment processing is not limited to utility charges. For example, in addition to utility charges, the objects of the lump-sum payment process may be various bills, such as bills for regularly subscribed magazines and newspapers, and bills for regularly delivered health foods and cosmetics. That is, the object of the lump-sum payment process may be payment (settlement) for any payment object as long as it is a bill. Further, for example, the above-described confirmation to the user may not be performed. This point will be explained using FIG. 4. Note that the same points as those in FIG. 2 are given the same reference numerals, and the description thereof will be omitted as appropriate. FIG. 4 is a diagram showing another example of content displayed by the electronic payment application. For example, content C1 and content C2 in FIG. 4 are the same as content C1 and content C2 in FIG. 2, so description thereof will be omitted.

Contents C1, C2, and C13 shown in FIG. 4 are an example of the transition of the display on the terminal device 100 when the batch payment process is executed without confirming with the user U whether the payment process can be executed for each bill in the batch payment process. shows. In this way, in the lump sum payment process shown in FIG. After completion), content C13 is displayed.

That is, in the batch payment process shown in FIG. 4, as in the batch payment process shown in FIGS. 2 and 3, each time the payment process for each bill is completed (payment is completed), the payment process (payment) for the next bill is started. To automatically execute settlement processing (payment) for a group of lump-sum payment bills one after another without asking user U whether or not to do so. In the lump sum payment process shown in FIG. 4, the payment server 10 performs the processing corresponding to steps S51, S55, and S59 in FIG. The terminal device 100 is notified of this. The terminal device 100 receives a notification from the payment server 10 that all the processing for the group of lump-sum payment requests has been completed, and displays the content C13.

Content C13 in FIG. 4 shows in a list that the payment processing for each of the three bills, AAA gas, AAA electricity, and AAA water, has been completed. By operating the terminal device 100, such as scrolling down, the user U can cause the terminal device 100 to display information indicating that payment for AAA electricity and AAA water has been completed among the content C13.

[1-4. Other processing examples (insufficient balance, etc.)
Note that the processing described above is an example, and the processing performed by the terminal device 100 is not limited to the above. For example, in the example described above, the case where the user's balance is equal to or greater than the total amount of lump-sum payment was explained as an example. If the user's balance is less than the total lump sum payment amount, the terminal device 100 may perform processing using various processing modes. An example of this point will be given below.

If the user's balance is less than the total lump sum payment amount, the terminal device 100 does not need to perform the lump sum payment process. That is, the terminal device 100 executes the lump-sum payment process when the user's balance is equal to or greater than the total lump-sum payment amount, and does not execute the lump-sum payment process when the user's balance is less than the total lump-sum payment amount. Good too. For example, if the user's balance is less than the total lump sum payment amount, the terminal device 100 may provide the user with information indicating that the lump sum payment process cannot be executed. For example, the terminal device 100 may display information indicating that the lump-sum payment process cannot be executed if the user's balance is less than the total lump-sum payment amount. For example, if the user's balance is less than the total lump sum payment amount, the terminal device 100 may display information urging the user to increase the balance.

Furthermore, if the user's balance is less than the total lump sum payment amount, the terminal device 100 may execute the payment process for some of the charges in the lump sum bill group. If the balance of the user is less than the total amount of lump-sum payment, the terminal device 100 may execute the payment processing for some of the charges in the group of lump-sum payments in descending order of priority. The priority may be determined based on the payment deadline. For example, the terminal device 100 may set the priority of the claim to be higher as the payment deadline of the claim is closer. If the balance of the user is less than the total amount of lump-sum payment, the terminal device 100 may execute the payment processing for some of the charges in the group of lump-sum payment claims in order of the payment deadline being closest.

In the above example, if the balance of user U is "20,000 yen", it is less than the total lump sum payment amount of "20,019 yen" for AAA gas, AAA electricity, and AAA water, so the terminal device 100 and AAA water, all three payments cannot be made. Therefore, the terminal device 100 ranks AAA gas with the closest payment deadline in first place, AAA electricity with the next closest payment deadline in second place, and AAA water with the latest payment deadline in third place. Payment processing may be executed in order from .

In this case, the terminal device 100 executes a settlement process (payment) for the billed amount of "7200 yen" for the AAA gas bill that ranks first. As a result, user U's balance becomes "12,800 (20,000-7,200) yen." Then, the terminal device 100 executes a settlement process (payment) for the billed amount of ``6837 yen'' of the second-ranked AAA electricity bill. As a result, user U's balance becomes "5963 (12800-6837) yen." Since user U's balance "5,963 yen" is less than the billed amount "5,982 yen" for the third-ranked AAA water bill, the terminal device 100 does not execute the settlement process (payment) for the AAA water bill. The process (lump payment process) ends. In this way, when user U's balance is "20,000 yen," the terminal device 100 processes only two bills for AAA gas and AAA electricity among the three charges: AAA gas, AAA electricity, and AAA water.

Furthermore, when the balance of user U is "10,000 yen," the terminal device 100 executes a settlement process (payment) for the billed amount of "7,200 yen" for the AAA gas that ranks first. As a result, user U's balance becomes "2,800 (10,000-7,200) yen." Since user U's balance "2,800 yen" is less than the bill amount "6,837 yen" for the second-ranked AAA electricity bill, the terminal device 100 performs the settlement process (payment) for the AAA electricity and AAA water bills. End the process (batch payment process) without executing it. In this way, when user U's balance is "10,000 yen," the terminal device 100 processes only the bill for AAA gas among the three charges: AAA gas, AAA electricity, and AAA water.

Furthermore, if the user's balance is less than the total lump sum payment amount, the terminal device 100 may perform processing to increase the user's balance. If the user's balance is less than the total lump-sum payment amount, the terminal device 100 may perform a process of charging electronic money to the user's account (also referred to as “charging process”). For example, if the user's balance is less than the total amount of the lump-sum payment, the terminal device 100 performs a charging process to increase the user's balance until it becomes equal to or greater than the total amount of the lump-sum payment. Then, the terminal device 100 executes a lump-sum payment process based on the user's balance that exceeds the total lump-sum payment amount.

[2. Terminal device configuration]
Next, the terminal device 100 for realizing the above-described payment processing will be described using FIG. 5. FIG. 5 is a diagram illustrating a configuration example of a terminal device according to an embodiment. As shown in FIG. 5, the terminal device 100 includes a communication section 110, a storage section 120, an imaging section 130, a display section 140, and a control section 150.

(Communication Department 110)
The communication unit 110 is realized by, for example, a NIC (Network Interface Card). The communication unit 110 is connected to the network N by wire or wirelessly, and sends and receives information to and from the payment server 10 that distributes electronic payment applications, the business server 200, and the like.

(Storage unit 120)
The storage unit 120 is realized by, for example, a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. Furthermore, the storage unit 120 stores images captured by the imaging unit 130.

(Imaging unit 130)
The imaging unit 130 is an imaging device (camera) for capturing images (moving images or still images). The imaging unit 130 is configured by, for example, an imaging element such as a charged-coupled device (CCD) sensor or a complementary metal-oxide-semiconductor (CMOS) sensor.

(Display section 140)
The display unit 140 is a display screen of a tablet terminal or the like realized by, for example, a liquid crystal display or an organic EL (Electro-Luminescence) display, and is a display device for displaying various information. The display unit 140 displays various information under the control of the display control unit 1525. Further, the display unit 140 may function as a reception unit that receives user operations using a touch panel function. In this case, the display unit 140 also functions as an input device that receives various operations from the user using his or her finger or a dedicated pen.

(Control unit 150)
The control unit 150 is a controller, and for example, various programs stored in the storage device inside the terminal device 100 use the RAM as a work area by a CPU (Central Processing Unit), an MPU (Micro Processing Unit), etc. This is achieved through execution. Further, the control unit 150 is a controller, and is realized by, for example, an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

Here, the control unit 150 realizes various functions related to the terminal device 100 by executing a plurality of applications. For example, in the example shown in FIG. 5, the control unit 150 executes a first application 151 and a second application 152. In addition to the applications shown in FIG. 5, the control unit 150 may execute any number of applications to perform any function.

The first application 151 is an application that becomes the OS (Operating System) of the terminal device 100. The second application 152 causes the terminal device 100 to execute various payment processes such as the above-mentioned batch payment process. An example of the functional configuration of the second application 152 will be described below with reference to FIG. 6. FIG. 6 is a diagram illustrating a configuration example of the second application according to the embodiment. As shown in FIG. 6, the second application 152 according to the embodiment includes a reception section 1521, a notification section 1522, a provision section 1523, a payment processing section 1524, and a display control section 1525, which will be described below. Realize or execute information processing functions and actions.

(Reception Department 1521)
The reception unit 1521 receives operations from a user who uses the terminal device 100. The reception unit 1521 receives user operations via the display unit 140 having a touch panel function. The reception unit 1521 receives various information from external devices. The reception unit 1521 receives various information from the payment server 10. The reception unit 1521 receives various information from the payment server 10 via the communication unit 110. The reception unit 1521 receives billing information from the payment server 10.

(Notification section 1522)
The notification unit 1522 notifies external devices of various information. The notification unit 1522 notifies the payment server 10 of various information. The notification unit 1522 transmits various information to the payment server 10 via the communication unit 110. The notification unit 1522 transmits billing information corresponding to each bill in the collective payment bill group to the payment server 10. The notification unit 1522 transmits billing information corresponding to each of three bills: AAA gas, AAA electricity, and AAA water to the payment server 10.

The notification unit 1522 instructs the payment server 10 to perform bill payment processing (payment) in the order of AAA gas, AAA electricity, and AAA water. The notification unit 1522 transmits information indicating the order in which billing settlement processing (payment) is to be executed to the settlement server 10. The notification unit 1522 notifies the payment server 10 of billing information corresponding to each of three bills: AAA gas, AAA electricity, and AAA water.

(Providing Department 1523)
The providing unit 1523 provides various information to the user who uses the terminal device 100. The providing unit 1523 provides various information to the user via the display unit 140. The providing unit 1523 displays various information on the display unit 140. The providing unit 1523 instructs the display control unit 1525 to display various information on the display unit 140.

The providing unit 1523 provides the user with a plurality of pieces of billing information indicating the contents of each of the plurality of bills made to the user. The providing unit 1523 provides a plurality of billing information indicating the contents of each of a plurality of bills including a bill for which an electronic bill has been accepted. The providing unit 1523 provides a plurality of pieces of billing information indicating the contents of each of a plurality of bills including a bill read from a bill printed on paper. The providing unit 1523 provides a plurality of pieces of billing information indicating the contents of each of a plurality of bills including a bill for payment of utility charges.

The providing unit 1523 displays a list of multiple requests. The providing unit 1523 displays a list of multiple claims arranged in a predetermined direction in an order based on predetermined criteria. The providing unit 1523 displays a list of multiple bills arranged in descending order of payment deadline. The providing unit 1523 displays a list of multiple claims arranged in the order based on the payment amount. For example, if there are multiple claims with payment deadlines on the same day (same-day claims), the providing unit 1523 may display a list of the multiple same-day claims in an order based on the payment amount. In this case, the providing unit 1523 may display a list of multiple same-day deadline requests arranged in descending order of payment amount. Further, the providing unit 1523 may display a list of multiple same-day deadline requests arranged in descending order of payment amount. For example, the providing unit 1523 may display a list of multiple claims arranged in descending order of payment amount. Thereby, the providing unit 1523 can make the user aware of a bill that requires a large amount of expense. Further, for example, the providing unit 1523 may display a list of multiple claims arranged in descending order of payment amount. The providing unit 1523 provides, as billing information, information including at least one of the following: information indicating the billing amount, information indicating the billing source, and information indicating the transaction object to be billed.

The providing unit 1523 provides various contents such as contents C1, C2, C3, C4, C5, and C13 to the user. The providing unit 1523 displays various contents such as contents C1, C2, C3, C4, C5, and C13 on the display unit 140. The providing unit 1523 displays various contents such as contents C1, C2, C3, C4, C5, and C13 on the display unit 140.

For example, the providing unit 1523 generates various contents as shown in contents C1, C2, C3, C4, C5, C13, etc. In this case, the providing unit 1523 generates the screen (content) using various technologies such as Java (registered trademark) as appropriate. Note that the providing unit 1523 may generate the screen (content) based on CSS, JavaScript (registered trademark), or HTML format. Further, for example, the providing unit 1523 may generate screens (content) in various formats such as JPEG (Joint Photographic Experts Group), GIF (Graphics Interchange Format), and PNG (Portable Network Graphics). The providing unit 1523 displays the generated content on the display unit 140.

(Payment processing unit 1524)
When the user selects a group of claims that includes at least two or more claims to be paid at once among multiple claims, the payment processing unit 1524 performs batch payment processing to collectively pay for each of the group of claims. Execute. The payment processing unit 1524 executes the batch payment process when the user selects a group of claims and then performs the batch payment operation, which is one operation for performing the batch payment process.

The payment processing unit 1524 executes the lump sum payment process when the remaining amount, which is the amount that the user can use for the lump sum payment process, satisfies a predetermined condition. The payment processing unit 1524 executes the batch payment process when the comparison result between the user's remaining balance and the sum of the billing amounts of each billing group satisfies a predetermined condition. The payment processing unit 1524 executes batch payment processing when the user's remaining balance is greater than or equal to the sum of the billing amounts for each of the billing groups, and when the user's remaining balance is less than the sum of the billing amounts for each of the billing groups. , do not perform bulk payment processing.

The payment processing unit 1524 executes payment processing for some of the claims in the group of claims when the user's remaining balance is less than the sum of the charges for each of the group of claims. The payment processing unit 1524 performs payment processing on some of the claims in the order of priority among the claims. The payment processing unit 1524 performs payment processing on some of the claims in the order of payment deadlines from among the claims.

The payment processing unit 1524 executes processing to increase the user's remaining balance when the user's remaining balance is less than the sum of the billing amounts of each billing group. The payment processing unit 1524 executes a process of increasing the user's balance until it becomes equal to or greater than the sum of the billing amounts of each billing group, and then executes a lump-sum settlement process. The payment processing unit 1524 transmits information indicating the contents of each bill group to an external server device that realizes remittance between accounts.

The payment processing unit 1524 performs various processes such as normal payment processing in addition to batch payment processing. When the user performs an operation for making a payment, the payment processing unit 1524 executes payment processing for paying the bill indicated by the billing information. For example, when the user performs an operation to make a payment, the payment processing unit 1524 executes payment processing using the electronic payment service provided by the payment server 10.

In addition, if the user performs an operation after selecting any billing information, the payment processing unit 1524 executes the payment processing to pay the bill indicated by the selected billing information. Good too. For example, when the user performs an operation to make a payment after selecting one of the plurality of billing information provided by the providing unit 1523, the payment processing unit 1524 selects one of the billing information provided by the providing unit 1523, and then performs an operation to make a payment. The payment process for paying the bill is executed using the electronic payment service provided by the payment server 10.

Further, the payment processing unit 1524 may execute payment processing for paying utility charges. For example, the payment processing unit 1524 executes payment processing for paying utility fees charged to users by a business that provides services (public utilities) that supply water, electricity, gas, etc. to users. Further, the payment processing unit 1524 may notify the contents of the bill indicated by the billing information to an external server device that realizes remittance between accounts.

In addition, if the user selects automatic content, the payment processing unit 1524 executes payment processing to automatically pay when a request for a transaction object corresponding to the object information selected by the user occurs. You may. For example, if the user selects automatic content included in the target content corresponding to the transaction object "Electricity", the payment processing unit 1524 will receive billing information regarding the transaction object "Electricity" from the payment server 10. , executes payment processing to automatically pay the billed amount by the payment date indicated by the billing information. To give a specific example, if the user performs an operation to make a payment after the payment server 10 distributes the billing information regarding the transaction object "electricity" and before the payment deadline, the payment processing unit 1524 A payment process is executed in accordance with the operation, and if the user does not perform an operation to make a payment by the payment deadline, a payment process for automatically making the payment is executed.

Note that the payment processing unit 1524 may perform payment processing using a payment form sent by the business to the user. For example, the imaging unit 130 reads a barcode included in a payment form via an electronic payment application in response to a user's operation. The payment processing unit 1524 then executes payment processing based on the billing source, billing amount, etc. indicated by the read barcode.

Further, the payment processing unit 1524 may execute payment processing using electronic payment at a store. For example, the payment processing unit 1524 may collect user information that identifies the user, information indicating store identification information photographed by the imaging unit 130, and the payment amount input into the terminal device 100 by the user or store clerk. The payment information shown is transmitted to the payment server 10.

(Display control unit 1525)
The display control unit 1525 controls the display on the screen (display unit 140) of the terminal device 100. The display control unit 1525 controls the display on the display unit 140 according to user operations. The display control unit 1525 controls the display on the screen (display unit 140) of the terminal device according to the payment processing executed by the payment processing unit 1524. The display control unit 1525 controls the display on the screen (display unit 140) of the terminal device according to instructions from the providing unit 1523.

Furthermore, when the user makes a payment using a payment slip, the display control unit 1525 displays a screen for photographing a barcode or a screen indicating that the payment process has been executed in accordance with the user's operation. You may let them. When a user reads a paper bill and makes a payment, the display control unit 1525 displays a screen for photographing information printed on the bill (barcode, character information, etc.) according to the user's operations. , a screen indicating that the payment process has been executed may be displayed. Furthermore, when the user makes a payment using electronic payment at a store, the display control unit 1525 may control the display of a screen related to electronic payment according to the user's operation. For example, the display control unit 1526 may display a screen for photographing an image of store identification information for identifying a store, a screen for accepting input of a payment amount from a user U or a store clerk, and a screen for transmitting payment information to the payment server 10. Display a screen indicating that the message has been sent.

[3. Payment server configuration]
Next, the configuration of the payment server 10 will be explained using FIG. 7. FIG. 7 is a diagram illustrating a configuration example of a payment server according to an embodiment. As shown in FIG. 7, the payment server 10 includes a communication section 20, a storage section 30, and a control section 40.

(Communication department 20)
The communication unit 20 is realized by, for example, a NIC or the like. The communication unit 20 is connected to the network N by wire or wirelessly, and transmits and receives information to and from the terminal device 100, the operator server 200, and the like.

(Storage unit 30)
The storage unit 30 is realized by, for example, a semiconductor memory device such as a RAM or a flash memory, or a storage device such as a hard disk or an optical disk. As shown in FIG. 7, the storage unit 30 includes an account database 31 and a billing information database 32.

(Account database 31)
The account database 31 stores various information regarding accounts of users and businesses. Here, an example of information stored in the account database 31 will be explained using FIG. 8. FIG. 8 is a diagram illustrating an example of an account database according to the embodiment. In the example of FIG. 8, the account database 31 has items such as "account ID", "owner information", and "account balance".

“Account ID” indicates identification information for identifying an account. "Owner information" indicates information regarding the owner (user or business operator) of the account, and stores, for example, identification information (identifier) for identifying the owner. "Account balance" indicates the balance of an account owned by a user or business operator.

That is, FIG. 8 shows an example in which the information on the owner of the account identified by the account ID "AID #1" is "User #1" and the account balance is "30000".

(Billing information database 32)
The billing information database 32 stores billing information transmitted from the business server 200. Here, an example of information stored in the billing information database 32 will be explained using FIG. 9. FIG. 9 is a diagram illustrating an example of a billing information database according to the embodiment. In the example of FIG. 9, the billing information database 32 has items such as "billing information ID", "company information", "user information", "billing object", "billing amount", and "payment deadline".

"Billing information ID" indicates identification information for identifying billing information. "Business information" indicates information regarding the business that is the billing party, and stores, for example, identification information for identifying the business. "User information" indicates information regarding the user who is the billing party, and stores, for example, identification information for identifying the user. “Billing object” indicates the transaction object to be charged. “Billed amount” indicates the amount to be billed to the billing party. “Payment deadline” indicates the deadline for payment of the bill corresponding to the billing information. For example, the bill corresponding to billing information identified by billing information ID "AID #2" indicates that the payment deadline is "2020/11/30", that is, November 30, 2020.

In FIG. 9, the billing information identified by the billing information ID "AID #1" includes business information "Business #1," user information "User #1," billing target "Electricity," and billing amount "6837. An example in which information such as "(yen)" and payment deadline "2020/12/5" is included is shown.

(Control unit 40)
The control unit 40 is a controller, and is realized by, for example, a CPU, an MPU, or the like executing various programs stored in a storage device inside the payment server 10 using a RAM as a work area. Further, the control unit 40 is a controller, and is realized by, for example, an integrated circuit such as an ASIC or an FPGA. As shown in FIG. 7, the control unit 40 according to the embodiment includes a reception unit 41, a provision unit 42, and a payment processing unit 43, and realizes or executes information processing functions and operations described below. .

(Reception Department 41)
The reception unit 41 receives billing information. The reception unit 41 receives billing information from the business server 200, including information indicating the user who has charged the fee, information indicating the business entity that charges the fee to the user, the billing amount, and the transaction object to be billed. accept.

Further, the reception unit 41 may receive notification of billing information to be paid. The reception unit 41 receives notification of billing information selected by the user U as a subject of payment processing. The reception unit 41 receives various information from the terminal device 100 via the communication unit 20. The payment server 10 receives billing information for each bill that is subject to batch payment processing from the terminal device 100. The payment server 10 receives billing information for each of three bills: water, electricity, and gas from the terminal device 100.

The receiving unit 41 receives from the terminal device 100 information indicating the order in which billing settlement processing (payment) is to be executed. The reception unit 41 receives billing information corresponding to each of three bills: AAA gas, AAA electricity, and AAA water from the terminal device 100.

(Providing unit 42)
The providing unit 42 distributes (provides) billing information. The providing unit 42 transmits billing information corresponding to the user U to the terminal device 100. The providing unit 42 transmits a plurality of pieces of billing information indicating the contents of each of the plurality of bills of the user U such as water, electricity, gas, etc. to the terminal device 100. The providing unit 42 transmits a plurality of pieces of billing information displayed in a list on the terminal device 100 to the terminal device 100.

The providing unit 42 notifies the terminal device 100 of the request for which the process of remittance between accounts has been completed. The providing unit 42 notifies the terminal device 100 that the inter-account remittance process for the bill for which payment processing was instructed by the terminal device 100 has been completed.

(Payment processing unit 43)
The payment processing unit 43 executes payment processing according to the billing information corresponding to the notification received by the reception unit 41. The payment processing unit 43 remits electronic money equivalent to the billed amount from the user U's account to the billing source's account corresponding to the notified billing information.

The payment processing unit 43 executes batch payment processing. The payment processing unit 43 performs remittance between accounts for each bill in the collective payment bill group. The payment processing unit 43 executes payment processing for each of the plurality of claims included in the collective payment claim group. The payment processing unit 43 uses information (order information) indicating the order in which the payment processing (payment) of the claims is executed, and targets each of the plurality of claims included in the collective payment claim group in the order indicated by the order information. , execute payment processing.

[4. Payment processing flow]
The payment processing procedure of the terminal device 100 according to the embodiment will be described using FIG. 10. FIG. 10 is a flowchart illustrating an example of a payment processing procedure according to the embodiment.

As shown in FIG. 10, the terminal device 100 provides the user with a plurality of billing information indicating the contents of each of the plurality of billings to the user (step S101).

If the user has not selected a group of claims to be paid together (step S102; No), the terminal device 100 waits until the user selects a group of claims to be paid together. On the other hand, if the user selects a group of claims to be paid together (step S102; Yes), the terminal device 100 executes a batch payment process to pay for each of the group of claims at once (step S103). .

[5. others〕
Among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, and conversely, all of the processes described as being performed manually can be performed manually. Alternatively, some of the steps can be performed automatically using known methods. In addition, information including the processing procedures, specific names, and various data and parameters shown in the above documents and drawings may be changed arbitrarily, unless otherwise specified. For example, the various information shown in each figure is not limited to the illustrated information.

Further, each component of each device shown in the drawings is functionally conceptual, and does not necessarily need to be physically configured as shown in the drawings. In other words, the specific form of distributing and integrating each device is not limited to what is shown in the diagram, and all or part of the devices can be functionally or physically distributed or integrated in arbitrary units depending on various loads and usage conditions. Can be integrated and configured.

Furthermore, the embodiments described above can be combined as appropriate within a range that does not conflict with the processing contents.

[6. effect〕
As described above, the terminal device 100 according to the embodiment includes the providing section 1523 and the payment processing section 1524. The providing unit 1523 provides the user with a plurality of pieces of billing information indicating the contents of each of the plurality of bills made to the user. When the user selects a group of claims that includes at least two or more claims to be paid at once among multiple claims, the payment processing unit 1524 performs batch payment processing to collectively pay for each of the group of claims. Execute.

As a result, the terminal device 100 according to the embodiment can collectively process two or more charges to a user, thereby improving usability in settling charges to a user.

Furthermore, in the terminal device 100 according to the embodiment, the providing unit 1523 provides a plurality of billing information indicating the contents of each of a plurality of bills including a bill for which an electronic bill has been accepted.

As a result, the terminal device 100 according to the embodiment can process two or more claims at once, including electronic billing, so that the terminal device 100 can process two or more claims at once, including electronic billing. Usability can be improved.

Further, in the terminal device 100 according to the embodiment, the providing unit 1523 provides a plurality of billing information indicating the contents of each of a plurality of bills including a bill read from a bill printed on paper.

As a result, the terminal device 100 according to the embodiment can process two or more bills at once, including a bill printed on a paper bill. Usability in bill settlement can be improved.

Furthermore, in the terminal device 100 according to the embodiment, the providing unit 1523 provides a plurality of billing information indicating the contents of each of a plurality of bills including a bill for payment of utility charges.

As a result, the terminal device 100 according to the embodiment can process two or more bills at once, targeting a plurality of bills including a bill for payment of utility charges. Usability can be improved.

Furthermore, in the terminal device 100 according to the embodiment, the providing unit 1523 displays a list of multiple requests.

As a result, the terminal device 100 according to the embodiment can display a list of multiple claims, thereby making it easier for the user to select the claims for which he or she wants to pay all at once. Usability can be improved.

Furthermore, in the terminal device 100 according to the embodiment, the providing unit 1523 displays a list of multiple claims arranged in a predetermined direction in an order based on a predetermined criterion.

As a result, the terminal device 100 according to the embodiment can display a list of multiple claims in a predetermined order and in a predetermined direction, making it easier for the user to check the multiple claims. Usability in bill settlement can be improved.

Furthermore, in the terminal device 100 according to the embodiment, the providing unit 1523 displays a list of multiple bills arranged in order of payment deadline.

As a result, the terminal device 100 according to the embodiment displays a list of multiple bills in order of payment deadline, thereby preventing the user from forgetting to pay and exceeding the bill payment deadline. As a result, usability in bill settlement for users can be improved.

Furthermore, in the terminal device 100 according to the embodiment, the providing unit 1523 displays a list of multiple claims arranged in an order based on the payment amount.

As a result, the terminal device 100 according to the embodiment can display a list of a plurality of claims in an order based on the payment amount, thereby displaying the claims according to the payment amount to the user. The usability of payments can be improved.

In addition, in the terminal device 100 according to the embodiment, the payment processing unit 1524 performs a lump sum payment when the user selects a group of claims and then performs a lump sum payment operation, which is one operation for carrying out batch payment processing. Execute processing.

As a result, the terminal device 100 according to the embodiment can save the user's time and effort by executing the batch payment process with one operation of the batch payment operation, thereby improving usability in the payment of charges to the user. can be improved.

Furthermore, in the terminal device 100 according to the embodiment, the payment processing unit 1524 executes the lump sum payment process when the remaining amount, which is the amount that the user can use for the lump sum payment process, satisfies a predetermined condition.

As a result, when the user's balance satisfies a predetermined condition, the terminal device 100 according to the embodiment executes the lump sum payment process, for example, by adding up the billing amounts of each billing group (total lump sum payment amount). Since it is possible to suppress processing when batch payment processing is not possible, such as when the user's balance is insufficient, it is possible to improve usability in payment of charges to users.

Furthermore, in the terminal device 100 according to the embodiment, the payment processing unit 1524 executes the batch payment process when the comparison result between the user's remaining balance and the sum of the billing amounts of each billing group satisfies a predetermined condition. .

Thereby, the terminal device 100 according to the embodiment executes the lump sum payment process according to the comparison result between the user's remaining balance and the total amount to be paid, so that, for example, the user's balance is insufficient for the total lump sum payment amount. etc., it is possible to suppress processing when batch payment processing is not possible, thereby improving usability in payment of charges to users.

In addition, in the terminal device 100 according to the embodiment, if the user's remaining balance is equal to or greater than the sum of the billing amounts of each billing group, batch payment processing is executed, and the user's balance is equal to or greater than the sum of the billing amounts of each billing group. If the total is less than the total, batch payment processing will not be executed.

As a result, in the terminal device 100 according to the embodiment, the payment processing unit 1524 adds the user's remaining balance to the total lump-sum payment amount by executing the lump-sum payment process when the user's remaining balance is equal to or greater than the total amount to be paid. Since it is possible to prevent bulk payment processing from being performed due to insufficient funds, etc., it is possible to improve usability in payment of bills to users.

Furthermore, in the terminal device 100 according to the embodiment, the payment processing unit 1524 performs payment processing for some of the claims in the group of claims when the user's remaining balance is less than the sum of the charges for each of the group of claims. Execute.

As a result, if the user's remaining balance is less than the total lump-sum payment amount, the terminal device 100 according to the embodiment executes payment processing for some of the charges, so that the terminal device 100 can prevent the user from running out of funds by executing payment processing for some of the charges. Since payment processing can be performed even if there is a problem, it is possible to improve usability in payment of charges to users.

Furthermore, in the terminal device 100 according to the embodiment, the payment processing unit 1524 performs payment processing on some of the claims in the order of priority among the claims.

As a result, if the balance of the user's balance is less than the total lump-sum payment amount, the terminal device 100 according to the embodiment can process the payment by giving priority to the claim with a higher priority. Usability can be improved.

Furthermore, in the terminal device 100 according to the embodiment, the payment processing unit 1524 executes payment processing for some of the claims in the order of payment deadlines from among the claims group.

As a result, when the user's remaining balance is less than the total lump sum payment amount, the terminal device 100 according to the embodiment prioritizes the payment process for bills with close payment deadlines, so that the user forgets to pay, Since it is possible to prevent the bill payment deadline from being passed, it is possible to improve usability in bill settlement for the user.

Furthermore, in the terminal device 100 according to the embodiment, the payment processing unit 1524 executes processing to increase the user's remaining balance when the user's remaining balance is less than the sum of the billing amounts of each billing group.

As a result, when the user's remaining balance is less than the total lump sum payment amount, the terminal device 100 according to the embodiment executes processing to increase the user's remaining balance, for example, by increasing the user's balance in the lump sum payment process. Since the amount can be increased to an amount that is practicable, it is possible to improve the usability of bill settlement for users.

Further, in the terminal device 100 according to the embodiment, the payment processing unit 1524 executes a process of increasing the user's balance until it becomes equal to or greater than the sum of the billing amounts of each billing group, and then executes a lump-sum settlement process. .

As a result, when the user's remaining balance is less than the total lump-sum payment amount, the terminal device 100 according to the embodiment increases the user's balance until it becomes equal to or more than the lump-sum payment total amount, and executes the lump-sum payment process. , it is possible to improve the usability of bill settlement for users.

Further, in the terminal device 100 according to the embodiment, the providing unit 1523 includes, as billing information, at least one of information indicating the billing amount, information indicating the billing source, and information indicating the transaction object to be billed. Provide information.

As a result, the terminal device 100 according to the embodiment can provide the user with useful information for determining whether or not to settle the bill, thereby improving usability in settling the bill for the user. Can be done.

Furthermore, in the terminal device 100 according to the embodiment, the payment processing unit 1524 transmits information indicating the contents of each bill group to an external server device that realizes remittance between accounts.

As a result, the terminal device 100 according to the embodiment transmits information indicating the contents of each bill group to an external server device that realizes remittance between accounts, thereby transferring money between accounts on the external server device. Remittances can complete the settlement of each bill group.

[7. Hardware configuration]
Further, the terminal device 100 according to each of the embodiments described above is realized by, for example, a computer 1000 having a configuration as shown in FIG. 11. The following will explain the terminal device 100 as an example. FIG. 11 is a hardware configuration diagram showing an example of a computer that implements the functions of the terminal device. Computer 1000 has CPU 1100, ROM 1200, RAM 1300, HDD 1400, communication interface (I/F) 1500, input/output interface (I/F) 1600, and media interface (I/F) 1700.

CPU 1100 operates based on a program stored in ROM 1200 or HDD 1400, and controls each part. The ROM 1200 stores a boot program executed by the CPU 1100 when the computer 1000 is started, programs depending on the hardware of the computer 1000, and the like.

The HDD 1400 stores programs executed by the CPU 1100, data used by the programs, and the like. Communication interface 1500 receives data from other devices via communication network 500 (corresponding to network N in the embodiment) and sends it to CPU 1100, and also sends data generated by CPU 1100 to other devices via communication network 500. Send to device.

The CPU 1100 controls output devices such as a display and a printer, and input devices such as a keyboard and mouse via an input/output interface 1600. CPU 1100 obtains data from an input device via input/output interface 1600. Further, CPU 1100 outputs the generated data to an output device via input/output interface 1600.

Media interface 1700 reads programs or data stored in recording medium 1800 and provides them to CPU 1100 via RAM 1300. CPU 1100 loads this program from recording medium 1800 onto RAM 1300 via media interface 1700, and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase change rewritable disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. etc.

For example, when the computer 1000 functions as the terminal device 100, the CPU 1100 of the computer 1000 realizes the functions of the control unit 150 by executing a program loaded onto the RAM 1300. Further, each data in the storage device of the terminal device 100 is stored in the HDD 1400. The CPU 1100 of the computer 1000 reads these programs from the recording medium 1800 and executes them, but as another example, these programs may be acquired from another device via a predetermined communication network.

[8. others〕
Some of the embodiments of the present application have been described above in detail based on the drawings, but these are merely examples, and various modifications and variations may be made based on the knowledge of those skilled in the art, including the embodiments described in the disclosure section of the invention. It is possible to carry out the invention in other forms with modifications.

Furthermore, the configuration of the terminal device 100 described above can be changed flexibly, such as implementing some functions by calling an external platform or the like using an API (Application Programming Interface), network computing, or the like.

Further, the "unit" described in the claims can be read as "means", "circuit", etc. For example, the reception unit can be read as reception means or reception circuit.

1 Payment system 10 Payment server 20 Communication unit 30 Storage unit 31 Account database 32 Billing information database 40 Control unit 41 Reception unit 42 Providing unit 43 Payment processing unit 100 Terminal device 110 Communication unit 120 Storage unit 130 Imaging unit 140 Display unit 150 Control unit 151 First application 152 Second application 1521 Reception section 1522 Notification section 1523 Providing section 1524 Payment processing section 1525 Display control section

Claims (19)

A plurality of billing information indicating the contents of each of the plurality of bills, including a bill read from a bill printed on paper, which is a plurality of bills to the user , and a payment corresponding to the plurality of billing information. generating payment content including a first button for accepting execution of the process, providing the payment content to the user, and at least two or more claims to be collectively paid by the user among the plurality of claims; If you select a group of claims that includes a group of claims, information for confirming the contents of the lump sum payment including the contents of each of the group of claims selected as a target of the lump sum payment , and information for confirming the contents of the lump sum payment for the group of claims selected as the target of the lump sum payment . 2 buttons, providing the user with bulk payment content;
When an operation is performed to make a lump-sum payment via the lump-sum payment content, the payment server that performs the payment is notified of the content indicated by the billing information of each billing group selected as a lump-sum payment target. A payment program for causing a computer to execute a payment processing procedure for transmitting claims and performing a batch payment process for collectively paying each of the claims. The provision procedure is as follows:
The payment program according to claim 1, wherein the payment program provides the plurality of billing information indicating the content of each of the plurality of bills including a bill for which an electronic bill has been accepted. The provision procedure is as follows:
The payment program according to claim 1 or 2, wherein the payment program displays a list of the plurality of claims. The provision procedure is as follows:
The payment program according to claim 3 , wherein the plurality of claims are displayed in a list in a predetermined direction in an order based on a predetermined criterion. The provision procedure is as follows:
The payment program according to claim 3 or 4 , wherein the plurality of claims are displayed in a list in order of payment deadline. The provision procedure is as follows:
The payment program according to any one of claims 3 to 5 , wherein the plurality of claims are arranged and displayed as a list in an order based on the payment amount. The payment processing procedure is as follows:
If the user selects the group of claims and then performs a lump sum payment operation, which is one operation for carrying out the batch payment process, the payment server causes the payment server to execute the lump sum payment process. The payment program according to any one of claims 1 to 6 . The payment processing procedure is as follows:
If the remaining balance, which is the amount available for the lump-sum payment process , satisfies the batch payment enablement condition that the group of claims selected for lump-sum payment can be paid at once, the user can perform the lump-sum payment process as described above. 8. The payment program according to claim 1, wherein the payment program is executed by a payment server . The payment processing procedure is as follows:
If a comparison result between the remaining amount of the user and the sum of the billed amounts of each of the billing groups satisfies the condition for batch payment , the billing method causes the payment server to execute the batch payment process. Payment program described in Section 8 . The payment processing procedure is as follows:
If the remaining balance of the user is greater than or equal to the sum of the billing amounts of each of the billing groups, the payment server executes the batch payment process, and the remaining balance of the user is equal to or greater than the sum of the billing amounts of each of the billing groups. The payment program according to claim 8 or 9 , wherein the payment program does not cause the payment server to execute the batch payment process if the total amount is less than the total amount . The payment processing procedure is as follows:
If the remaining balance of the user is less than the sum of the billing amounts of each of the billing groups, the payment server may cause the payment server to execute payment processing for some of the billings in the billing group. The payment program according to claim 8 or 9 . The payment processing procedure is as follows:
12. The payment program according to claim 11 , wherein the payment server executes payment processing for some of the claims in the order of priority among the claims. The payment processing procedure is as follows:
13. The payment program according to claim 11 or 12 , wherein the payment server executes payment processing for some of the claims in the order of payment deadlines from among the group of claims. The payment processing procedure is as follows:
10. If the remaining balance of the user is less than the sum of the billing amounts of each of the billing groups, a process for increasing the remaining balance of the user is executed. Payment program. The payment processing procedure is as follows:
14. Claim 14 , wherein the payment server is caused to perform the lump-sum payment process after performing a process of increasing the remaining balance of the user until it becomes equal to or greater than the sum of the billing amounts of each of the billing groups. Payment programs listed in . The provision procedure is as follows:
Claims 1 to 15 characterized in that the billing information includes at least one of the following: information indicating the billing amount, information indicating the billing source, and information indicating the transaction object to be billed. Payment program listed in any one of the above. The payment processing procedure is as follows:
The payment program according to any one of claims 1 to 16 , characterized in that information indicating the contents of each of the bill groups is transmitted to the payment server that realizes remittance between accounts. A plurality of billing information indicating the contents of each of the plurality of bills, including a bill read from a bill printed on paper, which is a plurality of bills to the user , and a payment corresponding to the plurality of billing information. generating payment content including a first button for accepting execution of the process, providing the payment content to the user, and at least two or more claims to be collectively paid by the user among the plurality of claims; If you select a group of claims that includes a group of claims, information for confirming the contents of the lump sum payment including the contents of each of the group of claims selected as a target of the lump sum payment , and information for confirming the contents of the lump sum payment for the group of claims selected as the target of the lump sum payment . a provision unit that provides the user with bulk payment content including two buttons ;
When an operation is performed to make a lump-sum payment via the lump-sum payment content, the payment server that performs the payment is notified of the content indicated by the billing information of each billing group selected as a lump-sum payment target. A payment processing unit configured to send a claim and execute a batch payment process for collectively paying each of the claims. A payment method executed by a payment device,
A plurality of billing information indicating the contents of each of the plurality of bills, including a bill read from a bill printed on paper, which is a plurality of bills to the user , and a payment corresponding to the plurality of billing information. generating payment content including a first button for accepting execution of the process, providing the payment content to the user, and at least two or more claims to be paid collectively by the user among the plurality of claims; If you select a group of claims that includes a group of claims, information for confirming the contents of the lump sum payment including the contents of each of the group of claims selected as a target of the lump sum payment , and information for confirming the contents of the lump sum payment for the group of claims selected as the target of the lump sum payment . a provision step of providing the user with bulk payment content including two buttons ;
When an operation is performed to make a lump-sum payment via the lump-sum payment content, the payment server that performs the payment is notified of the content indicated by the billing information of each billing group selected as a lump-sum payment target. A payment method for causing a computer to execute a payment processing step of transmitting a claim and performing a batch payment process for collectively paying each of the claims.

Images