Terminal device, server, information processing method, and program

Abstract

To provide a terminal device, a server, an information processing method, and a program that make it easy for a user to select settlement means, which is troublesome for the user.SOLUTION: A terminal device includes: a terminal output unit 15 that outputs a settlement screen that receives selection of one of two or more settlement means; a terminal reception unit 12 that receives the selection of one of two or more settlement means on a screen; a terminal processing unit 13 that performs settlement processing, which is processing for settlement, using the selected one of the settlement means received by the terminal reception unit 12; and a terminal update unit 132 that performs, in association with the selected settlement means received by the terminal reception unit 12, update processing to update use information that identifies use status of one of settlement means. A settlement screen displays settlement means that are actively used, as identified by the use information corresponding to each of two or more settlement means, in a more prominent manner compared to settlement means that are not actively used, and then the terminal device 1 provides a settlement screen that corresponds to the user use status of the settlement means, making it easier for the user to select a settlement means.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a terminal device or the like that can perform processing for settlement. [Background technology]

[0002] Conventionally, there have been applications and sites that allow a user to select one payment method from two or more payment methods to make a payment (see Patent Document 1). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] amazon.co.jp [Retrieved March 12, 2024], Internet [URL: https: / / www.amazon.co.jp / ] Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the prior art, the payment screen that accepts the selection of one of two or more payment methods is a screen that displays only the payment methods adopted by the business operator. In other words, the payment screen is not based on the user's usage of the payment method, which can make selecting a payment method troublesome for the user. [Means for solving the problem]

[0005] The terminal device of the first invention comprises a terminal output unit that outputs a payment screen that accepts the selection of one of two or more payment means; a terminal reception unit that accepts the selection of one of the two or more payment means on the payment screen; a terminal processing unit that performs payment processing, which is processing for payment, using the selected one payment means accepted by the terminal reception unit; and a terminal update unit that performs update processing to update usage information that identifies the usage status of the selected one payment means accepted by the terminal reception unit, in association with the selected one payment means accepted by the terminal reception unit, wherein the payment screen is a screen that displays payment means that are more actively used, as identified by the usage information corresponding to each of the two or more payment means, in a manner that makes them stand out compared to payment means that are less actively used.

[0006] With this configuration, a payment screen is provided that corresponds to the user's usage of the payment method, making it easier for the user to select a payment method.

[0007] In addition, compared to the first invention, the terminal device of the second invention is a terminal device that further includes a terminal configuration unit that references a usage management unit in which usage information corresponding to two or more payment methods is stored, and configures a payment screen that displays payment methods that are used more frequently as specified by the usage information in a more prominent manner compared to payment methods that are used less frequently.

[0008] With this configuration, a payment screen is provided that corresponds to the user's usage of the payment method, making it easier for the user to select a payment method.

[0009] In addition, compared to the first invention, the terminal device of the third invention is a terminal device that further comprises a terminal receiving unit that receives payment screen information that constitutes the payment screen from a server, and a terminal configuration unit that references a usage management unit in which usage information corresponding to each of two or more payment methods is stored, and constructs a payment screen from the payment screen information received by the terminal receiving unit, in which payment methods that are more actively used as specified by the usage information are displayed in a more prominent manner compared to payment methods that are less actively used.

[0010] With this configuration, a payment screen is provided that corresponds to the user's usage of the payment method, making it easier for the user to select a payment method.

[0011] Furthermore, in the terminal device of the fourth invention, compared to the second or third invention, the usage management unit stores usage information corresponding to two or more payment methods for each of two or more apps, and the terminal configuration unit configures a payment screen using the usage information corresponding to the app being used.

[0012] With this configuration, a payment screen is provided that corresponds to the user's usage of the payment method, making it easier for the user to select a payment method.

[0013] Furthermore, compared to the first invention, the terminal device of the fifth invention further includes a terminal receiving unit that receives payment screen information from a server that references a usage management unit in which usage information corresponding to each of two or more payment methods is stored and acquires payment screen information that constitutes a payment screen, and the terminal output unit is a terminal device that outputs a payment screen based on the payment screen information received by the terminal receiving unit.

[0014] With this configuration, a payment screen is provided that corresponds to the user's usage of the payment method, making it easier for the user to select a payment method.

[0015] Furthermore, the terminal device of the sixth invention is a terminal device according to any one of the first to fifth inventions, wherein the usage information includes one or more of the following information: the number of times the payment means is used, the total usage amount which is the cumulative amount of payments made using the payment means, the total usage time which is the cumulative operation time related to the payment means, the average usage amount which is the average amount of a single payment made using the payment means, and the maximum usage amount per single payment of the payment means; and the payment screen is a screen which displays the payment means in a more prominent manner the more the payment means is used, or the larger the total usage amount of the payment means, the longer the total usage time of the payment means, the smaller the difference between the current payment amount and the average usage amount, or the larger the maximum usage amount.

[0016] With this configuration, a payment screen is provided that corresponds to the user's usage status, such as the amount of time the payment method has been used, the number of times it has been used, or the amount used, making it easier for the user to select a payment method.

[0017] In addition, the server of the seventh invention is a server comprising: a screen management unit in which payment screen information constituting a payment screen that accepts selection of one of two or more payment methods; an instruction receiving unit that receives a transmission instruction from a terminal device, which is an instruction to transmit a payment screen and is an instruction that corresponds to a user identifier; a component that, in response to receiving the transmission instruction, acquires usage status information, which is two or more pieces of usage information corresponding to the user identifier that corresponds to the transmission instruction, from the usage management unit in which usage information corresponding to each of two or more payment methods for each user identifier is stored, and acquires payment screen information to be transmitted to the terminal device using the usage status information and the payment screen information; and a screen transmission unit that transmits the payment screen information acquired by the component unit to the terminal device.

[0018] With this configuration, a payment screen is provided that corresponds to the user's usage of the payment method, making it easier for the user to select a payment method. [Effects of the Invention]

[0019] The terminal device according to the present invention provides a payment screen according to the user's usage status of the payment means, making it easier for the user to select a payment means. [Brief explanation of the drawings]

[0020] [Figure 1] Block diagram of terminal device 1 according to the first embodiment. [Figure 2] Flowchart for explaining an example of operation of the simultaneous terminal device 1 [Figure 3] 10 is a flowchart illustrating a first example of the screen configuration process. [Figure 4] 10 is a flowchart illustrating a second example of the screen configuration process. [Figure 5] 10 is a flowchart illustrating a first example of the update process. [Figure 6] 10 is a flowchart illustrating a second example of the update process. [Figure 7] A diagram showing the usage status management table [Figure 8] Figure showing an example of the payment screen [Figure 9] Figure showing the same-end usage information management table [Figure 10] Conceptual diagram of information system A in embodiment 2 [Figure 11] Block diagram of Information System A [Figure 12] A flowchart illustrating an example of the operation of the terminal device 3 [Figure 13] 10 is a flowchart illustrating a first example of the screen configuration process. [Figure 14] 10 is a flowchart illustrating a second example of the screen configuration process. [Figure 15] Conceptual diagram of information system B in embodiment 3 [Figure 16] Block diagram of Information System B [Figure 17] A flowchart illustrating an example of the operation of the server 4 [Figure 18] 10 is a flowchart illustrating a first example of the screen configuration process. [Figure 19] 10 is a flowchart illustrating a second example of the screen configuration process. [Figure 20] 10 is a flowchart illustrating a first example of the update process. [Figure 21] 10 is a flowchart illustrating a second example of the update process. [Figure 22] A flowchart illustrating an example of the operation of the terminal device 5 [Figure 23] A diagram showing the usage information management table [Figure 24] Block diagram of a computer system according to the above embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0021] Hereinafter, embodiments of a terminal device and the like will be described with reference to the drawings. Note that components with the same reference numerals in the embodiments perform similar operations, and therefore repeated description may be omitted.

[0022] (Embodiment 1) In this embodiment, a terminal device is described which manages the usage status of two or more payment methods by a user and can dynamically change the screen for selecting two or more payment methods depending on the usage status.

[0023] Furthermore, in this embodiment, a terminal device is described in which the user's usage status of two or more payment methods is managed for each app or site, and the screen for selecting two or more payment methods can be dynamically changed depending on the app or site where the payment is made, according to the usage status of the payment method corresponding to the app or site. Note that the site has two or more web pages, but it may also be a single web page. In other words, the site here may also be a web page.

[0024] In this specification, information X being associated with information Y means that information Y can be obtained from information X, or information X can be obtained from information Y, and the method of association is not important. Information X and information Y may be linked, may exist in the same buffer, information X may be included in information Y, or information Y may be included in information X, etc.

