Information processing system, information processing apparatus, and information processing method

The information processing system enhances the usability of deferred payment systems by enabling users to postpone credit card billing dates with a flexible and user-friendly mechanism, addressing the complexity and duration issues in existing systems.

JP2024168918AActive Publication Date: 2024-12-05PAYPAY CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023085974
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-25
Publication Date
2024-12-05
Estimated Expiration
2043-05-25

AI Technical Summary

Technical Problem

Existing deferred payment type cashless payment systems, such as credit cards, lack usability due to complex repayment mechanisms and potential for prolonged fee accrual, especially when unexpected expenses lead to high usage amounts.

Method used

An information processing system that allows users to request and manage postponement of credit card billing dates through a user terminal, payment server, and credit card server, enabling flexible billing date adjustments with a predetermined postponement fee.

Benefits of technology

Improves the usability of deferred payment type cashless payments by providing a clear and easy-to-use mechanism for extending billing dates, allowing users to manage repayment schedules effectively.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024168918000001_ABST
    Figure 2024168918000001_ABST
Patent Text Reader

Abstract

To improve the usability in deferred cashless settlement.SOLUTION: An information processing apparatus executes processing on a bill for a credit card calculated by aggregating the amount of use for each predetermined period. The information processing apparatus includes a receiving unit and a deferment processing unit. The receiving unit receives a deferment request from a user of a credit card to defer a billing due date on which the user is billed. The deferment processing unit executes deferment processing to defer the billing due date when the receiving unit receives the deferment request.SELECTED DRAWING: Figure 4
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an information processing system, 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, with regard to post-payment cashless payments using credit cards and the like, technology has been proposed that takes into account changes such as postponing the payment date for credit card charges set by the customer. [Prior art documents] [Patent documents]

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

[0005] However, the above-mentioned conventional technologies leave room for improving the usability of postpaid cashless payments. For example, the charges for postpaid cashless payments, such as credit cards, are usually repaid on a predetermined billing date. However, when the amount used becomes high due to an unexpected expense, some users may wish to reduce the repayment amount. In response to this, one of the repayment methods proposed by credit card companies is revolving payment, but it may have a complicated mechanism or require users to bear fees for a long period of time, and it may not be necessarily user-friendly.

[0006] The present application has been made in consideration of the above, and aims to provide an information processing system, an information processing device, an information processing method, and an information processing program that can improve the usability of post-payment type cashless payment. [Means for solving the problem]

[0007] The information processing system according to the present application is an information processing system that executes processing related to billing for credit card charges calculated by tallying up usage amounts for each specified period, and includes a reception unit and a postponement processing unit. The reception unit receives a postponement request from a credit card user requesting to postpone the billing date on which the usage fee will be billed. When the reception unit receives the postponement request, the postponement processing unit executes postponement processing to postpone the billing date. 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 the billing due date postponement process according to the embodiment. [Diagram 2] FIG. 2 is a diagram showing a screen transition example (part 1) in a user terminal according to the embodiment. [Diagram 3] FIG. 3 is a diagram showing a screen transition example (part 2) in the user terminal according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of the device configuration of the information processing system according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of user information stored in a user information storage unit according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of balance information stored in a balance information storage unit according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of fee information stored in a fee information storage unit according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of sales information stored in the sales information storage unit according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of billing information stored in the billing information storage unit according to the embodiment. [Figure 10] FIG. 10 is a sequence diagram showing an example of a processing procedure of information processing executed by the information processing system according to the embodiment. [Figure 11] FIG. 11 is a hardware configuration diagram showing an example of a computer that realizes the functions of the payment server and the credit card server that constitute 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 system, 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 denoted by 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. 4, 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 an application program for a user (hereinafter, appropriately referred to as a "payment application") for using code payment (also referred to as "smartphone payment") provided to the service user UA as a cashless payment means by an electronic payment service. When the user terminal 10 receives control information for realizing a predetermined information processing through the payment application 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 a business that provides an electronic payment service. For example, the electronic payment service is a service that provides a service user with a usage environment for code payment, which allows the user to instantly pay for the price of a transaction object with a money balance, which is the balance of electronic money held by the user, using predetermined code information as described below (it can also be said to be a service that provides a predetermined transaction means that controls the exchange of electronic money by code payment).

[0016] The payment server 100 may be realized by a mainframe, a workstation, etc. 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 a plurality of server devices and a plurality of storage devices operate in cooperation with each other.

