Information processing device, information processing method, and information processing program

Abstract

To improve convenience of users.SOLUTION: An information processing device includes: an acquisition part for acquiring invoice information represented by an invoice; a specification part for specifying a payable period based on the invoice information; a setting part for selecting a payment date satisfying a prescribed condition from the specified payable period and setting the selected payment date; and a settlement processing part for performing settlement based on the invoice information on the set payment date.SELECTED DRAWING: Figure 1

Description

[Technical field]

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

[0002] Conventionally, there is known a technology for providing a service in which an electronic invoice (referred to as an "electronic invoice") is sent to a user's terminal and the invoice amount can be paid with electronic money. In addition, there is also known a technology for providing a service in which information such as the invoice amount printed on a paper invoice is read and the payment can be made with electronic money, even if the invoice is a paper invoice. [Prior art documents] [Patent documents]

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

[0004] However, the above-mentioned conventional techniques are not necessarily convenient for users.

[0005] For example, in the above-mentioned conventional technology, the timing for making payment on an invoice is the timing when the user performs the payment procedure, so there is a possibility that the user may forget to make a payment. Also, in the above-mentioned conventional technology, the user may not always be able to make a payment when he or she wishes (for example, after payday).

[0006] The present application has been made in consideration of the above, and has an object to provide an information processing device, an information processing method, and an information processing program that improve convenience for users. [Means for solving the problem]

[0007] The information processing device of the present application is characterized by comprising an acquisition unit that acquires invoice information indicated on an invoice via a user terminal of a user that photographs a specified code or a character string used for optical character recognition, or receives data from a specified terminal, an identification unit that identifies a payment period based on the invoice information, a setting unit that selects a payment date that satisfies specified conditions from the identified payment period and sets the selected payment date, and a payment processing unit that makes payment based on the invoice information on the set payment date.

[0008] The information processing device of the present application is a payment service using a user terminal, and is characterized in that it comprises an acquisition unit that acquires invoice information indicated on an invoice via an application that provides a payment service that, upon receiving notification of user identification information that identifies the user, payment destination identification information that identifies the payment destination, and a payment amount, debits electronic money for the payment amount from an account corresponding to the user identification information and deposits the payment amount into an account corresponding to the payment destination identification information, an identification unit that identifies a payment period based on the invoice information, a setting unit that selects a payment date that satisfies specified conditions from the identified payment period and sets the selected payment date, and a payment processing unit that performs payment based on the invoice information on the set payment date by debiting electronic money for the payment amount indicated by the invoice information from an account corresponding to the user and depositing the payment amount indicated by the invoice information into an account corresponding to the business identification information indicated by the invoice information.

[0009] The information processing device of the present application is a payment service using a user terminal, and upon receiving notification of user identification information that identifies the user, payment destination identification information that identifies the payment destination, and a payment amount, the information processing device is characterized by comprising an acquisition unit that acquires invoice information indicated on an invoice via an application that provides a payment service in which, upon receiving notification of user identification information that identifies the user, payment destination identification information that identifies the payment destination, and a payment amount, electronic money equivalent to the payment amount is debited from an account corresponding to the user identification information and credited to the account corresponding to the payment destination identification information, the information processing device comprising: an acquisition unit that acquires invoice information indicated on an invoice via an application; an identification unit that identifies a payment period based on the invoice information; a setting unit that selects a payment date that satisfies certain conditions that are set in advance by the user via the application from the identified payment period and sets the selected payment date; and a payment processing unit that makes payment based on the invoice information on the set payment date via the application. Effect of the Invention

[0010] According to one aspect of the embodiment, an effect is achieved in that it is possible to improve convenience for users. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of information processing according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of the configuration of the payment server according to the embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of an account database according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of the invoice information database according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of a user information database according to the embodiment. [Figure 6] FIG. 6 is a diagram showing a specific example 1 of a display screen according to the embodiment. [Figure 7] FIG. 7 is a diagram showing a second specific example of a display screen according to the embodiment. [Figure 8] FIG. 8 is a diagram showing a third specific example of a display screen according to the embodiment. [Figure 9] FIG. 9 is a diagram showing a fourth specific example of a display screen according to the embodiment. [Figure 10] FIG. 10 is a diagram showing a fifth specific example of a display screen according to the embodiment. [Figure 11] FIG. 11 is a diagram showing a sixth specific example of a display screen according to the embodiment. [Figure 12] FIG. 12 is a flowchart illustrating an example of a procedure of information processing according to the embodiment. [Figure 13] FIG. 13 is a hardware configuration diagram illustrating an example of a computer that realizes the functions of the payment server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, the information processing device, the information processing method, and the information processing program according to the present application will be described in detail with reference to the drawings. Note that the information processing device, the information processing method, and the information processing program according to the present application are not limited to the embodiments. In addition, the same parts in the following embodiments are given the same reference numerals, and duplicated descriptions are omitted.

[0013] [1. Information Processing Systems] The information processing performed by the information processing device of the present embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the information processing according to the embodiment. In Fig. 1, the information processing according to the embodiment is performed by a payment server 10, which is an example of the information processing device according to the present embodiment.

[0014] [1-1. Configuration of information processing system] As shown in Fig. 1, the information processing system 1 according to the embodiment includes a payment server 10 and a user terminal 100. The payment server 10 and the user terminal 100 are connected to each other via a network N (see Fig. 2, for example) so as to be able to communicate with each other by wire or wirelessly. The network N is, for example, a wide area network (WAN) such as the Internet. Note that the information processing system 1 shown in Fig. 1 may include a plurality of payment servers 10 and a plurality of user terminals 100.

[0015] The payment server 10 shown in FIG. 1 is an information processing device that executes information processing according to the embodiment, and is realized by a server device, a cloud system, or the like. For example, the payment server 10 provides an electronic payment service related to electronic payment using a user terminal 100. For example, the payment server 10 manages accounts of providers (businesses) of transaction objects and users to whom transaction objects are provided, and realizes various payments by transferring electronic money between accounts in accordance with a payment request from a user. Note that electronic money may be, for example, points or currency used independently by various companies, or may be electronically tradable currency provided by a country, such as Japanese yen or dollars.

[0016] The user terminal 100 shown in Fig. 1 is an information processing device used by a user U1. The user terminal 100 is realized, for example, by a smartphone, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, a mobile phone, a PDA (Personal Digital Assistant), or the like. The user terminal 100 also 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 user terminal 100 is a smartphone.

[0017] When the user terminal 100 receives control information for implementing a predetermined information process from the payment server 10, the user terminal 100 implements the information process according to the control information. Here, the control information is described in, for example, a script language such as JavaScript (registered trademark), a style sheet language such as CSS (Cascading Style Sheets), a programming language such as Java (registered trademark), or a markup language such as HTML (HyperText Markup Language). The predetermined application itself delivered from the payment server 10 may be regarded as the control information.

