Payment system, display control method, and program

Abstract

To improve user convenience. [Solution] The status acquisition unit (101) of the display control system (1) acquires the status of a user's card that is compatible with the payment service. Based on the status, the display control unit (102) displays content related to the card on the relevant screen related to the payment service.

Description

Technical Field

[0001] The present disclosure relates to a settlement system, a display control method, and a program.

Background Art

[0002] Conventionally, with the spread of electronic settlement (cashless settlement), various settlement services are known. For example, in Patent Document 1, when a user applies for a specific credit card on a settlement application provided by an operator who operates a settlement service, personal identification information used by the user for personal identification in another service is acquired, and an information processing apparatus that provides a credit card application screen to the user with the personal identification information input is described.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, with the technology of Patent Document 1, although it is possible to display content for a user to apply for a specific credit card on a settlement application, it is not possible to display flexible content according to the status of the credit card. This also applies to settlement services corresponding to cards other than credit cards such as Patent Document 1. For this reason, the conventional technology has not been able to sufficiently improve the convenience for users.

[0005] One object of the present disclosure is to improve the convenience for users.

Means for Solving the Problems

[0006] The payment system relating to this disclosure is a card that supports a payment service and includes a status acquisition unit that acquires the status of a user's card and a display control unit that displays content related to the card on a related screen related to the payment service based on the status. [Effects of the Invention]

[0007] This disclosure can improve user convenience. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of the hardware configuration of a payment system. [Figure 2] This figure shows an example of a screen displayed on a user's terminal. [Figure 3] This figure shows an example of a screen displayed on a user's terminal. [Figure 4] This figure shows an example of a screen displayed on a user's terminal. [Figure 5] This figure shows an example of the functions implemented in the payment system of the first embodiment. [Figure 6] This is a diagram showing an example of a payment database. [Figure 7] This figure shows an example of a card database. [Figure 8] This figure shows an example of the processing performed in the payment system of the first embodiment. [Figure 9] This figure shows an example of the processing performed in the payment system of the first embodiment. [Figure 10] This figure shows an example of a screen displayed on a user's terminal. [Figure 11] This figure shows an example of the functions implemented in the payment system of the second embodiment. [Figure 12] This figure shows an example of the processing performed in the payment system of the second embodiment. [Figure 13] This figure shows an example of a function realized by a modified version of the first embodiment. [Figure 14]It is a diagram showing an example of a screen displayed on a user terminal in Modification Example 1-1. [Figure 15] It is a diagram showing an example of a screen displayed on a user terminal in Modification Example 1-4. [Figure 16] It is a diagram showing an example of a screen displayed on a user terminal in Modification Example 1-7. [Figure 17] It is a diagram showing an example of a screen displayed on a user terminal in Modification Example 1-9. [Figure 18] It is a diagram showing an example of a screen displayed on a user terminal in Modification Example 1-10. [Figure 19] It is a diagram showing an example of a screen displayed on a user terminal in Modification Example 1-11. [Figure 20] It is a diagram showing an example of a screen displayed on a user terminal in Modification Example 1-12. [Figure 21] It is a diagram showing an example of a function realized in a modification of the second embodiment. [Figure 22] It is a diagram showing an example of a screen displayed on a user terminal in Modification Example 2-6. [Figure 23] It is a diagram showing an example of a screen displayed on a user terminal in Modification Example 2-11. [Mode for Carrying Out the Invention]

[0009] [1. First Embodiment] An example of the first embodiment of the settlement system, display control method, and program according to the present disclosure will be described.

[0010] [1-1. Hardware Configuration of the Settlement System] Figure 1 shows an example of the hardware configuration of a payment system. For example, payment system 1 includes a payment server 10, a card server 20, and a user terminal 30. Each of the payment server 10, card server 20, and user terminal 30 is connected to a network N such as the Internet or a LAN. In Figure 1, one of each of the payment server 10, card server 20, and user terminal 30 is shown, but there may be multiple units of at least one of the payment server 10, card server 20, and user terminal 30.

[0011] The payment server 10 is a server computer for payment services. The payment service is a service that provides electronic payment (cashless payment) to users. For example, the payment server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The storage unit 12 includes at least one of volatile memory such as RAM and non-volatile memory such as flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

[0012] The card server 20 is a server computer for card services. Card services are services in which users' cards are used. A card may be a physical object (e.g., a so-called card plate) or an electronic card that does not have a physical form (e.g., a so-called virtual card). In the first embodiment, a credit card is described as an example of a card. The card may be any card. The card is not limited to a credit card. For example, the card may be a debit card, an electronic money card, a point card, a transportation IC card, a cash card, a My Number card, or another card. For example, the card server 20 includes a control unit 21, a storage unit 22, and a communication unit 23. The hardware configuration of the control unit 21, the storage unit 22, and the communication unit 23 may be the same as that of the control unit 11, the storage unit 12, and the communication unit 13, respectively.

[0013] The user terminal 30 is the user's computer. For example, the user terminal 30 is a smartphone, tablet, personal computer, or wearable device. The user terminal 30 includes a control unit 31, a storage unit 32, a communication unit 33, an operation unit 34, and a display unit 35. The hardware configurations of the control unit 31, storage unit 32, and communication unit 33 may be the same as those of the control unit 11, storage unit 12, and communication unit 13, respectively. The operation unit 34 is an input device such as a touch panel or mouse. The display unit 35 is a display such as a liquid crystal or organic EL.

[0014] Furthermore, programs stored in memory units 12, 22, and 32 may be supplied to the payment server 10, card server 20, or user terminal 30 via the network N. Also, at least one of a reader unit (e.g., a memory card slot) for reading computer-readable information storage media and an input / output unit (e.g., a USB port) for inputting and outputting data to and from external devices may be included in the payment server 10, card server 20, or user terminal 30. For example, a program stored on the information storage media may be supplied to the payment server 10, card server 20, or user terminal 30 via at least one of the reader unit and the input / output unit.

[0015] Furthermore, payment system 1 may include at least one computer. The computers included in payment system 1 are not limited to the example in Figure 1. For example, payment system 1 may include only payment server 10 and user terminal 30. In this case, card server 20 is located outside payment system 1. Payment system 1 may include only payment server 10. In this case, card server 20 and user terminal 30 are located outside payment system 1. For example, payment system 1 may include payment server 10 and other computers not shown in Figure 1.

[0016] [1-2. Overview of the First Embodiment] In the first embodiment, the user uses the payment service by operating the user terminal 30. The user can use any payment method with the payment service. A payment method is a means that the user uses for payment. For example, a payment method may be the various cards mentioned above, electronic money, points, crypto assets, debit cards, wallets, bank accounts, or other means. Codes such as barcodes or two-dimensional codes are also considered payment methods as they are means for payment. A payment method can also be used for making payments, so it can also be called a payment method. A payment method can also be used for charging the balance of electronic money, etc., so it can also be called a charging method.

[0017] In the first embodiment, we take the example of a case where a user makes a payment using a payment application installed on the user terminal 30. The payment application is an application provided by a business operator that operates a payment service. Once the user installs the payment application on the user terminal 30 and registers as a member of the payment service, they can use the payment service. When the user completes member registration and launches the payment application, the user terminal 30 displays the top screen of the payment application on the display unit 35. The top screen is the first screen displayed after the payment application is launched. The top screen is sometimes called the first view.

[0018] Figures 2 to 4 show examples of screens displayed on the user terminal 30. For example, when the payment app is launched, the user terminal 30 displays the top screen SC1 on the display unit 35, which includes a code C10 generated based on a code ID that can temporarily identify the user, as shown in the upper left of Figure 2. The code C10 is at least one of a barcode and a two-dimensional code. When the code C10 is read by the terminal of a merchant (e.g., a store) participating in the payment service, the payment is executed based on the code ID obtained from the code C10.

[0019] In the example in Figure 2, an online electronic money service called "AAA Cash" is set as the payment source, so a payment is executed based on the electronic money that has been pre-charged. The payment source is the payment method used for the payment. The payment source can be any payment method. For example, a user may be able to register multiple payment methods as candidates for payment sources with the payment service. In this case, the user designates one of the multiple payment methods as the payment source. The payment based on the payment source specified by the user may be a publicly known process.

[0020] Furthermore, the payment methods available to users through the payment service are not limited to the method of having the merchant's terminal read code C10. The payment method may be any method. For example, the payment method may be a type in which the user terminal 30 reads a code displayed on the merchant's terminal, a type in which the user terminal 30 reads a code posted at the merchant's facility, a type that is completed solely by operations on the user terminal 30, a type that utilizes the IC chip of the user terminal 30, online payment (for example, account payment using the user's account, or ID payment using the user's ID), carrier payment which is the payment method of the carrier used by the user terminal 30, or other types.

[0021] For example, a user can change the payment source by selecting button B11. When a user selects button B11, the user terminal 30 displays the payment source setting screen SC2 on the display unit 35, as shown in the upper right of Figure 2, for the user to set the payment source. The payment source setting screen SC2 can also be described as a screen for the user to change the payment source. In the example in the upper right of Figure 2, the top panel P20 shows the current payment source, the electronic money "AAA Cash". Below panel P20 are panels P21 to P23. Panel P21 will be described later.

[0022] For example, panel P22 shows the "ZZZ Card" that the user has registered with the payment service. By selecting panel P22, the user can change the payment source to the "ZZZ Card". The user can also register a new card with the payment service by selecting panel P23. If the user has registered other payment methods with the payment service, the user can also change the payment source to another payment method from the payment source settings screen SC2. If the payment service supports payment methods other than cards, the user may also register other payment methods with the payment service from the payment source settings screen SC2.

[0023] In the first embodiment, the payment service accepts applications for cards from specific card companies. For example, if a user does not possess a card that can be applied for through the payment service, they can apply for such a card from the payment source setting screen SC2. In the example in the upper right of Figure 2, the user can apply for the "AAA card," issued by the payment service provider or a card company affiliated with the payment service provider, through the payment service. Hereafter, where simply referred to as "card," it generally means a card that can be applied for through the payment service. Note that the aforementioned card "ZZZ card" cannot be applied for through the payment service.

[0024] In the upper right example of Figure 2, a panel P21 for accepting card applications is placed below panel P20, which shows the payment source being set. For example, when a user selects panel P21, the user terminal 30 displays an application screen SC3 on the display unit 35, which accepts input of the necessary information for applying for a card, as shown in the lower left of Figure 2. In the first embodiment, the application screen SC3 is shown as an example of being displayed as a web view of the payment application. The application screen SC3 may be the screen of the payment application itself, or it may be a screen on a browser launched by selecting panel P21.

[0025] The application process for the card after the application screen SC3 is displayed may be the same as the publicly known process. For example, the user enters necessary information such as the card brand, employment information, and bank account information for direct debit. The user may also upload identity verification documents required for card screening. Once the user completes the card application, the user terminal 30 displays a completion screen SC4 on the display unit 35, indicating that the card application has been completed, as shown in the lower right of Figure 2. Subsequently, the card company screens the card. The screening process for the card may be the same as the publicly known process.

[0026] For example, card applications may be accepted on screens other than the payment source setting screen SC2. Below, we will explain an example of the process when a card application is made from another screen, referring to Figure 3. The top screen SC1 in the upper left of Figure 3 is the same as the top screen SC1 in the upper left of Figure 2. For example, a user can change the charge source by selecting button B12 on the top screen SC1. The charge source is the payment method used for charging. The charge source can also be described as the payment method that provides the funds for the charge, or a payment method used indirectly for payment. Charging is the process of increasing the balance of a payment method.

[0027] In the first embodiment, we take the case where electronic money is charged as an example, but the payment method to be charged can be any payment method that has the concept of charging, and is not limited to electronic money. For example, charging may be performed on a payment method such as an account. The payment method that can be used as the charging source can also be any payment method. For example, when the user selects button B12, the user terminal 30 displays a charging source setting screen SC5 on the display unit 35 for the user to set the charging source, as shown in the upper right of Figure 3.

[0028] In the upper right example of Figure 3, the top panel P50 shows the current bank account from which the funds are being charged. Below panel P50 are panels P51 to P53. Panel P51 will be described later. For example, a user can change the charging source to the "ZZZ Card" by selecting panel P52. A user can also register a new card with the payment service by selecting panel P53. If a user has registered other payment methods with the payment service, they can also change the charging source to another payment method from the charging source settings screen SC5.

[0029] In the first embodiment, the user can also apply for a card from the charge source setting screen SC5. For example, when the user selects panel P51, the user terminal 30 displays an application screen SC3 on the display unit 35, similar to the one in the lower left of Figure 2, as shown in the lower left of Figure 3. The procedure for applying for a card is as described above. When the user completes the application, the user terminal 30 displays a completion screen SC4 on the display unit 35, similar to the one in the lower right of Figure 2, as shown in the lower right of Figure 3.

[0030] For example, once the card application submitted by the user via the payment source setting screen SC2 or the charge source setting screen SC5 has been approved, the card issuer issues the user's card. The card issuer then ships the card to the address specified by the user. The payment service may allow the user to use the card before they receive it. Alternatively, possession authentication may be performed after the user has received the card, such as by reading the card. The timing at which the user can use the card with the payment service may be at any time after the card approval process is complete.

[0031] From here on, with reference to Figure 4, an example of the process after the card "AAA Card," which was applied for through the payment service, becomes available for use with the payment service will be explained. For example, when the user selects button B11 on the top screen SC1 in the upper left of Figure 4, the user terminal 30 displays panel P24, which indicates the card "AAA Card," on the payment source setting screen SC2, as shown in the upper right of Figure 4. Since the user already possesses the card "AAA Card," panel P21 for applying for the card "AAA Card" is not displayed on the payment source setting screen SC2. The user can change the payment source to the card "AAA Card" by selecting panel P24.

[0032] For example, if the user selects button B12 on the top screen SC1 in the upper left of Figure 4, the user terminal 30 will display panel P54, which indicates the card "AAA Card," on the charge source setting screen SC5, as shown in the lower right of Figure 4. Since the user already possesses the card "AAA Card," panel P51 for applying for the card "AAA Card" is not displayed on the charge source setting screen SC5. The user can change the charge source to the card "AAA Card" by selecting panel P54.

[0033] As described above, if the user does not possess the "AAA card," payment system 1 displays panels P21 and P51 for applying for the card on the payment source setting screen SC2 or the charge source setting screen SC5. If the user does possess the "AAA card," payment system 1 displays panels P24 and P54 for setting up the card on the payment source setting screen SC2 or the charge source setting screen SC5. By using these displays appropriately, payment system 1 aims to enhance user convenience. The details of payment system 1 will be explained below.

[0034] [1-3. Functions realized in the payment system of the first embodiment] Figure 5 shows an example of the functions realized in the payment system 1 of the first embodiment. The various parts realized in the payment system 1 can be configured by combining them into a single device or by further distributing them among multiple devices.

[0035] [1-3-1. Functions implemented by the payment server] For example, the payment server 10 includes a data storage unit 100, a status acquisition unit 101, and a display control unit 102. The data storage unit 100 is implemented by a storage unit 12. The status acquisition unit 101 and the display control unit 102 are each implemented by a control unit 11.