[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] In addition, as one of the services incidental to the electronic payment service, the payment server 100 provides the service user with a cashless payment environment in which the user can pay the price of the transaction object on a deferred basis using a credit card registered in advance by the user using a predetermined code information. In addition, as described later, the payment server 100 cooperates with the credit card server 200 as information processing according to the embodiment, and executes various processes related to the deferred cashless payment using a cash card.

[0019] 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 settlements made by the service user UA using a credit card. For example, the credit card server 200 calculates the credit card usage fee by tallying up the credit card usage amounts of each user (such as the service user UA shown in FIG. 1) for each predetermined period, and executes processing related to billing for the calculated usage fee. As an example of the predetermined period, it is assumed that the period is one month of each month, with the closing date being the end of the month. In this case, the processing related to billing for usage fees executed by the credit card server 200 is assumed to be processing in which the credit card usage amounts are tallied up with the closing date being the end of the month, and the usage fee for the previous month, which is the subject of billing, is billed to the user on the 27th of the following month.

[0020] Credit card server 200 may be realized by a mainframe, a workstation, etc. Furthermore, when credit card server 200 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 a plurality of server devices and a plurality of storage devices operate in cooperation with each other.

[0021] (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.

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

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

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

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

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

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

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

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

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

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

[0032] (1-3. Information Processing According to the Embodiment) (1-3-1. Overview of billing deadline extension process) 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 billing due date postponement processing according to an embodiment. In the following description, the service user UA and the user terminal 10 may be regarded as the same. In other words, the service user UA can be read as the user terminal 10.

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

[0034] When the payment server 100 receives a billing date extension request from the user terminal 10, it determines a predetermined extension fee according to the usage status of the billing date extension by the service user UA (step S02). For example, the payment server 100 may determine the extension fee according to the number of times the service user UA has extended the billing date in a predetermined target period. Also, for example, the payment server 100 may determine the extension fee according to the cumulative amount of the usage fee whose payment has been extended by the service user UA due to the extension of the billing date in a predetermined target period. In addition to the above-mentioned method, the payment server 100 may determine the extension fee based on the amount of the usage fee multiplied by a predetermined rate, credit information based on the transaction history of the service user UA's credit card, the usage history of the electronic payment service, or the like.

[0035] In addition, the payment server 100 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 including information to the effect that the request for postponement of the billing date is accepted on the condition that a predetermined postponement fee is paid to the user terminal 10, thereby presenting the information to the service user UA.

[0036] The service user UA checks the postponement-related information displayed on the user terminal 10, and executes an operation to express a desire to postpone the billing due date and to confirm the application for the postponement of the billing due date. For example, the user terminal 10 transmits an instruction to postpone the billing due date to the settlement server 100 in accordance with the operation by the service user UA (step S04).

[0037] When the payment server 100 receives the instruction to postpone the billing due date from the user terminal 10, it executes the settlement of the predetermined postponement fee corresponding to the service user UA (step S05). For example, the payment server 100 settles the predetermined postponement fee by the payment method designated by the service user UA. When the service user UA designates payment by money balance as the payment method of the predetermined postponement fee, the payment server 100 settles the predetermined postponement fee by the money balance, which is the balance of electronic money held by the service user UA in the electronic payment service. When the service user UA designates payment by credit card as the payment method of the predetermined postponement fee, the payment server 100 settles the predetermined postponement fee by the credit card set by the service user UA in the electronic payment service.

[0038] When the payment server 100 completes the payment of the predetermined postponement fee, it transmits a billing due date postponement request to the credit card server 200 (step S06). For example, the payment server 100 transmits to the credit card server 200 a billing due date postponement request including information for identifying the credit card of the service user UA who has requested the billing due date postponement request, and information for identifying the target of the billing due date to be postponed.

[0039] When the credit card server 200 receives the billing due date extension request from the payment server 100, it executes a postponement process to postpone the billing due date based on the received billing due date extension request (step S07). When the payment server 100 receives a response from the credit card server 200 indicating that the billing due date extension has been completed, it notifies the service user UA that the billing due date has been extended. For example, the payment server 100 provides the service user UA with information on the expected billing date after the extension via the payment application along with information that the billing due date has been extended.

[0040] (1-3-2. Screen transition example (part 1) on user terminal 10) Hereinafter, a screen transition example (part 1) in the user terminal 10 according to the embodiment will be described with reference to Fig. 2. Fig. 2 is a diagram showing a screen transition example (part 1) 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 request to postpone the billing due date.

[0041] 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). Furthermore, when the user terminal 10 detects an operation by the service user UA on a "deferred payment" icon OB-1 provided on the top screen G-1, it displays a deferred payment screen G1-2 for executing various processes related to deferred payment (display example EX1-2). The "deferred payment" icon OB-1 is an object for activating the functions of various processes related to deferred payment that are installed as mini-apps in the payment application.