[0025] Furthermore, in this specification, selecting or determining information Z means obtaining information Z, obtaining a pointer to information Z, obtaining the ID of information Z, setting a flag on information Z, etc., and it is sufficient if information Z can be accessed.

[0026] 1 is a block diagram of a terminal device 1 according to this embodiment. The terminal device 1 is a terminal used by a user. The terminal device 1 may be, for example, a smartphone, a tablet terminal, or a personal computer, but the type is not important.

[0027] The terminal device 1 includes a terminal storage unit 11, a terminal reception unit 12, a terminal processing unit 13, a terminal transmission unit 14, and a terminal output unit 15. The terminal storage unit 11 includes a usage management unit 111. The terminal processing unit 13 includes a terminal configuration unit 131 and a terminal update unit 132.

[0028] Various types of information are stored in the terminal storage unit 11. The various types of information include, for example, usage information (described later), one or more applications (hereinafter referred to as "apps") for making payments, and various types of software.

[0029] Usage management unit 111 stores usage information. The usage information includes two or more pieces of usage information. Each of the two or more pieces of usage information corresponds to a payment method identifier. Usage information may be stored in usage management unit 111 for each of two or more apps. That is, usage information may correspond to an app identifier. An app identifier is information that identifies an app. An app identifier is, for example, an app name or an app ID. The usage information for each of two or more apps may be usage information for two or more sites. That is, an app identifier may be a site identifier. A site identifier is, for example, a URL, a URI, or a site name.

[0030] Each of the two or more pieces of usage information is associated with a payment method. A payment method being associated with a payment method identifier means that a payment method is associated with the payment method. A payment method is a method used to pay for goods or services. Examples of payment methods are credit cards, electronic payments, debit cards, and cash. A payment method identifier is information that identifies a payment method. Examples of payment method identifiers are "credit card," "VISA (registered trademark) card," "JCB card (registered trademark)," "PayPay (registered trademark)," "LINE Pay (registered trademark)," "Rakuten Pay (registered trademark)," and "debit card."

[0031] Usage information is information relating to the usage status of a payment method. Usage information includes, for example, one or more of the following: the number of times a payment method has been used; the total amount of usage, which is the cumulative amount of payments made using the payment method; the total usage time, which is the cumulative amount of operation time related to the payment method; the average usage amount, which is the average amount of a single payment made using the payment method; and the maximum usage amount for a single payment made using the payment method. The number of times a payment method has been used may be cumulative information up to now, or may be information within a predetermined period (for example, the past year).

[0032] The terminal reception unit 12 receives various instructions and information, such as an instruction to launch a specific application, or an operation on an application or web page.

[0033] The terminal acceptance unit 12 accepts the selection of one of two or more payment methods on, for example, a payment screen.

[0034] Reception usually refers to the reception of information entered from an input device such as a keyboard, mouse, or touch panel, but the concept may also include the reception of information transmitted via a wired or wireless communication line, or the reception of information read from a recording medium such as an optical disk, a magnetic disk, or a semiconductor memory.

[0035] The means for inputting various instructions and information may be any means, such as a touch panel, keyboard, mouse, or menu screen.

[0036] The terminal processing unit 13 performs a payment process, which is a process for making a payment, using the selected payment method accepted by the terminal accepting unit 12. The payment process is, for example, a process of sending information necessary for payment to a payment server (not shown). The payment process is, for example, a process of making a payment using a payment app. Note that the payment process is a well-known process, so a detailed description will be omitted.

[0037] The device processing unit 13 performs processing in accordance with instructions and information received by the terminal receiving unit 12. Such processing is, for example, processing to start an application and processing to perform screen transitions in the application.

[0038] The terminal configuration unit 131 refers to the usage management unit 111 and configures a payment screen that, for example, displays payment methods that are used actively as identified by the usage information in a more prominent manner than payment methods that are used less actively.

[0039] The terminal configuration unit 131 refers to the usage management unit 111 and configures, for example, a payment screen that does not include payment methods that match the non-display condition. The non-display condition is a condition for hiding. For example, the non-display condition is "total number of uses >= threshold number of times AND score = 0." A payment screen is constructed in which payment means that are actively used as specified by the usage information are displayed in a more prominent manner than payment means that are not actively used.

[0040] Examples of prominent features include a high position on the screen, a prominent background color, a large display size, and text in a prominent font (e.g., bold font). Prominent features usually relate to attribute values ​​related to the display of an object that includes the payment method identifier to be selected. Display attribute values ​​include the object's position, background color, size, and font of text in the object. An object is information related to a payment method and is both a display and a selection target. An object is a component that makes up a user interface (screen), such as a menu item, a button, a check box, and text corresponding to the check box.

[0041] The payment screen is a screen for selecting one of two or more payment methods. It is preferable that the payment screen is a screen for accepting instructions to make a payment using the selected payment method.

[0042] The payment screen here is a screen that, for example, displays payment methods with active usage identified by usage information corresponding to two or more payment methods in a prominent manner compared to payment methods with inactive usage. Active usage means, for example, that the number of uses is equal to or greater than a threshold, the total usage amount (payment amount) is equal to or greater than a threshold, the average usage amount is equal to or greater than a threshold, the total usage time is equal to or greater than a threshold, or the maximum usage amount is equal to or greater than a threshold.

[0043] The payment screen here is a screen in which the payment method is displayed in a more prominent manner, for example, the longer the time the payment method has been used, the more frequently the payment method has been used, or the larger the amount used for the payment method.

[0044] The payment screen is a screen that displays payment methods in a more prominent manner, for example, when the absolute value of the difference between the current payment amount and the average payment amount is smaller and the paired payment method is associated with an average payment amount.

[0045] The terminal configuration unit 131 configures a payment screen using, for example, usage information corresponding to the app being used. The terminal configuration unit 131 acquires, for example, an app identifier being used. Next, the terminal configuration unit 131 acquires usage status information paired with the app identifier. Note that apps may also be considered to include websites. In such cases, the app identifier may be a site identifier (for example, a URL).

[0046] The terminal update unit 132 performs an update process to associate a payment method accepted by the terminal acceptance unit 12 with the usage information that specifies the usage status of the payment method.

[0047] The update process is typically a process of increasing a value in the usage information, such as a process of increasing the usage time, a process of increasing the number of times of usage, a process of increasing the usage amount, or a process of updating the score.

[0048] The terminal update unit 132 obtains a score using, for example, one or more pieces of information from the number of uses, total amount used, total time used, average amount used, and maximum amount used. The score is information that indicates the degree of activity in using a payment method. The score is, for example, an integer between 1 and 10, or between 0 and 100.

[0049] The terminal update unit 132 calculates the score using an increasing function that uses as a parameter one or more pieces of information from, for example, the number of uses, the total use amount, the total use time, the average use amount, and the maximum use amount.

[0050] The terminal update unit 132 may calculate, for example, the absolute value of the difference between the average usage amount and the current payment amount as the score.

[0051] The terminal transmitting unit 14 transmits various instructions and information.

[0052] The terminal output unit 15 outputs the payment screen configured by the terminal configuration unit 131. The terminal output unit 15 outputs a payment screen that accepts the selection of one payment method from two or more payment methods.

[0053] Here, output usually means display on a display, but it may also be a concept that includes projection using a projector, printing on a printer, sound output, transmission to an external device, storage on a recording medium, and handing over of processing results to other processing devices or other programs.

[0054] The terminal storage unit 11 and the usage management unit 111 are preferably non-volatile recording media, but can also be realized by volatile recording media.

[0055] There is no restriction on the process by which information is stored in the terminal storage unit 11 etc. For example, information may be stored in the terminal storage unit 11 etc. via a recording medium, information transmitted via a communication line etc. may be stored in the terminal storage unit 11 etc., or information input via an input device may be stored in the terminal storage unit 11 etc.

[0056] The terminal reception unit 12 can be realized by a device driver for an input means such as a touch panel or a keyboard, or control software for a menu screen.

[0057] The device processing unit 13, the terminal configuration unit 131, and the terminal update unit 132 can usually be realized by a processor, a memory, etc. The processing procedures of the device processing unit 13, etc. are usually realized by software, and the software is recorded on a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and the type does not matter.

[0058] The terminal transmitting unit 14 is usually realized by a wireless or wired communication means, but may also be realized by a broadcasting means.

[0059] The terminal output unit 15 may or may not include an output device such as a display, a speaker, etc. The terminal output unit 15 may be realized by driver software for an output device, or by a combination of driver software for an output device and the output device, etc.

