Program, information processing method and server

A server system addresses the inefficiency of traditional loan notification methods by directly transmitting overdue repayment information to user devices, improving repayment awareness and compliance through digital messaging services.

JP2024159107APending Publication Date: 2024-11-08LY CORP

Patent Information

Application Number
JP2023074884
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-04-28
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

Existing loan systems lack efficient mechanisms for notifying borrowers of overdue repayments and providing detailed repayment information, often relying on traditional methods like letters which are less effective in digital formats.

Method used

A server-based system that communicates with user terminals to store loan information and automatically transmit overdue repayment notifications and detailed loan information, including interest rates, directly to the user's device, utilizing messaging services for digital delivery.

Benefits of technology

Ensures timely and effective communication of overdue repayment notices and loan details to users, enhancing repayment awareness and compliance through digital means.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024159107000001_ABST
    Figure 2024159107000001_ABST
Patent Text Reader

Abstract

To improve convenience regarding payment of a lent amount, etc.SOLUTION: A program executed by a server that communicates with a user's terminal causes the server to: cause a control unit of the server to perform control for storing information on an amount lent to a user in a storage unit of the server; and, when a repayment deadline for the lent amount has passed, transmit the information on the lent amount and an interest rate to the terminal via a communication unit of the server.SELECTED DRAWING: Figure 1-1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a program, an information processing method, a server, and the like. [Background technology]

[0002] For example, Patent Document 1 discloses a technology relating to a loan contract system in which a consumer applies for a loan at a retail store. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2002-099721 A Summary of the Invention

[0004] According to a first aspect of the present invention, a program executed by a server communicating with a user's terminal is executed by the server, in which a control unit of the server controls the storage of information on the amount loaned to the user in the server's memory unit, and, if the repayment deadline for the loaned amount has passed, the server transmits information on the loaned amount and information on the loan interest rate to the terminal via the server's communication unit. According to a second aspect of the present invention, an information processing method of a server communicating with a user's terminal includes controlling the storage of information on the amount loaned to the user in the server's memory unit by a control unit of the server, and, if the repayment deadline for the loaned amount has passed, transmitting information on the loaned amount and information on the loan interest rate to the terminal by the server's communication unit. According to a third aspect of the present invention, a server communicating with a user's terminal comprises a control unit which controls the storage of information on the amount loaned to the user in the server's memory unit, and a communication unit which, if the repayment deadline for the loaned amount has passed, transmits information on the loaned amount and information on the loan interest rate to the terminal. [Brief description of the drawings]

[0005] [Figure 1-1]FIG. 1 is a diagram showing an example of a system configuration of a communication system according to an embodiment. [Figure 1-2] FIG. 2 is a diagram showing an example of functions realized by a control unit of the server according to the first embodiment. [Figure 1-3] FIG. 4 is a diagram showing an example of information stored in a storage unit of the server according to the first embodiment. [Figure 1-4] FIG. 4 is a diagram showing an example of account registration data according to the first embodiment. [Figure 1-5] FIG. 2 is a diagram showing an example of an account management database according to the first embodiment. [Figure 1-6] FIG. 2 is a diagram showing an example of functions realized by a control unit of the terminal according to the first embodiment. [Figure 1-7] FIG. 4 is a diagram showing an example of information stored in a storage unit of the terminal according to the first embodiment. [Figure 1-8] FIG. 4 is a diagram showing an example of a screen displayed on a display unit of the terminal according to the first embodiment. [Figure 1-9] 4 is a flowchart showing an example of the flow of processes executed by each device according to the first embodiment. [Figure 1-10] FIG. 11 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a first modified example. [Figure 1-11] FIG. 11 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a first modified example. [Figure 2-1] FIG. 11 is a diagram showing an example of an account management database according to the second embodiment. [Figure 2-2] FIG. 11 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a second embodiment. [Figure 2-3] FIG. 11 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a second embodiment. [Figure 2-4] 10 is a flowchart showing an example of the flow of processes executed by each device according to the second embodiment. [Figure 2-5] FIG. 11 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a second modified example. [Figure 2-6] FIG. 11 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a second modified example. [Diagram 2-7] 10 is a flowchart showing an example of the flow of processes executed by each device according to a second modified example. [Figure 2-8] FIG. 11 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a second modified example. [Figure 2-9] FIG. 11 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a second modified example. [Figure 2-10] FIG. 11 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a second modified example. [Figure 3-1] FIG. 11 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a third embodiment. [Figure 3-2] 13 is a flowchart showing an example of the flow of processes executed by each device according to the third embodiment. [Figure 4-1] FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fourth embodiment. [Figure 5-1] FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to the sixth embodiment. [Figure 5-2] FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to the sixth embodiment. [Figure 6-1] FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to the ninth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0006] <Compliance with legal matters> It should be noted that the disclosures described herein are subject to compliance with the laws of the country of implementation, such as communications secrecy, as necessary for the implementation of the disclosure.

[0007] <Embodiment> In this specification, for ease of understanding, there are some places where the phrase "by way of example and not by way of limitation" is used, but please note that not only these places but also the entire embodiment described below are not limited to the contents of the description.

[0008] An embodiment for implementing a program or the like according to the present disclosure will be described with reference to the drawings.

[0009] The production of a terminal of the present invention (a terminal of the present invention) may include, by way of example and not limitation, the concept of a program (an application program, by way of example and not limitation) described in this specification being received (or being received and stored in) a terminal owned (possessed) by a user, thereby creating a state in which the functions of the present invention can be realized (a state in which the present invention can be executed) in the terminal.

[0010] Furthermore, the production of the system of the invention claimed in the present application (the system of the invention) may include the concept that, by way of example and not limitation, a state in which the functions of the invention of the system claimed in the present application can be realized (a state in which the invention claimed in the present application can be executed) is created by receiving, at a terminal included in the system of the present application, a program described in this specification (by way of example and not limitation, an application program) transmitted from a server included in the system of the present application (or by storing the received program in the terminal).

[0011] In addition, in this specification, a system may be, for example and not by way of limitation, configured to include a plurality of devices. The multiple devices may be a combination of devices of the same type, a combination of devices of different types, or a combination of devices of the same type and devices of different types. Note that a system can be considered, for example and not by way of limitation, as a plurality of devices working together to perform some kind of processing.

[0012] Furthermore, a system relating to a client (client device) and a server can be considered to be, by way of example and not of limitation, at least one of the following: (1) Terminals and servers (2) Server (3) Terminal

[0013] (1) is, by way of example and not limitation, a system including at least one terminal and at least one server. One example of this is a client-server system.

[0014] The server is configured by the following devices, for example and not by way of limitation, and may be a single device or a combination of multiple devices.

[0015] Specifically, the server is configured to have at least one processor (for example and without limitation, CPU: Central Processing Unit, GPU: Graphics Processing Unit, APU: Accelerated Processing Unit, DSP: Digital Signal Processor (for example and without limitation, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array), etc.), computer device (processor + memory), control device, arithmetic device, processing device, etc., and may be a configuration having multiple of the same type of any one device (for example and without limitation, CPU + CPU, homogeneous multi-core processor, etc.) or a configuration having multiple different types of any one device (for example and without limitation, CPU + DSP, heterogeneous multi-core processor, etc.), or may be a combination of multiple devices (for example and without limitation, processor + computer device, processor + arithmetic device, multiple devices made heterogeneous, etc.). The processor may be a virtual processor.

[0016] Also, when a server executes some processing, if the server is configured with a single device, the processing described in the embodiment is executed by the single device. If the server is configured with multiple devices, one device may execute some processing, and the other device may execute other processing. As a non-limiting example, if the server is configured with a processor and an arithmetic device, the processor may execute a first processing, and the arithmetic device may execute a second processing. Furthermore, when a configuration is made up of a plurality of devices, the devices may be arranged in locations physically separated from one another.

[0017] Furthermore, the functions of the server may be provided in the form of PaaS, IaaS, or SaaS in cloud computing, for example and without limitation.

[0018] The control unit of the system may be at least one of the control unit of the terminal and the control unit of the server. That is, by way of example and not limitation, the control unit of the system may be any of the following: (1A) only the control unit of the terminal, (1B) only the control unit of the server, or (1C) both the control unit of the terminal and the control unit of the server.

[0019] In addition, the control and processing (hereinafter collectively referred to as "control, etc.") performed by the control unit of the system may be performed by (1A) only the control unit of the terminal, (1B) only the control unit of the server, or (1C) both the control unit of the terminal and the control unit of the server. In addition, in (1C), as an example and not a limitation, some of the controls performed by the control unit of the system may be performed by the control unit of the terminal, and the remaining controls may be performed by the control unit of the server. In this case, the allocation (allocation) of the controls may be equal or may be allocated in different proportions.

[0020] Furthermore, when referring to a communication unit of a server, if the server is configured with a single device, it may be the communication unit itself that the single device has, or, if the server is configured with multiple devices, the communication unit of the server may be configured to include each communication unit that each device has. As an example and not by way of limitation, if a server comprises a first device and a second device, the first device having a first communication unit and the second device having a second communication unit, the communication unit of the server may be conceptualized as including the first communication unit and the second communication unit.

[0021] (2) is not limited to, but may be, for example, a system consisting of multiple servers (hereinafter, referred to as a "server system"). In this case, the configuration of each server may be the same as that described above.

[0022] The control etc. performed by the server system may be performed by only one of the multiple servers (2A), by only the other servers (2B), or by both the one server and the other servers (2C). In addition, in (2C), as an example and not a limitation, one server may perform part of the control etc. performed by the server system, and another server may perform the remaining control etc. In this case, the allocation (allocation) of the control etc. may be equal or may be allocated in different proportions.

[0023] (3) By way of example and not limitation, the system may be comprised of multiple terminals. The system may be, by way of example and not limitation, a system such as the following: A system that gives server functions to terminals (distributed system). This can be realized using blockchain technology, for example and not by way of limitation. A system in which terminals communicate wirelessly with each other. This can be realized, for example and without limitation, by communicating in a peer-to-peer (P2P) manner using short-range wireless communication technology such as Bluetooth (registered trademark).

[0024] The above is not limited to the control unit, but also applies to each functional unit such as an input / output unit, a communication unit, a storage unit, and a clock unit that may be components of the system.

[0025] In the following embodiment, a system including a terminal and a server (a client-server system) is illustrated as an example and not as a limitation. It should be noted that the server system described above in (2) can also be used as the server.

[0026] Also, instead of a system including a terminal and a server, a system not including a server, such as the above system (3) as an example and not a limitation, may be applied. In this case, the embodiment can be configured based on the above-mentioned blockchain technology. Specifically, by way of example and not limitation, data stored and managed in a server described in the following embodiment is stored on the blockchain. Then, the terminal generates a transaction to the blockchain, and when the transaction is approved on the blockchain, the data stored on the blockchain can be updated.

[0027] It should be noted that even when the term "terminal" is used, this is not limited to the meaning of a terminal as a client device in a client server. That is, a terminal may include the concept of a device other than in a client-server context.

[0028] Furthermore, in this specification, the expression "through a communication I / F" is used as appropriate. This is not intended to be limiting, but may indicate, by way of example, that a device transmits and receives various types of information and data through a communication I / F (through a communication unit) based on the control of a control unit (such as a processor).

[0029] In addition, in this specification, when the terms "related to" and "associated with" are used, "B related to A" or "B related to A" may mean, by way of example and not limitation, "B" having some kind of relationship with "A." Specific examples of this will be described later.

[0030] In addition, in this specification, when a device performs processing on two or more objects, such as "transmitting A and B" or "receiving A and B," this may include performing "A" and "B" in a synchronized manner (hereinafter referred to as "simultaneous"), and performing "A" and "B" with a different timing (hereinafter referred to as "non-simultaneous"). As an example and not a limitation, when referring to transmitting first information and second information, this may include both concepts of transmitting the first information and the second information in a synchronized manner and transmitting the first information and the second information with a lag in timing. In addition, taking into account the lag (time lag), "simultaneous" may include "almost simultaneously."

[0031] Note that, even if "A" and "B" are performed at different times, this only needs to be the processing targeting "A" and "B," and the purpose does not necessarily have to be the same. As an example and not a limitation, when the first information and the second information are transmitted as described above, it is sufficient to transmit the first information and the second information, and this may include cases where the first information and the second information are transmitted for the same purpose, as well as cases where the first information and the second information are transmitted for different purposes.

[0032] In the following embodiment, a messaging service is illustrated as an example of a service that allows users to chat (hereinafter, referred to as a "chat service"). An application for realizing the chat service is referred to as a "chat application," and an application for realizing the messaging service is referred to as a "messaging application." By way of example and not limitation, a chat application may enable users to chat in chat rooms.

[0033] Note that messaging services (MS) (including instant messaging services (IMS)) can be considered as one form of social networking services (SNS). Therefore, messaging services and social networking services may or may not be distinguished. In other words, social networking services may include messaging services.

[0034] In addition, in the following embodiments, as an example of a messaging service, an instant messaging service (IMS) that transmits and receives simple messages between multiple devices (terminals, for example and not limitation) via a server is exemplified. By way of example and not limitation, an instant messaging application may allow users to talk in talk rooms.

[0035] A chat room (for example, but not limited to, a talk room) can be a UI (User Interface) or GUI (Graphical User Interface) that allows each user to view content transmitted and received between the terminals of multiple users.

[0036] In addition, talk rooms can include one-to-one user talk rooms (hereinafter referred to as "one-to-one talk rooms"), talk rooms for groups including multiple users (hereinafter referred to as "group talk rooms"), and talk rooms with OA businesses (as an example, but not limited to, businesses that are affiliated with messaging service providers) (hereinafter referred to as "OA talk rooms").

[0037] In addition, an account of a messaging application that is an account of a business operator and not a general user may be referred to as an "OA (Official Account)," and a user of this official account may be referred to as an "official user." This may also be referred to as an "official account user" or an "official account business operator," etc. In contrast, an account of a messaging application that is a user who is not an OA business is called a "general account," and a user of a general account is called a "general user." This may also be called a "general account user," etc. In other words, messaging application accounts may include general accounts and official accounts.

[0038] In addition, as a non-limiting example, OA operators may be able to use a terminal similar to that of a user with a general account to send and receive messages with other devices via the server.

[0039] Further, a message (message information) may be, by way of example and not limitation, information that defines a sender and a destination used in a messaging service, and may be information that is composed of identification information (message ID) for identifying the message and message content. Additionally, message content may refer to, by way of example and not limitation, the contents of a message excluding the message ID. Message content may be one or more pieces of content.

[0040] Moreover, information set as identification information for identifying a message is referred to as a "message ID." It can also be considered that message content included in a message with the same message ID is identified by this message ID. Therefore, it can also be considered that identification information for identifying a message is substantially synonymous with identification information for identifying message content. Alternatively, individual identification information (message content ID) may be set for each message content, but this is not essential.

[0041] The content may include, by way of example and not limitation, text content in text format, image content in image format (including at least one of still images and / or moving images), audio content in sound format (including voice), and the like. In addition, the content may include operation content such as buttons and icons for user operations, and link content such as URIs (including URLs).

[0042] The text may include, by way of example and not limitation, at least one of national characters, extended characters, machine-dependent characters, numbers, symbols, graphics, and symbols represented by character codes. Note that the text does not have to include at least one of the above characters, extended characters, machine-dependent characters, numbers, symbols, figures, and signs, and may include other text.

[0043] The image may include at least one of various types of image information, such as, for example and without limitation, an icon, a button, a stamp, an emoji, and a banner image.

[0044] Unlike the above definition, the superordinate concept of a message may be content, or content and message may be synonymous, or it is not necessary to define them in this way.

[0045] In the following embodiment, a money loan service is illustrated as an example of a service that allows a user to borrow money from a financial institution. An application for implementing the money loan service is referred to as a "money loan application." By way of example and not limitation, a money loan application may allow a user to borrow money from a money loan service provider and obtain information regarding loan repayment of the borrowed money.

[0046] In the following embodiment, a service for a user to make a payment (hereinafter, referred to as a "payment service") is exemplified. An application for realizing the payment service is referred to as a "payment application." By way of example and not limitation, a payment application may enable a user to make payments using electronic currency.

[0047] In this specification, "electronic currency" refers to electronic currency that is distinguished from physical currency and may refer to electronic currency owned by a terminal managed in the various applications mentioned above or by a user of the terminal. In addition, "electronic currency" may be considered as "digital currency (digital money)."

[0048] As one way of thinking, electronic currency can be considered as a concept that includes "electronic money," "virtual currency (crypto assets)," "central bank issued digital currency (CBDB)," etc.

[0049] In addition, electronic currency may be a "legal tender" or a "corporate currency". The implementation method of electronic currency may be "centralized finance (CeFi)" or "decentralized finance (DeFi)".

[0050] In the embodiment described below, electronic money as corporate currency in centralized finance will be described as an example of electronic currency, but is not limited thereto.

[0051] It should be noted that corporate currency may also include physical currency such as coupons.

[0052] As a form for realizing the money loan service (money loan application), any of the following forms can be applied, by way of example and not of limitation. (A1) A form in which a money loan service function is provided as one of the functions of a messaging application (A2) A form in which the function of the money loan service is provided as one of the functions of a payment application (B1) A form constituting an application having a money loan service function and a messaging service function (an integrated application) (B2) A form constituting an application having a money loan service function and a payment service function (an integrated application) (B3) A form constituting an application having a money loan service function, a payment service function, and a messaging service function (an integrated application) (C1) A messaging application that is a separate application from a money loan application (C2) A form in which a payment application is configured as a separate application from a money loan application (C3) A form in which a payment service and a messaging service are integrated into an application separate from a money loan application (D) A money loan application configured as a standalone application

[0053] In embodiments (A1), (B1) and (B3), by way of example and not limitation, the money loan service provider may be the same as the messaging service provider. In this case, one method is to treat the user's account in the messaging application and the user's account in the money loan application as a common account. Alternatively, in this case, the user's account in the messaging application and the user's account in the money loan application may be automatically associated (linked).

[0054] The same applies when the money loan service provider and the payment service provider are the same provider.

[0055] In the embodiments (C1) to (C3), by way of example and not limitation, the money loan service provider may be a different provider from the messaging service provider. In addition, in the embodiments (C1) to (C3), a process for associating a user's account in the messaging application with a user's account in the money loan application (a linking process) can be performed. The same is true for payment applications.

[0056] Alternatively, the money loan application may have a messaging service function as one of its functions, or a payment service function as one of its functions.

[0057] In the following, it is assumed, by way of example and not limitation, that the server 10 is operated and managed by a money loan service provider or a messaging service provider.

[0058] In the following description, the user of terminal 20A is referred to as "user AA", the user of terminal 20B as "user BB", the user of terminal 20C as "user CC", . . . .

[0059] <Example> An example of an embodiment to which the present invention is applied will be described below. For example, when a user borrows money from a business such as a money loan service provider, there may be cases where the user falls behind on the repayment even though the contractual repayment date stipulated in the loan contract has arrived. In such cases, the money loan service provider can send the user a written notice informing them that the repayment is behind. In the following embodiment, a money loan service provider is used as an example of the provider.

[0060] Conventionally, this document has been sent to the user in the form of a letter or the like (hereinafter, appropriately referred to as "analog form"). The embodiments described below relate to sending such documents in the form of, by way of example and not limitation, a messaging service message sent from the OA of the money loan service provider, a notice in the money loan service, or the like (hereinafter referred to as "digital format" as appropriate).

[0061] In the event of a late repayment, examples of written notices that a money loan service provider may send to a user to inform the user that the repayment is overdue may include, by way of example and not limitation, the following: -Late payment notice ·Demand letter ·Demand letter

[0062] By way of example and not limitation, the delinquent notice may be a document in which the money loan service provider notifies the user that a repayment is overdue and urges the user to repay.

[0063] A demand letter is, by way of example and not limitation, a document in which a money loan service provider notifies a user that a repayment is overdue and urges the user to repay, similar to the aforementioned delinquent payment notice, but, by way of example and not limitation, the demand letter may be a document that can clearly state that it is stricter than a delinquent payment notice.

[0064] Specifically, the reminder may include, by way of example and not limitation, the following items: Trade name, business name or name, address and telephone number of the person engaged in the employment business Name of the person sending the document or electromagnetic record ·Contract date Loan amount Loan interest rate - Payment deadline for claims related to payment demands - Amount to be paid The amount of the remaining debt at the time of the payment demand - Breakdown of the amount being demanded to be paid (principal, interest, and compensation for default)

