JP7675758B2 - Information processing device, information processing method, and information processing program - Google Patents

Description

Application of Article 30, Paragraph 2 of the Patent Act Public information. pdf

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

Conventionally, technology is known 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. Technology is also known for providing a service in which information such as the invoice amount printed on a paper invoice is read and payment can be made with electronic money, even in the case of a paper invoice.

JP 2007-305166 A

However, the above conventional technologies are not necessarily convenient for users.

For example, in the above-mentioned conventional technology, the timing for payment of an invoice is the timing when the user completes the payment procedure, which means there is a possibility that a payment may be forgotten. Also, in the above-mentioned conventional technology, the user may not necessarily be able to make a payment when he or she wishes (for example, after payday).

The present application has been made in consideration of the above, and aims to provide an information processing device, an information processing method, and an information processing program that improve user convenience.

The information processing device according to the present application is characterized by comprising: an acquisition unit that acquires invoice information indicated by an invoice via a user terminal of a user 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 identifies a payment period based on the invoice information; a setting unit that selects a payment date that satisfies a predetermined condition from the identified payment period and sets the selected payment date; and a payment processing unit that performs a payment based on the invoice information on the set payment date.

The information processing device according to the present application is a payment service using a user terminal of a user, and is characterized in that it includes an acquisition unit that acquires invoice information indicated by an invoice via an application that provides a payment service that, 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 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; a specification unit that specifies a payment period based on the invoice information; a setting unit that selects a payment date that satisfies a predetermined condition from the specified payment period and sets the selected payment date; and a payment processing unit that performs a 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.

The information processing device according to the present application is a payment service using a user terminal, and upon receiving notification of user identification information identifying the user, payment destination identification information identifying the payment destination, and a payment amount, the information processing device includes an acquisition unit that acquires invoice information indicated by an invoice via an application that provides a payment service in which electronic money equivalent to the payment amount is debited from an account corresponding to the user identification information and credited to an account corresponding to the payment destination identification information by the amount of the payment, an identification unit that identifies a payment period based on the invoice information, a setting unit that selects a payment date that satisfies a predetermined condition previously set by the user via the application from the identified payment period and sets the selected payment date, and a payment processing unit that makes a payment based on the invoice information via the application on the set payment date.

According to one aspect of the embodiment, it is possible to improve the convenience of users.

FIG. 1 is a diagram illustrating an example of information processing according to an embodiment. FIG. 2 is a diagram illustrating an example of the configuration of the payment server according to the embodiment. FIG. 3 is a diagram illustrating an example of an account database according to the embodiment. FIG. 4 is a diagram illustrating an example of an invoice information database according to the embodiment. FIG. 5 is a diagram illustrating an example of a user information database according to the embodiment. FIG. 6 is a diagram showing a specific example 1 of a display screen according to the embodiment. FIG. 7 is a diagram showing a second specific example of a display screen according to the embodiment. FIG. 8 is a diagram showing a third specific example of a display screen according to the embodiment. FIG. 9 is a diagram showing a fourth specific example of a display screen according to the embodiment. FIG. 10 is a diagram showing a fifth specific example of a display screen according to the embodiment. FIG. 11 is a diagram showing a sixth specific example of a display screen according to the embodiment. FIG. 12 is a flowchart illustrating an example of a procedure of information processing according to the embodiment. FIG. 13 is a hardware configuration diagram showing an example of a computer that realizes the function of the payment server.

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

[1. Information Processing System]
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.

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) in a wired or wireless manner so as to be able to communicate with each other. 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.

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 payments using a user terminal 100. For example, the payment server 10 manages the 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.

The user terminal 100 shown in FIG. 1 is an information processing device used by 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), etc. 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.

When the user terminal 100 receives control information for implementing a specified information processing from the payment server 10, the user terminal 100 implements the information processing in accordance with 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 specified application itself delivered from the payment server 10 may be regarded as the control information.

1-2. Payment Processing Using User Terminal 100
Here, an example of payment (electronic payment) using the user terminal 100 will be described prior to the information processing executed by the payment server 10. 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 can also be applied when 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, or the like.

For example, when user U1 makes a payment for the use or purchase of 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 the 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.

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. The payment server 10 then sends a notification that the payment has been completed to the user terminal 100. In such a case, the user terminal 100 notifies the user that the payment has been made with electronic money by outputting a screen or a specified sound indicating that the payment has been completed.