[0036] [Data Storage Unit] The data storage unit 100 stores the data necessary for the payment service. For example, the data storage unit 100 stores the payment database DB1.

[0037] Figure 6 shows an example of a payment database DB1. The payment database DB1 is a database that stores various information about users who use the payment service. For example, the payment database DB1 stores user ID, password, code ID, payment method information, payment source information, charge source information, status, application screen information, and application details information. Other information may also be stored in the payment database DB1. For example, the payment database DB1 may store usage history information related to the usage history of the payment service.

[0038] A User ID is an example of user identification information that can identify a user. A separate login account may exist in addition to the User ID. Users may be able to freely change their login account. The login account is also an example of user identification information. A password is information that is verified during login. A Code ID is also an example of user identification information, as it is an ID that can identify a user in the payment service. The Code ID is updated each time Code C10 is displayed. User identification information may include other information besides the User ID, login account, and Code ID.

[0039] Payment method information is information that identifies the payment methods available to the user in the payment service. The payment method indicated by the payment method information can be said to be a payment method that is a candidate for at least one of the payment source and / or charge source. For example, payment method information may include information such as credit card numbers, electronic money numbers, bank account information, or point card numbers. If a card corresponds to a payment method, the payment method information may also include information that identifies the card issuer that issued the card. Payment source information is information that identifies the payment method set as the payment source. Charge source information is information that identifies the payment method set as the charge source. If a card corresponds to a payment method, at least one of the payment source information and / or charge source information may include information that identifies the card issuer that issued the card.

[0040] In the first embodiment, once the application review of a card that can be applied for through the payment service is completed, the card information of the card is transmitted from the card server 20 to the payment server 10. The payment server 10 registers the card information of the card as payment method information. Therefore, once the card review is completed, the card is automatically registered with the payment service without the user having to perform any operation to register the card. However, instead of the card being automatically registered with the payment service, the user may register the card manually, or the card may be registered with the payment service after authentication such as scan authentication has been performed after the card has been delivered to the user.

[0041] The status is the status of the card. In the first embodiment, the status of a card that can be applied for from the payment service is stored in the payment database DB1 as an example, but the status of a card that cannot be applied for from the payment service (in the example of Figures 2 to 4, the card "ZZZ card") may also be stored in the payment database DB1. For example, the status may indicate whether the user possesses a card, whether the user has applied for a card, whether the user has started the application process for a card, whether the user has interrupted the application process for a card, whether the card is under review, whether the card review is complete, whether the card has been issued, whether the card has arrived in the user's possession, whether the card is set as a payment source, whether the card is set as a charge source, or a combination of two or more of these. The status may be in any format, for example, it may be information that represents letters, numbers, symbols, or a combination thereof. The status is changed as appropriate based on information from the card server 20, the user terminal 30, or other computers.

[0042] Application screen information refers to information about the application screen on which the user applied for the card. In the first embodiment, the payment source setting screen SC2 and the charge source setting screen SC5 correspond to the application screens. For example, the application screen information will be either a value indicating that the user applied for the card from the payment source setting screen SC2, or a value indicating that the user applied for the card from the charge source setting screen SC5. As in the second embodiment described later, the application screen may be a screen other than the payment source setting screen SC2 and the charge source setting screen SC5.

[0043] For example, the payment server 10 identifies which application screen it is based on the information received from the user terminal 30 and stores the application screen information in the payment database DB1. If the user makes an application from the payment source setting screen SC2, the user terminal 30 sends information to the payment server 10 indicating that the application screen is the payment source setting screen SC2. The payment server 10 stores the application screen information indicating that the application screen is the payment source setting screen SC2 in the payment database DB1. If the user makes an application from the charge source setting screen SC5, the user terminal 30 sends information to the payment server 10 indicating that the application screen is the charge source setting screen SC5. The payment server 10 stores the application screen information indicating that the application screen is the charge source setting screen SC5 in the payment database DB1.

[0044] Application details information is information that shows what the user entered when applying for a card. For example, application details information may show the card brand, the user's employer, the bank account for direct debit, or other information. Application details information may be any information necessary for applying for a card. The payment server 10 stores the application details information received from the user terminal 30 in the payment database DB1.

[0045] The data stored in the data storage unit 100 is not limited to the examples above. The data storage unit 100 only needs to store the data necessary for the payment service. For example, the data storage unit 100 may store data from various screens displayed on the payment application. The data storage unit 100 also stores programs and data necessary for payment, charging, and other processing.

[0046] [Status acquisition section] The status acquisition unit 101 acquires the status of a user's card that is compatible with the payment service. A card compatible with the payment service is a card that can be used with the payment service. In other words, a card that can be handled by the payment service, or a card that can be registered with the payment service, is a card compatible with the payment service. In the first embodiment, the status acquisition unit 101 acquires a status indicating whether or not the user possesses a card. The status indicates either a value indicating that the user possesses a card, or a value indicating that the user does not possess a card. As mentioned above, the status may be any status other than whether or not the user possesses a card.

[0047] In the first embodiment, since the status is stored in the settlement database DB1, the status acquisition unit 101 acquires the status from the settlement database DB1. The status may also be stored in a database other than the settlement database DB1. In this case, the status acquisition unit 101 acquires the status from the other database. The status may also be stored in a computer other than the settlement server 10 or in an external information storage medium. In this case, the status acquisition unit 101 acquires the status from the other computer or in an external information storage medium.

[0048] The status acquisition unit 101 can acquire the status at any time. For example, the status acquisition unit 101 may acquire the status of a user stored in the card database DB2 of the card server 20 before the user logs in to the payment service, and store the status in the payment database DB1 in association with the user's user ID. In the first embodiment, the case where the user ID is common to both the payment service and the card service is given as an example, but the user ID for the payment service and the user ID for the card service may be different. The relationship between the user ID for the payment service and the user ID for the card service is managed by the payment server 10, the card server 20, or another computer. At least one of the payment server 10 and the card server 20 identifies which user ID belongs to which user based on this relationship.

[0049] For example, the status acquisition unit 101 may acquire the status of a user stored in the settlement database DB1 when it receives a request from a user terminal 30 to display the payment source setting screen SC2 or the charge source setting screen SC5. The status acquisition unit 101 may also acquire the status from the card server 20 when it receives such a display request. The status acquisition unit 101 can acquire the status stored in the settlement database DB1 at any time. For example, the status acquisition unit 101 may acquire the status when the user logs into the settlement service, when the top screen SC1 is displayed, when the payment source setting screen SC2 is displayed, when the charge source setting screen SC5 is displayed, or at any other time.

[0050] [Display Control Unit] The display control unit 102 controls the display of various screens in the payment service. For example, the display control unit 102 displays card-related content on related screens related to the payment service based on the status acquired by the status acquisition unit 101. The display control unit 102 also displays card-related content on a user's related screen based on the status associated with a user's user ID. Related screens are screens that display content according to the status. In the first embodiment, the case where the payment source setting screen SC2 and the charge source setting screen SC5 each correspond to related screens is given as an example. Therefore, the sections describing the payment source setting screen SC2 and the charge source setting screen SC5 can be read as referring to related screens.

[0051] The related screen may be any screen displayed in the payment service. The related screen is not limited to the payment source setting screen SC2 and the charge source setting screen SC5. For example, the related screen may be the top screen SC1, the application screen SC3, the completion screen SC4, a screen for settings other than the payment source and charge source, a screen for displaying a point card code, a screen for sending electronic money, a screen for executing a charge, a screen indicating that a payment (e.g., payment or charge) has been completed, a screen displayed immediately after the completion of registration for using the payment service, a campaign screen, or any other screen. Data indicating which screen is the related screen may be stored in the data storage unit 100.

[0052] Content is a component of a related screen. Content can also be defined as an object displayed on a related screen. For example, content may be a user interface component (e.g., a panel, button, slider, or checkbox), an icon, banner, window, popup, modal, other image, text, symbol, shape, or other component. Content may or may not include links that lead to other screens based on user selection.

[0053] Card-related content refers to content related to cards that can be applied for through the payment service. For example, the content may include the card's name, brand, a string of text prompting the user to apply, benefits, campaign details, logo, icon, or other information. In the first embodiment, panels P21 and P51 for applying for a card are given as an example where they correspond to card-related content. Therefore, the sections describing panels P21 and P51 can be interpreted as card-related content.

[0054] In the first embodiment, we take as an example the case where content related to card applications corresponds to content related to cards, but content related to cards is not limited to content related to card applications. Content related to cards may also be content that shows things other than card applications. For example, content related to cards may be content that does not accept card applications but shows the features of the card, content that includes a link to the card provider's website, content for setting the card as the payment source, content for setting the card as the charging source, or other content.

[0055] In the first embodiment, the display control unit 102 displays content related to card application on the relevant screen related to setting the payment method used by the user in the payment service, based on a status indicating whether or not the user possesses a card. The content related to card application is content for accepting card applications. In the first embodiment, the case in which panels P21 and P51 correspond to the content related to card application is given as an example. Therefore, the sections describing panels P21 and P51 can be read as referring to the content related to card application.

[0056] For example, if the status indicates that the user does not possess a card, the display control unit 102 displays panel P21 for card application on the payment source setting screen SC2. The display control unit 102 generates display data for the payment source setting screen SC2, including panel P21, and transmits this display data to the user terminal 30, thereby displaying panel P21 on the payment source setting screen SC2. The display control unit 102 may also display panel P21 on the payment source setting screen SC2 by transmitting only a portion of the data from the payment source setting screen SC2 to the user terminal 30.

[0057] For example, if the status indicates that the user does not possess a card, the display control unit 102 displays panel P51 for card application on the charge source setting screen SC5. The display control unit 102 generates display data for the charge source setting screen SC5, including panel P51, and transmits this display data to the user terminal 30, thereby displaying panel P51 on the charge source setting screen SC5. The display control unit 102 may also display panel P51 on the charge source setting screen SC5 by transmitting only a portion of the data from the charge source setting screen SC5 to the user terminal 30.

[0058] For example, the display control unit 102 displays panel P24 for card settings on the payment source setting screen SC2 when the status indicates that the user possesses a card. The display control unit 102 generates display data for the payment source setting screen SC2, including panel P24, and transmits this display data to the user terminal 30, thereby displaying panel P24 on the payment source setting screen SC2. The display control unit 102 may also display panel P24 on the payment source setting screen SC2 by transmitting only a portion of the data from the payment source setting screen SC2 to the user terminal 30.

[0059] For example, if the status indicates that the user does not possess a card, the display control unit 102 causes panel P54 for card settings to be displayed on the charge source setting screen SC5. The display control unit 102 generates display data for the charge source setting screen SC5, including panel P54, and transmits this display data to the user terminal 30, thereby causing panel P54 to be displayed on the charge source setting screen SC5. The display control unit 102 may also cause panel P54 to be displayed on the charge source setting screen SC5 by transmitting only a portion of the data from the charge source setting screen SC5 to the user terminal 30.

[0060] [1-3-2. Functions implemented by the card server] For example, the card server 20 includes a data storage unit 200 and a card management unit 201. The data storage unit 200 is implemented by a storage unit 22. The card management unit 201 is implemented by a control unit 21.

[0061] [Data Storage Unit] The data storage unit 200 stores the data necessary for the card service. For example, the data storage unit 200 stores the card database DB2.

[0062] Figure 7 shows an example of the card database DB2. The card database DB2 is a database that stores various information about users who use card services. For example, the payment database DB1 stores user ID, password, status, application details, and card information. Other information may be stored in the card database DB2. For example, the card database DB2 may store usage history information related to the card usage history.

[0063] The user ID and password differ from those for the payment service in that they are used for the user to log in to the card service, but are otherwise the same. The status and application details are the same as those for the payment service. Card information refers to information about cards that have been approved and issued. For example, card information includes the card number, expiration date, cardholder information, and direct debit account information. If an application is made for a card other than a credit card, the card information should reflect the information appropriate for that card.

[0064] The data storage unit 200 only needs to store data corresponding to the card service. The data storage unit 200 may also store data other than the card database DB2. For example, the data storage unit 200 may store data that allows the card service and payment service to cooperate with each other.

[0065] [Card Management Department] The card management unit 201 manages the status of cards in the card service. For example, if a user applies for a card, the card management unit 201 updates the user's status to indicate that the application has been received. Card applications may be made via the payment service or directly to the card service. When a user's card application has been reviewed, the card management unit 201 updates the user's status to indicate that the application has been reviewed. Once the card review is complete, the card operator's terminal sends a list of reviewed cards to the card server 20. Based on this list, the card management unit 201 identifies the reviewed cards.

[0066] For example, when a user's card is shipped, the card management unit 201 updates the user's status to indicate that the card has been shipped. Once a card is shipped, the card operator's terminal sends a list of shipped cards to the card server 20. The card management unit 201 identifies the shipped cards based on this list. When a user receives a card, the card management unit 201 updates the user's status to indicate that the card has been received. The card management unit 201 can receive delivery status data from the delivery company's system responsible for card delivery and detect card receipt based on this data.

[0067] [1-3-3. Functions implemented on the user terminal] For example, the user terminal 30 includes a data storage unit 300, an operation reception unit 301, and a display control unit 302. The data storage unit 300 is implemented by a storage unit 32. The operation reception unit 301 and the display control unit 302 are implemented by a control unit 31.

[0068] [Data Storage Unit] The data storage unit 300 stores the data necessary for the user to use the payment service. For example, the data storage unit 300 stores the payment application. If the user uses the payment service from a browser instead of the payment application, the data storage unit 300 stores the browser.

[0069] [Operation Reception Section] The operation reception unit 301 receives various user operations. For example, the operation reception unit 301 receives operations on the payment application. The operation reception unit 301 transmits data indicating the user's operations to the payment server 10.

[0070] [Display Control Unit] The display control unit 302 displays various screens on the display unit 35. For example, the display control unit 302 displays the top screen SC1, the payment source setting screen SC2, the application screen SC3, the completion screen SC4, and the charge source setting screen SC5 on the display unit 35. The display control unit 302 communicates with the payment server 10, the card server 20, or other computers to receive the data necessary for displaying these screens and displays these screens on the display unit 35.

[0071] [1-4. Processing performed in the payment system of the first embodiment] Figures 8 and 9 show examples of processes performed in the payment system 1 of the first embodiment. The processes shown in Figures 8 and 9 are executed by the control units 11, 21, and 31 executing programs stored in the storage units 12, 22, and 32, respectively.

[0072] As shown in Figure 8, when a user launches the payment application, the user terminal 30 performs a login process with the payment server 10 to allow the user to log in to the payment service (S100). If the login is successful, the user terminal 30 performs a process with the payment server 10 to display the top screen SC1 (S101). The user terminal 30 identifies the user's operation (S102). In S102, the user may select button B11, button B12, or perform another operation. If the user performs another operation in S102 (S102: other operation), the process corresponding to the other operation is executed, and this process ends.