[0065] The notice may be, by way of example and not by way of limitation, a document similar to the demand letter discussed above, but which may, by way of example and not by way of limitation, be more severe than a demand letter. Specifically, the notice may include, by way of example and not limitation, the following items in addition to the items included in the reminder letter described above: · Taking legal action if performance is not met by the due date - Making claims against guarantors or cosigners - Requesting payment of the amount demanded in a lump sum

[0066] The demand or notice may include, by way of example and not by way of limitation, a legal implication that the money loan service provider intends to demand payment from the user by sending such documents to the user, and the completion of the statute of limitations for repayment of the debt may be extended by sending such documents to the user.

[0067] Additionally, by way of example and not limitation, the reminder or notice may or may not be sent by certified mail.

[0068] In addition, as a non-limiting example, a reminder letter and a notice of demand, which are documents used by a money loan service provider to urge a user to repay, may be documents with different names and different contents. However, the present invention is not limited to such an example, and the documents may have similar contents but only have different names.

[0069] In the embodiment described below, by way of example and not limitation, a case will be given in which the document sent to a user when the user is behind on repayment is a demand letter. However, this is not limited to this.

[0070] As used herein, loan agreements may include, by way of example and not limitation, plans such as the following: Pocket Plan - Self-paced plan

[0071] The pocket plan may be, for example and not by way of limitation, a typical loan contract in which the period from the loan date to the scheduled repayment start date and the period from the scheduled repayment start date to the scheduled repayment days after the scheduled repayment start date are set to be equal.

[0072] A self-paced plan may be, for example and not by way of limitation, a loan contract in which the period from the loan date to the scheduled repayment start date is set longer than the period of scheduled repayment days after the scheduled repayment start date.

[0073] The main embodiment herein illustrates the application of a pocket plan by way of example and not by way of limitation. The case where the My Pace Plan is applied will be described later.

[0074] In this specification, when a user of terminal 20 has entered into a loan contract with a money loan service provider, the repayment method to be made on the scheduled repayment date may be, by way of example and not limitation, automatic repayment mainly from the balance of electronic money linked to the money loan service (hereinafter referred to as the "electronic money balance"). However, the present invention is not limited to this, and as will be described later, repayment may be made by other methods, such as bank transfer repayment.

[0075] If a reminder is sent because the user has not made a repayment on the scheduled repayment date, the user may be able to make the repayment from the reminder. When the user taps a repayment button HBT or the like on the screen in the center of FIG. 1-8 described later, for example and not by way of limitation, the screen may transition to a screen for making repayment with electronic money. This screen may be, for example and not for limitation, a screen that prompts the user to charge the balance of electronic money (for example and not for limitation, so that the electronic money balance is an amount greater than the repayment amount).

[0076] <First Example> The first embodiment is an example, not a limitation, in which a user of a terminal 20 (hereinafter referred to as "terminal" as appropriate) enters into a loan contract with a money loan service provider operating a server 10 and receives a demand letter due to failure to repay the loan.

[0077] The contents described in the first embodiment are applicable to any of the other embodiments and other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0078] In the following, the name of the money loan application will be referred to as "Money Loan App" when appropriate, and the name of the messaging application will be referred to as "Messaging App" when appropriate, and ...

[0079] <System configuration> FIG. 1-1 is a diagram illustrating an example of a system configuration of a communication system 1 according to an embodiment of the present disclosure. In the communication system 1, as an example and not a limitation, a server 10 and a plurality of terminals 20 (terminal 20A, terminal 20B, terminal 20C, . . . ) are connected via a network 30.

[0080] The server 10 has a function of providing a predetermined service (such as, for example and not limitation, a money loan service, a messaging service, etc.) to a terminal 20 owned by a user via a network 30. The server 10 may be expressed as, for example and not limitation, a money loan service server, a messaging service server, etc. In this embodiment, users of the server 10 include money loan service providers (operators) and messaging service providers (operators).

[0081] The number of servers 10 and the number of terminals 20 connected to the network 30 are not limited.

[0082] The terminal 20 (terminal 20A, terminal 20B, terminal 20C, ...) may be any information processing terminal capable of implementing the functions described in each embodiment. The terminal 20 includes, but is not limited to, a smartphone, a mobile phone (feature phone), a computer (such as, but not limited to, a desktop, laptop, tablet, etc.), a media computer platform (such as, but not limited to, a cable or satellite set-top box, digital video recorder), a handheld computer device (such as, but not limited to, a PDA (personal digital assistant), email client, etc.), a wearable device (such as a glasses-type device, a watch-type device, etc.), a VR (Virtual Reality) terminal, a smart speaker (a device for voice recognition), or other types of computers or communication platforms. The terminal 20 may also be expressed as an information processing terminal.

[0083] The configurations of the terminals 20A, 20B, and 20C can be the same as one another, for example and not for limitation. In addition, if necessary, the terminal used by the user X may be expressed as the terminal 20X, and the user information in a predetermined service associated with the user X or the terminal 20X may or may not be expressed as the user information X. The user information is information of a user associated with an account used by the user in a specific service. The user information includes, but is not limited to, information associated with a user, such as the user's name, the user's icon image, the user's age, the user's sex, the user's address, the user's hobbies and interests, and the user's identifier, which is input by the user or given by a specific service, and may be any one of these, or a combination of these, or may not be the same.

[0084] The network 30 plays a role of connecting one or more terminals 20 and one or more servers 10. In other words, the network 30 refers to a communication network that provides a connection path so that the above-mentioned various devices can be connected and then transmit and receive data.

[0085] One or more portions of network 30 may or may not be wired or wireless networks. Network 30 may include, by way of example and not limitation, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular network, integrated service digital networks (ISDN), wireless LAN, long term evolution (LTE), code division multiple access (CDMA), Bluetooth, satellite communications, or the like, or a combination of two or more thereof. Network 30 may include one or more networks 30.

[0086] The server 10 (not limited to, but an example of a server, information processing device, or information management device) has a function of providing a predetermined service to the terminal 20. The server 10 may be any device as long as it is an information processing device capable of realizing the functions described in each embodiment. The server 10 includes, not limited to, a server device, a computer (not limited to, but an example of, a desktop, a laptop, a tablet, etc.), a media computer platform (not limited to, but an example of, a cable, a satellite set-top box, a digital video recorder), a handheld computer device (not limited to, but an example of, a PDA, an email client, etc.), or other types of computers or communication platforms. The server 10 may also be expressed as an information processing device. When it is not necessary to distinguish between the server 10 and the terminal 20, the server 10 and the terminal 20 may or may not be expressed as information processing devices.

[0087] [Hardware (HW) configuration of each device] The hardware configuration of each device included in the communication system 1 will be described.

[0088] (1) Terminal hardware configuration FIG. 1-1 shows an example of the hardware configuration of the terminal 20. In FIG. The terminal 20 includes a control unit 21 (CPU: central processing unit), a storage unit 28, a communication I / F 22 (interface), an input / output unit 23, a clock unit 29A, and a position calculation information detection unit 29B. The HW components of the terminal 20 are connected to each other via a bus B, for example and not for limitation. It is not essential that the HW configuration of the terminal 20 includes all of the components. For example and not for limitation, the terminal 20 may or may not be configured such that individual components or multiple components are removable.

[0089] The communication I / F 22 transmits and receives various data via the network 30. The communication may be performed either wired or wirelessly, and any communication protocol may be used as long as the communication between the two devices is possible. The communication I / F 22 has a function of communicating with various devices such as the server 10 via the network 30. The communication I / F 22 transmits various data to various devices such as the server 10 according to instructions from the control unit 21. The communication I / F 22 also receives various data transmitted from various devices such as the server 10 and transmits it to the control unit 21. The communication I / F 22 may also be simply referred to as a communication unit. When the communication I / F 22 is configured with a physically structured circuit, it may also be referred to as a communication circuit.

[0090] The input / output unit 23 includes a device for inputting various operations to the terminal 20, a device for outputting processing results processed by the terminal 20, etc. The input / output unit 23 may be an integrated input unit and an output unit, or may be separate from the input unit and the output unit, or may not be.

[0091] The input unit is realized by any one or a combination of all kinds of devices that can receive input from a user and transmit information related to the input to the control unit 21. Examples of the input unit include, but are not limited to, a touch panel, a touch display, hardware keys such as a keyboard, a pointing device such as a mouse, a camera (operation input via moving images), and a microphone (operation input by voice).

[0092] The output unit is realized by any one or a combination of all kinds of devices capable of outputting the processing results processed by the control unit 21. Examples of the output unit include, but are not limited to, a touch panel, a touch display, a speaker (audio output), a lens (for example, but not limited to, 3D (three dimensions) output and hologram output), a printer, etc.

[0093] By way of example only, the input / output unit 23 includes, by way of example and not limitation, a display unit 24, a sound input unit 25, a sound output unit 26, and an imaging unit 27.

[0094] The display unit 24 is realized by any one of all kinds of devices capable of displaying according to the display data written in the frame buffer, or a combination thereof. The display unit 24 includes, by way of example and not limitation, a touch panel, a touch display, a monitor (by way of example and not limitation, a liquid crystal display or an organic electroluminescence display (OLED)), a head mounted display (HDM), a projection mapping, a hologram, a device capable of displaying images, text information, and the like in air (which may or may not be a vacuum). Note that these display units 24 may or may not be capable of displaying display data in 3D.

[0095] The sound input unit 25 is used to input sound data (including voice data; the same applies below). The sound input unit 25 includes a microphone and the like. The sound output unit 26 is used to output sound data and includes a speaker and the like. The imaging unit 27 is used to obtain image data (including still image data and moving image data; the same applies below.) The imaging unit 27 includes a camera and the like.

[0096] When the input / output unit 23 is a touch panel, the input / output unit 23 and the display unit 24 may be disposed facing each other and have approximately the same size and shape.

[0097] The clock unit 29A is a built-in clock of the terminal 20, and outputs time information (timekeeping information). The clock unit 29A is configured to include, for example and not limitation, a clock using a crystal oscillator. The clock unit 29A can also be expressed as a timekeeping unit or a time information detection unit, for example and not limitation.

[0098] The clock unit 29A may or may not have a clock that conforms to the Network Identity and Time Zone (NITZ) standard or the like.

[0099] The position calculation information detection unit 29B is a functional unit that detects (measures) information (hereinafter referred to as "position calculation information") necessary for the control unit 21 to calculate (measure) the position of its own terminal 20. The position calculation information detection unit 29B can also be expressed as a position calculation sensor unit, for example and not by way of limitation.

[0100] The position calculation information detection unit 29B includes, by way of example and not limitation, a satellite positioning sensor (satellite positioning unit) which is a sensor or unit for calculating the position of the terminal 20 using a satellite positioning system such as GPS (Global Positioning System), an inertial measurement sensor (inertial measurement unit (IMU (Inertial Measurement Unit))) which is a sensor or unit for calculating the position of the terminal 20 using an inertial navigation system, a UWB positioning sensor (UWB positioning unit) which is a sensor or unit for calculating the position of the terminal 20 using UWB (Ultra Wide Band), and the like.

[0101] The satellite positioning unit includes, by way of example and not limitation, an RF receiving circuit that converts RF (Radio Frequency) signals, including positioning satellite signals transmitted from positioning satellites and received by an antenna (not shown), into digital signals, and a baseband processing circuit that performs correlation calculation processing or the like on the digital signals output from the RF receiving circuit to capture the positioning satellite signals, and outputs information such as satellite orbit data and time data extracted from the positioning satellite signals as information for position calculation.

[0102] The inertial measurement unit has an inertial sensor that is a sensor that detects information required for calculating the position of the terminal 20 by inertial navigation calculation. The inertial sensor includes, but is not limited to, a three-axis acceleration sensor and a three-axis gyro sensor, and outputs the acceleration detected by the acceleration sensor and the angular velocity detected by the gyro sensor as information for position calculation.

[0103] The UWB positioning unit includes, by way of example and not limitation, an ultra-wideband RF receiving circuit that converts an ultra-wideband RF (Radio Frequency) signal, including an ultra-wideband pulse signal for positioning transmitted from a positioning beacon and received by an antenna not shown, into a digital signal, and a relative position calculation processing circuit that calculates the relative position between the terminal 20 and the positioning beacon based on the digital signal output from the ultra-wideband RF receiving circuit. As an example and not by way of limitation, the UWB positioning unit may or may not cause the terminal 20 to function as a positioning beacon by transmitting an ultra-wideband RF signal including an ultra-wideband pulse signal for positioning from an antenna not shown.

[0104] As an example and not a limitation, the control unit 21 calculates the position of its own terminal 20 at regular timing or specific timing based on the position calculation information detected by the position calculation information detection unit 29B. The terminal position is referred to as the "terminal position", and the calculated terminal position is referred to as the "calculated terminal position". The control unit 21 may, but may not, associate the calculated terminal position with the date and time when the calculated terminal position is calculated and store it in the storage unit 28 as calculated terminal position history data.

[0105] The control unit 21 has a circuit physically structured to execute the functions realized by the code or instructions contained in the program, and is realized by a data processing device built into hardware, for example and not by way of limitation. Therefore, the control unit 21 may or may not be expressed as a control circuit.

[0106] The control unit 21 includes, by way of example and not limitation, a central processing unit (CPU), a microprocessor, a processor core, a multiprocessor, an application-specific integrated circuit (ASIC), and a field programmable gate array (FPGA).

[0107] The storage unit 28 has a function of storing various programs and various data required for the operation of the terminal 20. The storage unit 28 includes, by way of example and not limitation, various storage media such as a hard disk drive (HDD), a solid state drive (SSD), a flash memory, a random access memory (RAM), and a read only memory (ROM). In addition, the storage unit 28 may or may not be expressed as a memory.

[0108] Terminal 20 stores program P in storage unit 28, and executes this program P, causing control unit 21 to execute processing as each unit included in control unit 21. In other words, program P stored in storage unit 28 causes terminal 20 to realize each function executed by control unit 21. Also, this program P may or may not be expressed as a program module.

[0109] (2) Server hardware configuration FIG. 1-1 shows an example of the HW configuration of the server 10. In FIG. The server 10 includes a control unit 11 (CPU), a storage unit 15, a communication I / F 14 (interface), an input / output unit 12, and a clock unit 19. The components of the HW of the server 10 are connected to each other via a bus B, for example and not for limitation. It is not essential that the HW of the server 10 includes all the components as the configuration of the HW of the server 10. For example and not for limitation, the HW of the server 10 may or may not be configured such that individual components or multiple components are removable.

[0110] The control unit 11 has circuits physically structured to execute functions realized by codes or instructions contained in a program, and is realized, for example and not by way of limitation, by a data processing device embedded in hardware.

[0111] The control unit 11 is typically a central processing unit (CPU), but may also be a microprocessor, a processor core, a multiprocessor, an ASIC, or an FPGA, but is not limited to these in the present disclosure.

[0112] The storage unit 15 has a function of storing various programs and various data required for the operation of the server 10. The storage unit 15 is realized by various storage media such as an HDD, an SSD, and a flash memory. However, in the present disclosure, the storage unit 15 is not limited to these. Furthermore, the storage unit 15 may or may not be expressed as a memory.

[0113] The communication I / F 14 transmits and receives various data via the network 30. The communication may be performed either wired or wirelessly, and any communication protocol may be used as long as the communication between the two devices is possible. The communication I / F 14 has a function of communicating with various devices such as the terminal 20 via the network 30. The communication I / F 14 transmits various data to various devices such as the terminal 20 according to instructions from the control unit 11. The communication I / F 14 also receives various data transmitted from various devices such as the terminal 20 and transmits it to the control unit 11. The communication I / F 14 may also be simply referred to as a communication unit. When the communication I / F 14 is configured with a physically structured circuit, it may also be referred to as a communication circuit.

[0114] The input / output unit 12 includes a device for inputting various operations to the server 10, a device for outputting the results of processing by the server 10, etc. The input / output unit 12 may be an integrated input unit and an output unit, or may be separate input unit and output unit, or may not be the same.

[0115] The input unit is realized by any one or a combination of all kinds of devices capable of receiving input from a user and transmitting information related to the input to the control unit 11. The input unit is typically realized by hardware keys such as a keyboard or a pointing device such as a mouse. Note that the input unit may or may not include a touch panel, a camera (operation input via moving images), or a microphone (operation input by voice), as examples and without limitation.

[0116] The output unit is realized by any one or a combination of all kinds of devices capable of outputting the processing results processed by the control unit 11. Examples of the output unit include, but are not limited to, a touch panel, a touch display, a speaker (sound output), a lens (for example, but not limited to, 3D (three dimensions) output and hologram output), a printer, etc.

[0117] By way of example only, the input / output unit 12 includes a display unit 13, by way of example and not by way of limitation.

[0118] The display unit 13 is realized by a display or the like. The display is typically realized by a monitor (for example, but not limited to, a liquid crystal display or an organic electroluminescence display (OLED)). The display may or may not be a head mounted display (HDM) or the like. These displays may or may not be capable of displaying display data in 3D. In the present disclosure, the display is not limited to these.

[0119] The clock unit 19 is a built-in clock of the server 10, and outputs time information (timekeeping information). The clock unit 19 is configured to include, for example and not limitation, an RTC (Real Time Clock) as a hardware clock, a system clock, etc. The clock unit 19 can also be expressed as a timekeeping unit or a time information detection unit, for example and not limitation.

[0120] (3)Other The server 10 stores a program P in the storage unit 15, and by executing this program P, the control unit 11 executes the processes of each unit included in the control unit 11. In other words, the program P stored in the storage unit 15 causes the server 10 to realize each function executed by the control unit 11. This program P may or may not be expressed as a program module. The same applies to other devices.

[0121] In each embodiment of the present disclosure, the description will be given assuming that the CPU of the terminal 20 and / or the server 10 executes the program P to realize the present invention.

[0122] The control unit 21 of the terminal 20 and / or the control unit 11 of the server 10 may or may not realize each process by a CPU having a control circuit, but may also realize each process by a logic circuit (hardware) formed in an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)) or a dedicated circuit. These circuits may or may not be realized by one or more integrated circuits, and the multiple processes shown in each embodiment may or may not be realized by one integrated circuit. Furthermore, an LSI may be called a VLSI, a super LSI, an ultra LSI, or the like, depending on the degree of integration. Therefore, the control unit 21 may or may not be expressed as a control circuit.

[0123] In addition, the program P (as an example, but not limited to, a software program, a computer program, or a program module) of each embodiment of the present disclosure may or may not be provided in a state stored in a computer-readable storage medium. The storage medium can store the program P in a "non-transitory tangible medium." In addition, the program P may or may not be for realizing part of the functions of each embodiment of the present disclosure. Furthermore, the program P may or may not be a so-called difference file (difference program) that can realize the functions of each embodiment of the present disclosure in combination with a program P already recorded in a storage medium.

[0124] Furthermore, when referring to a system program (a program executed by the system), the system is as described above. The above-mentioned system program is a program that can be executed by the entire system, and this program may be composed of individual programs of the devices that make up the system, for example and without limitation, and the programs stored in the individual devices that make up the system may be different from each other. In other words, it is not necessary for the programs to be common to the individual devices that make up the system. As an example and not a limitation, if a system is composed of a terminal and a server, and the system program is P1, the system program P1 is composed of a program P2 stored in the terminal and a program P3 stored in the server, and P2 and P3 are for executing the system program and may be different programs. As an example and not a limitation, the program P2 stored in the terminal may be a program that executes a first process and transmits the result of the first process to the server, and the program P3 stored in the server may be a program that executes a second process on the received result of the first process and transmits the result of the second process to the terminal.

[0125] The storage medium may include one or more semiconductor-based or other integrated circuits (ICs) (such as, by way of example and not limitation, a field programmable gate array (FPGA) or an application specific IC (ASIC)), a hard disk drive (HDD), a hybrid hard drive (HHD), an optical disk, an optical disk drive (ODD), a magneto-optical disk, a magneto-optical drive, a floppy diskette, a floppy disk drive (FDD), a magnetic tape, a solid state drive (SSD), a RAM drive, a secure digital card, or a drive, any other suitable storage medium, or a suitable combination of two or more of these. The storage medium may be volatile, non-volatile, or a combination of volatile and non-volatile, where appropriate. It should be noted that the storage medium is not limited to these examples and may be any device or medium capable of storing the program P. In addition, the storage medium may or may not be referred to as a memory.

[0126] The server 10 and / or the terminal 20 can realize the functions of the multiple functional units shown in each embodiment by reading out the program P stored in a storage medium and executing the read out program P.

