JP7370489B1 - Information processing system, information processing device, and information processing method - Google Patents

Abstract

[Problem] To improve the usability of deferred payment type cashless payments. [Solution] An information processing device according to the present application is an information processing system that executes processing related to billing a credit card usage fee calculated by totaling the usage amount every predetermined period, and includes a reception unit and a postponement processing unit. and has. The reception unit accepts a postponement request from a credit card user requesting a postponement of the billing date for billing the usage fee. The deferral processing unit executes deferral processing to postpone the billing date when the deferral request is accepted by the receiving unit. [Selection diagram] Figure 4

Description

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

Conventionally, cashless payment methods have been widely recognized by consumers, mainly for commercial transactions between businesses and individuals, but due to their convenience, they are becoming increasingly popular online using user terminals such as smartphones owned by individuals. Electronic payment services have become widespread among consumers.

Furthermore, with regard to so-called deferred payment type cashless payments such as credit cards, technologies have been proposed that take into account changes that postpone the payment date of the credit card usage fee set by the customer.

JP 2019-3249 Publication

However, with the above-mentioned conventional technology, there is still room for improving the usability of deferred payment type cashless payments. For example, fees for deferred payment type cashless payments such as credit cards are usually repaid on a predetermined billing date. However, if the usage amount becomes high due to sudden expenses, etc., there is a considerable desire by some users to reduce the repayment amount. On the other hand, one of the repayment methods proposed by credit card companies is revolving payment, but the mechanism may be complicated and fees may be incurred over a long period of time, so it is not necessarily convenient for users. There are aspects that I can't say.

The present application was made in view of the above, and aims to provide an information processing system, an information processing device, and an information processing method that can improve usability regarding deferred payment type cashless payments. do.

The information processing system according to the present application is an information processing system that executes processing related to billing a credit card usage fee calculated by totaling the usage amount every predetermined period, and includes a reception unit and a postponement processing unit. . The reception unit accepts a postponement request from a credit card user requesting a postponement of the billing date for billing the usage fee. The deferral processing unit executes deferral processing to postpone the billing date when the deferral request is accepted by the reception unit.

According to one aspect of the embodiment, it is possible to improve the usability of deferred payment type cashless payment.

FIG. 1 is a diagram for explaining an overview of billing date postponement processing according to an embodiment. FIG. 2 is a diagram showing an example (part 1) of screen transitions in the user terminal according to the embodiment. FIG. 3 is a diagram showing an example (part 2) of screen transitions in the user terminal according to the embodiment. FIG. 4 is a diagram illustrating an example of the device configuration of the information processing system according to the embodiment. FIG. 5 is a diagram illustrating an example of user information stored in the user information storage unit according to the embodiment. FIG. 6 is a diagram illustrating an example of balance information stored in the balance information storage unit according to the embodiment. FIG. 7 is a diagram illustrating an example of fee information stored in the fee information storage unit according to the embodiment. FIG. 8 is a diagram illustrating an example of sales information stored in the sales information storage unit according to the embodiment. FIG. 9 is a diagram illustrating an example of billing information stored in the billing information storage unit according to the embodiment. FIG. 10 is a sequence diagram illustrating an example of an information processing procedure executed by the information processing system according to the embodiment. FIG. 11 is a hardware configuration diagram illustrating an example of a computer that implements the functions of a payment server and a credit card server that constitute an information processing system according to an embodiment or a modified example.

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

[1. Embodiment]
(1-1. System configuration)
Information processing according to the embodiment will be specifically described below. First, prior to explaining the information processing according to the embodiment, an example of the configuration of the information processing system SYS will be explained with reference to FIG.

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, for example, FIG. 4) 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.

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 that operates and manages the payment server 100. The user terminal 10 is realized by, for example, a smartphone, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, a mobile phone, a PDA (Personal Digital Assistant), or the like. Further, the user terminal 10 displays information distributed by the payment server 100 using a web browser or an application. Note that FIG. 1 illustrates a case where the user terminal 10 is a smartphone.

The user terminal 10 also has an application program for the user to use code payment (also referred to as "smartphone payment") provided to the service user UA as a cashless payment method by the electronic payment service. (hereinafter referred to as the "payment application" as appropriate) is installed. When the user terminal 10 receives control information for implementing predetermined information processing through the payment application from the payment server 100, it implements the information processing according to the control information. Here, the control information may be 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 language such as HTML (HyperText Markup Language). It is written in markup language etc. Note that the predetermined application itself distributed from the payment server 100 may be regarded as the control information.

The payment server 100 shown in FIG. 1 is an information processing device operated and managed by a business that provides electronic payment services. For example, as described below, electronic payment services utilize code payments that allow users to instantly settle the transaction price using their money balance, which is the balance of electronic money held by the user, using predetermined code information. This is a service that provides an environment to service users as one of the cashless payment methods (it can also be said to be a service that provides a predetermined transaction method that controls the exchange of electronic money by code payment).

Further, the payment server 100 may be realized by a mainframe, a workstation, or the like. In addition, when the payment server 100 is composed of 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 work together. good.

Further, the payment server 100 works in conjunction with a payment application running on the user terminal 10 to execute various processes related to electronic payment services provided through a dedicated online system, for example. For example, the payment server 100 distributes a 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 receives a transaction request from a 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), the payment server 100 handles the transaction. In accordance with requests, information processing including electronic money transfer processing between accounts is executed. The payment application transmits transaction information including information such as a payment destination, a payment source, and a payment amount to the payment server 100. In addition to the above-mentioned information, transaction information includes information such as a transaction code to identify each transaction and date and time information (i.e., timestamp) to identify the date and time the transaction was performed. It may be

In addition, as one of the services incidental to the electronic payment service, the payment server 100 allows users to pay for transactions in arrears using a credit card registered in advance using predetermined code information. Provide service users with an environment for cashless payments. Further, as will be described later, the payment server 100 cooperates with the credit card server 200 to execute various processes related to deferred cashless payment using a cash card as information processing according to the embodiment.