[0073] In S102, if the user selects button B11 (S102:B11), the user terminal 30 sends a request to the payment server 10 to display the payment source setting screen SC2 (S103). The payment server 10 receives the request from the user terminal 30 to display the payment source setting screen SC2 (S104). The payment server 10 performs processing with the card server 20 to obtain the user's status (S105). In S105, the payment server 10 sends the user ID of the logged-in user to the card server 20. The card server 20 obtains the status associated with the user ID from the card database DB2. The card server 20 sends the status to the payment server 10. The payment server 10 stores the status in the payment database DB1 in association with the user ID of the logged-in user.

[0074] The payment server 10 determines whether the user possesses a card based on the user's status (S106). If it is determined in S106 that the user does not possess a card (S106:N), the payment server 10 performs a process to display the payment source setting screen SC2, which includes the panel P21 for applying for a card, with the user terminal 30 (S107). The payment server 10 performs a process for applying for a card with the user terminal 30 (S108), and this process ends. In S108, if necessary, communication also occurs between the payment server 10 and at least one of the user terminal 30 and the card server 20.

[0075] In S106, if it is determined that the user possesses a card (S106:Y), the settlement server 10 performs a process to display the payment source setting screen SC2, which includes panel P24 for setting the card as the payment source, with the user terminal 30 (S109). The settlement server 10 performs a process to set the payment source with the user terminal 30 (S110), and this process ends. In S110, the settlement server 10 updates the payment source information to indicate the payment method selected by the user.

[0076] In S102, if the user selects button B12 (S102:B12), the process moves to Figure 9, and the user terminal 30 sends a request to the payment server 10 to display the charge source setting screen SC5 (S111). The payment server 10 receives the request from the user terminal 30 to display the charge source setting screen SC5 (S112). The payment server 10 performs processing with the card server 20 to obtain the user's status (S113). The processing in S113 is the same as the processing in S105.

[0077] The payment server 10 determines whether the user possesses a card based on the user's status (S114). If it is determined in S114 that the user does not possess a card (S114:N), the payment server 10 performs a process to display the charge source setting screen SC5, which includes the panel P21 for applying for a card, with the user terminal 30 (S115). The payment server 10 performs a process for applying for a card with the user terminal 30 (S116), and this process ends. In S116, if necessary, communication also occurs between the payment server 10 and at least one of the user terminal 30 and the card server 20.

[0078] In S114, if it is determined that the user possesses a card (S114:Y), the payment server 10 performs a process to display the charge source setting screen SC5, which includes a panel P24 that allows the user to set the card as the charge source, to the user terminal 30 (S117). The payment server 10 then performs a process to set the charge source to the user terminal 30 (S118), and this process ends. In S118, the payment server 10 updates the charge source information to indicate the payment method selected by the user.

[0079] [1-5. Summary of the First Embodiment] The payment system 1 of the first embodiment is a card compatible with the payment service and acquires the status of the user's card. Based on the status, the payment system 1 displays card-related content on the relevant screen related to the payment service. This allows the payment system 1 to display flexible content on the relevant screen according to the status, thereby improving user convenience. For example, displaying the same content to all users may not sufficiently increase the appeal to users, but displaying content according to the status can increase the appeal to users.

[0080] Furthermore, payment system 1 acquires a status indicating whether or not the user possesses a card. Based on this status, payment system 1 displays content related to card application on relevant screens related to setting the payment method used by the user in the payment service (for example, the payment source setting screen SC2 or the charge source setting screen SC5). This allows payment system 1 to provide a pathway for card application according to the user's status, thereby improving user convenience. Moreover, the relevant screens related to setting the payment method are screens that users pay particular attention to, and if it is possible to apply for a card that offers benefits in the payment service on these screens, users may become interested in applying for a card. Therefore, payment system 1 can promote card applications, thereby improving convenience for payment service providers and card providers.

[0081] [2. Second Embodiment] Next, a second embodiment, which is an example of another embodiment of the payment system, display control method, and program, will be described. In the second embodiment, the same configuration as in the first embodiment will not be described. For example, the hardware configuration of the payment system 1 may be the same as in the first embodiment.

[0082] [2-1. Overview of the Second Embodiment] In the second embodiment, similar to the first embodiment, we take the example of a case where a user can apply for a card from either the payment source setting screen SC2 or the charge source setting screen SC5. In this case, it may be desirable to control the screen transitions after the card application is approved based on which screen the user applied for the card from. For example, a user who applies for a card from the payment source setting screen SC2 may want to use that card as a payment source. A user who applies for a card from the charge source setting screen SC5 may want to use that card as a charge source.

[0083] Figure 10 shows an example of a screen displayed on the user terminal 30. For example, when the card application is approved, the user terminal 30 uses the payment application's notification function to display a notification screen SC6 on the display unit 35, which includes a notification indicating that the card application has been approved, as shown in the upper left of Figure 10. The notification screen SC6 may display various notifications to the user. The notification screen SC6 may be accessible from any screen, such as the top screen SC1. In the example in the upper left of Figure 10, the notification screen SC6 includes a button B60 for transitioning to the next screen. For example, button B60 includes a link to the next screen.

[0084] In the second embodiment, when the user selects button B60, the user terminal 30 transitions to the same screen as the application screen where the user applied for the card. For example, if the user applied for the card from the payment source setting screen SC2 (where the payment source setting screen SC2 is the application screen), as shown in the upper right of Figure 10, when the user selects a notification on the notification screen SC6, the user terminal 30 transitions from the notification screen SC6 to the payment source setting screen SC2. From the payment source setting screen SC2, the user can set the card whose application has been approved as the payment source.

[0085] For example, if a user applies for a card from the charge source setting screen SC5 (where SC5 is the application screen), as shown in the lower right of Figure 10, when the user selects a notification on the notification screen SC6, the user terminal 30 transitions from the notification screen SC6 to the charge source setting screen SC5. From the charge source setting screen SC5, the user can set the approved card as the charge source. In the second embodiment, an example is given where the user can use the card in the payment app even if they have not yet received the card, but the user may also be allowed to use the card in the payment app after receiving the card or after authentication for card use has been performed.

[0086] As described above, in the second embodiment, a user who applied for a card from the payment source setting screen SC2 may want to set that card as the payment source. Therefore, the payment system 1 can set that card as the payment source by transitioning from the notification screen SC6 to the payment source setting screen SC2. A user who applied for a card from the charge source setting screen SC5 may want to set that card as the charge source. Therefore, the payment system 1 can set that card as the charge source by transitioning from the notification screen SC6 to the charge source setting screen SC5. The details of the second embodiment will be described below.

[0087] [2-2. Functions realized in the payment system of the second embodiment] Figure 11 shows an example of the functions implemented in the payment system 1 of the second embodiment. Similar to the first embodiment, the components implemented in the payment system 1 can be configured by combining them into a single device or by further distributing them among multiple devices.

[0088] In the second embodiment, the payment system 1 may not include at least some of the functions described in the first embodiment. For example, the payment system 1 may not include the status acquisition unit 101. Figure 11 shows an example in which the payment system 1 does not include the status acquisition unit 101. When the first and second embodiments are combined, the payment system 1 includes the status acquisition unit 101. It will be obvious to those skilled in the art from the description of this disclosure that both embodiments of the payment system 1 including the status acquisition unit 101 and embodiments of the payment system 1 not including the status acquisition unit 101 are described in this disclosure.

[0089] [2-2-1. Functions implemented by the payment server] For example, the payment server 10 includes a data storage unit 100, an application screen information acquisition unit 103, and a display control unit 102. The data storage unit 100 is implemented by a storage unit 12. The application screen information acquisition unit 103 and the display control unit 102 are each implemented by a control unit 11.

[0090] [Data Storage Unit] The data storage unit 100 may be the same as in the first embodiment. The settlement database DB1 does not necessarily have to include status.

[0091] [Application Screen Information Acquisition Section] The application screen information acquisition unit 103 acquires application screen information related to the application screen on which a user applied for a card, in a payment service where a card application can be made from each of several application screens. In the second embodiment, since the application screen information is stored in the payment database DB1, the application screen information acquisition unit 103 acquires the application screen information from the payment database DB1. The application screen information may also be stored in a database other than the payment database DB1. In this case, the application screen information acquisition unit 103 acquires the application screen information from the other database. The application screen information may also be stored in a computer other than the payment server 10 or in an external information storage medium. In this case, the application screen information acquisition unit 103 acquires the application screen information from the other computer or in an external information storage medium.

[0092] The application screen information acquisition unit 103 can acquire application screen information at any time. For example, when the application screen information acquisition unit 103 receives a request from a user terminal 30 to display the payment source setting screen SC2 or the charge source setting screen SC5, it may generate application screen information and store the application screen information in the settlement database DB1 in association with the user ID of that user. The application screen information acquisition unit 103 can acquire the application screen information stored in the settlement database DB1 at any time. For example, the application screen information acquisition unit 103 may acquire application screen information when a user logs in to the payment service, when the top screen SC1 is displayed, when the notification screen SC6 is displayed, or at any other time.

[0093] [Display Control Unit] In the second embodiment, the display control unit 102 may not include at least some of the functions described in the first embodiment. For example, the display control unit 102 may not include a function to display a screen according to the status. When the first and second embodiments are combined, the display control unit 102 includes a function to display a screen according to the status. It will be obvious to those skilled in the art from the description of this disclosure that both embodiments of the display control unit 102 including a function to display a screen according to the status and embodiments of the display control unit 102 not including a function to display a screen according to the status are described in this disclosure.

[0094] For example, the display control unit 102 controls the transition of screens displayed in the payment service based on the application screen information. The display control unit 102 determines, as the destination screen from any given screen, to be the same screen as the application screen indicated by the application screen information, or a screen associated with the application screen indicated by the application screen information. The screen associated with the application screen indicated by the application screen information is assumed to be stored in advance in the data storage unit 100. For example, the screen associated with the application screen may be a screen displayed before the application screen (for example, a screen containing a link to the application screen), or a screen displayed after the application screen (for example, a screen indicated by a link included in the application screen).

[0095] For example, the display control unit 102 may control the transition of screens displayed in the payment service after the card review is completed, based on the application screen information. In the example in Figure 10, if the application screen information indicates the payment source setting screen SC2, the display control unit 102 transitions from the notification screen SC6, which notifies that the card review is complete, to the payment source setting screen SC2. If the application screen information indicates the charge source setting screen SC5, the display control unit 102 transitions from the notification screen SC6 to the charge source setting screen SC5.

[0096] For example, the display control unit 102 may display a link on the notification screen SC6 corresponding to the application screen information and control the screen transition according to the user's selection of the link. In the example in Figure 10, if the application screen information indicates the payment source setting screen SC2, the display control unit 102 displays a link to the payment source setting screen SC2 on the notification screen SC6, and when the user selects the link, it transitions from the notification screen SC6 to the payment source setting screen SC2. If the application screen information indicates the charge source setting screen SC5, the display control unit 102 displays a link to the charge source setting screen SC5 on the notification screen SC6, and when the user selects the link, it transitions from the notification screen SC6 to the charge source setting screen SC5. Note that the link corresponding to the application screen information may include not only screen transitions but also settings on that screen (settings for the payment source or settings for the charge source).

[0097] The display control unit 102 may also control the transition of screens displayed in the payment service after the card application is completed, based on the application screen information. For example, the display control unit 102 may control the transition of screens from the completion screen SC4, which indicates that the card application has been completed, based on the application screen information. For example, the completion screen SC4 may include a link similar to that of the notification screen SC6. The completion screen SC4 may include this link once the review process is complete. If the application screen information indicates the payment source setting screen SC2, the display control unit 102 will transition from the completion screen SC4 to the payment source setting screen SC2. If the application screen information indicates the charge source setting screen SC5, the display control unit 102 will transition from the completion screen SC4 to the charge source setting screen SC5.

[0098] In the second embodiment, we take the example of a case where the destination screen is the same screen as the application screen indicated by the application screen information. The source screen may be any screen. In the second embodiment, the notification screen SC6 is the source screen. The source screen may be a screen on the payment application or a screen unrelated to the payment application. For example, if a notification function other than the notification function on the payment application (e.g., email) is used, the screen of the other notification function may be the source screen. In this case, the display control unit 102 can cause the user to transition to the destination screen by including a link to the destination screen in the notification of the other notification function such as email.

[0099] For example, the display control unit 102 transitions to the settings screen when a settings screen related to the settings of the payment method used by the user in the payment service is shown as an application screen in the application screen information. In the second embodiment, an example is given in which the setting of the payment source and the setting of the charge source each correspond to the setting of the payment method. For this reason, an example is given in which the payment source setting screen SC2 and the charge source setting screen SC5 each correspond to the settings screen. Where it is written as payment source setting screen SC2 or charge source setting screen SC5, it can be read as settings screen.

[0100] Note that the settings screen may be any screen other than the payment source settings screen SC2 and the charge source settings screen SC5. The settings screen is not limited to the payment source settings screen SC2 and the charge source settings screen SC5. The settings screen may be any screen where some settings for the payment service are made. For example, the settings screen may be a screen where user registration information is set, a screen where the display settings of the payment app are set, a screen where the functions used by the user in the payment app are set, a screen where the money transfer settings in the payment app are set, or any other screen.

[0101] For example, the display control unit 102 displays a notification screen SC6 on the user terminal 30 that transitions to the destination screen corresponding to the application screen indicated by the application screen information. If the application screen is the payment source setting screen SC2, the display control unit 102 displays a button B60 on the notification screen SC6 that indicates a link to the payment source setting screen SC2. If the application screen is the charge source setting screen SC5, the display control unit 102 displays a button B60 on the notification screen SC6 that indicates a link to the charge source setting screen SC5. If button B60 is selected, the display control unit 102 controls the transition to the destination screen based on the link indicated by button B60.

[0102] [2-2-2. Functions implemented by the card server] The functions implemented by the card server 20 may be the same as those in the first embodiment. The card database DB2 does not necessarily need to include status information.

[0103] [2-2-3. Functions implemented on the user terminal] The functions implemented on the user terminal 30 may be the same as those in the first embodiment.

[0104] [2-3. Processing performed in the payment system of the second embodiment] Figure 12 shows an example of the processing performed in the payment system 1 of the second embodiment. The processing in Figure 12 is performed by the control units 11 and 21 executing programs stored in the storage units 12 and 22, respectively. Although the processing of the card server 20 is not shown in Figure 12, the card server 20 may perform the same processing as in the first embodiment.

[0105] As shown in Figure 12, the processes in S200 to S202 are the same as those in S100 to S102. In S202, the user performs an operation to display the notification screen SC6 (for example, an operation to select the notification function from the top screen SC1), or another operation. If the user performs another operation in S202 (S202: Other operation), the process corresponding to the other operation is executed, and this process ends. If the user performs an operation to display the notification screen SC6 in S202 (S202: Notification screen), the user terminal 30 sends a request to the payment server 10 to display the notification screen SC6 (S203). The payment server 10 receives the request to display the notification screen SC6 (S204).