[0127] Furthermore, the program P of the present disclosure may or may not be provided to the server 10 and / or the terminal 20 via any transmission medium capable of transmitting a program (such as a communication network or broadcast waves). The server 10 and / or the terminal 20 executes the program P downloaded via the Internet or the like, for example and not for limitation, to realize the functions of the multiple functional units shown in each embodiment.

[0128] In addition, each embodiment of the present disclosure may also be realized in the form of a data signal in which the program P is embodied by electronic transmission. At least a part of the processing in the server 10 and / or the terminal 20 may or may not be realized by cloud computing configured with one or more computers. At least a part or all of the processing in the terminal 20 may or may not be performed by the server 10. In this case, at least a part or all of the processing of each functional unit of the control unit 21 of the terminal 20 may or may not be performed by the server 10. At least a part or all of the processing in the server 10 may or may not be performed by the terminal 20. In this case, at least a part or all of the processing of each functional unit of the control unit 11 of the server 10 may or may not be performed by the terminal 20.

[0129] Unless explicitly stated, the judgment configuration in the embodiments of the present disclosure is not essential, and a specified process may or may not be executed when the judgment condition is satisfied, or a specified process may or may not be executed when the judgment condition is not satisfied.

[0130] Note that the programs of the present disclosure are implemented using, by way of example and not limitation, scripting languages ​​such as ActionScript and JavaScript (registered trademark), compiler languages ​​such as Objective-C and Java (registered trademark), and markup languages ​​such as HTML Living Standard.

[0131] <Functional configuration> (1) Functional configuration of the server FIG. 1-2 is a diagram showing an example of functions realized by the control unit 11 of the server 10 in this embodiment. The control unit 11 includes, as a functional unit, an application management processing unit 111 for executing application management processing in accordance with an application management processing program 151 stored in the storage unit 15, for example and not for limitation.

[0132] FIG. 1-3 is a diagram showing an example of information stored in the storage unit 15 of the server 10 in this embodiment. In the storage unit 15, for example and not for limitation, an application management processing program 151 executed as application management processing, account registration data 153, and an account management database 155 are stored.

[0133] The account registration data 153 is registration data related to the account of an application (a money loan application in this embodiment), and an example of the data configuration is shown in FIG. 1-4. In the account registration data 153, for example and not by way of limitation, a user name, an application ID, and other registration information are stored in association with each other.

[0134] The user name is the name of the account of the terminal 20 that uses this application, and by way of example and not limitation, the name registered when the user of the terminal 20 uses the application is stored.

[0135] The application ID is information used to identify an application account, or the account itself. This application ID is preferably a value unique to each account, and as a non-limiting example, a unique value (proper value) is set and stored by the server 10 for each account. The application ID is information associated with the terminal 20 or the user of the terminal 20, and is an example of information related to the terminal or information related to the user of the terminal.

[0136] Other registration information may include, by way of example and not limitation, various types of information such as identification information for identifying terminal 20, the telephone number (terminal telephone number) of terminal 20, an email address (terminal email address), and authentication information such as passwords (login password, authentication password, etc.) used for various authentications in applications.

[0137] In addition, the other registration information may include, by way of example and not limitation, the following items that can be registered by the user of the terminal 20 as information for determining credit when making a loan. ·Workplace ·annual income Length of service Family Composition Asset status Housing type

[0138] Furthermore, the other registration information may include, by way of example and not limitation, a credit score (social score) calculated based on the user information of the terminal 20.

[0139] The identification information for identifying the terminal 20 may be, for example and not for limitation, a terminal ID (for example and not for limitation, an International Mobile Equipment Identity (IMEI)). Furthermore, the identification information for identifying the user of the terminal 20 can be, for example and without limitation, an application ID for general users.

[0140] It should be noted that the application ID may or may not be replaced by a "user ID." Furthermore, if the application allows only one account to be registered per terminal 20, then, as a non-limiting example, "identification information for identifying terminal 20 = identification information for identifying the user of terminal 20 = application ID" may be used.

[0141] Also, by way of example and not limitation, it may or may not be possible to assign multiple terminal IDs to one application ID. In this case, it may or may not be possible to simultaneously launch an application on multiple terminals 20 using one application ID as an identification (login) target.

[0142] Also, instead of various IDs such as application IDs, it is possible to apply a method of managing accounts using information such as terminal telephone numbers. In this case, instead of storing ID information such as an application ID in account registration data 153, information such as a terminal telephone number can be stored in account registration data 153. Note that, instead of replacing ID information such as an application ID with information such as a terminal telephone number, ID information such as an application ID may or may not correspond one-to-one to information such as a terminal telephone number.

[0143] In the following various embodiments, for the sake of simplicity, it is assumed that one account is registered for one terminal 20. In this case, since, as described above, "identification information for identifying terminal 20 = identification information for identifying the user of terminal 20 = application ID," the term "user of the account" used in the following explanation may be essentially synonymous with "terminal of the account."

[0144] The account management database 155 is a database for managing information related to the accounts registered in the account registration data 153, and an example of the data configuration of the account management database 155A is shown in FIG. 1-5. Account management database 155A stores account management data as management data for each account.

[0145] Each account management data includes, by way of example and not limitation, an application ID, a name, and loan management data.

[0146] The application ID is information for identifying an account managed by the account management data, and as a non-limiting example, the application ID registered in the account registration data 153 is stored.

[0147] The name is the name of the user of the terminal 20 who uses the money loan service, and by way of example and not limitation, the name registered by the user of the terminal 20 when using the money loan service is stored. The name here will be referred to as the "contractor name" as appropriate.

[0148] The loan management data is, by way of example and not limitation, data for storing information regarding a loan contract that a money loan service provider lends to a user who is the account holder of this application ID. The loan management data stores, by way of example and not limitation, the loan date, loan balance, loan interest rate, contracted repayment amount, contracted repayment start date, late payment interest rate, late payment amount, and other loan information in association with each other. The scheduled repayment start date may be the date of the first scheduled repayment. It may also be called the "first scheduled repayment date."

[0149] The loan date (which may be called the loan contract date), loan balance, loan interest rate, agreed repayment amount, agreed repayment start date, late payment interest rate, and late payment damage amount may be, by way of example and not limitation, information that is updated and stored by the control unit 11 of the server 10 in association with the loan lending process and the repayment process of the loan that has been extended.

[0150] The other loan information may include, for example and without limitation, the contracted repayment date (contracted repayment frequency) after the contracted repayment start date, which is set by the control unit 11 of the server 10 in association with the loan lending process. The other loan information may include information on the repayment status of the loan provided, the social score (credit score) of the account of this application ID, and the like.

[0151] Other loan information may also include, by way of example and not limitation, the following: Trade name, name, address or telephone number of the money loan service provider Sender name Payment due date - Amount to be paid · Remaining loan balance Breakdown of the amount to be paid

[0152] (2) Functional configuration of the terminal FIG. 1-6 is a diagram showing an example of functions realized by a control unit 21 of a terminal 20 in this embodiment. The control unit 21 includes, as a functional unit, an application processing unit 211 for executing application processing according to an application processing program 281 stored in the storage unit 28, for example and not for limitation.

[0153] FIG. 1-7 is a diagram showing an example of data stored in the storage unit 28 of the terminal 20 in this embodiment. In the storage unit 28, for example and not for limitation, an application processing program 281 executed as application processing and an application ID 283 corresponding to this terminal 20 or the account of the user of the terminal 20 are stored.

[0154] <Display screen> An example of a display screen in this embodiment will be described. The transition of the display screens described below is merely an example of the transition of the display screens for implementing the method of the present disclosure. In the transition of the display screens illustrated below, some of the display screens may be omitted, or other display screens may be added.

[0155] In addition, the terminology used on the display screen described below may differ from the terminology used in the processes described thereafter (some terminology may not be consistent), but this is merely for convenience and to provide an easy-to-understand explanation of the display screen from the user's perspective. The same applies to the other embodiments and modifications.

[0156] In the following, as an example and not a limitation, a case will be illustrated in which the terminal 20 is a smartphone equipped with a display unit 24 having a portrait display.

[0157] For example, but not by way of limitation, a smartphone has a touch panel that functions as an input unit and is disposed opposite the display, thereby forming a touch screen. When an element such as an icon, button, item, or input area is displayed on the display, and a part of the touch panel that faces the area where the element is displayed is operated by a user, a program associated with the element or a subroutine of the program is executed.

[0158] In the following, as an example of a user operation, tapping (tapping operation) and the like will be given as a non-limiting example. A tap (tap operation) can be, by way of example and not limitation, an action in which a user lightly touches the display unit 24 (touch screen) that is integrally configured with a touch panel with a finger or the tip of a pen, and then releases the touch.

[0159] In addition, in the display screen example, as a repayment method in a loan contract, a calculation example based on the fixed principal and interest method is illustrated as an example and not a limitation, but the repayment method is not limited to this. As an example and not a limitation, the fixed principal method or the sliding balance method may be used. In addition, the calculated values ​​illustrated in the display screen example are merely approximate values ​​for illustrative purposes and may differ from the actual values.

[0160] 1-8 is a diagram showing an example of the transition of screens displayed on the display unit 24 of the terminal 20A in this embodiment. Note that, in the following, the process executed by the terminal 20 will be illustrated and described as the process executed by the terminal 20A of the user AA, by way of example and not by way of limitation.

[0161] This screen image shows, by way of example and not limitation, an example in which a user of terminal 20 borrows 30,000 yen from a money loan service provider at an annual interest rate of 15%, and a reminder letter is sent because the user fails to make a repayment on the first scheduled repayment date. However, this is merely an example and is not limited to this example.

[0162] The left side of FIG. 1-8 is, by way of example and not limitation, an example of a prompting information display screen that is displayed after an application is completed in a money loan application. This screen is configured to display the name of the money loan application, "Money Loan App," in the center of the top of the screen. Also, below that, the words "[Important] Payment Information" are displayed, based on the receipt of a reminder message.

[0163] Below that, a dunning information display area RR is configured for displaying detailed information about the dunning information. The reminder information display area RR displays, by way of example and not limitation, information regarding the contract holder's name (Mr. ****), information informing that repayment is overdue, information regarding the repayment deadline for this reminder (until February 19, 2023 (7 days later)), information regarding the amount claimed in this reminder (current claim amount: X, XXX yen), information regarding the breakdown of the amount claimed (principal A, AAA yen, accrued interest BBB yen, late payment charges CCC yen), etc.

[0164] By way of example and not limitation, when the user scrolls to view the bottom of the screen, the display changes to the screen shown in the center of Figure 1-8. This screen displays, by way of example and not by way of limitation, the continuation of the detailed information of the dunning information that was displayed on the screen on the left side of FIG. 1-8, among the detailed information of the dunning information. Also, in this screen, as an example and not a limitation, the description of the parts that are the same as the screen on the left side of FIG. 1-8 described above will be omitted.

[0165] In this example, the reminder information display area RR displays, by way of example and not limitation, information about the money loan service provider that sent the reminder (Money Loan Co., Ltd., telephone number: TT-TTTT-TTTT, etc.) and information for making the payment of the reminder (information including a repayment button HBT containing the words "repay").

[0166] By way of example and not limitation, when the user scrolls to view the bottom of the screen, the display changes to the screen shown on the right side of Figure 1-8. This screen displays, by way of example and not by way of limitation, the continuation of the detailed information of the dunning information that was displayed on the screen in the center of FIG. 1-8, among the detailed information of the dunning information. Also, in this screen, as an example and not a limitation, the description of the parts that are similar to the screen in the center of FIG. 1-8 described above will be omitted.

[0167] In this example, the reminder information display area RR displays, by way of example and not limitation, information regarding the loan balance (loan balance ZZ,ZZZ yen), information regarding the final loan date (January 1, 2023), information regarding the final loan balance (final post-loan balance ZZ,ZZZ yen), information regarding the loan date (contract date January 1, 2023), information regarding the loan interest rate (loan interest rate 15%), information regarding the late payment penalty interest rate (late payment penalty rate 20%), and information regarding the money loan service provider that sent this reminder (sender: Money Loan Co., Ltd., address: PPP-PPPP, Minato-ku, Tokyo..., person in charge: ○○○○, etc.).

[0168] Then, by way of example and not limitation, when the user taps the repayment button HBT on the screen in the center of Figure 1-8 or the screen on the right side of Figure 1-8, a repayment screen for actually making the repayment may be displayed (not shown), by way of example and not limitation. On this repayment screen, for example and not by way of limitation, the repayment method (electronic money payment, bank transfer, etc.) may be set, and actual payment may be made using the set repayment method.

[0169] <Processing> FIG. 1-9 is a flowchart showing an example of the flow of processing executed by each device in this embodiment. In this figure, from the left, an example of a process executed by the control unit 21 of the terminal 20A of the user AA and an example of a process executed by the control unit 11 of the server 10 are shown.

[0170] Note that the processes described below are merely examples of processes for implementing the method of the present disclosure, and the present disclosure is not limited to these. Another step may be added to the process described below, or some steps may be omitted (deleted) from the process described below.