Note that payment using the user terminal 100 is not limited to the above-mentioned process. For example, 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 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 user U1 indicated by the user identification information to the store's account, and may notify the store terminal or user terminal 100 of the completion of the payment by outputting a screen or a specified sound indicating that the payment has been completed.

Furthermore, payment using the user terminal 100 may not only be a process of transferring electronic money from an account to which user U1 has previously charged electronic money to the store's account, but may also be, for example, a payment using a credit card that user U1 has previously registered. 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 user U1's credit card for the payment amount.

Payment using the user terminal 100 may not only be a process of transferring electronic money from the account of user U1 to the account of a store, but may also be a payment to transfer electronic money from the account of user U1 to the account of a provider (business) that provides a specified transaction object. In such a case, 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 user U1 by the business with a photographing device (camera) equipped in the user terminal 100. Then, the user terminal 100 displays the payee and payment amount indicated by the read barcode on the screen, and when an operation is received from user U1 to approve the remittance to the payee, it transmits payment information indicating the user identification information, the payment amount, and information identifying the payee to the payment server 10. 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 to the account of the payee.

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.

The payment server 10 then 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. Note that 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. In other words, in the following description, the user U1 may also be read as the user terminal 100.

First, user U1 uses user terminal 100 to read invoice information from paper invoice B1 (step S1). For example, user U1 uses the camera function of user terminal 100 to photograph and import the barcode printed on paper invoice B1. Here, invoice information refers to information including identification information of the business entity making 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 described 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.

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 electronic money described above, and includes invoice information.

Next, the payment server 10 acquires 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 on the paper invoice B1, and identifies the period from the date and time when the invoice information was acquired from the user terminal 100 to the date and time of the payment deadline as the payment period. In addition, when the barcode on the paper invoice B1 does not contain payment deadline information, the payment server 10 can set the payment period to a specified period from the issue date, or can use OCR (Optical Character Recognition) technology to identify the payment deadline written in text.

Then, 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.

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

At this time, the payment server 10 can select a candidate payment date and time that satisfies a specified 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 automatic payment payment method described above, the payment server 10 can also display on the user terminal 100, as candidate information, payment methods such as a payment to be made on a payment date and time specified by user U1 from the presented payment period ("payment reservation" as appropriate), an immediate payment made by user U1 at a timing of his/her choice ("immediate payment" as appropriate), and a payment to be made on a specified date and time based on user U1's payment history (payment history) for each invoice ("history payment" as appropriate).

To explain an example of a payment reservation, the payment server 10 displays, as candidate information, a calendar on the screen of the user terminal 100, on which the payment date and time can be selected. 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.

To explain an example of immediate payment, the payment server 10 displays a button with a message such as "Pay now" on the screen of the user terminal 100 as candidate information. 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.

To explain an example of historical payments, the payment server 10 displays buttons on the screen of the user terminal 100 as candidate information that allow the selection and setting of historical payments. 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 user U1, and displays the identified payment dates on the user terminal 100 as the scheduled payment dates.

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

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.

Then, 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.

At this time, the payment server 10 can also accept re-designation of the payment date and time or a change to 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 to the specified payment date and time or the set historical payment date and time. The payment server 10 can also accept a change to the payment method from the user terminal 100. For example, the payment server 10 accepts a change to the payment method from the user terminal 100 to indicate a desire for immediate payment for the payment.

Then, 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 stated 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.

At this time, if the balance in 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 user U1 that has been set up in advance, and execute the payment process. Furthermore, if 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 automatic payment has been cancelled and user U1 has specified a payment reservation or set up a payment history, the payment server 10 may send a similar push notification.

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

At this time, if automatic charging has been performed during the payment process of the invoice, the payment server 10 may execute a notification to that effect. Also, if the payment process cannot be completed during the payment process of the invoice due to insufficient balance of electronic money, the payment server 10 may notify the user U1 of this effect and display a screen on the user terminal 100 that allows the user U1 to select a payment method. Also, based on the monthly payment history of user U1, the payment server 10 may notify the user U1 of the possibility of forgetting to make a payment (e.g., water bills that are paid by the end of each month have not been paid).

As described above, the payment server 10 according to the embodiment can identify the period during which an invoice can be paid, set the payment date and time from the identified period during which an invoice can be paid, enable the payment of an invoice to be scheduled, and prevent forgetting to pay an invoice. In other words, the payment server 10 according to the embodiment can improve user convenience. Furthermore, the payment server 10 according to the embodiment can further improve user convenience by enabling payment based on stored information even if a paper invoice is lost, and by enabling various notifications to prevent forgetting to pay or insufficient electronic money balances.