The credit card server 200 is an information processing device operated and managed by a business that provides credit card services. The credit card server 200 executes processing related to payments made by the service user UA using a credit card. For example, the credit card server 200 calculates the credit card usage fee by totaling the credit card usage amount of each user (for example, service user UA shown in FIG. 1) for each predetermined period. Executes processing related to billing usage fees. As an example, the predetermined period is assumed to be one month in each month with a deadline at the end of each month. In this case, the credit card server 200 performs the processing related to billing the usage fee by aggregating the credit card usage amount with the end of each month as the deadline, and using the usage fee of the previous month, which is the billing month, on the 27th of the following month. It is assumed that the process will be billed to a person.

Credit card server 200 may be realized by a mainframe, a workstation, or the like. In addition, when the credit card server 200 is composed of a server device, it may be realized by a single server device, or it may be realized by a cloud system in which multiple server devices and multiple storage devices work together. Good too.

(1-2. Regarding payment using user terminal 10)
Here, an example of code payment using the user terminal 10 will be explained. In the following explanation, for example, a two-dimensional code (QR code (registered trademark)) placed at a predetermined store and indicating store identification information for identifying the predetermined store will be used to identify the predetermined store. An example will be described in which a service user UA, who receives a transaction object from a service provider, makes a payment using the user terminal 10. Note that an example of code payment described below can be applied to a case where any user makes a payment at any store using any user terminal 10. Further, the two-dimensional code indicating store identification information may be not only a QR code but also a bar code, a predetermined mark, a number, etc. Further, the two-dimensional code is not limited to the example of being physically configured by printed matter printed on a medium such as paper, but may be configured by image information displayed on an arbitrary terminal.

For example, when a service user UA makes a payment for purchasing or using a transaction object such as various products or services at a predetermined store, the service user UA starts a payment application preinstalled on the user terminal 10. do. The service user UA then photographs the two-dimensional code installed at a predetermined 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 a predetermined store. Then, the user terminal 10 stores user identification information that identifies the service user UA and store identification information (or information indicated by the store identification information, that is, information indicating a predetermined store (for example, store ID)). , and the payment amount, to the payment server 100.

When the payment server 100 receives transaction information from the user terminal 10, the payment server 100 transfers the amount equivalent to the payment amount from the account of the service user UA indicated by the user identification information to the account of the predetermined store indicated by the store identification information. Transfer electronic money. At this time, the payment server 100 may deduct a predetermined fee charged to a predetermined store from the electronic money equivalent to the payment amount, and then transfer the electronic money to the account of the predetermined store. The payment server 100 then sends a notification to the user terminal 10 that the transaction has been completed. In such a case, the user terminal 10 notifies the service user UA that the transaction using electronic money has been completed by outputting a screen or a predetermined sound indicating that the transaction has been completed. Alternatively, the payment server 100 withdraws electronic money equivalent to the payment amount from the account of the service user UA indicated by the user identification information, manages it as sales information of a predetermined store, and collects electronic money equivalent to the sales at a predetermined timing. The amount of cash may be transferred to a bank account held by a predetermined store. In this case, the payment server 100 may notify the service user UA that the electronic money transaction has been completed at the timing when the electronic money equivalent to the payment amount is withdrawn from the service user UA's account.

Note that payment using the user terminal 10 is not limited to the processing described above. For example, the payment using the user terminal 10 may be made using a terminal device installed at a predetermined store (hereinafter referred to as a "store terminal"). Specifically, first, the user terminal 10 displays on the screen code information indicating user identification information for identifying the service user UA. In such a case, the store terminal reads the user identification information from the code information displayed on the user terminal 10, and stores the read user identification information (or the information indicated by the user identification information, that is, the service user UA). (for example, a user ID)), a payment amount, and information identifying a predetermined store, the transaction information is transmitted to the payment server 100.

Upon receiving the transaction information from the store terminal, the payment server 100 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 a predetermined store. The payment server 100 then sends a notification to the store terminal or user terminal 10 that the transaction has been completed. The store terminal or user terminal 10 notifies the service user UA that the transaction using electronic money has been completed by outputting a screen or a predetermined sound indicating that the transaction has been completed. In addition, the payment server 100 withdraws electronic money equivalent to the payment amount from the account of the service user UA indicated by the user identification information, manages it as sales information of a predetermined store, and collects electronic money equivalent to the sales at a predetermined timing. The amount of cash may be transferred to a bank account held by a predetermined store. In this case, the payment server 100 may notify the clerk or the service user UA that the electronic money transaction has been completed at the timing when the electronic money corresponding to the payment amount is withdrawn from the service user UA's account. good.

In addition, payment using the user terminal 10 is not limited to the process of transferring electronic money from an account in which the service user UA has previously charged electronic money to an account at a predetermined store. Payment may be made using a registered credit card. In such a case, for example, the user terminal 10 transfers the amount of electronic money indicated by the payment amount to a predetermined store account, and also informs the service user UA's credit card management company that the payment amount is You may request the amount indicated.

In addition, the payment using the user terminal 10 is not limited to the process of transferring electronic money from the account of the service user UA to the account of a predetermined store, but also the process of transferring electronic money from the account of the service user UA to the account of another user. It may also be a payment that transfers electronic money to (i.e., remittance between users). For example, the user terminal 10 used by the service user UA who is the remittance source uses user identification information that identifies the remittance destination user (for example, user identification information displayed on the terminal device used by the remittance destination user). ), receives input of the remittance amount from the service user UA, and transmits information indicating the read identification information, the remittance amount, and user identification information identifying the service user UA to the payment server 100. In such a case, the payment server 100 transfers the amount of electronic money indicated by the remittance amount from the account of the service user UA to the account of the remittee user, and the electronic money is transferred to the user terminal 10 or the remittee user's account. The notification that the remittance has been made may be notified by causing the terminal device to output a screen or a predetermined voice indicating that the remittance has been completed.

Note that remittance using the user terminal 10 is not limited to the above-described processing. For example, remittance using the user terminal 10 may be performed by inputting the telephone number of the user to whom the remittance is to be made or information indicating the user to whom the remittance is to be made (e.g., user ID) into the user terminal 10. . To give a specific example, the user terminal 10 receives the input of the telephone number or user ID of the user to whom the remittance is to be made and the remittance amount from the service user UA, and inputs the input telephone number or user ID and the remittance amount. , transmits the remittance amount and user identification information for identifying the service user UA to the payment server 100. Then, the payment server 100 transfers the amount of electronic money indicated by the remittance amount from the service user UA's account to the user's account linked to the transmitted telephone number or user ID.

