JP6855606B1 - Card usage management device, card usage management method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To construct a new repayment plan according to the intention of a card user while presenting a payment status including a plurality of payment methods in an easy-to-understand manner. SOLUTION: A plurality of payment methods including revolving payment based on card usage data corresponding to authorization data 12d3 and credit data 12d4 for storing data on the usage status of a card user and a simulation request from a card user terminal. Generates and sends data for the simulation screen that includes the payment amount calculation application 12p2 that calculates the individual and total payment amount for each usage period, and the calculated result and the operator that accepts the instruction to change the payment amount of revolving payment. It is provided with a CPU 11 that accepts an operation on an operator and regenerates and transmits data for a simulation screen in which the payment amount of revolving payment is changed. [Selection diagram] Fig. 2

Description

The present invention relates to a card usage management device, a card usage management method, and a program for appropriately managing the use of a credit card.

Conventionally, a credit card issued by a card company (hereinafter, simply referred to as a "card") has been used by its members to purchase goods and the like. In recent years, the market has rapidly become cashless, and the use of cards has become widespread among individuals.

Conventionally, one of the services on the website provided by the card company to the card user (card user) is "Revolving Credit User Guide-Course Change / Summary".

"Revolving Payment Usage Guide-Course Change / Summary" allows card users to select and change the payment amount according to the situation regarding revolving payment (revolving payment) that makes the monthly payment amount almost constant. (See, for example, Non-Patent Document 1).

The target of such a service in which the card user changes the payment amount after use is not limited to revolving payment, but a service for changing the payment of products purchased by lump sum payment to installment payment after that is also provided separately.

Rakuten Card, Revolving Credit Usage Guide-Course Change / Summary, [online], [Search May 29, 1st year of Reiwa], Internet <URL: https://www.rakuten-card.co.jp/revo / change />

The service for changing payment conditions on the website, which has been provided by card companies, individually changes the conditions for revolving payments and installment payments for each purchased product. Therefore, the card user individually grasps the card usage cases that he / she is obliged to pay, and after considering his / her own payment ability, selects the case for which the payment conditions are changed from the payment methods that are considered to be burdensome, and the conditions. Had to be selected and changed.

The present invention has been made in view of such a problem, and an object of the present invention is to provide a new repayment plan in line with the wishes of a card user while presenting a comprehensive and easy-to-understand payment status including a plurality of payment methods. The purpose is to provide a card usage management device, a card usage management method, and a program that can be constructed.

The card utilization management device according to one aspect of the present invention is
According to the card use of the card user, the card use data storage means for storing card use data that contains data for multiple payment methods and spend comprising re revolving payment,
A means for calculating a payment schedule for the latest period based on the card usage data stored in the card usage data storage means in response to a request from the card user terminal and transmitting the payment to the card user terminal.
The payment amount that receives the desired payment amount for the latest period from the card user terminal and calculates the individual and total payment amount for each usage period according to a plurality of payment methods, reflecting the received payment desired amount. Calculation means and
Including payment of the individual and overall each use time period corresponding to the plurality of payment calculated by the payment amount calculation means, that sends generates data for displaying a payment screen to the card user terminal and hand-stage,
To be equipped.

According to the present invention, it is possible to construct a new repayment plan according to the wishes of the card user while presenting the payment status including a plurality of payment methods in an easy-to-understand manner.

FIG. 1 is a block diagram showing an overall configuration of a card usage management system according to an embodiment of the present invention. FIG. 2 is a block diagram showing a configuration of an electronic circuit of the card usage management server according to the embodiment. FIG. 3 is a block diagram showing a configuration of an electronic circuit of a user terminal according to the embodiment. FIG. 4 is a flowchart showing an extraction of a particularly main flow of payment simulation processing executed in cooperation between the card usage management server and the user terminal according to the embodiment. FIG. 5 is a flowchart showing a particularly main flow of the payment simulation process executed in cooperation between the card usage management server and the user terminal according to the embodiment. FIG. 6 is a flowchart showing a particularly main flow of the payment simulation process executed in cooperation between the card usage management server and the user terminal according to the embodiment. FIG. 7 is a diagram showing an example of a screen displayed on the user terminal according to the embodiment. FIG. 8 is a diagram showing an example of a screen displayed on the user terminal according to the embodiment. FIG. 9 is a diagram showing an example of a screen displayed on the user terminal according to the embodiment. FIG. 10 is a diagram showing an example of a screen displayed on the user terminal according to the embodiment. FIG. 11 is a diagram showing an example of a screen displayed on the user terminal according to the embodiment. FIG. 12 is a diagram showing an example of a screen displayed on the user terminal according to the embodiment. FIG. 13 is a diagram showing an example of a screen displayed on the user terminal according to the embodiment. FIG. 14 is a diagram showing an example of a screen displayed on the user terminal according to the embodiment. FIG. 15 is a diagram showing an example of a screen displayed on the user terminal according to the embodiment. FIG. 16 is a diagram showing an example of a screen displayed on a user terminal according to the embodiment.

An embodiment of the present invention will be described below with reference to the drawings.
FIG. 1 is a block diagram showing an overall configuration of a card utilization management system according to an embodiment of the present invention.

The card usage management system includes a card usage management server 10 (card usage management device) of the card issuing company, a card user user terminal 20 (card user terminal) that is a member of the card issued by the card issuing company, and the card user terminal 20 (card user terminal). It is provided with a member store terminal 30 of the member store of the card.

The user terminal 20 is composed of a mobile terminal such as a smartphone or a tablet terminal that has registered in the card usage management server 10 that it is a terminal used by the card user, and is composed of the card usage management server 10 and a public communication network (for example,). Internet) It has a communication function that enables communication connection via IN. The user downloads the card use dedicated application 22p2 (see FIG. 3) provided by the card issuing company to the member from the program server (here, the application store) (not shown) on the communication network IN to the user terminal 20. , Install and use.

The member store terminal 30 is a credit inquiry terminal such as CAT (Credit Authorization Terminal), and can communicate with the card usage management server 10 via a card payment online network SN such as CAFIS (Credit And Finance Information Switching system). Has a function.

When the card user uses the card, the member store terminal 30 displays the authorization data of the card usage (card number / date and time of use / usage amount / payment method (once / bonus batch / division / revolving) / terminal identification number. (Including) (hereinafter referred to simply as "authorization data") is transmitted to the card payment online network SN, and the card usage judgment (credit inquiry) is received.

On the card payment online network SN, in addition to the card usage management server 10 of the card issuing company (issuer) and the member store terminal 30, the server of the card company that is the acquirer (member store acquisition / management company) (not shown). ), Servers of card companies (not shown) that are international brands (providing systems that allow international payments), servers of financial institutions such as banks, etc. are capable of communication.

In the card payment online network SN, there are card payment forms in which the same card company plays all three roles of international brand, issuer, and acquirer, and card payment in which the same card company plays any two roles. There are also forms, or card payment forms in which different card companies perform all roles.

