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

Abstract

To improve usability in postpaid cashless settlement.SOLUTION: An information processing device comprises an acquisition unit and a provision unit. When a display request of a first screen, which is a settlement application screen provided to an electronic settlement service user to use code settlement and corresponds to a postpaid payment method, is received from a user, the acquisition unit acquires request status information indicative of the request situation of a postpaid usage fee corresponding to a target user, who is a display request transmission source, from the other device managed by a business operator operating a settlement service, which is other service cooperating with the electronic settlement service and providing the user with a postpaid payment method through the electronic settlement service. The provision unit provides the target user with screen information for displaying the first screen reflecting the request situation corresponding to the target user on the basis of the request status information acquired by the acquisition unit.SELECTED DRAWING: Figure 6

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] Traditionally, cashless payment methods have been widely recognized by consumers, mainly in commercial transactions between companies and individuals. In particular, electronic payment services that are conducted online using personal user devices such as smartphones have become widely accepted among consumers due to their convenience.

[0003] In addition, for example, with regard to post-payment cashless payments such as credit cards, technologies have been proposed that provide a system that makes it easy for users to pay while also achieving both customer satisfaction and improved collection rates. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2011-108221 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, the above-mentioned conventional techniques leave room for improvement in terms of improving the usability of post-payment type cashless payment.

[0006] 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 can improve usability in post-payment type cashless payment. [Means for solving the problem]

[0007] The information processing device according to the present application is an information processing device that executes processing related to an electronic payment service that allows a user of the electronic payment service to select a deferred payment method as a payment method for a price of a transaction object when using code payment using predetermined code information, and includes an acquisition unit and a provision unit. The acquisition unit is a screen of a payment application provided to a user of the electronic payment service to use code payment, and when a display request for a first screen corresponding to the deferred payment method is received from the user, the acquisition unit acquires billing status information indicating a billing status of the deferred payment usage fee corresponding to the target user who is the sender of the display request from another device managed by a business that operates a payment service that is linked to the electronic payment service and provides the user with a deferred payment method through the electronic payment service. The provision unit provides the target user with screen information for displaying a first screen reflecting the billing status corresponding to the target user based on the billing status information acquired by the acquisition unit. Effect of the Invention

[0008] According to one aspect of the embodiment, it is possible to improve the usability of post-payment type cashless payment. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram for explaining an overview of information processing (part 1) according to an embodiment. [Diagram 2] FIG. 2 is a diagram showing an example of an application screen for carrying out a procedure for making a payment promise according to the embodiment. [Diagram 3] FIG. 3 is a diagram for explaining an overview of information processing (part 2) according to the embodiment. [Figure 4] FIG. 4 is a diagram showing an example of an application screen corresponding to a function of accepting changes to the payment method, etc., of a postpaid service charge according to the embodiment. [Diagram 5] FIG. 5 is a diagram conceptually illustrating an example of reference information indicating the correspondence between billing statuses and payment methods according to the embodiment. [Figure 6]FIG. 6 is a diagram illustrating an example of the configuration of the payment server according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of user information stored in a user information storage unit according to the embodiment. [Figure 8] FIG. 8 is a flowchart illustrating an example of a processing procedure of the information processing (part 1) executed by the payment server according to the embodiment. [Figure 9] FIG. 9 is a flowchart illustrating an example of a processing procedure of the information processing (part 2) executed by the payment server according to the embodiment. [Figure 10] FIG. 10 is a hardware configuration diagram showing an example of a computer that realizes the functions of the payment server constituting the information processing system according to the embodiment or the modification. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, the information processing system, 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 the embodiments. In addition, the same parts in the following embodiments are given the same reference numerals, and duplicated descriptions are omitted.

[0011] 1. Embodiment (1-1. System Configuration) Hereinafter, the information processing according to the embodiment will be specifically described. First, before describing the information processing according to the embodiment, an example of the configuration of the information processing system SYS will be described with reference to FIG.

[0012] As shown in Fig. 1, the information processing system SYS according to the embodiment includes a user terminal 10, a payment server 100, and a credit card server 200. The user terminal 10, the payment server 100, and the credit card server 200 are connected to a network N (see Fig. 2, for example) by wire or wirelessly. The user terminal 10, the payment server 100, and the credit card server 200 can communicate with other devices via the network N. The network N is, for example, a WAN (Wide Area Network) such as the Internet.

[0013] The user terminal 10 shown in Fig. 1 is an information processing terminal used by a service user UA who is a user of an electronic payment service provided by a business operator who operates and manages the payment server 100. The user terminal 10 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 10 displays information distributed by the payment server 100 by a web browser or an application. Note that Fig. 1 illustrates an example in which the user terminal 10 is a smartphone.

[0014] In addition, the user terminal 10 is installed with a user application program (hereinafter, appropriately referred to as a "payment app") for using code payment (also referred to as "smartphone payment") provided to the service user UA as one of the cashless payment methods. When the user terminal 10 receives control information for realizing a predetermined information processing through the payment app from the payment server 100, the user terminal 10 realizes the information processing 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). Note that the predetermined application itself delivered from the payment server 100 may be regarded as the control information.

[0015] The payment server 100 shown in Fig. 1 is an information processing device operated and managed by an electronic payment service provider UB (hereinafter referred to as "service provider UB") that provides electronic payment services. The payment server 100 may be realized by a mainframe, a workstation, or the like. In addition, when the payment server 100 is configured by a server device, it may be realized by a single server device, or may be realized by a cloud system in which multiple server devices and multiple storage devices operate in cooperation with each other.

[0016] Electronic payment services are provided to each service user through the above-mentioned payment app. For example, the payment app has various functions related to payments by code payment and additional functions related to the electronic payment service. Additional functions include a function to check transaction history, a function to search for nearby stores, and a function to manage user accounts. Electronic payment services can also be said to be services that provide a predetermined transaction method that controls the exchange of electronic money by code payment.

[0017] In addition, the payment server 100, in conjunction with a payment application running on the user terminal 10, executes various processes related to the electronic payment service provided, for example, through a dedicated online system. For example, the payment server 100 distributes the payment application to those who wish to use the electronic payment service, and provides the electronic payment service on the condition that a predetermined procedure in the payment application is completed. In addition, when the payment server 100 accepts a transaction request from the payment application via an interface dedicated to the payment application (for example, various operation screens displayed on the user terminal 10 by the function of the payment supplement), it executes information processing including a remittance process of electronic money between accounts according to the transaction request. The payment application transmits transaction information including information such as the payment destination, the payment source, and the payment amount to the payment server 100. In addition to the above-mentioned information, the transaction information may include information such as a transaction code for individually identifying the transaction and date and time information (i.e., a timestamp) for identifying the date and time when the transaction was performed.