[0106] The payment server 10 obtains application screen information based on the payment database DB1 (S205). The payment server 10 performs processing to display the notification screen SC6 with the user terminal 30 (S206). In S206, the payment server 10 generates display data for the notification screen SC6, which includes links to transition destinations according to the application screen information (for example, a link to the payment source setting screen SC2 if the application screen is the payment source setting screen SC2, and a link to the charge source setting screen SC5 if the application screen is the charge source setting screen SC5). The payment server 10 sends the display data for the notification screen SC6 to the user terminal 30. The user terminal 30 receives the display data for the notification screen SC6 from the payment server 10. Based on this display data, the user terminal 30 displays the notification screen SC6 on the display unit 35.

[0107] The user terminal 30 identifies the user's operation (S207). In S207, the user may select a notification (for example, select button B60) or perform another operation. If the user performs another operation in S207 (S207: Other operation), processing corresponding to the other operation is executed, and this process ends. If the user selects a notification in S207 (S207: Notification selected), the user terminal 30 executes a process with the payment server 10 to transition to the destination screen corresponding to the application screen information (S208), and this process ends. In S208, if the application screen information indicates the payment source setting screen SC2, the user terminal 30 executes a process with the payment server 10 to transition to the payment source setting screen SC2. If the application screen information indicates the charge source setting screen SC5, the user terminal 30 executes a process with the payment server 10 to transition to the charge source setting screen SC5.

[0108] [2-4. Summary of the Second Embodiment] The payment system 1 of the second embodiment acquires application screen information. Based on the application screen information, the payment system 1 controls the transitions between screens displayed in the payment service. This allows the payment system 1 to enhance user convenience. For example, the application screen where a user applies for a card reflects the user's purpose for using the card in the payment service. Therefore, the payment system 1 can transition the user to a screen that allows them to achieve their purpose by transitioning them to a screen corresponding to the application screen information.

[0109] Furthermore, if a settings screen related to the settings of the payment method used by the user in the payment service is shown as an application screen in the application screen information, the payment system 1 will transition to the settings screen. This allows the payment system 1 to enhance user convenience. For example, if a user who applied for a card from the payment source settings screen SC2 wants to set that card as the payment source, the payment system 1 will transition from the notification screen SC6 to the payment source settings screen SC2, allowing the user to set that card as the payment source directly. If a user who applied for a card from the charge source settings screen SC5 wants to set that card as the charge source, the payment system 1 will transition from the notification screen SC6 to the charge source settings screen SC5, allowing the user to set that card as the charge source directly.

[0110] [3. Variant] This disclosure is not limited to the embodiments described above. This disclosure may be modified as appropriate without departing from the spirit of this disclosure.

[0111] [3-1. Modified Examples of the First Embodiment]

[0112] Figure 13 shows an example of a function realized in a modified version of the first embodiment. For example, the payment server 10 includes an input information storage unit 104 and a resume unit 105. Each of the input information storage unit 104 and the resume unit 105 is realized by a control unit 11.

[0113] [Variation 1-1] For example, in the first embodiment, the status indicates whether or not the user possesses a card that can be applied for through the payment service. The status may also indicate other information about the card. In the modified example 1-1, the status acquisition unit 101 acquires a status indicating whether or not the card is set as a payment method used by the user in the payment service. In the modified example 1-1, the payment source or charge source is described as an example of a payment method used by the user, but a payment method that is not specifically set as a payment source or charge source but is registered with the payment service may also correspond to a payment method used by the user.

[0114] In Modification 1-1, an example is given where the status is stored in the settlement database DB1 as information separate from the payment source information and charge source information, but at least one of the payment source setting information and charge source information may correspond to the status. The status acquisition unit 101 acquires a status from the settlement database DB1 indicating whether or not a card that can be applied for from the settlement service is set as a payment method used by the user in the settlement service. The status acquisition unit 101 may acquire the status from another database, another computer other than the settlement server 10, or an external information storage medium.

[0115] For example, when a user terminal 30 performs an operation to set a card that can be applied for from the payment service as the payment source from the payment source setting screen SC2 (for example, by selecting on panel P24), it sends a payment source setting request to the payment server 10 to set that card as the payment source. When the payment server 10 receives the payment source setting request from the user terminal 30, it updates the status associated with the user's user ID among the statuses stored in the payment database DB1 to indicate that the card has been set as the payment source. The status acquisition unit 101 acquires the updated status.

[0116] For example, when a user performs an operation to set another payment method as the payment source from the payment source setting screen SC2 on the user terminal 30 (for example, by selecting on panel P22), the user terminal 30 sends a payment source setting request to the payment server 10 to set another payment method as the payment source. When the payment server 10 receives the payment source setting request from the user terminal 30, it updates the status associated with the user ID of the user in question among the statuses stored in the payment database DB1 to indicate that another payment method has been set as the payment source. The status acquisition unit 101 acquires the updated status.

[0117] For example, when a user performs an operation on the user terminal 30 to set a card that can be applied for from the payment service as the charge source (for example, by selecting on panel P54) from the charge source setting screen SC5, the user sends a charge source setting request to the payment server 10 to set that card as the charge source. When the payment server 10 receives the charge source setting request from the user terminal 30, it updates the status associated with the user's user ID among the statuses stored in the payment database DB1 to indicate that the card has been set as the charge source. The status acquisition unit 101 acquires the updated status.

[0118] For example, when a user performs an operation to set another payment method as the charge source from the charge source setting screen SC5 on the user terminal 30 (for example, by selecting on panel P52), the user terminal 30 sends a charge source setting request to the payment server 10 to set another payment method as the charge source. When the payment server 10 receives the charge source setting request from the user terminal 30, it updates the status associated with the user ID of the user in question among the statuses stored in the payment database DB1 to indicate that another payment method has been set as the charge source. The status acquisition unit 101 acquires the updated status.

[0119] Figure 14 shows an example of a screen displayed on the user terminal 30 in Modification 1-1. For example, once the application for a card that can be applied for through the payment service is completed, the display control unit 102 displays content related to the card settings on the relevant screen related to the settings of the payment method used by the user in the payment service, based on a status indicating whether or not the card is set as a payment method used by the user in the payment service. In Modification 1-1, as in the first embodiment, the payment source setting screen SC2 and the charge source setting screen SC5 are described as examples of relevant screens.

[0120] For example, if the status indicates that a card available for application through the payment service is set as the payment source, the display control unit 102 displays a payment source setting screen SC2 on the user terminal 30, as shown on the left side of Figure 14, indicating that the payment source being set is that card. In this case, since the payment source being set is that card, the payment source setting screen SC2 does not specifically prompt the user to set that card as the payment source. In the example on the left side of Figure 14, the panel P20 indicating the payment source being set shows the information of that card.

[0121] On the other hand, if the status indicates that no card available for application through the payment service is set as the payment source, the display control unit 102 displays a payment source setting screen SC2 on the user terminal 30, as shown on the right side of Figure 14, indicating that the payment source being set is not the card in question and prompting the user to set the card in question as the payment source. In the example on the right side of Figure 14, the panel P20 showing the payment source being set displays information on other payment methods besides the card in question, and also displays a string of text (for example, the string "recommended") prompting the user to set the card in question as the payment source. The user may be prompted to set the card in question as the payment source in any manner, for example, by other strings of text (for example, a string of text indicating "granting of points or other benefits"), icons, images other than icons, colors, patterns, shapes, screen effects, or in any other manner. The data necessary for these displays is stored in the data storage unit 100.

[0122] The display control unit 102 may also display a similar information on the charge source setting screen SC5. For example, if the status indicates that no card available for application from the payment service is set as the charge source, the display control unit 102 may display the charge source setting screen SC5 on the user terminal 30, indicating that the currently set charge source is not that card and prompting the user to set that card as the charge source.

[0123] The payment system 1 in Modification 1-1 acquires a status indicating whether or not a card is set as a payment method used by the user in the payment service. Based on the status indicating whether or not the card is set as a payment method used by the user in the payment service, the payment system 1 displays content related to the settings of the card on the relevant screen related to the settings of the payment method used by the user in the payment service. This allows the payment system 1 to promote the use of the card in the payment service. For example, as shown on the right side of Figure 14, the payment system 1 can motivate the user to use the card by displaying a string of text that encourages the use of the card.

[0124] [Variation 1-2] For example, the display control unit 102 may determine whether a predetermined payment method is set as the payment method used by the user in the payment service, and based on the result of this determination, it may display content related to the card setting on the relevant screen related to the setting of the payment method used by the user in the payment service. The predetermined payment method may be any predetermined payment method. The predetermined payment method shall be a payment method other than a card that can be applied for from the payment service.

[0125] Modification 1-2 takes the case where the bank account "AAA Bank" described in the first embodiment is the predetermined payment method as an example. Also, in Modification 1-2, as in the first embodiment, the payment source setting screen SC2 and the charge source setting screen SC5 are described as examples of related screens. The display control unit 102 performs a determination as in Modification 1-1 whether the predetermined payment method is set as the payment method used by the user in the payment service. That is, the display control unit 102 can perform the above determination based on the status described in Modification 1-1, or the payment source information or charge source information described in the first embodiment.

[0126] For example, if the display control unit 102 determines that a predetermined payment method is set as the payment method used by the user in the payment service, it does not display a prompt to set up a card as in the modified example 1-1. That is, if the bank account "AAA Bank" is set as the payment source or charge source, the display control unit 102 does not display a prompt to set up a card as in the modified example 1-1. For example, the display control unit 102 displays panel P24 on the payment source setting screen SC2, which does not contain the string "Recommended!" as in the example on the right side of Figure 14. Similarly, the display control unit 102 displays panel P54 on the charge source setting screen SC5, which does not contain the string "Recommended!".

[0127] For example, if the display control unit 102 determines that a payment method other than a predetermined payment method is set as the payment method used by the user in the payment service, it displays a message prompting the user to set up a card, as shown in Modification 1-1. The other payment method is a payment method other than a card that can be applied for from the payment service. That is, if a payment method other than the bank account "AAA Bank" (for example, the card "ZZZ Card") is set as the payment source or charge source, the display control unit 102 displays a message prompting the user to set up a card, as shown in Modification 1-1.

[0128] The payment system 1 in Modification 1-2 performs a determination to determine whether a predetermined payment method is set as the payment method used by the user in the payment service, and based on the result of this determination, displays content related to the card settings on the relevant screen related to the settings of the payment method used by the user in the payment service. This allows the payment system 1 to display flexible content on the relevant screen according to the payment method used by the user in the payment service. For example, the payment system 1 can decide whether or not to prompt the user to use a card that can be applied for from the payment service, depending on the payment source or charge source that is set.

[0129] [Modifications 1-3] For example, in Modification 1-2, the display control unit 102 may display content on the relevant screen related to the setting of the payment method used by the user in the payment service, according to the relationship between the setting business operator for the payment method being set and the card business operator for the card. The setting business operator is a business operator that manages the payment method being set as the source of payment or charge. For example, an electronic money business operator, a card business operator, a financial institution such as a bank or securities company, or another business operator corresponds to the setting business operator. The card business operator is a business operator that manages the cards that can be applied for from the payment service. For example, if a credit card corresponds to a card, the card company that issues the credit card corresponds to the card business operator.

[0130] In Modification 1-3, as in the first embodiment, the payment source setting screen SC2 and the charge source setting screen SC5 are described as examples of related screens. In Modification 1-3, the fact that the business being set up has a predetermined relationship (e.g., a cooperative relationship) with the card company corresponds to the fact that the payment source or charge source is a predetermined payment method in Modification 1-2. For example, if the business being set up has a predetermined relationship with the card company, the display control unit 102 does not display content prompting the user to set up a card on the payment source setting screen SC2 or the charge source setting screen SC5. If the business being set up does not have a predetermined relationship (e.g., a cooperative relationship) with the card company, the display control unit 102 displays content prompting the user to set up a card on the payment source setting screen SC2 or the charge source setting screen SC5. Note that the predetermined relationship includes the fact that the business being set up is the same as the card company.

[0131] The payment system 1 in Modification 1-3 displays content on related screens related to the setting of payment methods used by the user in the payment service, according to the relationship between the setting business operator for the payment method being set and the card company for the card. This allows the payment system 1 to display flexible content on related screens according to the relationship between the setting business operator and the card company. For example, the payment system 1 can display flexible content such as not showing content prompting the user to set up a card if the setting business operator has a cooperative relationship with the card company, and showing content prompting the user to set up a card if the setting business operator does not have a cooperative relationship with the card company.

[0132] [Modifications 1-4] For example, the status acquisition unit 101 may acquire a status indicating whether or not the user has applied for a card. The status will be either a value indicating that the user has applied for a card, or a value indicating that the user has not applied for a card. The initial value of the status will be a value indicating that the user has not applied for a card, however, if the user already possesses a card at the time of registering to use the payment service, the initial value of the status may be a value indicating that the user has applied for a card. The payment server 10 can determine whether or not the user already possesses a card at the time of registering to use the payment service by querying the card server 20.

[0133] For example, if the payment server 10 detects that a user has applied for a card using the procedure described in the first embodiment, based on the communication content with the user terminal 30, it updates the status associated with the user's user ID among the statuses stored in the payment database DB1 to indicate that the card application has been made. In this case, the status acquisition unit 101 acquires the updated status. If the payment server 10 does not detect that a user has applied for a card, it does not change the status from its initial value. In this case, the status acquisition unit 101 acquires the initial status.

[0134] Figure 15 shows an example of a screen displayed on the user terminal 30 in Modification 1-4. For example, the display control unit 102 displays content related to the card application on related screens related to the settings of the payment method used by the user in the payment service, based on a status indicating whether or not the user has applied for a card. In Modification 1-4, as in the first embodiment, the payment source setting screen SC2 and the charge source setting screen SC5 are described as examples of related screens.

[0135] For example, if the status indicates that the user has not applied for a card, the display control unit 102 displays the payment source setting screen SC2 (which does not include the "Applying" icon described later) on the user terminal 30, as shown on the left side of Figure 15, similar to the upper right of Figure 2. If the status indicates that the user has applied for a card, the display control unit 102 displays content on the payment source setting screen SC2 indicating that the user has applied for a card, as shown on the right side of Figure 15.

[0136] In the example on the right side of Figure 15, the icon "Application in Progress" displayed in panel P21 corresponds to the content in question. This content may be other icons, images other than icons, text strings, shapes, or other content. The data representing this content is stored in the data storage unit 100. Once the card application is approved, panel P24 is displayed in place of panel P21, as shown in the payment source setting screen SC2 in the upper right of Figure 4, allowing the user to set the card as the payment source.

[0137] The display control unit 102 may also display the same information on the charge source setting screen SC5. For example, if the status indicates that the user has not applied for a card, the display control unit 102 will display the charge source setting screen SC5 (without the "Applying" icon) on the user terminal 30, similar to the upper right of Figure 3. If the status indicates that the user has applied for a card, the display control unit 102 will display content on the charge source setting screen SC5 indicating that the user has applied for a card (for example, the "Applying" icon).