In the present embodiment, for example, the card usage management server 10 of the card issuing company performs a card usage availability determination process on the authority data transmitted from the member store terminal 30 to the card payment online network SN, and the determination result ( Authority data including credit approval / non-approval data is sent again to the server of the international brand card company, the server of the acquirer card company, and the member store terminal 30 via the card payment online network SN. To do.

When the authority data including the data of the judgment result of the card usage (credit approval) is transmitted from the card usage management server 10, the member store terminal 30 performs the payment processing of the card usage, and the card company, which is an international brand, performs the payment processing. The server transmits the confirmed data to the card usage management server 10 of the card issuing company after a certain period of time such as several days after the payment processing. The card usage management server 10 stores the received confirmed data as credit data.

In the card usage management system of the present embodiment, the card usage management server 10 responds to a request on the simulation screen for confirming the payment status and changing the payment conditions sent from the user terminal 20 via the communication network IN. Then, the data of the simulation screen including the individual cases and the total payment amount is generated and transmitted to the user terminal 20 to display the simulation screen.

In addition, the card usage management server 10 receives an operation for changing payment conditions and the like on the displayed simulation screen with the user terminal 20, and transmits and uses new simulation screen data each time. Displayed on the person terminal 20.

In this case, the payment conditions that can be changed on the simulation screen are to change the most recently fixed payment amount in revolving payment and the case of shopping with one-time payment or bonus lump sum payment to installment payment. The number of installments for payment projects that have already been confirmed as installments cannot be changed.

Finally, when an operation for instructing confirmation is performed on the simulation screen displayed on the user terminal 20, the card usage management server 10 accepts the operation and executes the process of updating and storing the credit data.

FIG. 2 is a block diagram showing a configuration of an electronic circuit of the card usage management server 10.
The card usage management server 10 includes a CPU 11 (processor) which is a control unit.

The CPU 11 (processor) is a program stored in advance in a storage unit 12 such as a hard disk or a flash memory, a program read by a recording medium reading unit 14 from an external recording medium 13 such as a CD-ROM, and stored in the storage unit 12. Alternatively, the operation of each part of the circuit is controlled according to the program downloaded from the Web server (program server in this case) (not shown) on the communication network IN via the communication unit 15 and stored in the storage unit 12, and various functions are performed. Execute.

The CPU 11 has a storage unit 12, a recording medium reading unit 14, a communication unit 15 (simulation screen transmission means) which is a communication interface with the communication network IN, and a communication interface with the card payment online network SN via the system bus Bus. A certain payment system communication unit 16, an input unit 17 such as a keyboard and a pointing device, a display unit 18, and the like are connected.

A plurality of types of data storage areas such as a program storage area 12P and a management data storage area 12D are secured in the storage unit 12.

In the program storage area 12P, in addition to the server system program 12p1 that controls the entire card usage management server 10, a payment amount calculation application 12p2, a screen generation data acquisition application 12p3, a payment simulation providing application 12p4, and the like are stored.

The payment amount calculation application 12p2 is determined by, for example, the monthly card usage deadline, based on the usage amount of the card user, the payment method for each usage amount (one-time payment / installment payment / revolving payment), the preset interest rate, etc. This is a program for calculating the payment amount for each predetermined card usage period (payment amount calculation means).

The screen generation data acquisition application 12p3 has a home screen dedicated to the card user, a simulation screen thereafter, and the like on the touch panel display unit 25 of the user terminal 20 according to the card use dedicated application 22p2 installed on the user terminal 20 (FIG. 7). This is a program for acquiring various data necessary for displaying (see FIG. 16) and transmitting the data to the user terminal 20 (simulation screen transmission means).

The payment simulation providing application 12p4 uses the screen generation data acquisition application 12p3 to send the necessary screen data to the user terminal 20 that has requested the display of the simulation screen, while appropriately confirming the latest payment. This is a program for creating copy data for each of the credit data when the payment conditions, etc. are changed with respect to the amount, temporarily storing it separately from the original credit data, and updating and storing each final data as this data. (Simulation screen transmission means, simulation control means, update means).

The management data storage area 12D stores user ID data 12d1, member store data 12d2, authority data 12d3, credit data 12d4, usage period data 12d5, payment amount data 12d6, and the like.

The user ID data 12d1 includes an ID (identification number) for each card user, a password, a card number, a name, a terminal device number which is terminal device information, an email address, a telephone number, and a bank name for withdrawing payment. , Branch name, account number, and other data unique to the card user (user identification information) and data unique to the user terminal 20 (terminal device information) are stored in association with each other.

As the member store data 12d2, the terminal identification number of the member store terminal 30 for each card member store and each data of the name of the member store are stored in association with each other.

The authority data 12d3 is received and stored from the member store terminal 30 via the card payment online network SN according to the card usage of the card user, and the authority data 12d3 contains the card number, the date and time of use, and the usage. Each data of amount, payment method (once / bonus batch / split / revolving), and terminal identification number is included (card usage data storage means). After receiving the card usage judgment (credit inquiry) on the card payment online network SN based on the authorization data 12d3 from the member store terminal 30, the judgment result (credit approval / non-credit approval / non-credit) is displayed on the authorization data 12d3. Approval) data is also included.

The credit data 12d4 stores the fixed data of the card usage amount received from the card payment online network SN after a certain period of time according to the card usage of the card user as the credit data for each card user. The claim data 12d4 includes data such as a card number, date and time of use, name of member store used, amount used, and payment method (once / bonus batch / split / revoked) (card usage data storage means).

As the usage period data 12d5, the card number for each card user, for example, the monthly card usage deadline date and the payment date data are stored in association with each other.

As the payment amount data 12d6, each data of the payment amount for each predetermined card usage period calculated by the payment amount calculation application 12p2 based on the card number for each card user, the authority data 12d3 and the bond data 12d4 is associated with each other. It will be remembered.

Due to the relationship between the card usage deadline and the date when the payment amount is calculated, confirmation information is added to the payment amount in the usage period when payment is confirmed, and the payment amount in the usage period when payment is unconfirmed Unconfirmed information is added.

In addition, when the calculated payment amount includes the payment amount based on the authority data 12d4, the information that the payment amount data based on the authority data 12d4 is also the payment amount based on the authority data is added. Is remembered.

FIG. 3 is a block diagram showing a configuration of an electronic circuit of the user terminal 20.
The user terminal 20 includes a CPU 21 (processor) which is a control unit.

The CPU 21 (processor) is a program stored in advance in a storage unit 22 such as a flash memory, a program read from an external recording medium 23 such as a memory card by the recording medium reading unit 24 and stored in the storage unit 22, or a communication network. (Internet) The operation of each part of the circuit is controlled according to the program downloaded from the program server (app store in this case) (not shown) on the IN via the communication unit 26 and stored in the storage unit 22, and various functions are performed. Execute.

The storage unit 22, the recording medium reading unit 24, the communication unit 26 which is a communication interface with the communication network IN, the touch panel type display unit 25, and the like are connected to the CPU 21 via the system bus Bus.

A plurality of types of data storage areas such as a terminal data storage area 22R, a program storage area 22P, and a work data storage area 22W are secured in the storage unit 22.

In the terminal data storage area 22R, each data (terminal device information) such as a terminal device number, an email address, and a telephone number unique to the user terminal 20 is stored.

In the program storage area 22P, in addition to the terminal system program 22p1 that controls the entire user terminal 20, the card use dedicated application 22p2 and the like are stored.

The card usage application 22p2 is downloaded from the program server (here, the application store) (not shown) on the communication network (Internet) IN based on the card user's ID (identification number), password, card number, etc. A program for generating and displaying a simulation screen of the payment amount, executing a series of processes corresponding to the received operations for items on the screen, etc. in cooperation with the card usage management server 10. Is.

The work data storage area 22W stores card usage screen generation data 22w1, card usage dedicated screen data 22w2, bitmap format display data 22w3 for display on the touch panel display unit 25, and the like.

The card usage screen generation data 22w1 stores data for generating various screens (FIGS. 7 to 16) based on the data transmitted from the card usage management server 10 received in advance by the user terminal 20. Has been done.

As the card use-only screen data 22w2, data of various screens (FIGS. 7 to 16) generated based on the card use screen generation data 22w1 are stored according to the card use-only application 22p2.

The data of various screens stored as the card use-only screen data 22w2 is written as display data 22w3 at the timing of displaying each screen, and is displayed on the touch panel type display unit 25.