Here, the telephone number and user ID of the user who is the remittance destination may be registered in advance in the payment application in association with information regarding the user. In this case, the user terminal 10 receives 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 the The telephone number or user ID, the remittance amount, and user identification information for identifying the service user UA are transmitted to the payment server 100.

Further, for example, remittance using the user terminal 10 may be performed by providing link information for receiving the remittance amount to the user of the remittance destination. To give a specific example, the user terminal 10 receives an input of the remittance amount from the service user UA, generates link information for receiving the remittance amount, sends an e-mail containing the link information, or sends an e-mail containing the link information. By posting posted information including the information on SNS (Social Networking Service), link information is provided to the terminal device used by the user of the remittance destination. Then, when the remittance destination user selects the link information and performs a receiving operation, the payment server 100 transfers electronic money in the amount indicated by the remittance amount from the service user UA's account to the remittance destination user's account. to migrate.

Note that the payment means and payment services described above are not limited to those for providing consideration for purchasing products or providing services (settlement of debts). For example, as described above, the payment means or payment service may have a function related to remittance between accounts owned by multiple users. That is, the above-mentioned payment means and payment service may be any service that controls the transmission and reception of electronic money between the accounts of arbitrary owners linked to the owner of electronic money, such as users and stores. In other words, the payment means and payment services according to the embodiments include various controls for realizing electronic money exchange (not only various inter-account remittance controls via electronic money, but also control regarding exchanges between electronic money accounts and bank accounts). Transaction methods and transaction services that carry out various types of debt processing such as control, processing related to splits and bonus payments, and various other controls related to the exchange of assets, including electronic money, may be provided in any format. Good too. Further, the various controls realized by such transaction means and transaction services may include both payment-related control and remittance-related control, or only one of them may be included. That is, the term "transaction" is a concept that includes not only "settlement" related to electronic money, but also "remittance" of electronic money and various other types of processing. That is, the payment server 100 may be an information processing device that implements a transaction means that controls the exchange of electronic money between arbitrary owners.

(1-3. Information processing according to embodiment)
(1-3-1. Overview of billing date postponement processing)
Hereinafter, an overview of information processing according to the embodiment will be described using FIG. 1. FIG. 1 is a diagram for explaining an overview of billing date postponement processing according to an embodiment. Note that in the following description, there are cases where the service user UA and the user terminal 10 can be equated. That is, the service user UA can be read as the user terminal 10.

As a premise of the information processing shown in FIG. 1, the service user UA operates the user terminal 10 to start a payment application. Then, the service user UA uses a function installed in the payment application to perform an operation to request a postponement of the billing date for billing the credit card usage fee using deferred payment. For example, the user terminal 10 operates the payment application in accordance with the operation by the service user UA, and transmits a billing date postponement request to the payment server 100 to postpone the billing date for one month (step S01). Note that the period of postponement of the billing date is not limited to one month, and may be any other period.

Upon receiving the billing date postponement request from the user terminal 10, the payment server 100 determines a predetermined postponement fee according to the usage status of the billing date postponement by the service user UA (step S02). For example, the payment server 100 may determine the postponement fee depending on the number of times the service user UA postpones the billing date in a predetermined target period. Further, for example, the payment server 100 may determine the postponement fee according to the cumulative amount of usage fees for which the service user UA has postponed payment due to postponement of the billing date during a predetermined target period. In addition to the above-mentioned method, the payment server 100 uses information such as an amount obtained by multiplying the usage fee by a predetermined percentage, credit information based on the credit card transaction history of the service user UA, usage history of electronic payment services, etc. The deferral fee may be determined based on the

The payment server 100 also transmits postponement related information regarding the postponement of the billing date to the service user UA (step S03). For example, the payment server 100 transmits postponement-related information to the user terminal 10, including information indicating that a billing date postponement request will be accepted on the condition that a predetermined postponement fee is paid, thereby presenting it to the service user UA. .

The service user UA checks the postponement related information displayed on the user terminal 10, expresses his/her intention to postpone the billing date, and executes an operation to confirm the application for postponement of the billing date. do. For example, the user terminal 10 transmits a billing date postponement instruction to the payment server 100 in accordance with the operation by the service user UA (step S04).

Upon receiving the billing date postponement instruction from the user terminal 10, the payment server 100 executes payment of a predetermined postponement fee corresponding to the service user UA (step S05). For example, the payment server 100 pays a predetermined postponement fee using a payment method specified by the service user UA. When the service user UA specifies payment using a money balance as a payment method for a predetermined postponement fee, the payment server 100 uses the money balance, which is the balance of electronic money held by the service user UA in the electronic payment service, to Settle the prescribed postponement fee. In addition, if the service user UA specifies payment by credit card as the payment method for the predetermined postponement fee, the payment server 100 will pay the predetermined postponement fee using the credit card that the service user UA sets in the electronic payment service. liquidate.

When the payment server 100 completes the payment of the predetermined postponement fee, it transmits a billing date postponement request to the credit card server 200 (step S06). For example, the payment server 100 may credit a billing date postponement request that includes information for identifying the credit card of the service user UA who is the requester of the billing date postponement request, and information for identifying the target of the billing date postponement. Send to card server 200.

Upon receiving the billing date postponement request from the payment server 100, the credit card server 200 executes postponement processing to postpone the billing date based on the received billing date postponement request (step S07). When the payment server 100 receives a response from the credit card server 200 indicating that the postponement of the billing date has been completed, it presents the completion of the postponement of the billing date to the service user UA. For example, the payment server 100 provides the service user UA with information that the billing date has been postponed, as well as information on the scheduled billing date after the postponement, through the payment application.

(1-3-2. Example of screen transition on user terminal 10 (Part 1))
Hereinafter, an example (part 1) of screen transitions in the user terminal 10 according to the embodiment will be described using FIG. 2. FIG. 2 is a diagram showing an example (part 1) of screen transitions in the user terminal 10 according to the embodiment. FIG. 2 shows an example of a screen displayed on the user terminal 10 before the service user UA makes a billing date postponement request.