[0171] First, the control unit 21 of the terminal 20A transmits borrowing request information to the server 10 via the communication I / F 22 to request borrowing a loan from a money loan service provider based on an input to the input / output unit 23 of the terminal 20A (by way of example and not limitation, a user input (such as a user's operational input or sound input) (the same applies below)). Here, the borrowing request information may include, for example and without limitation, any combination of one or more of information such as the desired borrowing amount, the desired repayment period, the desired transfer destination financial institution account, the desired contracted repayment amount, etc. It may also include information that can identify user AA (or terminal 20A) (information such as an application ID).

[0172] When borrowing request information is received from terminal 20A via communication I / F 14, control unit 11 of server 10 executes a loan condition calculation process (S110). In the loan condition calculation process, control unit 11 of server 10 calculates loan conditions (for example and not limitation, loan amount, loan interest rate, contracted repayment start date, and contracted repayment amount) available for loaning to the user based on the received borrowing request information and user information (for example and not limitation, other registered information in account registration data 153).

[0173] In general, the calculation method for loan terms is kept confidential, so the specific calculation formula is not disclosed. However, the calculation method of the loan conditions may be made public, and if so, the loan conditions may be calculated based on that calculation method.

[0174] Then, the control unit 11 of the server 10 transmits loan condition information including the calculated loan conditions to the terminal 20A via the communication I / F 14 (S120).

[0175] When the loan condition information is received from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received loan condition information (A120). As an example and not as a limitation, if it is determined that the user of terminal 20A agrees to the loan conditions based on user input for the displayed loan condition information, the control unit 21 of terminal 20A transmits loan condition approval information to server 10 via communication I / F 22 (A130).

[0176] When it is determined that loan condition approval information has been received from the terminal 20A via the communication I / F 14, the control unit 11 of the server 10 executes the loan process (S130). In the loan processing, the control unit 11 of the server 10, by way of example and not limitation, sends transfer request information via the communication I / F 14 to a financial institution server (not shown) to transfer or transfer the loan amount calculated in the loan condition calculation processing from the financial institution account of the money loan service provider to the financial institution account (financial institution name, branch name, transfer destination account number, receiving account name) specified in the borrowing request information. When the transfer process is completed at the financial institution, the control unit 11 of the server 10 receives transfer completion information from the financial institution server. The control unit 11 of the server 10 then adds the loan balance in the loan management data of the account management database 155A based on the loan amount. The control unit 11 of the server 10 also updates each element in the loan management data of the account management database 155A based on the calculated loan condition information, by way of example and not limitation.

[0177] In addition, the financial institution account to which the money is deposited in the loan process may be, for example and without limitation, an account of an electronic money service affiliated with the money loan service provider.

[0178] Thereafter, the control unit 11 of the server 10 transmits the loan result information to the terminal 20A via the communication I / F 14 (S140). Here, the loan result information may include, by way of example and not limitation, any combination of the following information. - Loan amount in loan processing (borrowing amount from the perspective of user AA) - Loan balance after loan processing (borrowing balance from the perspective of user AA) -Scheduled repayment start date -Scheduled repayment dates (or repayment frequency) after the scheduled repayment start date -Scheduled repayment amount for each scheduled repayment date

[0179] When the loan result information is received from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received loan result information (A140).

[0180] In the following, by way of example and not limitation, steps A110 to A140 and steps S110 to S140 may be collectively referred to as a borrowing process (A100·S100).

[0181] Then, the control unit 11 of the server 10 determines, by way of example and not limitation, whether or not a dunning information transmission condition, which is a condition for transmitting dunning information to the terminal 20, is satisfied (S150).

[0182] The conditions for sending the dunning information may include, by way of example and not limitation, the following conditions: “J01”: A certain number of days have passed since the scheduled repayment date without repayment.

[0183] However, in this example, it is assumed that the user may make a repayment (early repayment) before the scheduled repayment date. In addition, the "state of not being repaid" may be understood to mean "the entire amount of the agreed repayment amount not being repaid." In addition, the specified number of days may be set by the server 10 based on information input by the money loan service provider (which may be considered as a setting by the money loan service provider), or may be automatically set by the server 10.

[0184] As a non-limiting example, if the dunning information transmission condition is set to "J01" and the specified number of days is set to "10 days," the dunning information transmission condition will be met for the first time at 0:00 on the 11th day from the scheduled repayment date if no repayment has been made, and the first dunning information will be sent to terminal 20.

[0185] In this example, a condition for resending the dunning information (hereinafter referred to as a "dunning information resending condition") may be set. This is not a limitation, but may be regarded as a condition for re-dunning (re-dunning condition) including the meaning of reminding the user of the dunning. Specifically, by way of example and not limitation, in the above example, if no repayment has been made, the condition for resending dunning information may be met at 00:00 on the 12th day from the scheduled repayment date, and a second dunning information may be sent to terminal 20. Thereafter, if the repayment continues to be unspent, similar control may be performed, and dunning information may be repeatedly sent to the terminal 20. That is, in this example, by way of example and not limitation, the reminder information may be repeatedly transmitted to the terminal 20 every time one day passes. Note that this is merely an example, and the dunning information may be repeatedly transmitted every few hours, or may be transmitted at irregular times.

[0186] In this case, the same dunning information may be transmitted the first time (initial time) and the second time and thereafter, or different dunning information may be transmitted. Furthermore, the second time, different reminder information is sent than the first time, but from the third time onwards, the same reminder information as the second time may be sent.

[0187] When it is determined that the dunning information transmission condition is not satisfied (S150: NO), the control unit 11 of the server 10 ends the process, for example and not for limitation.

[0188] When it is determined that the dunning information transmission condition is met (S150: YES), the control unit 11 of the server 10 transmits the dunning information to the terminal 20A via the communication I / F 14, for example and not for limitation (S160). This prompting information may include, by way of example and not limitation, the following items of information: Trade name, business name or name, address and telephone number of the person engaged in the employment business Name of the person sending the document or electromagnetic record ·Contract date Loan amount Loan interest rate - Payment deadline for claims related to payment demands - Amount to be paid The amount of the remaining debt at the time of the payment demand Breakdown of the amount to be demanded for payment (principal, interest, and compensation for non-performance of obligation (including late payment penalty rate))

[0189] When the dunning information is received from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received dunning information (A150), and ends the process.

[0190] As described above, the server 10 may transmit dunning information (demand letter) to the terminal 20, and may also transmit, as a non-limiting example, delinquent notice information equivalent to a delinquent notice or demand information equivalent to a demand letter to the terminal 20. In this case, the server 10 may transmit delinquent notice information first, and then transmit dunning information when a certain period of time has passed, and then transmit demand information when a further certain period of time has passed.

[0191] One idea of ​​the present invention is that when a user is behind on repayment, an information processing device such as a server may transmit (in digital form) information informing the user of this fact and information encouraging the user to repay to the user's terminal 20, and as a non-limiting example, when the repayment deadline for the loaned amount has passed, the server 10 may transmit at least information on the loan amount and loan interest rate to the terminal 20. In addition to this information, the various types of information listed above may be additionally transmitted to this information. Furthermore, this information may be sent in the form of any of the above-mentioned written documents, such as a delinquent notice, a reminder, or a demand letter (including this information in the written document), by way of example and not limitation. The same applies below.

[0192] Also, for each repayment, if the repayment deadline has passed, by way of example and not by way of limitation, a delinquent notice may be sent the first time and a demand letter may be sent the second time. In this case, in the above condition of "J01", by way of example and not by way of limitation, the predetermined number of days for sending a delinquent notice may be set to "3 days" and the predetermined number of days for sending a demand letter may be set to "10 days". The predetermined number of days may be set arbitrarily by the money loan service provider. Also, the overdue notice may not be sent. The same applies below.

[0193] Furthermore, in cases where laws, regulations, or the like prescribe information that must be included in a document requesting a debtor, etc. to make a payment, the information to be transmitted may be determined based on such provisions. In countries where there is no such provision, the information to be transmitted may be freely determined. Even if there is such a provision, if laws, regulations, etc. are amended and the information that must be included in documents changes, the information to be transmitted may be determined based on the provision. The same applies below.

[0194] <Effects of the First Embodiment> In this embodiment, the control unit 11 controls the server 10 (not limited to, but an example of a server that communicates with a user's terminal) to store information on the loan amount (not limited to, but an example of information on the amount loaned to the user) in the memory unit 15. If the repayment deadline has passed, the server 10 is configured to transmit information on the loan amount (not limited, but an example of information on the loan amount) and information on the loan interest rate (not limited, but an example of information on the loan interest rate) to the terminal 20 via the communication I / F 14. As an example of the effect of an embodiment obtained by such a configuration, when the repayment deadline for the loaned amount has passed, the server can transmit information about the amount loaned to the user and the interest rate on the loan to the terminal, thereby informing the user of this, by way of example and not limitation.

[0195] In this case, the server 10 may transmit information on the late payment charge rate to the terminal 20 via the communication I / F 14 if the repayment deadline has passed. As an example of the effect of an embodiment obtained by such a configuration, when the repayment deadline for the loaned amount has passed, the server can transmit information on the late payment penalty rate to the terminal, thereby, by way of example and not limitation, informing the user of the late payment penalty rate.

[0196] In this case, the server 10 may transmit information on the contract date relating to the final borrowing date to the terminal 20 via the communication I / F 14 if the repayment deadline has passed. As an example of the effect of an embodiment obtained by such a configuration, when the repayment deadline for the loaned amount has passed, the server can transmit information of the contract date relating to the last borrowing date to the terminal, thereby informing the user of the contract date relating to the last borrowing date, by way of example and not limitation.

[0197] In addition, this embodiment shows a configuration in which, if the repayment deadline has passed, the server 10 sends a reminder letter to the terminal 20 via the communication I / F 14, which includes the above-mentioned information on the loan amount (not limited to this, but an example of information on the loan amount) and the above-mentioned information on the loan interest rate (not limited to this, but an example of information on the loan interest rate). As an example of the effect of an embodiment obtained by such a configuration, when the repayment deadline for the loaned amount has passed, the server can send a reminder letter to the terminal containing information on the amount loaned to the user and the interest rate on the loan, thereby realizing, by way of example and not limitation, a reminder for repayment by sending a reminder letter.

[0198] This embodiment shows a configuration in which, when the repayment deadline has passed, the terminal 20 receives information on the loan amount (not limited to, but an example of information on the loan amount) and information on the loan interest rate (not limited to, but an example of information on the loan interest rate) from the server 10 via the communication I / F 22. As an example of the effect of an embodiment obtained by such a configuration, when the repayment deadline for the loaned amount has passed, the terminal can receive information on the amount loaned to the user and the interest rate on the loan from the server, and by way of example and not limitation, can inform the user of this. As described above, the terminal 20 may receive information such as information on the late fee rate and information on the contract date related to the final borrowing date from the server 10. Also, as described above, a demand letter may be received from the server 10.

[0199] Furthermore, the terminal 20 may display the above-mentioned various information on the display unit 24. In this case, the terminal 20 may perform scroll control based on a scroll operation on the display unit 24 by the user to update the information display.

[0200] <First Modification (1)> In the above embodiment, the dunning information is displayed vertically on the display unit 24 of the terminal 20 that received the dunning information, and the user can scroll vertically to view the part of the dunning information that cannot be displayed in the maximum size that can be displayed at one time on the display unit 24 (in this example, the size of the dunning information display area RR), but this is not limiting. As a non-limiting example, the dunning information may be displayed in a display method different from the above-mentioned display method.

[0201] In this modified example, as a display method of the dunning information, for example and not by way of limitation, a display method may be adopted in which dunning information divided into pieces of dunning information (hereinafter referred to as "divided dunning information") at the maximum size that can be displayed at one time on the display unit 24 (in this example, the size of the dunning information display area RR) is displayed on the display unit 24 of the terminal 20 that received the dunning information, and the user can view other divided dunning information by scrolling (sliding) the divided dunning information horizontally. In other words, the divided dunning information is arranged horizontally, and any of the divided dunning information is displayed on the display unit 24 by the user scrolling (sliding) horizontally. Hereinafter, such a display method will be referred to as the "carousel method" or the like, as appropriate.

[0202] In this carousel method, by way of example and not limitation, when first installment reminder information is displayed on display unit 24, when the first installment reminder information is slid horizontally by the user to display second installment reminder information, by way of example and not limitation, a portion of the first installment reminder information may be displayed on display unit 24 while a portion of the second installment reminder information is displayed on display unit 24 (framing out and then framing in).

[0203] <Display screen> FIG. 1-10 is a diagram showing an example of transition of a screen displayed on the display unit 24 of the terminal 20A in this modified example. This screen image shows, by way of example and not limitation, an example in which, similar to the first embodiment, a user of terminal 20 borrows 30,000 yen from a money loan service provider at an annual interest rate of 15%, and a reminder letter is sent because the user fails to make a repayment on the first scheduled repayment date. However, this is merely an example and is not limited to this example.

[0204] The screen on the left side of FIG. 1-10 is an example and not a limitation, and description of the parts that are similar to the screen on the left side of FIG. 1-8 described above will be omitted. In this example, the words "[Important] Payment Information (1 / 3)" are displayed at the bottom center of the top of the screen, based on the fact that a reminder message has been received and that this is the first of three reminder messages that have been split into parts for display in a carousel format. Additionally, at the bottom center of the screen, information for making payment of the reminder (a button containing the word "repay") is displayed.

[0205] By way of example and not limitation, when the dunning information display region RR is scrolled leftward by the user to view the right side of the display unit 24, the display changes to the screen shown in the center of FIG. 1-10, by way of example and not limitation. This screen shows, by way of example and not by way of limitation, the second of a three-part reminder message. This screen is an example and not a limitation, and the description of the parts that are similar to the screen in the center of FIG. 1-8 described above will be omitted.

[0206] In this example, the words "[Important] Payment Information (2 / 3)" are displayed at the bottom center of the top of the screen, based on the fact that a reminder message has been received and that this is the second of three reminder messages that have been split into three for display in a carousel format. Additionally, at the bottom center of the screen, information for making payment of the reminder (a button containing the word "repay") is displayed.

[0207] By way of example and not limitation, when the dunning information display area RR is scrolled leftward by the user to view the right side of the display unit 24, the display changes to the screen shown on the right side of FIG. 1-10, by way of example and not limitation. This screen shows, by way of example and not by way of limitation, the third of a three-part reminder message. This screen is an example and not a limitation, and the description of the parts that are similar to the screen on the right side of FIG. 1-8 described above will be omitted.

[0208] In this example, the text "[Important] Payment Information (3 / 3)" is displayed at the bottom center of the top of the screen, based on the fact that a reminder message has been received and that this is the third instalment of a reminder message that has been split into three for display in a carousel format. Additionally, at the bottom center of the screen, information for making payment of the reminder (a button containing the word "repay") is displayed.

[0209] As shown in FIG. 1-10, when the dunning information is displayed in a carousel format, by way of example and not limitation, information for making a dunning payment (repayment button HBT) may be always displayed in a predetermined area of ​​the screen. With this configuration, even if any installment dunning information among the dunning information is being viewed, there is a lead line for making a dunning payment, so that the convenience of the user regarding payments can be improved.

[0210] In this modified example, the terminal 20 displays the reminder information on the display unit 24 in a carousel format. As an example of the effect of the modified example obtained by such a configuration, the user can perform a scroll operation (slide operation) on the display unit 24 on which one divided piece of dunning information is displayed, thereby causing other divided pieces of dunning information to be displayed on the display unit 24.

[0211] <First Modification (2)> In the above embodiment, an example was shown in which the dunning information transmission condition is set to be whether or not a predetermined number of days has passed since the contract repayment date, but this is not limiting. As a non-limiting example, other conditions may be set as the dunning information transmission condition in addition to or instead of whether or not a predetermined number of days has passed since the contract repayment date.

[0212] <Processing> The flow of the process executed by each device in this modified example is not limited to the above, but may be the same as that shown in FIG. 1-9, and therefore a description thereof will be omitted.

[0213] In this case, the conditions constituting the dunning information transmission conditions may include, by way of example and not limitation, the following: “J01”: A certain number of days have passed since the scheduled repayment date without repayment “J02”: The loan amount was equal to or greater than the specified amount “J03”: The interest rate on the loan was equal to or higher than the specified rate “J04”: Credit score was below a certain level

[0214] "J02": the loan amount was equal to or greater than a predetermined amount" may include, by way of example and not limitation, a case in which the amount loaned by the money loan service provider to the user was equal to or greater than a predetermined amount. Specifically, this condition may be satisfied when the amount loaned by the money loan service provider to the user is 10,000 yen or more. Note that the amount may be greater than a predetermined amount.

[0215] "J03": the interest rate of the loan was equal to or higher than the specified interest rate" may include, by way of example and not limitation, a case where the interest rate of the loan provided by the money loan service provider to the user is equal to or higher than the specified interest rate. Specifically, this condition may be satisfied when the interest rate of the loan provided by the money loan service provider to the user is 17% or higher. Note that the interest rate may be higher than the specified interest rate.

[0216] "J04": credit score was below a predetermined score" may include, by way of example and not limitation, a case where the credit score of a user to whom a money loan service provider has provided a loan is below a predetermined score. Specifically, this condition may be satisfied when the credit score of a user to whom a money loan service provider has provided a loan is below 550 points out of a maximum of 1000 points. It may also be less than the predetermined score. The credit score may be, for example and not limitation, an example of an index value indicating the degree (level) of a user's estimated social credit, and, for example and not limitation, the higher the value, the higher the user's estimated social credit.

[0217] The credit score of the user may be calculated and acquired by the server 10, or may be received and acquired by the server 10 from an external device that calculates the credit score of the user. Also, a business operator such as a money loan service business operator may calculate the credit score and input it to the server 10, and the credit score may be stored in the memory unit 15 of the server 10.

[0218] Here, the control unit 11 of the server 10 may, by way of example and not limitation, determine that the dunning information transmission condition is met (S150: YES) when at least one or more of the conditions constituting the dunning information transmission conditions "J01" to "J04" described above are met.

[0219] In addition, as a pattern of a combination of conditions for determining that the dunning information transmission condition is satisfied (S150: YES), the following combination patterns may be included as examples and not limitations. Note that "'J01' and 'J02'" indicates, as an example and not a limitation, a combination pattern in which the condition "J01" is satisfied and the condition "J02" is satisfied. "J01" "J01" and "J02" "J01", "J02" and "J03" "J01", "J02", "J03" and "J04"

[0220] Similarly, the conditions for re-transmission of dunning information mentioned above may include, in addition to or instead of the time-related conditions mentioned above (conditions based on time or date), conditions based on the loan amount, conditions based on the loan interest rate, conditions related to the user's creditworthiness, etc. By way of example and not limitation, users with lower credit scores may be resent dunning information more frequently (more frequently) than users with higher credit scores.

[0221] Also, by way of example and not limitation, if a user's credit score is above a predetermined score (or equal to or greater than a predetermined score), server 10 may be configured not to transmit information about the loan amount and the loan interest rate to terminal 20 even if the repayment deadline has passed.

[0222] This modified example shows a configuration in which, when the repayment deadline has passed, the server 10 transmits the above-mentioned information on the loan amount (not limited to, but an example of information on the loan amount) and the above-mentioned information on the loan interest rate (not limited to, but an example of information on the loan interest rate) to the terminal 20 via the communication I / F 14 based on information on the user's credit score. As an example of the effect of the modified example obtained by such a configuration, when the repayment deadline has passed and the user's credit score is below a certain level (or less than a certain level), the server can send information on the amount lent and the interest rate lent to the terminal.

[0223] <First Modification (3)> In the above embodiment, the dunning information received by the terminal 20 is displayed in a money loan application, but the present invention is not limited to this. For example and not for limitation, the dunning information received by the terminal 20 may be displayed in an application other than the money loan application. In this modification, the dunning information received by the terminal 20 is displayed in a messaging application different from the money loan application.

[0224] <Display screen> 1-11 is a diagram showing an example of a transition of a screen displayed on the display unit 24 of the terminal 20A in this modified example. Note that, in the following, the process executed by the terminal 20 is illustrated and described as a process executed by the terminal 20A of the user AA, by way of example and not by way of limitation.

[0225] This screen image shows, by way of example and not limitation, an example in which a user of terminal 20 borrows 30,000 yen from a money loan service provider at an annual interest rate of 15%, and a reminder letter is sent because the user fails to make a repayment on the scheduled repayment date. At this time, an example is shown in which a message regarding a demand letter sent from a money loan service provider in a messaging application is sent to the terminal 20A via the server 10. However, this is merely an example and is not limited to this example.

[0226] The left side of FIG. 1-11 shows an example of a talk room screen in a messaging application on the terminal 20A. At the top of the screen is the name of the messaging application (in this example, "Messaging App"), and to the right of that is an app information display area that includes an icon image of the user (in this example, the icon image of user AA) and the user name (in this example, user AA).

[0227] Below that, a talk room name display area CLR including the name of the talk room (hereinafter referred to as the "talk room name") is provided as a type of area indicating which page (in this example, the talk room) in the messaging application is currently displayed. The talk room name display area CLR can also be considered an area indicating the page (in this example, the talk room) in the messaging application where the user is currently located.

[0228] The talk room name display area CLR displays, by way of example and not limitation, information indicating that this is an OA talk room in which user AA can talk with "Money Loan Service," a company that provides money loan services (in this example, an icon indicating OA and the words "Money Loan Service")

[0229] Below that is a talk area TR for user AA and the money loan service to talk in an interactive format, with message information (message) sent from the other party, the money loan service, displayed on the left side of the screen, and message information from user AA itself displayed on the right side of the screen.

[0230] In this example, message information regarding a reminder letter is sent from the money loan service, and based on terminal 20A receiving this message information via server 10, this message information is displayed on the left side of the OA talk room screen in association with an icon image of the money loan service. This message information is not limited to this, but is an example that is similar to the detailed information of the reminder information shown on the left side of FIG. 1-8 described above, so a description thereof will be omitted.

[0231] By way of example and not limitation, when the user scrolls down the screen in the left side of FIG. 1-11, the display changes to the screen in the center of FIG. 1-11. This screen displays, by way of example and not by way of limitation, the continuation of the message information displayed on the left screen of FIG. 1-11 among the message information related to the collection notice. This message information is not limited to any particular information, but is similar to the detailed information of the reminder information in the center of FIG. 1-8, and therefore will not be described here.

[0232] For example and not for limitation, when the user scrolls down the screen in the center of FIG. 1-11, the display changes to the screen in the right side of FIG. 1-11. This screen displays, by way of example and not by way of limitation, the continuation of the message information displayed on the screen in the center of FIG. 1-11, among the message information related to the collection notice. This message information is not limited to any particular information, but is similar to the detailed information of the reminder information on the right side of FIG. 1-8 described above, and therefore will not be described here.

[0233] This modified example shows a configuration in which the server 10 transmits information on the loan amount (not limited to, but an example of information on the loan amount) and information on the loan interest rate (not limited to, but an example of information on the loan interest rate) to a talk room (not limited to, but an example of a chat room) including the user via the communication I / F 14. As an example of the effect of the modified example obtained by such a configuration, information on the amount lent to the user and the interest rate on the loan can be transmitted by the server to a chat room including the user, so that this information can be displayed in the chat room. In terminal 20, information on the loan amount (not limited to this, but an example of information on the loan amount) and information on the loan interest rate (not limited to this, but an example of information on the loan interest rate) can be displayed in a talk room (not limited to this, but an example of a chat room) including the user, which is displayed on display unit 24, thereby making it possible to inform the user of this information by displaying it in the chat room.

[0234] <Second Example> When repayment of a money loan is behind, the user and the money loan service provider may agree on a date for repayment (hereinafter referred to as a "repayment promise", "deposit promise", etc., as appropriate). Such repayment promises are generally made over the telephone, which requires the money loan service provider to keep a record of the telephone conversations, resulting in considerable costs.

[0235] In this embodiment, the repayment promise between the user and the money loan service provider is made on the web, by way of example and not by way of limitation. By making the repayment promise on the web, the task of storing the history of the promise is also simplified, and the cost can be reduced.

[0236] In this embodiment, as an example of a repayment promise between a user and a money loan service provider made on the web, a non-limiting example will be described using a money loan application.

[0237] The contents described in the second embodiment are applicable to any of the other embodiments and other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0238] <System configuration> FIG. 2-1 shows an example of the data structure of the account management data 155B, which is an example of the account management database 155 in this embodiment. Description of parts that are the same as those in the account management database 155A of FIG. 1-5 described above will be omitted.

[0239] The loan management data is, by way of example and not by way of limitation, data for storing information regarding a loan contract that a money loan service provider will lend to a user who is the account holder of this application ID, and by way of example and not by way of limitation, the loan date, loan balance, loan interest rate, agreed repayment amount, agreed repayment start date, late payment interest rate, late payment amount, and other loan information, as well as the promised repayment date, are stored in association with each other.

[0240] The repayment promise date may be, by way of example and not limitation, information regarding the date of the repayment promise specified by the user of the terminal 20, and may be information that is updated and stored by the control unit 11 of the server 10.

[0241] <Display screen> FIG. 2-2 is a diagram showing an example of transition of a screen displayed on the display unit 24 of the terminal 20A in this embodiment. This screen diagram shows, as an example and not a limitation, an example in which, similar to the first embodiment, a user of terminal 20 borrows 30,000 yen from a money loan service provider at an annual interest rate of 15%, and a reminder letter is sent to the user because the user fails to make a repayment on the scheduled repayment date, and a repayment schedule is set from that reminder letter. However, this is merely an example and is not limited to this example.

[0242] The screen on the left side of FIG. 2-2 is an example of a reminder information display screen, by way of example and not limitation. This screen is an example and not a limitation, and the description of the parts that are similar to the screen on the right side of FIG. 1-8 described above will be omitted.

[0243] In this example, below the information for making this reminder payment (the repayment button HBT containing the word "Repay") is information for setting up a repayment agreement (in this example, the message "If you have decided on a repayment schedule, you can set up your repayment schedule from the link below," and the repayment agreement button HYBT containing the word "Set up a repayment schedule").

[0244] By way of example and not limitation, when the user taps the repayment promise button HYBT on the screen on the left side of FIG. 2-2, the display changes to the screen shown in the center of FIG. 2-2.

[0245] This screen is, by way of example and not limitation, a repayment promise setting screen for setting a repayment promise, and a message is displayed at the top of the screen encouraging the user to specify the repayment promise date (scheduled repayment date, promised repayment date). Below that, by way of example and not limitation, a promised repayment date designation area for designating the promised repayment date on the calendar, and a designated promised repayment date display area in which the promised repayment date designated on the calendar is displayed are configured to be displayed.

[0246] In the promised repayment date designation area, by way of example and not limitation, a black circle indicating the current date is displayed at "February 13, 2023," and a white circle indicating that the promised repayment date is designated by the user's tap operation is displayed at "February 15, 2023."

[0247] As a method for specifying the promised repayment date in this promised repayment date specification area, the following method may be used as an example and is not limited thereto. Drum roll method Direct input method

[0248] The drum roll method is a method for specifying a promised repayment date using, by way of example and not limitation, a drum roll type object provided in the promised repayment date specification area that the user can scroll to specify a date.

[0249] The direct input method is, by way of example and not limitation, a method in which a user can specify a date by directly inputting text or the like provided in a repayment promise date specification area.

[0250] The specified promised repayment date display area displays, by way of example and not limitation, the promised repayment date (scheduled repayment date: February 15th) specified in the promised repayment date specification area.

[0251] Also displayed below this are a Decision button DBT (a button containing the word "Decide") for deciding on the promised repayment date specified by the user in the promised repayment date specification area as the final promised repayment date, and a Back button (a button containing the word "Back") for returning from this screen to the previous screen.

[0252] As an example, and not as a limitation, when the promised repayment date (February 15th) is specified in the promised repayment date specification area and the decision button DBT is tapped, as an example, and not as a limitation, repayment promise information is sent from the terminal 20 to the server 10 based on the contents specified in the promised repayment date specification area, and as an example, and not as a limitation, the display changes to the screen shown on the right side of Figure 2-2.

[0253] This screen is, by way of example and not by way of limitation, a screen that notifies the user that the setting of the promised repayment date specified by the user on the repayment promise setting screen has been completed, and by way of example and not by way of limitation, information indicating that setting of the scheduled repayment date has been completed is displayed.

[0254] FIG. 2-3 is a diagram showing an example of a pattern different from that shown in FIG. 2-2 described above, among examples of screen transitions displayed on the display unit 24 of the terminal 20A in this embodiment. This screen diagram shows, as an example and not a limitation, an example in which, similar to the first embodiment, a user of terminal 20 borrows 30,000 yen from a money loan service provider at an annual interest rate of 15%, and a reminder letter is sent because the user fails to make a repayment on the agreed repayment date, and the reminder letter includes a repayment promise date designation area for specifying the promised repayment date on a calendar. However, this is merely an example and is not limited to this example.

[0255] The screen on the left side of FIG. 2-3 is an example of a reminder information display screen, by way of example and not by way of limitation. This screen is an example and not a limitation, and a description of the parts that are similar to the screen on the left side of FIG. 2-2 described above will be omitted. In this example, information for setting a repayment promise is displayed below the message "If you have decided on a repayment schedule, you can set up your repayment schedule from the link below," along with information encouraging the user to specify the date of the repayment promise (scheduled repayment date, promised repayment date) (in this example, the message "Please select the scheduled repayment date") and a promised repayment date specification area for specifying the promised repayment date from a calendar. And below that, as an example and not a limitation, a repayment promise button HYBT is displayed that includes the words "Set a repayment schedule" from the information for setting a repayment promise.

[0256] As an example and not as a limitation, when a user taps “February 15, 2023” in the repayment promise date designation area on the screen on the left side of Figure 2-3 and then taps the repayment promise button HYBT, the display will change to the screen shown on the right side of Figure 2-3, as an example and not as a limitation. This screen is similar to the screen on the right side of FIG. 2-2 described above, but is not limited thereto, and therefore a description thereof will be omitted.

[0257] With this configuration, a user can be provided with a guide for selecting and setting a scheduled repayment date from a calendar while scrolling through the reminder notice, thereby improving convenience when setting a repayment promise.

[0258] <Processing> FIG. 2-4 is a flowchart showing an example of the flow of processing executed by each device in this embodiment. In this figure, from the left, an example of a process executed by the control unit 21 of the terminal 20A and an example of a process executed by the control unit 11 of the server 10 are shown. Regarding this flowchart, explanation of the parts that are the same as those in FIG. 1-9 described above will be omitted.

[0259] In this flowchart, the reminder information in S160 and A150 may include, by way of example and not limitation, information for setting a repayment promise (hereinafter referred to as "information for setting a repayment promise"). This repayment promise setting information may include, by way of example and not limitation, information on the reminder information display screen informing the user that a repayment promise can be set (such as a message such as "If you have decided on your repayment schedule, you can set your repayment schedule from the link below"), information regarding a link to transition to a page for making a repayment promise (repayment promise setting screen) (such as a repayment promise button HYBT containing the words "Set repayment schedule"), information regarding a message on the repayment promise setting screen encouraging the user to specify the repayment promise date (scheduled repayment date, promised repayment date), information regarding the promised repayment date specification area, and information regarding the specified promised repayment date display area.

[0260] After A150, the control unit 21 of the terminal 20A transmits the repayment promise information to the server 10 via the communication I / F 22 based on an input to the input / output unit 23 of the terminal 20A, for example and not by way of limitation (A210). This repayment promise information may include, for example and without limitation, information on the promised date of deposit (scheduled deposit date, promised repayment date, scheduled repayment date) and information on the amount of the planned repayment (hereinafter referred to as the "scheduled repayment amount"), etc. It may also include information that can identify the user AA (or the terminal 20A) (information such as an application ID).

[0261] When the repayment promise information is received from the terminal 20A via the communication I / F 14, the control unit 11 of the server 10 executes a repayment promise update process (S210). In the repayment promise update process, the control unit 11 of the server 10 stores the received repayment promise information in user information (for example and not limitation, the repayment promise date of the account management data 155B).

[0262] Then, the control unit 11 of the server 10 transmits repayment promise update information including the repayment promise date stored in the account management data to the terminal 20A via the communication I / F 14 (S220).

[0263] When the repayment promise update information is received from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received repayment promise update information (A220).

[0264] Also, in this process, instead of the server 10 transmitting dunning information including information for setting a repayment promise to the terminal 20, by way of example and not limitation, it may transmit overdue notice information (information equivalent to the above-mentioned overdue notice) including information for setting a repayment promise to the terminal 20 (S160). Then, as in this process, it may be possible for the user to make a promise to repay from this overdue notice information. That is, in the terminal 20, the overdue notice information may be displayed on the display unit 24 (A150), and the repayment promise information may be transmitted from the terminal 20 to the server 10 based on a user input for the displayed overdue notice information (A210).

[0265] <Effects of the second embodiment> In this embodiment, the server 10 (not limited to this, but an example of a server) receives repayment promise information (not limited to this, but an example of information on a promise to deposit money based on the loan amount) from the terminal 20 via the communication I / F 14. The server 10 then shows a configuration in which the control unit 11 controls the storage of the received repayment promise information in the storage unit 15. As an example of the effect of the embodiment obtained by such a configuration, information regarding a promise of payment based on the loan amount can be received from the terminal and stored in the storage unit.

[0266] In this case, the repayment promise information may also include information regarding the promised date of payment. As an example of the effect of the embodiment obtained by such a configuration, the server can receive information on the promise of deposit, including information on the promised deposit date, from the terminal and store it in the memory unit. As a result, the server side (money loan service provider side) can grasp and manage the promised deposit date.

[0267] In this case, if the repayment deadline has passed, the server 10 transmits dunning information (not limited to, an example of a dunning notice, an example of a first dunning notice) including information on the loan amount and information on the loan interest rate to the terminal 20 via the communication I / F 14. Then, the server 10 may receive the above-mentioned repayment promise information from the terminal 20 via the communication I / F 14 based on an input by the user in response to the sent dunning notice. As an example of the effect of an embodiment obtained by such a configuration, information regarding the promise to pay the payment can be sent from the terminal to the server based on the user's input in response to a reminder letter (first reminder letter) sent from the server to the terminal, thereby improving convenience.

[0268] <Second Modification Example (1)> In the above embodiment, when the promised repayment date is set, the repayment amount corresponding to the promised repayment date is not displayed on the display unit 24 of the terminal 20, but this is not limiting. As a non-limiting example, when the promised repayment date is set, the repayment amount corresponding to the promised repayment date may be displayed on the display unit 24 of the terminal 20.

[0269] <Display screen> FIG. 2-5 is a diagram showing an example of transition of a screen displayed on the display unit 24 of the terminal 20A in this modified example. This screen diagram shows, by way of example and not limitation, an example in which the promised repayment dates are specified as "February 15th" and "February 16th" when setting a repayment schedule from a reminder letter, as in the second embodiment. However, this is merely an example and is not limited to this example.

[0270] The left screen in FIG. 2-5 is the same as the center screen in FIG. 2-2, so a description thereof will be omitted. In this example, below the specified promised repayment date display area, based on the promised repayment date (February 15th) specified by the user in the promised repayment date specification area, information regarding the amount to be claimed (scheduled amount to be claimed: M, MMM yen) and information regarding the breakdown of the amount to be claimed (principal A, AAA yen, accrued interest BBB yen, late payment charges DDD yen) are displayed, by way of example and not limitation.

[0271] By way of example, and not by way of limitation, when the user taps the promised repayment date (February 16th) in the promised repayment date designation area, the display changes to the screen shown on the right side of Figure 2-5. This screen is an example and not a limitation, and the description of the parts that are similar to the screen on the left side of FIG. 2-5 described above will be omitted.

[0272] In this example, below the specified promised repayment date display area, based on the promised repayment date (February 16th) specified by the user in the promised repayment date specification area, by way of example and not limitation, information regarding the amount to be claimed (scheduled amount to be claimed: N, NNN yen) and information regarding the breakdown of the amount to be claimed (principal A, AAA yen, accrued interest BBB yen, late payment charges EEE yen) are displayed.

[0273] In this way, when setting a promised repayment date, the user is presented with the planned repayment amount and its breakdown (especially late payment charges) for the specified date each time the user specifies a promised repayment date, so the user can see at a glance the balance between the promised repayment date and the repayment amount, and can make a reasonable repayment schedule.

[0274] FIG. 2-6 is a diagram showing an example of a pattern different from that shown in FIG. 2-5 described above, among examples of transitions of screens displayed on the display unit 24 of the terminal 20A in this modified example. In this screen diagram, as an example and not a limitation, an example is shown in which the promised repayment date is specified as "February 15th" when setting a repayment schedule from a reminder letter, as in the second embodiment. However, this is merely an example and is not limited to this example.

[0275] The screen on the left side of FIG. 2-6 is an example and not a limitation, and description of the parts that are similar to the screen on the left side of FIG. 2-5 described above will be omitted. In this example, based on the user specifying the promised repayment date (February 15th) in the promised repayment date specification area, by way of example and not limitation, information regarding the scheduled repayment date etc. specified by the user is displayed in a speech bubble near (in this example, above) the date specified by the user in the promised repayment date specification area. This speech bubble information (speech bubble information) may include, by way of example and not limitation, information regarding the scheduled repayment date specified by the user (scheduled repayment date: February 15th), information regarding the amount to be claimed (scheduled amount to be claimed: M, MMM yen), and information for displaying a breakdown of the amount to be claimed (link information including the words "breakdown").

[0276] As a non-limiting example, when the user taps on link information including the text "Details" in the speech bubble information on the left side of FIG. 2-6, the display changes to the screen on the right side of FIG. 2-6, as a non-limiting example.

[0277] In this screen, by way of example and not limitation, based on the user tapping on link information containing the word "Details" in the speech bubble information, the speech bubble information displays, by way of example and not limitation, information regarding the breakdown of the amount to be billed (principal A, AAA yen, accrued interest BBB yen, late payment charges DDD yen, etc.) in addition to the various information mentioned above.

[0278] In this example, the user simply specifies the promised payment date (scheduled repayment date) on the calendar, and information about the repayment in the case of making the repayment on that date is displayed near the specified date. This allows the user to easily check information about the repayment while selecting a date on the calendar, and appropriately supports the user in setting the repayment promise (payment promise).

[0279] <Processing> In the flowchart showing an example of the flow of processes executed by each device in this modified example, the description of the parts that are the same as those in FIG. 2-4 described above will be omitted.

[0280] In this modification, the reminder information sent by the control unit 11 of the server 10 to the terminal 20A in S160 may include, by way of example and not limitation, information on candidate dates that the user can select when setting the repayment promise (hereinafter, appropriately referred to as "candidate repayment promise dates") and the scheduled repayment amounts corresponding to those candidate repayment promise dates (including a breakdown of late payment charges, etc.). Information on these candidate repayment promise dates and scheduled repayment amounts is appropriately referred to as "advance repayment promise information."

[0281] For example and not limitation, the reminder information may include, as potential promised repayment dates, dates from the current date and time when step S160 is being executed up to one month in the future, and may include information regarding the scheduled repayment amount (including a breakdown of late payment charges, etc.) corresponding to each date for that one month.

[0282] In A150, when dunning information including repayment promise advance information is received from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received dunning information. Here, when the user taps the information for setting a repayment promise (the repayment promise button HYBT) among the reminder information, and then specifies a date (proposed repayment date) in the repayment promise date specification area of ​​the repayment promise setting screen, the scheduled repayment amount corresponding to that date is displayed.

[0283] In addition, in S160, the dunning information transmitted by the control unit 11 of the server 10 to the terminal 20A may not include information regarding a specific repayment promise candidate date or a scheduled repayment amount, for example and not by way of limitation. In S160, the dunning information transmitted by the control unit 11 of the server 10 to the terminal 20A may not include information regarding a specific repayment promise candidate date or a scheduled repayment amount, but may include information regarding the loan balance, the contracted repayment start date, and the late payment damage interest rate, and therefore the control unit 21 of the terminal 20A that has received the dunning information may, for example and not by way of limitation, calculate the scheduled repayment amount (including a breakdown of late payment damages, etc.) corresponding to each date based on this information, and display it on the display unit 24.

[0284] Also, by way of example and not limitation, when a date (candidate repayment date) is specified by the user in the promised repayment date specification area on the promised repayment setting screen, terminal 20A requests information on the planned repayment amount corresponding to that date from server 10 (queries server 10 about the planned repayment amount corresponding to that date). Then, information on the planned repayment amount may be transmitted from server 10 to terminal 20.

[0285] In this modified example, the server 10 transmits information on the scheduled repayment amount based on the loan amount to the terminal 20 via the communication I / F 14, based on an input by the user in response to the demand notice (first demand notice). As an example of the effect of an embodiment obtained by such a configuration, based on the user's input in response to the reminder letter (first reminder letter), information on the scheduled repayment amount based on the loan amount can be sent to the terminal, and the user of the terminal can be informed of the scheduled repayment amount.

[0286] <Second Modification Example (2)> In the case where a repayment promise is made by the user as described above, and the deadline for this repayment promise is not met, a reminder may be sent.

[0287] In this modified example, as an example and not a limitation, a second dunning notice may be sent based on the expiration of a set promised repayment date, which is different from the dunning notice sent based on the fulfillment of the dunning information transmission condition shown in <First embodiment>. Note that, for convenience, the dunning notice sent based on the fulfillment of the dunning information transmission condition shown in <First embodiment> is referred to as the "first dunning notice."

[0288] Here, the first demand notice may be, for example and not for limitation, an example of the demand information in S160 or A150. Also, the second demand notice may be, for example and not for limitation, an example of the second demand information in S240 or A230.

[0289] This second reminder may, by way of example and not limitation, be the same in content as the first reminder, or may be different in content than the first reminder. If the second demand letter is different from the first demand letter, then, by way of example and not limitation, the second demand letter may be more forceful in requesting repayment than the first demand letter.

[0290] <Processing> FIG. 2-7 is a flowchart showing an example of the flow of processes executed by each device in this modified example. In this figure, from the left, an example of a process executed by the control unit 21 of the terminal 20A and an example of a process executed by the control unit 11 of the server 10 are shown. In this flowchart, by way of example and not limitation, the description of parts that are similar to those in FIGS. 2-4 above will be omitted.

[0291] After S220, the control unit 11 of the server 10 determines, by way of example and not limitation, whether a second dunning information transmission condition, which is a condition for transmitting the second dunning information to the terminal 20, is satisfied (S230).

[0292] The second dunning information transmission conditions may include, by way of example and not limitation, the following: “K01”: The promised repayment date has passed without any repayment

[0293] “K01: the promised repayment date has passed without repayment” is, by way of example and not by way of limitation, a case in which the repayment has not been made even after the promised repayment date set by the user has passed, and, by way of example and not by way of limitation, this condition is met at 0:00 on the day following the promised repayment date.

[0294] When it is determined that the second dunning information transmission condition is not satisfied (S230: NO), the control unit 11 of the server 10 ends the process, for example and not for limitation.

[0295] When it is determined that the second dunning information transmission condition is met (S230: YES), the control unit 11 of the server 10 transmits the second dunning information to the terminal 20A via the communication I / F 14, for example and not for limitation (S240).

[0296] When the second urging information is received from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received second urging information (A230), and ends the process.

[0297] In this modification, if the repayment deadline has passed, the server 10 transmits a first demand notice including information on the loan amount and the loan interest rate to the terminal 20 via the communication I / F 14. The server 10 may then receive the above-mentioned repayment promise information from the terminal 20 via the communication I / F 14 based on an input by the user in response to the transmitted first demand notice. As an example of the effect of the modified example obtained by such a configuration, information regarding the promise to pay the payment can be sent from the terminal to the server based on the user's input in response to the first reminder sent from the server to the terminal, thereby improving convenience.

[0298] In this case, the second demand notice, which is sent later than the first demand notice, may be sent from the server 10 to the terminal 20 by the communication I / F 14 based on the promised payment date. As an example of the effect of the modified example obtained by such a configuration, the second demand notice can be transmitted to the terminal after the first demand notice based on the promised payment date.

[0299] Furthermore, this modified example shows a configuration in which the server 10 transmits information on the scheduled repayment amount based on the loan amount to the terminal 20 via the communication I / F 14, based on an input by the user in response to the first demand notice. As an example of the effect of this modified example obtained by such a configuration, information on the scheduled repayment amount based on the amount lent can be sent to the terminal based on the user's input in response to the first reminder, thereby informing the user of the terminal of the scheduled repayment amount.

[0300] <Second Modification Example (3)> When a user has made a repayment promise as described above, even if the repayment amount has not been repaid and the conditions for resending dunning information are met, the sending of a dunning reminder may be restricted.

[0301] Specifically, as an example and not a limitation, in the processing of Figure 2-4, in step A150, based on user input for the displayed reminder information, repayment promise information is sent from the terminal 20 to the server 10 (A210), and when the control unit 11 of the server 10 executes the repayment promise update process (S210), as an example and not a limitation, a flag (hereinafter referred to as the "retransmission restriction flag" as appropriate) for restricting the sending of reminders or reminders of reminders may be set (the flag may be turned ON). Then, based on the fact that this resend restriction flag is set, a reminder of dunning information (a reminder of a dunning letter) may not be sent to the terminal 20 even if the dunning information resend condition is met.

[0302] However, if a user has made a repayment promise, even if the repayment amount has not been repaid and the condition for resending the reminder information is met, a reminder letter may be sent (the sending restriction may be lifted) if the promised repayment date has passed. Specifically, when the promised repayment date updated in the promised repayment update process has passed, the control unit 11 of the server 10, by way of example and not limitation, erases the retransmission restriction flag (sets the flag to OFF). Then, if the dunning information resend condition is met based on the fact that the resend restriction flag is not set, a dunning information reminder (a dunning notice reminder) may be sent to the terminal 20.

[0303] Furthermore, when a repayment promise is made by the user as described above, the timing of sending a reminder of the dunning letter to the terminal 20 may be determined based on the user's credit score, for example and not by way of limitation.

[0304] As an example and not by way of limitation, if the credit score is equal to or greater than a predetermined score (or above the predetermined score), the period before a reminder of the dunning letter is sent to terminal 20 may be increased, and if the credit score is less than the predetermined score (or below the predetermined score), the period before a reminder of the dunning letter is sent to terminal 20 may be decreased.

[0305] Specifically, as a non-limiting example, if the credit score is 550 points or more, a reminder for a dunning letter will not be sent to terminal 20 for three days after the dunning information resend condition is met for the first time, and a reminder for a dunning letter will be sent to terminal 20 at 00:00 on the fourth day after the dunning information resend condition is met for the first time. On the other hand, for example and not by way of limitation, if the credit score is below 550 points, a reminder of the dunning notice may be sent to the terminal 20 as soon as the dunning information re-sending condition is met for the first time.

[0306] In this way, a user whose credit score is equal to or greater than a predetermined number is presumed to have a certain degree of social credibility, and therefore a certain degree of grace period can be given before a reminder of a dunning letter is sent to the terminal 20. On the other hand, since a user whose credit score is below a certain level may have low social credibility, it is possible to more reliably encourage repayment by not giving him or her a grace period until a reminder of the dunning letter is sent to the terminal 20.

[0307] Further, as a non-limiting example, a stepped threshold value may be set as the credit score threshold value. In this case, by way of example and not limitation, the higher the credit score is at (or above) the threshold, the longer the period before a dunning reminder is sent to the terminal 20 . Also, by way of example and not limitation, if the credit score is at or above a top threshold value (or above the threshold value), dunning information may not be resent.

[0308] Additionally, regardless of whether or not a repayment promise has been made by the user, the timing of sending a reminder letter (including a reminder letter) to the terminal 20 may be determined based on, for example and not by way of limitation, the user's credit score.

[0309] As a non-limiting example, when the conditions for sending reminder information are met regardless of whether or not a repayment promise has been made by the user, if the credit score is equal to or above a specified score (or exceeds the specified score), the period until a reminder notice is sent to terminal 20 may be lengthened, and if the credit score is below the specified score (or below the specified score), the period until a reminder notice is sent to terminal 20 may be shortened.

[0310] Specifically, as a non-limiting example, if the credit score is 550 points or more, a reminder notice may not be sent to terminal 20 for three days after the reminder information transmission condition is met for the first time, and a reminder notice may be sent to terminal 20 at 00:00 on the fourth day after the reminder information transmission condition is met for the first time. On the other hand, for example and not by way of limitation, if the credit score is below 550 points, a dunning reminder may be sent to the terminal 20 as soon as the dunning information sending condition is met for the first time.

[0311] Also, by way of example and not limitation, the conditions for sending dunning information for a user for subsequent repayments may be changed based on the user's credit score. Specifically, as an example and not a limitation, when applying the aforementioned dunning information transmission condition "J01": a specified number of days have passed since the scheduled repayment date without repayment, the higher the credit score, the longer the specified number of days for the next and subsequent repayments may be set. The same may be applied to the conditions for resending the dunning information next time and thereafter.

[0312] <Second Modification Example (4)> When a repayment promise is made by the user as described above, information regarding the repayment promise may be transmitted from the server 10 to the terminal 20 around the promised repayment date. This information may be regarded as, for example and not as a limitation, information that reminds the user of the promise of repayment (deposit) (reminder information regarding the promise of repayment).

[0313] The period before and after the promised repayment date may include, by way of example and not by way of limitation, a period of a predetermined number of days before and after the promised repayment date set by the user. As an example of the period of a predetermined number of days before and after the promised repayment date, the following periods (A) to (G) may be included by way of example and not by way of limitation. (A): The period from three days before the promised repayment date to the promised repayment date. (B): On the promised repayment date (C): The period from the end of the repayment date to three days after the repayment date. (D): (A) + (B) (E):(B)+(C) (F): (A) + (C) (G): (A) + (B) + (C)

[0314] Additionally, the information regarding the promise to repay may include, by way of example and not limitation, at least one of the following: ·Dunning information Information regarding dunning reminders - Information that is different from information regarding dunning information or dunning information reminders

[0315] Here, information that is different from dunning information or information related to a reminder of dunning information may be, by way of example and not by way of limitation, information that is different from a dunning letter or a reminder and does not include the various information that should constitute the aforementioned dunning letter or reminder (the trade name, title or name, address, and telephone number of the person operating the wage business, the name of the person sending the document or electronic record, the date of the contract, the amount of the loan, the interest rate of the loan, the repayment deadline for the claim related to the payment demand, the amount of the payment demand, the amount of the remaining debt related to the demand at the time of the payment demand, the breakdown of the amount of the payment demand, etc.). As examples, but not limited to, the information may include information sent before the promised repayment date to notify that the promised repayment date is approaching (as an example, but not limited to, information including a message such as "The promised repayment date set by the customer is approaching"), information sent on the promised repayment date to notify that it is the promised repayment date (as an example, but not limited to, information including a message such as "Today is the promised repayment date set by the customer"), and information sent after the promised repayment date to notify that the promised repayment date has passed (as an example, but not limited to, information including a message such as "The promised repayment date set by the customer has arrived, but the payment has not been confirmed").

[0316] In addition, the timing of transmitting the information regarding the repayment promise may be determined based on the user's credit score. For example and not limitation, if the credit score is equal to or greater than a predetermined score (or exceeds the predetermined score), it is presumed that the user has high credit, so that, for example and not limitation, information may not be sent before the promised repayment date (excluding the period (A) above) and the period (E):(B)+(C) above may be set. Information may also not be sent on the promised repayment date (excluding the period (B) above) and the period (C) above may be set. On the other hand, if the credit score is below a specified score (or equal to or less than the specified score), the user is presumed to have low creditworthiness, and the period for transmitting information may be set to the above (G):(A)+(B)+(C) period.

[0317] Further, as a non-limiting example, a stepped threshold value may be set as the credit score threshold value. In this case, by way of example and not limitation, the more the credit score is at (or above) a higher threshold, the less frequently information may be sent. Also, by way of example and not limitation, if the credit score is at or above a top threshold value (or above the threshold value), then the above information may not be sent.

[0318] <Second Modification (5)> In addition to the displays exemplified above, various displays can be made to be displayed as displays that enable the user to make a repayment promise (deposit promise). Here, by way of example and not limitation, an example is given of a display in which, when a user makes a repayment promise, the user is allowed to set the reason for the overdue repayment (hereinafter referred to as the "reason for overdue payment" or may be referred to as the "reason for delay" etc.) from the reminder letter.

[0319] 2-8 and 2-9 are diagrams showing an example of a screen displayed on the display unit 24 of the terminal 20A in this modified example. This screen may be displayed as a separate screen by a link when the repayment promise button HYBT is tapped by the user on the screen on the left side of FIG. 2-2, and may be displayed by scrolling through the reminder information, for example and not for limitation.

[0320] The screen on the left side of Figure 2-8 displays a message prompting the user to enter the reason for late payment and the scheduled repayment date, by way of example and not limitation, in the event that payment is difficult on the scheduled repayment date, and below that is an area for displaying the reason for late payment, which allows the user to select and display the reason for late payment. In this modified example, a case where the user selects and inputs the reason for overdue payment as a self-report from this screen will be illustrated.

[0321] In the overdue reason display area, for example and not for limitation, a pull-down menu is used to allow the user to select a reason for overdue from among multiple candidates for reasons for overdue that are set in advance by the money loan service. Alternatively, the user may directly input the reason for overdue using a keyboard or the like. In addition, a decision button DBT is displayed at the bottom of the screen, but in this example, it is in a state where no operation is accepted until the reason for the late payment and the scheduled repayment date are selected, and by way of example and not limitation, the decision button DBT is displayed in a disabled state (grayed out on the display screen).

[0322] This example display screen is configured, by way of example and not limitation, so that when a user selects a reason for delinquency that the money loan service provider has pre-set as a reason for delinquency for which a repayment promise can be registered from this screen (hereinafter referred to as a "specific reason for delinquency") from among multiple candidate reasons for delinquency set by the money loan service provider, the user can input the scheduled repayment date (promised date of deposit).

[0323] As candidates for the reason for overdue, for example and without limitation, it may be possible to set reasons for overdue that are difficult or impossible for the server 10 to detect, or reasons for overdue that are presumed to be known by the user. As examples and without limitation, it may be possible to set reasons for overdue such as "due to a decrease in income," "due to an increase in expenditure," "due to an unexpected expense," "due to being hospitalized," and "due to an accident." However, the reasons for overdue may not be limited to these.

[0324] In addition, reasons such as insufficient electronic money balance and improper electronic money linkage, which will be described later in the sixth embodiment, may also be reasons for overdue payment. These may be considered as reasons for overdue payment that the server 10 can detect or that the user may not be aware of. These reasons for overdue do not have to be included in the above candidate reasons for overdue, but since the user may be aware of these reasons for overdue, they may be included in the above candidate reasons for overdue.

[0325] The center of Figure 2-8 shows the state in which a reason for overdue has been selected by the user. In this example, "due to reduced income" is displayed in the reason for delinquency display area based on the user's selection of "due to reduced income" as the reason for delinquency. In this example, by way of example and not limitation, a scheduled repayment date input area for inputting a scheduled repayment date is additionally displayed below the reason for delinquency display area based on the fact that the selected reason for delinquency "due to reduced income" corresponds to a specific reason for delinquency. Since the scheduled repayment date has not been entered, the decision button DBT remains in a disabled state.

[0326] The right side of Figure 2-8 shows the state after the scheduled repayment date has been entered by the user. In this example, the user inputs "2020 / 02 / 15" as the scheduled repayment date, which is displayed in the scheduled repayment date display area. In this example, the estimated amount to be claimed, including late fees, in the case where repayment is made on the inputted estimated repayment date is displayed below the estimated repayment date display area based on the input estimated repayment date. Other information, such as information on the rate of late fees, may also be displayed.

[0327] Furthermore, based on the input of the reason for overdue payment and the scheduled repayment date, the disablement state of the decision button DBT is released, making it ready to accept operations. When the decision button DBT is tapped by the user, repayment promise information including, by way of example and not limitation, the reason for the overdue payment and information on the scheduled repayment date may be transmitted from the terminal 20A to the server 10. Then, based on the received information, the server 10 can store the reason for overdue and the scheduled repayment date in the account management data in association with the application ID of the user AA (or the terminal 20A).

[0328] FIG. 2-9 shows an example of a display screen when a reason for overdue payment different from the reason for overdue payment selected in FIG. 2-8 is selected by the user. The screen on the left side of Figure 2-9 is the same as the screen on the left side of Figure 2-8, and in the screen on the right side of Figure 2-9, "Due to hospitalization" is displayed in the reason for overdue display area based on the user selecting "Due to hospitalization" as the reason for overdue. However, in this example, by way of example and not limitation, the selected reason for late payment, "due to hospitalization," does not fall under the specific reason for late payment, so the area for inputting the scheduled repayment date is not displayed, as in the screen on the right side of Figure 2-8. Instead, it is not possible to register a repayment promise from this screen for the selected reason for late payment, and a message urging the user to contact the company via the inquiry form, and an inquiry form button FBT for displaying the inquiry form screen are displayed. When the inquiry form button FBT is tapped by the user, by way of example and not limitation, an inquiry form screen (not shown) is displayed on the display unit 24, and the user is configured to be able to make individual inquiries about the repayment promise from that screen.

[0329] To realize the above display, the terminal 20 may determine whether the selected reason for delinquency corresponds to a specific reason for delinquency, and if it determines that it corresponds, it may display a display for inputting the scheduled repayment date. On the other hand, if it determines that the selected reason for delinquency does not correspond to a specific reason for delinquency, the terminal 20 may display a display for making an inquiry from the above inquiry form. Alternatively, when a reason for overdue is selected by the user, the terminal 20 may transmit information on the selected reason for overdue to the server 10, and the server 10 may determine whether or not the reason for overdue corresponds to a specific reason for overdue. The server 10 may then transmit the result of the determination to the terminal 20, and the terminal 20 may perform the above display according to the result of the determination received from the server 10.

[0330] Also, as a non-limiting example, information on the scheduled repayment date may be input regardless of the reason for overdue selected by the user, and once the reason for overdue and information on the scheduled repayment date are transmitted from the terminal 20 to the server 10, the server 10 may determine whether or not the reason for overdue corresponds to a specific reason for overdue. If it is determined that the reason for overdue does not correspond to a specific reason for overdue, the server 10 may transmit information to the terminal 20 urging the user to submit detailed information on the reason for overdue.

[0331] In addition, without setting a specific reason for overdue payment, and regardless of the reason for overdue payment, the user may be able to register a repayment promise from the display shown in either Figure 2-8 or Figure 2-9, which is an example and not a limitation.

[0332] In this modified example, the repayment promise information (not limited to this, an example of information regarding a promise of payment based on the loan amount) includes information regarding the promised payment date. As an example of the effect of the modified example obtained by such a configuration, the server can receive information on the promise of deposit, including information on the promised deposit date, from the terminal and store it in the memory unit. As a result, the server side (money loan service provider side) can grasp and manage the promised deposit date.

[0333] In addition, this modified example shows a configuration in which the repayment promise information (not limited to, but an example of information regarding a promise to pay based on the amount lent) includes information regarding the reason for the delay in repayment (reason for overdue payment, reason for delay). As an example of the effect of the modified example obtained by such a configuration, the server can receive information on the promise of deposit including information on the reason for the overdue repayment from the terminal and store it in the memory unit. As a result, the server side (the money loan service provider side) can understand and manage the reason for the overdue repayment.

[0334] <Second Modification (6)> The above embodiment and modifications may be applied to the configuration shown in <First Modification (3)> in which the reminder information received by the terminal 20 may be displayed in a messaging application. In this modification, a case will be described in which the configuration of <Modified Example 1 (3)> is applied to <Modified Example 2 (1)> as an example and not a limitation.

[0335] <Display screen> 2-10 is a diagram showing an example of the transition of screens displayed on the display unit 24 of the terminal 20 in this modified example. Note that, in the following, the process executed by the terminal 20 will be illustrated and described as the process executed by the terminal 20A of the user AA, by way of example and not by way of limitation.

[0336] This screen diagram shows an example of a case where the user sets the promised repayment date to February 15th when setting a repayment schedule after receiving a reminder letter. At this time, an example is shown in which a message regarding a demand letter sent from a money loan service provider in a messaging application is sent to the terminal 20A via the server 10. However, this is merely an example and is not limited to this example.

[0337] In addition, the OA account (money loan service provider) of the OA talk room here may be an account operated by a human, or an account (chatbot account) operated by an AI (bot) described later.

[0338] In this example, the account of the terminal 20A is the account of "user AA", and the account of the chatbot, which is a business operator, is the chatbot of "money loan service". The "money loan service" account is an example of an account operated by an AI (bot) associated with the OA account "money loan service", which is a business operator.

[0339] The screen on the left side of FIG. 2-10 is, by way of example and not limitation, similar to the screen on the right side of FIG. 1-11 described above, and therefore a description thereof will be omitted.

[0340] As an example and not as a limitation, when a user inputs into the input / output unit 23 of the terminal 20A (entering text into the text input area in the center of the bottom of the screen and tapping the send button to send the entered text), the display changes to the screen shown in the center of Figure 2-10, as an example and not as a limitation.

[0341] In this example, as an example and not a limitation, based on the text "I would like to make an appointment to pay" being entered by the user, message information sent from user AA (in this example, the message "I would like to make an appointment to pay") is displayed on the right side of the OA talk room screen. Below that, as a non-limiting example, based on the message information of user AA, "I would like to make a payment promise," message information sent from the OA account (money loan service) (in this example, the message "Please specify a date") is displayed on the left side of the OA talk room screen.

[0342] Below that, as an example and not a limitation, based on the text "February 15th" entered by the user, message information sent from user AA (in this example, the message "February 15th") is displayed on the right side of the OA Talk Room screen. Below that, as an example and not a limitation, based on the message information for "February 15th" from user AA, message information sent from the OA account (money loan service) is displayed on the left side of the OA chat room screen (in this example, the message "If you set Wednesday, February 15th as the scheduled repayment date, the amount you will have to pay will be as follows. Do you want to set this date as the scheduled repayment date?", along with information about the scheduled amount to be charged and its breakdown (principal, accrued interest, late payment charges, etc.)).

[0343] Below that, as an example and not by way of limitation, based on the text "Yes" entered by the user, message information (in this example, the message "Yes") sent from user AA is displayed on the right side of the OA Talk Room screen.

[0344] As an example and not as a limitation, when a user inputs information into the input / output unit 23 of the terminal 20A (entering text into the text input area in the center of the bottom of the screen and tapping the send button to send the entered text), the display changes to the screen shown on the right side of Figure 2-10, as an example and not as a limitation.

[0345] On this screen, as a non-limiting example, based on the message information of user AA selecting "Yes," message information sent from the OA account (money loan service) (in this example, the message "The repayment date has been set for Wednesday, February 15th," and information regarding the amount to be billed and its breakdown (principal, accrued interest, late payment charges, etc.)) is displayed on the left side of the OA chat room screen.

[0346] In this modified example, the server 10 transmits information on the loan amount and the loan interest rate to a chat room (not limited to, but an example of a chat room including users) including the user of the terminal 20 via the communication I / F 14. The server 10 then receives payment promise information via the communication I / F 14 based on an input to this chat room by the user of the terminal 20. As an example of the effect of the modified example obtained by such a configuration, information on the loan amount and the loan interest rate can be sent to a chat room including the user. This makes it possible to display a chat room including this information on the user's terminal. Then, based on the user's input to this chat room, information regarding the promise of payment can be received from the terminal.

[0347] <Third Example> This embodiment is an embodiment in which the user confirms the repayment amount. A conduit for the user to confirm the repayment amount may be provided in the money loan application, for example and not by way of limitation, or in the messaging application, for example and not by way of limitation. In this embodiment, a conductor for a user to confirm a repayment amount is provided, for example and not by way of limitation, in a money loan application.

[0348] The contents described in the third embodiment are applicable to any of the other embodiments and other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0349] <Display screen> FIG. 3-1 is a diagram showing an example of transition of a screen displayed on the display unit 24 of the terminal 20A in this embodiment. This screen diagram shows, as an example and not a limitation, an example in which, similar to the first embodiment, a user of terminal 20 borrows 30,000 yen from a money loan service provider at an annual interest rate of 15%, and a reminder letter is sent because the user fails to make a repayment on the scheduled repayment date, and the current repayment amount can be confirmed from the reminder letter. However, this is merely an example and is not limited to this example.

[0350] The screen on the left side of FIG. 3-1 is an example of a reminder information display screen, by way of example and not limitation. This screen is an example and not a limitation, and the description of the parts that are similar to the screen on the left side of FIG. 1-8 described above will be omitted.

[0351] In this example, below the information regarding the breakdown of the billed amount at the time the reminder letter was sent (principal A, AAA yen, accrued interest BBB yen, late payment charges CCC yen), information for confirming the repayment amount is displayed, by way of example and not limitation (in this example, the message "You can check the latest repayment amount from the link below," and a repayment amount confirmation button HMBT containing the words "Check repayment amount").

[0352] By way of example and not limitation, when the user taps the repayment amount confirmation button HMBT on the screen on the left side of FIG. 3-1, the display changes to the screen on the right side of FIG. 3-1.

[0353] This screen is, by way of example and not limitation, a repayment amount confirmation screen for confirming the repayment amount, and based on the current date being February 15th, repayment amount information (in this example, a message regarding the repayment amount (the message "The billing amount as of Wednesday, February 15th, 2023 is as follows," the words "Latest billing amount: M,MMM yen," information regarding the breakdown, etc.)) is displayed.

[0354] Techniques for verifying the repayment amount may include, by way of example and not limitation, the following: -Check from the reminder button Go to your Money Loan application page and check Check with messaging applications

[0355] "Confirming via the button on the reminder letter" may, by way of example and not limitation, be a method in which the user can confirm the repayment amount by inputting (tapping) a button on the reminder letter, and repayment amount information is displayed on display unit 24.

[0356] "Go to My Page of the money loan application and check" may mean, by way of example and not limitation, a method of checking loan information including information regarding the repayment amount on My Page by displaying My Page of the money loan application (by way of example and not limitation, a page for setting user information (name, address) and checking loan information (loan amount, repayment amount, repayment date, etc.)).

[0357] By way of example and not limitation, "checking via a messaging application" may refer to a method of checking the repayment amount by displaying message information including information regarding the repayment amount sent from the money loan service on display unit 24 in response to a message sent by a user inquiring about the repayment amount in an OA talk room where a conversation takes place between a user of a messaging application and an OA of a money loan service provider.

[0358] Regardless of which of the above methods is used to check the repayment amount, for example and not limitation, the user may be allowed to specify the date for which the repayment amount is to be checked. As shown in the center screen of Figure 2-2 above, an area may be displayed for the user to specify the date on a calendar that he or she wishes to check.

[0359] <Processing> FIG. 3-2 is a flowchart showing an example of the flow of processes executed by each device in this embodiment. In this figure, from the left, an example of a process executed by the control unit 21 of the terminal 20A and an example of a process executed by the control unit 11 of the server 10 are shown. Regarding this flowchart, explanation of the parts that are the same as those in FIG. 2-4 described above will be omitted.

[0360] After A150, the control unit 21 of the terminal 20A sends amount confirmation request information to the server 10 via the communication I / F 22 to request confirmation of the repayment amount based on an input to the input / output unit 23 of the terminal 20A, for example and not by way of limitation (A310). This amount confirmation request information may include, by way of example and not limitation, information regarding the application ID of the user of terminal 20A, information regarding the current date and time, information regarding the date specified by the user, and the like.

[0361] Upon receiving the amount confirmation request information, the control unit 11 of the server 10 transmits repayment amount information including information related to the repayment amount to the terminal 20A via the communication I / F 14 (S310). This repayment amount information may include, by way of example and not by way of limitation, information regarding the current repayment amount, and, by way of example and not by way of limitation, may include information regarding the repayment amount corresponding to a date specified by the user.

[0362] In addition, this information regarding the repayment amount may include, by way of example and not limitation, information regarding the repayment amount that the user needs to repay to the money loan service provider based on the amount lent by the money loan service provider to the user.

[0363] When the repayment amount information is received from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received repayment amount information (A320).

[0364] <Effects of the third embodiment> This embodiment shows a configuration in which the server 10 transmits repayment amount information (not limited to, but an example of information regarding the repayment amount that the user needs to repay, based on the amount lent) to the terminal 20 via the communication I / F 14, based on input by the user of the terminal 20. As an example of the effect of an embodiment obtained by such a configuration, based on input by the user, information regarding the repayment amount that the user needs to repay, based on the amount lent, is transmitted to the terminal, thereby informing the user of the terminal of the repayment amount.

[0365] In this case, the server 10 may also transmit repayment amount information (not limited to this, but an example of information regarding the repayment amount that the user needs to repay, based on the amount lent) to the terminal 20 via the communication I / F 14 based on input by the user of the terminal 20 into a talk room (not limited to this, but an example of a chat room) including the user of the terminal 20. As an example of an effect of an embodiment obtained by such a configuration, based on input by a user into a chat room including the user, information regarding the repayment amount that the user needs to repay, based on the amount lent, is sent to the terminal, thereby informing the user of the terminal of the repayment amount.

[0366] <Fourth Example> The fourth embodiment is an embodiment in which the reminder letter is provided with a guide for the user to select the loan repayment method.

[0367] The contents described in the fourth embodiment are applicable to any of the other embodiments and other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0368] In this embodiment, the loan repayment methods that a user may select may include, by way of example and not limitation, the following: Electronic money repayment · Bank transfer repayment Although the present specification uses a "bank" as an example, it may be another financial institution.