[0018] 1-2. Payment Processing Using User Terminal 100 Here, prior to the information processing executed by the payment server 10, an example of payment (electronic payment) using the user terminal 100 will be described. In the following description, an example will be described in which a user U1 makes a payment using the user terminal 100 using a two-dimensional code (QR code (registered trademark)) placed in a store, which indicates store identification information that identifies the store, but the embodiment is not limited to this. The example of payment described below is also applicable to a case in which an arbitrary user U1 makes a payment at an arbitrary store using an arbitrary user terminal 100. In addition, the store identification information may be not only a QR code (registered trademark), but also a barcode, a predetermined mark, a number, etc.

[0019] For example, when user U1 makes a payment for using or purchasing a payment object such as various products or services at a store, user U1 launches a payment application pre-installed on user terminal 100. User U1 then photographs store identification information set up in the store via the application. In such a case, user terminal 100 displays a screen for inputting the price of the payment object and accepts input of the payment amount from user U1 or a store clerk. User terminal 100 then transmits to payment server 10 user information identifying user U1, store identification information (or information indicated by the store identification information, i.e., information indicating the store), and payment information indicating the payment amount.

[0020] In such a case, the payment server 10 transfers electronic money in the amount indicated by the payment amount from the account of user U1 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 that the payment has been completed to the user terminal 100. In such a case, the user terminal 100 notifies that the payment has been made with electronic money by outputting a screen or a predetermined sound indicating that the payment has been completed.

[0021] It should be noted that the payment using the user terminal 100 is not limited to the above-mentioned process. For example, the payment using the user terminal 100 may be made using a store terminal installed in a store. For example, the user terminal 100 displays user identification information for identifying the user U1 on a screen. In such a case, the store terminal installed in the store reads the user identification information displayed on the user terminal 100, and transmits payment information indicating the user identification information, the payment amount, and information identifying the store to the payment server 10. In such a case, the payment server 10 transfers electronic money in an amount indicated by the payment amount from the account of the user U1 indicated by the user identification information to the account of the store, and may notify the store terminal or the user terminal 100 of the completion of the payment by outputting a screen or a predetermined sound indicating that the payment has been completed.

[0022] Furthermore, the payment using the user terminal 100 may not only be a process of transferring electronic money from an account to which the user U1 has previously charged electronic money to the store's account, but may also be a payment using a credit card previously registered by the user U1. In such a case, for example, the payment server 10 may transfer the electronic money of the payment amount to the store's account and bill the management company of the credit card of the user U1 for the payment amount.

[0023] Furthermore, the settlement using the user terminal 100 may not only be a process of transferring electronic money from the account of the user U1 to the account of a store, but may also be a settlement of transferring electronic money from the account of the user U1 to the account of a provider (business) that provides a specified transaction object. In such a case, the user U1 reads a barcode included in a payment slip (for example, a transfer slip used in a convenience store collection agency service) sent to the user U1 by the business, using a photographing device (camera) provided in the user terminal 100. The user terminal 100 then displays the payee and the payment amount indicated by the read barcode on the screen, and when an operation is received from the user U1 to approve the remittance to the payee, it transmits settlement information indicating the user identification information, the payment amount, and information identifying the payee to the settlement server 10. In such a case, the settlement server 10 transfers electronic money in an amount indicated by the payment amount from the account of the user U1 to the account of the payee.

[0024] [1-3. Processing of Information Processing System 1] As described above, there are known technologies for providing a service that reads information such as the bill amount printed on a paper bill and enables payment with electronic money. There are also known technologies for providing a service that transmits an electronic bill to a user's terminal and enables payment of the bill amount with electronic money. However, with such technologies, the timing for payment of the bill is the timing when the user performs the payment procedure, which may lead to forgetting to pay, and is not necessarily convenient for the user.

[0025] Therefore, the payment server 10 executes information processing according to the embodiment. The information processing executed by the payment server 10 will be described below with reference to FIG. 1. In the following description, an example is shown in which the user terminal 100 is used by the user U1. In addition, in the following description, the user terminal 100 may be regarded as the same as the user U1. That is, in the following description, the user U1 may also be read as the user terminal 100.

[0026] First, user U1 reads invoice information from paper invoice B1 using user terminal 100 (step S1). For example, user U1 uses the camera function of user terminal 100 to photograph and capture the barcode printed on paper invoice B1. Here, invoice information refers to information including identification information of the business entity that makes the bill, identification information of the user to whom the bill is to be sent, the billed amount, the payment deadline, etc. In the following explanation, the invoice information printed on the invoice is explained as a barcode, but the invoice information may not only be a barcode, but may also be a two-dimensional code (QR code (registered trademark)), a specified mark, a number, etc.

[0027] At this time, the user terminal 100 may receive an electronic invoice B2 sent from a business terminal (not shown) of the business that is the billing source, instead of a paper invoice B1. Here, the electronic invoice B2 is an invoice that can be paid online using the above-mentioned electronic money, and includes invoice information.

[0028] Next, the payment server 10 acquires the invoice information from the user terminal 100 (step S2), and identifies the payment period from the invoice information (step S3). For example, the payment server 10 identifies the date and time of the payment deadline from the invoice information of the paper invoice B1, and identifies the period from the date and time of acquiring the invoice information from the user terminal 100 to the date and time of the payment deadline as the payment period. In addition, when the barcode of the paper invoice B1 does not include information on the payment deadline, the payment server 10 can set the payment period to a predetermined period from the issue date, or can use OCR (Optical Character Recognition) technology to identify the payment deadline written in characters.

[0029] Next, the payment server 10 selects a payment date and time that satisfies a predetermined condition, and sets the selected payment date and time as the payment date and time of the acquired invoice (step S4). For example, the payment server 10 identifies the date and time of the payment due date from the invoice information of the electronic invoice B2, and sets the day before the payment due date as the payment date and time. The payment server 10 can also set the payment date and time to any date and time, such as the day of the payment due date, 48 hours before the payment due date, or one week before the payment due date. At this time, if the user U1 has previously specified a desired payment period, such as after payday, the payment server 10 sets the payment date and time from the specified period.

[0030] The payment server 10 sets the basic payment method to a payment method for a payment made at a set date and time, such as the day before the payment due date, without the user U1 specifying the payment date and time ("automatic payment" as appropriate), but may display a setting button on the screen of the user terminal 100 that allows the automatic payment setting to be switched on and off. That is, the payment server 10 displays a setting button that indicates that the automatic payment setting is on as a screen to be displayed on the user terminal 100, but can also accept an operation of the setting button by the user U1 to turn the automatic payment setting off and cancel the automatic payment setting. The payment server 10 sets the basic automatic payment settlement date to the day before the payment due date of each invoice, but can also change the settlement date to any date and time within the payment period by accepting a designation by the user U1.