[0018] Furthermore, electronic payment services offer multiple payment methods that service users can choose from when using code payment, such as "balance payment," "deferred payment," and "credit card payment." "Deferred payment" and "credit card payment" are deferred payment methods that service users UA of electronic payment services can choose when using code payment to pay for the price of a transaction. Note that in the following explanation, "deferred payment" and "deferred payment" are synonymous and are merely alternative terms for the sake of convenience.

[0019] For example, when the service user UA selects "balance payment," the payment server 100 immediately settles the price of the transaction by transferring an amount of electronic money equivalent to the price of the transaction from the money balance, which is the balance of electronic money held by the service user UA, to the payment destination account.

[0020] In addition, if a credit card service provider UC (hereinafter referred to as the "service provider UC"), which will be described later, is the operating company of the credit card registered by the service user UA in the payment application, the service provider UB cooperates with the service provider UC to realize the payment process when the service user UA selects "credit card payment". In other words, the credit card service provided by the service provider UC to the service user UA is an example of another service that cooperates with the electronic payment service provided by the service provider UB to the service user UA. When collaborating, the service providers UB and UC link information about each other's customers by ID collaboration or the like. The information about each other's customers includes identification information given to each service user in each service and bank account information used for settling various charges. For example, the service providers UB and UC may manage common identification information between the providers as information for identifying the same customer. Furthermore, identification information uniquely assigned to a customer by either the service provider UB or the service provider UC may be managed by the other provider. For example, in an electronic payment service, the service provider UC may manage the user IDs individually assigned to the service users UA in association with the same customer. When authenticating the identity of a customer, the payment server 100 or the credit card server 200 may execute an identity verification procedure using a method such as eKYC (electronic Know Your Customer).

[0021] For example, when the service user UA selects "credit card payment," the payment server 100 transfers electronic money in an amount equivalent to the price of the transaction to the payment destination account. The service provider UB then bills the service provider UC for the payment amount equivalent to the price of the transaction. The service provider UC pays the billed amount in response to the bill from the service provider UB. The credit card server 200 also collects the credit card usage fee by debiting it on a specified date from the bank account registered by the service user UA as the account for debiting the credit card usage fee.

[0022] Also, for example, when the service user UA selects "deferred payment," the payment server 100 advances the price of the transaction and settles it at a later date. For example, when the service user UA selects "deferred payment," the payment server 100 advances the price of the transaction by transferring electronic money in an amount equivalent to the price of the transaction from the advance payment account to an electronic money account (account where the balance of electronic money is managed) held by the store that is the payment destination, or by electronically transferring cash in an amount equivalent to the price of the transaction to a bank account held by the store that is the payment destination. Also, the payment server 100 collects the price of the "deferred payment" by withdrawing the price on a specified date from a bank account that the service user UA has registered in the payment app as an account for withdrawing the price of the "deferred payment."

[0023] The credit card server 200 shown in FIG. 2 is an information processing device operated and managed by a service provider UC that provides a postpaid cashless payment service using a credit card to customers including the service user UA. The service provider UC issues credit cards to users of the cashless payment service and manages the credit card information in association with user information registered by the user. For example, the credit card server 200 manages billing status information indicating the billing status of the postpaid usage fee to the service user UA. The credit card server 200 may be realized by a mainframe, a workstation, or the like. Furthermore, when the credit card server 200 is configured as a server device, it may be realized by a single server device, or may be realized by a cloud system in which multiple server devices and multiple storage devices operate in cooperation with each other.

[0024] For example, when the credit card server 200 receives billing information related to "credit card payment" from the payment server 100, it executes a payment process to pay the billed amount to the service provider UB. Furthermore, the credit card server 200 manages the service user UA who registers the use of a credit card issued by the service provider UC as a payment method in an identifiable state when registering for the use of "credit card payment" in the electronic payment service. For example, the credit card server 200 manages the user ID corresponding to the service user UA in association with the customer information of the cashless payment service operated by the service provider UC. Then, the credit card server 200 bills the service user UA who used the "credit card payment" in the electronic payment service for the usage fee of the "credit card payment" in the electronic payment service based on the bill received from the payment server 100. Furthermore, the credit card server 200 collects the credit card usage fee by debiting the bank account registered by the service user UA as the account for debiting the credit card usage fee on a specified date.

[0025] Furthermore, the credit card server 200 may execute a process of deducting the usage fee for "deferred payment" in the electronic payment service together with the usage fee for "credit card payment" in response to a request from the payment server 100. In this case, the credit card server 200 acquires billing information regarding the usage fee for "deferred payment" from the payment server 100. Then, the credit card server 200 deducts the usage fee for "deferred payment" together with the usage fee for "credit card payment" based on the usage fee for "deferred payment" included in the acquired billing information.

[0026] (1-2. Payment using user terminal 10) Here, an example of code payment using the user terminal 10 will be described. In the following description, for example, a two-dimensional code (QR code (registered trademark)) placed in a specific store and indicating store identification information for identifying the specific store is used to perform a payment using the user terminal 10 by a service user UA who receives a transaction object from a specific store. Note that the example of code payment described below is also applicable to a case where an arbitrary user uses an arbitrary user terminal 10 to perform a payment at an arbitrary store. In addition, the two-dimensional code indicating the store identification information may be not only a QR code, but also a barcode, a predetermined mark, a number, or the like. In addition, the two-dimensional code is not limited to an example that is physically formed by a printed matter printed on a medium such as paper, and may be formed by image information displayed on an arbitrary terminal.

[0027] For example, when a service user UA makes a payment for the purchase or use of a transaction object such as various products or services at a specific store, the service user UA launches a payment application pre-installed in the user terminal 10. Then, the service user UA photographs a two-dimensional code placed at the specific store via the payment application. In such a case, the user terminal 10 displays a screen for inputting the price of the transaction object, and accepts input of the payment amount from the service user UA or a clerk at the specific store. Then, the user terminal 10 transmits transaction information including user identification information that identifies the service user UA, store identification information (or information indicated by the store identification information, i.e., information indicating the specific store (e.g., store ID)), and the payment amount to the payment server 100.