[0369] By way of example and not limitation, electronic money repayment may be a repayment method in which an amount owed by a user to a money loan service provider is paid using electronic money. This repayment method may be, by way of example and not limitation, a repayment method in which a user repays the repayment amount in electronic money using an electronic money service affiliated with the money loan service provider.

[0370] By way of example and not limitation, bank transfer repayment may be a repayment method in which the amount owed by the user to the money loan service provider is paid by bank transfer. Hereinafter, bank transfer repayment will be referred to as "account transfer repayment", "bank account transfer repayment", etc. as appropriate. Specifically, the repayment method may be such that the user transfers the amount to be repaid to a bank account opened by the money loan service provider at a bank.

[0371] This bank account may or may not be a user-specific (application ID-specific) bank account, for example and not by way of limitation, and may be a real bank account that is generally provided to a subscriber by a bank, or may be a virtual bank account that is different from a real bank account.

[0372] In this embodiment, the bank account used in the bank transfer repayment method may be, by way of example and not by way of limitation, a bank account dedicated to the user (dedicated to the application ID) that is opened by the money loan service provider approaching the bank, and by way of example and not by way of limitation, a virtual bank account (hereinafter referred to as a "virtual account", "virtual account", etc., as appropriate). However, this is merely an example and is not limited to this example.