[0060] Next, an example of the operation of the terminal device 1 will be described with reference to the flowchart of FIG.

[0061] (Step S201) The terminal reception unit 12 determines whether or not an instruction to output a payment screen has been received. If such an instruction to output has been received, the process proceeds to step S202, and if not, the process proceeds to step S208.

[0062] (Step S202) The terminal configuration unit 131 performs processing to configure a payment screen. An example of such screen configuration processing will be described with reference to the flowcharts of FIGS.

[0063] (Step S203) The terminal output unit 15 outputs the payment screen constructed in step S202.

[0064] (Step S204) The terminal reception unit 12 determines whether or not the selection of a payment method, etc., has been accepted from the user on the payment screen being output. If the selection of a payment method, etc., has been accepted, the process proceeds to step S205; if not, the process proceeds to step S204. The selection of a payment method, etc., includes the selection of a payment method and other information required for payment. The other information required for payment is, for example, the payment amount and the identifier of the product to be purchased.

[0065] (Step S205) The terminal processing unit 13 acquires the payment method identifier of the selected payment method.

[0066] (Step S206) The terminal processing unit 13 performs payment processing using the payment method identified by the payment method identifier acquired in step S205 and using the information acquired in step S204.

[0067] (Step S207) The terminal update unit 132 performs an update process for the usage information. Return to step S201. An example of the update process will be described with reference to the flowcharts of FIGS.

[0068] (Step S208) The terminal reception unit 12 determines whether or not other instructions have been received. If other instructions have been received, the process proceeds to step S209; if other instructions have not been received, the process returns to step S201. Note that other instructions are instructions other than the instruction to output the payment screen.

[0069] (Step S209) The device processing unit 13 performs processing according to other instructions. Return to step S201.

[0070] In the flowchart of FIG. 2, the process ends when the power is turned off or an interrupt occurs to end the process.

[0071] Next, a first example of the screen configuration process in step S202 will be described with reference to the flowchart in Fig. 3. The first example of the screen configuration process is a process performed when usage information common to one or more apps is stored in usage management unit 111.

[0072] (Step S301) The terminal configuration unit 131 acquires the usage status information from the usage management unit 111.

[0073] (Step S302) The terminal configuration unit 131 sorts the payment method identifiers in descending order based on key information (for example, score) from the information contained in the usage information acquired in step S301.

[0074] (Step S303) The terminal configuration unit 131 configures a payment method selection menu so that the payment method objects are arranged from top to bottom in the order of the payment method identifiers sorted in step S302. Note that the selection menu may be any user interface for selecting a payment method, and is not limited to a menu with two or more menu items, but may also be a user interface with checkboxes for selection, a user interface with buttons for selection, or the like.

[0075] (Step S304) The terminal configuration unit 131 configures a payment screen including the selection menu of payment methods configured in step S303, and returns to the upper processing.

[0076] In the flowchart of FIG. 3, the prominent aspect is to place the object corresponding to the payment method on top, but other aspects may also be used, such as making the background color prominent.

[0077] Next, a second example of the screen configuration process in step S302 will be described with reference to the flowchart in Fig. 4. The second example of the screen configuration process is a process performed when usage information is stored in usage management unit 111 for each application.

[0078] (Step S401) The terminal configuration unit 131 acquires the application identifier of the application including the payment screen. Note that the application here may be a web page, and the application identifier may be a site identifier.

[0079] (Step S402) The terminal configuration unit 131 acquires, from the usage management unit 111, usage status information paired with the application identifier acquired in step S401.

[0080] (Step S403) The terminal configuration unit 131 sorts the payment method identifiers based on key information (e.g., score) contained in the usage information acquired in step S402. Here, the terminal configuration unit 131 normally sorts the payment method identifiers in descending order, but may sort the payment method identifiers in ascending order depending on the key information.

[0081] (Step S404) The terminal configuration unit 131 configures the selection menu for payment methods so that the payment method objects are arranged from the top in the order of the payment method identifiers sorted in step S403.

[0082] (Step S405) The terminal configuration unit 131 configures a payment screen including the selection menu of payment methods configured in step S404, and returns to the upper processing.

[0083] In the flowchart of FIG. 4, the prominent aspect is to place the object corresponding to the payment method on top, but other aspects may also be used, such as making the background color prominent.

[0084] Next, a first example of the update process in step S207 will be described with reference to the flowchart in Fig. 5. The first example of the update process is a process performed when usage management unit 111 stores usage information that is common to one or more apps.

[0085] (Step S501) The terminal update unit 132 increments the usage count in the usage management unit 111 by 1, which is the usage count paired with the acquired payment method identifier.

[0086] (Step S502) The terminal update unit 132 acquires the amount of the current payment, "UA."

[0087] (Step S503) The terminal update unit 132 increases the total amount used that is paired with the acquired payment method identifier by the payment amount "UA".

[0088] (Step S504) The terminal update unit 132 uses the updated number of uses and the updated total amount of use to calculate the average amount of use according to "average amount of use = total amount of use / number of uses", and updates the average amount of use paired with the acquired payment method identifier to the calculated average amount of use.

[0089] (Step S505) The terminal update unit 132 acquires "UT", the time required for the procedure for this payment (for example, the usage time of the payment app (for example, the PayPay app)).

[0090] (Step S506) The terminal update unit 132 increases the total usage time paired with the acquired payment method identifier by the usage time "UT".

[0091] (Step S507) The terminal update unit 132 calculates a score using one or more of the updated number of uses, total use amount, average use amount, and total use time, and stores the score in pairs with the acquired payment method identifier. The process returns to the upper level process.

[0092] Next, a second example of the update process in step S207 will be described with reference to the flowchart in Fig. 6. The second example of the update process is a process performed when usage information is stored in usage management unit 111 for each application.

[0093] (Step S601) The terminal configuration unit 131 acquires the application identifier of the application including the payment screen. Note that the application here may be a web page, and the application identifier may be a site identifier.

[0094] (Step S602) Terminal update unit 132 increments by 1 the usage count in usage management unit 111, which is the usage count paired with the application identifier and the payment method identifier acquired in step S601.

[0095] (Step S603) The terminal update unit 132 acquires the amount of the current payment, "UA."

[0096] (Step S604) The terminal update unit 132 increases the total usage amount paired with the application identifier and the payment method identifier by the payment amount "UA."

[0097] (Step S605) The terminal update unit 132 uses the updated number of uses and the updated total amount of use to calculate the average amount of use according to "average amount of use = total amount of use / number of uses", and updates the average amount of use paired with the app identifier and payment method identifier to the calculated average amount of use.

[0098] (Step S606) The terminal update unit 132 acquires "UT", the time required for the procedure for this payment (for example, the usage time of the payment app (for example, the PayPay app)).

[0099] (Step S607) The terminal update unit 132 increases the total usage time paired with the application identifier and the payment method identifier by the usage time "UT".

[0100] (Step S608) The terminal update unit 132 calculates a score using one or more pieces of information from the updated number of uses, total use amount, average use amount, and total use time, and stores the score in pairs with the application identifier and payment method identifier. The process returns to the upper level process.

[0101] Specific examples of the operation of the terminal device 1 in this embodiment will be described below. Two specific examples will be described below. Specific example 1 is a case where one usage information management table exists in the terminal device 1. Specific example 2 is a case where a usage information management table exists for each application in the terminal device 1.

[0102] (Example 1) Currently, the usage management table of Figure 7 is stored in the usage management unit 111 of user A's terminal device 1. The usage management table is a table that manages the usage status of each of two or more payment methods. The usage management table manages usage information for each of two or more payment methods. The usage management table manages two or more records that have an "ID," "payment method identifier," "total amount used," "average amount used," "total usage time," and "score."

[0103] Here, the "score" is an integer between "0" and "100." The "score" is a value calculated using an increasing function with one or more of the following information as parameters: number of uses, total amount used, average amount used, and total time used. In other words, the "score" is information that indicates the level of activity in the use of a payment method. Here, the calculation formula is, for example, "score = a × number of uses + b × total amount used + c × average amount used + d × total time used" (a, b, c, and d are positive numbers).

[0104] In this situation, user A operates terminal device 1, launches app X of a product purchasing site, selects a product priced at 1,000 yen from app X, and inputs an instruction to output a payment screen to terminal device 1 to make payment.

[0105] Next, the terminal reception unit 12 of the terminal device 1 receives an instruction to output a payment screen. Next, the terminal configuration unit 131 performs the configuration process for the payment screen described using the flowchart in Fig. 3. Here, the terminal configuration unit 131 configures a selection menu (801 in Fig. 8) in which the payment method identifiers are sorted in descending order of score, and configures a payment screen having the selection menu (801), a payment button (802), etc.