[0138] The payment system 1 in Modification 1-4 acquires a status indicating whether or not the user has applied for a card. Based on this status, the payment system 1 displays content related to card applications on the relevant screens associated with the settings of the payment method used by the user in the payment service. This allows the payment system 1 to display flexible content on the relevant screens depending on whether or not the user has applied for a card. For example, the user can easily determine from the content whether or not they have applied for a card.

[0139] [Variations 1-5] For example, the display control unit 102 may determine whether or not a card other than the card (for example, the card applied for by the payment service) is set as a payment method used by the user in the payment service, and display content according to the result of the determination. Modification 1-5 describes the payment source setting screen SC2 and the charge source setting screen SC5 as examples of related screens, similar to the first embodiment. The display control unit 102 makes the above determination based on the payment source information or charge source information. The other card may be any card other than the card applied for by the payment service. The other card is a card for which no application is made by the payment service. The display control unit 102 may make the above determination by determining whether or not the card operator of the card indicated by the payment source information or charge source information is a specific operator.

[0140] For example, if the display control unit 102 determines that another card is set as the payment method used by the user in the payment service, it displays a payment source setting screen SC2 or a charge source setting screen SC5 on the user terminal 30 prompting the user to set the card to be applied for by the payment service. Setting the card to be applied for by the payment service may be prompted in the same manner as in the modified example 1-1. If the display control unit 102 does not determine that another card is set as the payment method used by the user in the payment service, it displays a payment source setting screen SC2 or a charge source setting screen SC5 on the user terminal 30 that does not prompt the user to set the card to be applied for by the payment service.

[0141] The payment system 1 in Modification 1-5 determines whether a card other than a credit card is set as the payment method used by the user in the payment service, and displays content according to the result of that determination. This allows the payment system 1 to display flexible content depending on whether a card other than a credit card is set as the payment method used by the user in the payment service. For example, if a specific card that the payment system 1 wants to promote the use of in the payment service is not set as the payment source or charge source, it can encourage applications for that card. For example, if a user has set another card as the payment method used in the payment service, it is highly likely that the user is more inclined to use a credit card itself rather than a payment method such as a bank account. Since credit cards are likely to be highly appealing to such users, the payment system 1 can encourage such users to apply for a credit card.

[0142] [Variations 1-6] For example, a payment service may allow users to start using the service without having to configure any payment source settings after registering for the service. In this case, electronic money is set as the default payment source. Electronic money is permitted for use on the condition that the user registers for the payment service. Users can top up their electronic money by depositing cash into an ATM, etc. The method of topping up electronic money may be a publicly known method. The default payment source may also be a payment method other than electronic money.

[0143] In Modification 1-6, the display control unit 102 determines whether the user has started using the payment service without setting a payment method to be used in the payment service, and displays content according to the result of the determination. In Modification 1-6, it is assumed that the payment service start information indicating whether the user has started using the payment service without setting a payment method to be used in the payment service is stored in the payment database DB1. For example, if the user starts using the payment service without setting a payment method to be used in the payment service, the payment server 10 updates the payment service start information associated with the user's user ID to indicate this. If the user sets a payment method to be used in the payment service and starts using the payment service, the payment server 10 updates the payment service start information associated with the user's user ID to indicate this.

[0144] For example, if the display control unit 102 determines that the user has started using the payment service without setting a payment method to be used with the payment service, it displays the payment source setting screen SC2, which is either unset or has the default payment source setting, or the charge source setting screen SC5, which is either unset or has the default charge source setting, on the user terminal 30. If the display control unit 102 determines that the user has started using the payment service after setting a payment method to be used with the payment service, and the user possesses a card that can be applied for through the payment service, it displays the payment source setting screen SC2 or charge source setting screen SC5, similar to Figure 4, on the user terminal 30. Even if the user does not possess a card that can be applied for through the payment service, if any payment method is set as the payment source or charge source, the display control unit 102 may display the payment source setting screen SC2 or charge source setting screen SC5, similar to Figure 4, on the user terminal 30.

[0145] The payment system 1 in Modification 1-6 determines whether the user has started using the payment service without setting a payment method to be used with the payment service, and displays content according to the result of that determination. This allows the payment system 1 to display flexible content depending on whether the user has started using the payment service without setting a payment method to be used with the payment service. For example, the payment system 1 can prompt a user who has started using the payment service without setting a payment method to apply for a card that can be applied for through the payment service.

[0146] [Variations 1-7] For example, if a user starts a card application from the application screen SC3, the user may interrupt the application process before the card application is completed. Therefore, the status acquisition unit 101 may acquire a status indicating whether or not the user has interrupted the card application. Interrupting an application means that the user stops the application process midway. Interrupting an application can also be described as a status where the application has been started but has not been completed.

[0147] For example, the status acquisition unit 101 determines whether the user has interrupted the card application based on the content of communication with the user terminal 30. When the user performs an application start operation to begin the card application (for example, selecting panels P21 and P51), the user terminal 30 sends an application start notification to the settlement server 10 indicating that the user has performed an application start operation. When the settlement server 10 receives the application start notification from the user terminal 30, the status acquisition unit 101 updates the status stored in the settlement database DB1 so that the status associated with the user's user ID indicates the start of the application. The status acquisition unit 101 may acquire the updated status from the settlement database DB1 at any time. In the modified example 1-7, the status acquisition unit 101 may also acquire the status from another database, another computer other than the settlement server 10, or an external information storage medium.

[0148] For example, when a user completes the application completion operation to finalize their card application (for example, the final operation performed from the application screen SC3), the user terminal 30 sends an application completion notification indicating that the user has completed the application completion operation. When the payment server 10 receives the application completion notification from the user terminal 30, the status acquisition unit 101 updates the status stored in the payment database DB1 so that the status associated with the user's user ID indicates that the application has been completed. The status acquisition unit 101 may acquire the updated status from the payment database DB1 at any time.

[0149] For example, if a user performs an application interruption operation to interrupt a card application (for example, by selecting a predetermined button displayed on the application screen SC3), the user terminal 30 sends an application interruption notification indicating that the user has performed an application interruption operation. An application interruption operation is an operation in which the user stops the application, or an operation in which the user temporarily interrupts the application without stopping it (for example, by saving at least some of the input information and resuming the application later). When the settlement server 10 receives the application interruption notification from the user terminal 30, the status acquisition unit 101 updates the status stored in the settlement database DB1 so that the status associated with the user's user ID indicates that the application has been interrupted. The status acquisition unit 101 may acquire the updated status from the settlement database DB1 at any time.

[0150] It should be noted that users may not perform an application interruption operation, or the application interruption operation may not even exist. In this case, the status acquisition unit 101 may update the status to a value indicating application interruption if a predetermined amount of time has elapsed since the user started the card application (for example, since the payment server 10 received the application start operation, or since the status became a value indicating the start of the application) without receiving an application completion notification. Alternatively, for example, the status acquisition unit 101 may update the status to a value indicating application interruption if the session with the user terminal 30 is disconnected after the user started the card application without receiving an application completion notification.

[0151] Figure 16 shows an example of a screen displayed on the user terminal 30 in Modification 1-7. In Modification 1-7, the display control unit 102 displays content on the relevant screen to allow the user to resume the card application, based on a status indicating whether or not the user has interrupted the card application. In Modification 1-7, as in the first embodiment, the payment source setting screen SC2 and the charge source setting screen SC5 are described as examples of relevant screens.

[0152] For example, if the status indicates that the user has interrupted their card application, the display control unit 102 displays a payment source setting screen SC2, which includes a panel P21 for the user to resume their card application, on the user terminal 30, as shown on the left side of Figure 16. In the example on the left side of Figure 16, panel P21 includes an icon indicating that the card application is interrupted. The data for the icon is stored in the data storage unit 100.

[0153] On the other hand, if the status indicates that the user has not interrupted the card application, the display control unit 102 displays the payment source setting screen SC2, which includes panel P21 without an icon, on the user terminal 30, as shown on the right side of Figure 16, so that the user can resume the card application. In the example on the right side of Figure 16, similar to the right side of Figure 15 described in Modification 1-5, the display control unit 102 displays the payment source setting screen SC2, which includes panel P21 with an icon indicating that the user has applied for a card, on the user terminal 30.

[0154] The display control unit 102 may also display the same information on the charge source setting screen SC5. For example, if the status indicates that the user has interrupted the card application, the display control unit 102 may display content indicating that the user has interrupted the card application (for example, an icon "Interrupted").

[0155] The payment system 1 in Modification 1-7 obtains a status indicating whether the user has interrupted their card application. Based on this status, the payment system 1 displays content on the relevant screen to allow the user to resume their card application. This allows the payment system 1 to display flexible content on the relevant screen depending on whether the user has interrupted their card application. For example, the user can easily determine from the content whether they have interrupted their card application.

[0156] [Variations 1-8] For example, in Modification 1-7, at least some of the input information entered by the user before interrupting the application may be saved. The input information is the information entered by the user from the operation unit 34. For example, the input information may be a string entered by the user, the on / off value of a checkbox or radio button selected by the user, an identity verification document uploaded by the user, or other information. If the user resumes the application, the application may be resumed based on the saved input information.

[0157] Furthermore, the aforementioned modifications 1-7 also include a configuration in which the input information is not saved. For example, if a user resumes the application, the card application may be restarted so that the user enters the input information from the beginning. In this case, if some pre-processing is performed before the input of the input information, data indicating the result of the pre-processing is stored in the settlement server 10 or the user terminal 30, and based on this data, the card application may be restarted without performing pre-processing again.

[0158] The settlement system 1 of Modification 1-8 includes an input information storage unit 104 and a resume unit 105. The input information storage unit 104 stores at least some of the input information entered by the user up to that point when the user interrupts the card application. For example, when a user interrupts the application, the user terminal 30 sends input information to the settlement server 10 indicating the content entered by the user up to that point. When the settlement server 10 receives the input information from the user terminal 30, the input information storage unit 104 stores the input information by associating it with the user's user ID and storing it in the settlement database DB1. The input information storage unit 104 may store the input information in a database other than the settlement database DB1, a computer other than the settlement server 10, or an external information storage medium.

[0159] If the user does not perform an application interruption operation, or if there is no application interruption operation in the first place, the user terminal 30 sends input information to the payment server 10 each time the user enters input information. The user terminal 30 may also periodically send input information to the payment server 10. The input information storage unit 104 stores the input information received from the user terminal 30 in the payment database DB1.

[0160] The restart unit 105 restarts the card application when the user restarts the card application, based on at least some of the input information saved by the input information storage unit 104. For example, when the user restarts the application (for example, by selecting panels P21 and P51 which include an icon indicating that the application is suspended), the user terminal 30 sends an application restart notification indicating that the user has restarted the application. When the settlement server 10 receives the application restart notification from the user terminal 30, the restart unit 105 restarts the card application by displaying the application screen SC3 on the user terminal 30 based on the input information saved by the input information storage unit 104.

[0161] The payment system 1 in Modification 1-8 saves at least some of the input information that the user has entered up to that point if the user interrupts the card application process. When the user resumes the card application, the payment system 1 resumes the application based on at least some of the input information saved by the input information storage unit 104. As a result, the user does not have to re-enter previously entered information when resuming the card application, thus reducing the effort required from the user.

[0162] [Modifications 1-9] For example, the status acquisition unit 101 may acquire a status indicating whether or not the user has passed the card application review. If the user has passed the card application review, the status acquisition unit 101 updates the status associated with the user's user ID to indicate this. If the user has not passed the card application review (i.e., the user has failed the card application review), the status acquisition unit 101 updates the status associated with the user's user ID to indicate this. The card application review results are uploaded to the card server 20 by a person from the card company. The card application review process may be automated, at least partially. The card server 20 updates the status stored in the card database DB2 based on the card application review results. The status acquisition unit 101 acquires the status from the card server 20 and updates the status stored in the payment database DB1.

[0163] Figure 17 shows an example of a screen displayed on the user terminal 30 in Modification 1-9. In Modification 1-9, the display control unit 102 displays content on the relevant screen for the user to apply for the card again, based on the status indicating whether or not the user has passed the card screening. In Modification 1-9, as in the first embodiment, the payment source setting screen SC2 and the charge source setting screen SC5 are described as examples of relevant screens.

[0164] For example, if the user passes the card application review, the display control unit 102 displays a panel P24 on the payment source setting screen SC2 with an icon indicating that the user has passed the card application review, as shown on the left side of Figure 17. If the user does not pass the card application review, the display control unit 102 displays a panel P21 on the payment source setting screen SC2 with an icon indicating that the user has not passed the card application review, as shown on the right side of Figure 17. If the user selects panel P21, the card application is submitted again.

[0165] The payment system 1 in Modification 1-9 obtains a status indicating whether the user has passed the card application review. Based on this status, the payment system 1 displays content on the relevant screen that allows the user to reapply for the card. This allows the payment system 1 to display flexible content on the relevant screen depending on whether the user has passed the card application review. For example, the user can easily understand from the content whether they have passed the card application review or not. The user can also easily understand from the content whether they have failed the card application review and need to reapply or have already done so.

[0166] [Variations 1-10] For example, as described in the first embodiment, the user uses a payment service from a payment app stored on the user's terminal 30. The payment app screen may be displayed when the user selects a link (e.g., Deep Link). In Modification 1-10, the example given is that the link is to an app other than the payment app, but the link may also be a link within the payment app.

[0167] Figure 18 shows an example of a screen displayed on the user terminal 30 in Modification 1-10. As shown on the left side of Figure 18, the user terminal 30 displays a link screen SC7, which includes a link L70 to a related screen, on the display unit 35, based on an application other than the payment application. The other application may be any application that works in conjunction with the payment application. For example, the other application may be an e-commerce service, a travel booking service, a communication service, a financial service, a points management service, or an application for another service.

[0168] Link L70 is a link to a related screen. For example, link L70 includes app identifier information that can identify a payment app and screen identifier information that can identify a screen within the payment app. Link L70 may be in any format and may include a URL, for example. Modification 1-10 takes the case where application screen SC3 corresponds to a related screen as an example. Therefore, where application screen SC3 is written in Modification 1-10, it can be read as related screen. Link L70 is a link to application screen SC3.

[0169] In the modified example 1-10, the status acquisition unit 101 acquires the status when the user selects link L70 to launch the payment application on the user terminal 30. For example, when the user selects link L70, the user terminal 30 sends a request to the payment server 10 to display the application screen SC3. The process by which the display request is sent upon selection of link L70 may be the same as known processes. If the payment application is not running on the user terminal 30 when link L70 is selected, the user terminal 30 launches the payment application. If the payment application is running but in the background, the user terminal 30 brings the payment application to the foreground.

[0170] For example, as shown on the right side of Figure 18, the display control unit 102 displays card-related content on the application screen SC3 displayed on the payment application when the user selects link L70. Modification example 1-10 takes the case where the input form for card application corresponds to card-related content. When the payment server 10 receives a request to display the application screen SC3 from the user terminal 30, it sends the display data for the application screen SC3 to the user terminal 30. When the user terminal 30 receives the display data for the application screen SC3 from the payment server 10, the display control unit 102 displays the application screen SC3 based on the display data.