In the user terminal 20 configured in this way, the CPU 21 controls the operation of each part of the circuit according to the instructions described in each program 22p1, 22p2, and the software and the hardware operate in cooperation with each other. Various functions as described in the following operation explanation are realized.

Next, the operation of the card usage management system according to the embodiment will be described.

4 to 6 are flowcharts showing a particularly main flow of payment simulation processing executed in cooperation between the card usage management server 10 and the user terminal 20.

7 to 16 are diagrams illustrating a screen displayed at any time on the touch panel type display unit 25 of the user terminal 20 in the process of payment simulation.

As described above, in the present embodiment, the display of various screens on the touch panel display unit 25 of the user terminal 20 includes data such as payment amount sent from the card usage management server 10 and information for identifying the screen. Based on the above, the user terminal 20 side constructs bitmap format display data using the card use screen generation data 22w1 and the card use dedicated screen data 22w2, and stores the display data in the display data 22w3. ..

When the card use dedicated application 22p2 is started in the user terminal 20 in response to the operation of the user (user) (step T11), the CPU 21 is input by the user or is already input and stored. The ID data of the existing card user is transmitted to the card usage management server 10 (step T12).

When the card user ID data transmitted from the user terminal 20 is received by the card usage management server 10 (step S11), the CPU 11 displays the home screen on the user terminal 20 according to the screen generation data acquisition application 12p3. Various data necessary for generating the screen necessary for displaying are acquired and transmitted to the user terminal 20 as the data for generating the screen (step S12).

When the user terminal 20 receives the screen generation data from the card usage management server 10, the CPU 21 creates display data based on the received screen generation data, and the card usage dedicated application is used. The home screen is displayed on the touch panel type display unit 25 (step T13).

FIG. 7A is a home screen SC11 displayed on the touch panel type display unit 25 of the user terminal 20 at this time. On the home screen SC11, the latest payment amount is shown together with a graph, and the "view details" button BT01 for displaying the details is displayed.
Further, at the lower end of the screen SC11, "Home" icon IC01, "Easy alert" icon IC02, "Pinch avoidance" icon IC03, "Emolog" icon IC04, "○○○ application" for indicating specific service items. Five icons IC05 are displayed.

The "home" icon IC01 is an icon for returning to the home screen, and since it is the home screen at the present time, the operation is invalid.
The "reference alert" icon IC02 is an icon for setting a function for alerting the application when the usage amount determined by oneself is reached.
The "pinch avoidance" icon IC03 is an icon for shifting to an application that freely adjusts the repayment period and the monthly repayment amount in an easy-to-understand manner, as will be described in detail later in the present embodiment.
The "emolog" icon IC04 is an icon for shifting to an application for looking back on the satisfied consumption (card usage) of oneself (card user).
The "○○○ app" icon IC05 is an icon for migrating to the official app of XX company that provides the card use-only app.

When any of the five displayed icons is touch-operated by the user, the process related to the selected function is executed.

FIG. 7B illustrates a screen immediately after pressing the “pinch avoidance” icon.

In the user terminal 20, the CPU 21 transmits data indicating an item for which any item has been touch-operated to the card usage management server 10, and determines whether or not the touched item is "pinch avoidance". (Step T14).

When it is determined that the touched item is an item other than "pinch avoidance" (NO in step T14), the CPU 21 performs a process corresponding to that item based on the data sent from the card usage management server 10 thereafter. However, further description will be omitted, assuming that the processing is other processing that is not directly related to the present embodiment.

If it is determined in step T14 that the touched item is "pinch avoidance" (YES in step T14), the CPU 21 uses the data indicating the touched item "pinch avoidance" together with the user's ID data on the card. It is transmitted to the management server 10.

The card usage management server 10 transmits data to the user terminal 20 for displaying a screen for adjusting the payment amount and depositing money into the account, which is the first screen of the "pinch avoidance" item ( Step S13).

The user terminal 20 creates display data based on the data sent from the card usage management server 10 and displays a screen for adjusting the payment amount and depositing money into the account (step T15).

FIG. 7B illustrates a head screen SC12 displayed on the touch panel display unit 25 of the user terminal 20 for operating the adjustment of the payment amount and the payment to the account. On this screen SC12, as options for newly borrowing, the button BT11 that wants to deposit money in the designated account, the button BT12 that wants to adjust the payment amount, and this screen SC12 are closed to close the card use-only application. A "close" button BT13 for the purpose is arranged, and one of them is waited for an operation.

When any of the buttons BT11 to BT13 is touch-operated on the screen SC12, the CPU 21 transmits the data corresponding to the operation to the card usage management server 10, and the touch operation adjusts the payment amount. It is determined whether or not the button BT12 is desired (step T16).

Regarding the touch operation of the "close" button BT13, the following description will be omitted, assuming that the application is terminated as described above.

In step T16, when it is determined that the button BT12 for which the payment amount is to be adjusted is touch-operated (YES in step T16), the CPU 21 manages the card usage together with the user's ID data in the data corresponding to the touch-operated button BT12. Send to server 10.

In the card usage management server 10 that has received the data corresponding to the operation of the button BT12, the CPU 11 generates data for displaying the screen for determining the payment plan and transmits it to the user terminal 20 (step S14). ).

The user terminal 20 that has received the data from the card usage management server 10 creates display data for plan determination based on the received data and displays it on the touch panel type display unit 25 (step T17).

FIG. 8A illustrates a screen SC13 for determining a plan, which is displayed on the touch panel type display unit 25 of the user terminal 20. On this screen SC13, as an option, the "split change" button BT14 for changing the content of the installment payment for each contract, the content of the revolving payment for each contract individually, for the specified amount unit, or for all payable receivables is changed. A "revolving change" button BT15 and a "to simulation" button BT16 that changes payment conditions while simulating from the current overall payment status are arranged, and one of them waits for a touch operation.

When any of the buttons BT14 to BT16 is touch-operated on the screen SC13, the CPU 21 transmits the data corresponding to the touch operation to the card usage management server 10, and the touch operation is "to simulation". It is determined whether or not the button BT16 is used (step T18).

When it is determined that the touch-operated item is the "split change" button BT14 or the "revolving change" button BT15 (NO in step T18), the CPU 21 is based on the data sent from the card usage management server 10 thereafter. , The process of changing the selected individual payment terms is continued, but further description will be omitted as it is another process not directly related to the present embodiment.

Further, in step T18, when it is determined that the touch-operated "to simulation" button BT16 (YES in step T18), the CPU 21 uses the data indicating the touch-operated "to simulation" button BT16 as the user's ID. It is transmitted to the card usage management server 10 together with the data.

The card usage management server 10 that has received the data from the user terminal 20 refers to the user ID data 12d1, the authority data 12d3, the credit data 12d4, and the payment amount data 12d6 based on the received data, and then starts the simulation. The screen data is transmitted to the user terminal 20. (Step S15).

The user terminal 20 that has received the data from the card usage management server 10 creates display data based on the received data, and displays the simulation head screen on the touch panel type display unit 25 (step T19).

FIG. 8B illustrates a simulation head screen SC14 displayed on the touch panel type display unit 25 of the user terminal 20. On this screen SC14, the withdrawal amount that the card user wishes to change with respect to the withdrawal amount (¥ 92,931) of the latest payment date (2/27) of the card user who is the user of the user terminal 20. Input area IA11 for inputting, "I want to" button BT17 for shifting to the state of comprehensively simulating other payment amounts after inputting the desired amount of withdrawal attached to the input area IA11, screen SC13 immediately before There is a "return" button BT18 to return to.

Regarding the touch operation of the "return" button BT18, as described above, it returns to the state of the screen SC13 immediately before, and the following description will be omitted.