[0042] In addition, when the user terminal 10 detects an operation by the service user UA on the item OB-2 of "Notice of April 2023 Payment Amount" from the list of notifications displayed on the postpaid screen G1-2, it displays the payment amount details screen G1-3 (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 is provided to accept a postponement request from the service user UA requesting a postponement of the billing date, which is the billing due date for the total amount of credit card charges that is determined every predetermined period. In FIG. 2, when the "Skip billing date" icon OB-3 is operated by the service user UA, a postponement of the billing due date for the total amount of credit card charges in April 2023 is requested.

[0043] In addition, when the user terminal 10 detects an operation by the service user UA on the item OB-4 indicating transaction information at "A Mart Ginza Ten" from the credit card usage details for April 2023, it displays a transaction details screen 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 provided to accept a postponement request from the service user UA requesting a postponement of the billing date, which is the billing date on which the usage fee is billed, for the transaction unit constituting the credit card usage fee determined every predetermined period. In FIG. 2, when the "Skip billing date" icon OB-5 is operated by the service user UA, a postponement of the billing date is individually requested for the amount "1,439 yen" corresponding to the transaction at "A Mart Ginza Ten" among the credit card usage fees in April 2023.

[0044] In addition, the settlement server 100 may accept a request to postpone the billing date until the credit card charge is settled. In this case, the "billing date skip" icons OB-3 and OB-5 shown in Fig. 2 are displayed on the user terminal 10 until the credit card charge is settled.

[0045] (1-3-3. Screen transition example (part 2) on user terminal 10) Hereinafter, a screen transition example (part 2) in the user terminal 10 according to the embodiment will be described with reference to Fig. 3. Fig. 3 is a diagram showing a screen transition example (part 2) 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 to postpone the billing date until the application for the billing date postponement request is confirmed.

[0046] As shown in FIG. 3, when the operation of the service user UA on the "Skip billing date" icon OB-5 on the transaction details screen G1-4 is detected (display example EX1-4), the user terminal 10 displays the postponement procedure screen G1-5 (display example EX1-5). The postponement procedure screen G1-5 displays information that the postponement request is accepted on the condition of payment of a predetermined postponement fee. For example, in the example shown in FIG. 3, information indicating the current scheduled billing date and information indicating the scheduled billing date when postponement is performed are displayed. In addition, in the example shown in FIG. 3, information on a predetermined postponement fee required to accept the postponement request is displayed. In addition, the postponement procedure screen G1-5 shown in FIG. 3 is provided with a check box OB-6 for accepting an expression of intent to the effect that the billing date is to be postponed from the service user UA, and an application icon OB-7 for accepting an operation to confirm an application for postponement of the billing date from the service user UA. Note that the application icon OB-7 may be controlled so that the operation is valid when the check box OB-6 is checked.

[0047] Furthermore, when the user terminal 10 detects an operation by the service user UA on the application icon OB-7 on the postponement procedure screen G1-5, it redisplays the transaction details screen G1-4 with some of the 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 postponement.

[0048] As described above, according to the information processing system SYS of the embodiment, the billing date of the credit card usage fee 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 of the embodiment can provide the service user UA with a clear and easy-to-use reduction scheme by simply extending the billing date by one month, thereby improving the usability of post-payment type cashless payment.

[0049] [2. Equipment 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 with reference to 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, the payment server 100 includes a communication unit 110, a storage unit 120, and a control unit 130.

[0050] (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.

[0051] (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. 4, the storage unit 120 has a user information storage unit 121, a balance information storage unit 122, and a fee information storage unit 123.

[0052] (Regarding the user information storage unit 121) The user information storage unit 121 stores user information related to users of electronic payment services. Fig. 5 is a diagram showing an example of user information stored in the user information storage unit 121 according to the embodiment.

[0053] 5, the user information stored in the user information storage unit 121 has multiple items such as a "user ID", a "transaction history", a "registered card information", a "withdrawal account information", a "postponement fee payment method", a "postponement usage status", etc. These items in the user information are mutually associated.

[0054] The "user ID" field stores a user ID, which is unique identification information assigned to each user of an electronic payment service (such as service user UA shown in FIG. 1) in order to uniquely identify the user.

[0055] The "transaction history" field 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 fee, the total amount paid, the payment amount, the payment month, and the balance carried over from the next month.

[0056] The "Registered Card Information" field stores information about the credit card registered by the service user as a credit card to be used for deferred payment. The registered card information may include information such as the cardholder's name, expiration date, and card number.

[0057] The "withdrawal account information" item stores information for identifying a bank account registered by the service user as an account for withholding payments for credit card charges. Information for identifying a bank account may include information such as the bank name, branch name, account name, and account number.

[0058] The "Postponement Fee Payment Method" field stores information indicating the payment method registered by the service user as the payment method for the predetermined postponement fee that must be paid when the billing date is postponed. For example, possible payment methods available to the service user include payment with a money balance, which is the balance of electronic money held by the user as a source of payment for code settlement provided by an electronic settlement service, and payment with a credit card for deferred payment.

[0059] The "postponement usage status" field stores information indicating the usage status of postponing the billing date for the usage fee using deferred payment. The usage status may include the number of times the usage fee was postponed in a specified target period, the cumulative amount of the usage fee whose payment was postponed due to the postponement of the billing date in a specified target period, etc.

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

[0061] 6, the balance information stored in the balance information storage unit 122 has multiple items such as a "user ID" item and a "money balance" item. These items in the balance information are associated with each other.

[0062] The "user ID" field stores a user ID, which is unique identification information assigned to each user of an electronic payment service (such as service user UA shown in FIG. 1) in order to uniquely identify the user.

[0063] The "money balance" field stores information indicating the money balance, which is the balance of electronic money held by the user as payment resources for code payments provided by electronic payment services.

[0064] (Regarding the fee information storage unit 123) The fee information storage unit 123 stores fee information related to a predetermined postponement fee corresponding to the usage status of the postponement of the billing date on which the credit card usage fee is billed. Fig. 7 is a diagram showing an example of fee information stored in the fee information storage unit 123 according to the embodiment.

[0065] 7, the fee information stored in fee information storage unit 123 has an item of "usage status" and an item of "fee amount." These items in the fee information are associated with each other.

[0066] The "usage status" field stores information for identifying the usage status of billing date extension. For example, the usage status may include the number of times that billing dates were extended during a specified target period, or the cumulative amount of usage fees that were extended due to billing date extension during a specified target period for users who used deferred payment for usage fees.

[0067] The "fee amount" field stores information indicating a fee that is determined in advance according to the usage situation. For example, the fee may be determined arbitrarily by a business providing an electronic payment service or a business providing a credit card service.

[0068] (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).

[0069] As shown in Fig. 4, the control unit 130 has a reception unit 131, a determination unit 132, and a payment processing unit 133, 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. 4 in response to the extension of various processes executed by the payment server 100.

[0070] (Regarding the reception unit 131) The reception unit 131 receives a postponement request from a credit card user to request a postponement of the billing date on which the charge for the transaction will be billed.

[0071] For example, the receiving unit 131 may receive a postponement request for the total amount of the usage fee determined for each predetermined period. For example, the receiving unit 131 may receive a postponement request for each transaction unit constituting the usage fee determined for each predetermined period.

[0072] Furthermore, for example, the accepting unit 131 may accept a request to postpone the billing date on which the credit card usage fee is billed until the usage fee is finalized.

[0073] Also, for example, the reception unit 131 may notify a user (such as the service user UA shown in FIG. 1) that it will accept a request to postpone the billing date on which the credit card usage fee is charged, subject to the payment of a specified postponement fee.

[0074] Also, for example, the reception unit 131 may notify a user (such as the service user UA shown in FIG. 1) that a request to postpone the billing due date will be accepted, subject to payment of a specified postponement fee corresponding to the credit card usage status.

[0075] Also, for example, the reception unit 131 may be a program that operates on a platform of a first application (e.g., a payment supplement) for using a specified electronic payment service that a user (e.g., service user UA shown in FIG. 1) has registered to use, and that receives a request to postpone billing of credit card usage fees through a second application (e.g., a "pay later" mini-app) that operates on a terminal device (e.g., user terminal 10 shown in FIG. 1) used by the user.

[0076] The reception unit 131 may also receive sales data related to credit card settlement 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.

[0077] Furthermore, when the reception unit 131 receives a response from the credit card server 200 via the communication unit 110 notifying the completion of the postponement of the billing date, the reception unit 131 may present the completion of the postponement of the billing date to the service user UA. For example, the reception unit 131 provides the service user UA with information on the postponed scheduled billing date together with the fact that the billing date has been postponed to the user terminal 10 via the communication unit 110.

[0078] (Regarding the determination unit 132) The determination unit 132 determines a predetermined postponement fee depending on the usage status of postponement of the billing date on which the credit card usage fee is billed.

[0079] (Regarding the payment processing unit 133) When an application is made for postponement of the billing date on which the credit card usage fee is charged, the payment processing unit 133 settles a prescribed postponement fee according to the payment method registered by the applying user (for example, the service user UA shown in FIG. 1). When the payment of the prescribed postponement fee is completed, the payment processing unit 133 transmits a request to postpone the billing date to the credit card server 200 via the communication unit 110.

[0080] (2-2. Configuration of Credit Card Server 200) Next, an example of a 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, the credit card server 200 includes a communication unit 210, a storage unit 220, and a control unit 230.

[0081] (Regarding communication unit 210) The communication unit 210 is realized by, for example, a network interface card (NIC) etc. 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.

[0082] (Regarding the storage unit 220) The storage unit 220 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. 8, the storage unit 220 has a sales information storage unit 221 and a billing information storage unit 222.

[0083] (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.

[0084] 8, the sales information stored in the sales information storage unit 221 has a number of items such as a "sales ID" item and a "sales information" item. These items in the sales information are associated with each other.

[0085] The "sales ID" field stores a sales ID, which is identification information that is individually assigned to each piece of sales information in order to identify the sales information.

[0086] The "Sales Information" field stores sales information for credit cards. For example, the sales information may include information such as the date of use (settlement date), the user, the store (affiliated store), the amount used (settlement amount), and the card number.

[0087] (Regarding the 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.

[0088] 9, the billing information stored in the billing information storage unit 222 has multiple items such as a "billing ID" field, a "billing destination" field, a "details of use" field, a "usage amount" field, a "billing date" field, a "withdrawal account information" field, a "postponement target" field, etc. These items in the billing information are mutually associated.

[0089] The "billing ID" field stores a billing ID, which is identification information that is individually assigned to each piece of billing information in order to identify the billing information.

[0090] The "billing destination" field stores information for identifying the billing destination. For example, the information for identifying the billing destination may include information on the user and card number information. The "usage details" field stores information indicating the credit card usage during a specified period. The "usage amount" field stores information indicating the total amount of credit card usage during a specified period. The "billing date" field stores information indicating the billing date for the credit card usage fee. The "withdrawal account information" field stores information regarding the withdrawal account for the credit card usage fee. The "postponement target" field stores information indicating the target of the billing date for which the billing date will be postponed. For example, the total amount of the usage fee and the usage amounts corresponding to the individual transactions that make up the usage fee are expected to be postponed.

[0091] (Regarding the control unit 230) The control unit 230 is a controller, and is realized, for example, by a CPU (Central Processing Unit) or an MPU (Micro Processing Unit) executing various programs stored in a storage device inside the payment server 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 ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

[0092] As shown in Fig. 4, control unit 230 has sales transmission unit 231 and postponement processing unit 232, and these units realize or execute the functions and actions of information processing described below. Note that control unit 230 may introduce new functional units different from the units shown in Fig. 4 in response to the expansion of various processes executed by credit card server 200.

[0093] (About Sales Transmission Section 231) When the sales transmission unit 231 acquires sales information from a credit card affiliated store, it transmits the acquired sales information to the payment server 100 via the communication unit 210.

[0094] (Regarding the postponement processing unit 232) The postponement processing unit 232 executes a postponement process to postpone the billing date when a request to postpone the billing date is accepted by the settlement server 100. For example, the postponement processing unit 232 executes a postponement process to postpone the billing date (billing date) by one month.

[0095] Moreover, the postponement processing unit 232 executes the process of postponing the billing date on the condition that consent to the payment of a predetermined postponement fee is obtained from the user (for example, the service user UA shown in FIG. 1).

[0096] In addition, the postponement processing unit 232 executes the billing date postponement processing on the condition that the user (for example, the service user UA shown in Figure 1) agrees to pay a specified postponement fee corresponding to the usage status of the billing date postponement.

[0097] In addition, the postponement processing unit 232 executes the postponement processing of the billing due date through a second application (e.g., a "pay later" mini-app) running on a terminal device (e.g., the user terminal 10 shown in FIG. 1) used by a user (e.g., the service user UA shown in FIG. 1), on the condition that the user's consent to the payment of a specified postponement fee is obtained.

[0098] [3. Example of processing procedure] Hereinafter, the flow of information processing executed by the information processing system SYS according to the embodiment will be described with reference to Fig. 10. Fig. 10 is a sequence diagram showing an example of a processing procedure of information processing executed by the information processing system SYS according to the embodiment. In the processing procedure shown in Fig. 10, the processing corresponding to the payment server 100 is executed by the control unit 130 possessed by the payment server 100. The control unit 130 repeatedly executes the processing procedure shown in Fig. 10 while the payment server 100 is operating. In the processing procedure shown in Fig. 10, the processing corresponding to the credit card server 200 is executed by the control unit 230 possessed by 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 operating.

[0099] As shown in FIG. 10, a service user UA operates the user terminal 10 to carry out a credit card payment for purchasing an item or applying to use a service at an affiliated store that has introduced an electronic payment service (step S101).

[0100] When an affiliated store (e.g., a store terminal installed at the affiliated store) accepts a payment for the purchase of an item or application for use of a service, it performs authorization (e.g., online processing related to credit card payment) with the credit card server 200 through the acquirer (step S102).

[0101] Furthermore, when authorization is normally completed, the affiliated store provides goods or services to the service user UA (step S103).

[0102] In addition, the affiliated store (for example, a store terminal installed at the affiliated store) transmits sales data related to the service user UA's credit card to the credit card server 200 via the acquirer, for example by batch processing scheduled at a predetermined timing (step S104).

[0103] The sales transmitting unit 231 of the credit card server 200 transmits the sales data provided by the affiliated store to the settlement server 100 (step S105).

[0104] When the acceptance unit 131 of the settlement server 100 receives the sales data from the credit card server 200, the acceptance unit 131 reflects the received sales data in the transaction history included in the user information of the corresponding user (step S106).

[0105] Furthermore, the service user UA checks the transaction history displayed on the payment app at any time and requests, through the payment app, to postpone the billing date for the credit card usage fee (step S201). For example, when the user terminal 10 detects an operation by the service user UA on the "skip billing date" icon OB-3 (see FIG. 2) on the payment amount details screen G1-3 or the "skip billing date" icon OB-5 on the transaction details screen G1-4, the user terminal 10 transmits a billing date postponement request to postpone the billing date by one month to the payment server 100.

[0106] When the payment server 100 receives a request to postpone the billing date, it determines a predetermined postponement fee, and presents the determined amount of the predetermined postponement fee and the postponed billing date to the service user UA through the payment application (step S202). For example, the payment server 100 transmits information indicating the amount of the predetermined postponement fee and the postponed billing date to the user terminal 10, transmits the information to the user terminal 10 to be displayed in the payment application, and presents the amount of the predetermined postponement fee and the postponed billing date to the service user UA through the postponement procedure screen G1-5 (see FIG. 3) of the payment application.

[0107] In addition, the service user UA checks 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 of 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 transmits an instruction to postpone the billing date to the payment server 100 (step S203).

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

[0109] When the postponement processing unit 232 of the credit card server 200 receives a request to postpone the billing due date from the payment server 100, it executes the billing due date postponement processing (step S206) and sends a response to the payment server 100 indicating that the billing due date postponement processing has been completed (step S207).

[0110] When the reception unit 131 of the settlement server 100 receives a response from the credit card server 200 indicating that the billing date has been postponed, the reception unit 131 presents the completion of the postponement of the billing date to the service user UA (step S208). For example, the settlement server 100 presents this to the service user UA by displaying the "Skip billing date" icon OB-5 and the transaction details screen G1-4 (see FIG. 3) on the user terminal 10 in which the payment month information has been changed to the postponed scheduled billing date.

[0111] 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 this case, for example, the control unit 130 of the payment server 100 may have the processing function of the postponement processing unit 232 provided in the credit card server 200 as the processing function according to the embodiment.

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

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

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

[0115] 5. Effects As described above, the information processing system SYS according to the embodiment is a computer system that executes processing related to billing for credit card charges calculated by tallying up usage amounts for each predetermined period, and includes a reception unit 131 and a postponement processing unit 232. The reception unit 131 receives a postponement request from a credit card user requesting postponement of the billing date on which the usage fee will be billed. When the reception unit 131 receives a postponement request, the postponement processing unit 232 executes postponement processing to postpone the billing date.

[0116] In this way, the information processing system SYS according to the embodiment can provide the service user UA with a clear and easy-to-use reduction scheme by a simple method, for example, of simply extending the billing due date by one month, thereby improving the usability of post-payment type cashless payment.

[0117] The reception unit 131 may also receive the postponement request for the total amount of the usage fee determined for each predetermined period. This allows the information processing system SYS according to the embodiment to flexibly respond to individual requests from users of the electronic payment service (for example, the service user UA shown in FIG. 1).

[0118] The reception unit 131 may also receive the postponement request in units of transactions constituting the usage fee determined for each predetermined period. This allows the information processing system SYS according to the embodiment to flexibly respond to individual requests from users of the electronic payment service (for example, the service user UA shown in FIG. 1).

[0119] The reception unit 131 may receive a request for postponement until the usage fee is determined. In this way, the information processing system SYS according to the embodiment can improve the usability of the postpaid cashless payment while utilizing the existing billing scheme for credit card billing.

[0120] Furthermore, the reception unit 131 may notify a 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 execute the postponement processing on the condition that the user's consent to the payment of the predetermined postponement fee is obtained. Furthermore, the information processing system SYS according to the embodiment may further include a settlement processing unit 133 that settles the postponement fee when the user's consent to the payment of the predetermined postponement fee is obtained. In this way, the information processing system SYS according to the embodiment can provide the user with a billing date postponement scheme as a sustainable service.

[0121] In addition, the settlement processing unit 133 may settle a predetermined postponement fee using the money balance held by the user. This allows the information processing system SYS according to the embodiment to smoothly proceed with the procedure for postponing the billing date.

[0122] In addition, the payment processing unit 133 may settle a predetermined postponement fee by a credit card registered by the user. This allows the information processing system SYS according to the embodiment to smoothly proceed with the procedure for postponing the billing date.

[0123] The information processing system SYS according to the embodiment may further include a determination unit 132 that determines a predetermined postponement fee depending on the usage status of the postponement of the billing date by a user (for example, the service user UA shown in FIG. 1). This allows the information processing system SYS according to the embodiment to charge an appropriate fee to a user who applies for the postponement of the billing date.

[0124] The reception unit 131 may be a program that operates on a platform of a first application for using a specific electronic payment service that the user has registered to use, and may receive a postponement request through a second application that operates on a terminal device used by the user. The postponement processing unit 232 may execute the postponement process through the second application on the condition that the user's consent to the payment of a specific postponement fee is obtained. This allows the information processing system SYS according to the embodiment to further improve usability for users who apply for postponement of the billing date.

[0125] Moreover, the payment server 100 according to the embodiment has a reception unit 131. The reception unit 131 receives a postponement request from a credit card user requesting postponement of the billing date on which the usage fee will be billed. Moreover, the credit card server 200 according to the embodiment has a postponement processing unit 232. When the postponement request is received by the reception unit 131, the postponement processing unit 232 executes a postponement process to postpone the billing date.

[0126] [6. Hardware Configuration] Moreover, the payment server 100 and the credit card server 200 according to the above-mentioned embodiment or modification are realized, for example, by a computer 1000 configured as shown in Fig. 11. Fig. 11 is a hardware configuration diagram showing an example of a computer that realizes the functions of the payment server 100 and the credit card server 200 constituting the information processing system according to the embodiment or modification.

[0127] The computer 1000 has a CPU 1100, a RAM 1200, a ROM 1300, a HDD 1400, a communication interface (I / F) 1500, an input / output interface (I / F) 1600, and a media interface (I / F) 1700.

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

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

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

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

[0132] For example, when the computer 1000 functions as the payment server 100 according to the embodiment or the modification, the CPU 1100 of the computer 1000 executes a program loaded on the RAM 1200 to realize the function of the control unit 130. That is, the CPU 1100 realizes the processing by the payment server 100 according to the embodiment or the modification in cooperation with the program (e.g., an information processing program) loaded on the RAM 1200. In addition, the HDD 1400 stores each data in the storage device of the payment server 100. The CPU 1100 of the computer 1000 reads and executes these programs from the recording medium 1800, but as another example, these programs may be obtained from another device via a predetermined communication network.

[0133] Also, for example, when computer 1000 functions as credit card server 200 according to the embodiment or the modification, CPU 1100 of computer 1000 executes a program loaded on RAM 1200 to realize the function of control unit 230. That is, CPU 1100 realizes the processing by credit card server 200 according to the embodiment or the modification in cooperation with a program (e.g., an information processing program) loaded on RAM 1200. Also, HDD 1400 stores each data in the storage device of credit card server 200. CPU 1100 of computer 1000 reads and executes these programs from recording medium 1800, but as another example, these programs may be obtained from another device via a predetermined communication network.

[0134] Also, for example, when computer 1000 functions as an information processing device having the processing functions of both payment server 100 and credit card server 200 according to the embodiment or the modified example, CPU 1100 of computer 1000 executes a program loaded on RAM 1200 to realize the function of the control unit of the information processing device. That is, CPU 1100 realizes the processing by the 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 on RAM 1200. Also, HDD 1400 stores each data in the storage device of the information processing device having the processing functions of both payment server 100 and credit card server 200. CPU 1100 of computer 1000 reads these programs from recording medium 1800 and executes them, but as another example, these programs may be obtained from another device via a predetermined communication network.

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

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

[0137] 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]

[0138] SYS Information Processing System 10 User terminal 100 Payment Server 110 Communications Department 120 Storage section 121 User information storage unit 122 Balance information storage unit 123 Fee information storage unit 130 Control section 131 Reception 132 Decision Section 133 Payment Processing Unit 200 Credit Card Server 210 Communications Department 220 Storage section 221 Sales information storage unit 222 Billing information storage unit 230 Control Unit 231 Sales Transmission Department 232 Postponement Processing Unit

Claims

1. An information processing system that performs processing related to billing for credit card usage fees calculated by tallying up usage amounts for each specified period, comprising: a reception unit for receiving a request for postponement from a user of the credit card to request a postponement of a billing date on which the charge for the use will be billed; a postponement processing unit that executes a postponement process for postponing the billing due date when the postponement request is accepted by the accepting unit; An information processing system comprising:

2. The reception unit is The request for postponement is accepted for the total amount of the usage fee determined for each predetermined period.

2. The information processing system according to claim 1 .

3. The reception unit is The request for postponement is accepted in transaction units constituting the usage fee determined for each predetermined period.

2. The information processing system according to claim 1 .

4. The reception unit is The request for postponement is accepted until the usage fee is determined.

4. The information processing system according to claim 2 or 3.

5. The reception unit is notifying the user that the postponement request will be accepted subject to payment of a prescribed postponement fee; The postponement processing unit: Executing the postponement process on the condition that the user agrees to pay the predetermined postponement fee; a payment processing unit that performs payment of the postponement fee when the user's consent to the payment of the predetermined postponement fee is obtained; 2. The information processing system according to claim 1, further comprising:

6. The payment processing unit, The predetermined postponement fee is paid using the money balance held by the user.

6. The information processing system according to claim 5.

7. The payment processing unit, The predetermined postponement fee is paid by the credit card registered by the user.

6. The information processing system according to claim 5.

8. A determination unit that determines the predetermined postponement fee according to a usage status of the postponement of the billing date by the user 6. The information processing system according to claim 5, further comprising:

9. The reception unit is A program that operates using a first application as a platform for using a predetermined electronic payment service that the user has registered for and is using, and that accepts the postponement request through a second application that operates on a terminal device used by the user; The postponement processing unit: Executing the postponement process on the condition that the user's consent to the payment of the predetermined postponement fee is obtained through the second application.

6. The information processing system according to claim 5.

10. An information processing device that executes a process related to billing for credit card usage fees calculated by tallying up usage amounts for each specified period, a reception unit for receiving a request for postponement from a user of the credit card to request a postponement of a billing date on which the charge for the use will be billed; a postponement processing unit that executes a postponement process for postponing the billing due date when the postponement request is accepted by the accepting unit; 13. An information processing device comprising:

11. 1. An information processing method executed by a computer that executes a process related to billing for credit card usage fees calculated by tallying up usage amounts for each specified period, comprising: a receiving step of receiving a request for postponement from the credit card user to request a postponement of the billing date on which the charge for the transaction will be billed; a postponement processing step of executing a postponement process for postponing the billing due date when the postponement request is accepted by the accepting step; 13. An information processing method comprising:

12. A computer that executes a process related to billing for credit card charges calculated by tallying up charges for each specified period, a receiving step of receiving a request for postponement from the credit card user to request a postponement of the billing date on which the charge for the transaction is to be billed; a postponement processing step of executing a postponement process for postponing the billing due date when the postponement request is accepted by the accepting step; An information processing program characterized by causing the program to execute the above steps.

Citation Information

Patent Citations

  • Credit card usage amount management system

    JP2019003249A