[0171] In the modified example 1-10, the payment system 1 obtains a status when the user selects link L70 to launch the payment app on the user terminal 30. When the user selects link L70, the payment system 1 displays card-related content on the related screen displayed on the payment app. This eliminates the need for the user to perform an operation to display card-related content separately from the operation to select link L70, thus reducing the user's operational burden and further enhancing user convenience. For example, if the related screen is the application screen SC3 and the card-related content is an input form for application, the payment system 1 can facilitate the application of the card.

[0172] [Variations 1-11] For example, when a user uses a payment service from a payment app, the display control unit 102 may, based on whether or not the user possesses a card, display content on the relevant screen displayed on the payment app that allows the user to use card-related functions. Card-related functions refer to at least one of the programs or data in the card service and the programs or data for the payment service to cooperate with the card service. In Modification 1-11, the case where the top screen SC1 corresponds to the relevant screen is given as an example.

[0173] Figure 19 shows an example of a screen displayed on the user terminal 30 in Modification 1-11. As shown on the left side of Figure 19, the display control unit 102 displays icon I130 in the display area A13 of the top screen SC1. In Modification 1-11, icon I130 is described as an example of content for users to utilize card-related functions. The display control unit 102 displays icon I130 for users to utilize card-related functions on the same top screen SC1 as the code C10 for users to utilize payment services.

[0174] For example, when a user selects icon I130, the user terminal 30 sends a request to the payment server 10 to display the card screen SC8, which is a screen for the user to use card-related functions. When the payment server 10 receives the request to display the card screen SC8, the status acquisition unit 101 acquires the status of the user's card. The method for acquiring the status may be the same as in the first embodiment. The display control unit 102 causes the user terminal 30 to display the card screen SC8 according to the status.

[0175] For example, if the status indicates that the user does not possess a card, the display control unit 102 displays a card screen SC8 similar to the application screen SC3, as shown in the upper right of Figure 19. The user applies for a card from the card screen SC8. The display method of the card screen SC8 may be the same as the display method of the application screen SC3. If the status indicates that the user possesses a card, the display control unit 102 displays a card screen SC8 showing information about the card already possessed, as shown in the lower right of Figure 19. The card screen SC8 may display the card company's website as a web view of the payment application.

[0176] The display control unit 102 may also display an icon I130 on the top screen SC1 corresponding to the status. For example, if the status indicates that the user does not possess a card, the display control unit 102 may display an icon I130 prompting the user to apply for a card. If the status indicates that the user does not possess a card, the display control unit 102 may display a message prompting the user to apply for a card, associated with the icon I130. If the status indicates that the user possesses a card, the display control unit 102 may display a different icon I130 from the one prompting the user to apply for a card. If the status indicates that the user does not possess a card, the display control unit 102 may display a message other than the message prompting the user to apply for a card, associated with the icon I130.

[0177] The payment system 1 in modified example 1-11 displays content on the relevant screen shown on the payment app that allows the user to use card-related functions, based on whether or not the user possesses a card. This allows the user to check the content on the relevant screen that allows the user to use card-related functions, thereby improving user convenience.

[0178] [Variations 1-12] For example, the display control unit 102 may determine whether a payment made by a user in the payment service satisfies predetermined content display conditions, and based on the result of this determination, display content on a related screen indicating that the payment has been completed. Modification 1-12 gives an example where the payment completion screen indicating that the payment has been completed corresponds to the related screen. Therefore, the part of Modification 1-12 that describes the payment completion screen can be read as referring to the related screen.

[0179] Content display conditions are criteria for determining whether or not to display content. Content display conditions can be any conditions that can be determined based on payment information. For example, content display conditions may be that the payment amount is equal to or greater than a predetermined amount, that the number of payments in a certain period is a predetermined number, that the payment was made by a predetermined member, that the payment was made on a predetermined date and time, or other conditions. The display control unit 102 determines whether or not the content display conditions have been met based on information indicating the result of the payment execution.

[0180] Figure 20 shows an example of a screen displayed on the user terminal 30 in the modified example 1-12. For example, as shown on the left side of Figure 20, when the top screen SC1 is displayed and code C10 is read by the terminal of a merchant (e.g., a store) participating in the payment service, the payment is executed. The payment flow may be the same as the known flow. For example, the merchant's terminal sends a payment request to the payment server 10, which includes the code ID obtained from code C10. The payment request also includes other information such as the payment amount. The payment server 10 executes the payment based on the code ID received from the merchant's terminal and the payment database DB1.

[0181] For example, the status acquisition unit 101 acquires the status when a payment is completed. The method for acquiring the status is the same as in the first embodiment. As shown on the right side of Figure 20, when a payment is completed, the display control unit 102 causes the user terminal 30 to display a payment completion screen SC9 containing content corresponding to the status. In the example on the right side of Figure 20, the payment completion screen SC9 shows the details of the completed payment (for example, the name of the merchant, the payment amount, and the date and time of payment). The data necessary for displaying the payment completion screen SC9 is stored in the data storage unit 100. Based on this data, the display control unit 102 generates display data for the payment completion screen SC9 and transmits this display data to the user terminal 30, thereby causing the user terminal 30 to display the payment completion screen SC9.

[0182] For example, if the status indicates that the user does not possess a card, the display control unit 102 displays a panel P90 for accepting a card application on the payment completion screen SC9. Panel P90 includes a link to the application screen SC3. If panel P90 is selected, the display control unit 102 displays the application screen SC3 on the user terminal 30. If the status indicates that the user possesses a card, the display control unit 102 displays other content (e.g., an advertisement) on the payment completion screen SC9 without including panel P90.

[0183] The payment system 1 in Modification 1-12 performs a determination to determine whether a payment made by a user in the payment service meets predetermined content display conditions, and based on the result of this determination, displays card-related content on a related screen indicating that the payment has been completed. Users often check the related screen indicating that the payment has been completed to confirm that the payment has been completed. The payment system 1 can display content on related screens that users are particularly interested in. For example, the payment system 1 can enhance the appeal of content for card applications.

[0184] [3-2. Modified Examples of the Second Embodiment] Figure 21 shows an example of a function realized in a modified version of the second embodiment. For example, the payment server 10 includes a first setting unit 106, a necessity determination unit 107, a second setting unit 108, an availability notification unit 109, and a third setting unit 110. Each of the first setting unit 106, the necessity determination unit 107, the second setting unit 108, the availability notification unit 109, and the third setting unit 110 is realized by a control unit 11.

[0185] [Variation 2-1] For example, in the second embodiment, we gave an example where the user manually sets a card that has completed the screening process as the payment source or charge source. However, a card that has completed the screening process may be automatically set as the payment source or charge source under predetermined conditions. Hereafter, these conditions will be referred to as the first setting conditions.

[0186] The payment system 1 of Modification 2-1 includes a first setting unit 106. The first setting unit 106 performs a determination to determine whether a predetermined first setting condition is met, and based on the result of the determination, automatically sets the card as the payment method used by the user in the payment service. For example, the payment method used by the user in the payment service is the payer or charge source. The first setting condition is a condition that serves as the criterion for whether or not to set the card as the payer or charge source. The first setting condition can be any predetermined condition. For example, the first setting condition may be that the user's card information is registered in the payment service, card service, or other service. Automatic setting means that the setting is performed by information processing on the payment system 1 side without requiring any user operation.

[0187] In variation 2-1, we take the example of a case where the first setting condition is met when a card application is made from a payment app. A user may apply for a card through other channels, not just through the payment service. For example, a user may apply for a card directly to the card service, or they may apply for a card through a service other than the payment service or the card service. The first setting unit 106 determines whether the first setting condition is met based on at least one of the application screen information and application details information stored in the payment database DB1.

[0188] For example, when a user applies for a card through a payment service, at least one of the application screen information and the application details information is stored in the payment database DB1, associated with the user's user ID. The first setting unit 106 determines that the first setting condition is not met if at least one of the application screen information and the application details information is not stored in the payment database DB1, and determines that the first setting condition is met if at least one of the application screen information and the application details information is stored in the payment database DB1.

[0189] For example, if the first setting unit 106 determines that the first setting condition is not met, it does not automatically set the card as the payment source or charge source. In this case, as in the second embodiment, the user manually sets the card as the payment source or charge source. If the first setting unit 106 determines that the first setting condition is met, it automatically sets the card as the payment source or charge source. The first setting unit 106 automatically sets the card as the payment source or charge source by updating the settlement database DB1 so that at least one of the payment source information and charge source information associated with the user's user ID indicates the card.

[0190] The payment system 1 in modified example 2-1 performs a determination to determine whether a predetermined first setting condition is met, and based on the result of this determination, automatically sets the card as the payment method to be used by the user in the payment service. As a result, the payment system 1 can eliminate the need for the user to manually set the card, thereby further enhancing user convenience.

[0191] [Modification 2-2] For example, the first setting condition is not limited to the example in Modification 2-1. Modifications 2-2 to 2-4 describe other examples of the first setting condition. The first setting unit 106 determines whether the first setting condition is met by determining whether a setting screen related to the setting of the payment method used by the user in the payment service is shown as an application screen in the application screen information. The setting of the payment method used by the user is the setting of the payment source or charge source, as in Modification 2-1.

[0192] The settings screen is a screen that accepts setting operations, or a screen for transitioning to such a screen. Modification 2-2 gives an example where the payment source setting screen SC2 and the charge source setting screen SC5 correspond to the settings screen. Therefore, where it says payment source setting screen SC2 or charge source setting screen SC5, it can be read as settings screen. The settings screen may also be another screen, such as the top screen SC1. The data indicating which screen is the settings screen is stored in the data storage unit 100. The first setting unit 106 can make a determination based on this data and the application screen information.

[0193] For example, the first setting unit 106 determines whether the payment source setting screen SC2 or the charge source setting screen SC5 is shown in the application screen information. If the payment source setting screen SC2 or the charge source setting screen SC5 is not shown in the application screen information, the first setting unit 106 determines that the first setting condition is not met, and if the payment source setting screen SC2 or the charge source setting screen SC5 is shown in the application screen information, it determines that the first setting condition is met. The processing after the determination of the first setting condition is the same as in the modified example 2-1.

[0194] The payment system 1 in modified example 2-2 determines whether the first setting condition is met by determining whether the setting screen related to the setting of the payment method used by the user in the payment service is shown as an application screen in the application screen information. If the user applies for a card using the setting screen as a gateway, there is a strong possibility that they want to set the card as the payment source or charge source in the payment service. Therefore, the payment system 1 can further enhance user convenience by automatically setting the card as the payment source or charge source.

[0195] [Modification 2-3] For example, as explained in Modification 1-6, the user may be allowed to start using the payment service without setting the payment source or charge source. In this case, the first setting unit 106 may determine whether the first setting condition is met by determining whether the payment method to be used by the user has been set in the payment service. The setting of the payment method to be used by the user is the setting of the payment source or charge source, as in Modifications 2-1 and 2-2.

[0196] For example, the first setting unit 106 determines whether the user has set up a payer or charge source based on the payer or charge source information stored in the settlement database DB1. If the user has not set up a payer or charge source, the payer or charge source information does not exist in the settlement database DB1, or the payer or charge source information indicates that the payer or charge source has not been set up. The first setting unit 106 determines that the first setting condition is not met if the user has set up a payer or charge source, and determines that the first setting condition is met if the user has not set up a payer or charge source. The processing after the determination of the first setting condition is the same as in the modified example 2-1.

[0197] The payment system 1 in modified example 2-3 determines whether the first setting condition is met by determining whether the payment method used by the user has been set up in the payment service. This allows the payment system 1 to perform flexible automatic settings according to the result of the determination. For example, the payment system 1 can improve user convenience by saving users who start using the payment service without setting up the payment source or charge source, by eliminating the need for them to set up the payment source or charge source.

[0198] [Modification 2-4] For example, the first setting unit 106 may determine whether the first setting condition has been met by determining whether a predetermined timing has occurred. The predetermined timing is the timing that serves as the basis for automatically setting the card as the payment source or charge source. In the modified example 2-4, the predetermined timing is given as an example where the timing is within a predetermined time (for example, within one week) after the card review is completed. The predetermined timing is determined for each user. The information indicating the predetermined timing is stored in the payment database DB1.

[0199] The designated timing is not limited to the examples above. For example, the designated timing may be the time when the card application is approved, the time when the card is dispatched, a certain amount of time has elapsed since the card was dispatched, the time when the card arrives, a certain amount of time has elapsed since the card arrived, or any other time. The payment service provider will specify in advance what constitutes the designated timing.

[0200] For example, the payment server 10 determines the timing for each user so that it matches the timing specified by the payment service provider. The payment server 10 may receive data from the card server 20 indicating at least one of the following: the timing when the card review is completed and the timing when the card is shipped, and identify at least one of these. The payment server 10 may also receive data from the delivery company's system indicating that the card has arrived, and identify the timing when the card has arrived.

[0201] For example, the first setting unit 106 obtains the current date and time using a known method such as a real-time clock or GPS. Based on the current date and time, the first setting unit 106 determines whether a predetermined timing has occurred. If the first setting unit 106 determines that the predetermined timing has not occurred, it determines that the first setting condition is not met, and if it determines that the predetermined timing has occurred, it determines that the first setting condition has been met. In cases where the current date and time is not required, such as when the card application is approved, when the card is shipped, or when the card arrives, the first setting unit 106 may determine whether the predetermined timing has occurred based on the content of communication with the card server 20, the delivery company's system, or another computer.

[0202] The payment system 1 in modified example 2-4 determines whether the first setting condition has been met by determining whether a predetermined timing has arrived. As a result, the payment system 1 can automatically set up the card as the payment source or charge source at the appropriate time, thereby further enhancing user convenience.

[0203] [Modification 2-5] For example, authentication of the card may be required when a user registers a card with a payment service or sets up a card as a payer or charge source. Authentication may be by any of the known methods. For example, possession authentication or knowledge authentication may be required. For example, it may be scan authentication performed by scanning the card, authentication using a security code printed on the card (e.g., so-called CVV authentication), authentication using a password (e.g., so-called 3D Secure authentication), or other authentication methods.

[0204] The payment system 1 in Modification 2-5 includes a necessity determination unit 107. The necessity determination unit 107 performs a determination of whether predetermined authentication necessity conditions have been met, and based on the result of the determination, determines whether authentication is required for the user to use the card in the payment service. The authentication necessity conditions are the conditions that serve as the basis for determining whether authentication is required or not. The authentication necessity conditions can be any predetermined conditions. For example, the authentication necessity conditions may be the same as the first setting conditions. In Modification 2-5, as with the first setting conditions in Modification 2-1, an example is given where the authentication necessity condition is that a card application is made from the payment app.