[0031] At this time, the payment server 10 can select a candidate payment date and time that satisfies a predetermined condition from the identified payment period, and display candidate information related to the selected candidate on the user terminal 100. For example, in addition to the above-mentioned automatic payment payment method, the payment server 10 can also display on the user terminal 100, as candidate information, payment methods such as a payment to be executed on a payment date and time designated by the user U1 from the presented payment period ("payment reservation" as appropriate), an immediate payment to be executed by the user U1 at a timing of his / her choice ("immediate payment" as appropriate), and a payment to be executed on a predetermined date and time based on the payment history (payment history) of the user U1 for each invoice ("history payment" as appropriate).

[0032] Taking an example of a payment reservation, the payment server 10 displays, as candidate information, a calendar on which the payment date and time can be selected on the screen of the user terminal 100. At this time, the payment server 10 can also display, on the screen of the user terminal 100, a calendar in which dates for which the payment date and time cannot be selected, such as dates after the payment deadline, are grayed out.

[0033] To explain an example of immediate payment, the payment server 10 displays a button with a message such as "Pay now" as candidate information on the screen of the user terminal 100. At this time, if the date or time period is not available for immediate payment, the payment server 10 can also display a grayed-out button on the screen of the user terminal 100 to indicate that it is not selectable.

[0034] To explain an example of a payment history, the payment server 10 displays buttons that allow the selection and setting of payment history as candidate information on the screen of the user terminal 100. For example, for invoices with the same invoice ID included in the invoice information, the payment server 10 identifies past monthly payment dates (e.g., the 18th for water bill and the 20th for gas bill) from the payment history of the user U1, and displays the identified payment dates on the user terminal 100 as the scheduled payment dates.

[0035] At this time, user U1 can also specify the payment method and payment date and time on the displayed content using the user terminal 100. For example, when user U1 wants to cancel automatic payment, he or she taps a setting button that allows automatic payment to be switched on and off, displayed on the screen of user terminal 100, and selects off. Furthermore, even when using automatic payment, user U1 can specify a desired payment date and time (e.g., one week before the payment due date) if he or she wants to change the settings for the payment date and time.

[0036] Furthermore, when user U1 selects scheduled payment, after canceling the automatic payment setting, a screen for specifying the payment date and time is displayed on the screen of user terminal 100, and the payment date and time is specified by tapping the desired date from among the dates displayed in a selectable state on the displayed calendar. When user U1 selects immediate payment, he / she taps a button displayed on the screen of user terminal 100 with a message such as "Pay now" to select it. When user U1 selects historical payment, after canceling the automatic payment setting, he / she taps a button displayed on the screen of user terminal 100 that allows selection and setting of historical payment to select "on" and approves the proposed scheduled payment date.

[0037] Next, the payment server 10 accepts the specification of the payment date and time from the user terminal 100. The payment server 10 accepts the specification of the date and time of payment as the payment date and time specified by the user U1. The payment server 10 can also store the invoice information accepted from the user terminal 100.

[0038] At this time, the payment server 10 can also accept re-designation of the payment date and time or change of the payment date and time from the user terminal 100. For example, when the automatic payment setting is cancelled and a payment reservation is set or a historical payment is set, the payment server 10 accepts a change of the designated payment date and time or the set historical payment date and time. The payment server 10 can also accept a change of the payment method from the user terminal 100. For example, the payment server 10 accepts a change of the payment method from the user terminal 100 to indicate a desire for immediate payment for the relevant payment.

[0039] Next, the payment server 10 executes the payment process based on the invoice information at the payment date and time set by the payment server 10 or the payment date and time specified by the user U1 (step S5). For example, the payment server 10 transfers electronic money for the invoice amount described in the invoice information from the account of the user U1 to the account of the business that is the billing source. The payment server 10 can also execute the payment process based on the stored invoice information at the payment date and time specified by the user U1.

[0040] At this time, if the balance of the user U1's account is insufficient to cover the billing amount, the payment server 10 can transfer (automatically charge) electronic money from another account of the user U1 that has been set up in advance, and execute the payment process. Furthermore, if the automatic payment has not been cancelled, the payment server 10 may send a push notification such as "Payment will be made today" on the day the payment process is executed. Furthermore, if the automatic payment has been cancelled and the user U1 has specified a payment reservation or set a payment history, the payment server 10 may send a similar push notification.

[0041] Finally, the payment server 10 notifies the user U1 of information regarding the payment of the invoice (step S6). For example, the payment server 10 notifies the user terminal 100 that the payment of the invoice of the user U1 has been completed.

[0042] At this time, if automatic charging is performed during bill payment processing, the payment server 10 may execute a notification to that effect. Also, if the payment processing cannot be completed due to insufficient balance of electronic money during bill payment processing, the payment server 10 may notify the user U1 of that effect and display a screen on the user terminal 100 for the user U1 to select a payment method. Also, the payment server 10 may notify the user U1 of the possibility of forgetting to pay based on the monthly payment history of the user U1 (for example, water charges that are paid by the end of each month are not paid).

[0043] As described above, the payment server 10 according to the embodiment can specify the period during which an invoice can be paid, set the payment date and time from the specified period during which an invoice can be paid, and schedule the payment of the invoice, thereby preventing the invoice from being forgotten to be paid. In other words, the payment server 10 according to the embodiment can improve the convenience of the user. Furthermore, the payment server 10 according to the embodiment can further improve the convenience of the user by enabling payment based on stored information even if a paper invoice is lost, and enabling various notifications to prevent forgetting to pay or insufficient balance of electronic money.

[0044] [2. Payment Server Configuration] Next, the configuration of the payment server 10 will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of the configuration of the payment server according to the embodiment. As shown in Fig. 2, the payment server 10 includes a communication unit 20, a storage unit 30, and a control unit 40.

[0045] [2-1. Communications Department 20] The communication unit 20 is realized by, for example, a network interface card (NIC) etc. The communication unit 20 is connected to the network N by wire or wirelessly, and transmits and receives information to and from the user terminal 100, the operator terminal 200, etc.

[0046] [2-2. Storage section 30] The storage unit 30 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk or an optical disk. As shown in FIG. 2, the storage unit 30 has an account database 31, a billing information database 32, and a user information database 33.

[0047] (Account Database 31) Account database 31 stores various information related to accounts held by users, businesses, etc. in electronic payment services. An example of information stored in account database 31 will now be described with reference to Fig. 3. Fig. 3 is a diagram showing an example of an account database according to an embodiment. In the example of Fig. 3, account database 31 has items such as "account ID", "owner information", and "account balance".

[0048] "Account ID" indicates identification information for identifying an account. "Owner Information" indicates information about the owner of the account, and for example, identification information for identifying the owner is stored. "Account Balance" indicates the balance of the account.

[0049] That is, FIG. 3 shows an example in which the information of the owner of the account identified by the account ID "AID#1" is "User #1" and the account balance is "7,800 yen."

[0050] (Invoice Information Database 32) The invoice information database 32 stores various information indicated on invoices created by businesses that issue bills. An example of information stored in the invoice information database 32 will now be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of an invoice information database according to an embodiment. In the example of Fig. 4, the invoice information database 32 has items such as "invoice ID", "business ID", "billed amount", and "payment deadline".