As shown in FIG. 2, the user terminal 10 displays the top screen G1-1 of the payment application in response to an operation from the service user UA (display example EX1-1). In addition, when the user terminal 10 detects an operation by the service user UA on the "Pay Later" icon OB-1 provided on the top screen G-1, the User Terminal 10 displays the Pay Later screen for executing various processes related to paying later. Display G1-2 (display example EX1-2). The “pay later” icon OB-1 is an object for activating various processing functions related to post-pay that are installed as mini-apps in the payment application.

In addition, the user terminal 10 detects the operation of the service user UA for the item OB-2 of "April 2023 Payment Amount Notice" from the list of notices displayed on the deferred payment screen G1-2. Then, the payment amount details screen G1-3 is displayed (display example EX1-3). The payment amount details screen G1-3 shown in FIG. 2 is provided with a "Skip billing date" icon OB-3. The "Skip billing date" icon OB-3 accepts a postponement request from the service user UA requesting a postponement of the billing date, which is the due date for billing the usage charges, for the total amount of credit card usage charges that are determined every predetermined period. It is provided for. In FIG. 2, when the service user UA operates the "Skip billing date" icon OB-3, a request is made to postpone the billing date for the total amount of credit card usage charges in April 2023.

In addition, when the user terminal 10 detects an operation by the service user UA on item OB-4 indicating transaction information at "A Mart Ginza Ten" from among the credit card usage details for April 2023, the user terminal 10 displays the transaction details screen. Display G1-4 (display example EX1-4). The transaction details screen G1-4 shown in FIG. 2 is provided with a "Skip billing date" icon OB-5. The "Skip billing date" icon OB-5 is a transaction unit that constitutes the credit card usage fee that is determined every predetermined period, and is a postponement request that requests the postponement of the billing date, which is the billing date on which the usage fee is billed. It is provided to receive the information from the service user UA. In Figure 2, when the "Skip billing date" icon OB-5 is operated by the service user UA, out of the credit card usage charges in April 2023, the amount corresponding to the transaction at "A Mart Ginza Ten" is "1". , 439 yen", an individual request is made to postpone the billing date.

Further, the payment server 100 may accept a request to postpone the billing date until the credit card usage fee is determined. In this case, the "bill date skip" icons OB-3 and OB-5 shown in FIG. 2 are displayed on the user terminal 10 until the credit card usage fee is determined.

(1-3-3. Example of screen transition on user terminal 10 (Part 2))
Hereinafter, an example (part 2) of screen transitions in the user terminal 10 according to the embodiment will be described using FIG. 3. FIG. 3 is a diagram showing an example (part 2) of screen transitions in the user terminal 10 according to the embodiment. FIG. 3 shows an example of a screen displayed on the user terminal 10 after the service user UA makes a request for postponement of the billing date and before the application for the request for postponement of the billing date is finalized.

As shown in FIG. 3, when the user terminal 10 detects the service user UA's operation on the "Skip billing date" icon OB-5 on the transaction details screen G1-4 (display example EX1-4), Display the postponement procedure screen G1-5 (display example EX1-5). The postponement procedure screen G1-5 displays information to the effect that the postponement request will be accepted on the condition that a predetermined postponement fee is paid. For example, in the example shown in FIG. 3, information indicating the current scheduled billing date and information indicating the scheduled billing date if postponed are displayed. Further, in the example shown in FIG. 3, information on a predetermined postponement fee required for accepting a postponement request is displayed. In addition, the postponement procedure screen G1-5 shown in Figure 3 includes a check box OB-6 for accepting an expression of intention from the service user UA to postpone the billing date, and an application for postponing the billing date. An application icon OB-7 is provided for accepting an operation from the service user UA to confirm the application. Note that the application icon OB-7 may be controlled so that the operation becomes valid when the check box OB-6 is checked.

Furthermore, when the service user UA's operation on the application icon OB-7 is detected on the postponement procedure screen G1-5, the user terminal 10 redisplays the transaction details screen G1-4 with some information changed. (Display example EX1-6). For example, in the example shown in FIG. 3, the display of the "Skip billing date" icon OB-5 is changed, and the information on the payment month is changed to the scheduled billing date after the postponement.

As described above, according to the information processing system SYS according to the embodiment, the billing date for credit card usage fees is postponed, for example, by one month in response to a request from the service user UA. As a result, the information processing system SYS according to the embodiment can provide a clear and easy-to-use reduction scheme for the service user UA by simply extending the billing date by one month, and is able to provide a clear and easy-to-use reduction scheme for deferred payment type cashless payments. , usability can be improved.