[0205] For example, the necessity determination unit 107 determines whether the authentication necessity conditions are met by determining whether or not a card application was made from the payment app based on at least one of the application screen information and the application details information, in the same manner as the first setting unit 106 in Modification 2-1. If the necessity determination unit 107 determines that no card application was made from the payment app, it determines that the authentication necessity conditions are not met, and if it determines that a card application was made from the payment app, it determines that the authentication necessity conditions are met.

[0206] The authentication requirements may be the same as the first setting conditions in Modifications 2-2 to 2-4. For example, the requirement determination unit 107 may determine whether the authentication requirements are met by determining whether the payment source setting screen SC2 or the charge source setting screen SC5 is shown in the application screen information, in the same manner as the first setting unit 106 in Modification 2-2. The requirement determination unit 107 determines that the authentication requirements are not met if the payment source setting screen SC2 or the charge source setting screen SC5 is not shown in the application screen information, and determines that the authentication requirements are met if the payment source setting screen SC2 or the charge source setting screen SC5 is shown in the application screen information.

[0207] For example, the necessity determination unit 107 may determine whether the authentication necessity conditions are met by determining whether the user has set up a payment source or charge source, similar to the first setting unit 106 in Modification 2-3. The necessity determination unit 107 determines that the necessity determination conditions are not met if the user has set up a payment source or charge source, and determines that the necessity determination conditions are met if the user has not set up a payment source or charge source.

[0208] For example, the necessity determination unit 107 may determine whether the authentication necessity conditions have been met by determining whether a predetermined timing has occurred, in the same manner as the first setting unit 106 in Modification 2-4. If the necessity determination unit 107 determines that the predetermined timing has not occurred, it determines that the necessity determination conditions have not been met, and if it determines that the predetermined timing has occurred, it determines that the necessity determination conditions have been met.

[0209] For example, the necessity determination unit 107 determines that authentication is not required if it determines that the authentication necessity conditions are not met, and determines that authentication is required if it determines that the authentication necessity conditions are met. If it is determined that authentication is not required, the user can set the card as the payment source or charge source without performing authentication. The process for setting the card as the payment source or charge source may be the same as in the second embodiment or modifications 2-1 to 2-4.

[0210] For example, if authentication is determined to be required, the payment server 10 performs authentication with the user terminal 30. The authentication process may be the same as known processes. For example, the payment server 10 performs scan authentication, CVV authentication, 3D Secure authentication, or other authentication with the user terminal 30. If authentication is successful, the payment server 10 allows the card to be set as the payment source or charge source.

[0211] The payment system 1 in modified example 2-5 performs a determination to determine whether predetermined authentication requirements are met, and based on the result of this determination, determines whether authentication is required for the user to use the card in the payment service. In this way, the payment system 1 can enhance security by requiring authentication for users who require it. The payment system 1 can reduce the effort required of users by omitting authentication for users who do not require it.

[0212] [Modification 2-6] For example, a user can apply for a card from either the payment source setting screen SC2 or the charge source setting screen SC5. If a user applies for a card from the payment source setting screen SC2, it is assumed that the user wants to set the card as the payment source, so the card may be automatically set as the payment source. This point is as explained in the modified example 2-2. On the other hand, the user may also want to set the card as the charge source. Therefore, after the payment source setting screen SC2 is displayed, the screen on the payment app may transition to the charge source setting screen SC5.

[0213] The payment system 1 of Modification 2-6 includes a first setting unit 106. The first setting unit 106 may be generally the same as in Modification 2-2, but in Modification 2-6, the user may manually perform the first setting. For example, the first setting unit 106 performs the first setting so that the first setting indicates a card when the first setting screen related to the first setting of the payment method used by the user for the first purpose in the payment service is shown as an application screen in the application screen information. The first setting unit 106 may also perform the first setting based on user operation. For example, the first setting unit 106 performs the first setting so that the first setting indicates a card when the user selects to use a card for the first purpose. The first setting unit 106 may also automatically perform the first setting so that the first setting indicates a card when the first setting screen is shown as an application screen in the application screen information. The process for automatically performing the first setting may be the same as in Modification 2-2. If there is a first settings screen (for example, a payment source settings screen SC2) and a second settings screen (for example, a charge source settings screen SC5), a user who applies from the first settings screen may be redirected to the first settings screen, and after the user completes the first settings, they may be redirected to the second settings screen. For example, there may be two methods for redirecting to the second settings screen: selecting a button for the redirection and automatic redirection.

[0214] Modification 2-6 takes an example where there are multiple setting screens as described in Modification 2-2. For example, there are multiple setting screens such as the payment source setting screen SC2 and the charge source setting screen SC5. The first setting screen is one of the multiple setting screens. Modification 2-6 takes an example where the payment source setting screen SC2 corresponds to the first setting screen. The purpose of using the payment method differs for each setting screen. The first purpose is the purpose of using the payment method set on the first setting screen. For example, if the first setting screen is the payment source setting screen SC2, the first purpose is payment. The first setting screen may also be the charge source setting screen SC5. In this case, the first purpose is charging.

[0215] Figure 22 shows an example of a screen displayed on the user terminal 30 in modified example 2-6. For example, if the first setting screen is shown in the application screen information and the first setting is performed, the display control unit 102 transitions from the first setting screen to the second setting screen related to the second setting of the payment method that the user will use for the second purpose in the payment service. The display control unit 102 may also transition from the first setting screen to the second setting screen if the user manually performs the first setting. The display control unit 102 may also transition from the first setting screen to the second setting screen if the first setting is performed automatically by the first setting unit 106. The second setting screen is a different setting screen from the first setting screen. The second purpose is the purpose of using the payment method set on the second setting screen. For example, the second setting is for charging purposes. If the first setting screen is the charging source setting screen SC5, then the second setting screen becomes the payment source setting screen SC2, and the second purpose is for payment purposes.

[0216] In the example shown in Figure 22, the user applied for a card from the payment source setting screen SC2, which is an example of the first setting screen. Therefore, the display control unit 102 displays the payment source setting screen SC2 on the user terminal 30, indicating that the card has been automatically set as the payment source. Subsequently, when the user performs an operation to transition to the next screen (for example, by selecting a button for screen transition displayed on the payment source setting screen SC2), the display control unit 102 displays the charge source setting screen SC5, which is an example of the second setting screen, on the user terminal 30, as shown in the lower left of Figure 22. The user performs the operation to set the card as the charge source in the same manner as in the second embodiment. Alternatively, after displaying the payment source setting screen SC2, which indicates that the card has been automatically set as the payment source, the user terminal 30 may automatically transition to the next screen (e.g., charge source setting screen SC5) without any operation by the user.

[0217] If the user applies for a card from the charge source setting screen SC5, then the charge source setting screen SC5 corresponds to the first setting screen. The display control unit 102 displays the charge source setting screen SC5 on the user terminal 30, indicating that the card has been automatically set as the charge source. Subsequently, when the user performs an operation to transition to the next screen, the display control unit 102 displays the payment source setting screen SC2, which is an example of the second setting screen, on the user terminal 30. The user performs the operation to set the card as the payment source in the same manner as in the second embodiment.

[0218] In the modified example 2-6, payment system 1 performs the first setting so that the first setting indicates a card when the first setting screen related to the first setting of the payment method used by the user for the first purpose in the payment service is shown as an application screen in the application screen information. When the first setting screen is shown in the application screen information and the first setting has been performed, payment system 1 transitions from the first setting screen to the second setting screen related to the second setting of the payment method used by the user for the second purpose in the payment service. As a result, payment system 1 can reduce the effort required for the user to perform screen transitions, thereby further improving user convenience.

[0219] Furthermore, if payment system 1 automatically performs the initial setup, it eliminates the need for the user to perform the initial setup, thereby further enhancing user convenience. When payment system 1 automatically performs the initial setup, it eliminates the need for the user to perform screen transitions, thus further enhancing user convenience.

[0220] [Modification 2-7] For example, in Modification 2-6, the case where the user manually sets the card as the payment source or charge source after a screen transition is given as an example, but the card may be automatically set as the payment source or charge source. In Modification 2-7, the display control unit 102 transitions to the first setting screen when the first setting screen related to the first setting of the payment method used by the user for the first purpose in the payment service is shown as an application screen in the application screen information. For example, similar to the second embodiment, the display control unit 102 transitions to the first setting screen when notification is selected on the notification screen SC6. In Modification 2-7 and later, the first setting may be performed manually by the user or automatically. The processing when the first setting is performed automatically is as described in Modifications 2-2 and 2-6.

[0221] The payment system 1 of Modification 2-7 further includes a second setting unit 108. When the first setting is performed so that the first setting indicates a card, the second setting unit 108 determines whether predetermined second setting conditions have been met, and based on the result of the determination, automatically performs the second setting so that the second setting of the payment method used by the user in the payment service indicates a card. The first setting conditions described in Modifications 2-1 to 2-4 are the conditions for the first setting as referred to in Modification 2-7, while the second setting conditions are the conditions for the second setting. The second setting conditions are the conditions that serve as the basis for deciding whether or not to perform the second setting. The second setting conditions can be any predetermined conditions.

[0222] For example, the second setting condition may be the same as the first setting condition. The second setting unit 108 determines whether the second setting condition is met in the same manner as the process by which the first setting unit 106 determines the first setting condition as described in Modifications 2-1 to 2-4. In this case, the processing of the second setting unit 108 can be performed by replacing "second" with "first" in Modifications 2-1 to 2-4.

[0223] For example, if the second setting unit 108 determines that the second setting condition is not met, it does not perform an automatic setting to indicate the card for the second setting. If it determines that the second setting condition is met, it performs an automatic setting to indicate the card for the second setting. If the charge source setting corresponds to the second setting, the second setting unit 108 updates the settlement database DB1 so that the charge source information indicates the card. If the payment source setting corresponds to the second setting, the second setting unit 108 updates the settlement database DB1 so that the payment source information indicates the card.

[0224] In the modified example 2-7, the payment system 1 transitions to the first setting screen when the first setting screen related to the first setting of the payment method used by the user for the first purpose in the payment service is shown as an application screen in the application screen information. When the first setting is performed so that the first setting indicates a card, the payment system 1 performs a determination to see if a predetermined second setting condition has been met. Based on the result of this determination, the payment system 1 automatically performs the second setting so that the second setting of the payment method used by the user in the payment service indicates a card. This eliminates the need for the user to manually perform the second setting, thereby improving user convenience.

[0225] [Modification 2-8] For example, in Modification 2-7, the second setting unit 108 may determine whether the second setting condition is met by determining whether the user has performed the second setting. The second setting unit 108 determines whether the user has performed the second setting based on the payment source information or charge source information stored in the settlement database DB1. If the user has not performed the second setting, the payment source information or charge source information does not exist in the settlement database DB1, or the payment source information or charge source information indicates that the second setting has not been performed. If the user has performed the second setting, the second setting unit 108 determines that the second setting condition is not met, and if the user has not performed the second setting, it determines that the second setting condition is met. The processing after the determination of the second setting condition is the same as in Modification 2-7.

[0226] The payment system 1 in modified example 2-8 determines whether the user's second setting has been performed, thereby determining whether the second setting condition has been met. This allows the payment system 1 to perform flexible automatic settings according to the result of the determination. For example, the payment system 1 can improve user convenience by saving users who started using the payment service without performing the second setting the trouble of performing the second setting.

[0227] [Modification 2-9] For example, in modified examples 2-7 and 2-8, the second setting unit 108 may determine whether the second setting condition has been met by determining whether a predetermined timing has occurred. The predetermined timing is a reference timing for making the second setting. The predetermined timing may be the same as in modified example 2-4. In modified example 2-9, the second setting unit 108 determines whether a predetermined timing has occurred in the same manner as the first setting unit 106 described in modified example 2-4. The predetermined timing may also be a timing within a predetermined time after the first setting has been made.

[0228] For example, the second setting unit 108 obtains the current date and time using a known method such as a real-time clock or GPS. Based on the current date and time, the second setting unit 108 determines whether a predetermined timing has occurred. If the second setting unit 108 determines that the predetermined timing has not occurred, it determines that the second setting condition is not met, and if it determines that the predetermined timing has occurred, it determines that the second setting condition has been met. In cases where the current date and time is not required, such as when the card application is approved, when the card is shipped, or when the card arrives, the second setting unit 108 may determine whether a predetermined timing has occurred based on the content of communication with the card server 20, the delivery company's system, or another computer.

[0229] The payment system 1 in modified example 2-9 determines whether the second setting condition has been met by determining whether a predetermined timing has arrived. As a result, the payment system 1 can automatically set up the card as the second setting at the appropriate timing, thereby further enhancing user convenience.

[0230] [Modification 2-10] For example, the display control unit 102 may transition to the first setting screen if the first setting screen related to the first setting of the payment method used by the user for the first purpose in the payment service is shown as an application screen in the application screen information. The processing in this case may be the same as in the second embodiment, modification 2-6, and modification 2-7.

[0231] The payment system 1 of Modification 2-10 further includes a necessity determination unit 107. The necessity determination unit 107 may have some processing similar to that of Modification 1-5, but the necessity determination unit 107 of Modification 2-10 performs a determination of whether predetermined authentication necessity conditions are met when the first setting screen is shown in the application screen information, and determines whether authentication is necessary for the second setting screen related to the second setting of the payment method used by the user for a second purpose in the payment service, and whether authentication is necessary for the second setting to indicate a card.

[0232] The meaning of the authentication requirement conditions is the same as in Modification 2-5. The method for determining the authentication requirement conditions may also be the same as in Modification 2-5. The authentication requirement conditions may be conditions such as whether or not authentication has been completed in the first setting, or whether or not a predetermined time has passed since authentication in the first setting. For example, the requirement determination unit 107 determines that authentication is not required if it determines that the authentication requirement conditions are not met, and determines that authentication is required if it determines that the authentication requirement conditions are met. If it is determined that authentication is not required, the second setting is performed without performing authentication. The flow of the second setting may be the same as in Modifications 2-7 to 2-9. For example, if it is determined that authentication is required, the payment server 10 performs authentication with the user terminal 30. The processing for authentication may be the same as in Modification 2-5, or the same as known processing. If authentication is successful, the payment server 10 permits the second setting.

[0233] In the modified version 2-10, payment system 1 transitions to the first setting screen when the first setting screen related to the first setting of the payment method used by the user for the first purpose in the payment service is shown as an application screen in the application screen information. When the first setting screen is shown in the application screen information, payment system 1 performs a determination of whether predetermined authentication requirements have been met, and based on the result of this determination, it determines whether authentication is required for the second setting screen related to the second setting of the payment method used by the user for the second purpose in the payment service, specifically for the second setting to indicate a card. In this way, payment system 1 can enhance security by requiring authentication for users who require it. Payment system 1 can reduce user effort by omitting authentication for users who do not require it.

[0234] [Variation 2-11] For example, in the second embodiment, a notification indicating that the card application has been approved was given on the notification screen SC6, but this notification may be given on any screen within the payment app. For example, the notification indicating that the card application has been approved may be given on the top screen SC1. Furthermore, if the user selects a notification on the top screen SC1, at least one of the payment source and charge source may be automatically set on the card.