[0051] "Invoice ID" indicates identification information used to identify an invoice created by a business. "Business ID" indicates identification information used to identify the business that created the invoice. "Invoice amount" indicates the amount the business will invoice the user. "Payment deadline" indicates the deadline by which the user can pay the invoice amount to the business.

[0052] That is, Figure 4 shows an example of an invoice identified by invoice ID "BID#1" created by a business identified by business ID "MID#1", with the invoice amount being "Invoice amount #1" and the payment deadline being "Payment deadline #1", and an example of an invoice identified by invoice ID "BID#2" created by a business identified by business ID "MID#2", with the invoice amount being "Invoice amount #2" and the payment deadline being "Payment deadline #2".

[0053] (User Information Database 33) The user information database 33 stores various information related to users of the electronic payment service provided by the payment server 10. An example of information stored in the user information database 33 will now be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of a user information database according to an embodiment. In the example of Fig. 5, the user information database 33 has items such as "user ID", "payment history", "invoice ID", and "payment date and time".

[0054] "User ID" indicates identification information used to identify a user. "Payment history" indicates the history of payments made using electronic payment services, and stores information such as the payment destination and payment amount. "Invoice ID" indicates identification information used to identify an invoice created by a business. "Payment date and time" indicates the date and time during the payment period when the user wishes to pay the invoice (payment reservation date and time), etc.

[0055] That is, Figure 5 shows an example in which the payment history of a user identified by user ID "UID#1" is "Payment History #1", the payment reservation date and time of an invoice identified by "BID#1" is "Payment Date and Time #1", and the payment reservation date and time of an invoice identified by "BID#2" is "Payment Date and Time #2".

[0056] 2-3. Control Unit 40 The control unit 40 is a controller, and is realized, for example, by a CPU (Central Processing Unit) or an MPU (Micro Processing Unit) executing various programs stored in a storage device inside the payment server 10 using a RAM as a working area. The control unit 40 is also a controller, and is realized, for example, by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). As shown in FIG. 2, the control unit 40 according to the embodiment has an acquisition unit 41, a specification unit 42, a setting unit 43, a display unit 44, a reception unit 45, a payment processing unit 46, and a notification unit 47, and realizes or executes the functions and actions of information processing described below.

[0057] (Acquisition part 41) The acquisition unit 41 acquires invoice information indicated by the invoice. For example, the acquisition unit 41 acquires invoice information indicated by the invoice photographed by the user terminal of the user. That is, the acquisition unit 41 receives invoice information read from a barcode photographed by the user U1 using the camera function of the user terminal 100. The acquisition unit 41 also receives invoice information indicated by the invoice transmitted to the user terminal of the user. That is, the acquisition unit 41 receives invoice information included in an electronic invoice B2 transmitted by a business operator terminal and received by the user terminal 100. The acquisition unit 41 may also receive invoice information included in an electronic invoice B2 selected by the user U1 from among multiple electronic invoices B2 received by the user terminal 100. Here, the acquisition unit 41 receives invoice ID, business operator ID, billing amount, payment deadline, etc. as invoice information. The acquisition unit 41 stores the acquired invoice information in the invoice information database 32.

[0058] (Specific part 42) The identifying unit 42 identifies the payment period based on the acquired invoice information. For example, the identifying unit 42 identifies the date and time of the payment due date from the invoice information of the paper invoice B1, and identifies the period from the date and time when the invoice information is acquired from the user terminal 100 to the date and time of the payment due date as the payment period. At this time, if there is a time period during which payment cannot be executed due to server maintenance or the like, the identifying unit 42 can also identify the time period.

[0059] (Settings section 43) The setting unit 43 selects a payment date that satisfies a predetermined condition from the identified payment period, and sets the selected payment date. For example, the setting unit 43 sets a date corresponding to a predetermined time before the payment due date indicated by the invoice information as the payment date. That is, the setting unit 43 can set a date and time corresponding to one day (the day before) before the payment due date, 48 hours before the payment due date, one week before the payment due date, etc. as the payment date and time.

[0060] (Display section 44) The display unit 44 selects a candidate payment date that satisfies a predetermined condition from the identified payment period, and displays candidate information related to the selected candidate. For example, the display unit 44 selects a candidate payment date such as a period after payday within the payment period, and displays content for selecting a payment method that can be used to execute payment on the candidate payment date on the user terminal 100. At this time, the display unit 44 selects the candidate payment date based on the designation of user U1 and the payment history of user U1, and displays content for selecting the above-mentioned payment method on the user terminal 100.

[0061] To explain an example of the content to be displayed, the display unit 44 displays content in which a payment date can be selected as candidate information related to a payment reservation. For example, the display unit 44 displays a calendar in which a payment date can be selected as the content. Furthermore, the display unit 44 displays content in which a designation for making an immediate payment can be selected as candidate information related to an immediate payment. For example, the display unit 44 displays a button with a message such as "Pay now" on the screen of the user terminal 100. Furthermore, the display unit 44 displays content in which a designation for making a payment on a specific date based on the user's payment history can be selected as candidate information related to a payment history. For example, the display unit 44 displays a button in which a payment history can be selected or set on the screen of the user terminal 100.

[0062] (Reception Department 45) The reception unit 45 also receives a designation of a payment date from the displayed candidate information. For example, the reception unit 45 receives a designation of a payment date by an operation on a content that selects a payment method such as automatic payment, scheduled payment, immediate payment, or historical payment. At this time, the reception unit 45 may further receive a designation of a time to make the payment.

[0063] To explain an example of the designation accepted for each content, the accepting unit 45 accepts a designation to make payment on a predetermined date based on the payment due date by an operation on the automatic payment content. For example, the accepting unit 45 accepts the setting of automatic payment when the user U1 taps a setting button that can switch automatic payment on and off displayed on the screen of the user terminal 100, and accepts the designated payment date when the user U1 taps a button to approve the scheduled payment date presented on the screen of the user terminal 100.

[0064] The reception unit 45 also accepts the designation of the selected payment date by an operation on the payment reservation content. For example, the reception unit 45 accepts the payment date designated by the user U1 tapping on a calendar displayed on the screen of the user terminal 100. The reception unit 45 also accepts the designation of making an immediate payment by an operation on the immediate payment content. For example, the reception unit 45 accepts the payment date and time (immediately) designated by the user U1 tapping on a button with a message such as "Pay now" displayed on the screen of the user terminal 100. The reception unit 45 also accepts the designation of making a payment on a predetermined date based on the payment history of the user U1 by an operation on the history payment content. For example, the reception unit 45 accepts the setting of an automatic payment by the user U1 tapping on a button that allows the user U1 to select or set a history payment displayed on the screen of the user terminal 100, and accepts the designated payment date by the user U1 tapping on a button to approve the scheduled payment date presented on the screen of the user terminal 100.