On the screen SC14, the desired amount to be withdrawn is input to the input area IA11, and the input is confirmed by operating the "want to" button BT17 (step T20).

The CPU 21 transmits the data of the desired withdrawal amount after the change input to the input area IA11 at that time to the card usage management server 10 together with the user's ID data (step T21).

In the card usage management server 10, the CPU 11 receives the data of the desired amount of withdrawal from the user terminal 20 (step S16). The CPU 11 first refers to the user ID data 12d1, the authority data 12d3, the credit data 12d4, and the payment amount data 12d6, assuming that the revolving payment is prioritized by default, while the revolving payment and the installment payment are prioritized in the present embodiment. Based on the desired amount of data, the payment amount for each usage period that constitutes the revolving payment simulation screen is calculated and transmitted to the user terminal 20 as data for creating the revolving payment simulation screen. (Step S31).

In the user terminal 20, the CPU 21 creates display data including graph creation based on the data received from the card usage management server 10, and displays the revolving payment / installment payment simulation screen on the touch panel display unit 25 (step). T31).

FIG. 9A illustrates a payment simulation screen SC15 for revolving payment / installment payment. FIG. 8A shows, for example, a simulation result when "46,000" yen is input as the withdrawal amount of the desired latest payment date in the input area IA11 of FIG. 8B. The screen contents in the range that cannot be displayed by the touch panel type display unit 25 correspond by moving the display range according to the scroll operation of the screen by the card user. As described above, in the present embodiment, the "revolving payment" tab TB11 and the "installment payment" tab TB12 are described together as the default revolving payment simulation screen is presented at the beginning of the simulation screen, and the "revolving payment" tab TB11. It presents the total amount of payment with the side operated and the individual payment amount for each usage period.

In the "Revolving payment" tab TB11 and below, the "year" and "month" for which the repayment is completed, the total payment amount, the fee amount, the payment amount and the period can be freely combined, and the guide message GM11, the payment period and Simulation change part SM11 that presents the monthly payment amount and accepts each change, image part PI11 that shows the future payment image in a bar graph, " "Next" button BT19, "Return" button BT18 to return to the previous screen SC14, presentation of the total payment amount of revolving payment and the fee, and "Next" button BT20 to confirm the contents are arranged. The payment confirmation unit PT11 is arranged.

Of these, the simulation change unit SM11 is provided with controls "-" and "+" for increasing and decreasing the payment period, and controls "-" and "+" for increasing and decreasing each of the monthly payment amounts. And the payment period and monthly payment amount are displayed.

In this simulation change unit SM11, instead of changing either the payment period or the monthly payment amount, the revolving payment payment course after the latest payment date is stepped by the bimonthly payment amount according to the payment balance. You may present a course that slides in a target manner, or an operator that changes the monthly payment amount course, for example, with the monthly payment amount as a fixed amount.

In addition, the image section PI11 showing the future payment image as a bar graph displays an image in which the future monthly payment amount is made into a bar graph only with the payment amount for this application.

In the image section PI11, by touching "Display payment for this application" on the screen, instead of the default, the display mode is switched to "Display all payments" for each month in the future. Regarding the payment amount, it is also possible to display a bar graph image in which the payment amount for this application, the payment amount for installments, and the payment amount for shopping such as unconfirmed lump sum payment are color-coded.

In the payment simulation screen SC15 of FIG. 9A, the image unit PI11'as shown in FIG. 10A may be displayed instead of the simulation change unit SM11 and the image unit PI11.

In FIG. 10A, in this image unit PI11', the current revolving payment course setting is the fixed-price course "30,000 yen course", the operator "∨" for changing the course, and the revolving change. Regarding the later payment amount and the fee, and the future monthly payment amount due to this payment change, the payment amount changed this time, the payment amount such as installment payment and annual membership fee that can not be changed, and the one-time payment after the next month The bar graph image is displayed by color-coding the payment amount for shopping such as bonus lump sum payment.

Also in the image unit PI11'of FIG. 10A, a display mode corresponding to "all payments", which is switched from the default display mode of "change of payment this time", is set, and as described above, the bar graph is displayed. The state in which the image is displayed is illustrated. By touching "Change this payment" on the screen, you can switch to the display mode that displays only the original default "Change this payment" and display the corresponding bar graph image. ..

In the CPU 21 of the user terminal 20, it is determined whether or not the "installment payment" tab TB12 for shifting to the installment payment simulation screen has been operated from the state where the screen SC15 is displayed on the touch panel type display unit 25 (step). T32).

When it is determined that the "installment payment" tab TB12 is not operated (NO in step T32), the CPU 21 further executes a process of rewriting the display contents in the simulation change unit SM11 according to the operation in the simulation change unit SM11. While (step T33), it is further determined whether or not the "Next" buttons BT19 and BT20 have been operated (step T34).

When it is determined that the "Next" buttons BT19 and BT20 are not operated (NO in step T34), the CPU 21 further returns to the processing from step T31 and continues the processing on the revolving payment simulation screen SC15 as described above. ..

In step T33, when an operator corresponding to the payment period or monthly payment amount in the simulation change unit SM11 is operated, the CPU 21 sends data indicating the operation to the card usage management server 10 together with the user's ID data. And send.

In the card usage management server 10, the CPU 11 receives the operation data from the user terminal 20 and executes a simulation process of recalculating the payment period and the payment amount comprehensively, and the calculated simulation results are obtained as authorization data 12d3. Temporarily store each of the bond data 12d4 as copy data different from this data (step S32).

Then, the CPU 11 transmits the calculated simulation result data to the user terminal 20 as data for displaying the simulation screen SC15 (step S33).

In the user terminal 20, in the process in which the CPU 21 repeatedly executes the processes of steps T31 to T34, while executing the process of rewriting the display contents in the simulation change unit SM11 as described above by communicating with the card usage management server 10. Waits for the "installation payment" tab TB2 for moving to the installment payment simulation screen to be operated, or for the "next" buttons BT19 and BT20 to be operated.
Although the description is omitted in the flowchart of FIG. 5 for the sake of explanation, when the "return" button BT18 is operated, the screen returns to the screen displayed immediately before that.

In step T32, when it is determined that the "installment payment" tab TB12 for shifting to the installment payment simulation screen has been operated (YES in step T32), the CPU 21 operates the "installment payment" tab TB12 for the card usage management server 10. The data indicating that the payment has been made is transmitted together with the user's ID data, and the data for the simulation screen of the installment payment amount sent from the card usage management server 10 is received and displayed (step T35).

At this time, in the card usage management server 10, the CPU 11 receives the user ID data 12d1 and the user ID data 12d1 based on the data of the desired withdrawal amount received from the user terminal 20 corresponding to the simulation start screen SC14 shown in FIG. 8 (B). Simulation of installment payment amount by referring to authority data 12d3, credit data 12d4, and payment amount data 12d6, taking into consideration the payment amount and the number of installments when changing one-time payment and bonus lump sum payment shopping to installment payment. Data for displaying the payment amount and the graph of the payment amount for each usage period constituting the screen is created and transmitted to the user terminal 20 (step S34).

FIG. 9B illustrates the revolving payment / installment payment payment simulation screen SC16 displayed on the touch panel display unit 25 of the user terminal 20. FIG. 8B shows, for example, a simulation result when "46,000" yen is input as the withdrawal amount of the desired latest payment date in the input area IA11 of FIG. 8B. Here, it corresponds to the operation of the "installment payment" tab TB12. The screen contents in the range that cannot be displayed by the touch panel type display unit 25 correspond by moving the display range according to the scroll operation of the screen by the card user.