[2. Device configuration〕
(2-1. Configuration of payment server 100)
Hereinafter, the device configuration of the information processing system SYS according to the embodiment will be described using FIG. 4. FIG. 4 is a diagram showing an example of the device configuration of the information processing system SYS according to the embodiment. First, an example of the 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. 4. As shown in FIG. 4, payment server 100 includes a communication section 110, a storage section 120, and a control section 130.

(About communication department 110)
The communication unit 110 is realized by, for example, a NIC (Network Interface Card). The communication unit 110 is connected to the network N by wire or wirelessly, and transmits and receives information to and from other devices such as the user terminal 10 and the credit card server 200.

(About storage unit 120)
The storage unit 120 is realized by, for example, a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. As shown in FIG. 4, the storage unit 120 includes a user information storage unit 121, a balance information storage unit 122, and a fee information storage unit 123.

(About user information storage unit 121)
The user information storage unit 121 stores user information regarding users of the electronic payment service. FIG. 5 is a diagram showing an example of user information stored in the user information storage unit 121 according to the embodiment.

As shown in FIG. 5, the user information stored in the user information storage unit 121 includes items such as "user ID", "transaction history", "registered card information", and "debit card information". It has multiple items such as ``account information'', ``deferral fee payment method'', and ``deferral usage status''. These items included in the user information are associated with each other.

The "User ID" item contains unique identification information that is individually assigned to each user in order to uniquely identify the user of the electronic payment service (for example, service user UA shown in Figure 1). A user ID is stored.

The "transaction history" item stores information indicating the transaction history using deferred payment. The transaction history may include information such as the date of use, the user, the payment category, the commission, the total payment amount, the payment amount, the month of payment, and the balance carried over from the next month.

The "registered card information" item stores information regarding the credit card that the service user has registered as a credit card used for deferred payment. The registered card information may include information such as the card name, expiration date, and card number.

The item "Debit account information" stores information for specifying the bank account registered by the service user as a withdrawal account for paying the credit card usage fee. The information for identifying the bank account may include information such as the bank name, branch name, account name, and account number.

The "Postponement Fee Payment Method" item stores information indicating the payment method registered by the service user as the payment method for the specified postponement fee that must be paid when the billing date is postponed. Ru. For example, payment methods available to service users include payment using a money balance, which is the balance of electronic money held by the user as a payment source for code payments provided by electronic payment services, and payment using a credit card for deferred payment. etc. are assumed.

The item "postponed usage status" stores information indicating the usage status of postponing the billing date for usage fees using deferred payment. The usage status is assumed to include the number of times usage fees have been postponed in a predetermined target period, the cumulative amount of usage fees whose payment has been postponed due to postponement of the billing date in a predetermined target period, and the like.

(About balance information storage unit 122)
The balance information storage unit 122 stores balance information indicating a money balance held by a user (for example, the service user UA shown in FIG. 1). FIG. 6 is a diagram illustrating an example of balance information stored in the balance information storage unit 122 according to the embodiment.

As shown in FIG. 6, the balance information stored in the balance information storage unit 122 includes a plurality of items such as a "user ID" item and a "money balance" item. These items included in the balance information are correlated with each other.

The "User ID" item contains unique identification information that is individually assigned to each user in order to uniquely identify the user of the electronic payment service (for example, service user UA shown in Figure 1). A user ID is stored.

The "money balance" item stores information indicating the money balance, which is the balance of electronic money held by the user as a payment source for code payments provided by the electronic payment service.

(Regarding the fee information storage unit 123)
The fee information storage unit 123 stores fee information regarding a predetermined postponement fee corresponding to the usage status of postponing the billing date for billing the credit card usage fee. FIG. 7 is a diagram showing an example of fee information stored in the fee information storage unit 123 according to the embodiment.

As shown in FIG. 7, the fee information stored in the fee information storage unit 123 includes an item of "usage status" and an item of "fee amount." These items included in the fee information are associated with each other.

The item "usage status" stores information for specifying the usage status of postponing the billing date. For example, the usage status includes the number of times the billing date was postponed during a specified target period, or the amount of usage charges that were deferred due to a postponement of the billing date during a specified target period by a user who used deferred payment of usage charges. It is assumed that the cumulative amount of

The "fee amount" item stores information indicating a predefined fee depending on usage status. For example, the fee may be arbitrarily determined by a business providing an electronic payment service or a business providing a credit card service.

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

As shown in FIG. 4, the control unit 130 includes a reception unit 131, a determination unit 132, and a payment processing unit 133, and each of these units realizes or executes information processing functions and operations described below. do. Note that a new functional unit different from each unit shown in FIG. 4 may be introduced into the control unit 130 depending on expansion of various processes executed by the payment server 100.

(About reception department 131)
The accepting unit 131 accepts a postponement request from a credit card user requesting a postponement of the billing date for billing the usage fee.

For example, the reception unit 131 may accept a request for postponement of the total amount of usage fees determined for each predetermined period. For example, the reception unit 131 may accept the postponement request in units of transactions that constitute the usage fee that is determined every predetermined period.

Further, for example, the reception unit 131 may accept a request to postpone the billing date for billing the credit card usage fee until the usage fee is determined.

For example, the reception unit 131 may send a request to a user (for example, a service user shown in FIG. UA, etc.) may be notified.

For example, the reception unit 131 may send a request to a user (for example, service user UA shown in FIG. ) may be notified.

Further, for example, the reception unit 131 may use a first application (for example, A second application (for example, a "pay later" mini-app) that operates on a terminal device used by the user (for example, the user terminal 10 shown in FIG. 1), which is a program that operates using a payment supplement (payment supplement) as a platform. A request for postponement of billing the credit card usage fee may be accepted through the website.

Note that the reception unit 131 may receive sales data related to credit card payments transmitted from the credit card server 200. The reception unit 131 reflects the sales data received from the credit card server 200 in the transaction history included in the user information of the corresponding user.

Further, upon receiving a response indicating that the postponement of the billing date has been completed from the credit card server 200 through the communication unit 110, the reception unit 131 may present the completion of postponement of the billing date to the service user UA. For example, the reception unit 131 provides the service user UA with information that the billing date has been postponed and information on the scheduled billing date after the postponement to the user terminal 10 via the communication unit 110.

(About the determining unit 132)
The determining unit 132 determines a predetermined postponement fee depending on the usage status of the postponement of the billing date when the credit card usage fee is billed.

(About payment processing unit 133)
When there is an application for postponement of the billing date for billing the credit card usage fee, the payment processing unit 133 uses the payment method registered by the user who made the application (for example, the service user UA shown in FIG. 1). Accordingly, the prescribed postponement fee will be settled. When the payment of the predetermined postponement fee is completed, the payment processing unit 133 transmits a request to postpone the billing date to the credit card server 200 through the communication unit 110.

(2-2. Configuration of credit card server 200)
Next, an example of the functional configuration of the credit card server 200 included in the information processing system SYS according to the embodiment will be described with reference to FIG. 4. As shown in FIG. 4, credit card server 200 includes a communication section 210, a storage section 220, and a control section 230.

(About communication department 210)
The communication unit 210 is realized by, for example, a NIC (Network Interface Card). The communication unit 210 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 payment server 100.

(About storage unit 220)
The storage unit 220 is realized by, for example, a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. As shown in FIG. 8, the storage unit 220 includes a sales information storage unit 221 and a billing information storage unit 222.

(About sales information storage unit 221)
The sales information storage unit 221 stores credit card sales information. FIG. 8 is a diagram showing an example of sales information stored in the sales information storage unit 221 according to the embodiment.

As shown in FIG. 8, the sales information stored in the sales information storage unit 221 includes a plurality of items such as a "sales ID" item and a "sales information" item. These items included in the sales information are associated with each other.

The item "Sales ID" stores a sales ID, which is identification information individually assigned to each piece of sales information in order to identify the sales information.

Credit card sales information is stored in the "sales information" item. For example, the sales information may include information such as the usage date (payment date), the user, the usage store (affiliated store), the usage amount (payment amount), and the card number.

(Regarding billing information storage unit 222)
The billing information storage unit 222 stores credit card billing information. FIG. 9 is a diagram showing an example of billing information stored in the billing information storage unit 222 according to the embodiment.

As shown in FIG. 9, the billing information stored in the billing information storage unit 222 includes items such as "Billing ID", "Billing party", "Usage details", "Usage amount", etc. , it has multiple items such as "billing date", "debit account information", and "postponement target". These items included in the billing information are associated with each other.

The "Billing ID" item stores a billing ID, which is identification information individually assigned to each piece of billing information in order to identify the billing information.

The "Billing Party" item stores information for specifying the billing party. For example, the information for identifying the billing party may include user information, card number information, and the like. The item "Usage Details" stores information indicating the details of credit card usage during a predetermined period. Information indicating the total amount of credit card usage for a predetermined period is stored in the item "Used amount". In the item "billing date", information indicating the billing date of the credit card usage fee is stored. The item "Debit account information" stores information regarding the account from which the credit card usage fee is debited. The item "postponement target" stores information indicating the subject of postponement of the billing date. For example, the total amount of usage fees and usage amounts corresponding to individual transactions that make up the usage fees are assumed to be subject to postponement.

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

As shown in FIG. 4, the control unit 230 includes a sales transmission unit 231 and a postponement processing unit 232, and these units realize or execute information processing functions and operations described below. Note that a new functional unit different from each unit shown in FIG. 4 may be introduced into the control unit 230 depending on expansion of various processes executed by the credit card server 200.

(About sales transmission department 231)
Upon acquiring sales information from a credit card affiliated store, the sales transmission unit 231 transmits the acquired sales information to the payment server 100 through the communication unit 210.

(About the postponement processing unit 232)
When the payment server 100 accepts a request to postpone the billing date, the postponement processing unit 232 executes postponement processing to postpone the billing date. For example, the postponement processing unit 232 executes postponement processing to postpone the billing date (billing date) to one month later.

Furthermore, the deferral processing unit 232 executes the process of deferring the billing date on the condition that the user (for example, the service user UA shown in FIG. 1) consents to payment of a predetermined deferral fee.

Further, the deferral processing unit 232 may perform the following actions on the condition that the user (for example, the service user UA shown in FIG. 1) consents to the payment of a predetermined deferral fee corresponding to the usage status of deferring the billing date. Execute the billing date postponement process.

Further, the postponement processing unit 232 operates on a second application (for example, " Postponement of the billing date is executed on the condition that the user's consent to pay a predetermined postponement fee is obtained through the "Pay later" mini app).

[3. Processing procedure example]
The flow of information processing executed by the information processing system SYS according to the embodiment will be described below with reference to FIG. FIG. 10 is a sequence diagram illustrating an example of an information processing procedure executed by the information processing system SYS according to the embodiment. Note that in the processing procedure shown in FIG. 10, the processing corresponding to the payment server 100 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. 10 while the payment server 100 is in operation. In the processing procedure shown in FIG. 10, the processing corresponding to the credit card server 200 is executed by the control unit 230 included in the credit card server 200. The control unit 230 repeatedly executes the processing procedure shown in FIG. 10 while the credit card server 200 is in operation.

As shown in FIG. 10, the service user UA operates the user terminal 10 and executes a credit card payment for purchasing goods or applying for service at a member store that has introduced the electronic payment service (step S101). ).

When a member store (e.g., a store terminal installed at the member store) receives a payment related to a product purchase or a service usage application, the member store (for example, a store terminal installed at the member store) issues an authorization (e.g., online payment processing regarding credit card payment) with the credit card server 200 through the acquirer. process) is executed (step S102).

Further, when the authorization is successfully completed, the member store provides goods or services to the service user UA (step S103).

In addition, the member store (for example, a store terminal installed at the member store) transmits sales data related to the credit card of the service user UA to the credit card server 200 through batch processing scheduled at a predetermined timing through the acquirer. (Step S104).

The sales transmission unit 231 of the credit card server 200 transmits the sales data provided by the affiliated store to the payment server 100 (step S105).

Upon receiving the sales data from the credit card server 200, the reception unit 131 of the payment server 100 reflects the received sales data in the transaction history included in the user information of the corresponding user (step S106).

In addition, the service user UA checks the transaction history displayed on the payment application at any time and requests, through the payment application, a postponement of the billing date for billing the credit card usage fee (step S201). . For example, the user terminal 10 can display the "Skip billing date" icon OB-3 (see Figure 2) provided on the payment details screen G1-3, or the "Skip billing date" icon provided on the transaction details screen G1-4. When detecting an operation by the service user UA on the "Skip" icon OB-5, a request to postpone the billing date to one month later is sent to the payment server 100.

When the payment server 100 receives a request for postponement of the billing date, it determines a predetermined postponement fee, and presents the determined fee amount of the predetermined postponement fee and the billing date after the postponement to the service user UA through the payment application. (Step S202). For example, the payment server 100 transmits information indicating the amount of a predetermined postponement fee and the billing date after the postponement to the user terminal 10 displayed on the payment application, and sends the information to the user terminal 10 displayed on the payment application. Through the postponement procedure screen G1-5 (see FIG. 3), the amount of the predetermined postponement fee and the billing date after the postponement are presented to the service user UA.

The service user UA also confirms the amount of the predetermined postponement fee and the billing date after the postponement, and applies for postponement of the billing date. For example, when the user terminal 10 detects an operation by the service user UA on the application icon OB-7 displayed on the postponement procedure screen G1-5 (see FIG. 3) of the payment application, the user terminal 10 sends the billing date postponement instruction to the payment application. It is transmitted to the server 100 (step S203).

When the payment processing unit 133 of the payment server 100 receives an instruction to confirm the postponement of the billing date from the service user UA, it executes payment of a predetermined postponement fee (step S204). Further, the payment processing unit 133 of the payment server 100 transmits a request to postpone the billing date to the credit card server 200 (step S205).

When the postponement processing unit 232 of the credit card server 200 receives the billing date postponement request from the payment server 100, it executes the billing date postponement process (step S206), and responds that the billing date postponement process is completed. is sent to the payment server 100 (step S207).

Upon receiving a response from the credit card server 200 indicating that the postponement of the billing date has been completed, the receiving unit 131 of the payment server 100 presents the completion of postponement of the billing date to the service user UA (step S208). For example, the payment server 100 displays the transaction details screen G1-4 (see FIG. 3) on the user terminal 10, displaying the "Skip billing date" icon OB-5 and changing the payment month information to the scheduled billing date after the postponement. The information is presented to the service user UA by displaying it on the screen.

[4. Modified example]
In the embodiments described above, the information processing system SYS according to the embodiments has been described as an example configured to include the payment server 100 and the credit card server 200, but there is no need to be particularly limited to such an example. . For example, payment server 100 and credit card server 200 may be a single server that is functionally or physically integrated. In this case, for example, the control unit 130 of the payment server 100 may have the processing function of the postponement processing unit 232 included in the credit card server 200 as the processing function according to the embodiment.

Further, 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, the processes described as being performed automatically can be performed manually. All or part of the processing can also be performed automatically using known methods. In addition, information including the processing procedures, specific names, and various data and parameters shown in the above documents and drawings may be changed arbitrarily, unless otherwise specified. For example, the various information shown in each figure is not limited to the illustrated information.

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

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

[5. effect〕
As described above, the information processing system SYS according to the embodiment is a computer system that executes processing related to billing a credit card usage fee calculated by summing up the usage amount every predetermined period, and includes the reception unit 131 and the information processing system SYS. , and a postponement processing section 232. The accepting unit 131 accepts a postponement request from a credit card user requesting a postponement of the billing date for billing the usage fee. When the reception unit 131 accepts the postponement request, the postponement processing unit 232 executes postponement processing to postpone the billing date.

In this way, the information processing system SYS according to the embodiment can provide a clear and easy-to-use reduction scheme for the service user UA by simply extending the billing date by one month, for example, and can provide a deferred payment type discount scheme. Usability can be improved for cashless payments.

Further, the accepting unit 131 may accept the postponement request regarding the total amount of usage fees determined for each predetermined period. Thereby, the information processing system SYS according to the embodiment can flexibly respond to individual requests of users of the electronic payment service (for example, the service user UA shown in FIG. 1).

Further, the accepting unit 131 may accept the postponement request in units of transactions that constitute the usage fee that is determined every predetermined period. Thereby, the information processing system SYS according to the embodiment can flexibly respond to individual requests of users of the electronic payment service (for example, the service user UA shown in FIG. 1).

Further, the reception unit 131 may accept a request for postponement until the usage fee is determined. Thereby, the information processing system SYS according to the embodiment can improve the usability of deferred payment type cashless payment while utilizing the existing billing scheme regarding credit card billing.

Further, the reception unit 131 may notify the user (for example, the service user UA shown in FIG. 1) that the postponement request will be accepted on the condition that a predetermined postponement fee is paid, and the postponement processing unit 232 may notify the user (for example, the service user UA shown in FIG. The postponement process may be executed on the condition that the user consents to the payment of the postponement fee. Further, the information processing system SYS according to the embodiment may further include a payment processing unit 133 that performs payment of the postponement fee when the user consents to payment of a predetermined postponement fee. Thereby, the information processing system SYS according to the embodiment can provide the billing date postponement scheme to the user as a sustainable service.

Further, the payment processing unit 133 may pay a predetermined postponement fee using the money balance held by the user. Thereby, the information processing system SYS according to the embodiment can smoothly proceed with the procedure regarding the postponement of the billing date.

Further, the payment processing unit 133 may pay a predetermined postponement fee using a credit card registered by the user. Thereby, the information processing system SYS according to the embodiment can smoothly proceed with the procedure regarding the postponement of the billing date.

The information processing system SYS according to the embodiment further includes a determining unit 132 that determines a predetermined postponement fee depending on the usage status of the postponement of the billing date by the user (for example, the service user UA shown in FIG. 1). You may do so. Thereby, the information processing system SYS according to the embodiment can charge an appropriate fee to the user who applies for postponement of the billing date.

In addition, the reception unit 131 is a program that operates using a first application as a platform for using a predetermined electronic payment service that the user has registered and uses, and is a program that operates on a terminal device used by the user. The postponement request may be accepted through the second application running. The postponement processing unit 232 may execute the postponement process on the condition that the user's consent to payment of a predetermined postponement fee is obtained through the second application. Thereby, the information processing system SYS according to the embodiment can further improve usability for users who apply for postponement of billing dates.

Further, the payment server 100 according to the embodiment includes a reception unit 131. The accepting unit 131 accepts a postponement request from a credit card user requesting a postponement of the billing date for billing the usage fee. Further, the credit card server 200 according to the embodiment includes a postponement processing unit 232. When the reception unit 131 accepts the postponement request, the postponement processing unit 232 executes postponement processing to postpone the billing date.

[6. Hardware configuration]
Further, the payment server 100 and the credit card server 200 according to the embodiment or modification described above are realized by, for example, a computer 1000 having a configuration as shown in FIG. 11. FIG. 11 is a hardware configuration diagram showing an example of a computer that implements the functions of the payment server 100 and the credit card server 200 that constitute the information processing system according to the embodiment or the modified example.

Computer 1000 has CPU 1100, RAM 1200, ROM 1300, HDD 1400, communication interface (I/F) 1500, input/output interface (I/F) 1600, and media interface (I/F) 1700.

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

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

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

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

For example, when the computer 1000 functions as the payment server 100 according to the embodiment or modification, the CPU 1100 of the computer 1000 realizes the functions of the control unit 130 by executing a program loaded onto the RAM 1200. That is, the CPU 1100 realizes the processing by the payment server 100 according to the embodiment or the modified example in cooperation with a program (for example, an information processing program) loaded onto the RAM 1200. Further, each data in the storage device of the payment server 100 is stored in the HDD 1400. The CPU 1100 of the computer 1000 reads these programs from the recording medium 1800 and executes them, but as another example, these programs may be acquired from another device via a predetermined communication network.

Further, for example, when the computer 1000 functions as the credit card server 200 according to the embodiment or modification, the CPU 1100 of the computer 1000 realizes the functions of the control unit 230 by executing a program loaded on the RAM 1200. . That is, the CPU 1100 realizes the processing by the credit card server 200 according to the embodiment or the modified example in cooperation with a program (for example, an information processing program) loaded onto the RAM 1200. Further, each data in the storage device of the credit card server 200 is stored in the HDD 1400. The CPU 1100 of the computer 1000 reads these programs from the recording medium 1800 and executes them, but as another example, these programs may be acquired from another device via a predetermined communication network.

Further, for example, when the computer 1000 functions as an information processing device having processing functions of both the payment server 100 and the credit card server 200 according to the embodiment or modification, the CPU 1100 of the computer 1000 executes a program loaded on the RAM 1200. By executing the above, the functions of the control unit of the information processing device are realized. That is, CPU 1100 realizes processing by an information processing device having the processing functions of both payment server 100 and credit card server 200 in cooperation with a program (for example, an information processing program) loaded onto RAM 1200. Furthermore, each data in the storage device of the information processing device having the processing functions of both the payment server 100 and the credit card server 200 is stored in the HDD 1400. The CPU 1100 of the computer 1000 reads these programs from the recording medium 1800 and executes them, but as another example, these programs may be acquired from another device via a predetermined communication network.

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

Furthermore, the configurations of the payment server 100 and credit card server 200 described above can be changed flexibly, such as implementing some functions by calling an external platform using an API (Application Programming Interface), network computing, or the like.

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

SYS Information processing system 10 User terminal 100 Payment server 110 Communication unit 120 Storage unit 121 User information storage unit 122 Balance information storage unit 123 Fee information storage unit 130 Control unit 131 Reception unit 132 Determination unit 133 Payment processing unit 200 Credit card server 210 Communication section 220 Storage section 221 Sales information storage section 222 Billing information storage section 230 Control section 231 Sales transmission section 232 Postponement processing section

Claims (14)

An information processing system that executes processing related to billing a credit card usage fee calculated by aggregating the usage amount every predetermined period, the information processing system comprising:
As one of the services incidental to the electronic payment service, the information processing system is a payment server that cooperates with a credit card server and provides users of the electronic payment service with an environment for using cashless payments using credit cards. , and the credit card server;
The payment server is
a reception unit that receives a postponement request from the credit card user requesting a postponement of the billing date on which the usage fee will be billed;
a payment processing unit that settles a predetermined postponement fee according to the usage status of the postponement of the billing date;
has
The credit card server is
a postponement processing unit that executes postponement processing to postpone the billing date when the postponement request is accepted by the payment server ;
has _
The payment processing unit is
When the payment of the predetermined postponement fee is completed, transmitting a billing date postponement instruction to the credit card server to request a postponement of the billing date;
The postponement processing unit is
When receiving the billing date postponement instruction from the payment server, execute the postponement process.
An information processing system characterized by: The reception department is
The information processing system according to claim 1, wherein the request for postponement is accepted for the total amount of the usage fee determined for each predetermined period. The reception department is
The information processing system according to claim 1, wherein the postponement request is received in units of transactions that constitute the usage fee determined for each predetermined period. The reception department is
The information processing system according to claim 2 or 3, wherein the postponement request is accepted until the usage fee is determined. The reception department is
Notifying the user that the postponement request will be accepted on condition of payment of a prescribed postponement fee;
The payment processing unit is
If the user consents to the payment of the predetermined postponement fee, the payment of the postponement fee is made .
The information processing system according to claim 1, characterized in that : The payment processing unit is
The information processing system according to claim 5, wherein the predetermined postponement fee is settled using a money balance held by the user. The payment processing unit is
The information processing system according to claim 5, wherein the predetermined postponement fee is paid using the credit card registered by the user. 6. The information processing system according to claim 5, further comprising: a determining unit that determines the predetermined postponement fee depending on how the user uses the postponement of the billing date. The determining unit is
The predetermined postponement fee is determined according to the number of times the billing date has been postponed.
9. The information processing system according to claim 8. The determining unit is
The predetermined postponement fee is determined according to the cumulative amount of usage fees whose payment has been postponed due to the postponement of the billing date.
9. The information processing system according to claim 8. The reception department is
A program that operates using a first application as a platform for using a predetermined electronic payment service that the user has registered to use, and a second application that operates on a terminal device used by the user. accept the said postponement request through;
The postponement processing unit is
The information processing system according to claim 5, wherein the postponement process is executed on the condition that the user's consent to payment of the predetermined postponement fee is obtained through the second application. As one of the services incidental to the electronic payment service, it works with a credit card server to provide users of the electronic payment service with an environment for cashless payment using credit cards, and aggregates the usage amount every predetermined period. An information processing device that executes processing related to billing a credit card usage fee calculated by
a reception unit that receives a postponement request from the credit card user requesting a postponement of the billing date on which the usage fee will be billed;
a payment processing unit that pays a predetermined postponement fee depending on the usage status of the postponement of the billing date when the request for postponement is accepted by the reception unit;
has
The payment processing unit is
The information processing device is characterized in that, when payment of the predetermined postponement fee is completed, a billing date postponement instruction for requesting postponement of the billing date is transmitted to the credit card server. Calculated by aggregating the usage amount for each predetermined period for cashless payments using credit cards that are used by users of electronic payment services provided by linked payment servers as one of the services incidental to said electronic payment services. An information processing device that executes processing related to billing a credit card usage fee, the information processing device comprising:
a postponement processing unit that executes postponement processing to postpone the billing date when receiving a billing date postponement instruction for requesting postponement of the billing date from the payment server;
An information processing device comprising: An information processing method executed by an information processing system that executes processing related to billing a credit card usage fee calculated by aggregating the usage amount every predetermined period, the information processing method comprising:
As one of the services incidental to the electronic payment service, the information processing system is a payment server that cooperates with a credit card server and provides users of the electronic payment service with an environment for using cashless payments using credit cards. , and the credit card server;
a reception step in which the payment server receives a postponement request from the credit card user requesting a postponement of the billing date for billing the usage fee;
a payment processing step in which the payment server pays a predetermined postponement fee according to the usage status of the postponement of the billing date;
a deferral processing step in which the credit card server executes deferral processing for postponing the billing date if the deferral request is accepted by the payment server ;
The payment processing step is
When the payment of the predetermined postponement fee is completed, transmitting a billing date postponement instruction to the credit card server to request a postponement of the billing date;
The postponement processing step is
When receiving the billing date postponement instruction from the payment server, execute the postponement process.
An information processing method characterized by:

Images