[0106] In Figure 8, the selection menu is a user interface that allows a user to select one payment method using a check box. Also, in Figure 8, payment method identifiers are arranged from top to bottom in descending order of score. Also, in Figure 8, the terminal configuration unit 131 makes the background color of only the top-level payment method stand out. Furthermore, in Figure 8, the terminal configuration unit 131 sets the top-level payment method to a selected state (803).

[0107] Here, for example, if the payment method identifier "debit card" meets the non-display condition, it is preferable that the terminal configuration unit 131 configures a selection menu from FIG. 8 that excludes the option "debit card."

[0108] Next, the user selects the payment button (802) on the payment screen in FIG. 8. The terminal processing unit 13 of the terminal device 1 then acquires the payment method identifier "Pay2" of the selected payment method. The terminal processing unit 13 then launches the payment app identified by the payment method identifier "Pay2". The terminal processing unit 13 then performs payment processing for the amount "1,000 yen" using the payment app. The payment app identified by "Pay2" is stored in the terminal storage unit 11.

[0109] Next, the terminal update unit 132 performs the update process for the usage information described using the flowchart in Figure 5. That is, the terminal update unit 132 increments the number of usages paired with the payment method identifier "Pay2" by 1. The terminal update unit 132 also adds "1000 yen" to the total usage amount paired with the payment method identifier "Pay2". The terminal update unit 132 also updates the average usage amount paired with the payment method identifier "Pay2". Furthermore, the terminal update unit 132 acquires the amount of time that the payment app corresponding to the payment method identifier "Pay2" was running. Next, the terminal update unit 132 adds the running time to the total usage time. The terminal update unit 132 also updates the score corresponding to the payment method identifier "Pay2".

[0110] (Example 2) Specific example 2 is a case where a usage information management table for each application exists in the terminal device 1. As shown in FIG. 9, the usage management unit 111 of the terminal device 1 stores N usage information management tables associated with application identifiers. For example, a usage information management table 901 is stored associated with the application identifier "EC site 1." The application identifier may be an identifier (e.g., a URL) of a site (or a web page). In FIG. 9, the usage management unit 111 stores multiple usage information management tables (901, 902, . . . , 90N) associated with application identifiers.

[0111] In this situation, user A operates terminal device 1, launches the product purchasing site app "EC Site 1," selects a product priced at "1,000 yen" from EC Site 1, and inputs an instruction to output the payment screen into terminal device 1 to make payment.

[0112] Next, the terminal reception unit 12 of the terminal device 1 receives an instruction to output a payment screen. Next, the terminal configuration unit 131 performs the configuration process for the payment screen described using the flowchart in FIG. 4. That is, the terminal configuration unit 131 acquires the application identifier "EC site 1" of the running application. Next, the terminal configuration unit 131 acquires the usage information management table (901) paired with the application identifier "EC site 1" from the usage management unit 111. Next, the terminal configuration unit 131 configures a selection menu (801 in FIG. 8) in which the payment method identifiers are sorted in descending order of score, and configures a payment screen having the selection menu (801), a payment button (802), etc.

[0113] Next, the user selects the payment button (802). The terminal processing unit 13 of the terminal device 1 then acquires the payment method identifier "Pay2" of the selected payment method. The terminal processing unit 13 then launches the payment app identified by the payment method identifier "Pay2". The terminal processing unit 13 then performs payment processing for the amount "1000 yen" using the payment app.

[0114] Next, the terminal update unit 132 performs the update process for the usage information described using the flowchart in Fig. 6. That is, the terminal update unit 132 updates the number of uses, total usage amount, average usage amount, total usage time, and score that are paired with the application identifier "EC site 1" and the payment method identifier "Pay2."

[0115] As described above, according to this embodiment, by providing a payment screen according to the user's usage status of the payment method, it becomes easier for the user to select a payment method.

[0116] Furthermore, according to this embodiment, by providing a payment screen that corresponds to the user's usage of payment methods for each app, it becomes easier for the user to select a payment method in the app.

[0117] Furthermore, according to this embodiment, by providing a payment screen according to the user's usage status such as the time of use, frequency of use, or amount of use of the payment method, it becomes easier for the user to select a payment method.

[0118] The processing in this embodiment may be implemented by software. This software may be distributed by software download, etc. Furthermore, this software may be distributed by recording it on a recording medium such as a CD-ROM. This also applies to other embodiments in this specification. The software implementing the terminal device 1 in this embodiment is the following program. Specifically, this program causes a computer to function as: a terminal output unit that outputs a payment screen that accepts the selection of one of two or more payment methods; a terminal acceptance unit that accepts the selection of one of the two or more payment methods on the screen; a terminal processing unit that performs payment processing, which is processing for payment, using the selected one of the payment methods accepted by the terminal acceptance unit; and a terminal update unit that performs an update process to update usage information that identifies the usage status of the selected one of the payment methods accepted by the terminal acceptance unit, in association with the selected one of the payment methods accepted by the terminal acceptance unit. The payment screen is a screen that displays payment methods that are more frequently used, as identified by the usage information corresponding to each of the two or more payment methods, in a more prominent manner than payment methods that are less frequently used.

[0119] (Embodiment 2) The difference between this embodiment and embodiment 1 is that the terminal device appropriately changes the payment screen information received from the server according to the payment method usage information managed by the terminal device, and outputs a different payment screen according to the payment method usage information.

[0120] 10 is a conceptual diagram of an information system A in this embodiment. The information system A includes a server 2 and one or more terminal devices 3. The server 2 and one or more terminal devices 3 can communicate with each other via a network such as the Internet.

[0121] The server 2 is, for example, a web server, a so-called cloud server, or an ASP server, but the type is not important.

[0122] The terminal device 3 is a terminal used by a user. The terminal device 1 is, for example, a smartphone, a tablet terminal, or a personal computer, but the type does not matter.

[0123] 11 is a block diagram of an information system A according to the present embodiment. The server 2 constituting the information system A includes a storage unit 21, a receiving unit 22, a processing unit 23, and a transmitting unit 24. The storage unit 21 includes a screen management unit 211. The receiving unit 22 includes an instruction receiving unit 221.

[0124] The terminal device 3 includes a terminal storage unit 31, a terminal reception unit 32, a terminal processing unit 33, a terminal transmission unit 34, a terminal reception unit 35, and a terminal output unit 36. The terminal storage unit 31 includes a usage management unit 111. The terminal processing unit 33 includes a terminal configuration unit 331 and a terminal update unit 132.

[0125] Various types of information are stored in the storage unit 21 that constitutes the server 2. The various types of information are, for example, various types of screen information, which will be described later. Screen information is information for configuring a screen. Screen information is configured, for example, in HTML, XML, a program, or the like, but the means for realizing it is not important.

[0126] One or more pieces of screen information are stored in the screen management unit 211. The one or more pieces of screen information include payment screen information.

[0127] The receiving unit 22 receives various instructions and information from the terminal device 3.

[0128] The instruction receiving unit 221 receives various instructions from the terminal device 3. The various instructions are, for example, an instruction to transmit a specific screen. The instruction to transmit a specific screen is, for example, an instruction to transmit a payment screen.

[0129] The processing unit 23 performs various processes. For example, in response to receiving an instruction to send a specific screen, the processing unit 23 acquires screen information for configuring the screen from the screen management unit 211. For example, in response to receiving an instruction to send a payment screen, the processing unit 23 acquires payment screen information from the screen management unit 211. The processing unit 23 may also perform payment processing.

[0130] The transmission unit 24 transmits the screen information acquired by the processing unit 23 to the terminal device 3. The transmission unit 24 transmits the payment screen information acquired by the processing unit 23 to the terminal device 3, for example.

[0131] Various types of information are stored in the terminal storage unit 31 constituting the terminal device 3. The various types of information include, for example, usage information and various types of software.

[0132] The terminal reception unit 32 receives various instructions and information, such as an instruction to launch a specific app or an operation on an app or web page. For example, the terminal reception unit 32 receives the selection of one of two or more payment methods on a payment screen.

[0133] The terminal processing unit 33 performs a payment process, which is a process for payment, using the selected one of the payment methods accepted by the terminal accepting unit 32.

[0134] The terminal configuration unit 331 configures an output screen from the screen information received by the terminal receiving unit 35. For example, the terminal configuration unit 331 references the usage management unit 111 and configures, from the payment screen information received by the terminal receiving unit 35, a payment screen that displays payment methods that are actively used as specified by the usage information in a more prominent manner than payment methods that are not actively used.