[0373] <Display screen> FIG. 4-1 is a diagram showing an example of transition of a screen displayed on the display unit 24 of the terminal 20A in this embodiment. This screen diagram shows, as an example and not a limitation, an example in which, similar to the first embodiment, a user of terminal 20 borrows "30,000 yen" from a money loan service provider at an annual interest rate of 15%, and a reminder letter is sent to the user because the user fails to make a repayment on the scheduled repayment date, and the user can select a repayment method from the reminder letter. However, this is merely an example and is not limited to this example.

[0374] The screen on the left side of FIG. 4-1 is an example of a reminder information display screen, by way of example and not limitation. This screen is an example and not a limitation, and the description of the parts that are similar to the screen in the center of FIG. 1-8 described above will be omitted.

[0375] In this example, the reminder information display area RR displays, by way of example and not limitation, information for making this reminder payment, such as an electronic money repayment button DHBT containing the words "Repay with electronic money" for making repayment with electronic money, and a bank transfer repayment button BHBT containing the words "Repay by account transfer (virtual account)" for making repayment by bank transfer.

[0376] By way of example and not limitation, when the bank transfer repayment button BHBT on the screen on the left side of FIG. 4-1 is tapped by the user, the display changes to the screen on the right side of FIG. 4-1, by way of example and not limitation.