[0065] The reception unit 45 also accepts changes to the payment date and time. For example, the reception unit 45 accepts changes to the desired payment date, etc., for invoice B1 for which payment has not been completed, within the payment period. Specifically, if automatic payment has not been canceled, the reception unit 45 accepts changes to the payment date, etc., for automatic payment, and changes to the payment date, etc., based on a change in the payment method to a scheduled payment or history payment. At this time, if the reception unit 45 accepts a change in the payment method to immediate payment, it accepts a change to a designation of immediate payment on the specified payment date, etc.

[0066] The reception unit 45 stores the received designation of the payment date, etc. and changes to the payment date, etc. in the user information database 33.

[0067] (Payment processing unit 46) The payment processing unit 46 performs payment based on the invoice information on the set payment date. At this time, the payment processing unit 46 may perform the payment at the time when the designation is accepted. For example, the payment processing unit 46 performs payment based on the invoice information indicated by the invoice photographed by the user terminal 100 of the user U1. The payment processing unit 46 also performs payment based on the invoice information indicated by the invoice transmitted to the user terminal 100 of the user U1. The payment processing unit 46 also performs payment based on the invoice information stored in the storage unit. That is, the payment processing unit 46 performs payment using the invoice information indicated by the invoice photographed by the user terminal 100 of the user U1, so that the payment can be performed even if the user U1 loses the paper invoice B1. Furthermore, when the acceptance unit 45 accepts a change in the payment date or time, the payment processing unit 46 performs payment based on the invoice information on the payment date or time when the change is accepted. Furthermore, when the acceptance unit 45 accepts a designation to perform the payment immediately, the payment processing unit 46 performs the designated payment immediately.

[0068] At this time, the payment processing unit 46 transfers electronic money in an amount indicated by the billing amount from the user's account indicated by the user ID to the account of the business entity indicated by the business entity ID at the designated payment date and time. The payment processing unit 46 also performs payment based on the bill information at the payment date and time when the change is accepted. Furthermore, when the electronic money owned by the user is insufficient for the billing amount of the payment based on the bill information, the payment processing unit 46 transfers the shortfall amount as electronic money from a specified account set by the user and performs the payment. Furthermore, the payment using the user terminal 100 may not only be a process of transferring electronic money from an account to which the user U1 has previously charged electronic money to the account of the store A, but may also be, for example, a payment using a credit card registered by the user U1 in advance. In such a case, for example, the user terminal 100 may transfer electronic money in an amount of the payment amount to the account of the store A and bill the operating company of the credit card of the user U1 for the payment amount.

[0069] (Notification section 47) The notification unit 47 notifies user U1 of information regarding the payment. Furthermore, based on user U1's past payment history, the notification unit 47 notifies user U1 of payments that may not have been completed. Furthermore, if user U1 does not have enough electronic money to cover the amount claimed for the payment, the notification unit 47 notifies user U1 of the lack of electronic money. Furthermore, if user U1 does not have enough electronic money to cover the amount claimed for the payment, the notification unit 47 notifies user U1 to that effect, urging them to deposit electronic money.

[0070] [3. Examples of display screens] Specific examples of display screens displayed by the payment server 10 according to the embodiment will be described with reference to Fig. 6 to Fig. 11. Fig. 6 to Fig. 11 are diagrams showing specific examples of display screens according to the embodiment. Below, the display screens relating to the processing of paper invoice B1 and the display screens relating to the processing of electronic invoice B2 will be described in that order.

[0071] [3-1. Paper invoice B1] 6 to 7, a specific example of a display screen related to the processing of the paper invoice B1 displayed by the payment server 10 according to the embodiment will be described. The display screen related to the reading process and the display screen of the management list will be described below in that order.

[0072] (Display screen regarding reading process) The display screen for the paper invoice B1 reading process will be explained using Figure 6. First, the invoice payment top screen (see Figure 6(1)) is displayed, and by tapping the "Read invoice" display, the screen transitions to a screen (see Figure 6(2)) for reading the barcode on the paper invoice B1 with a camera.

[0073] Next, the barcode on the paper invoice B1 is read by the camera, and if the payment date and time can be specified, the screen transitions to a details screen (see Figure 6(3)) where immediate payment or scheduled payment can be selected. On the other hand, if scheduled payment is not possible, the screen transitions to a details screen (see Figure 6(4)) where only immediate payment can be selected.

[0074] Here, by tapping on the "Register automatic payment date" display on the screen of Fig. 6(3), a calendar screen (see Fig. 6(5)) showing the payment period with the non-payment period dates greyed out will be displayed. At this time, tap on the date column (see Fig. 6(6)) on the calendar screen for which you wish to make payment, then tap on the "Register" display (see Fig. 6(7)). If the registration is successful, you will be transferred to a screen (see Fig. 6(13)) that indicates the success of the registration, such as "Automatic payment date registered."

[0075] Furthermore, even if a payment reservation is registered as described above, if you wish to make an immediate payment, you can do so by tapping the "Pay Now" display (see Figure 6 (14)). You can also change the date and time of the registered payment reservation by tapping the "Change" display on the screen in Figure 6 (14).

[0076] On the other hand, if the registration of the payment reservation fails on the screen of Figure 6 (7), the screen will transition to a screen (see Figure 6 (15)) that displays the registration failure, such as "Registration of automatic payment date has failed," and will display a message explaining the reason for the failure and encouraging the user to re-specify the payment date and time, etc.

[0077] Furthermore, on the calendar screen in Figure 6 (5), if there are already registered payment reservations for other invoices, the number of registrations (see Figure 6 (8)) will be displayed in the date column on the calendar corresponding to the registered date. In the example of Figure 6 (8), one payment reservation has been registered on January 26th, and three on January 28th. At this time, you can check the registered details or reset the payment date and time by tapping on the registered date column (see Figures 6 (9) to (12)).

[0078] (Management list display screen) The display screen of the management list of paper invoice B1 will be explained using Figure 7. First, the bill payment top screen (see Figure 7(1)) is displayed, and by tapping the "Manage automatic payments" display, the display screen of the management list of paper invoice B1 (see Figure 7(2)) is displayed. At this time, by tapping the "Add invoice" display on the screen of Figure 7(2), it is possible to additionally register a payment reservation for paper invoice B1 or electronic invoice B2.

[0079] Next, if there is an electronic invoice B2 available for registration on the screen of Fig. 7(2), the screen transitions to a screen for selecting an electronic invoice B2 available for registration (see Fig. 7(3)). At this time, by selecting electronic invoice B2 on the screen of Fig. 7(3), the screen transitions to a screen (see Fig. 7(4)) that displays the completion of the additional registration to the payment schedule.

[0080] On the other hand, if there is no electronic invoice B2 available for registration on the screen in Fig. 7(2), but there is a paper invoice B1 available for registration, tapping the "Read invoice" display will take you to a screen where the barcode on the paper invoice B1 can be read with a camera (see Fig. 7(5)), and then to a details screen (see Fig. 7(6)) where you can select immediate payment or scheduled payment. At this time, a screen for selecting automatic payment settings can also be displayed on the screen in Fig. 7(6).