[0135] The terminal configuration unit 331 refers to the usage management unit 111, changes the received payment screen information, and configures a payment screen from the changed payment screen information.

[0136] If the received payment screen information includes a selection menu definition having object definitions corresponding to two or more payment methods, the terminal configuration unit 331 changes the order of definition of the object definitions in the selection menu definition, changes the attribute values ​​(e.g., background color, font) of the object definitions, or deletes object definitions that meet the hide conditions.

[0137] The terminal configuration unit 331 configures a payment screen using usage information corresponding to the site or app being used.

[0138] The terminal transmitting unit 34 transmits various instructions and information, such as instructions to transmit various screens.

[0139] The terminal receiving unit 35 receives various types of screen information from the server 2. For example, the terminal receiving unit 35 receives from the server 2 payment screen information that configures a payment screen.

[0140] The terminal output unit 36 ​​outputs various screens configured by the terminal configuration unit 331. For example, the terminal output unit 36 ​​outputs a payment screen that accepts the selection of one of two or more payment methods.

[0141] The storage unit 21, the screen management unit 211, and the terminal storage unit 31 are preferably non-volatile recording media, but may also be realized as volatile recording media.

[0142] There is no restriction on the process by which information is stored in the storage unit 21 etc. For example, information may be stored in the storage unit 21 etc. via a recording medium, information transmitted via a communication line etc. may be stored in the storage unit 21 etc., or information input via an input device may be stored in the storage unit 21 etc.

[0143] The receiving unit 22, the instruction receiving unit 221, and the terminal receiving unit 35 are usually realized by wireless or wired communication means, but may also be realized by means for receiving broadcasts.

[0144] The processing unit 23, the device processing unit 33, and the terminal configuration unit 331 can usually be realized by a processor, a memory, etc. The processing procedures of the processing unit 23, etc. are usually realized by software, and the software is recorded on a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and the type does not matter.

[0145] The transmitting unit 24 and the terminal transmitting unit 34 are usually realized by wireless or wired communication means, but may also be realized by broadcasting means.

[0146] The terminal reception unit 32 can be realized by a device driver for an input means such as a touch panel or a keyboard, or control software for a menu screen.

[0147] The terminal output unit 36 ​​may or may not include an output device such as a display, a speaker, etc. The terminal output unit 36 ​​may be realized by driver software for an output device, or by a combination of driver software for an output device and the output device, etc.

[0148] Next, an example of the operation of the server 2 will be described. The instruction receiving unit 221 of the server 2 receives various instructions. The instruction receiving unit 221 receives, for example, an instruction to send a payment screen. The processing unit 23 performs processing according to the received instruction. For example, in response to receiving the instruction to send a payment screen, the processing unit 23 acquires payment screen information from the screen management unit 211. The transmission unit 24 transmits the screen information acquired by the processing unit 23 to the terminal device 3. For example, the transmission unit 24 transmits the payment screen information acquired by the processing unit 23 to the terminal device 3.

[0149] Next, an example of the operation of the terminal device 3 will be described with reference to the flowchart of Fig. 12. In the flowchart of Fig. 12, the description of the same steps as in the flowchart of Fig. 2 will be omitted.

[0150] (Step S1201) The terminal processing unit 33 generates a transmission instruction for a payment screen. The terminal transmitting unit 34 transmits the transmission instruction to the server 2.

[0151] (Step S1202) The terminal receiving unit 35 determines whether or not the payment screen information has been received from the server 2. If the payment screen information has been received, the process proceeds to step S1203, and if not, the process returns to step S1202.

[0152] (Step S1203) The terminal configuration unit 331 configures a payment screen to be output using the received payment screen information. The process proceeds to step S203. An example of such screen configuration processing will be described with reference to the flowcharts in FIGS. 13 and 14.

[0153] In the flowchart of FIG. 12, the process ends when the power is turned off or an interrupt occurs to end the process.

[0154] Next, a first example of the screen configuration processing in step S1203 will be described using the flowchart in Fig. 13. In the flowchart in Fig. 13, explanations of steps that are the same as those in the flowchart in Fig. 3 will be omitted. Note that the first example of the screen configuration processing is processing when usage information common to one or more apps is stored in usage management unit 111.

[0155] (Step S1301) The terminal configuration unit 331 acquires a selection menu definition of payment methods from the received payment screen information.

[0156] The terminal configuration unit 331 acquires the selection menu definition from the payment screen information, for example, using a specific tag as a clue. If the payment screen information is written in HTML, the specific tag is, for example, a tag that specifies the definition of a table or a tag that specifies the definition of a bulleted list. The tag that specifies the definition of a table is, for example, and The tag that identifies the definition of a bullet point is, for example, and ,or and is.

[0157] The terminal configuration unit 331, for example, and Between and Between or and The terminal configuration unit 331 obtains a selection menu definition, which is an HTML description between and Between and Between or and and obtain a selection menu definition, which is an HTML description between the above and the above, and which is a description including a payment method identifier (for example, the string "credit card").

[0158] (Step S1302) The terminal configuration unit 331 assigns 1 to a counter i.

[0159] (Step S1303) The terminal configuration unit 331 determines whether the i-th payment method identifier exists among the payment method identifiers sorted in step S302. If the i-th payment method identifier exists, the process proceeds to step S1304; if not, the process proceeds to step S1307.

[0160] (Step S1304) The terminal configuration unit 331 determines whether the object definition including the i-th payment method identifier is included in the selection menu definition acquired in step S1301. If the object definition is included, the process proceeds to step S1305; if not, the process proceeds to step S1306.

[0161] (Step S1305) The terminal configuration unit 331 acquires the object definition including the i-th payment method identifier from the selection menu definition, and adds the object definition to the buffer that stores the final selection menu definition.

[0162] (Step S1306) The terminal configuration unit 331 increments the counter i by 1. The process returns to step S1303.

[0163] (Step S1307) The terminal configuration unit 331 acquires one or more object definitions that were not added in step S1305 from the object definitions in the selection menu definition acquired in step S1301. The terminal configuration unit 331 changes the attribute values ​​(e.g., background color, font, size) of the one or more object definitions to attribute values ​​that will not stand out when displayed, and adds the one or more object definitions to a buffer that stores the final selection menu definition. Note that if the terminal configuration unit 331 does not acquire any object definitions here, the process proceeds to step S1308.

[0164] Here, the terminal configuration unit 331, for example, sets the background color of the object definition to gray. Also, the terminal configuration unit 331 may exclude the one or more object definitions from being included in the final selection menu definition.

[0165] In other words, the terminal configuration unit 331 may determine that one or more object definitions among the object definitions in the selection menu definition acquired in step S1301 that have not been added in step S1305 satisfy the display conditions and may not include them in the final selection menu definition.

[0166] (Step S1308) The terminal configuration unit 331 overwrites (changes) the two or more object definitions stored in the buffer (not shown) over the two or more object definitions included in the selection menu definition of the received payment screen information.

[0167] (Step S1309) The terminal configuration unit 331 configures a payment screen using the payment screen information changed in step S1308, and returns to the upper processing.

[0168] Next, a second example of the screen configuration process in step S1203 will be described with reference to the flowchart in Fig. 14. The flowchart in Fig. 14 shows the process when the usage information is stored for each site, which is the same as the flowchart in Fig. 13.

[0169] (Step S1401) The terminal configuration unit 331 acquires the site identifier of the site that includes the received payment screen information.

[0170] (Step S1402) The terminal configuration unit 331 acquires from the usage management unit 111 the usage status information paired with the site identifier acquired in step S1401.

[0171] (Step S1403) The terminal configuration unit 331 sorts the payment method identifiers in descending order based on key information (for example, score) from the information contained in the usage information acquired in step S1402. Go to step S1301.

[0172] Below, specific examples of the operation of the information system A in this embodiment will be described. Two specific examples will be described below. Specific example 1 is a case where one usage information management table exists in the terminal device 3. Specific example 2 is a case where the terminal device 3 has a usage information management table for each site.

[0173] (Example 1) Now, the usage management unit 111 of the terminal device 1 of the user A stores the usage status management table of FIG.

[0174] In this situation, user A operates terminal device 1, accesses product purchasing site X, selects a product priced at 1,000 yen from site X, and inputs an instruction to output a payment screen into terminal device 1 to make payment.

[0175] Next, the terminal reception unit 12 of the terminal device 1 receives an instruction to output a payment screen. Next, the terminal processing unit 33 generates an instruction to send the payment screen. Next, the terminal transmission unit 34 sends the transmission instruction to the server 2.

[0176] Next, the server 2 receives the transmission instruction and transmits to the terminal device 1 payment screen information corresponding to the transmission instruction.