In the "installment payment" tab TB12 or less, the "year" and "month" that repayment will be completed when changing to installment payment, the total payment amount, the fee amount of them, and the change to the installment condition for projects below the specified amount of installment payment Guide message GM12 to the effect that it cannot be done, guide message GM13 to the effect that the payment amount can be set for personal reasons (for projects with an amount higher than that), and accept the change of period by presenting the payment period and monthly payment amount Simulation change part SM12, image part PI12 showing future payment image in bar graph, "Next" button BT21 to confirm the application contents after changing the conditions of installment payment, "Return" to return to the previous screen SC14 The button BT18 is arranged.

Of these, in particular, in the simulation change unit SM12, controls "-" and "+" for increasing or decreasing the payment period are provided and displayed, and the payment period and the monthly payment amount are displayed.

In addition, the image unit PI12, which represents the future payment image as a bar graph, displays an image in which the future monthly payment amount is made into a bar graph only by the installment payment amount.

In the image section PI12, by touching "Display payment for this application", the display mode is switched to "Display all payments" instead of the default, and the monthly payment amount in the future It is also possible to display a bar graph image in which the payment amount of the installment payment, the payment amount of the application this time, and the payment amount of shopping such as unconfirmed lump sum payment are color-coded.

In the payment simulation screen SC16 of FIG. 9B, instead of displaying the simulation change unit SM12 and the image unit PI12, the image unit PI12'as shown in FIG. 10B may be displayed.

In FIG. 10B, in this image unit PI12', the operator ">" for changing the number of installments, the one-time payment calculated from the desired amount of withdrawal, and the payment that can be changed from the one-time payment and the bonus lump sum payment shopping to the installment payment. Regarding the total amount, the fee, and the future monthly payment amount due to this payment change, the payment amount changed this time, other installment payments that can not be changed, revolving payments that can not be changed on this screen, etc. The image is displayed as a bar graph by color-coding the payment amount for shopping such as one-time payment and bonus payment.

Also in the image unit PI12'of FIG. 10B, a display mode corresponding to "all payments", which is switched from the default display mode of "change of payment this time", is set, and as described above, the bar graph is displayed. The state in which the image is displayed is illustrated. By touching "Change this payment" on the screen, you can switch to the display mode that displays only the original default "Change this payment" and display the corresponding bar graph image. ..

In the CPU 21 of the user terminal 20, it is determined whether or not the "revolving payment" tab TB11 for shifting to the simulation screen of revolving payment has been operated from the state where the screen SC16 is displayed on the touch panel type display unit 25. (Step T36).

When it is determined that the "revolving payment" tab TB11 is not operated (NO in step T36), the CPU 21 further executes a process of rewriting the display contents in the simulation change unit SM12 according to the operation in the simulation change unit SM12. While (step T37), it is further determined whether or not the "Next" button BT21 has been operated (step T38).

When it is determined that the "Next" button BT21 is not operated (NO in step T38), the CPU 21 further returns to the process from step T35 and continues the process on the installment payment simulation screen SC16 as described above.

In step T37, when the operator corresponding to the payment period in the simulation change unit SM12 is operated, the CPU 21 transmits data indicating the operation to the card usage management server 10 together with the user's ID data.

In the card usage management server 10, the CPU 11 receives the operation data from the user terminal 20, refers to the user ID data 12d1, the authority data 12d3, the credit data 12d4, and the payment amount data 12d6, and makes payments related to revolving payment and installment payment. A simulation process for comprehensively recalculating the period and the payment amount is executed, and the calculated simulation results are temporarily stored in the authority data 12d3 and the credit data 12d4 as copy data different from this data (step S35).

Then, the CPU 11 transmits the calculated simulation result data to the user terminal 20 as data for displaying the simulation screen SC16 (step S36).

In the user terminal 20, in the process in which the CPU 21 repeatedly executes the processes of steps T35 to T38, while executing the process of rewriting the display contents in the simulation change unit SM12 as described above by communicating with the card usage management server 10. , Waits for the "revolving payment" tab TB11 for shifting to the revolving payment simulation screen to be operated or the "next" button BT21 to be operated.
Although the description is omitted in the flowchart of FIG. 5 for the sake of explanation, when the "return" button BT18 is operated, the screen returns to the screen displayed immediately before that.

In step T36, when it is determined that the "revolving payment" tab TB11 for shifting to the revolving payment simulation screen has been operated (YES in step T36), the CPU 21 sends the "revolving payment" tab to the card usage management server 10. The data indicating that the TB11 has been operated is transmitted, the process returns from step T31, the data for the simulation screen of the revolving payment amount sent from the card usage management server 10 is received, and the display data is displayed. After creating it, it is displayed on the touch panel type display unit 25.

When it is determined in step T34 that either the "Next" button BT19 or BT20 has been operated (YES in step T34), and when it is determined in step T38 that the "Next" button BT21 has been operated (YES in step T38). ), The CPU 21 transmits the data corresponding to the operation to the card usage management server 10 together with the user's ID data.

In the card usage management server 10, the CPU 11 receives the data from the user terminal 20, refers to the latest authority data and the copy data of the credit data temporarily stored in the authority data 12d3 and the credit data 12d4, and refers to the confirmation screen. Is transmitted to the user terminal 20 (step S37).

In the user terminal 20, the CPU 21 receives the data from the card usage management server 10 to create display data, and displays the confirmation screen of the application contents on the touch panel display unit 25 (step T39).

FIG. 11A illustrates a confirmation screen SC17 of application contents displayed on the touch panel type display unit 25. This screen SC17 exemplifies the confirmation contents from the revolving payment simulation screen, the total amount before the change of the revolving payment, the course used in the payment contents, the total payment amount, the fee thereof, and the caution regarding the change. In addition to displaying the matters, the "Apply" button BT22 for instructing the application after confirmation and the "Modify" button BT23 for modifying the changed contents of the payment terms are displayed at the lower part.

While displaying the confirmation screen SC17, the CPU 21 waits for the "apply" button BT22 to be operated (step T40).

Then, in step T40, when it is determined that the "apply" button BT22 has been operated (YES in step T40), the CPU 21 transmits the data corresponding to the operation to the card usage management server 10 together with the user's ID data.

In the card usage management server 10, the CPU 11 receives the data from the user terminal 20, and as a process for confirming, updates and stores the contents stored in the payment amount data 12d6 based on the latest copy data. (Step S38), data for displaying a screen indicating that the application has been completed is transmitted to the user terminal 20 (step S39), and once this process is completed, the next connection request is made. Prepare for.

In the user terminal 20, the CPU 21 creates display data based on the data received from the card usage management server 10, displays the application completion screen on the touch panel display unit 25, and temporarily ends the series of processes. ..

FIG. 11B illustrates an application completion screen SC18 displayed on the touch panel type display unit 25 of the user terminal 20. On this screen SC18, a guide message is displayed indicating that the application has been completed, the payment conditions have been changed, and the current usage / payment status can be confirmed from the home screen, and "Go to home" for moving to the home screen. Button BT24 is displayed.

FIG. 12A exemplifies the explanation screen SC19 displayed on the touch panel type display unit 25 in response to the operation of “What is the difference between revolving and division?” Shown at the upper parts of the SC payment simulation screens SC15 and SC16. Is.

On this screen SC19, while explaining revolving payment and installment payment, it is displayed that the fee rate is the same for revolving payment and installment payment, and a "close" button BT25 for closing this screen SC19 and returning to the original screen is displayed. doing.

FIG. 12B illustrates, for example, the advice screen SC20 displayed on the touch panel display unit 25 in response to the touch operation of the guide message GM11 on the SC payment simulation screen SC15 or the guide message GM13 on the SC payment simulation screen SC16. is there.