[0377] This screen is, by way of example and not limitation, a bank transfer screen for making repayments by bank transfer, and displays bank account information (in this example, information about a bank account (virtual account) opened exclusively for the user for transfers (bank name, bank number, branch name, branch number, account type, account number), an online bank transfer button NBBT (a button containing the words "Transfer via online bank") for making transfers via an internet bank that handles banking transactions over the web, etc.).

[0378] In this way, the user can select from the reminder whether to make repayment by electronic money or by bank transfer, thereby improving convenience regarding repayment.

[0379] <Processing> As a flowchart showing an example of the flow of processing executed by each device in this embodiment, the same flowchart as that shown in FIG. 1-9 can be applied, and therefore a description thereof will be omitted.

[0380] In this embodiment, the reminder information sent from the control unit 11 of the server 10 to the terminal 20A in S160 may include, by way of example and not limitation, bank account information (bank name, bank number, branch name, branch number, account type, account number, etc.) for repaying the loan balance and the agreed repayment amount by bank transfer.

[0381] <Effects of the Fourth Embodiment> This embodiment shows a configuration in which the server 10 transmits information about an account (not limiting, but an example of account information for making repayments) for making repayments of the loaned amount (not limiting, but an example of account information for making repayments, as examples and not limiting, a real account or a virtual account) to the terminal 20 via the communication I / F 14, based on input by the user of the terminal 20 regarding dunning information (not limiting, but an example of a dunning letter). As an example of the effect of an embodiment obtained by such a configuration, based on the user's input in response to the reminder letter, account information for making repayments of the loaned amount is sent to the terminal, thereby informing the user of the account for making repayments of the loaned amount.

[0382] <Fifth Example> The fifth embodiment relates to changing the format of the reminder letter depending on the repayment status (repayment situation) of the user.

[0383] The contents described in the fifth embodiment are applicable to any of the other embodiments and other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0384] An example of a user's repayment status in this embodiment may include, by way of example and not limitation, the status of the user's electronic money balance. As an example and not as a limitation, if the electronic money balance is greater than the repayment amount, a normal reminder letter may be sent to the user, and, as an example and not as a limitation, if the electronic money balance is less than the repayment amount, a reminder letter different from the normal reminder letter (hereinafter referred to as a "special reminder letter" as appropriate) may be sent to the user.

[0385] Note that examples of the repayment status of the user are not limited to the above examples. As a non-limiting example, the repayment status of the user may include whether or not the user's account for the money loan service and the account for the electronic money service are linked. As an example and not as a limitation, if the user's money loan service account and electronic money service account are linked, a normal type of reminder letter may be sent to the user, and as an example and not as a limitation, if the user's money loan service account and electronic money service account are not linked, a special type of reminder letter may be sent to the user.

[0386] As a non-limiting example, when a request for account linking with an electronic money service is received in advance from terminal 20, server 10 may perform inter-service account linking processing with the server of the electronic money service (hereinafter referred to as the "electronic money service server"). In the inter-service account linking process, as an example and not a limitation, account information for each service may be sent and received between server 10 and the electronic money service server, and in each server, the account management data for the user may be stored in association with the account (as an example and not a limitation) for the mutual service. The inter-service account linking process may be performed when the user requests account linking with the money loan service from the electronic money service.

[0387] Also, in this case, the electronic money service server may obtain information regarding the user's repayment (information, by way of example and not limitation, regarding the agreed repayment date, the repayment amount on the agreed repayment date, the bank account for transfer designated by the money loan service provider (by way of example and not limitation, a real account) etc.) from the server 10. Then, by way of example and not limitation, when the agreed repayment date arrives, the electronic money service server may transfer the repayment amount from the user's electronic money balance to the bank account for transfer of the money loan service provider by performing an electronic money transfer process.

[0388] A normal type of reminder letter may be, for example and without limitation, a reminder letter that has a lead line only for electronic money repayment as a repayment method. Specifically, the screen of a normal reminder notice may be, by way of example and not by way of limitation, a screen such as that shown in FIG. 1-8, and, by way of example and not by way of limitation, when the repayment button HBT is tapped by the user, the screen may transition to a screen for making electronic money repayment.

[0389] Furthermore, a special type of reminder letter may be, for example and without limitation, a reminder letter that has two leads for repayment methods: electronic money repayment and bank transfer repayment. Specifically, the screen for the special type of reminder notice may be, by way of example and not by way of limitation, a screen such as that shown in FIG. 4-1, and by way of example and not by way of limitation, when the electronic money repayment button DHBT is tapped by the user, the screen may transition to a screen for making an electronic money repayment, and when the bank transfer repayment button BHBT is tapped by the user, the screen may transition to a screen for making a bank transfer repayment.

[0390] However, this is merely an example and is not limiting. By way of example and not limitation, differences between regular and special demand letters may include the following: -Whether there is a link to inquire about repayment methods -Whether there is a path to further borrowing

[0391] The "presence or absence of a link to inquire about repayment methods" may, by way of example and not by way of limitation, differ between normal and special demand letters in the following ways: A typical collection notice may not include, by way of example and not by way of limitation, information regarding the path to make an inquiry regarding repayment methods (how to use various services in electronic money services (such as, but not by way of limitation, how to increase electronic money balance, how to link accounts between electronic money services and money loan applications, etc.) and how to use various services in banking services (such as, but not by way of limitation, how to make bank transfers, how to use online banking)) (such as, but not by way of example and not by way of limitation, contact information for the customer center of each service (telephone number, email address, etc.)). However, the special embodiment of the reminder may include, by way of example and not limitation, information regarding the lead to make an inquiry regarding repayment methods as previously described.

[0392] By way of example and not limitation, "the presence or absence of a path to further borrowing" may differ between a normal demand letter and a special demand letter in the following ways: For example, and not by way of limitation, a typical demand letter may not include information regarding the path for the user to borrow more money from the money loan service provider to repay the outstanding repayment amount in addition to the money currently borrowed from the money loan service provider (information regarding a link for the user to transition to a screen for borrowing, information regarding a link for the user to have the provider send the documents for the user to borrow, etc.). On the other hand, a special type of reminder letter may, by way of example and not limitation, include information regarding a path for the user to borrow more money from the money loan service provider to repay any outstanding repayment amount in addition to the money currently borrowed from the money loan service provider, as described above.

[0393] <Processing> As a flowchart showing an example of the flow of processing executed by each device in this embodiment, the same flowchart as that shown in FIG. 1-9 can be applied, and therefore a description thereof will be omitted.

[0394] In this embodiment, as an example and not as a limitation, in S160, first, the control unit 11 of the server 10 determines, as an example and not as a limitation, whether or not electronic money repayment is possible. The determination of whether electronic money repayment is possible may be, for example and without limitation, determined by determining whether the electronic money balance linked to the user's money loan service is greater than the repayment amount.

[0395] When electronic money repayment is possible, the control unit 11 of the server 10 transmits, by way of example and not limitation, normal reminder information (a normal reminder notice) to the terminal 20A via the communication I / F 14. This normal form of dunning information may be, for example and not by way of limitation, an example of a dunning notice (third dunning notice) sent when the user's balance of electronic currency is greater than the repayment amount based on the loaned amount.

[0396] If electronic money repayment is not possible, the control unit 11 of the server 10 transmits, by way of example and not limitation, special type of reminder information (special type of reminder notice) to the terminal 20A via the communication I / F 14. This special type of reminder information may be, for example and not by way of limitation, an example of a reminder (fourth reminder) sent when the user's balance of electronic currency is less than the repayment amount based on the loaned amount. This special type of reminder information may include information on an account for making repayments to the loaned amount.

[0397] According to this configuration, different types of reminder letters are sent to the user depending on the user's repayment status, and by providing a path for electronic money repayment to users who are able to make electronic money repayment, it is possible to encourage them to repay using electronic money as a repayment method, and by providing a path for bank transfer repayment in addition to electronic money repayment to users who are unable to make electronic money repayment, it is possible to encourage them to repay by providing multiple options as a repayment method.

[0398] <Effects of the Fifth Example> This embodiment shows a configuration in which, when the electronic money balance of the user of terminal 20 is greater than the repayment amount based on the loaned amount, server 10 transmits normal type dunning information (not limited to, an example of a third dunning notice) to terminal 20 via communication I / F 14, and, when the electronic money balance of the user of terminal 20 is less than the repayment amount based on the loaned amount, server 10 transmits special type dunning information (not limited to, an example of a fourth dunning notice) including information on an account for repaying the loaned amount to terminal 20 via communication I / F 14. As an example of the effect of the embodiment obtained by such a configuration, different reminders can be sent to the terminal depending on whether the balance of electronic currency of the user of the terminal is more or less than the repayment amount based on the loaned amount. This allows the user to know whether the balance of his / her electronic currency is more or less than the repayment amount based on the loaned amount. Also, if the balance of the user's electronic currency is less than the repayment amount based on the loaned amount, it is possible to provide the user with information on an account for repaying the loaned amount and urge the user to repay.

[0399] <Sixth Example> The sixth embodiment relates to including information regarding the reason for overdue payment (the reason for the overdue payment) in the collection letter.

[0400] The contents described in the sixth embodiment are applicable to any of the other embodiments and other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0401] In this embodiment, as an example of a reason for overdue payment, by way of example and not limitation, the following situation may occur: -Insufficient electronic money balance · Improper electronic money connection (improper account connection)

[0402] Insufficient electronic money balance may be, by way of example and not limitation, a situation in which a user's electronic money balance is less than the repayment amount owed by the user to the money loan service provider, and therefore the repayment amount cannot be paid.

[0403] An electronic money link failure may be, for example and not by way of limitation, a situation in which the repayment amount cannot be paid because the user's electronic money service account and the user's money loan service account are not linked. This situation may include, for example and not by way of limitation, a situation in which the accounts are not linked even though the user has selected electronic money repayment as the repayment method, or a situation in which the accounts are linked but the settings are not properly configured (for example and not by way of limitation, there is a problem with the linking between the user's electronic money account and the account of the money loan service provider).

[0404] In some cases, users may not be aware of the insufficient balance of electronic money or the insufficient electronic money connection, and may not understand why their repayments are delayed. Therefore, when the system including the server 10 determines that the above-mentioned situation has occurred, the system makes it possible to inform the user of the reason for the overdue payment by including information regarding the reason for the overdue payment in a reminder letter and sending it to the terminal 20.

[0405] <Display screen> FIG. 5-1 is a diagram showing an example of transition of a screen displayed on the display unit 24 of the terminal 20A in this embodiment. This screen diagram shows, as an example and not a limitation, an example in which, similar to the first embodiment, a user of terminal 20 borrows "30,000 yen" from a money loan service provider at an annual interest rate of "15%", and a reminder letter is sent because the user fails to make a repayment on the scheduled repayment date, and if the reason for the late payment is insufficient electronic money balance, the reason for the late payment is displayed in the reminder letter. However, this is merely an example and is not limited to this example.

[0406] In the screen of FIG. 5-1, the description of the parts that are similar to the screen on the left side of FIG. 1-8 described above will be omitted as an example and not a limitation. In this example, the dunning information display area RR displays, by way of example and not limitation, information regarding the reason for the overdue payment (in this example, the message "Your repayment was not possible due to insufficient electronic money balance").

[0407] In this way, by displaying information regarding the reason for overdue in the reminder letter, the reason for overdue can be notified to the user when the reminder letter is sent, allowing the user to take measures at an earlier stage.

[0408] FIG. 5-2 is a diagram showing another example of transition of the screen displayed on the display unit 24 of the terminal 20A in this embodiment. This screen diagram shows, as an example and not a limitation, an example in which, similar to the first embodiment, a user of terminal 20 borrows "30,000 yen" from a money loan service provider at an annual interest rate of 15%, and a reminder letter is sent because the user fails to make a repayment on the scheduled repayment date, and if the reason for the late payment is due to an insufficient electronic money connection, the reason for the late payment is displayed in the reminder letter. However, this is merely an example and is not limited to this example.

[0409] In the screen of FIG. 5-2, the description of the parts that are similar to the screen of FIG. 5-1 described above will be omitted as an example and not a limitation. In this example, the dunning information display area RR displays, by way of example and not limitation, information regarding the reason for the overdue payment (in this example, the message "Your repayment was not made due to a failure to link your electronic money"), an electronic money setting button DSBT (a button containing the words "Set up electronic money") for transitioning to a screen for making settings including linking the money loan service account with the electronic money service account, and a bank transfer repayment button BHBT containing the words "Repay by direct bank transfer (virtual account)" for making repayment by bank transfer.

[0410] In this way, if the reason for the overdue payment is insufficient electronic money balance, a regular reminder letter including information regarding the reason for the overdue payment can be sent to the user. On the other hand, if the reason for the overdue payment is due to an electronic money link failure, a reminder letter containing information suggesting an alternative repayment method (in this example, a bank transfer repayment) can be sent to the user in addition to information regarding the reason for the overdue payment. This allows different reminder letters to be sent to the user depending on the reason for the overdue payment, making it possible to more effectively urge the user to repay.

[0411] In addition, even if the reason for the overdue payment is insufficient electronic money balance, a reminder letter may be sent to the user that includes information regarding the reason for the overdue payment as well as information suggesting an alternative repayment method (in this example, repayment by bank transfer). Furthermore, if the reason for the overdue payment is due to an electronic money linkage defect, a regular reminder letter including information regarding the reason for the overdue payment may be sent to the user.

[0412] <Processing> As a flowchart showing an example of the flow of processing executed by each device in this embodiment, the same flowchart as that shown in FIG. 1-9 can be applied, and therefore a description thereof will be omitted.

[0413] In this embodiment, as an example and not a limitation, in S160, the control unit 11 of the server 10 determines the reason for overdue. In this case, if the accounts are linked, the server 10 may inquire of the electronic money service server about the reason for non-repayment (why the repayment was not made) and identify the reason for the overdue payment based on the response from the electronic money service server.

[0414] If the result of the determination of the reason for the overdue payment is insufficient electronic money balance, the control unit 11 of the server 10 transmits, via the communication I / F 14 to the terminal 20A, dunning information including information indicating that the reason for the overdue payment is insufficient electronic money balance. When the result of the determination of the reason for the overdue payment is an electronic money linkage defect, the control unit 11 of the server 10 transmits, via the communication I / F 14 to the terminal 20A, dunning information including information indicating that the reason for the overdue payment is an electronic money linkage defect.

[0415] Also, as in the example shown above, but not as a limitation, by way of example, if the determination result of the reason for the overdue payment is insufficient electronic money balance, the control unit 11 of the server 10 may send to the terminal 20A dunning information (normal dunning information) including information indicating that the reason for the overdue payment is insufficient electronic money balance, whereas if the determination result of the reason for the overdue payment is an electronic money linkage error, the control unit 11 of the server 10 may send to the terminal 20A dunning information including information indicating that the reason for the overdue payment is an electronic money linkage error and information on the issued virtual account, etc.

[0416] <Effects of the Sixth Embodiment> In this embodiment, the dunning information includes information on the reason for overdue payment (not limited to this, but is an example of information on the reason for the overdue repayment based on the amount of the loan to the user). As an example of the effect of the embodiment obtained by such a configuration, it is possible to enable the user to understand the reason for delay in repayment based on the loan amount.

[0417] <Seventh Example> The seventh embodiment is an embodiment in which there is a restriction on the time (including the time zone, etc.) when a money loan service provider sends a reminder to a user.

[0418] The contents described in the seventh embodiment are applicable to any of the other embodiments and other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0419] By way of example and not limitation, the time period during which a reminder can be sent may be set to be between 9:00 and 21:00. Therefore, by way of example and not limitation, it may be impossible to send a reminder during the time period between 21:00 and 9:00 the following day. Note that the example of the time period during which the reminder can be sent is merely an example, and other time periods may be set as examples and not as limitations. As an example and not as limitations, the period during which the reminder can be sent may be set from 8:00 to 21:00 as an example and not as limitations.

[0420] Also, instead of a time period, a time or date for sending a reminder may be set, or conversely, a time or date for not sending a reminder may be set.

[0421] Furthermore, these settings may be set by the server 10 based on input by the money loan service provider, or may be set automatically by the server 10.

[0422] If there are restrictions imposed by laws, regulations, etc. on the time (time period, etc.) for sending reminders, etc., the time period, etc. may be set based on such restrictions. In countries where there are no provisions, the time zones may be freely determined. In addition, when laws, regulations, etc. are revised, the time zones may be set based on the provisions of those laws, regulations, etc.

[0423] <Processing> As a flowchart showing an example of the flow of processing executed by each device in this embodiment, the same flowchart as that shown in FIG. 1-9 can be applied, and therefore a description thereof will be omitted.

[0424] In this embodiment, in the process of determining whether the dunning information transmission condition of S150 is met, in addition to the dunning information transmission condition shown in the above-mentioned <First embodiment>, as a non-limiting example, a determination of the condition "the current date and time is between 9:00 and 21:00" may be added.