[0177] Next, the terminal receiving unit 35 receives the payment screen information from the server 2. Next, the terminal configuration unit 131 performs the configuration process of the payment screen described using the flowchart in Fig. 13. Here, the terminal configuration unit 131 configures a selection menu (801 in Fig. 8) in which the payment method identifiers are sorted in descending order of the scores in the usage status management table, and configures a payment screen having the selection menu (801), a payment button (802), etc.

[0178] Next, the user selects the payment button (802). The terminal processing unit 13 of the terminal device 1 then acquires the payment method identifier "Pay2" of the selected payment method. The terminal processing unit 13 then launches the payment app identified by the payment method identifier "Pay2". The terminal processing unit 13 then performs payment processing for the amount "1000 yen" using the payment app.

[0179] Next, the terminal update unit 132 performs the update process of the usage information described using the flowchart in Fig. 4. This process has been described in the first embodiment.

[0180] (Example 2) Specific example 2 is a case where a usage information management table for each site exists in the terminal device 1. The usage management unit 111 of the terminal device 1 stores N usage information management tables in association with application identifiers. For example, a usage information management table 901 is stored in association with the site identifier "EC site 1."

[0181] In this situation, user A operates terminal device 1, accesses EC site 1 for purchasing goods, selects a product priced at 1,000 yen from EC site 1, and inputs an instruction to output a payment screen into terminal device 1 to make payment.

[0182] Next, the terminal reception unit 12 of the terminal device 1 receives an instruction to output a payment screen. Next, the terminal processing unit 33 generates an instruction to send the payment screen. Next, the terminal transmission unit 34 sends the transmission instruction to the server 2.

[0183] Next, the server 2 receives the transmission instruction and transmits to the terminal device 1 payment screen information corresponding to the transmission instruction.

[0184] Next, the terminal receiving unit 35 receives the payment screen information from the server 2. Next, the terminal configuration unit 131 acquires the site identifier "EC site 1". Next, the terminal configuration unit 131 acquires the usage information management table (901) paired with the site identifier "EC site 1". Next, the terminal configuration unit 131 uses the usage information management table (901) to perform the payment screen configuration process described using the flowchart in FIG. 14. Here, the terminal configuration unit 131 configures a selection menu (801 in FIG. 8) in which the payment method identifiers are sorted in descending order of score, and configures a payment screen having the selection menu (801), a payment button (802), etc.

[0185] Next, the user selects the payment button (802). The terminal processing unit 13 of the terminal device 1 then acquires the payment method identifier "Pay2" of the selected payment method. The terminal processing unit 13 then launches the payment app identified by the payment method identifier "Pay2". The terminal processing unit 13 then performs payment processing for the amount "1000 yen" using the payment app.

[0186] Next, the terminal update unit 132 performs the update process of the usage information described using the flowchart in FIG.

[0187] As described above, according to this embodiment, by providing a payment screen according to the user's usage status of the payment method, it becomes easier for the user to select a payment method.

[0188] Furthermore, according to this embodiment, by providing a payment screen that corresponds to the user's usage of payment methods for each site, it becomes easier for the user to select a payment method on the site.

[0189] Furthermore, according to this embodiment, by providing a payment screen according to the user's usage status such as the usage time, frequency of usage, or amount of usage of the payment method, it becomes easier for the user to select a payment method.

[0190] The software for realizing information system A in this embodiment is the following program: That is, this program causes a computer to function as a terminal output unit that outputs a payment screen that accepts the selection of one of two or more payment methods, a terminal acceptance unit that accepts the selection of one of the two or more payment methods on the screen, a terminal processing unit that performs payment processing, which is processing for payment, using the selected one payment method accepted by the terminal acceptance unit, and a terminal update unit that performs update processing to update usage information that identifies the usage status of the selected one payment method, in association with the selected one payment method accepted by the terminal acceptance unit, wherein the payment screen is a screen that displays payment methods that are more frequently used, as identified by the usage information corresponding to each of the two or more payment methods, in a manner that makes them stand out compared to payment methods that are less frequently used.

[0191] (Embodiment 3) The present embodiment differs from the first and second embodiments in that the server provides payment screen information customized for each user according to the usage status of the user's payment method.

[0192] 15 is a conceptual diagram of an information system B in this embodiment. The information system B includes a server 4 and one or more terminal devices 5. The server 4 and one or more terminal devices 5 can communicate with each other via a network such as the Internet.

[0193] The server 4 is, for example, a web server, a so-called cloud server, or an ASP server, but the type is not important.

[0194] The terminal device 5 is a terminal used by a user. The terminal device 5 may be, for example, a smartphone, a tablet terminal, or a personal computer, but the type is not important.

[0195] 16 is a block diagram of an information system B according to this embodiment. The server 4 constituting the information system B includes a storage unit 41, a receiving unit 42, a processing unit 43, and a transmitting unit 44. The storage unit 41 includes a screen management unit 211 and a usage management unit 412. The receiving unit 42 includes an instruction receiving unit 221. The processing unit 43 includes a configuration unit 431 and an update unit 432. The transmitting unit 44 includes a screen transmission unit 441.

[0196] The terminal device 5 includes a terminal storage unit 51, a terminal reception unit 52, a terminal processing unit 53, a terminal transmission unit 54, a terminal reception unit 55, and a terminal output unit 56.

[0197] Various types of information are stored in the storage unit 41 that constitutes the server 4. The various types of information include, for example, various types of screen information and usage information for each user.

[0198] The usage management unit 412 stores usage status information in association with one or more user identifiers.

[0199] The usage management unit 412 may store, for example, usage status information for each site in association with one or more user identifiers.

[0200] The receiving unit 42 receives various instructions and information from the terminal device 5. The various instructions and information are, for example, an instruction to send a specific screen and operation information. An instruction to send a specific screen is, for example, an instruction to send a payment screen. The operation information is an operation performed by the user on a web page. The operation information includes, for example, the button identifier of the pressed button and information entered in a field.

[0201] The processing unit 43 performs various types of processing. The various types of processing are, for example, processing performed by the configuration unit 431 or the update unit 432. The processing unit 43 performs, for example, payment processing.

[0202] The composition unit 431 acquires payment screen information from the screen management unit 211. The composition unit 431 also references the usage management unit 412 and acquires usage status information corresponding to the instruction to send the payment screen from the usage management unit 412. The composition unit 431 acquires from the payment screen information for constructing a payment screen that displays payment methods with active usage identified by the acquired usage information in a more prominent manner compared to payment methods with inactive usage.

[0203] The update unit 432 performs an update process to update the usage information that corresponds to the user identifier that is paired with the user operation and that identifies the usage status of one payment method selected by the user, based on the user operation.

[0204] The transmitting unit 44 transmits various types of information, such as various types of screen information.

[0205] The screen transmission unit 441 transmits various types of screen information to the terminal device 5. The various types of screen information are, for example, payment screen information.

[0206] Various types of information are stored in the terminal storage unit 51 constituting the terminal device 5. The various types of information include, for example, a user identifier, operation information, and various types of software.

[0207] Terminal reception unit 52 receives various instructions and information. Terminal reception unit 52 receives various operations for the displayed web page. Terminal reception unit 52 receives the selection of one of two or more payment methods on the screen.

[0208] The input means for various operations may be any means such as a touch panel, keyboard, mouse, or menu screen.

[0209] The terminal processing unit 53 performs a payment process, which is a process for payment, using one of the payment methods corresponding to the selection accepted by the terminal accepting unit 52. Note that the payment process here is, for example, sending information required for payment to the server 4.

[0210] The terminal transmitting unit 54 transmits various instructions and information to the server 4. The various instructions and information are, for example, instructions to transmit various screens.

[0211] The terminal receiving unit 55 receives various types of information from the server 4. The various types of information are, for example, various types of screen information. The various types of screen information are, for example, payment screen information.

[0212] The terminal output unit 56 outputs various information and screens. For example, the terminal output unit 56 outputs a payment screen that accepts the selection of one of two or more payment methods.

[0213] The storage unit 41 and the usage management unit 412 are preferably non-volatile recording media, but can also be realized by volatile recording media.

[0214] There is no restriction on the process by which information is stored in the storage unit 41 etc. For example, information may be stored in the storage unit 41 etc. via a recording medium, information transmitted via a communication line etc. may be stored in the storage unit 41 etc., or information input via an input device may be stored in the storage unit 41 etc.

[0215] The receiving unit 42 and the terminal receiving unit 55 are usually realized by wireless or wired communication means, but may also be realized by means for receiving broadcasts.