On this screen SC20, the monthly payment amount is taken as an example of borrowing 60,000 yen and returning 25,000 yen in the first month to the effect that the fee can be reduced by making a large amount of payment early. It is shown together with the bar graph and the total fee, and the "close" button BT26 for closing this screen SC20 and returning to the original screen is displayed.

Further, on the user terminal 20, the button BT11 requesting payment to the designated account as a new borrowing from the top screen SC12 for operating the adjustment of the payment amount and the payment to the account shown in FIG. 7 (B). Is operated, in step T16, the operation of this button is determined (NO in step T16), and the CPU 21 sends the data corresponding to the touch-operated button BT11 to the card usage management server 10 together with the user's ID data. And send.

In the card usage management server 10 that has received the data corresponding to the operation of the button BT 11, the CPU 11 transmits the data for displaying the first screen for receiving the application for net caching to the user terminal 20 (step S51).

The user terminal 20 that has received the data from the card usage management server 10 creates a head screen for receiving an application for net caching based on the received data and displays it on the touch panel display unit 25 (step T51).

FIG. 13A illustrates a head screen SC21 for receiving an application for net caching, which is displayed on the touch panel display unit 25 of the user terminal 20. On this screen SC21, it is possible to deposit in a minimum of several tens of seconds when cashing online, if the holder is the same, it is possible to deposit to an account other than the withdrawal account of the card used, and the payment status can be checked from the home screen of this application. Along with listing the merits such as being easy to check, the "Click here for details on net caching" button BTXIIIa to explain the details of net caching, and the button BTXIIIb to move to the screen explaining the details such as loan conditions, etc. The "Next" button BT27 for moving to the actual application screen is displayed.

"Click here for details on net caching" button When BTXIIIa is touch-operated, the screen transitions to a screen that lists useful and advantageous points in net caching, precautions regarding them, and the login button for "application for net caching". To do.
When the button BTXIIIb for moving to the screen explaining the details of the loan conditions etc. is touch-operated on the screen SC21, (a) enlightenment wording about caching and (b) registration in the money lending business register prepared in the application. The collation, name or name, (c) money lending business registration number, (d) association member number, (e) telephone number listed in the register, (f) repayment simulation, (g) loan condition table, etc. Transit to the screens listed with the "Back" button.
Further, when the "Next" button BT27 is touch-operated on the screen SC21, the CPU 21 transmits the data corresponding to the touch operation to the card usage management server 10 together with the user's ID data.

In the card usage management server 10 that has received the data corresponding to the operation of the "Next" button BT27, the CPU 11 has the credit data stored in the credit data 12d4 and the payment amount data stored in the payment amount data 12d6. After checking the loan limit amount based on, the maximum amount of money that can be newly used is calculated, and the data for displaying the screen for accepting the deposit amount of net cashing is transmitted to the user terminal 20 ( Step S52).

The user terminal 20 that has received the data from the card usage management server 10 creates display data on the screen that accepts the usage amount of net caching based on the received data and displays it on the touch panel type display unit 25 (step T52). ..

FIG. 13B illustrates a screen SC22 for accepting a deposit amount for net cashing, which is displayed on the touch panel type display unit 25 of the user terminal 20. On this screen SC22, a guide message asking how much the usage amount is, a usage frame, and an available balance are presented, and an input area IA12 in units of 10,000 yen and an input area IA13 in units of 1,000 yen are displayed, and the lower part thereof. In addition, a button BTXIIIc stating that the "caching statement mail notification service" will be applied at the same time as this use as confirmation of the consent content, and a "next" button BT28 for confirming the usage amount and moving to the next screen. Is displayed.
When the button BTXIIIc in the range including "Cashing details mail notification service" is touch-operated, the buttons for logging in to My Page of Net Caching, the button for moving to new registration of Net Caching, terms of use and frequently asked questions are listed. Transition to the screen that was displayed.

The CPU 21 receives the amount of money to be input to the input area IA12 in units of 10,000 yen and the input area IA13 in units of 1,000 yen according to the operation of the card user, and then based on the touch operation of the "Next" button BT28. , The received usage amount data is transmitted to the card usage management server 10 (step T53).

In the card usage management server 10 that has received the usage amount data, the CPU 11 acquires the received usage amount (step S53), and then displays the data for displaying the screen for selecting the deposit destination account. , Transmit to the user terminal 20 (step S54).

The user terminal 20 that has received the data from the card usage management server 10 creates display data for a screen for selecting a payment destination based on the received data and displays it on the touch panel display unit 25 (step T54).

FIG. 14A illustrates a screen SC23 for selecting a deposit destination for net cashing, which is displayed on the touch panel type display unit 25 of the user terminal 20. On this screen SC23, the button BT29 for instructing the deposit to the withdrawal account registered with the usage card (○○○ card) and the payment to another bank account of the same holder as the holder of the usage card are instructed. The button BT30 to be pressed is displayed, and the touch operation to any of the buttons BT29 and BT30 is waited for.

When any of the buttons BT29 and BT30 is touch-operated, the data corresponding to the operated button is transmitted to the card usage management server 10.

The card usage management server 10 that has received the data from the user terminal 20 transmits the data for the setting screen of the selected payment destination to the user terminal 20 (step S55).

If the touch operation in step T54 is the button BT29 instructing the withdrawal account registered with the user card, the CPU 11 refers to the user ID data 12d1 and withdraws. Data for confirming that the account is to be used is transmitted to the user terminal 20.

On the other hand, if the touch operation in step T54 is the button BT30 instructing the deposit to another bank account of the same holder as the holder of the card, the CPU 11 further presses the bank name, branch name, and account number. Data for the screen for data input including the above is transmitted to the user terminal 20.

The user terminal 20 that has received the data from the card usage management server 10 generates the necessary deposit setting screen display data based on the account selected by the touch operation and displays it on the touch panel display unit 25 (step T55). ).

In step T55, if the touch operation on the screen SC23 immediately before is the button BT29 instructing the deposit to the withdrawal account registered with the usage card, the CPU 21 is the account to which the deposit destination performs the withdrawal. A guide message for confirming that the button is displayed and a button for confirmation are displayed on the touch panel display unit 25, and when a touch operation is performed on the button, data based on the operation is transmitted to the card usage management server 10. Send to.

Further, in step T55, when the touch operation on the screen SC23 immediately before is the button BT30 instructing the deposit to another bank account of the same holder as the holder of the card, the CPU 21 uses the bank name. A screen provided with an input area for data input for designating a branch name and an account number is displayed on the touch panel display unit 25, and input contents in each input area are accepted. When the input to all the input areas is made, the CPU 21 transmits the data of the input contents to the card usage management server 10.

In the card usage management server 10 that has received the data from the user terminal 20, the CPU 11 executes a process of confirming the designated bank account as necessary, and then selects and inputs the number of payments. The screen data is transmitted to the user terminal 20 (step S56).

The user terminal 20 that has received the data from the card usage management server 10 creates display data for selecting and inputting the number of payments and displays it on the touch panel display unit 25 (step T56).

FIG. 14B illustrates a screen SC24 for selecting the number of payments for net caching, which is displayed on the touch panel display unit 25 of the user terminal 20. On this screen SC24, a button BT31 instructing to pay at one time and a button BT32 instructing to pay in multiple times using revolving payment are displayed, and touching either of these buttons BT31 or BT32 is performed. Wait for the operation to be performed.

When any one of the buttons BT31 and BT32 is touch-operated, the CPU 21 of the user terminal 20 determines whether or not the operated button is the button BT32 button (step T57).

In step T57, if it is determined that the button BT31 button is operated instead of the button BT32 button (NO in step T57), it means that the payment is instructed once, so that the CPU 21 manages the card usage. Data indicating that the button BT31 button has been operated is transmitted to the server 10.