[0425] When it is determined that the dunning information transmission condition shown in the above-mentioned <First embodiment> is satisfied, as an example and not a limitation, if the condition "the current date and time is between 9:00 and 21:00" is satisfied, S150: YES is determined, and the control unit 11 of the server 10 may, as an example and not a limitation, perform the processing of S160.

[0426] On the other hand, even if it is determined that the dunning information transmission condition shown in the above-mentioned <First embodiment> is satisfied, as an example and not a limitation, if the condition "the current date and time is between 9:00 and 21:00" is not satisfied, the result of S150:NO may be determined, and the control unit 11 of the server 10 may, as an example and not a limitation, not perform the processing of S160.

[0427] With this configuration, when a reminder is sent to a user in digital format, it is possible to prevent the money loan service provider from mistakenly sending a reminder to a user at a time when the money loan service provider cannot send a reminder to the user.

[0428] <Effects of the Seventh Embodiment> In this embodiment, the server 10 uses the control unit 11 to control the transmission of information on the loan amount and the loan interest rate based on a set time period. As an example of the effect of the embodiment obtained by such a configuration, information on the loan amount and the loan interest rate can be transmitted to the terminal based on a set time period. Even if a time period during which transmission is prohibited is specified by law or regulation, the information can be transmitted to the terminal at a timing that does not violate the provision.

[0429] <Eighth Example> The eighth embodiment is an embodiment in which a money loan service provider is able to know whether or not the user of the terminal to which the demand notice was sent has viewed the demand notice.

[0430] The contents described in the eighth embodiment are applicable to any of the other embodiments and other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0431] <Processing> As a flowchart showing an example of the flow of processing executed by each device in this embodiment, the same flowchart as that shown in FIG. 1-9 can be applied, and therefore a description thereof will be omitted.

[0432] In this embodiment, after S160, the control unit 11 of the server 10 may, by way of example and not limitation, transmit to terminal 20A via communication I / F 14 view / non-view request information requesting information as to whether or not the user of terminal 20A has viewed the reminder information transmitted in S160 (not shown).

[0433] When the control unit 21 of the terminal 20A receives the viewing / non-viewing request information from the server 10 via the communication I / F 22, the control unit 21 may, by way of example and not limitation, transmit viewing / non-viewing result information indicating whether or not the received prompting information has been displayed on the display unit 24 to the server 10 via the communication I / F 22 based on the received viewing / non-viewing request information (not shown).

[0434] The control unit 21 of the terminal 20A that receives the viewing / non-viewing request information, by way of example and not limitation, when processing A150 is being executed, transmits viewing / non-viewing result information indicating that the received reminder information has been displayed on the display unit 24 (i.e., that the user has viewed the reminder notice) to the server 10 via the communication I / F 22.

[0435] On the other hand, the control unit 21 of the terminal 20A that receives the viewing / non-viewing request information, by way of example and not limitation, if the processing of A150 is not executed, transmits viewing / non-viewing result information to the server 10 via the communication I / F 22 indicating that the received reminder information has not been displayed on the display unit 24 (i.e., the user has not viewed the reminder notice).

[0436] When the control unit 11 of the server 10 receives the viewing / non-viewing result information from the terminal 20A via the communication I / F 14, the control unit 11 of the server 10 may, for example and not limitation, associate the received viewing / non-viewing result information with information that can identify the application ID of the user AA (or the terminal 20A) and the sent reminder information, and store the information in the memory unit 15 (for example and not limitation, the account management data of the user AA). This allows the server 10 to know whether or not the dunning information has been displayed on the terminal 20A (whether or not the dunning notice has been viewed) (not shown).

[0437] Note that the series of processes performed by the server 10 and the terminal 20A may be, for example and not limited to, a series of processes performed by the server 10 and the terminal 20A as needed after S160.

[0438] <Effects of the Eighth Example> This embodiment shows a configuration in which the control unit 11 controls the server 10 to store in the memory unit 15 viewing / non-viewing result information (not limited to, but an example of information regarding the fact that the user viewed the information on the loan amount and the loan interest rate sent to the terminal) in association with information such as the user's application ID. As an example of the effect of an embodiment obtained by such a configuration, by storing information regarding a user's viewing of information on the loan amount and loan interest rate sent to the terminal in the server's memory in association with user information, it becomes possible for the server side to manage and grasp the status of the user's viewing of information on the loan amount and loan interest rate sent to the terminal.

[0439] <Ninth Example> The ninth embodiment is an embodiment in which the attributes of a user can be changed in a reminder letter.

[0440] The contents described in the ninth embodiment are applicable to any of the other embodiments and other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0441] User attributes in this embodiment refer to user information, which may include, by way of example and not limitation, the following: ·full name ·address ·telephone number ·Occupation ·annual income Repayment Method

[0442] <Display screen> FIG. 6-1 is a diagram showing an example of transition of a screen displayed on the display unit 24 of the terminal 20A in this embodiment. This screen diagram shows, as an example and not a limitation, an example in which, similar to the first embodiment, a user of terminal 20 borrows "30,000 yen" from a money loan service provider at an annual interest rate of 15%, and a reminder letter is sent because the user fails to make a repayment on the scheduled repayment date, and the user's attributes (user information) are changed based on that reminder letter. However, this is merely an example and is not limited to this example.

[0443] In the screen of FIG. 6-1, the description of the parts that are similar to the screen on the right side of FIG. 1-8 described above will be omitted as an example and not a limitation. In this example, at the bottom of the reminder information display area RR, by way of example and not limitation, information for changing the user's attributes (in this example, an attribute change button ZBT containing the words "Change user information") is displayed.

[0444] By way of example and not limitation, when the attribute change button ZBT on the screen on the left side of FIG. 6-1 is tapped by the user, the display changes to the screen on the right side of FIG. 6-1, by way of example and not limitation.

[0445] This screen is, by way of example and not limitation, an attribute change screen for changing a user's attributes, and displays specific information for changing the user's attributes (user information items (name, address, ...), change buttons for actually changing those items (buttons containing the word "change"), etc.).

[0446] With this configuration, a guide line can be provided on the reminder letter to allow the user to change their attributes, thereby improving convenience for users to change their attributes and enabling the money loan service provider to obtain more accurate information regarding the user's attributes in loan contracts that could develop into legal issues.

[0447] In the above example, the user's attributes can be changed in a reminder letter, but the present invention is not limited to this example. For example and without limitation, the user's attributes can be changed in a messaging service.

[0448] The following is an example of a case where user AA changes the attributes of a user in an OA talk room in which the user AA talks with "Money Loan Service," a company that provides money loan services, as the talk partner.

[0449] As a non-limiting example, based on the user inputting the text “I would like to change my user information”, message information sent from user AA (in this example, the message “I would like to change my user information”) is displayed on the right side of the OA talk room screen.

[0450] Next, as a non-limiting example, based on the message information of user AA "I would like to change my user information", message information (in this example, a message for the user to select the item of user information they wish to change) sent from the OA account (money loan service) is displayed on the left side of the OA talk room screen.

[0451] And, by way of example and not limitation, it may be possible to change a user's attributes based on user input in response to message information (in this example, a message for selecting the item of user information that the user wishes to change) sent from an OA account (money loan service).

[0452] <Processing> As a flowchart showing an example of the flow of processing executed by each device in this embodiment, the same flowchart as that shown in FIG. 1-9 can be applied, and therefore a description thereof will be omitted.

[0453] In this embodiment, the reminder information sent from the control unit 11 of the server 10 to the terminal 20A in S160 may include, by way of example and not limitation, information for changing the user's attributes (information regarding a button for transitioning to an attribute change screen for changing the user's attributes, information regarding the attribute change screen (items of the user's attributes, information for the user to enter to make changes, etc.)).

[0454] <Effects of the ninth embodiment> In this embodiment, the prompting information includes information regarding input of attribute information of the user of the terminal 20 . As an example of an effect of an embodiment obtained by such a configuration, a reminder letter containing information regarding the input of the user's attribute information is sent to the terminal, allowing the user of the terminal to input his or her own attribute information from the reminder letter.

[0455] <Other Examples> In the above embodiment and modified example, the pocket plan is applied as a loan contract plan by way of example and not by way of limitation, but the present invention is not limited to this. In the above embodiment and modified example, the aforementioned self-paced plan may be applied as a loan contract plan by way of example and not by way of limitation.

[0456] The pocket plan may be, for example and not by way of limitation, a typical loan contract in which the period from the loan date to the scheduled repayment start date and the period from the scheduled repayment start date to the scheduled repayment days after the scheduled repayment start date are set to be equal. Specifically, in the pocket plan, as an example and not a limitation, the period from the lending date to the scheduled repayment start date may be one month. The period until the next scheduled repayment date may be one month. In other words, the loan contract plan may be such that the first scheduled repayment date (scheduled repayment start date) occurs one month after the lending date, and the next scheduled repayment date occurs one month after the scheduled repayment start date.

[0457] A self-paced plan may be, for example and not by way of limitation, a loan contract in which the period from the loan date to the scheduled repayment start date is set longer than the period of scheduled repayment days after the scheduled repayment start date. Specifically, in the self-paced plan, by way of example and not limitation, the period from the lending date to the scheduled repayment start date may be six months. The period until the next scheduled repayment date may be one month. In other words, the loan contract plan may be such that the first scheduled repayment date (scheduled repayment start date) occurs six months after the lending date, and the next scheduled repayment date occurs one month after the scheduled repayment start date.

[0458] In addition, the period from the lending date to the scheduled repayment start date for the My Pace Plan may be, by way of example and not by way of limitation, set to be longer than the period from the lending date to the scheduled repayment start date for the Pocket Plan. If the period from the loan date to the scheduled repayment start date for the Pocket Plan is one month, then, by way of example and not limitation, the period from the loan date to the scheduled repayment start date for the My Pace Plan may be, by way of example and not limitation, four months, five months, seven months, or eight months.

[0459] In addition, the pocket plan and the self-paced plan may differ in the following items, by way of example and not by way of limitation. ·Usage limit Loan interest rate · Interest payment cashback

[0460] The credit limit may be, by way of example and not limitation, a limit on the amount of money a user can borrow from a money loan service provider. The Pocket Plan's spending limit may be, for example and not for limitation, 500,000 yen, and the My Pace Plan's spending limit may be, for example and not for limitation, 30,000 yen.

[0461] The loan interest rate for the Pocket Plan may be, by way of example and not limitation, 3-15%, and the loan interest rate for the Self-Pace Plan may be, by way of example and not limitation, 15%.

[0462] The interest payment cashback may be, for example and not by way of limitation, a service in which a consideration equivalent to the interest paid by the user to the money loan service provider is paid to the user by the money loan service provider (cashback). The consideration here may be, for example and not by way of limitation, money, points, etc. The interest rebate for the Pocket Plan may be available for up to 100 days from the date of loan, for example and not by way of limitation, and the interest rebate for the Self-Pace Plan may not be available for even a single day, for example and not by way of limitation.

[0463] In the above embodiment and modified examples, a case where a self-paced plan is applied as a loan contract plan will be illustrated by way of example and not by way of limitation. Here, as an example, and not a limitation, the My Pace Plan will be described as a case in which the period from the loan date to the start date of the scheduled repayment is six months, and the period until the next scheduled repayment date is one month, and a reminder letter is sent based on the user's default in repayment.

[0464] <Processing> The flow of the process executed by each device is not limited to the above, but may be the same as that shown in FIG. 1-9, for example, and therefore the description thereof will be omitted.

[0465] In this case, the conditions for sending the dunning information may include, by way of example and not limitation, the following conditions, similar to the case where the pocket plan is applied: “J01”: A certain number of days have passed since the scheduled repayment date without repayment. However, as an example and not a limitation, based on the application of the self-paced plan, the scheduled repayment start date here is six months from the loan date, and the next and subsequent scheduled repayment dates will be dates more than six months after the loan date (seven months, eight months, ...).

[0466] As a non-limiting example, similar to when the Pocket Plan is applied, if the reminder information transmission condition is set to "J01" and the specified number of days is set to "10 days," the reminder information transmission condition will be met for the first time at 0:00 on the 11th day from the scheduled repayment date if no repayment has been made, and the first reminder information will be sent to terminal 20.

[0467] Also, as an example and not a limitation, in the above example, similar to when the pocket plan is applied, if no repayment has been made, the condition for resending dunning information may be met at 00:00 on the 12th day from the scheduled repayment date, and a second dunning information may be sent to terminal 20. Thereafter, similarly to the case where the pocket plan is applied, if the non-repayment state continues, similar control may be performed and dunning information may be repeatedly sent to the terminal 20. That is, in this example, by way of example and not limitation, reminder information may be repeatedly transmitted to the terminal 20 every time a day passes, similar to the case where a pocket plan is applied. Note that this is merely an example, and the reminder information may be repeatedly sent every few hours, as in the case of applying the pocket plan, or may be sent at irregular times.

[0468] In this case, similar to the case where the pocket plan is applied, the same dunning information may be sent for the first (initial) payment and the second or subsequent payment, or different dunning information may be sent. Furthermore, the second time, different reminder information is sent than the first time, but from the third time onwards, the same reminder information as the second time may be sent.

[0469] Then, when it is determined that the dunning information transmission condition is not satisfied (S150: NO), the control unit 11 of the server 10 ends the process in the same manner as in the case of applying the pocket plan, by way of example and not limitation.

[0470] If it is determined that the dunning information transmission condition is met (S150: YES), the control unit 11 of the server 10 transmits the dunning information to the terminal 20A via the communication I / F 14 (S160), as an example and not a limitation, similar to when the pocket plan is applied.

[0471] In this way, the self-paced plan can be applied to any of the other embodiments and other modified examples.

[0472] <Other> At least a part of the processing that is to be performed by the server 10 in the above embodiment may be performed by the terminal 20. Conversely, at least a part of the processing that is to be performed by the terminal 20 in the above embodiment may be performed by the server 10.

[0473] In the above embodiment, the server 10 may be divided into a plurality of servers, and the processes described in the above embodiment and the modified example may be realized by a server system composed of the plurality of servers. As a non-limiting example, the server 10 may be divided into a server of a money loan service provider and a server of an SNS provider such as a messaging service provider, and the processes described in the above embodiment and the modified example may be realized.

[0474] Furthermore, an SNS operator, such as a messaging service operator, may also be a money loan service operator and an electronic money service operator. In this case, the processing described in the above embodiments and variants may be realized by a single server, or the processing described in the above embodiments and variants may be realized by a server system consisting of multiple servers.

[0475] Note that, as an example and not a limitation, a system configured with one or more servers may be defined as a server system, and the server of the present invention may be a server system.

[0476] In the above embodiment, a server for distributing various applications (a server from which the terminal 20 downloads applications) may be configured as a server different from a server providing a corresponding service (application), etc. In other words, a server for distributing applications and a server performing application management processing, etc., described in the above embodiment, etc., may be configured as physically separated servers, or may be configured as a single server.

[0477] Furthermore, the application is not limited to various application programs, but may include, for example and without limitation, a program for providing a function of another service as one function of a base application (for example and without limitation, a program for providing a function of an advertisement delivery service as one function of a messaging application, or vice versa), a program for updating the base application, etc. Also, data used in the application program (which may include data for updating the application, etc.) may be included.

[0478] In the above embodiment, the method of realizing the present invention by a client-server system has been described as an example and not a limitation, but the present invention is not limited to this. As described above, the present invention may be realized by a system such as a distributed system in which the terminal 20 has the functions of a server or a server system. As an example and not a limitation, the processing described as being performed by a server or a server system in the flowcharts described in the above embodiment may be performed by a terminal.

[0479] As described above, the contents described in the above embodiments, the modifications, other embodiments, and the like can be applied in combination with each other. [Explanation of symbols]

[0480] 1. Communication Systems 10 Server 20 Terminals 30 Network

Claims

1. A program executed by a server in communication with a user's terminal, A control unit of the server controls to store information on the amount of money lent to the user in a storage unit of the server; If the repayment deadline for the loaned amount has passed, the server transmits information on the loaned amount and the loan interest rate to the terminal via a communication unit of the server.

2. The program according to claim 1, If the repayment deadline for the loaned amount has passed, the server transmits information on the late payment charge rate to the terminal via the communication unit.

3. The program according to claim 1 or 2, If the repayment deadline for the loaned amount has passed, the server transmits, via the communication unit, contract date information relating to the final borrowing date to the terminal.

4. The program according to any one of claims 1 to 3, If the repayment deadline for the loaned amount has passed, the server executes the process of transmitting a reminder letter to the terminal via the communication unit, the reminder letter including information on the loaned amount and the loaned interest rate.

5. The program according to any one of claims 1 to 4, The server transmits information on the loan amount and the loan interest rate to a chat room including the user via the communication unit.

6. The program according to any one of claims 1 to 5, If the repayment deadline for the loaned amount has passed, the server executes the process of transmitting information on the loaned amount and the loaned interest rate to the terminal via the communication unit based on information on the user's credit score.

7. The program according to any one of claims 1 to 6, receiving information regarding a promise of payment based on the loan amount from the terminal by the communication unit; The server controls the control unit to store information regarding the promise of payment in the memory unit.

8. The program according to claim 7, The information regarding the promise of payment includes information regarding the promised payment date.

9. The program according to claim 8, If the repayment deadline for the loaned amount has passed, transmitting a first demand notice including information on the loaned amount and information on the loaned interest rate to the terminal by the communication unit; The server executes a process of receiving information regarding the promise of payment from the terminal via the communication unit based on an input by the user in response to the first reminder.

10. The program according to claim 9, A second demand notice, which is sent later than the first demand notice based on the promised payment date, is sent to the terminal by the communication unit.

11. The program according to claim 9 or 10, The server executes a process of transmitting information on a scheduled repayment amount based on the loan amount to the terminal via the communication unit based on an input by the user in response to the first demand notice.

12. The program according to any one of claims 7 to 11, transmitting information on the loan amount and information on the loan interest rate to a chat room including the user by the communication unit; The server receives information regarding the promise of deposit from the terminal via the communication unit based on an input by the user to the chat room.

13. The program according to claim 5, Based on input by the user into the chat room, the server transmits to the terminal via the communication unit information regarding a repayment amount that the user needs to repay, based on the loan amount.

14. The program according to claim 4, The server executes a process of transmitting, to the terminal via the communication unit, account information for making repayment of the loan amount, based on the user's input in response to the demand letter.

15. The program according to claim 4, The server executes the following operations: if the user's electronic currency balance is greater than the repayment amount based on the loaned amount, it sends a third demand notice to the terminal via the communication unit; if the user's electronic currency balance is less than the repayment amount based on the loaned amount, it sends a fourth demand notice to the terminal via the communication unit, which includes information about an account for making repayment of the loaned amount.

16. The program according to claim 4, The reminder includes information regarding why the user is behind on repayments based on the loan amount.

17. The program according to any one of claims 1 to 16, The server executes control by the control unit to transmit information on the loan amount and information on the loan interest rate based on a set time period.

18. The program according to any one of claims 1 to 17, The server executes control by the control unit to store information regarding the user's viewing of the information on the loan amount and the loan interest rate sent to the terminal in the memory unit in association with the user's information.

19. The program according to claim 4, The reminder includes information regarding inputting attribute information of the user.

20. An information processing method for a server that communicates with a user terminal, comprising: A control unit of the server controls to store information on the amount of money lent to the user in a storage unit of the server; If the repayment deadline for the loaned amount has passed, information on the loaned amount and information on the loaned interest rate are transmitted to the terminal by a communication unit of the server.

21. A server that communicates with a user's terminal, a control unit that controls storing information on the amount of money lent to the user in a storage unit of the server; The device includes a communication unit for transmitting information on the loaned amount and the loan interest rate to the terminal when the repayment deadline for the loaned amount has passed.

Citation Information

Patent Citations

  • Contract system for consumer loan

    JP2002099721A

Cited By

  • Billing amount by payment scheduled date calculation device, billing amount by payment scheduled date calculation method and billing amount by payment scheduled date calculation program

    JP2025004845A

  • Financial instrument management device, accounting method, and accounting program

    JP2026110162A

  • Business support device, business support method, and business support program

    JP2026114027A

  • Loan repayment management device, loan repayment management method, and loan repayment management program

    JP2026115682A

  • Device for calculating billing amount by estimated payment date, method for calculating billing amount by estimated payment date, and program for calculating billing amount by estimated payment date

    JP7716445B2