[0028] When the payment server 100 accepts the transaction information from the user terminal 10, it transfers electronic money equivalent to the payment amount from the account of the service user UA indicated by the user identification information to the account of the specified store indicated by the store identification information. At this time, the payment server 100 may transfer the electronic money to the account of the specified store after subtracting a predetermined fee to be charged to the specified store from the electronic money equivalent to the payment amount. Then, the payment server 100 transmits a notification that the transaction is completed to the user terminal 10. In such a case, the user terminal 10 notifies the service user UA that the transaction using electronic money is completed by outputting a screen or a predetermined sound indicating that the transaction is completed. Alternatively, the payment server 100 may withdraw electronic money equivalent to the payment amount from the account of the service user UA indicated by the user identification information, manage it as sales information of the specified store, and transfer cash equivalent to the sales to a bank account held by the specified store at a predetermined timing. In this case, the payment server 100 may notify the service user UA that the transaction using electronic money has been completed at the time when electronic money equivalent to the payment amount has been withdrawn from the account of the service user UA.

[0029] It should be noted that the payment using the user terminal 10 is not limited to the above-mentioned process. For example, the payment using the user terminal 10 may be made using a terminal device (hereinafter referred to as a "store terminal") installed in a specific store. Specifically, the user terminal 10 first displays code information indicating user identification information for identifying the service user UA on a screen. In such a case, the store terminal reads the user identification information from the code information displayed on the user terminal 10, and transmits transaction information including the read user identification information (or information indicated by the user identification information, i.e., information indicating the service user UA (e.g., user ID)), the payment amount, and information identifying the specific store to the payment server 100.

[0030] When the payment server 100 receives the transaction information from the store terminal, it transfers electronic money equivalent to the payment amount from the account of the service user UA indicated by the user identification information to the account of the specified store. Then, the payment server 100 transmits a notification that the transaction has been completed to the store terminal or the user terminal 10. The store terminal or the user terminal 10 notifies the service user UA that the transaction using electronic money has been completed by outputting a screen or a specified sound indicating that the transaction has been completed. The payment server 100 may also withdraw electronic money equivalent to the payment amount from the account of the service user UA indicated by the user identification information, manage the electronic money as sales information of the specified store, and transfer cash equivalent to the sales amount to a bank account held by the specified store at a specified timing. In this case, the payment server 100 may notify the store clerk or the service user UA that the transaction using electronic money has been completed at the timing when the electronic money equivalent to the payment amount is withdrawn from the account of the service user UA.

[0031] Furthermore, the payment using the user terminal 10 may not only be a process of transferring electronic money from an account to which the service user UA has previously charged electronic money to an account of a specific store, but may also be, for example, a payment using a credit card registered in advance by the service user UA. In such a case, for example, the user terminal 10 may transfer electronic money in an amount indicated by the payment amount to the account of the specific store, and may also bill the operating company of the service user UA's credit card for the amount indicated by the payment amount.

[0032] Furthermore, the settlement using the user terminal 10 may not only be a process of transferring electronic money from the account of the service user UA to the account of a specific store, but may also be, for example, a settlement of transferring electronic money from the account of the service user UA to the account of another user (i.e., a transfer between users). For example, the user terminal 10 used by the service user UA who is the sender of the remittance reads user identification information (for example, user identification information displayed on a terminal device used by the user of the remittance destination) that identifies the user of the remittance destination, accepts an input of the remittance amount from the service user UA, and transmits information indicating the read identification information, the remittance amount, and the user identification information that identifies the service user UA to the settlement server 100. In such a case, the settlement server 100 may transfer electronic money in an amount indicated by the remittance amount from the account of the service user UA to the account of the user of the remittance destination, and notify the fact that the remittance has been completed by outputting a screen or a predetermined sound indicating that the remittance has been completed on the user terminal 10 or the terminal device used by the user of the remittance destination.

[0033] Note that remittance using the user terminal 10 is not limited to the above-mentioned process. For example, remittance using the user terminal 10 may be performed by inputting the telephone number of the remittance destination user or information indicating the remittance destination user (e.g., user ID) into the user terminal 10. As a specific example, the user terminal 10 accepts input of the telephone number or user ID of the remittance destination user and the remittance amount from the service user UA, and transmits the input telephone number or user ID, the remittance amount, and user identification information for identifying the service user UA to the payment server 100. The payment server 100 then transfers electronic money in an amount indicated by the remittance amount from the account of the service user UA to the account of the user linked to the transmitted telephone number or user ID.

[0034] Here, the telephone number or user ID of the remittance destination user may be linked to information about the user and registered in advance in the payment application. In this case, the user terminal 10 accepts, from the service user UA, the designation of the user (remittance destination) registered in the payment application and the input of the remittance amount to the user, and transmits to the payment server 100 the telephone number or user ID linked to the designated user, the remittance amount, and user identification information for identifying the service user UA.

[0035] Furthermore, for example, remittance using the user terminal 10 may be performed by providing the remittance user with link information for receiving the remittance amount. As a specific example, the user terminal 10 accepts an input of the remittance amount from the service user UA, generates link information for receiving the remittance amount, and provides the link information to a terminal device used by the remittance user by sending an email including the link information or posting information including the link information on a social networking service (SNS). Then, when the remittance user selects the link information and performs a receiving operation, the settlement server 100 transfers electronic money in an amount indicated by the remittance amount from the account of the service user UA to the account of the remittance user.

[0036] The above-mentioned payment means and payment services are not limited to those for providing a price (settlement of debt) for purchasing a product or providing a service. For example, as described above, the payment means and payment services may have a function related to remittance between accounts held by multiple users. That is, the above-mentioned payment means and payment services may be services that control the transmission and reception of electronic money between accounts of any owner linked to the owner of electronic money, such as a user or a store. That is, the payment means and payment services according to the embodiment may be provided in any form as long as they are transaction means and transaction services that execute various controls for realizing the exchange of electronic money (not only various inter-account remittance controls via electronic money, but also controls related to exchanges between electronic money accounts and bank accounts, various claim processes such as installments and processes associated with bonus payments, and various controls related to the exchange of assets including electronic money). In addition, the various controls realized by such transaction means and transaction services may include both control related to payment and control related to remittance, or only one of them. That is, a "transaction" is a concept that includes not only "settlement" related to electronic money, but also "remittance" of electronic money and various other processes. In other words, the payment server 100 may be an information processing device that realizes a transaction means for controlling the exchange of electronic money between any owners.

[0037] (1-3. Information Processing According to the Embodiment) (1-3-1. Overview of Information Processing (part 1) according to the embodiment) An overview of information processing according to an embodiment will be described below with reference to FIG. 1. FIG. 1 is a diagram for explaining an overview of information processing (part 1) according to an embodiment. The following description shows an example of information processing in the case where a credit card server 200 collects in a lump sum the usage fee for code payment made by a service user UA using "deferred payment" or "credit card payment." Note that in the following description, the service user UA and the user terminal 10 may be regarded as the same thing. In other words, the service user UA can be read as the user terminal 10.