[0235] The payment system 1 in Modification 2-11 includes an availability notification unit 109 and a third setting unit 110. The availability notification unit 109 issues an availability notification indicating that the card is now available for use with the payment service after the card review is complete. The availability notification may be any notification issued on the payment app. In Modification 2-11, an example is given where a notification on the top screen SC1 corresponds to the availability notification, but a notification on the notification screen SC6 or another screen may also correspond to the availability notification.

[0236] Figure 23 shows an example of a screen displayed on the user terminal 30 in modified example 2-11. As shown on the left side of Figure 23, the availability notification unit 109 displays window W14, an example of an availability notification, on the top screen SC1. The availability notification unit 109 may also be a function of the display control unit 102. The availability notification unit 109 determines whether the review has been completed based on the status. When the status indicates that the review has been completed, the availability notification unit 109 displays window W14 on the top screen SC1. For example, window W14 includes a button B140 for setting the card as the payment source and a button B141 for not setting the card as the payment source.

[0237] The third setting unit 110 automatically sets the card as the payment method to be used by the user in the payment service when the user selects an available notification (for example, when the user selects button B140 in window W14, which is an example of an available notification). The third setting unit 110 automatically sets the card as the payer or charge source by updating the payment database DB1 so that at least one of the payer information and charge source information associated with the user's user ID indicates the card. The third setting unit 110 automatically sets the card as the payment method to be used by the user in the payment service when the user does not select an available notification (for example, when the user does not select button B140 in window W14, which is an example of an available notification). For example, if the user selects button B141, the third setting unit 110 does not automatically set the card as the payer or charge source.

[0238] In the modified version 2-11, payment system 1 issues an availability notification after the card application has been approved, indicating that the card is now available for use with the payment service. If the user selects to receive the availability notification, payment system 1 automatically sets the card as the payment method the user will use with the payment service. This eliminates the need for the user to manually configure the settings, thereby enhancing user convenience.

[0239] [3-3. Other variations] For example, the above variations may be combined.

[0240] For example, in this embodiment, we have given an example of a user using a payment app to access the payment service, but the user may also use the payment service through the browser on the user terminal 30. In this case, the user may execute the payment when the code C10 displayed in the browser is read at the store, or the user may execute the payment online without using code C10 at a store. Online payments are completed solely through operations on the user terminal 30. For example, the user may execute payments for online e-commerce services, e-book services, travel booking services, communication services, or other services from the browser.

[0241] For example, the functions described as being implemented by the payment server 10 may be implemented by the card server 20, the user terminal 30, or other computers. The processing described as being implemented by the payment server 10 may be shared among multiple computers. The processing described as being implemented by the card server 20 may be implemented by the payment server 10, the user terminal 30, or other computers. The processing described as being implemented by the user terminal 30 may be implemented by the payment server 10, the card server 20, or other computers.

[0242] [4. Addendum] For example, a payment system can also be configured as follows:

[0243] [4-1. Notes on the First Embodiment] For example, the payment system of the first embodiment can also be configured as follows: (1-1) A card that supports payment services, comprising a status acquisition unit that acquires the status of the user's card, A display control unit that displays content related to the card on a related screen associated with the payment service based on the status, A payment system that includes this. (1-2) The status acquisition unit acquires the status indicating whether or not the user possesses the card, The display control unit, based on the status indicating whether or not the user possesses the card, causes the related screen related to the setting of the payment method used by the user in the payment service to display the content related to the application for the card. The payment system described in (1-1). (1-3) The status acquisition unit acquires the status indicating whether or not the card is set as the payment method used by the user in the payment service. Based on the status indicating whether or not the card is set as a payment method used by the user in the payment service, the display control unit causes the related screen related to the setting of the payment method used by the user in the payment service to display the content related to the setting of the card. The payment system described in (1-1) or (1-2). (1-4) The display control unit performs a determination to determine whether a predetermined payment method is set as the payment method used by the user in the payment service, and based on the result of the determination, displays the content related to the setting of the card on the related screen related to the setting of the payment method used by the user in the payment service. The payment system described in any of (1-1) to (1-3). (1-5) The display control unit causes the related screen related to the setting of the payment method used by the user in the payment service to display the content corresponding to the relationship between the business operator setting up the payment method and the card operator related to the card. The payment system described in (1-4). (1-6) The status acquisition unit acquires the status indicating whether or not the user has applied for the card, The display control unit displays the content related to the application for the card on the related screen related to the setting of the payment method used by the user in the payment service, based on the status indicating whether or not the user has applied for the card. The payment system described in any of (1-1) to (1-5). (1-7) The display control unit performs a determination to determine whether or not a card other than the card is set as the payment means used by the user in the payment service, and displays the content according to the result of the determination. The payment system described in any of (1-1) to (1-6). (1-8) The display control unit determines whether the user has started using the payment service without setting a payment method to be used in the payment service, and displays the content according to the result of the determination. The payment system described in any of (1-1) to (1-7). (1-9) The status acquisition unit acquires the status indicating whether the user has interrupted the application for the card, The display control unit, based on the status indicating whether the user has interrupted the application for the card, causes the related screen to display the content for the user to resume the application for the card. The payment system described in any of (1-1) to (1-8). (1-10) The aforementioned payment system If the user interrupts the application for the card, the input information storage unit stores at least some of the input information that the user has entered up to that point. When the user resumes applying for the card, the resume unit resumes the application for the card based on at least some of the input information stored by the input information storage unit, The payment systems described in (1-9) further include the following. (1-11) The status acquisition unit acquires the status indicating whether the user has passed the review of the card. Based on the status indicating whether the user has passed the review of the card, the display control unit causes the related screen to display the content for the user to apply for the card again. The payment system according to any one of (1-1) to (1-10). (1-12) The user uses the payment service from a payment application stored in the user's user terminal. When the user selects a link for starting the payment application on the user terminal, the status acquisition unit acquires the status. When the user selects the link, the display control unit causes the related screen displayed on the payment application to display the content. The payment system according to any one of (1-1) to (1-11). (1-13) The user uses the payment service from a payment application stored in the user's user terminal. Based on whether the user holds the card, the display control unit causes the related screen displayed on the payment application to display the content for the user to use the functions related to the card. The payment system according to any one of (1-1) to (1-12). (1-14) The display control unit executes a determination as to whether the payment made by the user in the payment service satisfies a predetermined content display condition, and based on the execution result of the determination, causes the related screen indicating that the payment has been completed to display the content. The payment system according to any one of (1-1) to (1-13).

[0244] [4-2. Additional Notes on the Second Embodiment] For example, the payment system of the second embodiment can also have the following configuration. (2-1) In a payment service that allows users to apply for a card from multiple application screens, an application screen information acquisition unit acquires application screen information relating to the application screen on which the user applied for the card, among the multiple application screens. A display control unit that controls the transition of screens displayed in the payment service based on the application screen information, A payment system that includes this. (2-2) The display control unit, when a settings screen related to the setting of the payment method used by the user in the payment service is shown as the application screen in the application screen information, will transition to the settings screen. The payment system described in (2-1). (2-3) The payment system further includes a first setting unit that performs a determination of whether or not a predetermined first setting condition is met, and based on the result of the determination, automatically sets the card as the payment means to be used by the user in the payment service. The payment system described in (2-1) or (2-2). (2-4) The first setting unit performs a determination to determine whether the first setting condition is met by determining whether a setting screen related to the setting of the payment method used by the user in the payment service is shown in the application screen information as the application screen. The payment system described in (2-3). (2-5) The first setting unit performs a determination to determine whether the payment method used by the user has been set in the payment service, thereby determining whether the first setting condition has been met. The payment system described in (2-3) or (2-4). (2-6) The first setting unit performs a determination of whether the first setting condition has been met by determining whether a predetermined timing has occurred. The payment system described in any of (2-3) to (2-5). (2-7) The payment system further includes a necessity determination unit that performs a determination of whether predetermined authentication requirements have been met and, based on the result of the determination, determines whether authentication is required for the user to use the card in the payment service. The payment system described in any of (2-1) to (2-6). (2-8) The payment system further includes a first setting unit that performs the first setting so that the first setting indicates the card when a first setting screen related to the first setting of a payment method used by the user for a first purpose in the payment service is shown in the application screen information as the application screen, The display control unit, when the first setting screen is shown in the application screen information and the first setting is performed, transitions from the first setting screen to a second setting screen related to the second setting of the payment method used by the user for the second purpose in the payment service. The payment system described in any of (2-1) to (2-7). (2-9) The first setting unit automatically performs the first setting so that the first setting indicates the card when the first setting screen is shown as the application screen in the application screen information. The display control unit, when the first setting screen is shown in the application screen information and the first setting is performed automatically, transitions from the first setting screen to the second setting screen. The payment system described in (2-8). (2-10) The display control unit, when the first setting screen related to the first setting of the payment method used by the user for the first purpose in the payment service is shown as the application screen in the application screen information, transitions to the first setting screen. The payment system further includes a second setting unit that, when the first setting is made so that the first setting indicates the card, determines whether a predetermined second setting condition has been met, and based on the result of the determination, automatically performs the second setting so that the second setting of the payment method used by the user in the payment service indicates the card. The payment system described in any of (2-1) to (2-9). (2-11) The second setting unit performs a determination of whether the second setting condition has been met by determining whether the user's second setting has been performed. The payment system described in (2-10). (2-12) The second setting unit determines whether the second setting condition has been met by determining whether a predetermined timing has occurred. The payment system described in (2-10) or (2-11). (2-13) The display control unit, when the first setting screen related to the first setting of the payment method used by the user for the first purpose in the payment service is shown as the application screen in the application screen information, transitions to the first setting screen. The payment system further includes a necessity determination unit that, when the first setting screen is shown in the application screen information, determines whether predetermined authentication requirements have been met, and determines, based on the result of the determination, whether authentication is necessary for the second setting screen relating to the second setting of a payment method used by the user for a second purpose in the payment service, wherein the second setting indicates the card. The payment system described in any of (2-1) to (2-12). (2-14) The aforementioned payment system An availability notification unit that, after the card's review is completed, issues an availability notification indicating that the card has become available for use with the payment service, A third setting unit that automatically sets the card as the payment method to be used by the user in the payment service when the user selects the available notification, A payment system described in any of (2-1) to (2-13), which further includes the above. [Explanation of Symbols]

[0245] 1 Payment system, N Network, 10 Payment server, 11,21,31 Control unit, 12,22,32 Storage unit, 13,23,33 Communication unit, 20 Card server, 30 User terminal, 34 Operation unit, 35 Display unit, 100 Data storage unit, 101 Status acquisition unit, 102 Display control unit, 103 Application screen information acquisition unit, 104 Input information storage unit, 105 Restart unit, 106 First setting unit, 107 Necessity / Determination unit, 108 Second setting unit, 109 Available notification unit, 110 Third setting unit, 200 Data storage unit, 201 Card management unit, 300 Data storage unit, 301 Operation reception unit, 302 Display control unit, B11,B12,B60 Buttons, C10 Code, DB1 Payment database, DB2 Card database, A13 Display area, L70 Links, P20, P21, P22, P23, P24, P50, P51, P52, P53, P54, P90 Panels, SC1 Top screen, SC2 Payment source setting screen, SC3 Application screen, SC4 Completion screen, SC5 Charge source setting screen, SC6 Notification screen, SC7 Link screen, SC8 Card screen, SC9 Payment completion screen, W13 Window, I130 Icons.

Claims

1. A card that supports payment services, comprising a status acquisition unit that acquires the status of the user's card, A display control unit that displays content related to the card on a related screen associated with the payment service based on the status, A payment system that includes this.

2. The status acquisition unit acquires the status indicating whether or not the user possesses the card, The display control unit, based on the status indicating whether or not the user possesses the card, causes the related screen related to the setting of the payment method used by the user in the payment service to display the content related to the application for the card. The payment system according to claim 1.

3. The status acquisition unit acquires the status indicating whether or not the card is set as the payment method used by the user in the payment service. Based on the status indicating whether or not the card is set as a payment method used by the user in the payment service, the display control unit causes the related screen related to the setting of the payment method used by the user in the payment service to display the content related to the setting of the card. The payment system according to claim 1 or 2.

4. The display control unit performs a determination to determine whether a predetermined payment method is set as the payment method used by the user in the payment service, and based on the result of the determination, displays the content related to the setting of the card on the related screen related to the setting of the payment method used by the user in the payment service. The payment system according to claim 1 or 2.

5. The display control unit causes the related screen related to the setting of the payment method used by the user in the payment service to display the content corresponding to the relationship between the business operator setting up the payment method and the card operator related to the card. The payment system according to claim 4.

6. The status acquisition unit acquires the status indicating whether or not the user has applied for the card, The display control unit displays the content related to the application for the card on the related screen related to the setting of the payment method used by the user in the payment service, based on the status indicating whether or not the user has applied for the card. The payment system according to claim 1 or 2.

7. The display control unit performs a determination to determine whether or not a card other than the card is set as the payment means used by the user in the payment service, and displays the content according to the result of the determination. The payment system according to claim 1 or 2.

8. The display control unit determines whether the user has started using the payment service without setting a payment method to be used in the payment service, and displays the content according to the result of the determination. The payment system according to claim 1 or 2.

9. The status acquisition unit acquires the status indicating whether the user has interrupted the application for the card, The display control unit, based on the status indicating whether the user has interrupted the application for the card, causes the related screen to display the content for the user to resume the application for the card. The payment system according to claim 1 or 2.

10. The aforementioned payment system If the user interrupts the application for the card, the input information storage unit stores at least some of the input information that the user has entered up to that point. When the user resumes applying for the card, the resume unit resumes the application for the card based on at least some of the input information stored by the input information storage unit, The settlement system according to claim 9, further comprising:

11. The status acquisition unit acquires the status indicating whether or not the user has passed the card screening, The display control unit displays the content on the related screen for the user to apply for the card again, based on the status indicating whether or not the user has passed the card application review. The payment system according to claim 1 or 2.

12. The user uses the payment service from the payment application stored on the user's terminal. The status acquisition unit acquires the status when the user selects a link to launch the payment application on the user terminal. The display control unit causes the content to be displayed on the related screen shown on the payment app when the user selects the link. The payment system according to claim 1 or 2.

13. The user uses the payment service from the payment application stored on the user's terminal. The display control unit, based on whether or not the user possesses the card, causes the related screen displayed on the payment app to display the content that allows the user to use the card's functions. The payment system according to claim 1 or 2.

14. The display control unit performs a determination to determine whether the payment made by the user in the payment service satisfies predetermined content display conditions, and based on the result of the determination, displays the content on the related screen indicating that the payment has been completed. The payment system according to claim 1 or 2.

15. A card that supports a payment service, comprising a status acquisition step of obtaining the status of the user's card, A display control step that causes content related to the card to be displayed on a related screen associated with the payment service based on the status, A display control method including the following.

16. A card that supports payment services, and a status acquisition unit that acquires the status of the user's card, A display control unit that displays content related to the card on a related screen associated with the payment service based on the status, A program that makes a computer function.

Images