In the card usage management server 10 that has received the data from the user terminal 20, the credit data stored in the credit data 12d4 and the credit data stored in the credit data 12d4 based on the deposit amount input by the CPU 11 and the number of payments being one. After calculating the payment amount based on the payment amount data stored in the payment amount data 12d6, the data for the confirmation screen of the application contents of the net cashing is transmitted to the user terminal 20 (step S60).

The user terminal 20 that has received the data from the card usage management server 10 creates display data for the net caching application based on the data received by the CPU 21, and displays a confirmation screen on the touch panel display unit 25 (step S60). ).

FIG. 15A illustrates a confirmation screen SC25 of application contents displayed on the touch panel type display unit 25. This screen SC25 exemplifies the confirmation contents from the application for net cashing, and shows the application amount to be deposited, the scheduled transfer date, the total payment amount including fees, the bank account information to which the deposit is transferred, and notes. At the bottom of the display, there is a "Apply" button BT33 that instructs you to apply after confirmation, a "Modify" button BT34 that corrects the changes in payment terms, and a guide message "Cancellation of future applications is not accepted. When the application is completed, we will send you a guidance email. Please log in to XX Net from the guidance email and check the transfer status. "

While displaying the confirmation screen SC25, the CPU 21 waits for the "apply" button BT33 to be operated (step T61).

Then, in step T61, when it is determined that the "apply" button BT33 has been operated (YES in step T61), the CPU 21 transmits the data corresponding to the operation to the card usage management server 10 together with the user's ID data.

In the card usage management server 10, the CPU 11 receives the data from the user terminal 20 and performs update storage of the data stored in the credit data 12d4 as a process for confirmation, and also in the payment amount data 12d6. After updating and memorizing the memorized contents (step S61), the data for displaying the screen indicating that the application is completed is transmitted to the user terminal 20 (step S62). Finish the process and prepare for the next connection request.

In the user terminal 20, the CPU 21 displays the application completion screen received from the card usage management server 10, and once completes the series of processes.

FIG. 15B illustrates an application completion screen SC26 displayed on the touch panel type display unit 25 of the user terminal 20. On this screen SC26, a guide message is displayed to notify when the application is completed and the transfer is completed, and the current usage / payment status can be confirmed from the home screen, and "Go to home" for moving to the home screen. Button BT35 is displayed.

If it is determined in step T57 that the button BT32 button has been operated (YES in step T57), it means that the payment is instructed in multiple times by revolving payment, so that the CPU 21 is the card usage management server. Data indicating that the BT32 button has been operated for 10 is transmitted together with the user's ID data.

The card usage management server 10 that has received the data from the user terminal 20 presents the current usage amount based on the deposit amount input by the CPU 11, and then inputs the amount to be revolving on the latest payment date. The screen data for prompting is transmitted to the user terminal 20 (step S57).

In the user terminal 20 that has received the data from the card usage management server 10, the CPU 21 creates display data on the screen for inputting the amount to be revolving based on the received data, and displays it on the touch panel type display unit 25 ( Step T58).

FIG. 16A illustrates a screen SC27 for inputting the amount to be revolving, which is displayed on the touch panel type display unit 25 of the user terminal 20. On this screen SC27, the input area IA14 for inputting the desired payment amount on the latest payment date (2/27) of the card user who is the user of the user terminal 20 by revolving payment by net caching, the input area. After inputting the desired payment amount to IA14, a "Next" button BT36 is arranged to shift to a state of comprehensively simulating the remaining payment amount and the like.

When the "Next" button BT36 is touched on the screen SC27, the CPU 21 uses the data of the desired amount of revolving payment input in the input area IA14 at that time together with the user's ID data as the card usage management server. Send to 10.

When the CPU 11 receives the data of the desired amount of revolving payment from the user terminal 20 in the card usage management server 10, the CPU 11 refers to the user ID data 12d1, the credit data 12d4, and the payment amount data 12d6, and receives the desired amount of money. Calculate the payment amount for each usage period that constitutes the simulation screen of the revolving payment amount based on the data of, and create the data to display the graph.

The CPU 11 temporarily stores the calculated payment amount as copy data of the bond data separately from the original bond data (step S58), and then uses the data necessary to display the revolving payment simulation screen based on the result. It is transmitted to the person terminal 20 (step S59).

In the user terminal 20, the CPU 21 generates display data of a simulation screen of net caching by revolving payment based on the data received from the card usage management server 10 and displays it on the touch panel type display unit 25 (step T59).

FIG. 16B illustrates a payment simulation screen SC28 for net cashing by revolving payment. FIG. 6B shows a simulation result when, for example, the desired cashing usage amount of "50,000" yen is input to the input area IA14 of FIG. 16A and the payment for this month is 10,000 yen. .. The screen contents in the range that cannot be displayed by the touch panel type display unit 25 correspond by moving the display range according to the scroll operation of the screen by the card user.

On this screen SC28, the guide message GM14, the payment period and month, to the effect that the "year" and "month" when the repayment of this cashing is completed, the total payment amount, the fee amount, the payment amount and the period can be freely combined and set. Simulation change part SM13 that presents the payment amount for each and accepts each change, image part PI13 that shows the future payment image in a bar graph, "Next" to confirm the application contents after changing the conditions of revolving payment "To" button BT37, "Return" button BT38 to return to the previous screen SC27, presentation of the total payment amount of revolving payment and the fee, and payment with "Next" button BT39 to confirm the contents The confirmation unit PT12 is arranged.

Of these, especially in the simulation change unit SM13, the payment period and the controls "-" and "+" for increasing and decreasing the period, and the controls "-" and "+" for increasing and decreasing the monthly payment amount, respectively. "Is displayed, and the payment period and monthly payment amount are displayed. Regarding the increase / decrease in the monthly payment amount, in reality, a simulation including other receivables is executed according to this cashing, and then a process for adjusting the payment amount is executed.

In addition, in the image section PI13, which shows the future payment image as a bar graph, the payment amount for this application, the installment payment amount, and the unconfirmed shopping payment amount are color-coded for the future monthly payment amount. The image is displayed as a bar graph.

The CPU 21 of the user terminal 20 waits for the "Next" buttons BT37 and BT39 to be operated from the state in which the screen SC28 is displayed on the touch panel type display unit 25.

When an operator corresponding to the payment period or monthly payment amount in the simulation change unit SM13 is operated on the screen SC28, the CPU 21 sends data indicating the operation to the card usage management server 10 together with the user's ID data. And send.

In the card usage management server 10, the CPU 11 receives the operation data from the user terminal 20 and executes a simulation process of recalculating the payment period and the payment amount comprehensively, and the calculated simulation result is converted into the credit data 12d4. , Temporarily store as copy data different from this data.

Then, the CPU 11 transmits the calculated simulation result data to the user terminal 20 as display data of the simulation screen SC15.

In the user terminal 20, the "Next" buttons BT37 and BT39 are operated while the CPU 21 executes a process of rewriting the display contents in the simulation change unit SM13 as described above by communicating with the card usage management server 10. Wait for

When the "Next" buttons BT37 and BT39 are operated, the CPU 21 transmits the data corresponding to the operation to the card usage management server 10 together with the user's ID data.

In the card usage management server 10, the CPU 11 receives data from the user terminal 20, refers to the latest credit data temporarily stored in the credit data 12d4, creates data for displaying a confirmation screen, and uses it. The data is transmitted to the user terminal 20 (step S60).

In the user terminal 20, the CPU 21 receives the data from the card usage management server 10 and displays the confirmation screen of the application contents on the touch panel type display unit 25 (step T60).