[0216] The processing unit 43, configuration unit 431, update unit 432, and device processing unit 53 can usually be realized by a processor, memory, etc. The processing procedures of the processing unit 43, etc. are usually realized by software, and the software is recorded on a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and the type does not matter.

[0217] The transmitting unit 44, the screen transmitting unit 441, and the terminal transmitting unit 54 are usually realized by wireless or wired communication means, but may also be realized by broadcasting means.

[0218] The terminal reception unit 52 can be realized by a device driver for an input means such as a touch panel or a keyboard, or control software for a menu screen.

[0219] The terminal output unit 56 may or may not be considered to include an output device such as a display, a speaker, etc. The terminal output unit 56 may be realized by driver software for an output device, or by a combination of driver software for an output device and the output device, etc.

[0220] Next, an example of the operation of the server 4 will be described with reference to the flowchart of FIG.

[0221] (Step S1701) The instruction receiving unit 221 determines whether or not an instruction to send a payment screen has been received from the terminal device 5. If the instruction to send has been received, the process proceeds to step S1702, and if not, the process proceeds to step S1705.

[0222] (Step S1702) The configuration unit 431 acquires payment screen information from the screen management unit 211.

[0223] (Step S1703) The configuration unit 431 configures the payment screen information to be sent using the payment screen information acquired in step S1702. An example of such screen configuration processing will be described with reference to the flowcharts in Figures 18 and 19. The payment screen information to be sent is customized according to the user's payment method usage status.

[0224] (Step S1704) The screen transmission unit 441 transmits the payment screen information constructed in step S1703 to the terminal device 5. The process returns to step S1701.

[0225] (Step S1705) The instruction receiving unit 221 determines whether or not a payment instruction has been received. If a payment instruction has been received, the process proceeds to step S1706, and if not, the process proceeds to step S1708.

[0226] (Step S1706) The processing unit 43 performs a payment process in accordance with the received payment instruction. Note that such a payment process is a known technique.

[0227] (Step S1707) The update unit 432 updates the usage information in accordance with the payment process. Return to step S1701. An example of such update process will be described with reference to the flowcharts of FIGS.

[0228] (Step S1708) The receiving unit 42 determines whether or not other instructions or information have been received. If other instructions or information have been received, the process proceeds to step S1709, and if not, the process returns to step S1701.

[0229] (Step S1709) The processing unit 43 performs processing in accordance with other instructions, etc. The process returns to step S1701.

[0230] In the flowchart of FIG. 17, the process ends when the power is turned off or an interrupt occurs to end the process.

[0231] Next, a first example of the screen configuration process in step S1703 will be described using the flowchart in Fig. 18. In the flowchart in Fig. 18, the description of the same steps as in the flowchart in Fig. 3 or Fig. 13 will be omitted.

[0232] (Step S1801) The configuration unit 431 acquires a user identifier corresponding to the received transmission instruction.

[0233] (Step S1802) The configuration unit 431 acquires the usage status information paired with the user identifier from the usage management unit 412. The process proceeds to step S302.

[0234] Next, a second example of the screen configuration process in step S1703 will be described with reference to the flowchart in Fig. 19. In the flowchart in Fig. 19, the description of the same steps as in the flowchart in Fig. 14 or Fig. 18 will be omitted.

[0235] (Step S1901) The configuration unit 431 acquires the usage status information corresponding to the user identifier and the site identifier from the usage management unit 412. The process proceeds to step S1403.

[0236] Next, a first example of the update process in step S1707 will be described with reference to the flowchart in FIG.

[0237] (Step S2001) The update unit 432 acquires the user identifier paired with the received payment instruction.

[0238] (Step S2002) The update unit 432 acquires the payment identifier included in the received payment instruction.

[0239] (Step S2003) The update unit 432 increments by one the number of times of use included in the use information paired with the user identifier, the payment identifier, etc.

[0240] (Step S2004) The update unit 432 acquires the current payment amount "UA" included in the received payment instruction.

[0241] (Step S2005) The update unit 432 increases the total amount used that is paired with the acquired user identifier and payment method identifier by the payment amount "UA".

[0242] (Step S2006) The update unit 432 uses the updated number of uses and the updated total amount of use to calculate the average amount of use by the formula "average amount of use = total amount of use / number of uses", and updates the average amount of use paired with the acquired user identifier and payment method identifier to the calculated average amount of use.

[0243] (Step S2007) The update unit 432 acquires "UT", the time required for the current payment procedure (for example, the time from sending payment screen information to receiving a payment instruction).

[0244] (Step S2008) The update unit 432 increases the total usage time paired with the acquired payment method identifier by the usage time "UT".

[0245] (Step S2009) The update unit 432 calculates a score using one or more of the updated number of uses, total use amount, average use amount, and total use time, and stores the score as a pair with the acquired user identifier and payment method identifier. The process returns to the upper level process.

[0246] Next, a second example of the update process in step S1707 will be described using the flowchart in Fig. 21. In the flowchart in Fig. 21, the description of the same steps as in the flowchart in Fig. 20 will be omitted.

[0247] (Step S2101) The update unit 432 acquires the site identifier corresponding to the payment instruction. Thereafter, the update unit 432 updates the usage information corresponding to the user identifier, site identifier, and payment method identifier. The usage information update process is the same as the flowchart in FIG. 20.

[0248] Next, an example of the operation of the terminal device 5 will be described using the flowchart in Fig. 22. The flowchart in Fig. 22 is composed of steps included in the flowchart in Fig. 2 or Fig. 12.

[0249] A specific example of the operation of the information system B in this embodiment will be described below.

[0250] 23, the usage management unit 412 of the server 4 currently stores N usage information management tables associated with user identifiers. For example, usage information management table 2301 is stored associated with user identifier "user U1." The usage management unit 412 also stores usage information management tables 2302, ..., 230N associated with other different user identifiers.

[0251] In this situation, assume that user U1 operates terminal device 1, accesses product purchasing site "EC site 1," selects a product priced at "1,000 yen" from EC site 1, and inputs an instruction to output a payment screen to terminal device 5 in order to make payment. Terminal device 5 then accepts the instruction to output the payment screen on "EC site 1," and transmits an instruction to send the payment screen to server 4.

[0252] Next, the instruction receiving unit 221 of the server 4 receives an instruction to send a payment screen from the terminal device 5. Next, the configuration unit 431 acquires payment screen information for "EC site 1" from the screen management unit 211. Next, the configuration unit 431 configures payment screen information to be sent using the acquired payment screen information through the operation described using the flowchart in FIG. 18. Then, it is assumed that the configuration unit 431 acquires payment screen information for configuring the screen shown in FIG. 8.

[0253] Next, the screen transmission unit 441 transmits the payment screen information to the terminal device 5.

[0254] Next, the terminal device 5 receives the payment screen information and outputs the payment screen of FIG.

[0255] Next, the user selects the payment button (802) on the payment screen in FIG. 8. The terminal processing unit 53 of the terminal device 5 then acquires the payment method identifier "Pay2" of the selected payment method. The terminal processing unit 53 then constructs a payment instruction having the payment method identifier "Pay2" and the amount "1,000 yen." The terminal transmission unit 54 then transmits the payment instruction to the server 4. The construction and transmission of this payment instruction constitutes payment processing in the terminal device 5.

[0256] Next, the instruction receiving unit 221 of the server 4 receives the payment instruction. Next, the processing unit 43 performs payment processing according to the received payment instruction.

[0257] Next, in response to the payment process, the update unit 432 performs the update process of the usage information described using the flowchart in Fig. 20. This update process updates the number of uses, total usage amount, average usage amount, total usage time, and score paired with the user identifier "User U1" and the payment method identifier "Pay2."

[0258] As described above, according to this embodiment, by providing a payment screen according to the user's usage status of the payment method, it becomes easier for the user to select a payment method.

[0259] Furthermore, according to this embodiment, by providing a payment screen that corresponds to the user's usage of payment methods for each site, it becomes easier for the user to select a payment method for each site.

[0260] Furthermore, according to this embodiment, by providing a payment screen according to the user's usage status such as the usage time, frequency of usage, or amount of usage of the payment method, it becomes easier for the user to select a payment method.

[0261] The software that realizes server 4 in this embodiment is the following program. In other words, this program causes a computer that can access a usage management unit in which usage status information, which is usage information corresponding to each of two or more payment methods, is stored for each user identifier, and a screen management unit in which payment screen information that configures a payment screen for accepting selection of one of two or more payment methods, to function as: an instruction receiving unit that receives a transmission instruction, which is an instruction to transmit a payment screen and is associated with a user identifier, from a terminal device; a configuration unit that, in response to receiving the transmission instruction, obtains usage status information corresponding to the user identifier that is associated with the transmission instruction from the usage management unit, and uses the usage status information and the payment screen information to obtain payment screen information to be transmitted to the terminal device; and a screen transmitting unit that transmits the payment screen information obtained by the screen configuration unit to the terminal device.