[0081] [3-2. Electronic bill B2] 8 to 11, specific examples of display screens related to the processing of electronic invoice B2 displayed by the payment server 10 according to the embodiment will be described. The following describes the payment history list display screen, the electronic invoice detail display screen, and the management list display screen, in that order.

[0082] (Payment history list display screen) The display screen for the payment history list of electronic invoice B2 will be described using Figure 8. First, the invoice payment top screen (see Figure 8(1)) is displayed, and by tapping the display of the invoice for which you want to display the payment history list, you will be transferred to the display screen for the payment history list of electronic invoice B2 (see Figure 8(2)).

[0083] Next, by turning on the "Automatic Payment" setting button on the screen of Figure 8 (2), the screen will transition to a screen (see Figure 8 (3)) that displays the completion of the automatic payment setting, which executes settlement before the payment due date every month. For example, by setting the above automatic payment, settlement can be made automatically on the day before the payment due date indicated by electronic invoice B2 without specifying the payment date and time. Here, the settlement date for the above automatic payment is not limited to the day before the payment due date, but can be set any time before the payment due date, and this setting can also be changed. It is also possible to cancel the above automatic payment setting and select a payment reservation with a specified payment date and time, or to select immediate payment.

[0084] Once the above automatic payment settings are complete, the "Pay automatically every month" setting etc. (see Figure 8 (4)-(5)) will be displayed for the invoice that has been set on the bill payment home screen. On the other hand, by tapping "Check automatic payment schedule" on the screen of Figure 8 (3), you will be transferred to the automatic payment management screen.

[0085] (Electronic invoice details display screen 1) The display screen 1 of the electronic invoice detail screen of electronic invoice B2 will be described with reference to Figure 9. First, the invoice payment top screen (see Figure 9(1)) is displayed, and by tapping on the display of the invoice for which you wish to display the electronic invoice detail screen, you will be transferred to the electronic invoice detail screen of electronic invoice B2 (see Figure 9(2)).

[0086] Next, by turning on the "Automatic Payment" setting button on the screen of FIG. 9(2), the screen transitions to a screen (see FIG. 9(3)) that displays the completion of the automatic payment setting, which executes settlement before the payment due date every month. For example, by setting the above automatic payment, it becomes possible to automatically settle the day before the payment due date indicated by electronic invoice B2 without specifying the payment date and time. Here, the settlement date of the above automatic payment is not limited to the day before the payment due date, but can be set any time before the payment due date, and the setting can also be changed. Also, as shown in the example of FIG. 9(4), even if the "Automatic Payment" setting button is turned on, the automatic payment setting can be canceled, an immediate payment can be executed by tapping the "Pay Now" display, or the payment date and time can be changed to a scheduled payment.

[0087] (Electronic invoice details screen 2) The display screen 2 of the electronic invoice detail screen of electronic invoice B2 will be described with reference to Figure 10. First, the invoice payment top screen (see Figure 10(1)) is displayed, and by tapping on the display of the invoice for which you wish to display the electronic invoice detail screen, you will be transferred to the electronic invoice detail screen of electronic invoice B2 (see Figure 10(2)).

[0088] Next, on the screen of FIG. 10(2), if the "Pay" display is tapped and the automatic payment setting is on, an immediate payment is made and the screen transitions to a payment completion screen (see FIG. 10(4)). On the other hand, if the "Pay" display is tapped on the screen of FIG. 10(2) and the automatic payment setting is off, the screen transitions to a screen where automatic payment can be set up (see FIG. 10(3)). On the screen of FIG. 10(3), by tapping the "Turn on automatic payment for this invoice" display, the screen transitions to a screen (see FIG. 10(5)) that displays the completion of automatic payment settings, which executes automatic payment before the payment due date every month. For example, by setting the above automatic payment, payment can be made automatically on the day before the payment due date indicated on electronic invoice B2 without the need to specify a payment date and time.

[0089] (Management list display screen) The display screen of the management list of electronic invoice B2 will be explained using Figure 11. First, the bill payment top screen (see Figure 11(1)) is displayed, and by tapping the "Manage automatic payments" display, the display screen of the management list of electronic invoice B2 (see Figure 11(2)) is displayed. At this time, by tapping the "Add invoice" display on the screen of Figure 11(2), it is possible to additionally register a payment reservation for paper invoice B1 or electronic invoice B2.

[0090] Next, if there is an electronic invoice B2 available for registration on the screen of Fig. 11(2), the screen transitions to a screen for selecting an electronic invoice B2 available for registration (see Fig. 11(3)). By selecting electronic invoice B2 on the screen of Fig. 11(3), the screen transitions to a screen (see Fig. 11(4)) that displays the completion of the additional registration to the payment schedule.

[0091] On the other hand, if there is no electronic invoice B2 available for registration on the screen in Fig. 11(2), but there is a paper invoice B1 available for registration, tapping the "Read invoice" display will take you to a screen where the barcode on the paper invoice B1 can be read with a camera (see Fig. 11(5)), and then to a details screen where you can select immediate payment or scheduled payment (see Fig. 11(6)). At this time, a screen for selecting automatic payment settings can also be displayed on the screen in Fig. 11(6).

[0092] [4. Provision process flow] An information processing procedure of the payment server 10 according to the embodiment will be described with reference to Fig. 12. Fig. 12 is a flowchart showing an example of the information processing procedure according to the embodiment. Note that the following steps S101 to S106 may be executed in a different order. Also, among the following steps S101 to S106, some processes may be omitted.

[0093] First, the acquisition unit 41 of the payment server 10 executes an invoice information acquisition process (step S101). For example, the acquisition unit 41 acquires invoice information read from a paper invoice B1 by the user U1 using the user terminal 100.

[0094] Secondly, the specification unit 42 of the payment server 10 executes a payment period specification process (step S102). For example, the specification unit 42 specifies the date and time of the payment deadline from the invoice information, and specifies the period from the date and time of acquiring the invoice information from the user terminal 100 to the date and time of the payment deadline as the payment period.

[0095] Thirdly, the setting unit 43 of the payment server 10 executes a payment date and time setting process (step S103). For example, the setting unit 43 sets an automatic payment to be made on the day before the payment deadline. At this time, the display unit 44 of the payment server 10 may display content on the screen of the user terminal 100 that allows selection of payment methods such as scheduled payment, immediate payment, and historical payment as candidate information of payment methods other than those mentioned above.

[0096] Fourth, the reception unit 45 executes a payment date and time reception process (step S104). For example, the reception unit 45 receives the payment date and time specified by the user U1 using the user terminal 100.

[0097] Fifth, the payment processing unit 46 executes the payment process (step S105). For example, the payment processing unit 46 executes the payment process based on the invoice information at the payment date and time designated by the user U1.

[0098] Sixth, the notification unit 47 executes notification processing (step S106) and ends the processing. For example, the notification unit 47 notifies information regarding the payment of the bill of the user U1 (e.g., insufficient payment amount, automatic charge completion, etc.).