At this time, the confirmation screen displayed on the touch panel type display unit 25 of the user terminal 20 is substantially the same as the content shown in FIG. 15 (A). However, the description of the payment method is not "one-time payment" but "caching revolving".

While displaying the confirmation screen, the CPU 21 waits for the "apply" button to be operated (step T61).

Then, when it is determined in step T61 that the "apply" button has been operated (YES in step T61), the CPU 21 transmits data corresponding to the operation to the card usage management server 10 together with the user's ID data.

In the card usage management server 10, the CPU 11 receives the data from the user terminal 20 and performs the update storage of the credit data stored in the credit data 12d4 as a process for confirmation, and the payment amount data 12d6. After updating and memorizing the memorized contents (step S61), the data for displaying the screen indicating that the application is completed is transmitted to the user terminal 20 (step S62). Finish the process and prepare for the next connection request.

In the user terminal 20, the CPU 21 displays the application completion screen received from the card usage management server 10, and once completes the series of processes.

At this time, the application completion screen displayed on the touch panel type display unit 25 of the user terminal 20 is the same as in FIG. 15 (B).

As described in detail above, according to the present embodiment, it is possible to construct a new repayment plan according to the wishes of the card user while presenting the payment status including a plurality of payment methods in an easy-to-understand manner. ..

Further, in the present embodiment, various payment conditions on the payment simulation screen are changed many times, the repayment plan that seems to be optimal is examined each time, and the repayment plan is changed after obtaining the consent of the card user. Can be confirmed at.

Further, in the present embodiment, the desired payment amount for the latest planned payment amount is accepted, and the payment simulation screen is displayed after considering the received desired payment amount. Therefore, depending on the payment ability of the card user at that time. You can also build a more realistic and reasonable repayment plan.

Further, in the present embodiment, since the payment simulation screen displays an image in which the payment amount for each usage period is graphed together with the screen, the payment amount for each usage period is visually extremely easy to understand when using the card. Can be presented to a person.

Further, in the present embodiment, in the payment simulation screen, the screen is selectively displayed by using the tabs TB11 and TB12 for touch operation corresponding to a plurality of payment methods such as revolving payment and installment payment. Therefore, even if the user terminal 20 is a terminal device having a limited display capacity such as a smartphone, the screen can be effectively used to provide an easy-to-understand screen.

In the present embodiment, the card usage management server 10 transmits data such as various payment amounts to the user terminal 20, so that the user terminal 20 generates a card usage screen according to the card usage dedicated application 22p2. Using the data 22w1, the screen data 22w2 dedicated to card use, and the display data 22w3, a payment simulation screen as shown in FIGS. 7 to 16 is created and displayed on the touch panel display unit 25. Is not limited to this, the screen data to be displayed on the user terminal 20 is created on the card usage management server 10 side and transmitted to the card usage management server 10, and the user terminal 20 has a touch panel based on the received screen data. The display may be performed by the expression display unit 25.

In addition, the present invention is not limited to the above-described embodiment, and can be variously modified at the implementation stage without departing from the gist thereof. In addition, each embodiment may be carried out in combination as appropriate, and in that case, the combined effect can be obtained. Further, the above-described embodiment includes various inventions, and various inventions can be extracted by a combination selected from a plurality of disclosed constituent requirements. For example, even if some constituent requirements are deleted from all the constituent requirements shown in the embodiment, if the problem can be solved and the effect is obtained, the configuration in which the constituent requirements are deleted can be extracted as an invention.

10 ... Card usage management server 11 ... CPU
12 ... Storage unit 12D ... Management data storage area 12d1 ... User ID data 12d2 ... Merchant data 12d3 ... Authorized data 12d4 ... Credit data 12d5 ... Usage period data 12d6 ... Payment amount data 12P ... Program storage area 12p1 ... Server system program 12p2 ... Payment amount calculation application 12p3 ... Screen generation data acquisition application 12p4 ... Payment simulation providing application 13 ... External recording medium 14 ... Recording medium reading unit 15 ... Communication unit 16 ... Payment system communication unit 17 ... Input unit 18 ... Display unit 20 ... Use Person terminal 21 ... CPU
22 ... Storage unit 22P ... Program storage area 22p1 ... Terminal system program 22p2 ... Card usage dedicated application 22R ... Terminal data storage area 22W ... Work data storage area 22w1 ... Card usage screen generation data 22w2 ... Card usage dedicated screen data 22w3 ... Display Data 23 ... External recording medium 24 ... Recording medium reading unit 25 ... Touch panel display unit 26 ... Communication unit 30 ... Merchant terminal IN ... Communication network (Internet)
SN ... Card payment online network

Claims (10)

A card usage data storage means for storing card usage data including data on multiple payment methods including revolving payment and installment payment and usage amount according to the card usage of the card user, and
In response to a request from the card user terminal, on the basis of the card use data storage unit card use data stored in, the card user terminal calculates the payment schedule total amount of straight proximal to the plurality of payment methods Means of transmission and
Accepting a straight near-payment hope the total amount for the plurality of payment methods from the card user terminal, to reflect the payment hope the total amount that has been received, the individual and the whole of each use period corresponding to the plurality of payment methods A payment amount calculation method that recalculates the payment amount,
Including payment of the individual and overall each use time period corresponding to the plurality of payment methods recalculated with the payment amount calculation means, and generates data for displaying a payment screen sent to the card user terminal Means to do and
A card usage management device equipped with. The card usage management device according to claim 1, further comprising a means for receiving an instruction to change the monthly payment amount of revolving payment payment and the number of payments. The card usage management device according to claim 1, further comprising a means for receiving a change instruction of a payment course for revolving payment. The card usage management device according to claim 1, further comprising a means for receiving an instruction to change the installment condition of the installment payment. The card usage management device according to claim 4 , wherein the change of the installment condition is to change from lump-sum payment to installment payment. The card usage management device according to claim 5 , wherein the change from the lump sum payment to the installment payment is determined based on the card usage amount. Generate data for displaying the payment screen, including data for displaying a graphed image of payment amounts for each of a plurality of payment methods for each usage period.
The card usage management device according to any one of claims 1 to 6. The card usage management device according to any one of claims 1 to 7 , wherein the request from the card user terminal is a simulation request, and the payment screen is a payment simulation screen. By the processor of the card usage management device
Stores card usage data that includes data on multiple payment methods and usage amounts, including revolving payments and installment payments, according to the card usage of the card user.
In response to a request from the card user terminal, on the basis of the card use data, calculates the payment schedule total amount of straight proximal to the plurality of payment transmitted to the card user terminal,
Said accepting the payment hope the total amount of the direct proximity to the plurality of payment methods from the card user terminal, to reflect the payment hope the total amount that has been received, the individual and the whole of each use period corresponding to the plurality of payment methods of re-calculating the payments,
Data for displaying the payment screen, including individual and total payment amounts for each usage period according to the recalculated payment methods, is generated and transmitted to the card user terminal.
Card usage management method. The processor of the card usage management device,
A card usage data storage means for storing card usage data including data on multiple payment methods including revolving payment and installment payment and usage amount according to the card usage of the card user, and
In response to a request from the card user terminal, on the basis of the card use data storage unit card use data stored in, the card user terminal calculates the payment schedule total amount of straight proximal to the plurality of payment methods Means of transmission and
Accepting a straight near-payment hope the total amount for the plurality of payment methods from the card user terminal, to reflect the payment hope the total amount that has been received, the individual and the whole of each use period corresponding to the plurality of payment methods A payment amount calculation method that recalculates the payment amount,
Including payment of the individual and overall each use time period corresponding to the plurality of payment methods recalculated with the payment amount calculation means, and generates data for displaying a payment screen sent to the card user terminal Means to do and
A program of the card usage management device to make it function.

Images