[0038] As shown in Fig. 1, the user terminal 10 transmits a display request for an application screen corresponding to a "deferred payment" function installed in the payment application to the payment server 100 in accordance with an operation of the service user UA (step S01). The display request includes a user ID (e.g., U#001) for uniquely identifying the service user UA in the electronic payment service.

[0039] When the payment server 100 receives a display request for an application screen corresponding to the "deferred payment" function from the user terminal 10, it transmits to the credit card server 200 a request to obtain billing status information indicating the billing status of the deferred payment usage fee corresponding to the target user (step S02). For example, the request includes the user ID included in the display request received from the user terminal 10, i.e., a user ID (e.g., "U#001") for uniquely identifying the service user UA who is the target user.

[0040] When the credit card server 200 receives a request to obtain billing status information from the payment server 100, it obtains the billing status information associated with the user ID included in the request, and responds with the obtained billing status information to the payment server 100 (step S03).

[0041] When the payment server 100 receives the billing status information from the credit card server 200, it transmits screen information for displaying an app screen reflecting the billing status of the target user to the user terminal 10 based on the received billing status information (step S04).

[0042] For example, the settlement server 100 may provide the service user UA with screen information including image information showing the billing status of the postpaid usage fee corresponding to the service user UA. Specifically, the settlement server 100 can provide screen information including image information showing the billing status as "provisionally confirmed", "confirmed", "payment confirmation in progress", "paid", or "unpaid".

[0043] When the user terminal 10 receives the screen information from the payment server 100, the user terminal 10 displays an application screen G-1 corresponding to the "deferred payment" function based on the received screen information. Each of the display examples EX-1 to EX-5 shown in FIG. 1 shows an example of the application screen G-1 corresponding to the "deferred payment" function displayed on the user terminal 10.

[0044] For example, the application screen G-1 shown in the display example EX-1 includes image information OB-1 indicating that the billing amount for the service user UA is provisionally determined. Also, for example, the application screen G-1 shown in the display example EX-2 includes image information OB-2 indicating that the billing amount for the service user UA is determined. Also, for example, the application screen G-1 shown in the display example EX-3 includes image information OB-3 indicating that the payment is being confirmed to confirm whether or not the postpaid usage fee has been paid by the service user UA. Also, for example, the application screen G-1 shown in the display example EX-4 includes image information OB-4 indicating that the payment of the postpaid usage fee has been confirmed by the service user UA and that the payment has been already made. Also, for example, the application screen G-1 shown in the display example EX-5 includes image information OB-5 indicating that the postpaid usage fee has not been paid by the service user UA.

[0045] In addition, each of the application screens G-1 shown in the display examples EX-1 to EX-5 in FIG. 1 includes link information LK for presenting to the target user payment methods for the deferred payment charges that can be selected by the target user depending on the billing status, and for displaying on the user terminal 10 an application screen G-3 (see, for example, FIG. 4) that can accept a change in the payment method for the deferred payment charges, in response to an operation from the service user UA.

[0046] Among the application screens G-1 shown in display examples EX-1 to EX-5 in FIG. 1, the application screen G-1 shown in display example EX-5 includes information M-1 indicating the number of days elapsed from the payment deadline of the deferred payment usage fee, and a button BT-1 for accepting a "payment promise" from the service user UA, which is a predetermined procedure for promising to repay the deferred payment usage fee. FIG. 2 is a diagram showing an example of an application screen for carrying out the payment promise procedure according to the embodiment. Display example EX-6 shown in FIG. 2 shows an example of an application screen G-2 corresponding to the "payment promise" function displayed on the user terminal 10.

[0047] The application screen G-2 shown in Fig. 2 includes information indicating the billing amount. The application screen G-2 shown in Fig. 2 also includes an area that presents a list of payment methods that the service user UA can select when repaying the deferred payment charge, and an area for accepting the setting of the scheduled payment date, which is the scheduled date for repaying the deferred payment charge, by the service user UA. The service user UA can select the payment method when repaying the deferred payment charge and set the scheduled payment date by operating the application screen G-2. Furthermore, the user terminal 10 can transmit information on the payment method and scheduled payment date set by the service user UA to the payment server 100 according to the operation of the service user UA.

[0048] As shown in Fig. 2, the payment methods that the service user UA can select when repaying the deferred payment charge include balance payment, which is made from the balance of electronic money held by the service user UA in the electronic payment service, retransfer, which is made by debiting again from a payment account that is a bank account set as a withdrawal account for the deferred payment charge, convenience store payment, which is made at a convenience store using an electronic document, bank transfer, which is made by transferring money to a specified bank account, and lump sum payment, which is made together with the next month's usage charge. For example, when a payment method that is expected to be paid immediately, such as balance payment, or a payment method that has a predetermined scheduled payment date, such as lump sum payment, is selected by the service user, the payment server 100 may perform control so that the area for setting the scheduled payment date is automatically hidden. In this case, the payment server 100 may transmit control information for causing the user terminal 10 to execute such control together with the screen information to the user terminal 10.

[0049] In the example shown in FIG. 2, the payment server 100 displays the money balance held by the service user UA as the available amount in association with the item "Balance Payment" displayed on the application screen G-2 as a payment method selectable by the service user UA when repaying a deferred payment charge. The payment server 100 realizes the display of the money balance by including the balance information in the screen information and transmitting it to the user terminal 10. In addition, when displaying the money balance, the payment server 100 may change the display mode depending on whether the money balance is insufficient for the billing amount or not, for example, by highlighting the money balance information more prominently when the balance is insufficient than when the balance is not insufficient. In this case, the payment server 100 may transmit control information for causing the user terminal 10 to execute such control together with the screen information to the user terminal 10.

[0050] In the example shown in Fig. 2, the payment server 100 may display the balance of the bank account set by the service user UA as the withdrawal account, in association with the item "withdraw again from payment account" displayed on the application screen G-2, as a payment method selectable by the service user UA when repaying the deferred payment charge. In this case, the payment server 100 assumes that the bank account held by the service user UA is an account loaned to the service user UA by a bank affiliated with the service provider UB, and is in an environment in which the service user UA's balance information can be obtained from this bank. In this case, the payment server 100 may transmit control information for causing the user terminal 10 to execute such control together with the screen information to the user terminal 10.

[0051] 2, the payment server 100 may control the display of payment methods that cannot be used due to insufficient balance or the like, among the payment methods included in the list of payment methods that the service user UA can select when paying back the deferred payment amount, by changing the standard, not displaying the unavailable payment methods, or displaying frequently used payment methods at the top, so that the payment methods that cannot be used due to insufficient balance or the like are displayed below the available payment methods. In this case, the payment server 100 may transmit control information to the user terminal 10 together with the screen information for causing the user terminal 10 to execute such control.

[0052] In the example shown in Fig. 2, if the payment method is not registered for balance payment or re-withdrawal from the payment account, the payment server 100 may display a button or the like on the application screen G-2 to guide the target user to a registration screen. For example, if the payment server 100 has registered balance payment as the payment method for the deferred payment charge, but has not registered deduction from the bank account, the payment server 100 may guide the target user to an operation for setting deduction from the bank account as the payment method. For example, if the payment server 100 has registered deduction from the bank account as the payment method for the deferred payment charge, but has not registered deduction from the balance, the payment server 100 may guide the target user to an operation for setting deduction from the bank account as the payment method.

[0053] In addition, in the example shown in Figure 2, when the payment server 100 receives information on the scheduled payment date set by the service user UA on the application screen G-2, it may temporarily suspend the execution of a specified action (such as making a phone call to remind the service user UA to make payment) to urge the service user UA, who has an unpaid deferred payment charge, to repay the payment until the scheduled payment date has passed.

[0054] In addition, in the example shown in Figure 2, when convenience store payment is selected as the payment method on the application screen G-2, the payment server 100 can set the expected deposit date set on the application screen G-2 as the expiration date of the barcode on the electronic document used for the convenience store payment.

[0055] Also, for example, when displaying the application screen G-1 shown in the above-mentioned display example EX-1 and display example EX-2, the payment server 100 may provide the service user UA with the money balance and the balance of a bank account for which automatic charge of electronic money is set by displaying them on the application screen G-1. For example, the payment server 100 obtains information on the balance of the bank account of the service user UA using an API provided by the bank that manages the bank account set by the service user UA as the source of charge of the money balance, which is accessible to the system of the bank, and displays the obtained balance information on the application screen G-1. Also, when the money balance or the total amount of the money balance and the bank account balance is less than the confirmed billing amount, the payment server 100 may highlight the money balance or the bank account balance on the application screen G-1. Also, the payment server 100 may execute the above-mentioned display only when "money balance" is set as a payment method selectable when repaying a deferred payment usage fee.

[0056] As described above, in the information processing system SYS according to the embodiment, the payment server 100 can make the service user UA aware of the payment status of the deferred payment usage fee, which is the usage fee for code payment made by selecting the deferred payment method of "deferred payment" or "credit card payment". As a result, in the information processing system SYS according to the embodiment, the payment server 100 can improve the usability of deferred cashless payment.

[0057] (1-3-2. Overview of Information Processing (Part 2) According to the Embodiment) Hereinafter, an overview of the information processing (part 2) according to the embodiment will be described with reference to Fig. 3. Fig. 3 is a diagram for explaining an overview of the information processing (part 2) according to the embodiment.

[0058] 3, the user terminal 10 transmits a display request for an application screen corresponding to a function for accepting changes to the payment method of the postpaid usage fee, etc., to the payment server 100 in accordance with an operation of the service user UA (step S11). The display request includes a user ID (e.g., U#001) for uniquely identifying the service user UA in the electronic payment service.

[0059] When the settlement server 100 receives a display request for an application screen corresponding to a function for accepting changes to the payment method of the postpaid service charge from the user terminal 10, the settlement server 100 transmits a request for acquiring billing status information indicating the billing status of the postpaid service charge corresponding to the target user to the credit card server 200 (step S12). For example, the acquisition request includes the user ID included in the display request received from the user terminal 10, i.e., a user ID (e.g., "U#001") for uniquely identifying the service user UA who is the target user.

[0060] When the credit card server 200 receives a request to obtain billing status information from the payment server 100, it obtains the billing status information associated with the user ID included in the request, and responds with the obtained billing status information to the payment server 100 (step S13).

[0061] When the payment server 100 receives the billing status information from the credit card server 200, it selects a payment method according to the billing status of the target user based on the received billing status information (step S14). In addition, the payment server 100 transmits screen information for displaying an application screen presenting the payment method etc. according to the billing status of the target user to the user terminal 10 (step S15).

[0062] When the user terminal 10 receives the screen information from the payment server 100, the user terminal 10 displays an application screen corresponding to a function for accepting changes to the payment method of the postpaid usage fee, etc., based on the received screen information. Fig. 4 is a diagram showing an example of an application screen corresponding to a function for accepting changes to the payment method of the postpaid usage fee, etc., according to the embodiment. Display example EX-7 shown in Fig. 4 shows an example of an application screen G-3 corresponding to a function for accepting changes to the payment method of the postpaid usage fee, etc., displayed on the user terminal 10.

[0063] The application screen G-3 shown in FIG. 4 is displayed on the user terminal 10 by, for example, the service user UA operating the link information LK shown in FIG. 1. The trigger for displaying the application screen G-4 does not need to be particularly limited to the detection of the operation of the service user UA on the link information LK shown in FIG. 1. For example, the application screen G-3 may be displayed on the user terminal 10 by the detection of the operation of the service user UA on a menu field provided on the top screen of the payment application or a link attached to an e-mail addressed to the target user. As shown in FIG. 4, the application screen G-3 includes a list of information indicating the payment method selected by the payment server 100 according to the billing status of the postpaid usage fee to the service user UA who is the target user, as a payment method for the postpaid usage fee. Note that the list of information indicating the payment method may include a "payment promise" which is a predetermined procedure for promising to repay the postpaid usage fee, and in this case, a button or link for transitioning to the application screen G-2 shown in FIG. 2 described above may be provided. FIG. 5 is a diagram conceptually illustrating an example of reference information indicating the correspondence between the billing status and the payment method according to the embodiment.

[0064] Based on reference information M-2 shown in Figure 5, when the billing status for the target user, service user UA, corresponds to "ST1-1", "ST1-2", "ST2-1", "ST2-2", "ST3-1", or "ST3-2", the payment server 100 can select "Payment Method P1", "Payment Method P2", "Payment Method P3", "Payment Method P4", "Payment Method P5", "Payment Method P6", and "Payment Method P7" as payment methods selectable by the service user UA.

[0065] For example, when the billing status for the service user UA is "ST1-1," it is assumed that the billing amount has not been determined. Also, when the billing status for the service user UA is "ST1-2," it is assumed that the billing amount has been provisionally determined. Also, when the billing status for the service user UA is "ST1-3," it is assumed that the billing amount has been determined.

[0066] Also, for example, if the billing status for service user UA is "ST2-1," "ST2-2," "ST2-3," "ST3-1," "ST3-2," or "ST3-3," it is assumed that the payment has been confirmed and that the amount equivalent to the billing amount has been paid.

[0067] In addition, based on the reference information M-2 shown in Figure 5, when the billing status of the target user, service user UA, corresponds to "ST1-3", "ST2-3", or "ST3-3", the payment server 100 can select "Payment Method 1", "Payment Method 2", "Payment Method 3", and "Payment Method 4" as payment methods selectable by the service user UA.

[0068] Furthermore, when the billing status of the service user UA, who is the target user, corresponds to "ST4-1" or "ST4-2", the settlement server 100 can select "Payment method P8", "Payment method P9", and "Payment method P10" as payment methods selectable by the service user UA based on the reference information M-2 shown in Fig. 5. Furthermore, as shown in Fig. 5, when the billing status of the service user UA, who is the target user, corresponds to "ST4-1" or "ST4-2", the settlement server 100 can select "Payment promise".

[0069] The payment methods selectable by the service user UA may include, for example, revolving payment, cash advance, installment payment, deferral, balance payment when the deferred payment usage fee is unpaid, barcode payment available at convenience stores, re-transfer payment from a bank account, deferral, etc. The settlement server 100 selects a payment method selectable by the service user UA according to the billing status.

[0070] In the information processing system SYS according to the embodiment, the payment server 100 can make the service user UA aware of the payment status of the deferred payment usage fee, which is the usage fee for code payment made by selecting the deferred payment method of "deferred payment" or "credit card payment". As a result, in the information processing system SYS according to the embodiment, the payment server 100 can improve the usability of deferred cashless payment.

[0071] In addition, in the information processing (part 2) according to the embodiment, when the payment server 100 displays an app screen corresponding to the “deferred payment” function, if the billing status of the deferred payment usage fee corresponding to the service user UA is “paid”, it may display the payment method (for example, balance payment or direct debit) used when the deferred payment usage fee was paid.

[0072] In the information processing (part 2) according to the embodiment, the payment server 100 may also display details of the deferred payment usage fee when displaying an application screen corresponding to the “deferred payment” function.

[0073] [2. Equipment configuration] Hereinafter, an example of a functional configuration of the payment server 100 included in the information processing system SYS according to the embodiment will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of the configuration of the payment server 100 according to the embodiment. As shown in Fig. 6, the payment server 100 includes a communication unit 110, a storage unit 120, and a control unit 130.

[0074] (Regarding communication unit 110) The communication unit 110 is realized by, for example, a network interface card (NIC) etc. The communication unit 110 is connected to the network N by wire or wirelessly, and transmits and receives information to and from other devices such as the user terminal 10 and the credit card server 200.

[0075] (Regarding the storage unit 120) The storage unit 120 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. 6, the storage unit 120 has a user information storage unit 121 and a payment method selection information storage unit 122.

[0076] (Regarding the user information storage unit 121) The user information storage unit 121 stores user information related to a service user who uses an electronic payment service. Fig. 7 is a diagram showing an example of user information stored in the user information storage unit 121 according to the embodiment.

[0077] 7, the user information stored in the user information storage unit 121 has multiple items such as a "user ID" item, a "balance payment transaction history" item, a "deferred payment transaction history" item, etc. These items in the user information are mutually associated.

[0078] The "User ID" item stores a user ID, which is unique identification information assigned individually to each service user (such as service user UA shown in Figure 1) who uses the electronic payment service, in order to uniquely identify the service user.

[0079] The "Balance payment transaction history" field stores the history of code payment transactions that were made by selecting "Balance payment." The transaction history may include information such as the payment date and time, the payment destination, and the payment amount for each transaction.

[0080] The "deferred payment transaction history" field stores the history of code payment transactions that were made by selecting "deferred payment." The transaction history may include information such as the date and time of payment, the payment destination, and the payment amount for each transaction.

[0081] (Payment method selection information storage unit 122) The payment method selection information storage unit 122 stores reference information (such as reference information M-2 shown in Figure 5) for selecting a payment method according to the billing status of the deferred payment service charge corresponding to a target user who requests a change in the payment method, etc., of the service charge for the deferred payment service charge.

[0082] (Regarding the control unit 130) The control unit 130 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 100 using a RAM as a working area. The control unit 130 can also be realized, for example, by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0083] As shown in Fig. 4, the control unit 130 has an acquisition unit 131 and a provision unit 132, and these units realize or execute the functions and actions of information processing described below. Note that the control unit 130 may have new functional units different from the units shown in Fig. 6 in response to the extension of various processes executed by the payment server 100.

[0084] (Regarding the acquisition unit 131) The acquisition unit 131 is a screen of a payment application provided to a service user UA, who is a user of an electronic payment service to use code payment, and when it receives a display request for application screen G-1 (an example of a "first screen corresponding to a post-paid payment method") from the service user UA, it acquires billing status information indicating the billing status of the post-paid usage fee corresponding to the service user UA (an example of a "target user") who is the sender of the display request, from a credit card server 200 (an example of an "other device") managed by a service provider UC that operates a payment service that is linked to the electronic payment service and provides the service user UA with credit card payment (an example of a "post-paid payment method") through the electronic payment service.

[0085] (About the provider 132) The provision unit 132 provides screen information for displaying an app screen G-1 reflecting the billing status corresponding to the target user (e.g., service user UA) based on the billing status information acquired by the acquisition unit 131 to the target user by transmitting the screen information to the user terminal 10 via the communication unit 110.

[0086] The providing unit 132 may also provide screen information including image information showing the billing status to the user terminal 10, thereby providing the screen information to the target user.

[0087] In addition, the providing unit 132 may provide the target user with screen information including image information indicating that the deferred payment usage fee is provisionally confirmed, confirmed, payment is being confirmed, paid, or unpaid, as the billing status, by transmitting the screen information to the user terminal 10.

[0088] In addition, the provision unit 132 may present to the target user payment methods for the deferred usage fee that the target user can select depending on the billing status, and provide them to the target user by transmitting screen information for displaying an app screen G-3 (an example of a "second screen") that can accept a change in the payment method to the user terminal 10.

[0089] In addition, when the billing status is unpaid, the provision unit 132 may provide the target user with screen information for displaying an app screen G-2 (an example of a "third screen") that can accept the payment method and expected payment date of the deferred payment usage fee from the target user by transmitting it to the user terminal 10.

[0090] Furthermore, when displaying the application screen G shown in the above-mentioned display example EX-1 and display example EX-2, the providing unit 132 may provide the service user UA with the money balance and the balance of a bank account for which automatic charge of electronic money is set by displaying them on the application screen G. For example, the providing unit 132 obtains information on the balance of the bank account of the service user UA using an API provided by the bank that manages the bank account set by the service user UA as the source of charge of the money balance, which is accessible to the system of the bank, and displays the obtained balance information on the application screen G. Furthermore, when the money balance or the total amount of the money balance and the bank account balance is less than the confirmed billing amount, the providing unit 132 may highlight the money balance or the bank account balance on the application screen G. Furthermore, the providing unit 132 may execute the above-mentioned display only when "money balance" is set as a payment method selectable when repaying a deferred payment usage fee.

[0091] [3. Example of processing procedure] (3-1. Information processing by the payment server 100 (part 1)) Hereinafter, a flow of information processing executed by the payment server 100 according to the embodiment will be described. First, an example of a processing procedure of information processing (part 1) executed by the payment server 100 according to the embodiment will be described with reference to FIG. 8. FIG. 8 is a flowchart showing an example of a processing procedure of information processing (part 1) executed by the payment server 100 according to the embodiment. Note that the processing procedure shown in FIG. 8 is executed by the control unit 130 included in the payment server 100. The control unit 130 repeatedly executes the processing procedure shown in FIG. 8 while the payment server 100 is operating.

[0092] As shown in FIG. 8, the acquisition unit 131 receives a display request for an application screen corresponding to the "deferred payment" function from a user of the electronic payment service through the communication unit 110 (step S101).

[0093] The acquisition unit 131 transmits a request to acquire billing status information of the target user who is the sender of the request to display the application screen to the credit card server 200 via the communication unit 110 (Step S102).

[0094] The acquiring unit 131 acquires the billing status information of the target user transmitted from the credit card server 200 via the communication unit 110 (step S103).

[0095] The provision unit 132 provides the target user with an app screen reflecting the billing status of the postpaid usage fee corresponding to the target user based on the billing status information acquired by the acquisition unit 131 (step S104), and terminates the processing procedure shown in Figure 8.

[0096] (3-2. Information processing by the payment server 100 (part 2)) Hereinafter, an example of the processing procedure of the information processing (part 2) executed by the payment server 100 according to the embodiment will be described with reference to Fig. 9. Fig. 9 is a flowchart showing an example of the processing procedure of the information processing (part 2) executed by the payment server 100 according to the embodiment. The processing procedure shown in Fig. 9 is executed by the control unit 130 included in the payment server 100. The control unit 130 repeatedly executes the processing procedure shown in Fig. 9 while the payment server 100 is operating.

[0097] As shown in FIG. 9, the acquisition unit 131 receives a request from a user of the electronic payment service through the communication unit 110 to display an application screen corresponding to a change acceptance function for accepting changes to the payment method, etc., of the postpaid usage fee (step S201).

[0098] The acquisition unit 131 transmits a request to acquire billing status information of the target user who is the sender of the request to display the application screen to the credit card server 200 via the communication unit 110 (Step S202).

[0099] Acquisition unit 131 acquires the billing status information of the target user transmitted from credit card server 200 via communication unit 110 (step S203).

[0100] The providing unit 132 selects a payment method selectable by the target user according to the billing status of the postpaid service charge corresponding to the target user based on the billing status information acquired by the acquiring unit 131 (step S204).

[0101] The providing unit 132 provides the target user with an application screen presenting a payment method and the like according to the billing status of the postpaid service charge corresponding to the target user (step S205), and ends the processing procedure shown in FIG.

[0102] 4. Modifications In the above embodiment, an example has been described in which the information processing system SYS according to the embodiment is configured to include the payment server 100 and the credit card server 200, but the information processing system SYS does not need to be particularly limited to such an example. For example, the payment server 100 and the credit card server 200 may be a single server that is functionally or physically integrated. In addition, a part of the processing function of the control unit 130 of the payment server 100 may be distributed to the credit card server 200.

[0103] In addition, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, and conversely, all 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.

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

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

[0106] 5. Effects As described above, the payment server 100 of the information processing system SYS according to the embodiment is an information processing device that executes processing related to an electronic payment service that allows a user to select a deferred payment method as a payment method for a price of a transaction object when using code payment using predetermined code information, and includes an acquisition unit 131 and a provision unit 132. The acquisition unit 131 is a screen of a payment application provided to a service user UA who is a user of an electronic payment service to use code payment, and when a display request for an application screen G-1 (an example of a "first screen corresponding to a deferred payment method") is received from the service user UA, the acquisition unit 131 acquires billing status information indicating the billing status of the deferred payment usage fee corresponding to the service user UA (an example of a "target user") who is the sender of the display request, from a credit card server 200 (an example of an "other device") managed by a service provider UC that operates a payment service that is another service linked with the electronic payment service and provides the service user UA with credit card payment (an example of a "deferred payment method") through the electronic payment service. The provision unit 132 provides screen information for displaying an app screen G-1 reflecting the billing status corresponding to the target user (e.g., service user UA) based on the billing status information acquired by the acquisition unit 131 to the target user by transmitting the screen information to the user terminal 10 via the communication unit 110.

[0107] In this way, the payment server 100 of the information processing system SYS according to the embodiment can make the service user UA aware of the payment status of the deferred payment usage fee, which is the usage fee of the code payment made by selecting the deferred payment method of "deferred payment" or "credit card payment". As a result, in the information processing system SYS according to the embodiment, the payment server 100 can improve the usability of deferred cashless payment.

[0108] The providing unit 132 may provide screen information including image information showing the billing status. This allows the payment server 100 to allow the target user to easily recognize the payment status of the deferred payment service fee.

[0109] The providing unit 132 may provide screen information including image information indicating the billing status of the deferred payment usage fee, such as provisional confirmation, confirmation, payment confirmation in progress, payment completed, or unpaid. This allows the settlement server 100 to allow the target user to easily recognize the payment status of the deferred payment usage fee at each stage.

[0110] The providing unit 132 may also provide the target user with screen information for displaying an application screen G-3 (an example of a "second screen") that presents the target user with payment methods for the deferred payment service charge that can be selected by the target user depending on the billing status and accepts a change in the payment method. This allows the settlement server 100 to allow the target user to easily confirm and change the payment methods that can be selected depending on the billing status of the deferred payment service charge, thereby improving usability.

[0111] In addition, when the billing status is unpaid, the providing unit 132 may provide the target user with screen information for displaying the application screen G-2 (an example of the "third screen") on which the payment method and expected date of payment of the deferred payment charge can be received from the target user. This allows the settlement server 100 to smoothly execute the repayment procedure for the deferred payment charge of the target user, thereby improving usability.

[0112] [6. Hardware Configuration] The payment server 100 according to the above-described embodiment or modification is realized, for example, by a computer 1000 having a configuration as shown in Fig. 10. Fig. 10 is a hardware configuration diagram showing an example of a computer that realizes the functions of the payment server 100 constituting the information processing system according to the embodiment or modification.

[0113] The computer 1000 is connected to an output device 1010 and an input device 1020, and has a configuration in which an arithmetic unit 1030, a primary storage device 1040, a secondary storage device 1050, an output IF (Interface) 1060, an input IF 1070, and a network IF 1080 are connected via a bus 1090.

[0114] The arithmetic device 1030 operates based on programs stored in the primary storage device 1040 and the secondary storage device 1050 and programs read from the input device 1020, and executes various processes. The primary storage device 1040 is a memory device, such as a RAM, that temporarily stores data used by the arithmetic device 1030 for various calculations. The secondary storage device 1050 is a storage device in which data used by the arithmetic device 1030 for various calculations and various databases are registered, and is realized by a ROM (Read Only Memory), HDD, flash memory, etc.

[0115] The output IF 1060 is an interface for transmitting information to be output to an output device 1010 that outputs various types of information, such as a monitor or a printer, and is realized by a connector conforming to a standard such as USB (Universal Serial Bus), DVI (Digital Visual Interface), or HDMI (High Definition Multimedia Interface), a registered trademark. The input IF 1070 is an interface for receiving information from various input devices 1020, such as a mouse, keyboard, and scanner, and is realized by a USB, for example.

[0116] The input device 1020 may be a device that reads information from an optical recording medium such as a CD (Compact Disc), a DVD (Digital Versatile Disc), or a PD (Phase change rewritable Disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. The input device 1020 may also be an external storage medium such as a USB memory.

[0117] The network IF 1080 receives data from other devices via the network N and sends it to the arithmetic device 1030, and also transmits data generated by the arithmetic device 1030 to other devices via the network N.

[0118] The arithmetic unit 1030 controls the output device 1010 and the input device 1020 via the output IF 1060 and the input IF 1070. For example, the arithmetic unit 1030 loads a program from the input device 1020 or the secondary storage device 1050 onto the primary storage device 1040 and executes the loaded program.

[0119] For example, when the computer 1000 functions as the payment server 100 according to the embodiment or the modification, the arithmetic device 1030 of the computer 1000 executes a program (e.g., an information processing program) loaded onto the primary storage device 1040 to realize a function similar to that of the control unit 130. That is, the arithmetic device 1030 cooperates with the program (e.g., an information processing program) loaded onto the primary storage device 1040 to realize the processing by the payment server 100 according to the embodiment or the modification.

[0120] [7. Other] Although some of the embodiments of the present application have been described in detail above with reference to the drawings, these are merely examples, and the present invention can be embodied in other forms that incorporate various modifications and improvements based on the knowledge of those skilled in the art, including the forms described in the Disclosure of the Invention section.

[0121] Further, the above-mentioned payment server 100 and credit card server 200 can be flexibly changed in configuration, for example, by calling an external platform or the like using an API (Application Programming Interface) or network computing, depending on the function.

[0122] Furthermore, the term "unit" in the claims may be read as "means" or "circuit," etc. For example, a control unit may be read as control means or a control circuit. [Explanation of symbols]

[0123] SYS Information Processing System 10 User terminal 100 Payment Server 110 Communications Department 120 Storage section 121 User information storage unit 122 Payment method selection information storage unit 130 Control section 131 Acquisition Department 132 Provision Department 200 Credit Card Server

Claims

1. An information processing device that executes a process related to an electronic payment service that allows a user to select a deferred payment method as a payment method for a price of a transaction object when using a code settlement using predetermined code information, an acquisition unit which, when a display request for a first screen corresponding to the deferred payment method is received from the user, acquires billing status information indicating the billing status of the deferred payment fee corresponding to the target user who is the sender of the display request from another device managed by a business that operates another service linked to the electronic payment service and that provides the deferred payment method to the user through the electronic payment service; a providing unit that provides screen information for displaying the first screen that reflects the billing status corresponding to the target user based on the billing status information acquired by the acquiring unit, to the target user; 13. An information processing device comprising:

2. The providing unit is The screen information including image information showing the claim status is provided.

2. The information processing apparatus according to claim 1,

3. The providing unit is The screen information including the image information indicating, as the billing status, whether the deferred payment usage fee is provisionally confirmed, confirmed, payment is being confirmed, paid, or unpaid is provided.

3. The information processing apparatus according to claim 2.

4. The providing unit is presenting to the target user a payment method for the deferred payment service charge that can be selected by the target user according to the billing status, and providing screen information for displaying a second screen that can accept a change to the payment method; The information processing device according to claim 1 .

5. The providing unit is If the billing status is unpaid, screen information is provided for displaying a third screen on which the payment method and expected payment date of the deferred payment charge can be received from the target user. The information processing device according to claim 4.

6. An information processing method executed by a computer that executes a process related to an electronic payment service that allows a user to select a deferred payment method as a payment method for a price of a transaction object when using a code settlement using predetermined code information, comprising: an acquisition step of acquiring, when a display request for a first screen corresponding to the deferred payment method is received from a user of the electronic payment service in order to use the code payment, billing status information indicating the billing status of the deferred payment usage fee corresponding to the target user who is the sender of the display request from another device managed by a business that operates another service linked to the electronic payment service and that provides the deferred payment method to the user through the electronic payment service; a providing step of providing screen information for displaying the first screen reflecting the billing status corresponding to the target user, based on the billing status information acquired by the acquiring step, to the target user; 13. An information processing method comprising:

7. In the case of using code settlement using predetermined code information, a computer that executes a process related to an electronic settlement service that allows a deferred payment method to be selected as a payment method for the price of a transaction, an acquisition step of acquiring billing status information indicating the billing status of the deferred payment usage fee corresponding to the target user who is the sender of the display request from another device managed by a business that operates a payment service that provides the deferred payment method to the user through the electronic payment service, the billing status information being a screen of a payment application provided to a user of the electronic payment service to use the code payment, when a display request for a first screen corresponding to the deferred payment method is received from the user; a providing step of providing screen information for displaying the first screen reflecting the billing status corresponding to the target user, based on the billing status information acquired by the acquiring step, to the target user; An information processing program characterized by causing the program to execute the above steps.

Images