[0262] The above-described embodiments can also be realized by computer hardware and a computer program executed thereon. FIG. 24 is a block diagram of a computer system 300.

[0263] 24, computer system 300 includes a computer 301 including a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304. In addition to a CD-ROM drive 3012, computer 301 also includes an MPU 3013, a bus 3014 connected to CD-ROM drive 3012 and the like, a ROM 3015 for storing programs such as a boot-up program, a RAM 3016 connected to MPU 3013 for temporarily storing instructions for application programs and providing temporary storage space, and a hard disk 3017 for storing application programs, system programs, and data. Although not shown here, computer 301 may further include a network card for providing connection to a LAN.

[0264] A program that causes computer system 300 to execute the functions of terminal device 1, server 2, etc. of the above-described embodiments may be stored on CD-ROM 3101, inserted into CD-ROM drive 3012, and then transferred to hard disk 3017. Alternatively, the program may be transmitted to computer 301 via a network (not shown) and stored on hard disk 3017. The program is loaded into RAM 3016 when executed. The program may also be loaded directly from CD-ROM 3101 or the network.

[0265] The program does not necessarily include an operating system (OS) or a third-party program that causes the computer 301 to execute the functions of the terminal device 1 of the above-described embodiment. The program only needs to include instructions that call appropriate functions (modules) in a controlled manner to achieve the desired results. How the computer system 300 operates is well known, and a detailed description thereof will be omitted.

[0266] In addition, in the above program, the steps of transmitting information and receiving information do not include processing performed by hardware, such as processing performed by a modem or interface card in the transmission step (processing that can only be performed by hardware).

[0267] The computer that executes the program may be a single computer or a plurality of computers, that is, it may perform centralized processing or distributed processing.

[0268] Furthermore, in each of the above embodiments, it goes without saying that two or more communication means present in one device may be physically realized by one medium.

[0269] Furthermore, in each of the above embodiments, each process may be realized by centralized processing in a single device, or may be realized by distributed processing in a plurality of devices.

[0270] The present invention is not limited to the above-described embodiment, and various modifications are possible, and it goes without saying that these modifications are also included within the scope of the present invention. [Industrial Applicability]

[0271] As described above, the terminal device 1 of the present invention has the effect of making it easier for users to select a payment method by providing a payment screen that corresponds to the user's usage status of the payment method, and is useful as a smartphone or the like that has convenient applications stored on it. [Explanation of symbols]

[0272] A, B Information Systems 1, 3, 5 terminal equipment 2, 4 servers 11, 31, 51 Terminal storage section 12, 32, 52 Terminal reception area 13, 33, 53 Terminal processing section 14, 34, 54 Terminal transmitter 15, 36, 56 Terminal output section 35, 55 Terminal receiving section 21, 41 storage area 22, 42 Receiver 23, 43 Processing section 24, 44 Transmitter 111, 412 Usage Management Department 131, 331 Terminal component 132 End of update section 132 Terminal Update Unit 211 Screen management department 221 Instruction receiving unit 431 Components 432 Update Department 441 Screen Transmission Unit

Claims

1. a terminal output unit that outputs a payment screen that accepts selection of one of two or more payment methods; a terminal reception unit that receives, on the payment screen, a selection of one of the two or more payment methods; a terminal processing unit that performs a payment process, which is a process for payment, using the selected one of the payment methods accepted by the terminal accepting unit; a terminal update unit that performs an update process to update usage information that identifies the usage status of the selected one payment method in association with the selected one payment method accepted by the terminal acceptance unit, The payment screen is A terminal device having a screen that displays payment methods with active usage identified by usage information corresponding to each of the two or more payment methods in a more prominent manner compared to payment methods with less active usage.

2. The terminal device of claim 1 further comprises a terminal configuration unit that references a usage management unit in which usage information corresponding to each of the two or more payment methods is stored, and configures the payment screen in such a way that payment methods with active usage as identified by the usage information are displayed in a more prominent manner compared to payment methods with inactive usage.

3. a terminal receiving unit that receives payment screen information that configures the payment screen from a server; The terminal device according to claim 1 further comprises a terminal configuration unit that references a usage management unit in which usage information corresponding to each of the two or more payment methods is stored, and configures the payment screen from the payment screen information received by the terminal receiving unit, in which payment methods with active usage as specified by the usage information are displayed in a more prominent manner compared to payment methods with inactive usage.

4. The usage management unit includes: Usage information corresponding to each of the two or more payment methods is stored for each of the two or more apps, The terminal configuration unit 4. The terminal device according to claim 2, wherein the payment screen is configured using usage information corresponding to the application being used.

5. a terminal receiving unit that receives the payment screen information from a server that acquires payment screen information constituting the payment screen by referring to a usage management unit that stores usage information corresponding to each of the two or more payment methods; The terminal output unit The terminal device according to claim 1 , wherein the terminal receiving unit outputs a payment screen based on the payment screen information received.

6. The usage information includes one or more of the following information: the number of times the payment method is used; the total usage amount, which is the cumulative amount of payments made using the payment method; the total usage time, which is the cumulative amount of operation time related to the payment method; the average usage amount, which is the average amount of a single payment made using the payment method; and the maximum usage amount of the payment method. The payment screen is A terminal device as claimed in any one of claims 1 to 5, wherein the screen displays the payment method in a more prominent manner the more frequently the payment method is used, or the larger the total amount used for the payment method, the longer the total time the payment method is used, the smaller the difference between the current payment amount and the average amount used, or the larger the maximum amount used.

7. a screen management unit that stores payment screen information for a payment screen that accepts selection of one of two or more payment methods; an instruction receiving unit that receives, from the terminal device, a transmission instruction that is an instruction to transmit a payment screen and that is an instruction associated with a user identifier; a component that, in response to receiving the transmission instruction, acquires usage status information, which is two or more pieces of usage information corresponding to the user identifier associated with the transmission instruction, from a usage management unit that stores usage information corresponding to two or more payment methods for each user identifier, and acquires payment screen information to be transmitted to a terminal device using the usage status information and the payment screen information; a screen transmission unit that transmits the payment screen information acquired by the configuration unit to the terminal device.

8. An information processing method implemented by a usage management unit that stores usage status information, which is usage information corresponding to each of two or more payment methods, for each user identifier, a screen management unit that stores payment screen information that configures a payment screen that accepts selection of one of two or more payment methods, an instruction receiving unit, a configuration unit, and a screen sending unit, an instruction receiving step in which the instruction receiving unit receives, from the terminal device, a transmission instruction that is an instruction to transmit a payment screen and that is associated with a user identifier; a configuration step in which the configuration unit, in response to receiving the transmission instruction, acquires usage status information corresponding to the user identifier associated with the transmission instruction from the usage management unit, and acquires payment screen information to be transmitted to a terminal device using the usage status information and the payment screen information; and a screen transmission step in which the screen transmission unit transmits the payment screen information acquired by the configuration unit to the terminal device.

9. Computer, a terminal output unit that outputs a payment screen that accepts selection of one of two or more payment methods; a terminal reception unit that receives, on the payment screen, a selection of one of the two or more payment methods; a terminal processing unit that performs a payment process, which is a process for payment, using the selected one of the payment methods accepted by the terminal accepting unit; a program that functions as a terminal update unit that performs an update process for updating usage information that identifies the usage status of the one selected payment method, in association with the one selected payment method accepted by the terminal acceptance unit, The payment screen is A program that displays a screen that displays payment methods with active usage identified by usage information corresponding to each of the two or more payment methods in a more prominent manner compared to payment methods with inactive usage.

10. A computer that can access a usage management unit that stores usage status information, which is usage information corresponding to each of two or more payment methods, for each user identifier, and a screen management unit that stores payment screen information that configures a payment screen that accepts selection of one of the two or more payment methods, an instruction receiving unit that receives, from the terminal device, a transmission instruction that is an instruction to transmit a payment screen and that is an instruction associated with a user identifier; a component that, in response to receiving the transmission instruction, acquires from the usage management unit usage status information corresponding to the user identifier associated with the transmission instruction, and acquires payment screen information to be transmitted to a terminal device using the usage status information and the payment screen information; A program for causing the configuration unit to function as a screen transmission unit that transmits the payment screen information acquired by the configuration unit to the terminal device.

Images