[0099] 5. Effects As described above, the payment server 10 according to the embodiment has an acquisition unit 41, an identification unit 42, a setting unit 43, a display unit 44, a reception unit 45, a payment processing unit 46, and a notification unit 47.

[0100] The acquisition unit 41 acquires invoice information indicated by the invoice, the specification unit 42 specifies the payment period based on the invoice information, the setting unit 43 selects a payment date and time that satisfies a predetermined condition from the specified payment period and sets the selected payment date and time, and the payment processing unit 46 makes a payment based on the invoice information at the set payment date and time. In this way, the payment server 10 according to the embodiment can improve the convenience of the user.

[0101] In addition, the acquisition unit 41 acquires invoice information indicated by the invoice photographed by the user terminal of the user. As a result, the payment server 10 according to the embodiment can improve the convenience of the user by using the invoice information indicated by the paper invoice B1.

[0102] In addition, the acquisition unit 41 acquires invoice information indicated by the invoice transmitted to the user terminal of the user. As a result, the payment server 10 according to the embodiment can improve the convenience of the user by using the invoice information indicated by the electronic invoice B2.

[0103] In addition, the setting unit 43 sets the date and time of payment to a date and time corresponding to a predetermined time before the payment deadline indicated by the invoice information. As a result, the payment server 10 according to the embodiment can improve the convenience of the user by automatically executing the payment at the predetermined date and time.

[0104] Furthermore, the display unit 44 selects a candidate payment date and time that satisfies a predetermined condition from the identified payment period and displays candidate information on the selected candidate, and the reception unit 45 receives a designation of the payment date and time from the displayed candidate information. In this way, the payment server 10 according to the embodiment can improve the convenience of the user by executing a payment using content for which a payment method can be selected.

[0105] The display unit 44 also displays content for which the payment date and time can be selected as candidate information, the reception unit 45 receives the designation of the selected payment date and time by an operation on the content, and the payment processing unit 46 performs the payment at the designated payment date and time. As a result, the payment server 10 according to the embodiment can improve the convenience of the user by executing the payment using the content for which the payment date and time can be selected.

[0106] The display unit 44 also displays, as candidate information, content for which instant payment can be selected, the reception unit 45 receives a designation for instant payment by an operation on the content, and the payment processing unit 46 immediately performs the payment for which a designation has been received. As a result, the payment server 10 according to the embodiment can improve the convenience of the user by executing a payment using content for which instant payment can be made.

[0107] Furthermore, the display unit 44 displays, as candidate information, selectable content for which payment can be made at a specific date and time based on the user's payment history, the reception unit 45 receives a designation for making the payment at a specific date and time based on the user's payment history through an operation on the content, and the payment processing unit 46 makes the payment at the specific date and time based on the user's payment history. As a result, the payment server 10 according to the embodiment can improve user convenience by making a payment using content for which payment can be made based on the user's behavioral history.

[0108] In addition, the reception unit 45 further receives a change to the payment date and time, and the payment processing unit 46 performs the payment at the payment date and time for which the change has been received. In this way, the payment server 10 according to the embodiment can improve the convenience of the user by enabling the payment reservation to be changed.

[0109] The payment server 10 according to the embodiment further includes a storage unit 30 that stores invoice information, and the payment processing unit 46 performs payment based on the invoice information stored in the storage unit 30. As a result, the payment server 10 according to the embodiment can improve the convenience of the user by enabling payment without storing a paper invoice.

[0110] The notification unit 47 further notifies the user U1 about a payment that may not be completed based on the past payment history of the user U1. This allows the payment server 10 according to the embodiment to further prevent the user U1 from forgetting to pay the bill, thereby improving the convenience of the user.

[0111] When the electronic money owned by the user U1 is insufficient to cover the billing amount, the payment processing unit 46 transfers the shortfall in electronic money from a specified account set by the user U1 and makes the payment. In this way, the payment server 10 according to the embodiment can prevent payment defaults caused by forgetting to charge electronic money, thereby improving the convenience of the user.

[0112] When the electronic money owned by the user U1 is insufficient for the billing amount of the payment, the notification unit 47 further notifies the user U1 that the electronic money is insufficient. This allows the payment server 10 according to the embodiment to recognize that the user has forgotten to charge the electronic money, thereby improving the convenience of the user.

[0113] If the electronic money owned by the user U1 is insufficient for the billing amount of the payment, the notification unit 47 further notifies the user U1 to prompt the user U1 to deposit electronic money. This allows the payment server 10 according to the embodiment to prevent the user from forgetting to charge electronic money, thereby improving the convenience of the user.

[0114] [6. Hardware Configuration] The payment server 10 according to each of the above-described embodiments is realized, for example, by a computer 1000 having a configuration as shown in FIG. 13. The payment server 10 will be described below as an example. FIG. 13 is a hardware configuration diagram showing an example of a computer that realizes the functions of the payment server. The computer 1000 has a CPU 1100, a RAM 1200, a ROM 1300, a HDD 1400, a communication interface (I / F) 1500, an input / output interface (I / F) 1600, and a media interface (I / F) 1700.

[0115] The CPU 1100 operates and controls each unit based on a program stored in the ROM 1300 or the HDD 1400. The ROM 1300 stores a boot program executed by the CPU 1100 when the computer 1000 is started up, programs that depend on the hardware of the computer 1000, and the like.

[0116] The HDD 1400 stores programs executed by the CPU 1100, data used by such programs, etc. The communication interface 1500 receives data from other devices via a communication network 500 (corresponding to the network N in the embodiment) and sends the data to the CPU 1100, and also transmits data generated by the CPU 1100 to other devices via the communication network 500.

[0117] The CPU 1100 controls output devices such as a display and a printer, and input devices such as a keyboard and a mouse, via the input / output interface 1600. The CPU 1100 acquires data from the input devices via the input / output interface 1600. The CPU 1100 also outputs data generated via the input / output interface 1600 to the output devices.

[0118] The media interface 1700 reads a program or data stored in the recording medium 1800 and provides it to the CPU 1100 via the RAM 1200. The CPU 1100 loads the program from the recording medium 1800 onto the RAM 1200 via the 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 Disc), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory.

[0119] For example, when the computer 1000 functions as the payment server 10, the CPU 1100 of the computer 1000 executes a program loaded on the RAM 1200 to realize the function of the control unit 40. In addition, the HDD 1400 stores each data in the storage device of the payment server 10. The CPU 1100 of the computer 1000 reads and executes these programs from the recording medium 1800, but as another example, the CPU 1100 may obtain these programs from another device via a predetermined communication network.

[0120] [7. Other] Although the embodiments of the present application have been described above, the present invention is not limited to the contents of these embodiments. The above-described components include those that can be easily imagined by a person skilled in the art, those that are substantially the same, and those that are within the so-called equivalent range. Furthermore, the above-described components can be appropriately combined. Furthermore, various omissions, substitutions, or modifications of the components can be made without departing from the gist of the above-described embodiments.