[2. Configuration of the payment server]
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 has a communication unit 20, a storage unit 30, and a control unit 40.

[2-1. Communication unit 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 between the user terminal 100, the operator terminal 200, etc.

[2-2. Storage unit 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, an optical disk, etc. As shown in Fig. 2, the storage unit 30 has an account database 31, an invoice information database 32, and a user information database 33.

(Account database 31)
The account database 31 stores various information related to accounts held by users, businesses, etc. in electronic payment services. An example of information stored in the 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, 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 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.

In other words, Figure 3 shows an example in which the information of the account holder identified by the account ID "AID#1" is "User #1" and the account balance is "7,800 yen."

(Invoice information database 32)
The invoice information database 32 stores various information indicated on invoices created by businesses that are billing sources. 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".

"Invoice ID" indicates identification information for identifying an invoice created by a business. "Business ID" indicates identification information for identifying the business that created the invoice. "Invoice amount" indicates the amount that the business will invoice the user. "Payment deadline" indicates the deadline by which the user can pay the invoice amount to the business.

That is, Figure 4 shows an example in which an invoice identified by invoice ID "BID#1" is created by a business identified by business ID "MID#1", the invoice amount is "Invoice amount #1", and the payment deadline is "Payment deadline #1", and an example in which an invoice identified by invoice ID "BID#2" is created by a business identified by business ID "MID#2", the invoice amount is "Invoice amount #2", and the payment deadline is "Payment deadline #2".

(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".

"User ID" indicates identification information for identifying 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 for identifying 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.

In other words, 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".

[2-3. Control unit 40]
The control unit 40 is a controller, and is realized, for example, by a central processing unit (CPU) or a micro processing unit (MPU) 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 application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). 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.

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

(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 made due to server maintenance or the like, the identifying unit 42 can also identify the time period.

(Setting unit 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.

(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 a 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.

As an example of the content to be displayed, the display unit 44 displays content in which the payment date can be selected as candidate information related to a payment reservation. For example, the display unit 44 displays a calendar in which the payment date can be selected as the content. The display unit 44 also displays content in which the designation of 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. The display unit 44 also displays content in which the designation of making a payment on a specific date based on the user's payment history can be selected as candidate information related to payment history. For example, the display unit 44 displays a button in which the designation of making a payment on a specific date based on the user's payment history can be selected on the screen of the user terminal 100.

(Reception unit 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, history payment, etc. At this time, the reception unit 45 may further receive a designation of a time to make the payment.

As an example of the designation accepted for each content, the acceptance unit 45 accepts a designation to make payment on a specific date based on the payment deadline by an operation on the automatic payment content. For example, the acceptance unit 45 accepts the automatic payment setting when the user U1 taps a setting button displayed on the screen of the user terminal 100 that allows the automatic payment to be switched on and off, and accepts the payment date specified when the user U1 taps a button that approves the scheduled payment date presented on the screen of the user terminal 100.

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 the 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 specific 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 selection and setting of 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 that approves the scheduled payment date presented on the screen of the user terminal 100.

The reception unit 45 also accepts changes to the payment date and time. For example, for invoice B1 for which payment has not been completed, the reception unit 45 accepts changes to the desired payment date, etc., 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 to the payment method to a payment reservation or history payment. At this time, if the reception unit 45 accepts a change to the payment method to immediate payment, it accepts a change to a designation of immediate payment on the specified payment date, etc.

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

(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 shown in 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 shown in 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 shown in 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.

At this time, the payment processing unit 46 transfers electronic money in the amount indicated by the billing amount from the user's account indicated by the user ID to the business's account indicated by the business ID at the specified payment date and time. The payment processing unit 46 also makes a payment based on the invoice information at the payment date and time for which the change has been accepted. Furthermore, if the electronic money owned by the user is insufficient for the billing amount of the payment based on the invoice information, the payment processing unit 46 transfers the missing amount as electronic money from a specified account set by the user and makes 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 in advance by the user U1. In such a case, for example, the user terminal 100 may transfer electronic money of the payment amount to the account of the store A and bill the management company of the credit card of the user U1 for the payment amount.

(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 has 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.

3. Specific 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 Figures 6 to 11. Figures 6 to 11 are diagrams showing specific examples of display screens according to the embodiment. Below, the display screens relating to the processing of paper invoices B1 and the display screens relating to the processing of electronic invoices B2 will be described in that order.

[3-1. Paper invoice B1]
6 and 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.

(Display screen regarding reading process)
The display screen for the reading process of the paper invoice B1 will be described with reference to Fig. 6. First, the invoice payment top screen (see Fig. 6(1)) is displayed, and by tapping the "Read invoice" display, the screen transitions to a screen (see Fig. 6(2)) for reading the barcode of the paper invoice B1 with a camera.

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

Here, by tapping 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 dates of the non-payment period grayed out will be displayed. At this time, tap the date column (see FIG. 6 (6)) on the calendar screen for which you wish to make payment, then tap the "Register" display (see FIG. 6 (7)). If the registration is successful, you will be transferred to a screen (see FIG. 6 (13)) that displays a message indicating successful registration, such as "Automatic payment date registered."

Furthermore, even if a payment reservation is registered as described above, if immediate payment is desired, immediate payment can be made by tapping the "Pay Now" display (see FIG. 6 (14)). Also, the date and time of the registered payment reservation can be changed by tapping the "Change" display on the screen of FIG. 6 (14).

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

In addition, 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)) is displayed in the date column on the calendar corresponding to the registered date. In the example of Figure 6 (8), one payment reservation is registered on January 26th and three payment reservations are registered on January 28th. At this time, you can check the registered details and reset the payment date and time by tapping on the registered date column (see Figures 6 (9) to (12)).

(Management list display screen)
The display screen of the management list of paper invoice B1 will be described with reference to Fig. 7. First, the bill payment top screen (see Fig. 7(1)) is displayed, and by tapping the "Manage automatic payments" display, the display screen of the management list of paper invoice B1 (see Fig. 7(2)) is displayed. At this time, by tapping the "Add invoice" display on the screen of Fig. 7(2), a payment reservation for paper invoice B1 or electronic invoice B2 can be additionally registered.

Next, on the screen of FIG. 7(2), if there is an electronic invoice B2 that can be registered, the screen transitions to a screen for selecting an electronic invoice B2 that can be registered (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 reservation.

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

[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 display screen for the payment history list, the display screen for the electronic invoice details, and the display screen for the management list will be described below in that order.

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

Next, by turning on the "Automatic Payment" setting button on the screen of FIG. 8 (2), the screen transitions to a screen (see FIG. 8 (3)) that displays the completion of the automatic payment setting, which executes settlement before the payment due date each 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.

When the above automatic payment settings are complete, the setting completion such as "Pay automatically every month" (see Figure 8 (4) to (5)) will be displayed for the set invoice on the bill payment top 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.

(Electronic invoice details display screen 1)
Display screen 1 of the electronic invoice details screen of electronic invoice B2 will be described with reference to Fig. 9. First, the invoice payment top screen (see Fig. 9(1)) is displayed, and by tapping on the display of an invoice for which the electronic invoice details screen is to be displayed, the display transitions to the electronic invoice details screen of electronic invoice B2 (see Fig. 9(2)).

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 payment before the payment due date every month. For example, by setting the above automatic payment, payment can be automatically made on the day before the payment due date indicated by electronic invoice B2 without specifying the payment date and time. Here, the payment 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 specified payment reservation.

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

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 (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 setting, which makes automatic payment before the payment due date each month. For example, by setting the above automatic payment, payment can be made automatically the day before the payment due date indicated on electronic invoice B2 without the need to specify a payment date and time.

(Management list display screen)
The display screen of the management list of electronic invoice B2 will be described with reference to Fig. 11. First, the bill payment top screen (see Fig. 11(1)) is displayed, and by tapping the "Manage automatic payments" display, the display screen of the management list of electronic invoice B2 (see Fig. 11(2)) is displayed. At this time, by tapping the "Add invoice" display on the screen of Fig. 11(2), a payment reservation for paper invoice B1 or electronic invoice B2 can be additionally registered.

Next, on the screen of FIG. 11 (2), if there is an electronic invoice B2 that can be registered, the screen transitions to a screen for selecting an electronic invoice B2 that can be registered (see FIG. 11 (3)). By selecting an electronic invoice B2 on the screen of FIG. 11 (3), the screen transitions to a screen that displays the completion of the additional registration to the payment reservation (see FIG. 11 (4)).

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

4. Provision process flow
The procedure of information processing 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 procedure of information processing 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 processing may be omitted.

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.

Second, the identification unit 42 of the payment server 10 executes a payment period identification process (step S102). For example, the identification unit 42 identifies the date and time of the payment deadline from the invoice information, 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 deadline as the payment period.

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 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 the selection of payment methods such as payment reservation, immediate payment, and historical payment as candidate information for payment methods other than those mentioned above.

Fourthly, 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.

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 specified by the user U1.

Sixth, the notification unit 47 executes notification processing (step S106) and terminates the processing. For example, the notification unit 47 notifies information regarding the payment of the bill of user U1 (e.g., shortfall in payment amount, automatic charge completion, etc.).

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.

The acquisition unit 41 acquires the invoice information indicated by the invoice, the identification unit 42 identifies 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 identified 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.

The acquisition unit 41 also acquires invoice information indicated by the invoice photographed by the user's user terminal. This allows the payment server 10 according to the embodiment to improve user convenience by using the invoice information indicated by the paper invoice B1.

The acquisition unit 41 also acquires invoice information indicated by the invoice sent to the user terminal of the user. This allows the payment server 10 according to the embodiment to improve user convenience by using the invoice information indicated by the electronic invoice B2.

The setting unit 43 also sets the payment date and time to a date and time that corresponds to a predetermined time before the payment deadline indicated in the invoice information. This allows the payment server 10 according to the embodiment to automatically execute payment at a predetermined date and time, thereby improving user convenience.

The display unit 44 also selects a candidate payment date and time that satisfies a predetermined condition from the identified payment period and displays candidate information related to the selected candidate, and the reception unit 45 receives the specification of the payment date and time from the displayed candidate information. 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 the payment method is selectable.

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 through an operation on the content, and the payment processing unit 46 performs the payment at the payment date and time for which the designation has been received. As a result, the payment server 10 according to the embodiment can improve the convenience of the user by executing the payment using content for which the payment date and time can be selected.

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.

The display unit 44 also 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 executing payment using content for which payment can be made based on the user's behavioral history.

The reception unit 45 also 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 allowing changes to the payment reservation.

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

The notification unit 47 further notifies the user U1 about payments that may not have been completed based on the user U1's past payment history. This allows the payment server 10 according to the embodiment to further prevent users from forgetting to pay invoices, improving user convenience.

When the electronic money held by user U1 is insufficient to cover the amount of the payment being requested, the payment processing unit 46 transfers the shortfall in electronic money from a specified account set by user U1 and makes the payment. This allows the payment server 10 according to the embodiment to prevent inability to pay due to forgetting to charge electronic money, thereby improving user convenience.

If the electronic money owned by user U1 is insufficient to cover the amount of the payment being requested, the notification unit 47 further notifies user U1 that the electronic money is insufficient. This allows the payment server 10 according to the embodiment to recognize that electronic money has been forgotten to be charged, thereby improving the convenience of the user.

If the electronic money owned by user U1 is insufficient to cover the amount of the payment request, the notification unit 47 further notifies user U1 to prompt him/her to deposit electronic money. This allows the payment server 10 according to the embodiment to prevent users from forgetting to charge their electronic money, thereby improving user convenience.

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.

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

HDD 1400 stores programs executed by CPU 1100 and data used by such programs. 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 transmits data generated by CPU 1100 to other devices via communication network 500.

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.

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.

For example, when the computer 1000 functions as the payment server 10, the CPU 1100 of the computer 1000 executes a program loaded onto the RAM 1200 to realize the functions of the control unit 40. In addition, the HDD 1400 stores each piece of 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 of the computer 1000 may obtain these programs from another device via a specified communication network.

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

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 using known methods. In addition, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified. For example, the various information shown in each drawing is not limited to the information shown in the drawings.

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 depending on various loads, usage conditions, etc.

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.

The above-described embodiments and variations can be combined as appropriate to the extent that they do not cause inconsistencies in the processing content.

The above-mentioned "section, module, unit" can be read as "means" or "circuit." For example, a control unit can be read as a control means or a control circuit.

REFERENCE SIGNS LIST 1 Information processing system 10 Payment server 20 Communication unit 30 Storage unit 31 Account database 32 Invoice information database 33 User information database 40 Control unit 41 Acquisition unit 42 Identification unit 43 Setting unit 44 Display unit 45 Reception unit 46 Payment processing unit 47 Notification unit 100 User terminal

Claims (16)

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: 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 , 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 , 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. 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: 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 , 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 . 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. 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. 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. 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, 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, 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: 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 , 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: a storage step for storing information on an account held by a user and a settlement destination business operator, and user information of the user, in a predetermined storage device, the information being used in a settlement 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