[0121] Furthermore, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by a known method. In addition, the information including the processing procedures, specific names, various data and parameters shown in the above documents and drawings can be changed arbitrarily unless otherwise specified. For example, the various information shown in each drawing is not limited to the illustrated information.

[0122] In addition, each component of each device shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit according to various loads, usage conditions, etc.

[0123] For example, the above-mentioned payment server 10 may be realized by multiple server computers, and depending on the function, the configuration can be flexibly changed, such as by calling an external platform using an API (Application Programming Interface) or network computing.

[0124] Furthermore, the above-described embodiments and modifications can be appropriately combined as long as the processing contents are not contradictory.

[0125] Moreover, the above-mentioned "section, module, unit" can be read as "means" or "circuit", etc. For example, a control section can be read as control means or a control circuit. [Explanation of symbols]

[0126] 1. Information Processing Systems 10 Payment Server 20 Communications Department 30 Storage section 31 Account Database 32 Invoice information database 33 User information database 40 Control section 41 Acquisition Department 42 Specific part 43 Setting section 44 Display section 45 Reception 46 Payment Processing Unit 47 Notification Department 100 User terminals

Claims

1. A storage unit that stores information on an account held by a user and a payment destination business operator, and user information of the user, which is used in a payment service using the user's user terminal; a payment service using the user terminal, which, upon receiving notification of user identification information identifying the user, payment destination identification information identifying the payment destination, and a payment amount, withdraws electronic money equivalent to the payment amount from an account corresponding to the user identification information, and deposits the payment amount into the account corresponding to the payment destination identification information, and also provides an acquisition unit that acquires invoice information indicated on an invoice via an application that photographs a predetermined code or a character string used for optical character recognition, or receives data from a predetermined terminal; A determination unit that determines a payment period based on the bill information; a setting unit that selects a payment date that satisfies a predetermined condition that is set in advance by a user via the application from the specified payment period, sets the payment date designated by the user from among the selected payment dates, and stores the set date in the storage unit as the user information; a payment processing unit that performs payment based on the invoice information via the application on the payment date stored in the storage unit; An information processing device comprising:

2. The acquisition unit acquires the invoice information indicated by the invoice photographed by the user terminal of the user.

2. The information processing apparatus according to claim 1,

3. The acquisition unit acquires the invoice information indicated by the invoice transmitted to the user terminal of the user.

2. The information processing apparatus according to claim 1,

4. The setting unit is setting, as the payment date, a date corresponding to a predetermined time before the payment deadline indicated by the invoice information; 4. The information processing apparatus according to claim 1, wherein the information processing apparatus is a computer.

5. a display unit that selects a candidate payment date that satisfies a predetermined condition from the specified payment period and displays candidate information regarding the selected candidate; a reception unit that receives a designation of the payment date from the displayed candidate information; The information processing apparatus according to claim 1 , further comprising:

6. The display unit is displaying content in which the payment date can be selected as the candidate information; The reception unit is accepting a designation of the payment date selected by an operation on the content; The payment processing unit, The settlement is made on the payment date designated and accepted.

6. The information processing apparatus according to claim 5,

7. The display unit is displaying content for which the selection of immediate payment can be made as the candidate information; The reception unit is Accepting a designation to immediately perform the payment by an operation on the content; The payment processing unit, Immediately make the payment for which the designation has been accepted; 7. The information processing apparatus according to claim 5, wherein the information processing apparatus is a computer.

8. The display unit is displaying, as the candidate information, content for which it is possible to select a designation for making the payment on a predetermined date based on the user's payment history; The reception unit is Accepting a designation to make the payment on a predetermined date based on the user's payment history through an operation on the content; The payment processing unit, making the payment on a predetermined date based on the user's payment history; 8. The information processing apparatus according to claim 5, wherein the information processing apparatus is a computer.

9. The reception unit is Further accepting a designation of a time for the settlement; The payment processing unit, making the payment at the time designated and accepted; 9. The information processing apparatus according to claim 5, wherein the information processing apparatus is a computer.

10. The reception unit is Further accepting changes to the payment date; The payment processing unit, making the settlement on the payment date for which the change has been accepted; 10. The information processing apparatus according to claim 5, wherein the information processing apparatus is a computer.

11. A storage unit for storing the invoice information; Further equipped with The payment processing unit, performing a settlement based on the invoice information stored in the storage unit; 11. The information processing apparatus according to claim 1,

12. The payment processing unit, If the electronic money owned by the user is insufficient to cover the amount of the payment, the shortfall is made by transferring the electronic money from a specified account set by the user, and the payment is made.

12. The information processing apparatus according to claim 1,

13. a notification unit for notifying the user of a shortage of electronic money when the electronic money owned by the user is insufficient to cover the amount of the payment; The information processing apparatus according to claim 1 , further comprising:

14. The notification unit is If the electronic money owned by the user is insufficient to cover the amount of the payment, a notification is further given to the user to encourage the user to deposit the electronic money.

14. The information processing apparatus according to claim 13,

15. 1. A computer-implemented information processing method, comprising: a storage step of storing information on the account held by the user and the settlement destination business operator, which is used in a settlement service using the user's user terminal, and the user information of the user in a predetermined storage device; a payment service using the user terminal, which, upon receiving notification of user identification information identifying the user, payment destination identification information identifying the payment destination, and a payment amount, withdraws electronic money equivalent to the payment amount from an account corresponding to the user identification information, and deposits the payment amount into the account corresponding to the payment destination identification information, and provides an acquisition step of photographing a predetermined code or a character string used for optical character recognition, or acquiring invoice information shown on an invoice via an application that receives data from a predetermined terminal; determining a payment period based on the bill information; a setting step of selecting a payment date that satisfies a predetermined condition set in advance by a user via the application from the identified payment period, setting the payment date designated by the user from among the selected payment dates, and storing the setting result as the user information in the storage device; a payment processing step of performing a payment based on the invoice information via the application on the payment date stored in the storage device; 13. An information processing method comprising:

16. a storage step for storing information on an account held by a user and a payment destination business operator, and user information of the user, in a predetermined storage device, the information being used in a payment service using the user's user terminal; a payment service using the user terminal, which, upon receiving notification of user identification information identifying the user, payment destination identification information identifying the payment destination, and a payment amount, debits electronic money equivalent to the payment amount from an account corresponding to the user identification information, and deposits the payment amount into the account corresponding to the payment destination identification information, and provides an acquisition step of acquiring invoice information shown on an invoice via an application for photographing a predetermined code or a character string used for optical character recognition, or receiving data from a predetermined terminal; a determination step of determining a payment period based on the bill information; a setting procedure for selecting a payment date that satisfies a predetermined condition set in advance by a user via the application from the identified payment period, setting a payment date designated by the user from among the selected payment dates, and storing the setting result as the user information in the storage device; a payment processing procedure for performing a payment based on the invoice information via the application on the payment date stored in the storage device; An information processing program characterized by causing a computer to execute the above.

Images